Bluetooth dies after a while.
A message that is not in the archive (sent off-list or not yet received): [email protected]/
https://bugzilla.kernel.org/show_bug.cgi?id=198303
--- Comment #5 from Nick ([email protected]) --- Created attachment 280027
--> https://bugzilla.kernel.org/attachment.cgi?id=280027&action=edit
btmon.log
Experiencing the same issue as the original reporter. Attached is the result of the btmon.log command, where the error occurred ~1-3 seconds after the error occurred.
Signature · 2 lines
You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=198303
--- Comment #6 from Nick ([email protected]) ---
Other details: the issue started after I updated to Ubuntu 18.10 (didn't seem to be present in 18.04).
There are complicating factors in my setup: I'm using an Intel 7260 PCIe WiFi/Bluetooth adapter which has pins 20 and 51 masked (the issue occurred with only pin 51 masked prior).
Signature · 2 lines
You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=198303
Mika Norén ([email protected]) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |PATCH_ALREADY_AVAILABLE--- Comment #7 from Mika Norén ([email protected]) --- (In reply to Grzegorz from comment #4)
Quoted 6 lines
It would be helpfull if you attach logs from btmon (example: sudo btmon -i 0 -w btmon.log) and from bluetoothd (sudo valgrind ./bluetoothd -n -d) - bluetoothd from bluez sources (you can checkout to 5.47-4 tag).
Regards,
Grzegorz
As this issue has been solved in later kernel versions, I see no reason to keep this open. Can be marked as solved.
I'm not sure when it was solved though. Everything started to work as intended after an update some time ago.
Signature · 2 lines
You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=198303
--- Comment #8 from Mika Norén ([email protected]) ---
If anyone hits this particular problem, please update your kernel to 4.18.20 or later.
Signature · 2 lines
You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=198303
--- Comment #9 from Nick ([email protected]) ---
Just updated to 4.18.20, issue not resolved. Should I open a new issue?
Signature · 2 lines
You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=198303
--- Comment #10 from Mika Norén ([email protected]) --- Yes, please do. :-)
Quoted 8 lines · On Mon, 17 Dec 2018, 21:07 <[email protected] wrote:
https://bugzilla.kernel.org/show_bug.cgi?id=198303
--- Comment #9 from Nick ([email protected]) ---
Just updated to 4.18.20, issue not resolved. Should I open a new issue?--
You are receiving this mail because:
You reported the bug.
Signature · 2 lines
You are receiving this mail because: You are the assignee for the bug.