Bug#1013731: linux-image-5.10.0-13-amd64: 5.10.0-13-amd64 RTL8153 power management kernel hang
On 12/6/22 03:43, Renato Gallo wrote: have you tried with 6.0 ? Can you clarify to whom your question is addressed? If to me, I haven't done any further troubleshooting since opening this issue.
Bug#1013731: linux-image-5.10.0-13-amd64: 5.10.0-13-amd64 RTL8153 power management kernel hang
have you tried with 6.0 ? On Tue, Dec 6, 2022 at 12:27 PM Diederik de Haas wrote: > Control: tag -1 moreinfo > > On Saturday, 25 June 2022 05:33:01 CET Ian Turner wrote: > > On this kernel (linux-image-5.10.0-13-amd64 and previous) I experience > > occasional kworker kernel hangs with numerous other associated > > uninterruptable processes. > > > > * The issue is resolved in linux-image-5.16.0-0.bpo.4-rt-amd64 > > What's the current status of this issue? > As it was resolved in 5.16, there's a reasonable chance such a fix has now > landed in 5.10 series too.
Processed: Re: Bug#1013731: linux-image-5.10.0-13-amd64: 5.10.0-13-amd64 RTL8153 power management kernel hang
Processing control commands: > tag -1 moreinfo Bug #1013731 [src:linux] linux-image-5.10.0-13-amd64: 5.10.0-13-amd64 RTL8153 power management kernel hang Added tag(s) moreinfo. -- 1013731: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013731 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1013731: linux-image-5.10.0-13-amd64: 5.10.0-13-amd64 RTL8153 power management kernel hang
Control: tag -1 moreinfo On Saturday, 25 June 2022 05:33:01 CET Ian Turner wrote: > On this kernel (linux-image-5.10.0-13-amd64 and previous) I experience > occasional kworker kernel hangs with numerous other associated > uninterruptable processes. > > * The issue is resolved in linux-image-5.16.0-0.bpo.4-rt-amd64 What's the current status of this issue? As it was resolved in 5.16, there's a reasonable chance such a fix has now landed in 5.10 series too. signature.asc Description: This is a digitally signed message part.
Bug#1013731: linux-image-5.10.0-13-amd64: 5.10.0-13-amd64 RTL8153 power management kernel hang
On zaterdag 25 juni 2022 05:33:01 CEST Ian Turner wrote: > I wonder if it makes sense to cherry pick this patch into Bullseye, I'm not seeing any patch? Only a request to test a 5.13 kernel ... and then the discussion stopped (without answer wrt 5.13 kernel). > assuming that Bullseye will not get 5.13 or later. That is a correct assumption, Bullseye will stay on 5.10. That doesn't automatically mean it can't be fixed in 5.10 as well. First you'd need to identify the exact commit that fixed the issue, which usually follows identifying the exact commit that caused the issue. Once you have that, you can ask *upstream* whether that commit can be backported to (upstream) stable kernel versions, like 5.10. Once that happens, Debian's 5.10 should pick that up when a newer 5.10 kernel gets packaged for Bullseye. HTH, Diederik signature.asc Description: This is a digitally signed message part.
Bug#1013731: linux-image-5.10.0-13-amd64: 5.10.0-13-amd64 RTL8153 power management kernel hang
Package: src:linux Version: 5.10.106-1 Severity: important Tags: upstream X-Debbugs-Cc: vec...@vectro.org Dear Maintainer, On this kernel (linux-image-5.10.0-13-amd64 and previous) I experience occasional kworker kernel hangs with numerous other associated uninterruptable processes. I think the issue must be the same as the one documented here: https://www.mail-archive.com/netdev@vger.kernel.org/msg404262.html because: * The stack trace of the hung kworker matches * Other elements of the syndrome match (numerous uninterruptable user processes etc.) * The issue is resolved in linux-image-5.16.0-0.bpo.4-rt-amd64 I wonder if it makes sense to cherry pick this patch into Bullseye, assuming that Bullseye will not get 5.13 or later. Ian Turner -- Package-specific info: ** Version: Linux version 5.10.0-13-amd64 (debian-kernel@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.10.106-1 (2022-03-17) ** Command line: BOOT_IMAGE=/vmlinuz-5.10.0-13-amd64 root=/dev/mapper/internal-root ro security=selinux quiet ** Not tainted ** Kernel log: [ 10.158476] skl_hda_dsp_generic skl_hda_dsp_generic: hda_dsp_hdmi_build_controls: no PCM in topology for HDMI converter 4 [ 10.172023] input: sof-hda-dsp Mic as /devices/pci:00/:00:1f.3/skl_hda_dsp_generic/sound/card0/input18 [ 10.172067] input: sof-hda-dsp Headphone as /devices/pci:00/:00:1f.3/skl_hda_dsp_generic/sound/card0/input19 [ 10.172097] input: sof-hda-dsp HDMI/DP,pcm=3 as /devices/pci:00/:00:1f.3/skl_hda_dsp_generic/sound/card0/input20 [ 10.172132] input: sof-hda-dsp HDMI/DP,pcm=4 as /devices/pci:00/:00:1f.3/skl_hda_dsp_generic/sound/card0/input21 [ 10.172156] input: sof-hda-dsp HDMI/DP,pcm=5 as /devices/pci:00/:00:1f.3/skl_hda_dsp_generic/sound/card0/input22 [ 10.245083] mc: Linux media interface: v0.10 [ 10.248374] Bluetooth: Core ver 2.22 [ 10.248393] NET: Registered protocol family 31 [ 10.248394] Bluetooth: HCI device and connection manager initialized [ 10.248396] Bluetooth: HCI socket layer initialized [ 10.248398] Bluetooth: L2CAP socket layer initialized [ 10.248401] Bluetooth: SCO socket layer initialized [ 10.259303] videodev: Linux video capture interface: v2.00 [ 10.376016] usbcore: registered new interface driver btusb [ 10.376460] Bluetooth: hci0: Firmware revision 0.0 build 121 week 7 2021 [ 10.468492] uvcvideo: Found UVC 1.00 device Integrated Camera (13d3:56ff) [ 10.473096] input: Integrated Camera: Integrated C as /devices/pci:00/:00:14.0/usb3/3-5/3-5:1.0/input/input23 [ 10.479341] uvcvideo: Found UVC 1.00 device Microsoft LifeCam VX-5000 (045e:0728) [ 10.483537] input: Microsoft LifeCam VX-5000: Micr as /devices/pci:00/:00:14.0/usb3/3-3/3-3.1/3-3.1.2/3-3.1.2.3/3-3.1.2.3:1.0/input/input24 [ 10.483606] usbcore: registered new interface driver uvcvideo [ 10.483607] USB Video Class driver (1.1.1) [ 10.672353] sd 1:0:0:0: Attached scsi generic sg0 type 0 [ 10.672540] sd 2:0:0:0: Attached scsi generic sg1 type 0 [ 10.672614] sr 3:0:0:0: Attached scsi generic sg2 type 5 [ 10.822767] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 10.822769] Bluetooth: BNEP filters: protocol multicast [ 10.822772] Bluetooth: BNEP socket layer initialized [ 10.846393] NET: Registered protocol family 38 [ 11.251961] usbcore: registered new interface driver r8152 [ 11.257681] usbcore: registered new interface driver cdc_ether [ 11.333140] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful [ 11.340797] usb 2-1.1.1: reset SuperSpeed Gen 1 USB device number 4 using xhci_hcd [ 11.374805] r8152 2-1.1.1:1.0: firmware: failed to load rtl_nic/rtl8153b-2.fw (-2) [ 11.374818] r8152 2-1.1.1:1.0: Direct firmware load for rtl_nic/rtl8153b-2.fw failed with error -2 [ 11.374820] r8152 2-1.1.1:1.0: unable to load firmware patch rtl_nic/rtl8153b-2.fw (-2) [ 11.412278] r8152 2-1.1.1:1.0 eth0: v1.11.11 [ 11.424124] r8152 2-1.1.1:1.0 enxe89f801f6f9c: renamed from eth0 [ 11.716218] SELinux: security_context_str_to_sid(system_u:object_r:snappy_snap_t:s0) failed for (dev loop18, type squashfs) errno=-22 [ 11.852020] usbcore: registered new interface driver snd-usb-audio [ 13.156350] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful [ 13.276895] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful [ 13.310293] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful [ 14.451740] Bluetooth: RFCOMM TTY layer initialized [ 14.451746] Bluetooth: RFCOMM socket layer initialized [ 14.451761] Bluetooth: RFCOMM ver 1.11 [ 15.147550] IPv6: ADDRCONF(NETDEV_CHANGE): enxe89f801f6f9c: link becomes ready [ 15.147784] r8152 2-1.1.1:1.0 enxe89f801f6f9c: carrier on [ 17.462699] irq 9: nobody cared (try booting with the "irqpoll" option) [ 17.462704] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.10.0-13-amd64 #1 Debian 5.10.106-1 [
