October 2023 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1215650] Assigning USB devices to guest system fails with kernel 5.14.21-150500.55.22.1
by bugzilla_noreply＠suse.com 02 Oct '23

02 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215650 https://bugzilla.suse.com/show_bug.cgi?id=1215650#c5 Ivan Ivanov <ivan.ivanov(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |DUPLICATE Status|NEW |RESOLVED --- Comment #5 from Ivan Ivanov <ivan.ivanov(a)suse.com> --- Thanks for confirmation, closing... *** This bug has been marked as a duplicate of bug 1215553 *** -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1215436] Unable to boot kernels 6.5.2 or 6.5.3 unless acpi=noirq specified
by bugzilla_noreply＠suse.com 02 Oct '23

02 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215436 https://bugzilla.suse.com/show_bug.cgi?id=1215436#c37 --- Comment #37 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Stuart Rogers from comment #36) > Checked again this evening and found kernel-default-6.5.5-8.4.x86_64.rpm > which I thought I'd try, still no go with blacklist removed sadly. OK, so it still fails, I enabled more reverts: 0018-Revert-firewire-cdev-code-refactoring-to-operate-eve.patch 0019-Revert-firewire-core-implement-variations-to-send-re.patch 0020-Revert-firewire-core-use-union-for-callback-of-trans.patch These remain to test after this step (if it still fails): #0021-Revert-firewire-cdev-implement-new-event-to-notify-r.patch #0022-Revert-firewire-cdev-add-new-event-to-notify-request.patch #0023-Revert-firewire-cdev-add-new-version-of-ABI-to-notif.patch #0024-Revert-firewire-add-KUnit-test-to-check-layout-of-UA.patch -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1215826] New: kernel-default-6.5.4 won't boot; can't activate swap
by bugzilla_noreply＠suse.com 01 Oct '23

01 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215826 Bug ID: 1215826 Summary: kernel-default-6.5.4 won't boot; can't activate swap Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: psychonaut(a)nothingisreal.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 869836 --> https://bugzilla.suse.com/attachment.cgi?id=869836&action=edit Output of hwinfo (with 6.4.12) I upgraded from Tumbleweed 20230908 to 20230921, which included an upgrade from kernel-default-6.4.12 to kernel-default-6.5.4. The new kernel has problems booting or resuming from suspend. In particular, when booting, about half the time the kernel is unable to activate the swap device. The last message printed to the console is "a start job is running for /dev/sda2" (the device in question being my swap partition) and a timer that counts up. I've let it run for as long as 10 hours but it never finishes. Resuming from suspend also doesn't work. In this case the computer simply locks up or powers off. (I haven't tested hibernate.) I had a similar problem (only with resuming from suspend, not with activating swap space) with kernel-default-5.19.1; not sure if this is related. See Bug 1202571. Downgrading to the 6.4.12 kernel works around the issue. I am attaching the output of hwinfo (using the 6.4.12 kernel). -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1215826] kernel-default-6.5.4 won't boot; can't activate swap
by bugzilla_noreply＠suse.com 01 Oct '23

01 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215826 https://bugzilla.suse.com/show_bug.cgi?id=1215826#c2 --- Comment #2 from Tristan Miller <psychonaut(a)nothingisreal.com> --- (In reply to Felix Miata from comment #1) > Something to try: Remove resume=/dev/sda2 from /etc/default/grub and > /boot/grub2/grub.cfg entirely, or replacing it with resume=UUID=<swapUUID> > or resume=LABEL=<swapLABEL> (using the actual UUID or LABEL from lsblk -f or > blkid). To test whether this is the right track, strike the E key at the > Grub menu and change resume=/dev/sda2 to noresume before proceeding with > boot. Noresume means what it spells, but it should boot straight away if I'm > right. Yes, using noresume or resume=UUID=<swapUUID> seems to solve the problem. I noticed when looking up the UUID of the swap device that it was always /dev/sdb2 when booting from the 6.4.12 kernel, whereas when booting from the 6.5.4 kernel it was sometimes /dev/sda2 and sometimes /dev/sdb2. So I think the real problem here is that the 6.5.4 kernel doesn't assign device names in the same consistent manner than 6.4.12 did, so you can't rely on these names in the bootloader. I think that nowadays a fresh install of Tumbleweed will always use the device's UUID, but my system was first installed back in 2014 and so was still using the old /dev/sdXY-style identifiers. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1215436] Unable to boot kernels 6.5.2 or 6.5.3 unless acpi=noirq specified
by bugzilla_noreply＠suse.com 01 Oct '23

