June 2023 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1211763] New: kernel 6.3.2-1-default AX201 Bluetooth regression: Opcode errors in dmesg
by bugzilla_noreply＠suse.com 05 Jun '23

05 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1211763 Bug ID: 1211763 Summary: kernel 6.3.2-1-default AX201 Bluetooth regression: Opcode errors in dmesg 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(a)opensuse.org Reporter: draeath(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- My bluetooth hardware stopped working with kernel 6.3.2-1. Booting to the previously installed kernel, 6.3.1-2 (yes, not a transposition) allows it to work. The firmware file has not changed (I can't find the DDC file to check, I think it may be embedded in the SFI file) Shortly after loading firmware, the following kernel messages are printed and the bluetooth device fails to function: May 26 19:52:29 muspelheimr kernel: Bluetooth: hci0: Device revision is 2 May 26 19:52:29 muspelheimr kernel: Bluetooth: hci0: Secure boot is enabled May 26 19:52:29 muspelheimr kernel: Bluetooth: hci0: OTP lock is enabled May 26 19:52:29 muspelheimr kernel: Bluetooth: hci0: API lock is enabled May 26 19:52:29 muspelheimr kernel: Bluetooth: hci0: Debug lock is disabled May 26 19:52:29 muspelheimr kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014 May 26 19:52:29 muspelheimr kernel: Bluetooth: hci0: Bootloader timestamp 2019.40 buildtype 1 build 38 May 26 19:52:29 muspelheimr kernel: Bluetooth: hci0: Found device firmware: intel/ibt-0040-4150.sfi May 26 19:52:29 muspelheimr kernel: Bluetooth: hci0: Boot Address: 0x100800 May 26 19:52:29 muspelheimr kernel: Bluetooth: hci0: Firmware Version: 98-13.23 May 26 19:52:31 muspelheimr kernel: Bluetooth: hci0: Waiting for firmware download to complete May 26 19:52:31 muspelheimr kernel: Bluetooth: hci0: Firmware loaded in 1485331 usecs May 26 19:52:31 muspelheimr kernel: Bluetooth: hci0: Waiting for device to boot May 26 19:52:31 muspelheimr kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02 May 26 19:52:31 muspelheimr kernel: Bluetooth: hci0: Device booted in 15774 usecs May 26 19:52:31 muspelheimr kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-0040-4150.ddc May 26 19:52:31 muspelheimr kernel: Bluetooth: hci0: Applying Intel DDC parameters completed May 26 19:52:31 muspelheimr kernel: Bluetooth: hci0: Firmware timestamp 2023.13 buildtype 1 build 62562 May 26 19:52:34 muspelheimr kernel: Bluetooth: hci0: Opcode 0x204b failed: -56 May 26 19:53:10 muspelheimr kernel: Bluetooth: hci0: Opcode 0x c03 failed: -110 May 26 19:53:11 muspelheimr kernel: Bluetooth: hci0: urb 00000000194e86ae failed to resubmit (113) May 26 19:53:12 muspelheimr kernel: Bluetooth: hci0: Failed to read MSFT supported features (-110) May 26 19:53:51 muspelheimr kernel: Bluetooth: hci0: Opcode 0x c03 failed: -110 May 26 19:53:51 muspelheimr kernel: Bluetooth: hci0: MSFT extension not registered May 26 19:54:04 muspelheimr kernel: Bluetooth: hci0: Opcode 0x c03 failed: -110 May 26 19:54:04 muspelheimr kernel: Bluetooth: hci0: MSFT extension not registered May 26 19:55:26 muspelheimr kernel: Bluetooth: hci0: Opcode 0x c03 failed: -110 May 26 19:55:26 muspelheimr kernel: Bluetooth: hci0: MSFT extension not registered May 26 19:55:40 muspelheimr kernel: Bluetooth: hci0: Opcode 0x c03 failed: -110 May 26 19:55:40 muspelheimr kernel: Bluetooth: hci0: MSFT extension not registered (repeated sequence of the "Opcode 0x c03 failed" and the MSFT extension report is due to my attempting to turn the device off/on etc). Normal logs (when it works correctly) look like this: May 13 22:02:07 muspelheimr kernel: Bluetooth: hci0: Device revision is 2 May 13 22:02:07 muspelheimr kernel: Bluetooth: hci0: Secure boot is enabled May 13 22:02:07 muspelheimr kernel: Bluetooth: hci0: OTP lock is enabled May 13 22:02:07 muspelheimr kernel: Bluetooth: hci0: API lock is enabled May 13 22:02:07 muspelheimr kernel: Bluetooth: hci0: Debug lock is disabled May 13 22:02:07 muspelheimr kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014 May 13 22:02:07 muspelheimr kernel: Bluetooth: hci0: Bootloader timestamp 2019.40 buildtype 1 build 38 May 13 22:02:07 muspelheimr kernel: Bluetooth: hci0: Found device firmware: intel/ibt-0040-4150.sfi May 13 22:02:07 muspelheimr kernel: Bluetooth: hci0: Boot Address: 0x100800 May 13 22:02:07 muspelheimr kernel: Bluetooth: hci0: Firmware Version: 98-13.23 May 13 22:02:08 muspelheimr kernel: Bluetooth: hci0: Waiting for firmware download to complete May 13 22:02:08 muspelheimr kernel: Bluetooth: hci0: Firmware loaded in 1487927 usecs May 13 22:02:08 muspelheimr kernel: Bluetooth: hci0: Waiting for device to boot May 13 22:02:08 muspelheimr kernel: Bluetooth: hci0: Device booted in 15698 usecs May 13 22:02:08 muspelheimr kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02 May 13 22:02:08 muspelheimr kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-0040-4150.ddc May 13 22:02:08 muspelheimr kernel: Bluetooth: hci0: Applying Intel DDC parameters completed May 13 22:02:08 muspelheimr kernel: Bluetooth: hci0: Firmware timestamp 2023.13 buildtype 1 build 62562 USB device IDs: idVendor 0x8087 Intel Corp. idProduct 0x0026 AX201 Bluetooth Note that the MSFT error is normal and (seems to be) harmless. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1211975] freeze with flip_done time out when external monitor attached
by bugzilla_noreply＠suse.com 05 Jun '23

05 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1211975 https://bugzilla.suse.com/show_bug.cgi?id=1211975#c3 --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- Just download kernel-default.rpm from the history repo. e.g. the oldest one found right now is: http://download.opensuse.org/history/20230514/tumbleweed/repo/oss/x86_64/ke… Then install it manually via zypper install --oldpackage option. % zypper in --oldpackage kernel-default-6.3.1-1.1.x86_64.rpm And boot with it (select the kernel at GRUB menu). After testing, you can uninstall the kernel again. % zypper rm kernel-default-6.3.1-1.1 But, before testing multiple kernels, I'd recommend you to modify /etc/zypp/zypp.conf at first. Change the line setting "multiversion.kernels" to add more entries, e.g. multiversion.kernels = latest,latest-1,latest-2,latest-3,running This will allow up to 4 kernels installed on the system simultaneously. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1212019] Thunderbolt USB audio disconnecting with Kernel 6.3.4
by bugzilla_noreply＠suse.com 05 Jun '23

05 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1212019 https://bugzilla.suse.com/show_bug.cgi?id=1212019#c2 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(pujos.michael@gma | |il.com) CC| |pujos.michael(a)gmail.com --- Comment #2 from Takashi Iwai <tiwai(a)suse.com> --- Also, I'm building a test kernel with the backport of the thunderbolt fix patch in the upstream subsystem tree. It's being built in OBS home:tiwai:bsc1212019 repo. Once after the build finishes (it takes an hour or so), could you check whether it works better? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1212019] Thunderbolt USB audio disconnecting with Kernel 6.3.4
by bugzilla_noreply＠suse.com 05 Jun '23

05 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1212019 https://bugzilla.suse.com/show_bug.cgi?id=1212019#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- So when you boot with 6.3.3 kernel on the same system now, the problem doesn't happen? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1211975] freeze with flip_done time out when external monitor attached
by bugzilla_noreply＠suse.com 05 Jun '23

05 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1211975 https://bugzilla.suse.com/show_bug.cgi?id=1211975#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mattm3a(a)yahoo.com, | |tiwai(a)suse.com Flags| |needinfo?(mattm3a(a)yahoo.com | |) --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Could you try the older kernels found in TW history repo and verify which one works and which not? http://download.opensuse.org/history/ -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1211763] kernel 6.3.2-1-default AX201 Bluetooth regression: Opcode errors in dmesg
by bugzilla_noreply＠suse.com 05 Jun '23

05 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1211763 https://bugzilla.suse.com/show_bug.cgi?id=1211763#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Hm, at least through a quick glance, there is no relevant change between 6.3.1 and 6.3.2 kernels about BT itself. The only change is the upstream commit d8d7ce037d9a8f1f0714ece268c4c2c50845bbc3 Revert "Bluetooth: btsdio: fix use after free bug in btsdio_remove due to un finished work" which is likely irrelevant. Please check with the latest kernel in OBS Kernel:stable repo to be sure. If the problem persists, we need to report to the upstream. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1211410] Weird "vmalloc error" kernel stack trace when lsof is executed
by bugzilla_noreply＠suse.com 05 Jun '23

05 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1211410 https://bugzilla.suse.com/show_bug.cgi?id=1211410#c4 --- Comment #4 from Vlastimil Babka <vbabka(a)suse.com> --- I've reported it upstream and a vmalloc guy should have a fix soon. The warning is spurious as there's a fallback to the failing order-9 allocation, so it's going to be suppressed. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1199848] kernel crash on e.g. usb stick attach to qemu-kvm or un-plugging usb stick generally / error_code(0x0000) - not-present page
by bugzilla_noreply＠suse.com 04 Jun '23

04 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1199848 https://bugzilla.suse.com/show_bug.cgi?id=1199848#c8 --- Comment #8 from Alexander Krupp <obs(a)akr.yagii.de> --- The issue did not occur anymore. I am running on 5.14.21-150400.24.63-default #1 SMP PREEMPT_DYNAMIC Tue May 2 15:49:04 UTC 2023 , currently. From my point of view, the issue has been resolved. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1211069] New: Bugged RMRR prevents PCIe Passthrough of KVM VMs on certain platforms
by bugzilla_noreply＠suse.com 02 Jun '23

02 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1211069 Bug ID: 1211069 Summary: Bugged RMRR prevents PCIe Passthrough of KVM VMs on certain platforms Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: bugtracker(a)fischbytes.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/112.0.0.0 Safari/537.36 Build Identifier: Certain vendors that are under the assumption that standards are for jerks and Intel's specifications are a loose optional guideline have implemented RMRR in such a way that every PCI device is marked as reserved and therefore cannot be passed through to a virtual machine. This issue has been very well documented by some people that have a lot more experience than I do at the below linked resource. I was hoping that SUSE could implement the Relaxed RMRR option as an optional kernel parameter to use on these bugged platforms as that would re-enable or rather enable a lot of broken servers for the first time ever to use PCIe Passthrough. I can verify the issue exists on a HPE DL360e Gen8 with trying to passthrough a GPU to a KVM/QEMU machine. https://github.com/Aterfax/relax-intel-rmrr Reproducible: Always Steps to Reproduce: 1. Be on a bugged platform (e.g. HPE ProLiant DL360e Gen8 with latest BIOS and iLO) 2. Install the latest release of openSUSE Leap 15.4 3. Install the KVM/QEMU/Libvirt stack and passthrough a GPU to a virtual machine 4. See how the process fails with an error of "Device is ineligible for IOMMU domain attach due to platform RMRR requirement. Contact your platform vendor." I followed the installation instructions: https://doc.opensuse.org/documentation/leap/virtualization/html/book-virtua… The issue is at a kernel-level however which means it also will not work on other platforms. Tested are Vanilla Proxmox and TrueNAS Scale. The patched Proxmox with relaxed-RMRR works(!) Actual Results: Dmesg: Device is ineligible for IOMMU domain attach due to platform RMRR requirement. Contact your platform vendor. QEMU: vfio: failed to set iommu for container: Operation not permitted Expected Results: Boot the VM with GPU Passthrough enabled. -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1211459] [Leap 15.4][btrfs][snapper-cleanup], 'systemctl start snapper-cleanup' causes infinite message 'BTRFS warning (device vda2): qgroup rescan is already in progress' in syslog and causes 'yast2 lan' command hang
by bugzilla_noreply＠suse.com 02 Jun '23

02 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1211459 https://bugzilla.suse.com/show_bug.cgi?id=1211459#c21 --- Comment #21 from Arvin Schnell <aschnell(a)suse.com> --- David wanted to look at the problem. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.

1 0