Bug#868082: linux-image-4.11.0-1-686: fails to boot on i386 (Soekris net5501)

[Francesco Poli]

Control: found -1 linux/4.13.4-2


On Sat, 14 Oct 2017 19:51:57 +0200 Francesco Poli wrote:

[...]
> I have just tried with 'earlyprintk=ttyS0,19200,n8' (and without
> 'quiet'), since I have 'console=ttyS0,19200,n8' among the normal
> parameters.
> 
> Unfortunately, I still get no useful debug output at all:
> 
> Booting a command list
> 
>   Loading Linux 4.13.0-1-686 ...
>   Loading initial ramdisk ...

I have just tried with the new kernel currently in testing, but I got
the same exact result (no boot and no debug output)...


-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgpIi_nW4kXsC.pgp
Description: PGP signature

Bug#868082: linux-image-4.11.0-1-686: fails to boot on i386 (Soekris net5501)

[Francesco Poli]

On Thu, 12 Oct 2017 02:12:45 +0100 Ben Hutchings wrote:

> On Wed, 2017-10-11 at 23:30 +0200, Francesco Poli wrote:
> [...]
> > For the record, I have just tried with the latest Linux kernel in
> > testing:
> > 
> >   Loading Linux 4.13.0-1-686 ...
> >   Loading initial ramdisk ...
> > 
> > 
> > Another boot failure...
> > 
> > Is there any progress in the bug investigation?
> 
> I don't think anyone's investigating this, I'm afraid.

Huh? What was point of having me bisecting among versions
uploaded to Debian experimental, then?

> 
> Going back to the lack of output with 'earlyprintk=ttyS0', I had a
> check and the default bit rate for that is 9600(!) whereas I (and maybe
> you) would have expected 115200.  So perhaps you could try
> 'earlyprintk=ttyS0,115200' (or whichever bit rate you want).

I have just tried with 'earlyprintk=ttyS0,19200,n8' (and without
'quiet'), since I have 'console=ttyS0,19200,n8' among the normal
parameters.

Unfortunately, I still get no useful debug output at all:

Booting a command list

  Loading Linux 4.13.0-1-686 ...
  Loading initial ramdisk ...




-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgpCKsRc4fo2O.pgp
Description: PGP signature

Bug#868082: linux-image-4.11.0-1-686: fails to boot on i386 (Soekris net5501)

[Ben Hutchings]

On Wed, 2017-10-11 at 23:30 +0200, Francesco Poli wrote:
[...]
> For the record, I have just tried with the latest Linux kernel in
> testing:
> 
>   Loading Linux 4.13.0-1-686 ...
>   Loading initial ramdisk ...
> 
> 
> Another boot failure...
> 
> Is there any progress in the bug investigation?

I don't think anyone's investigating this, I'm afraid.

Going back to the lack of output with 'earlyprintk=ttyS0', I had a
check and the default bit rate for that is 9600(!) whereas I (and maybe
you) would have expected 115200.  So perhaps you could try
'earlyprintk=ttyS0,115200' (or whichever bit rate you want).

Ben.

-- 
Ben Hutchings
Man invented language to satisfy his deep need to complain. - Lily
Tomlin



signature.asc
Description: This is a digitally signed message part

Bug#868082: linux-image-4.11.0-1-686: fails to boot on i386 (Soekris net5501)

[Francesco Poli]

Control: found -1 linux/4.13.4-1


On Mon, 2 Oct 2017 23:26:40 +0200 Francesco Poli wrote:

[...]
> OK, here's the result of the test, after some bisecting:
> 
>  • linux-image-4.10.0-trunk-686-unsigned_4.10.7-1~exp1_i386.deb
> 
>boots correctly
> 
>$ uname -a
>Linux $HOSTNAME 4.10.0-trunk-686 #1 SMP Debian 4.10.7-1~exp1 (2017-03-30) 
> i586 GNU/Linux
> 
> 
>  • linux-image-4.11.0-trunk-686_4.11-1~exp1_i386.deb
> 
>fails to boot
> 
>  Booting a command list
> 
>Loading Linux 4.11.0-trunk-686 ...
>Loading initial ramdisk ...
> 
> 
> 
> I hope this helps in pinpointing the cause of the issue.


For the record, I have just tried with the latest Linux kernel in
testing:

  Loading Linux 4.13.0-1-686 ...
  Loading initial ramdisk ...


Another boot failure...

Is there any progress in the bug investigation?


-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgp5C5r5Y8TtT.pgp
Description: PGP signature

Bug#868082: linux-image-4.11.0-1-686: fails to boot on i386 (Soekris net5501)

