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 [
Bug#1013728: mount: exfat filesystem mtime's are wrong
Package: src:linux
Version: 5.10.113-1
Severity: normal
X-Debbugs-Cc: dpchr...@holgerdanske.com
Dear Maintainer,
Please see:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001306
David
-- Package-specific info:
** Version:
Linux version 5.10.0-14-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.113-1 (2022-04-29)
** Command line:
BOOT_IMAGE=/vmlinuz-5.10.0-14-amd64
root=UUID=ca7232ce-9982-46a0-b7b2-ed819ed6068e ro noresume
** Tainted: POE (12289)
* proprietary module was loaded
* externally-built ("out-of-tree") module was loaded
* unsigned module was loaded
** Kernel log:
Unable to read kernel log; any relevant messages should be attached
** Model information
sys_vendor: Dell Inc.
product_name: Latitude E6520
product_version: 01
chassis_vendor: Dell Inc.
chassis_version:
bios_vendor: Dell Inc.
bios_version: A22
board_vendor: Dell Inc.
board_name: 0J4TFW
board_version: A01
** Loaded modules:
exfat
uas
usb_storage
md4
sha512_ssse3
sha512_generic
cmac
nls_utf8
cifs
dns_resolver
fscache
libdes
vboxnetadp(OE)
vboxnetflt(OE)
vboxdrv(OE)
cpufreq_conservative
cpufreq_powersave
cpufreq_ondemand
cpufreq_userspace
zfs(POE)
zunicode(POE)
zzstd(OE)
zlua(OE)
zavl(POE)
icp(POE)
zcommon(POE)
znvpair(POE)
spl(OE)
intel_rapl_msr
snd_hda_codec_hdmi
intel_rapl_common
snd_hda_codec_idt
snd_hda_codec_generic
snd_hda_intel
snd_intel_dspcfg
soundwire_intel
x86_pkg_temp_thermal
intel_powerclamp
soundwire_generic_allocation
coretemp
iwldvm
snd_soc_core
kvm_intel
uvcvideo
snd_compress
mac80211
dell_rbtn
soundwire_cadence
videobuf2_vmalloc
videobuf2_memops
libarc4
mei_wdt
mei_hdcp
videobuf2_v4l2
dell_laptop
snd_hda_codec
kvm
videobuf2_common
ledtrig_audio
snd_hda_core
iwlwifi
irqbypass
videodev
dell_wmi
snd_hwdep
dell_smm_hwmon
dell_smbios
rapl
joydev
mc
soundwire_bus
intel_cstate
cfg80211
wmi_bmof
pcspkr
dcdbas
snd_pcm
sparse_keymap
at24
dell_wmi_descriptor
intel_uncore
serio_raw
iTCO_wdt
snd_timer
intel_pmc_bxt
snd
sg
iTCO_vendor_support
mei_me
watchdog
soundcore
rfkill
mei
evdev
dell_smo8800
ac
firewire_sbp2
parport_pc
ppdev
lp
parport
fuse
configfs
ip_tables
x_tables
autofs4
ext4
crc16
mbcache
jbd2
crc32c_generic
dm_crypt
dm_mod
hid_generic
sd_mod
sr_mod
t10_pi
cdrom
crc_t10dif
crct10dif_generic
usbhid
hid
i915
nouveau
mxm_wmi
crct10dif_pclmul
crct10dif_common
crc32_pclmul
ttm
crc32c_intel
ahci
i2c_algo_bit
libahci
firewire_ohci
ghash_clmulni_intel
drm_kms_helper
libata
e1000e
ehci_pci
sdhci_pci
firewire_core
cqhci
i2c_i801
ehci_hcd
sdhci
cec
ptp
aesni_intel
drm
usbcore
libaes
crypto_simd
mmc_core
scsi_mod
cryptd
psmouse
glue_helper
i2c_smbus
lpc_ich
crc_itu_t
pps_core
wmi
usb_common
battery
video
button
** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core Processor
Family DRAM Controller [8086:0104] (rev 09)
Subsystem: Dell 2nd Generation Core Processor Family DRAM Controller
[1028:0494]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR-
00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200/2nd Generation Core
Processor Family PCI Express Root Port [8086:0101] (rev 09) (prog-if 00 [Normal
decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities:
Kernel driver in use: pcieport
00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core
Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if
00 [VGA controller])
DeviceName: Onboard IGD
Subsystem: Dell 2nd Generation Core Processor Family Integrated
Graphics Controller [1028:0494]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR-
Kernel driver in use: i915
Kernel modules: i915
00:16.0 Communication controller [0780]: Intel Corporation 6 Series/C200 Series
Chipset Family MEI Controller #1 [8086:1c3a] (rev 04)
Subsystem: Dell 6 Series/C200 Series Chipset Family MEI Controller
[1028:0494]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR-
Kernel driver in use: mei_me
Kernel modules: mei_me
00:19.0 Ethernet controller [0200]: Intel Corporation 82579LM Gigabit Network
Connection (Lewisville) [8086:1502] (rev 04)
DeviceName: Onboard LAN
Subsystem: Dell 82579LM Gigabit Network Connection (Lewisville)
[1028:0494]
Control: I/O+ Mem+
Re: virtio_balloon regression in 5.19-rc3
On Tue, Jun 21, 2022 at 06:10:00PM +0200, Ben Hutchings wrote: > On Tue, 2022-06-21 at 17:34 +0800, Jason Wang wrote: > > On Tue, Jun 21, 2022 at 5:24 PM David Hildenbrand wrote: > > > > > > On 20.06.22 20:49, Ben Hutchings wrote: > > > > I've tested a 5.19-rc3 kernel on top of QEMU/KVM with machine type > > > > pc-q35-5.2. It has a virtio balloon device defined in libvirt as: > > > > > > > > > > > >> > > function="0x0"/> > > > > > > > > > > > > but the virtio_balloon driver fails to bind to it: > > > > > > > > virtio_balloon virtio4: init_vqs: add stat_vq failed > > > > virtio_balloon: probe of virtio4 failed with error -5 > > > > > > > > > > Hmm, I don't see any recent changes to drivers/virtio/virtio_balloon.c > > > > > > virtqueue_add_outbuf() fails with -EIO if I'm not wrong. That's the > > > first call of virtqueue_add_outbuf() when virtio_balloon initializes. > > > > > > > > > Maybe something in generic virtio code changed? > > > > Yes, we introduced the IRQ hardening. That could be the root cause and > > we've received lots of reports so we decide to disable it by default. > > > > Ben, could you please try this patch: (and make sure > > CONFIG_VIRTIO_HARDEN_NOTIFICATION is not set) > > > > https://lore.kernel.org/lkml/20220620024158.2505-1-jasow...@redhat.com/T/ > > Yes, that patch fixes the regression for me. > > Ben. Jason are you going to fix balloon to call device_ready before registering device with linux? > -- > Ben Hutchings > Any smoothly functioning technology is indistinguishable > from a rigged demo.
