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]

Message-ID: <543ABD7D.5010308@hurleysoftware.com>
Date:	Sun, 12 Oct 2014 13:42:21 -0400
From:	Peter Hurley <peter@...leysoftware.com>
To:	Udo van den Heuvel <udovdh@...all.nl>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: CRASH during boot 3.16.3+

On 10/12/2014 09:57 AM, Udo van den Heuvel wrote:
> Hello,
> 
> 3.16.2 boots and works fine.
> Kernels 3.16.3 and newer crash very early during boot. (did not yet try
> 3.17)
> 
> 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.

What happens after the 'then a load of rubbish.'? And rubbish is not
very descriptive. Please include a sample, if you can't catch all the
console prints.


Regards,
Peter Hurley

--
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/