Re: [REGRESSION] Kernel 5.15 reboots / freezes upon ifup/ifdown

[Stefan Dietrich <roots@gmx.de>]

Hi Thorsten,

thanks for the pointer. netdev should be in the loop now.


Stefan

On Wed, 2021-11-24 at 08:28 +0100, Stefan Dietrich wrote:
> Summary: When attempting to rise or shut down a NIC manually or via
> network-manager under 5.15, the machine reboots or freezes.
>
> Occurs with: 5.15.4-051504-generic and earlier 5.15 mainline (
> https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.15.4/) as well as
> liquorix flavours.
> Does not occur with: 5.14 and 5.13 (both with various flavours)
>
>
> Hi all,
>
> I'm experiencing a severe bug that causes the machine to reboot or
> freeze when trying to login and/or rise/shutdown a NIC. Here's a
> brief
> description of scenarios I've tested:
>
> Scenario 1: enp6s0 managed manually using /etc/networking/interfaces,
> DHCP
> a. Issuing ifdown enp6s0 in terminal will throw
> 	"/etc/resolvconf/update.d/libc: Warning: /etc/resolv.conf is
> 	not a symbolic link to /run/resolvconf/resolv.conf"
> and cause the machine to reboot after ~10s of showing a blinking
> cursor
>
> b. Issuing shutdown -h now or trying to shutdown/reboot machine via
> GUI:
> shutdown will stop on "stop job is running for ifdown enp6s0" and
> after
> approx. 10..15s the countdown freezes. Repeated ALT-SysReq-REISUB
> does
> not reboot the machine, a hard reset is required.
>
> --
>
> Scenario 2: enp6s0 managed manually using /etc/networking/interfaces,
> STATIC
> a. Issuing ifdown enp6s0 in terminal will throw
> 	"send_packet: Operation not permitted
> 	dhclient.c:3010: Failed to send 300 byte long packet over
> 	fallback interface."
> and cause the machine to reboot after ~10s of blinking cursor.
>
> b. Issuing shutdown -h now or trying to shutdown or reboot machine
> via
> GUI: shutdown will stop on "stop job is running for ifdown enp6s0"
> and
> after approx. 10..15s the countdown freezes. Repeated ALT-SysReq-
> REISUB
> does not reboot the machine, a hard reset is required.
>
> --
>
> Scenario 3: enp6s0 managed by network manager
> a. After booting and logging in either via GUI or TTY, the display
> will
> stay blank and only show a blinking cursor and then freeze after
> 5..10s. ALT-SysReq-REISUB does not reboot the machine, a hard reset
> is
> required.
>
> --
>
> Here's a snippet from the journal for Scenario 1a:
>
> Nov 21 10:39:25 computer sudo[5606]:    user : TTY=pts/0 ;
> PWD=/home/user ; USER=root ; COMMAND=/usr/sbin/ifdown enp6s0
> Nov 21 10:39:25 computer sudo[5606]: pam_unix(sudo:session): session
> opened for user root by (uid=0)
> -- Reboot --
> Nov 21 10:40:14 computer systemd-journald[478]: Journal started
>
> --
>
> I'm running Alder Lake i9 12900K but I have E-cores disabled in BIOS.
> Here are some more specs with working kernel:
>
> $ inxi -bxz
> System:    Kernel: 5.14.0-19.2-liquorix-amd64 x86_64 bits: 64
> compiler:
> N/A Desktop: Xfce 4.16.3
>            Distro: Ubuntu 20.04.3 LTS (Focal Fossa)
> Machine:   Type: Desktop System: ASUS product: N/A v: N/A serial: N/A
>            Mobo: ASUSTeK model: ROG STRIX Z690-A GAMING WIFI D4 v:
> Rev
> 1.xx serial: <filter>
>            UEFI [Legacy]: American Megatrends v: 0707 date:
> 11/10/2021
> CPU:       8-Core: 12th Gen Intel Core i9-12900K type: MT MCP arch:
> N/A
> speed: 5381 MHz max: 3201 MHz
> Graphics:  Device-1: NVIDIA vendor: Gigabyte driver: nvidia v: 470.86
> bus ID: 01:00.0
>            Display: server: X.Org 1.20.11 driver: nvidia tty: N/A
>            Message: Unable to show advanced data. Required tool
> glxinfo
> missing.
> Network:   Device-1: Intel vendor: ASUSTeK driver: igc v: kernel
> port:
> 4000 bus ID: 06:00.0
>
>
> Please advice how I may assist in debugging!
>
> Thanks.
>