linux-kernel - Re: CRASH during boot 3.16.3+

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 13 Oct 2014 07:26:32 -0500
From:	Chuck Ebbert <cebbert.lkml@...il.com>
To:	Udo van den Heuvel <udovdh@...all.nl>
Cc:	Peter Hurley <peter@...leysoftware.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: CRASH during boot 3.16.3+

On Mon, 13 Oct 2014 12:14:40 +0200
Udo van den Heuvel <udovdh@...all.nl> wrote:

> On 2014-10-12 19:42, Peter Hurley wrote:
> > On 10/12/2014 09:57 AM, Udo van den Heuvel wrote:
> >> The problem:
> >> During the first few seconds of bootup the kernel gets into some sort of
> >> loop and rapidly prints loads of register-like things and then a load of
> >> rubbish.
> >> I did `make clean` and then a rebuild etc but this did not help.
> >>
> >> How can I capture the logging to find the point where things go wrong?
> >> How can I find out what is wrong?
> > 
> > Start with git bisect between good=3.16.2 and bad=3.16.3.
> > And dmesg from 3.16.2.
> 
> Incomplete dmesg attached for 3.16.2.
> 
> > What happens after the 'then a load of rubbish.'?
> 
> I press reset as this is unexpected and looks like it will not result in
> a succesfull boot.
> 
> > And rubbish is not
> very descriptive. Please include a sample, if you can't catch all the
> console prints.
> 
> How can I capture the output easily?

Add "boot_delay=3000" to the kernel command line. This will add a 3
second delay between each line. Then take pictures of the screen
while it boots. And try to time the shots so you take them during the
delays.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/