01 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215436 https://bugzilla.suse.com/show_bug.cgi?id=1215436#c35 --- Comment #35 from Stuart Rogers <stuart(a)stella-maris.org.uk> --- My issue is that any kernel after 6.4.12 fails unless I blacklist firewire. Now at some point in kernel 6.5.x a fix was applied which stopped this working. So I need help to determine what the change was and what in that change was causing it to fail so completely that the system rebooted. If I can get some assistance to get that far and it turns out to be an issue with my hardware/BIOS I can take it up with MSI who make my motherboard. I stress that up to and including 6.4.12 I had no issues with it at all. I do not have the information or experience to move this further bisecting the kernel without some help from someone with the relevant knowledge of the fixes etc. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1215848] New: bluetooth does not pair with some devices: with the latest kernel-firmware-bluetooth
by bugzilla_noreply＠suse.com 01 Oct '23

01 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215848 Bug ID: 1215848 Summary: bluetooth does not pair with some devices: with the latest kernel-firmware-bluetooth 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: alinm.elena(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 869853 --> https://bugzilla.suse.com/attachment.cgi?id=869853&action=edit btmon log I have a bt keyboard (using a xiao ble nrf52840 controller). this worked fine on the current computer with tumbleweed till beginning of september(may be red herring). when i decided to remove the old bt profiles and repair all my devices.. headphones, mice and keyboard. headphones and mice work as expected no issues.. the only one is the keyboard that refuses to connect or pair. there is nothing wrong with the keyboard since I can pair it without issues on another xps laptop (different bt adapter) or my android phone. trying to debug but kind of hit a wall since I have little experience with bt errors. in logs i see [ 367.758074] Bluetooth: hci0: unexpected SMP command 0x0b from e8:77:fb:f9:41:5a the bt adapter is integrated in the wifi as far as I can say 00:14.3 Network controller [0280]: Intel Corporation Alder Lake-P PCH CNVi WiFi [8086:51f0] (rev 01) Subsystem: Intel Corporation Wi-Fi 6E AX211 160MHz [8086:4090] Kernel driver in use: iwlwifi the computer itself is an XPS 9320 I also attach a btmon log when I try to pair the keyboard. I see a timeout event. kernel is Linux abbaton 6.5.4-1-vanilla #1 SMP PREEMPT_DYNAMIC Wed Sep 20 05:07:04 UTC 2023 (fdd7e9e) x86_64 x86_64 x86_64 GNU/Linux but on default I get the same behaviour. attached also the full dmesg for record the working computer is XPS 13 9370 and the adapter 02:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e] (rev 32) Subsystem: Rivet Networks Killer 1435 Wireless-AC [1a56:143a] Kernel driver in use: ath10k_pci Kernel modules: ath10k_pci workaround: replace ibt-0040-0041.ddc ibt-0040-0041.sfi from kernel-firmware-bluetooth(both default tw and from kernel head)... from kernel-firmware-bluetooth-20230320-150500.1.1.noarch.rpm and seems to work without any issues. -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1215436] Unable to boot kernels 6.5.2 or 6.5.3 unless acpi=noirq specified
by bugzilla_noreply＠suse.com 01 Oct '23

01 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215436 https://bugzilla.suse.com/show_bug.cgi?id=1215436#c34 --- Comment #34 from Takashi Sakamoto <o-takashi(a)sakamocchi.jp> --- As long As I tested Linux FireWire stack in actual machine, it works well. https://lore.kernel.org/lkml/0ed4012a-83a7-4849-92c4-87a86e1bbb84@app.fastm… As supplements: -> journalctl -k kernel: smpboot: CPU0: AMD Ryzen 5 2400G with Radeon Vega Graphics (family: 0x17, model: 0x11, stepping: 0x0) ... kernel: DMI: Gigabyte Technology Co., Ltd. AX370-Gaming 5/AX370-Gaming 5, BIOS F51h 02/09/2023 -- You are receiving this mail because: You are the assignee for the bug.

1 0