-
Notifications
You must be signed in to change notification settings - Fork 103
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RFCOMM, patchram results in HARDLOCK crash #7
Comments
I'll update this patch to also contain, these few lines which I had missed. `diff -urN a/net/bluetooth/l2cap_core.c b/net/bluetooth/l2cap_core.c -void l2cap_chan_destroy(struct l2cap_chan *chan)
write_lock(&chan_list_lock);
+void l2cap_chan_hold(struct l2cap_chan *c)
+void l2cap_chan_put(struct l2cap_chan *c)
void __l2cap_chan_add(struct l2cap_conn *conn, struct l2cap_chan *chan)
static struct l2cap_conn *l2cap_conn_add(struct hci_conn *hcon, u8 status)atus) /* Kill poor orphan */
|
Hello,
Recently - (and on behalf of eers 4.0 and Atlants Embedded), we have been using the FriendlyArm kernel, but it suffered from a stacktrace and CPU hardlock from IRQs when using patchram, RFCOMM and HCI (if you want BLE - which we did). Attached to this ticket is our conglomeration of backport patches.
With copious amounts of debugging information, you will receive a stack trace which looks like the following for CPU hardlocks/softlocks etc... while using patchram to load the AP6212 firmware (that runs in the background using & and --enable_hci & --baudrate 112500), and for a "random" period of time, it may or may not receive BT connections (we were also broadcasting BLE beacons). This was realized because the amba tty and the tty itself were struggling with spinlocks. I also backported some barrier patches from Linus, and l2comm segfaults which were discovered at the sametime during "fixing".
Here is the stacktrace:
And here is our fix. FriendlyArm (Jensen) can you merge this fix into the tree with credits to Atlants Embedded and eers 4.0?
Thanks!
eers-atlantsembedded-bt-rfcomm.txt
The text was updated successfully, but these errors were encountered: