lkml.org 
[lkml]   [2010]   [Dec]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: 2.6.36 does not boot properly
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2010-12-13 16:39    [from the cache]
©2003-2011 Jasper Spaans