linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Hurley <peter@hurleysoftware.com>
To: Udo van den Heuvel <udovdh@xs4all.nl>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: CRASH during boot 3.16.3+
Date: Mon, 13 Oct 2014 08:14:58 -0400	[thread overview]
Message-ID: <543BC242.7020304@hurleysoftware.com> (raw)
In-Reply-To: <543BA610.8010001@xs4all.nl>

On 10/13/2014 06:14 AM, Udo van den Heuvel 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.

Why incomplete? No kernel command line, no version stamp, no CPU info,
no memory map, no IRQ routing info, etc.

And this is only going to be useful with a commit identified by git bisect.

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

The bisect is preferred and will take you less time.

But if you _also_ want to try to capture the console output, I'd suggest
setting up netconsole if you can't setup a serial console.
Basic setup information is in Documentation/networking/netconsole.txt

Regards,
Peter Hurley

  reply	other threads:[~2014-10-13 12:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-12 13:57 CRASH during boot 3.16.3+ Udo van den Heuvel
2014-10-12 17:42 ` Peter Hurley
2014-10-13 10:14   ` Udo van den Heuvel
2014-10-13 12:14     ` Peter Hurley [this message]
2014-10-13 12:22       ` Udo van den Heuvel
2014-10-13 14:01         ` Peter Hurley
2014-10-13 13:46       ` Udo van den Heuvel
2014-10-25 15:18       ` Udo van den Heuvel
2014-10-28 20:32         ` Peter Hurley
2014-10-13 12:26     ` Chuck Ebbert
2014-10-18 10:56       ` Udo van den Heuvel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=543BC242.7020304@hurleysoftware.com \
    --to=peter@hurleysoftware.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=udovdh@xs4all.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).