All of lore.kernel.org
 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: Sun, 12 Oct 2014 13:42:21 -0400	[thread overview]
Message-ID: <543ABD7D.5010308@hurleysoftware.com> (raw)
In-Reply-To: <543A88E4.4060707@xs4all.nl>

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


  reply	other threads:[~2014-10-12 17:42 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 [this message]
2014-10-13 10:14   ` Udo van den Heuvel
2014-10-13 12:14     ` Peter Hurley
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=543ABD7D.5010308@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.