[Francesco Poli]

Control: found -1 linux/4.11-1~exp1


On Sun, 24 Sep 2017 20:25:26 +0100 Ben Hutchings wrote:

> On Sun, 2017-09-24 at 17:54 +0200, Francesco Poli wrote:
[...]
> > Is there anything that can be done in order to pinpoint the issue and
> > solve it once and for all?!?
> 
> You could test the 4.10 kernel version from snapshot.debian.org, which
> would narrow down the regresion a bit.

OK, here's the result of the test, after some bisecting:

 • linux-image-4.10.0-trunk-686-unsigned_4.10.7-1~exp1_i386.deb

   boots correctly

   $ uname -a
   Linux $HOSTNAME 4.10.0-trunk-686 #1 SMP Debian 4.10.7-1~exp1 (2017-03-30) 
i586 GNU/Linux


 • linux-image-4.11.0-trunk-686_4.11-1~exp1_i386.deb

   fails to boot

 Booting a command list

   Loading Linux 4.11.0-trunk-686 ...
   Loading initial ramdisk ...



I hope this helps in pinpointing the cause of the issue.



-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgp7hHzlf6BQ2.pgp
Description: PGP signature

Bug#868082: linux-image-4.11.0-1-686: fails to boot on i386 (Soekris net5501)

[Ben Hutchings]

On Sun, 2017-09-24 at 17:54 +0200, Francesco Poli wrote:
> On Sat, 26 Aug 2017 13:02:18 +0200 Francesco Poli wrote:
> 
> Control: found -1 linux/4.12.13-1
> 
> > 
> > On Mon, 17 Jul 2017 09:59:38 +0200 Francesco Poli wrote:
> 
> [...]
> > Hello again,
> > I tested the new kernel version that has recently migrated to Debian
> > testing.
> > 
> > Unfortunately, I get the same exact boot failure.
> > 
> > And no useful output on the serial console, even with
> > 'earlyprintk=ttyS0' and without 'quiet':
> > 
> > Booting a command list
> > 
> >   Loading Linux 4.12.0-1-686 ...
> >   Loading initial ramdisk ...
> > 
> > and then nothing else.
> 
> Another kernel version has just migrated to Debian testing.
> Another boot failure with no useful output on the serial console, even
> with 'earlyprintk=ttyS0' and without 'quiet':
> 
> Booting a command list
> 
>   Loading Linux 4.12.0-2-686 ...
>   Loading initial ramdisk ...
> 
> and nothing else.
> 
> Is there anything that can be done in order to pinpoint the issue and
> solve it once and for all?!?

You could test the 4.10 kernel version from snapshot.debian.org, which
would narrow down the regresion a bit.

Ben.

> Please let me know, thanks for your time.

-- 
Ben Hutchings
Make three consecutive correct guesses and you will be considered an
expert.



signature.asc
Description: This is a digitally signed message part

Bug#868082: linux-image-4.11.0-1-686: fails to boot on i386 (Soekris net5501)

[Francesco Poli]

Control: found -1 linux/4.12.13-1

[I should have put the above control command at the beginning of my
previous message... I am doing so now.]

-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgpU0JN8f3qFV.pgp
Description: PGP signature

Bug#868082: linux-image-4.11.0-1-686: fails to boot on i386 (Soekris net5501)

[Francesco Poli]

On Sat, 26 Aug 2017 13:02:18 +0200 Francesco Poli wrote:

Control: found -1 linux/4.12.13-1

> 
> On Mon, 17 Jul 2017 09:59:38 +0200 Francesco Poli wrote:
[...]
> Hello again,
> I tested the new kernel version that has recently migrated to Debian
> testing.
> 
> Unfortunately, I get the same exact boot failure.
> 
> And no useful output on the serial console, even with
> 'earlyprintk=ttyS0' and without 'quiet':
> 
> Booting a command list
> 
>   Loading Linux 4.12.0-1-686 ...
>   Loading initial ramdisk ...
> 
> and then nothing else.

Another kernel version has just migrated to Debian testing.
Another boot failure with no useful output on the serial console, even
with 'earlyprintk=ttyS0' and without 'quiet':

Booting a command list

  Loading Linux 4.12.0-2-686 ...
  Loading initial ramdisk ...

and nothing else.

Is there anything that can be done in order to pinpoint the issue and
solve it once and for all?!?

Please let me know, thanks for your time.


-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgpfTBveXa5e0.pgp
Description: PGP signature

Bug#868082: linux-image-4.11.0-1-686: fails to boot on i386 (Soekris net5501)

