[Bug 1193124] New: tumbleweed release 20211124 with kernel 5.15.3 bluetooth fail
http://bugzilla.opensuse.org/show_bug.cgi?id=1193124 Bug ID: 1193124 Summary: tumbleweed release 20211124 with kernel 5.15.3 bluetooth fail Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs@opensuse.org Reporter: tech@reachthetribes.org QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- My pc is an ASUS ZenBook Flip S UX371EA. This does not seem to be a duplicate After tumbleweed release 20211124 with kernel update to 5.15.3, bluetooth fails to operate. It no longer shows up in the system tray, the bluetooth service under systemctl doesn't start, and the btusb module is not loaded to the new kernel. When it is manually added to the kernel and the bluetooth service is started, the bluetooth icon comes back to the system tray, but bluetooth will not pick up any devices. Here are the command results: on the 5.15 kernel
sudo rfkill ID TYPE DEVICE SOFT HARD 0 wlan asus-wlan unblocked unblocked 1 bluetooth asus-bluetooth unblocked unblocked 2 wlan phy0 unblocked unblocked
When this command is run in the 5.14 kernel, there is another line that comes out that is missing here: 3 bluetooth hci0 unblocked unblocked on the 5.15 kernel, lsusb doesn't read anything with bluetooth
lsusb Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 003: ID 13d3:56eb IMC Networks USB2.0 HD UVC WebCam Bus 003 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
When this is run on the 5.14 kernel, the bluetooth adaptor shows up: Bus 003 Device 004: ID 8087:0026 Intel Corp. AX201 Bluetooth For journalctl on the 5.15 kernel:
journalctl -b | egrep -i bluetooth Nov 26 20:27:44 asustribetrek NetworkManager[780]: <info> [1637980064.3080] Loaded device plugin: NMBluezManager (/usr/lib64/NetworkManager/1.32.12/libnm-device-plugin-bluetooth.so) Nov 26 20:27:48 asustribetrek systemd[1]: Condition check resulted in Bluetooth service being skipped. Nov 26 20:27:50 asustribetrek kded5[1660]: bluedevil: Bluetooth operational changed false Nov 26 20:28:14 asustribetrek systemd[1]: Condition check resulted in Bluetooth service being skipped. Nov 26 20:31:29 asustribetrek systemd[1]: Condition check resulted in Bluetooth service being skipped. Nov 26 20:31:30 asustribetrek kded5[5664]: bluedevil: Bluetooth operational changed false
journalctl -b | egrep -i bluetooth Nov 26 20:35:16 asustribetrek NetworkManager[790]: <info> [1637980516.4366] Loaded device plugin: NMBluezManager (/usr/lib64/NetworkManager/1.32.12/libnm-device-plugin-bluetooth.so) Nov 26 20:35:17 asustribetrek kernel: Bluetooth: Core ver 2.22 Nov 26 20:35:17 asustribetrek kernel: NET: Registered PF_BLUETOOTH protocol family Nov 26 20:35:17 asustribetrek kernel: Bluetooth: HCI device and connection manager initialized Nov 26 20:35:17 asustribetrek kernel: Bluetooth: HCI socket layer initialized Nov 26 20:35:17 asustribetrek kernel: Bluetooth: L2CAP socket layer initialized Nov 26 20:35:17 asustribetrek kernel: Bluetooth: SCO socket layer initialized Nov 26 20:35:17 asustribetrek kernel: Bluetooth: hci0: Bootloader revision 0.4 build 0 week 30 2018 Nov 26 20:35:17 asustribetrek kernel: Bluetooth: hci0: Device revision is 2 Nov 26 20:35:17 asustribetrek kernel: Bluetooth: hci0: Secure boot is enabled Nov 26 20:35:17 asustribetrek kernel: Bluetooth: hci0: OTP lock is enabled Nov 26 20:35:17 asustribetrek kernel: Bluetooth: hci0: API lock is enabled Nov 26 20:35:17 asustribetrek kernel: Bluetooth: hci0: Debug lock is disabled Nov 26 20:35:17 asustribetrek kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014 Nov 26 20:35:17 asustribetrek kernel: Bluetooth: hci0: Found device firmware: intel/ibt-19-0-4.sfi Nov 26 20:35:17 asustribetrek systemd[1]: Starting Bluetooth service... Nov 26 20:35:17 asustribetrek bluetoothd[1432]: Bluetooth daemon 5.62 Nov 26 20:35:17 asustribetrek systemd[1]: Started Bluetooth service. Nov 26 20:35:17 asustribetrek systemd[1]: Reached target Bluetooth Support. Nov 26 20:35:17 asustribetrek bluetoothd[1432]: Starting SDP server Nov 26 20:35:17 asustribetrek bluetoothd[1432]: Bluetooth management interface 1.21 initialized Nov 26 20:35:17 asustribetrek kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3 Nov 26 20:35:17 asustribetrek kernel: Bluetooth: BNEP filters: protocol multicast Nov 26 20:35:17 asustribetrek kernel: Bluetooth: BNEP socket layer initialized Nov 26 20:35:19 asustribetrek kernel: Bluetooth: hci0: Waiting for firmware download to complete Nov 26 20:35:19 asustribetrek kernel: Bluetooth: hci0: Firmware loaded in 1694554 usecs Nov 26 20:35:19 asustribetrek kernel: Bluetooth: hci0: Waiting for device to boot Nov 26 20:35:19 asustribetrek kernel: Bluetooth: hci0: Device booted in 14663 usecs Nov 26 20:35:19 asustribetrek kernel: Bluetooth: hci0: Found Intel DDC
journalctl on the 5.14 kernel had significantly more results, as expected: parameters: intel/ibt-19-0-4.ddc Nov 26 20:35:19 asustribetrek kernel: Bluetooth: hci0: Applying Intel DDC parameters completed Nov 26 20:35:19 asustribetrek kernel: Bluetooth: hci0: Firmware revision 0.4 build 5 week 39 2021 Nov 26 20:35:19 asustribetrek bluetoothd[1432]: Admin Policy Set interface registered Nov 26 20:35:19 asustribetrek bluetoothd[1432]: Admin Policy Status interface registered Nov 26 20:35:22 asustribetrek bluetoothd[1432]: Player registered: sender=:1.33 path=/media_player0 Nov 26 20:35:22 asustribetrek kernel: Bluetooth: RFCOMM TTY layer initialized Nov 26 20:35:22 asustribetrek kernel: Bluetooth: RFCOMM socket layer initialized Nov 26 20:35:22 asustribetrek kernel: Bluetooth: RFCOMM ver 1.11 Nov 26 20:35:22 asustribetrek bluetoothd[1432]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/ldac Nov 26 20:35:22 asustribetrek bluetoothd[1432]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSink/aptx_hd Nov 26 20:35:22 asustribetrek bluetoothd[1432]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/aptx_hd Nov 26 20:35:22 asustribetrek bluetoothd[1432]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSink/aptx Nov 26 20:35:22 asustribetrek bluetoothd[1432]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/aptx Nov 26 20:35:22 asustribetrek bluetoothd[1432]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/aac Nov 26 20:35:22 asustribetrek bluetoothd[1432]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSink/sbc Nov 26 20:35:22 asustribetrek bluetoothd[1432]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/sbc Nov 26 20:35:22 asustribetrek bluetoothd[1432]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSink/sbc_xq Nov 26 20:35:22 asustribetrek bluetoothd[1432]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/sbc_xq Nov 26 20:35:22 asustribetrek bluetoothd[1432]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/faststream Nov 26 20:35:22 asustribetrek bluetoothd[1432]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/faststream_duplex Nov 26 20:35:22 asustribetrek bluetoothd[1432]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/aptx_ll_1 Nov 26 20:35:22 asustribetrek bluetoothd[1432]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/aptx_ll_0 Nov 26 20:35:22 asustribetrek bluetoothd[1432]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1 Nov 26 20:35:22 asustribetrek bluetoothd[1432]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0 Nov 26 20:35:24 asustribetrek kded5[1784]: bluedevil: Bluetooth operational changed true For dmesg on the 5.15 kernel, the results were empty:
dmesg | grep -i bluetooth
For dmesg on the 5.14 kernel, there were lots of results as expected:
dmesg | grep -i bluetooth [ 5.769571] Bluetooth: Core ver 2.22 [ 5.769616] NET: Registered PF_BLUETOOTH protocol family [ 5.769618] Bluetooth: HCI device and connection manager initialized [ 5.769622] Bluetooth: HCI socket layer initialized [ 5.769628] Bluetooth: L2CAP socket layer initialized [ 5.769633] Bluetooth: SCO socket layer initialized [ 5.915512] Bluetooth: hci0: Bootloader revision 0.4 build 0 week 30 2018 [ 5.916500] Bluetooth: hci0: Device revision is 2 [ 5.916511] Bluetooth: hci0: Secure boot is enabled [ 5.916513] Bluetooth: hci0: OTP lock is enabled [ 5.916514] Bluetooth: hci0: API lock is enabled [ 5.916515] Bluetooth: hci0: Debug lock is disabled [ 5.916516] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 5.963172] Bluetooth: hci0: Found device firmware: intel/ibt-19-0-4.sfi [ 6.003424] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 6.003428] Bluetooth: BNEP filters: protocol multicast [ 6.003431] Bluetooth: BNEP socket layer initialized [ 7.696847] Bluetooth: hci0: Waiting for firmware download to complete [ 7.698400] Bluetooth: hci0: Firmware loaded in 1694554 usecs [ 7.698487] Bluetooth: hci0: Waiting for device to boot [ 7.713473] Bluetooth: hci0: Device booted in 14663 usecs [ 7.714204] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc [ 7.716402] Bluetooth: hci0: Applying Intel DDC parameters completed [ 7.719474] Bluetooth: hci0: Firmware revision 0.4 build 5 week 39 2021 [ 11.170866] Bluetooth: RFCOMM TTY layer initialized [ 11.170873] Bluetooth: RFCOMM socket layer initialized [ 11.170877] Bluetooth: RFCOMM ver 1.11
-- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193124 http://bugzilla.opensuse.org/show_bug.cgi?id=1193124#c1 Harri Miettinen <harmie@opensuse.fi> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |harmie@opensuse.fi --- Comment #1 from Harri Miettinen <harmie@opensuse.fi> --- I have same issue with lenovo aio700. I can provide logs if needed. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193124 http://bugzilla.opensuse.org/show_bug.cgi?id=1193124#c2 Vignesh D <vignesh0025@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vignesh0025@gmail.com --- Comment #2 from Vignesh D <vignesh0025@gmail.com> --- I too have same issue in TW. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193124 http://bugzilla.opensuse.org/show_bug.cgi?id=1193124#c3 --- Comment #3 from Vignesh D <vignesh0025@gmail.com> --- I too have same issue in TW. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193124 Vignesh D <vignesh0025@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193124 http://bugzilla.opensuse.org/show_bug.cgi?id=1193124#c4 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai@suse.com --- Comment #4 from Takashi Iwai <tiwai@suse.com> --- Could you give the full output of dmesg after boot from both working (5.14.x?) and broken (5.15.x) kernels? Also get the output of hwinfo command from both, too. Please upload them via attachments on Bugzilla (don't paste). Last but not least, please try the latest 5.15.x kernel in OBS Kernel:stable repo. http://download.opensuse.org/repositories/Kernel:/stable/standard/ Note that it's an unofficial build, hence it won't boot with Secure Boot. Disable Secure Boot beforehand, if any. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193124 http://bugzilla.opensuse.org/show_bug.cgi?id=1193124#c5 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P3 - Medium |P5 - None --- Comment #5 from Takashi Iwai <tiwai@suse.com> --- BTW, please don't touch the Priority field on Bugzilla. It's the field adjusted only by the developer side. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193124 http://bugzilla.opensuse.org/show_bug.cgi?id=1193124#c6 --- Comment #6 from Harri Miettinen <harmie@opensuse.fi> --- Created attachment 854102 --> http://bugzilla.opensuse.org/attachment.cgi?id=854102&action=edit dmesg_5.15.3-1-default -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193124 http://bugzilla.opensuse.org/show_bug.cgi?id=1193124#c7 --- Comment #7 from Harri Miettinen <harmie@opensuse.fi> --- Created attachment 854103 --> http://bugzilla.opensuse.org/attachment.cgi?id=854103&action=edit dmesg_5.15.5-1.g83fc974-default -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193124 http://bugzilla.opensuse.org/show_bug.cgi?id=1193124#c8 --- Comment #8 from Harri Miettinen <harmie@opensuse.fi> --- Created attachment 854104 --> http://bugzilla.opensuse.org/attachment.cgi?id=854104&action=edit hwinfo_5.15.3-1-default -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193124 http://bugzilla.opensuse.org/show_bug.cgi?id=1193124#c9 --- Comment #9 from Harri Miettinen <harmie@opensuse.fi> --- Created attachment 854105 --> http://bugzilla.opensuse.org/attachment.cgi?id=854105&action=edit hwinfo_5.15.5-1.g83fc974-default -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193124 http://bugzilla.opensuse.org/show_bug.cgi?id=1193124#c10 --- Comment #10 from Harri Miettinen <harmie@opensuse.fi> --- I have attached requested logs from 5.15.3 and 5.15.5 kernels. Both version have same issue. I will try to install 5.14.x later today. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193124 http://bugzilla.opensuse.org/show_bug.cgi?id=1193124#c11 --- Comment #11 from Harri Miettinen <harmie@opensuse.fi> --- I didn't find 5.14.x kernel so I can't test that. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193124 http://bugzilla.opensuse.org/show_bug.cgi?id=1193124#c12 --- Comment #12 from Takashi Iwai <tiwai@suse.com> --- (In reply to Harri Miettinen from comment #11)
I didn't find 5.14.x kernel so I can't test that.
You can find it in TW history repo, http://download.opensuse.org/history/ BTW, I recommend to increase the number of installable kernels by editing /etc/zypp/zypp.conf beforehand. Add more entries in multiversion.kernels line. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193124 http://bugzilla.opensuse.org/show_bug.cgi?id=1193124#c13 --- Comment #13 from Harri Miettinen <harmie@opensuse.fi> --- Created attachment 854116 --> http://bugzilla.opensuse.org/attachment.cgi?id=854116&action=edit dmesg_5.14.14-3-default -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193124 http://bugzilla.opensuse.org/show_bug.cgi?id=1193124#c14 --- Comment #14 from Harri Miettinen <harmie@opensuse.fi> --- Created attachment 854117 --> http://bugzilla.opensuse.org/attachment.cgi?id=854117&action=edit hwinfo_5.14.14-3-default -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193124 http://bugzilla.opensuse.org/show_bug.cgi?id=1193124#c15 --- Comment #15 from Harri Miettinen <harmie@opensuse.fi> --- I have now attached logs using 5.14.14-3 kernel and bluetooth works with it. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193124 http://bugzilla.opensuse.org/show_bug.cgi?id=1193124#c17 --- Comment #17 from Harri Miettinen <harmie@opensuse.fi> --- I tried remove the module and reload it but it didn't help. Tried with both 5.15.3 and 5.15.5 kernels. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193124 http://bugzilla.opensuse.org/show_bug.cgi?id=1193124#c18 --- Comment #18 from Takashi Iwai <tiwai@suse.com> --- OK, and I suppose you get the errors again like: Bluetooth: hci0: Reading Intel version command failed (-110) Bluetooth: hci0: command 0xfc05 tx timeout at reloading the module, right? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193124 http://bugzilla.opensuse.org/show_bug.cgi?id=1193124#c19 --- Comment #19 from Harri Miettinen <harmie@opensuse.fi> --- Yep. [ 1457.216079] Bluetooth: hci0: Reading Intel version command failed (-110) [ 1457.216079] Bluetooth: hci0: command 0xfc05 tx timeout -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193124 http://bugzilla.opensuse.org/show_bug.cgi?id=1193124#c20 --- Comment #20 from Takashi Iwai <tiwai@suse.com> --- Then it's likely a regression due to the code change in btintel stuff. Could you try the latest 5.16-rc kernel in OBS Kernel:HEAD repo to see whether the problem persists? If yes, this should be reported to the upstream. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193124 http://bugzilla.opensuse.org/show_bug.cgi?id=1193124#c21 --- Comment #21 from Harri Miettinen <harmie@opensuse.fi> --- with 5.16.0-rc3-1.ge8ae228-default I don't see timeout in dmesg when removing and loading btusb but bluetooth is still not working. [ 216.658659] usbcore: registered new interface driver btusb [ 216.674464] pcieport 0000:00:1c.5: AER: Corrected error received: 0000:00:1c.5 [ 216.674473] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) [ 216.674475] pcieport 0000:00:1c.5: device [8086:a115] error status/mask=00000001/00002000 [ 216.674477] pcieport 0000:00:1c.5: [ 0] RxErr (First) [ 216.871178] pcieport 0000:00:1c.5: AER: Corrected error received: 0000:00:1c.5 [ 216.871195] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) [ 216.871200] pcieport 0000:00:1c.5: device [8086:a115] error status/mask=00000001/00002000 [ 216.871206] pcieport 0000:00:1c.5: [ 0] RxErr (First) [ 217.288866] pcieport 0000:00:1c.5: AER: Corrected error received: 0000:00:1c.5 [ 217.288889] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) [ 217.288897] pcieport 0000:00:1c.5: device [8086:a115] error status/mask=00000001/00002000 [ 217.288905] pcieport 0000:00:1c.5: [ 0] RxErr (First) [ 217.493725] pcieport 0000:00:1c.5: AER: Corrected error received: 0000:00:1c.5 [ 217.493741] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) [ 217.493746] pcieport 0000:00:1c.5: device [8086:a115] error status/mask=00000001/00002000 [ 217.493752] pcieport 0000:00:1c.5: [ 0] RxErr (First) [ 217.596078] pcieport 0000:00:1c.5: AER: Corrected error received: 0000:00:1c.5 [ 217.596094] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) [ 217.596099] pcieport 0000:00:1c.5: device [8086:a115] error status/mask=00000001/00002000 [ 217.596106] pcieport 0000:00:1c.5: [ 0] RxErr (First) [ 217.698472] pcieport 0000:00:1c.5: AER: Corrected error received: 0000:00:1c.5 [ 217.698487] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) [ 217.698492] pcieport 0000:00:1c.5: device [8086:a115] error status/mask=00000001/00002000 [ 217.698499] pcieport 0000:00:1c.5: [ 0] RxErr (First) [ 218.108108] pcieport 0000:00:1c.5: AER: Corrected error received: 0000:00:1c.5 [ 218.108125] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) [ 218.108130] pcieport 0000:00:1c.5: device [8086:a115] error status/mask=00000001/00002000 [ 218.108136] pcieport 0000:00:1c.5: [ 0] RxErr (First) [ 218.210488] pcieport 0000:00:1c.5: AER: Corrected error received: 0000:00:1c.5 [ 218.210504] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) [ 218.210509] pcieport 0000:00:1c.5: device [8086:a115] error status/mask=00000001/00002000 [ 218.210515] pcieport 0000:00:1c.5: [ 0] RxErr (First) [ 218.290125] pcieport 0000:00:1c.5: AER: Corrected error received: 0000:00:1c.5 [ 218.290141] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) [ 218.290146] pcieport 0000:00:1c.5: device [8086:a115] error status/mask=00000001/00002000 [ 218.290152] pcieport 0000:00:1c.5: [ 0] RxErr (First) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193124 http://bugzilla.opensuse.org/show_bug.cgi?id=1193124#c22 --- Comment #22 from Harri Miettinen <harmie@opensuse.fi> --- but I can see in journalctl Nov 29 18:15:35 lenovo kernel: Bluetooth: hci0: Reading Intel version command failed (-110) Nov 29 18:15:35 lenovo kernel: Bluetooth: hci0: command 0xfc05 tx timeout -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193124 http://bugzilla.opensuse.org/show_bug.cgi?id=1193124#c23 --- Comment #23 from Takashi Iwai <tiwai@suse.com> --- Thanks. Care to report it to the upstream bug tracker, e.g. bugzilla.kernel.org? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193124 http://bugzilla.opensuse.org/show_bug.cgi?id=1193124#c24 --- Comment #24 from Harri Miettinen <harmie@opensuse.fi> --- Sure. I have created a new bug https://bugzilla.kernel.org/show_bug.cgi?id=215167 I hope George Olson have same issue because I kind of "stole" his ticket. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193124 http://bugzilla.opensuse.org/show_bug.cgi?id=1193124#c25 --- Comment #25 from George Olson <tech@reachthetribes.org> --- No problem, I was on holiday, so I am back now. Here are my files: -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193124 http://bugzilla.opensuse.org/show_bug.cgi?id=1193124#c26 --- Comment #26 from George Olson <tech@reachthetribes.org> --- Created attachment 854153 --> http://bugzilla.opensuse.org/attachment.cgi?id=854153&action=edit dmesg with 5.14 kernel bluetooth works -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193124 http://bugzilla.opensuse.org/show_bug.cgi?id=1193124#c27 --- Comment #27 from George Olson <tech@reachthetribes.org> --- Created attachment 854154 --> http://bugzilla.opensuse.org/attachment.cgi?id=854154&action=edit dmesg with kernel 5.15 bluetooth fails -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193124 http://bugzilla.opensuse.org/show_bug.cgi?id=1193124#c28 --- Comment #28 from George Olson <tech@reachthetribes.org> --- Created attachment 854155 --> http://bugzilla.opensuse.org/attachment.cgi?id=854155&action=edit hwinfo kernel 5.14 bluetooth works -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193124 http://bugzilla.opensuse.org/show_bug.cgi?id=1193124#c29 --- Comment #29 from George Olson <tech@reachthetribes.org> --- Created attachment 854156 --> http://bugzilla.opensuse.org/attachment.cgi?id=854156&action=edit hwinfo kernel 5.15 bluetooth fails -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193124 http://bugzilla.opensuse.org/show_bug.cgi?id=1193124#c31 --- Comment #31 from Harri Miettinen <harmie@opensuse.fi> --- yes it works. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193124 http://bugzilla.opensuse.org/show_bug.cgi?id=1193124#c32 --- Comment #32 from Takashi Iwai <tiwai@suse.com> --- OK, now the step is to find the culprit commit. I prepared KMPs to test easily. In the same URL in comment 30, you can find btusb-1-kmp-default, btusb-2-kmp-default, ..., btusb-11-kmp-default packages. Start with btusb-1, just install the package via zypper, e.g. zypper install btusb-1-kmp-default This will override btusb and btintel modules. Boot with the same test kernel again, and check whether the problem shows up again. Once after test, uninstall the package zypper rm btusb-1-kmp-default and go for the next one, install btusb-2-kmp-default. Repeat the steps until you hit the problem again. From that KMP and later ones should keep showing the problem. In this way, please identify which KMP started causing the problem. Once after testing, uninstall the KMP. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193124 http://bugzilla.opensuse.org/show_bug.cgi?id=1193124#c33 --- Comment #33 from Harri Miettinen <harmie@opensuse.fi> --- it works with btusb-1-kmp-default but fails with btusb-2-kmp-default -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193124 http://bugzilla.opensuse.org/show_bug.cgi?id=1193124#c34 --- Comment #34 from Takashi Iwai <tiwai@suse.com> --- OK, thanks. Now I'm building one more KMP (btusb-12-kmp-default) with a potential fix patch. Could you give it a try? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193124 http://bugzilla.opensuse.org/show_bug.cgi?id=1193124#c35 --- Comment #35 from George Olson <tech@reachthetribes.org> --- not sure if it is my zypper, but when I went to install the kernel from your OBS repo, zypper automatically installed all 12 of the btusb-x-kmp-default packages. Not sure how to tell zypper to only install one of them, but when it is done I will try removing all of them except number 12. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193124 http://bugzilla.opensuse.org/show_bug.cgi?id=1193124#c36 --- Comment #36 from George Olson <tech@reachthetribes.org> --- After installing the kernel from the OBS and deleting all the btusb-x-kmp files except number 12, I rebooted, and I got an error and could not boot using that kernel. I attached the image of the reboot. Not sure why zypper and dracut failed to set up my system the right way, but I can't boot with that kernel as of now, so I cannot test the patches. The command I used to install the kernel was zypper in kernel-default-5.15.5-1.1.g5892887 It automatically selected all 12 of the btusb-x-kmp patches to install as dependencies. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193124 http://bugzilla.opensuse.org/show_bug.cgi?id=1193124#c37 --- Comment #37 from George Olson <tech@reachthetribes.org> --- Created attachment 854230 --> http://bugzilla.opensuse.org/attachment.cgi?id=854230&action=edit screen image of failure to boot into test kernel -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193124 http://bugzilla.opensuse.org/show_bug.cgi?id=1193124#c38 --- Comment #38 from Takashi Iwai <tiwai@suse.com> --- Did you disable Secure Boot in your BIOS? The test kernel won't boot when it's enabled. Also, when testing a new kernel, don't add the repository to zypper. Instead, just download kernel-default-5.15.*.rpm from the URL, and install it via zypper directly like zypper install kernel-default-5.15.*.rpm Sometimes you need --oldpackage option when installing, as the release number might get reset. Ditto for KMPs. Download each rpm file, and install / uninstall each one manually. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193124 http://bugzilla.opensuse.org/show_bug.cgi?id=1193124#c39 --- Comment #39 from Takashi Iwai <tiwai@suse.com> --- ... and if *-12 KMP works, the test kernel with the patch is found in OBS home:tiwai:bsc1193124-2 repo, too http://download.opensuse.org/repositories/home:/tiwai:/bsc1193124-2/standard... It's the latest stable kernel with the fixed patch, no KMP needed. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193124 http://bugzilla.opensuse.org/show_bug.cgi?id=1193124#c40 --- Comment #40 from Harri Miettinen <harmie@opensuse.fi> --- Happy days, both btusb-12-kmp-default and 5.15.6-1.g3560890-default seems to work. Thank you for troubleshooting and solving the issue -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193124 http://bugzilla.opensuse.org/show_bug.cgi?id=1193124#c43 --- Comment #43 from Harri Miettinen <harmie@opensuse.fi> --- (In reply to George Olson from comment #35)
not sure if it is my zypper, but when I went to install the kernel from your OBS repo, zypper automatically installed all 12 of the btusb-x-kmp-default packages. Not sure how to tell zypper to only install one of them, but when it is done I will try removing all of them except number 12.
For me it worked when I installed one by one and removed the previously installed before installing new. for example zypper in btusb-1-kmp-default zypper rm btusb-1-kmp-default -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193124 http://bugzilla.opensuse.org/show_bug.cgi?id=1193124#c44 --- Comment #44 from George Olson <tech@reachthetribes.org> --- So I disabled secure boot, removed the test repo, uninstalled the test kernel, and the btusb-x-kmp files. Then I downloaded the test kernel and the btusb-12-kmp patch, and used zypper to install them directly. But I still can't boot into the test kernel. It gives the exact same error as what I posted above - it says I have to load the kernel first and I have a bad "shim" signature. Not sure what that means. Not sure how to get the test kernel to load so that I can test this system. Should I try to run a grub update again? or mkinitrd? I would have thought that dracut would have managed all of those as necessary, because it did put the test kernel in my grub file so that I see it as the first choice on boot. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193124 http://bugzilla.opensuse.org/show_bug.cgi?id=1193124#c45 --- Comment #45 from George Olson <tech@reachthetribes.org> --- Sorry... just figured out that the problem is my secure boot... I can't remember how I got my system to boot without secure boot enabled in the past... I will see if I can figure it out, but if I can't, I will just have to wait for the next update when the patch is applied to the new kernel. When should we expect the patch to be applied to the next tumbleweed update? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193124 http://bugzilla.opensuse.org/show_bug.cgi?id=1193124#c46 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo? --- Comment #46 from Takashi Iwai <tiwai@suse.com> --- It'll take some time until it reaches to the Tumbleweed snapshot release. It'd be great if you can manage to turn off Secure Boot, beforehand... In anyway, the upstream devs asked whether you guys can get a bit more information like below: - Blacklist btusb driver: Create a file /etc/modprobe.d/60-btusb.conf containing the following line: blacklist btusb - Boot with the TW 5.15.x kernel that shows the problem. - Confirm that btusb isn't loaded lsmod | grep btusb - Run btmon program as root btmon > btmon.out - Load btusb module modprobe btusb - Stop btmon program by ctrl-C, keep the log file - Reboot to the patched (working) kernel, and repeat the same procedure. Save the log file to another name. And attach both btmon log files to Bugzilla. Once after testing, remove the blacklist file /etc/modprobe.d/60-btusb.conf again. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193124 http://bugzilla.opensuse.org/show_bug.cgi?id=1193124#c47 --- Comment #47 from Harri Miettinen <harmie@opensuse.fi> --- I have uploaded the files to upstream ticket -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193124 http://bugzilla.opensuse.org/show_bug.cgi?id=1193124#c48 --- Comment #48 from George Olson <tech@reachthetribes.org> --- Ok, sorry for the delay, I did figure out how to disable secure boot. My UEFI page has 2 places in which secure boot is designated, and it is a bit confusing, but I got it to work. Now, as to the patches, where I am starting, I am so far getting different results than Harri. The first thing to note is that patch number 12 fails for me. I will post the results here when I finish testing them all. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193124 http://bugzilla.opensuse.org/show_bug.cgi?id=1193124#c49 --- Comment #49 from George Olson <tech@reachthetribes.org> --- Ok, I have installed each of the patches one by one. Here are the results. Patches 1-11 all result in bluetooth working for me. Patch 12 results in a bluetooth failure. So I can run the btmon program, but when I run the working kernel, which patch do you want me to use? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193124 http://bugzilla.opensuse.org/show_bug.cgi?id=1193124#c50 --- Comment #50 from George Olson <tech@reachthetribes.org> --- And I just tested the new kernel-5.15.6-1.1.g3560890 with the patch built in, no kmp file. Also it fails, not bluetooth. I will upload the journalctl, dmesg, and hwinfo files for the failed install with this updated kernel, and for the working kernel with the kmp patch. I will just use the first patch. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193124 http://bugzilla.opensuse.org/show_bug.cgi?id=1193124#c51 --- Comment #51 from George Olson <tech@reachthetribes.org> --- Created attachment 854323 --> http://bugzilla.opensuse.org/attachment.cgi?id=854323&action=edit dmesg with kmp1 patch working -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193124 http://bugzilla.opensuse.org/show_bug.cgi?id=1193124#c52 --- Comment #52 from George Olson <tech@reachthetribes.org> --- Created attachment 854324 --> http://bugzilla.opensuse.org/attachment.cgi?id=854324&action=edit journalctl with kmp1 patch working -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193124 http://bugzilla.opensuse.org/show_bug.cgi?id=1193124#c53 --- Comment #53 from George Olson <tech@reachthetribes.org> --- Created attachment 854325 --> http://bugzilla.opensuse.org/attachment.cgi?id=854325&action=edit lsmod with kmp1 patch working -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193124 http://bugzilla.opensuse.org/show_bug.cgi?id=1193124#c54 --- Comment #54 from George Olson <tech@reachthetribes.org> --- Created attachment 854326 --> http://bugzilla.opensuse.org/attachment.cgi?id=854326&action=edit dmesg with 5.15.6 patched kernel FAIL -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193124 http://bugzilla.opensuse.org/show_bug.cgi?id=1193124#c55 --- Comment #55 from George Olson <tech@reachthetribes.org> --- Created attachment 854327 --> http://bugzilla.opensuse.org/attachment.cgi?id=854327&action=edit journalctl with 5.15.6 patched kernel FAIL -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193124 http://bugzilla.opensuse.org/show_bug.cgi?id=1193124#c56 --- Comment #56 from George Olson <tech@reachthetribes.org> --- Created attachment 854328 --> http://bugzilla.opensuse.org/attachment.cgi?id=854328&action=edit lsmod with kernel 5.15.6 patched FAIL -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193124 http://bugzilla.opensuse.org/show_bug.cgi?id=1193124#c57 --- Comment #57 from Takashi Iwai <tiwai@suse.com> --- First of all, please give the full dmesg, not only a part. (In reply to George Olson from comment #49)
Ok, I have installed each of the patches one by one. Here are the results.
Patches 1-11 all result in bluetooth working for me. Patch 12 results in a bluetooth failure.
Do you mean that you installed the kernel in comment 30 http://download.opensuse.org/repositories/home:/tiwai:/bsc1193124/standard/x... and tested btusb-*-kmp-default one by one with that kernel? Has the kernel worked ever without KMP at first? And, you mentioned that it worked with btusb-11-kmp: it's something wrong. With btusb-11-kmp, it's the same code as the genuine TW 5.15.x kernel. IOW, if btusb-11-kmp works, 5.15.x TW kernel should work as-is. Please confirm this again. Looking back at the old logs, I'm afraid that your problem is different from Harri's, any my patch won't cover it. Maybe I'll need to drop the workaround added there for your device again... For further debugging, please get the btmon logs as described, *but* until you hit the actual BT problem (i.e. after connecting to the device, etc). At best, try to get the logs from the good-working TW 5.14.x kernel (found in TW history repo) and the broken 5.15.x kernel. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193124 http://bugzilla.opensuse.org/show_bug.cgi?id=1193124#c58 Mischa Salle <mischa.salle@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mischa.salle@gmail.com --- Comment #58 from Mischa Salle <mischa.salle@gmail.com> --- (In reply to Takashi Iwai from comment #57) [...]
(In reply to George Olson from comment #49) [...] Looking back at the old logs, I'm afraid that your problem is different from Harri's, any my patch won't cover it. Maybe I'll need to drop the workaround added there for your device again...
FYI I ran into the same problem as George Olson, using Kernel:stable:Backport on LEAP 15.3: bluetoothctl no longer shows any controller and I see the following line appear in dmesg/journalctl, i.e. same -56 as George Olson has: kernel: Bluetooth: hci0: sending initial HCI reset failed (-56) It's broken from 5.15.6-lp153.3.gdc51f96-default onwards, while 5.15.6-lp153.2.gc2ce213-default was still ok. I take it that's when you added * Thu Dec 2 2021 tiwai@suse.de - Bluetooth: Apply initial command workaround for more Intel chips (bsc#83f2dafe2a62). - commit dc51f96 For reference I have a Fujitsu Lifebook U7511 with an Intel bluetooth 8087:0026 which indeed would have changed looking at https://lore.kernel.org/all/20211202162256.31837-1-tiwai@suse.de/ That would mean Bluetooth-Apply-initial-command-workaround-for-more-.patch would be the problem. Is that the last/12th one that George Olson metioned? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193124 http://bugzilla.opensuse.org/show_bug.cgi?id=1193124#c59 --- Comment #59 from Takashi Iwai <tiwai@suse.com> --- Yes, it seems that 8087:0026 was a false-positive, and should be dropped again. I updated the patch and submitted to stable branch. For now, only 8087:0a2a needs the workaround. In the upstream bugzilla entry, other people mentioned about 8087:0aa7, this might need the same workaround. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193124 http://bugzilla.opensuse.org/show_bug.cgi?id=1193124#c60 --- Comment #60 from Mischa Salle <mischa.salle@gmail.com> --- (In reply to Takashi Iwai from comment #59)
Yes, it seems that 8087:0026 was a false-positive, and should be dropped again.
I updated the patch and submitted to stable branch. For now, only 8087:0a2a needs the workaround.
In the upstream bugzilla entry, other people mentioned about 8087:0aa7, this might need the same workaround.
sorry for my ignorance, but where can I track the progress of the patch? https://build.opensuse.org/package/show/Kernel:stable/kernel-source doesn't seem updated yet? (and therefore neither is Kernel:stable:Backport/kernel-default). -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193124 http://bugzilla.opensuse.org/show_bug.cgi?id=1193124#c61 --- Comment #61 from Takashi Iwai <tiwai@suse.com> --- The published package hasn't been updated yet. The pull-request was merged today, so it'll appear in tomorrow's build of Kernel:stable and co. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193124 http://bugzilla.opensuse.org/show_bug.cgi?id=1193124#c64 --- Comment #64 from George Olson <tech@reachthetribes.org> --- Thank you for your work on this. I just downloaded kernel 5.10 from the kernel-stable repository, and using that, I am able to use bluetooth again. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193124 Peter Stolz <stolz@rfgs.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |stolz@rfgs.de -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193124 http://bugzilla.opensuse.org/show_bug.cgi?id=1193124#c65 Lee Matheson <lee_matheson@hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lee_matheson@hotmail.com --- Comment #65 from Lee Matheson <lee_matheson@hotmail.com> --- Thank you also. I have been tracking this bug report as an update for me from the 5.14.11 kernel to the 5.15.7 kernel also resulted in bluetooth no longer working with my bluetooth mouse nor my BoseSoundsport bluetooth speakers (this is on a LEAP-15.3 with the stable:backport:kernel ) on a Lenovo X1 Carbon gen-9 laptop. Updating to the 5.15.10 kernel and bluetooth is once again working properly with this laptop. The efforts made are very much appreciated. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193124 H <leodream2008@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |leodream2008@gmail.com -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com