From: Don Zickus <dzickus@redhat.com>
To: "CSÉCSY László" <boobaa@frugalware.org>
Cc: "Linus Torvalds" <torvalds@linux-foundation.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
gorcunov@gmail.com, aris@redhat.com, peterz@infradead.org,
"Ingo Molnar" <mingo@elte.hu>,
"VAJNA Miklós" <vmiklos@frugalware.org>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.36 does not boot properly
Date: Mon, 13 Dec 2010 10:09:09 -0500 [thread overview]
Message-ID: <20101213150909.GC18577@redhat.com> (raw)
In-Reply-To: <201012130019.41234.boobaa@frugalware.org>
On Mon, Dec 13, 2010 at 12:19:40AM +0100, CSÉCSY László wrote:
Hell Csecsy,
> Additional info:
>
> The first "bad" build while bisecting caused the above-mentioned freeze, but
> the latest 4 were all panicking immediately after boot - here is the
> "screenshot" I created with my camera:
I find it odd that commit would be the cause of a kernel freeze that early
in boot. But I did try to do a git log between your last known good
commit and bad commit. The output was just the bad commit.
[dzickus@ihatethathostname upstream]$ git log --oneline
93736624635235cc5372ffca6d62816d02170724..e40b17208b6805be50ffe891878662b6076206b9
e40b172 x86: Move notify_die from nmi.c to traps.c
[dzickus@ihatethathostname upstream]$
Though a git log on the bad commit showed other commits I thought would
have popped out before the intersection with the good commit.
Just for my sanity could you do a 'git revert
e40b17208b6805be50ffe891878662b6076206b9' and try that kernel. I would
think it would still fail, but if it does boot then I need to do some
serious head scratching.
Cheers,
Don
next prev parent reply other threads:[~2010-12-13 15:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-12 23:19 2.6.36 does not boot properly CSÉCSY László
2010-12-13 15:04 ` Cyrill Gorcunov
2010-12-13 15:09 ` Don Zickus [this message]
2010-12-14 4:22 ` Len Brown
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=20101213150909.GC18577@redhat.com \
--to=dzickus@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=aris@redhat.com \
--cc=boobaa@frugalware.org \
--cc=gorcunov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=torvalds@linux-foundation.org \
--cc=vmiklos@frugalware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox