Bug#1058999: linux-image-6.5.0-5-amd64: System hangs when connecting an ethernet NIC to network which was not connected on boot
Le 22/01/2024 à 13:49, Erwan David a écrit : Le 23/12/2023 à 21:26, Erwan David a écrit : Le 19/12/2023 à 19:34, Diederik de Haas a écrit : On Tuesday, 19 December 2023 19:16:33 CET Erwan David wrote: Same behaviour with 6.6.3-1 from experimental (that's what apt gave me, maybe tomoroow the 6.6.4). Either your APT cache should be updated or you're using a mirror which is rather severely out of date. 6.6.4-1 was uploaded to Debian on 2023-12-03, a day after .3-1. it was 6.6.4. I tried with my Aten Dock : same thing. I disabled the virtualbox service so that the virtualbox modules are not loaded : it does not hang immediately, but waits a few minutes before doing it. Some more details : 1) problem does not come from ethernet Nics, but rather from Wifi chipset, blocking appears when it is deactivated either by BIOS (when connecting Ethernet) or manually (through nm-applet in KDE) Wifi chipset is 02:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78) Sorry, mail sent too fast : It seems to work better with kernel 6.6.11 (6.6.9 still had the bug). I'll do some other tests when possible (this laptop is my work laptop, and I cannot do tests leading to possible crash as often as I would wa nt -- Erwan David
Bug#1058999: linux-image-6.5.0-5-amd64: System hangs when connecting an ethernet NIC to network which was not connected on boot
Le 23/12/2023 à 21:26, Erwan David a écrit : Le 19/12/2023 à 19:34, Diederik de Haas a écrit : On Tuesday, 19 December 2023 19:16:33 CET Erwan David wrote: Same behaviour with 6.6.3-1 from experimental (that's what apt gave me, maybe tomoroow the 6.6.4). Either your APT cache should be updated or you're using a mirror which is rather severely out of date. 6.6.4-1 was uploaded to Debian on 2023-12-03, a day after .3-1. it was 6.6.4. I tried with my Aten Dock : same thing. I disabled the virtualbox service so that the virtualbox modules are not loaded : it does not hang immediately, but waits a few minutes before doing it. Some more details : 1) problem does not come from ethernet Nics, but rather from Wifi chipset, blocking appears when it is deactivated either by BIOS (when connecting Ethernet) or manually (through nm-applet in KDE) Wifi chipset is 02:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78) -- Erwan David
Bug#1058999: linux-image-6.5.0-5-amd64: System hangs when connecting an ethernet NIC to network which was not connected on boot
Le 19/12/2023 à 19:34, Diederik de Haas a écrit : On Tuesday, 19 December 2023 19:16:33 CET Erwan David wrote: Same behaviour with 6.6.3-1 from experimental (that's what apt gave me, maybe tomoroow the 6.6.4). Either your APT cache should be updated or you're using a mirror which is rather severely out of date. 6.6.4-1 was uploaded to Debian on 2023-12-03, a day after .3-1. it was 6.6.4. I tried with my Aten Dock : same thing. I disabled the virtualbox service so that the virtualbox modules are not loaded : it does not hang immediately, but waits a few minutes before doing it.
Bug#1058999: linux-image-6.5.0-5-amd64: System hangs when connecting an ethernet NIC to network which was not connected on boot
On Tuesday, 19 December 2023 19:16:33 CET Erwan David wrote: > Same behaviour with 6.6.3-1 from experimental (that's what apt gave me, > maybe tomoroow the 6.6.4). Either your APT cache should be updated or you're using a mirror which is rather severely out of date. 6.6.4-1 was uploaded to Debian on 2023-12-03, a day after .3-1. signature.asc Description: This is a digitally signed message part.
Bug#1058999: linux-image-6.5.0-5-amd64: System hangs when connecting an ethernet NIC to network which was not connected on boot
Le 19/12/2023 à 09:10, Salvatore Bonaccorso a écrit : Control: tags -1 + moreinfo On Tue, Dec 19, 2023 at 08:49:45AM +0100, Erwan David wrote: Package: src:linux Version: 6.5.13-1 Severity: important On a Dell Latitude 7490, with 1 intergated e1000e nic, and an extrenal Dock with Realtek8153. If ethernet on one of those NICs is connected at boot, it runs OK. However, if a NIC is connected to network while the kernel runs (or when coming back from hibernation), system hangs, any network related process is stuck (even a simple ip a) and load climbs. Clean shutdown is not possible because disk cannot be unmounted because of those processes. Status here is obviously on a fresh booted system, without the problem. I know how to reproduce, and there is a small time window where I might be able to launch some diagnostic commands at the beginning of the problem. As there won't be any further updates in the 6.5.y series and we will move at some point to the 6.6.y one, can you test it against the version which is currently in experimental? (6.6.4-1~exp1). Regards, Salvatore Same behaviour with 6.6.3-1 from experimental (that's what apt gave me, maybe tomoroow the 6.6.4). I tested with a Lenovo T590 on an Aten dock with also a realtek5183 NIC. It works with 6.5.0-5 On the Dell it works with 6.5.0-4 which makes me think the hardware is good. One difference between the lenovo and the Dell : since the Dell has a smaller disk and was installed in 2020 then upgraded, the /boot is small and initramfs is in "dep" mode, with some modules forced for the dock. At the end of week I'll be able to test the Dell on same Dock as the lenovo (not the other way around, Dell and its dock are work issued and I cannot connect a personnal laptop on the dock), and try to use the "most mode for initramfs. I'll also check carefully the differences between the package lists, especially firmwares.
Processed: Re: Bug#1058999: linux-image-6.5.0-5-amd64: System hangs when connecting an ethernet NIC to network which was not connected on boot
Processing control commands: > tags -1 + moreinfo Bug #1058999 [src:linux] linux-image-6.5.0-5-amd64: System hangs when connecting an ethernet NIC to network which was not connected on boot Added tag(s) moreinfo. -- 1058999: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058999 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1058999: linux-image-6.5.0-5-amd64: System hangs when connecting an ethernet NIC to network which was not connected on boot
Control: tags -1 + moreinfo On Tue, Dec 19, 2023 at 08:49:45AM +0100, Erwan David wrote: > Package: src:linux > Version: 6.5.13-1 > Severity: important > > On a Dell Latitude 7490, with 1 intergated e1000e nic, and an extrenal Dock > with Realtek8153. If ethernet on one of those NICs is > connected at boot, it runs OK. However, if a NIC is connected to network > while the kernel runs (or when coming back from > hibernation), system hangs, any network related process is stuck (even a > simple ip a) and load climbs. > Clean shutdown is not possible because disk cannot be unmounted because of > those processes. > > Status here is obviously on a fresh booted system, without the problem. I > know how to reproduce, and there is a small time window > where I might be able to launch some diagnostic commands at the beginning of > the problem. As there won't be any further updates in the 6.5.y series and we will move at some point to the 6.6.y one, can you test it against the version which is currently in experimental? (6.6.4-1~exp1). Regards, Salvatore
Bug#1058999: linux-image-6.5.0-5-amd64: System hangs when connecting an ethernet NIC to network which was not connected on boot
Package: src:linux
Version: 6.5.13-1
Severity: important
On a Dell Latitude 7490, with 1 intergated e1000e nic, and an extrenal Dock
with Realtek8153. If ethernet on one of those NICs is
connected at boot, it runs OK. However, if a NIC is connected to network while
the kernel runs (or when coming back from
hibernation), system hangs, any network related process is stuck (even a simple
ip a) and load climbs.
Clean shutdown is not possible because disk cannot be unmounted because of
those processes.
Status here is obviously on a fresh booted system, without the problem. I know
how to reproduce, and there is a small time window
where I might be able to launch some diagnostic commands at the beginning of
the problem.
-- Package-specific info:
** Version:
Linux version 6.5.0-5-amd64 (debian-kernel@lists.debian.org) (gcc-13 (Debian
13.2.0-7) 13.2.0, GNU ld (GNU Binutils for Debian) 2.41) #1 SMP PREEMPT_DYNAMIC
Debian 6.5.13-1 (2023-11-29)
** Command line:
BOOT_IMAGE=/vmlinuz-6.5.0-5-amd64 root=/dev/mapper/ot--port--eda--vg-root ro
net.ifnames=0 quiet splash
** Tainted: OE (12288)
* externally-built ("out-of-tree") module was loaded
* unsigned module was loaded
** Kernel log:
[ 16.693178] iwlwifi :02:00.0: Detected crf-id 0xbadcafe, cnv-id 0x10
wfpm id 0x8000
[ 16.693235] iwlwifi :02:00.0: PCI dev 24fd/0050, rev=0x230,
rfid=0xd5d5
[ 16.702693] iwlwifi :02:00.0: firmware: direct-loading firmware
iwlwifi-8265-36.ucode
[ 16.706377] mei_hdcp :00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04:
bound :00:02.0 (ops i915_hdcp_ops [i915])
[ 16.706678] iTCO_vendor_support: vendor-support=0
[ 16.712182] iwlwifi :02:00.0: loaded firmware version 36.ca7b901d.0
8265-36.ucode op_mode iwlmvm
[ 16.712575] snd_hda_intel :00:1f.3: DSP detected with PCI
class/subclass/prog-if info 0x040380
[ 16.712592] snd_hda_intel :00:1f.3: enabling device ( -> 0002)
[ 16.726905] iTCO_wdt iTCO_wdt: Found a Intel PCH TCO device (Version=4,
TCOBASE=0x0400)
[ 16.726812] snd_hda_intel :00:1f.3: bound :00:02.0 (ops
i915_audio_component_bind_ops [i915])
[ 16.727471] ee1004 8-0050: 512 byte EE1004-compliant SPD EEPROM, read-only
[ 17.003787] Bluetooth: Core ver 2.22
[ 17.003802] NET: Registered PF_BLUETOOTH protocol family
[ 17.003803] Bluetooth: HCI device and connection manager initialized
[ 17.003806] Bluetooth: HCI socket layer initialized
[ 17.003808] Bluetooth: L2CAP socket layer initialized
[ 17.003811] Bluetooth: SCO socket layer initialized
[ 17.057532] snd_hda_codec_realtek hdaudioC1D0: autoconfig for ALC3246:
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
[ 17.057539] snd_hda_codec_realtek hdaudioC1D0:speaker_outs=0
(0x0/0x0/0x0/0x0/0x0)
[ 17.057542] snd_hda_codec_realtek hdaudioC1D0:hp_outs=1
(0x21/0x0/0x0/0x0/0x0)
[ 17.057545] snd_hda_codec_realtek hdaudioC1D0:mono: mono_out=0x0
[ 17.057546] snd_hda_codec_realtek hdaudioC1D0:inputs:
[ 17.057548] snd_hda_codec_realtek hdaudioC1D0: Mic=0x12
[ 17.092741] iwlwifi :02:00.0: Detected Intel(R) Dual Band Wireless AC
8265, REV=0x230
[ 17.092813] thermal thermal_zone7: failed to read out thermal zone (-61)
[ 17.099820] iwlwifi :02:00.0: reporting RF_KILL (radio disabled)
[ 17.118484] i2c_hid_acpi i2c-MELF0410:00: device returned incorrect report
(209 vs 4 expected)
[ 17.118602] hid-multitouch 0018:1FD2:7007.0008: failed to fetch feature 4
[ 17.118933] input: MELF0410:00 1FD2:7007 as
/devices/pci:00/:00:15.0/i2c_designware.0/i2c-7/i2c-MELF0410:00/0018:1FD2:7007.0008/input/input22
[ 17.119033] hid-multitouch 0018:1FD2:7007.0008: input,hidraw5: I2C HID v1.00
Device [MELF0410:00 1FD2:7007] on i2c-MELF0410:00
[ 17.124742] input: HDA Digital PCBeep as
/devices/pci:00/:00:1f.3/sound/card1/input20
[ 17.156389] iwlwifi :02:00.0: base HW address: ac:67:5d:ec:95:96, OTP
minor version: 0x0
[ 17.173097] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
[ 17.186889] input: HDA Intel PCH Front Headphone as
/devices/pci:00/:00:1f.3/sound/card1/input21
[ 17.266984] input: HDA Intel PCH HDMI/DP,pcm=3 as
/devices/pci:00/:00:1f.3/sound/card1/input24
[ 17.275704] iTCO_wdt iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[ 17.331264] input: HDA Intel PCH HDMI/DP,pcm=7 as
/devices/pci:00/:00:1f.3/sound/card1/input25
[ 17.331334] input: HDA Intel PCH HDMI/DP,pcm=8 as
/devices/pci:00/:00:1f.3/sound/card1/input26
[ 17.339518] EXT4-fs (nvme0n1p2): mounting ext2 file system using the ext4
subsystem
[ 17.340772] EXT4-fs (nvme0n1p2): mounted filesystem
2b049359-11a3-45fc-ad13-dda0e015c96f r/w without journal. Quota mode: none.
[ 17.340878] input: DELL081C:00 044E:121F Mouse as
/devices/pci:00/:00:15.1/i2c_designware.1/i2c-9/i2c-DELL081C:00/0018:044E:121F.0009/input/input27
[ 17.341209] input: DELL081C:00 044E:121F Touchpad as
