[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

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.


Reply to: