From: daniel@caiaq.de (Daniel Mack)
To: linux-arm-kernel@lists.infradead.org
Subject: 2.6.34 hangs during boot on PB11MPCore
Date: Sun, 30 May 2010 09:36:52 +0200 [thread overview]
Message-ID: <20100530073652.GX2695@buzzloop.caiaq.de> (raw)
In-Reply-To: <AANLkTin9n6HDdiTnQoQ9mrmuzSR8JhZVq7uPgU86yqgU@mail.gmail.com>
On Sat, May 29, 2010 at 06:02:28PM -0400, Bjoern Brandenburg wrote:
> We've tried three kernel versions:
> - 2.6.33-arm1 [1]
> - boot log: http://pastebin.com/UqhfJNgz
> - 2.6.34-vanilla
> - boot log with maxcpus=1: http://pastebin.com/NHHeYpbb
> - boot log with failure: http://pastebin.com/uy6y8msZ
> - config: http://pastebin.com/v9dttg0L
> - 2.6.34-arm [2]
> - boot log with maxcpus=1: http://pastebin.com/rCy2x9AP
> - boot log with failure: http://pastebin.com/spam.php?i=mpedVqp3
>
> Of these, only 2.6.33-arm1 boots with more than one CPU enabled. The 2.6.34
> versions only boot to login if we restrict the number of CPUs. The configuration
> used in all cases is based on the one provided by ARM [3]. For 2.6.34, we used
> 'make oldconfig' and accepted all defaults.
This sounds like a perfect case for giving 'git bisect' a try. It will
point you to the commit between 2.6.33 and 2.6.34 which broke it for
you.
See for example http://www.landley.net/writing/git-quick.html#bisect for
a detailed explanation of how to use it.
Daniel
next prev parent reply other threads:[~2010-05-30 7:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-29 22:02 2.6.34 hangs during boot on PB11MPCore Bjoern Brandenburg
2010-05-30 7:36 ` Daniel Mack [this message]
2010-05-30 19:27 ` Bjoern Brandenburg
2010-05-30 21:05 ` Bjoern Brandenburg
2010-05-30 21:38 ` Bjoern Brandenburg
2010-05-30 22:46 ` Catalin Marinas
2010-05-31 1:04 ` Bjoern Brandenburg
2010-05-31 1:16 ` Bjoern Brandenburg
2010-05-31 6:26 ` Shilimkar, Santosh
2010-06-01 22:53 ` Bjoern Brandenburg
2010-05-31 7:20 ` Catalin Marinas
2010-06-01 7:46 ` Colin Tuckley
2010-06-01 22:57 ` Bjoern Brandenburg
2010-05-30 7:54 ` Linus Walleij
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=20100530073652.GX2695@buzzloop.caiaq.de \
--to=daniel@caiaq.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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.