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

Bug#996667: kernel panic with kernel upgrade on diskless PXE + NFS system



Control: tags -1 + moreinfo
Control: severity -1 important 

On Sun, Oct 17, 2021 at 02:52:31AM +0000, debian@good-with-numbers.com wrote:
> Package: linux-image-4.19.0-17-amd64
> Version: 4.19.194-3
> Severity: critical
> 
> 
> I have the following packages installed:
> 
> linux-image-4.19.0-16-amd64
> linux-image-4.19.0-17-amd64
> linux-image-4.19.0-18-amd64
> 
> The system boots PXE on NFS--completely diskless.  eth0 connects to the
> PXE/NFS server.  The -16 release runs just fine.  I tried to upgrade to
> the -18, and then -17, releases by switching the PXE configuration, but
> both failed.  The -18 release failed at:
> 
> ----------------------------------------------------------------------
> Begin: Loading essential drivers ... done.
> Begin: Running /scripts/init-premount ... done.
> Begin: Mounting root file system ... Begin: Running /scripts/nfs-top ... done.
> Begin: Running /scripts/nfs-premount ... done.
> ipconfig: eth0: SIOCGIFINDEX: No such device
> ipconfig: no devices to configure
> ipconfig: eth0: SIOCGIFINDEX: No such device
> ipconfig: no devices to configure
> ipconfig: eth0: SIOCGIFINDEX: No such device
> ipconfig: no devices to configure
> ipconfig: eth0: SIOCGIFINDEX: No such device
> ipconfig: no devices to configure
> ipconfig: eth0: SIOCGIFINDEX: No such device
> ipconfig: no devices to configure
> ipconfig: eth0: SIOCGIFINDEX: No such device
> ipconfig: no devices to configure
> ipconfig: eth0: SIOCGIFINDEX: No such device
> ipconfig: no devices to configure
> ipconfig: eth0: SIOCGIFINDEX: No such device
> ipconfig: no devices to configure
> ipconfig: eth0: SIOCGIFINDEX: No such device
> ipconfig: no devices to configure
> ipconfig: eth0: SIOCGIFINDEX: No such device
> ipconfig: no devices to configure
> /init: .: line 275: can't open '/run/net-eth0.conf': No such file or directory
> [    4.xxxxxx] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000200
> ----------------------------------------------------------------------
> 
> etc.  (Retyped from a photo.)  The -17 release output is the same.
> 
> I don't know what file "line 275" refers to.
> 
> There were a lot of updates from 4.19.181-1 to 4.19.194-3.

We have too little information here. From the booting kernel could you
please add the boot log, and as well any of the information which
would be collected by reportbug kernel, so we can understand what NIC
you have on eth0.

Regards,
Salvatore


Reply to: