On Sat, 26 Aug 2017 13:02:18 +0200 Francesco Poli <
invernomuto@paranoici.org> 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!