[R.]

Hello,

I'm experiencing the same problem on Soekris net5501, also with the latest
testing 4.12.0.1-686 kernel : the boot process gets stuck on "Loading
initial ramdisk".

The 4.9.0.3-686 boots correctly.

Regards

On Sat, 26 Aug 2017 13:02:18 +0200 Francesco Poli 
wrote:
> Control: found -1 linux/4.12.6-1
>
>
> On Mon, 17 Jul 2017 09:59:38 +0200 Francesco Poli wrote:
>
> > On Sun, 16 Jul 2017 22:27:10 +0100 Ben Hutchings wrote:
> >
> > [...]
> > > If you add 'earlyprintk=ttyS0' to the kernel command line and delete
> > > 'quiet', does it log anything?
> >
> > Hello Ben,
> > thanks for your follow up.
> >
> > I have just tried with 'earlyprintk=ttyS0' and without 'quiet', but the
> > result seems to be the same:
> >
> > Booting a command list
> >
> >   Loading Linux 4.11.0-1-686 ...
> >   Loading initial ramdisk ...
> >
> > and then nothing else.
>
> Hello again,
> I tested the new kernel version that has recently migrated to Debian
> testing.
>
> Unfortunately, I get the same exact boot failure.
>
> And no useful output on the serial console, even with
> 'earlyprintk=ttyS0' and without 'quiet':
>
> Booting a command list
>
>   Loading Linux 4.12.0-1-686 ...
>   Loading initial ramdisk ...
>
> and then nothing else.
>
>
> Please note that, after the test, I again booted the machine with the
> old Linux 4.9.0-3-686 and noticed "recovering journal" for the root
> partition among the boot messages.
> Hence, I suppose the root filesystem was mounted in read/write mode
> during the failed boot of Linux 4.12.0-1-686.
> I don't know whether this piece of information may be useful in order
> to pinpoint the issue...
>
> Please let me know, in case you need any further information and/or in
> case there's some progress on this bug.
>
> Thanks for your time!
>
> Bye.
>
>
> --
>  http://www.inventati.org/frx/
>  There's not a second to spare! To the laboratory!

Bug#868082: linux-image-4.11.0-1-686: fails to boot on i386 (Soekris net5501)

[Francesco Poli]

Control: found -1 linux/4.12.6-1


On Mon, 17 Jul 2017 09:59:38 +0200 Francesco Poli wrote:

> On Sun, 16 Jul 2017 22:27:10 +0100 Ben Hutchings wrote:
> 
> [...]
> > If you add 'earlyprintk=ttyS0' to the kernel command line and delete
> > 'quiet', does it log anything?
> 
> Hello Ben,
> thanks for your follow up.
> 
> I have just tried with 'earlyprintk=ttyS0' and without 'quiet', but the
> result seems to be the same:
> 
> Booting a command list
> 
>   Loading Linux 4.11.0-1-686 ...
>   Loading initial ramdisk ...
> 
> and then nothing else.

Hello again,
I tested the new kernel version that has recently migrated to Debian
testing.

Unfortunately, I get the same exact boot failure.

And no useful output on the serial console, even with
'earlyprintk=ttyS0' and without 'quiet':

Booting a command list

  Loading Linux 4.12.0-1-686 ...
  Loading initial ramdisk ...

and then nothing else.


Please note that, after the test, I again booted the machine with the
old Linux 4.9.0-3-686 and noticed "recovering journal" for the root
partition among the boot messages.
Hence, I suppose the root filesystem was mounted in read/write mode
during the failed boot of Linux 4.12.0-1-686.
I don't know whether this piece of information may be useful in order
to pinpoint the issue...

Please let me know, in case you need any further information and/or in
case there's some progress on this bug.

Thanks for your time!

Bye.


-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgpfUQJZ3OB6J.pgp
Description: PGP signature

Bug#868082: linux-image-4.11.0-1-686: fails to boot on i386 (Soekris net5501)

[Francesco Poli]

On Sun, 16 Jul 2017 22:27:10 +0100 Ben Hutchings wrote:

[...]
> If you add 'earlyprintk=ttyS0' to the kernel command line and delete
> 'quiet', does it log anything?

Hello Ben,
thanks for your follow up.

I have just tried with 'earlyprintk=ttyS0' and without 'quiet', but the
result seems to be the same:

Booting a command list

  Loading Linux 4.11.0-1-686 ...
  Loading initial ramdisk ...

and then nothing else.

I am not removing the "moreinfo" tag from the bug report, since you
could need some further information... Please let me know.

