September 2023 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1215760] New: steam deck usb stop working after waking up from sleep
by bugzilla_noreply＠suse.com 27 Sep '23

27 Sep '23

https://bugzilla.suse.com/show_bug.cgi?id=1215760 Bug ID: 1215760 Summary: steam deck usb stop working after waking up from sleep 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: monkeyboyted(a)yahoo.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 869790 --> https://bugzilla.suse.com/attachment.cgi?id=869790&action=edit dmesg > file.txt Step to reproduce. 1. Plugin in power cable 2. Let the device sleep 3. Wake up the device with the power button 4. The keyboard doesn't work Observation The deck seems to sleep with the screen on screen on. I might try to sleep with cli [23927.566139] xhci_hcd 0000:04:00.3: Error while assigning device slot ID: Command Aborted [23927.566160] xhci_hcd 0000:04:00.3: Max number of devices this xHCI host supports is 64. [23927.566171] usb usb1-port1: couldn't allocate usb_device [23927.644041] xhci_hcd 0000:04:00.3: WARN: xHC save state timeout [23927.644083] xhci_hcd 0000:04:00.3: PM: suspend_common(): xhci_pci_suspend+0x0/0x1d0 [xhci_pci] returns -110 [23927.644106] xhci_hcd 0000:04:00.3: can't suspend (hcd_pci_runtime_suspend [usbcore] returned -110) doof@steamdeck:~> The usb port works again after a power cycle Expectation The usb port works on wake up. Other notes: The screen is on while the system sleeps. I did have time to test it with other methods. -- You are receiving this mail because: You are the assignee for the bug.

1 8

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

27 Sep '23

https://bugzilla.suse.com/show_bug.cgi?id=1215436 https://bugzilla.suse.com/show_bug.cgi?id=1215436#c30 --- Comment #30 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Stuart Rogers from comment #29) > Tested kernel-default-6.5.5-7.1.x86_64.rpm this morning and it fails to boot > if I remove the blacklist. The command outputs are from a working kernel and > are added as attachments. Huh, that's sort of unexpected. So it is one of cdev patches, I reverted 6 more: 0012-Revert-firewire-fix-build-failure-due-to-missing-mod.patch 0013-Revert-firewire-cdev-implement-new-event-relevant-to.patch 0014-Revert-firewire-cdev-add-new-event-to-notify-phy-pac.patch 0015-Revert-firewire-cdev-code-refactoring-to-dispatch-ev.patch 0016-Revert-firewire-cdev-implement-new-event-to-notify-r.patch 0017-Revert-firewire-cdev-add-new-event-to-notify-respons.patch Could you test once built? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1215695] amdgpu ring gfx_low timeout
by bugzilla_noreply＠suse.com 27 Sep '23

27 Sep '23

https://bugzilla.suse.com/show_bug.cgi?id=1215695 https://bugzilla.suse.com/show_bug.cgi?id=1215695#c2 Daniel Garcia <daniel.garcia(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |daniel.garcia(a)suse.com --- Comment #2 from Daniel Garcia <daniel.garcia(a)suse.com> --- I've done some investigation about this bug and it looks like it's related to the kernel real-time schedule [3]. There's a patch sent to the kernel to try to solve this issue [1]. There's also some work done in mutter project to avoid the problem [2]. Current upstream proposed patches: * [1] kernel: https://patchwork.kernel.org/project/dri-devel/patch/20230926170549.2589045… * [2] mutter: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3293 Related reported bugs for other distributions: * [3] freedesktop: https://gitlab.freedesktop.org/drm/amd/-/issues/2861 * [4] ubuntu: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2034619 * [5] gnome: https://gitlab.gnome.org/GNOME/mutter/-/issues/3037 -- 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 27 Sep '23

27 Sep '23

https://bugzilla.suse.com/show_bug.cgi?id=1215436 https://bugzilla.suse.com/show_bug.cgi?id=1215436#c25 --- Comment #25 from Jiri Slaby <jslaby(a)suse.com> --- @Takashi san, thanks for jumping in. @Stuart: could you retest the kernel once it builds? Now, it contains only these reverts: 0001-Revert-firewire-net-fix-use-after-free-in-fwnet_fini.patch 0002-Revert-firewire-ohci-release-buffer-for-AR-req-resp-.patch 0003-Revert-firewire-ohci-use-devres-for-content-of-confi.patch 0004-Revert-firewire-ohci-use-devres-for-IT-IR-AT-receive.patch 0005-Revert-firewire-ohci-use-devres-for-list-of-isochron.patch 0006-Revert-firewire-ohci-use-devres-for-requested-IRQ.patch 0007-Revert-firewire-ohci-use-devres-for-misc-DMA-buffer.patch 0008-Revert-firewire-ohci-use-devres-for-MMIO-region-mapp.patch 0009-Revert-firewire-ohci-use-devres-for-PCI-related-reso.patch 0010-Revert-firewire-ohci-use-devres-for-memory-object-of.patch 0011-Revert-firewire-fix-warnings-to-generate-UAPI-docume.patch Also, can you upload here outputs of below commands from a working kernel? hwinfo lspci -vvnnxxx lspci -tv -- 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 26 Sep '23

26 Sep '23

https://bugzilla.suse.com/show_bug.cgi?id=1215436 https://bugzilla.suse.com/show_bug.cgi?id=1215436#c24 Takashi Sakamoto <o-takashi(a)sakamocchi.jp> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |o-takashi(a)sakamocchi.jp --- Comment #24 from Takashi Sakamoto <o-takashi(a)sakamocchi.jp> --- Hi, I'm current maintainer of Linux FireWire subsystem. I realized your issue by receiving a message from Jiri Slaby[1], and apologize your inconvenience. This morning I installed OpenSUSE tumbleweed into my virtual machine (x86_64) on host machine (AMD Ryzen 5 2400G/Gigabyte AX370-Gaming 5, BIOS F51h). 1394 OHCI hardware is bind to the virtual machine by vfio-pci in host OS (Ubuntu 23.04 amd64). As a result, I have no issue in the virtual machine. (In guest system) ~> cat /etc/os-release NAME="openSUSE Tumbleweed" # VERSION="20230922" ID="opensuse-tumbleweed" ID_LIKE="opensuse suse" VERSION_ID="20230922" PRETTY_NAME="openSUSE Tumbleweed" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:tumbleweed:20230922" BUG_REPORT_URL="https://bugzilla.opensuse.org" SUPPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org" DOCUMENTATION_URL="https://en.opensuse.org/Portal:Tumbleweed" LOGO="distributor-logo-Tumbleweed" ~> cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-6.5.4-1-default root=UUID=ca1f9882-855b-4588-955d-8adf468e4fbb splash=silent mitigations=auto quiet security=apparmor ~> uname -r 6.5.4-1-default ~> sudo lspci -vvvv 08:01.0 FireWire (IEEE 1394): Texas Instruments XIO2213A/B/XIO2221 IEEE-1394b OHCI Controller [Cheetah Express] (rev 01) (prog-if 10 [OHCI]) Subsystem: Device 3412:7856 Physical Slot: 1 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 32 (500ns min, 1000ns max), Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 23 Region 0: Memory at c1804000 (32-bit, non-prefetchable) [size=2K] Region 1: Memory at c1800000 (32-bit, non-prefetchable) [size=16K] Capabilities: [44] Power Management version 3 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Kernel driver in use: firewire_ohci Kernel modules: firewire_ohci ~> LC_ALL=C sudo -E journalctl -k | grep ohci Sep 27 08:11:06 localhost kernel: firewire_ohci 0000:08:01.0: added OHCI v1.10 device as card 0, 8 IR + 8 IT contexts, quirks 0x2 ~> udevadm info -e ... P: /devices/pci0000:00/0000:00:02.6/0000:07:00.0/0000:08:01.0 M: 0000:08:01.0 R: 0 U: pci V: firewire_ohci E: DEVPATH=/devices/pci0000:00/0000:00:02.6/0000:07:00.0/0000:08:01.0 E: SUBSYSTEM=pci E: DRIVER=firewire_ohci E: PCI_CLASS=C0010 E: PCI_ID=104C:823F E: PCI_SUBSYS_ID=3412:7856 E: PCI_SLOT_NAME=0000:08:01.0 E: MODALIAS=pci:v0000104Cd0000823Fsv00003412sd00007856bc0Csc00i10 E: USEC_INITIALIZED=4075041 E: ID_PCI_CLASS_FROM_DATABASE=Serial bus controller E: ID_PCI_SUBCLASS_FROM_DATABASE=FireWire (IEEE 1394) E: ID_PCI_INTERFACE_FROM_DATABASE=OHCI E: ID_VENDOR_FROM_DATABASE=Texas Instruments E: ID_MODEL_FROM_DATABASE=XIO2213A/B/XIO2221 IEEE-1394b OHCI Controller [Cheetah Express] E: ID_PATH=pci-0000:08:01.0 E: ID_PATH_TAG=pci-0000_08_01_0 P: /devices/pci0000:00/0000:00:02.6/0000:07:00.0/0000:08:01.0/fw0 M: fw0 R: 0 U: firewire D: c 243:0 N: fw0 L: 0 E: DEVPATH=/devices/pci0000:00/0000:00:02.6/0000:07:00.0/0000:08:01.0/fw0 E: SUBSYSTEM=firewire E: DEVNAME=/dev/fw0 E: MAJOR=243 E: MINOR=0 ... I think the issued 1394 OHCI hardware seems to bring the issue as I mentioned in reply to the message[2]. My hardware integrates PCIe-PCI bridge as well as PCI-1394-bus bridge (OHCI), like: (in host system) ~> sudo lspci -v ... 01:00.0 PCI bridge: Texas Instruments XIO2213A/B/XIO2221 PCI Express to PCI Bridge [Cheetah Express] (rev 01) (prog-if 00 [Normal decode]) Subsystem: Device 3412:7856 Flags: bus master, fast devsel, latency 0, IOMMU group 8 Memory at fce00000 (32-bit, non-prefetchable) [size=4K] Bus: primary=01, secondary=02, subordinate=02, sec-latency=32 I/O behind bridge: [disabled] [32-bit] Memory behind bridge: fcd00000-fcdfffff [size=1M] [32-bit] Prefetchable memory behind bridge: [disabled] [64-bit] Capabilities: [50] Power Management version 3 Capabilities: [60] MSI: Enable- Count=1/16 Maskable- 64bit+ Capabilities: [80] Subsystem: Device 3412:7856 Capabilities: [90] Express PCI-Express to PCI/PCI-X Bridge, MSI 00 Capabilities: [100] Advanced Error Reporting 02:00.0 FireWire (IEEE 1394): Texas Instruments XIO2213A/B/XIO2221 IEEE-1394b OHCI Controller [Cheetah Express] (rev 01) (prog-if 10 [OHCI]) Subsystem: Device 3412:7856 Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 119, IOMMU group 8 Memory at fcd04000 (32-bit, non-prefetchable) [size=2K] Memory at fcd00000 (32-bit, non-prefetchable) [size=16K] Capabilities: [44] Power Management version 3 Kernel driver in use: vfio-pci Kernel modules: firewire_ohci If the issued hardware has different design related to bus bridge, it seems to be a hint of the issue. If not, I'm going to investigate the issue without the virtual environment. [1] https://lore.kernel.org/lkml/ZRLFP3UAX288JgAK@krava/ [2] https://lore.kernel.org/lkml/20230926140922.GA6538@workstation.local/ Regards -- You are receiving this mail because: You are the assignee for the bug.

1 0

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

26 Sep '23

https://bugzilla.suse.com/show_bug.cgi?id=1215650 https://bugzilla.suse.com/show_bug.cgi?id=1215650#c3 Felix Miata <mrmazda(a)earthlink.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mrmazda(a)earthlink.net --- Comment #3 from Felix Miata <mrmazda(a)earthlink.net> --- Does booting 5.14.21-150500.55.19.1 solve the problem? 5.14.21-150500.55.22.1 was retracted, should be uninstalled. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1215624] r8152 won't load after latest upgrade - kernel 5.14.21-150500.55.22-default
by bugzilla_noreply＠suse.com 26 Sep '23

26 Sep '23

https://bugzilla.suse.com/show_bug.cgi?id=1215624 https://bugzilla.suse.com/show_bug.cgi?id=1215624#c7 --- Comment #7 from Stephan Hemeier <Sauerlandlinux(a)gmx.de> --- The Version 5.14.21-150500.55.22 is retracted, but not deleted from the Repo. If you have deleted the Version, all is good. You will not get this Version by an Update, you can only install this Version by explicit selecting the Version to install. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1215624] New: r8152 won't load after latest upgrade - kernel 5.14.21-150500.55.22-default
by bugzilla_noreply＠suse.com 26 Sep '23

26 Sep '23

https://bugzilla.suse.com/show_bug.cgi?id=1215624 Bug ID: 1215624 Summary: r8152 won't load after latest upgrade - kernel 5.14.21-150500.55.22-default Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: kjchmielewski(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 869693 --> https://bugzilla.suse.com/attachment.cgi?id=869693&action=edit kernel 5.14.21-150500.55.22-default messages After applying latest kernel security update: 5.14.21-150500.55.22-default r8152 driver for Dell TB16 Dock ethernet usb lan device won't load anymore, dmesg -xe shows continously repeating messages: kern :info : [ +0,000056] r8152 6-1.2:1.0 (unnamed net_device) (uninitialized): Using pass-thru MAC addr c4:cb:e1:1e :de:03 kern :info : [ +0,000567] r8152 6-1.2:1.0 eth1: v1.12.13 kern :info : [ +0,000680] usb 6-1.2: USB disconnect, device number 4 kern :info : [ +0,401531] usb 6-1.2: new SuperSpeed USB device number 5 using xhci_hcd kern :info : [ +0,025511] usb 6-1.2: New USB device found, idVendor=0bda, idProduct=8153, bcdDevice=30.11 kern :info : [ +0,000020] usb 6-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=6 kern :info : [ +0,000006] usb 6-1.2: Product: USB 10/100/1000 LAN kern :info : [ +0,000004] usb 6-1.2: Manufacturer: Realtek kern :info : [ +0,000003] usb 6-1.2: SerialNumber: 000002000000 kern :info : [ +0,285851] usb 6-1.2: reset SuperSpeed USB device number 5 using xhci_hcd kern :info : [ +0,021016] usb 6-1.2: device firmware changed kern :info : [ +0,000131] usb 6-1.2: Dell TB16 Dock, disable RX aggregation kern :info : [ +0,000063] r8152 6-1.2:1.0 (unnamed net_device) (uninitialized): Using pass-thru MAC addr c4:cb:e1:1e :de:03 kern :info : [ +0,000510] r8152 6-1.2:1.0 eth1: v1.12.13 kern :info : [ +0,000660] usb 6-1.2: USB disconnect, device number 5 kern :info : [ +0,390240] usb 6-1.2: new SuperSpeed USB device number 6 using xhci_hcd kern :info : [ +0,025976] usb 6-1.2: New USB device found, idVendor=0bda, idProduct=8153, bcdDevice=30.11 kern :info : [ +0,000019] usb 6-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=6 kern :info : [ +0,000006] usb 6-1.2: Product: USB 10/100/1000 LAN kern :info : [ +0,000004] usb 6-1.2: Manufacturer: Realtek kern :info : [ +0,000004] usb 6-1.2: SerialNumber: 000002000000 kern :info : [ +0,285465] usb 6-1.2: reset SuperSpeed USB device number 6 using xhci_hcd kern :info : [ +0,021561] usb 6-1.2: device firmware changed kern :info : [ +0,000112] usb 6-1.2: Dell TB16 Dock, disable RX aggregation kern :info : [ +0,000064] r8152 6-1.2:1.0 (unnamed net_device) (uninitialized): Using pass-thru MAC addr c4:cb:e1:1e :de:03 It works fine after rebooting with previous kernel version: 5.14.21-150500.55.19-default and worked with earlier versions in the past. kern :info : [ +0,000614] usbcore: registered new interface driver r8152 kern :info : [ +0,013203] r8152 6-1.2:1.0 (unnamed net_device) (uninitialized): Using pass-thru MAC addr c4:cb:e1:1e:de:03 kern :info : [ +0,063254] r8152 6-1.2:1.0: load rtl8153a-3 v2 02/07/20 successfully kern :info : [ +0,022944] r8152 6-1.2:1.0 eth1: v1.12.13 kern :info : [ +0,001152] r8152 6-1.2:1.0 eth1: carrier on Full dmesg -xe logs attached. -- You are receiving this mail because: You are the assignee for the bug.

