On 8/11/07, Dan Merillat <[EMAIL PROTECTED]> wrote:
> This one is going to be fun, since it's a hard reset back to bios, no
> OOPS or anything shown. It may be about the time RadeonFB kicks in,
> but it's impossible to tell. I'd guess 15-20 lines into dmesg.
>
> I'm in the process of bisecting, currently 94c18227..d23cf676.
>
> Any guesses of a specific patch to check?
Except it's not d23cf676, that was the version I was running while
building HEAD, whoops.
I'm used to monotonic version numbers, not SHA hashes. I'll keep
better track next time.
For completeness, the commit that caused boot to fail was:
commit ab144f5ec64c42218a555ec1dbde6b60cf2982d6
Author: Andi Kleen <[EMAIL PROTECTED]>
Date: Fri Aug 10 22:31:03 2007 +0200
i386: Make patching more robust, fix paravirt issue
Except I'm using x86_64? So not sure why that one rev kills me.
ACPI? It dies right after the CPU is identified:
CPU: AMD Athlon(tm) 64 Processor 3000+ stepping 00
ACPI: Core revision 20070126
I don't think that second line is printed on the crash.
However, a git-pull at 2am (b8d3f244) fixed it. Not sure where in
there it started working again, I can bisect backwards to find out if
need be.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