Thanks for your time!


-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgpZqNsUDFXzp.pgp
Description: PGP signature

Bug#868082: linux-image-4.11.0-1-686: fails to boot on i386 (Soekris net5501)

[Ben Hutchings]

Control: tag -1 moreinfo

On Tue, 2017-07-11 at 23:27 +0200, Francesco Poli (wintermute) wrote:
> Package: src:linux
> Version: 4.11.6-1
> Severity: important
> 
> Hello,
> after upgrading an i386 box (Soekris net5501) running testing (buster),
> I found out that the newly migrated Linux kernel fails to boot.
> 
> Looking at the boot through the serial console reveals the following
> few messages:
> 
>   Booting 'Debian GNU/Linux, with Linux 4.11.0-1-686'
> 
>   Loading Linux 4.11.0-1-686 ...
>   Loading initial ramdisk ...
> 
> and then nothing else.
[...]

If you add 'earlyprintk=ttyS0' to the kernel command line and delete
'quiet', does it log anything?

Ben.

-- 
Ben Hutchings
If the facts do not conform to your theory, they must be disposed of.



signature.asc
Description: This is a digitally signed message part

Bug#868082: linux-image-4.11.0-1-686: fails to boot on i386 (Soekris net5501)

[Francesco Poli (wintermute)]

Package: src:linux
Version: 4.11.6-1
Severity: important

Hello,
after upgrading an i386 box (Soekris net5501) running testing (buster),
I found out that the newly migrated Linux kernel fails to boot.

Looking at the boot through the serial console reveals the following
few messages:

  Booting 'Debian GNU/Linux, with Linux 4.11.0-1-686'

  Loading Linux 4.11.0-1-686 ...
  Loading initial ramdisk ...

and then nothing else.

The previous kernel image (4.9.0-3-686) works fine.
I have currently altered GRUB_DEFAULT in /etc/default/grub, in order to
force the machine to automatically boot that kernel version.

I hope that this bug may be fixed soon.
Thanks to the Debian Kernel Team for any help they may provide.




-- Package-specific info:

** Model information

** PCI devices:
00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] CS5536 [Geode 
companion] Host Bridge [1022:2080] (rev 33)
Subsystem: Advanced Micro Devices, Inc. [AMD] CS5536 [Geode companion] 
Host Bridge [1022:2080]
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- 
Kernel driver in use: via-rhine
Kernel modules: via_rhine

00:07.0 Ethernet controller [0200]: VIA Technologies, Inc. VT6105M [Rhine-III] 
[1106:3053] (rev 96)
Subsystem: VIA Technologies, Inc. VT6105M [Rhine-III] [1106:0106]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: via-rhine
Kernel modules: via_rhine

00:08.0 Ethernet controller [0200]: VIA Technologies, Inc. VT6105M [Rhine-III] 
[1106:3053] (rev 96)
Subsystem: VIA Technologies, Inc. VT6105M [Rhine-III] [1106:0106]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: via-rhine
Kernel modules: via_rhine

00:09.0 Ethernet controller [0200]: VIA Technologies, Inc. VT6105M [Rhine-III] 
[1106:3053] (rev 96)
Subsystem: VIA Technologies, Inc. VT6105M [Rhine-III] [1106:0106]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: via-rhine
Kernel modules: via_rhine

00:14.0 ISA bridge [0601]: Advanced Micro Devices, Inc. [AMD] CS5536 [Geode 
companion] ISA [1022:2090] (rev 03)
Subsystem: Advanced Micro Devices, Inc. [AMD] CS5536 [Geode companion] 
ISA [1022:2090]
Control: I/O+ Mem- BusMaster- SpecCycle+ MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- 
ii  grub-pc 1.99-17
pn  linux-doc-4.11  

Versions of packages linux-image-4.11.0-1-686 is related to:
pn  firmware-amd-graphics 
pn  firmware-atheros  
pn  firmware-bnx2 
pn  firmware-bnx2x
pn  firmware-brcm80211
pn  firmware-cavium   
pn  firmware-intel-sound  
pn  firmware-intelwimax   
pn  firmware-ipw2x00  
pn  firmware-ivtv 
pn  firmware-iwlwifi  
pn  firmware-libertas 
pn  firmware-linux-nonfree
pn  firmware-misc-nonfree 
pn  firmware-myricom  
pn  firmware-netxen   
pn  firmware-qlogic   
pn  firmware-realtek  
pn  firmware-samsung  
pn  firmware-siano
pn  firmware-ti-connectivity  
pn  xen-hypervisor

-- no debconf information