1 4

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

26 Sep '23

https://bugzilla.suse.com/show_bug.cgi?id=1215436 https://bugzilla.suse.com/show_bug.cgi?id=1215436#c21 --- Comment #21 from Jiri Slaby <jslaby(a)suse.com> --- Could you try the kernel from: https://build.opensuse.org/project/monitor/home:jirislaby:stable-boot_delay again (once it builds)? It reverts all the 6.5 firewire commits. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1215665] New: Lenovo ThinkPad T14s Gen 2a intermittent freezing / "your system is too slow"
by bugzilla_noreply＠suse.com 26 Sep '23

26 Sep '23

https://bugzilla.suse.com/show_bug.cgi?id=1215665 Bug ID: 1215665 Summary: Lenovo ThinkPad T14s Gen 2a intermittent freezing / "your system is too slow" 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: georg.pfuetzenreuter(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hi, said machine will randomly freeze for a marginal period of time (1-5 seconds). This is particularly noticeable while performing touch-typing, where the short freezes result in irregular text input (missing, duplicate, or infinite characters). I attempted booting with `amd_pstate=active` with no change in behavior. My desktop environment is openSUSEway (Sway/Wayland). This problem started occurring some Tumbleweed snapshots ago, though I don't recall exactly - there were other freezing issues with this hardware model before, though not in the current form where it happens consistently for short periods throughout the day. There's nothing printed in the kernel log when this happens, but the system journal is spammed with the following: ``` Sep 25 13:09:44 dreamland sway[2704]: 25:10:18.402 [ERROR] [wlr] [libinput] event5 - Microsoft Microsoft Ergonomic Mouse: WARNING: log rate limit exceeded (5 msgs per 60min). Discarding future messages. Sep 25 13:10:03 dreamland sway[2704]: 25:10:36.590 [ERROR] [wlr] [libinput] event6 - Logitech K350: client bug: event processing lagging behind by 26ms, your system is too slow ``` Currently I am running: ``` $ grep ^VERSION /etc/os-release ; uname -r ; cpupower frequency-info --driver VERSION_ID="20230921" 6.5.4-1-default analyzing CPU 15: driver: amd-pstate-epp ``` Note that the behavior happens both under load and when idle, directly after rebooting. Happy to test any other constellations or provide more information as needed. I entered this in the Kernel component as there seem to have been other kernel issues with this machine in the past, however feel free to route elsewhere should this not apply here. Would appreciate any help, Georg -- You are receiving this mail because: You are the assignee for the bug.

1 1