From: "Dan Merillat" <dan.merillat@gmail.com>
To: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: reset during bootup - solved
Date: Sun, 12 Aug 2007 05:44:36 -0400 [thread overview]
Message-ID: <a56dfcf00708120244x3ae8f4w9183354cf5f33f93@mail.gmail.com> (raw)
On 8/11/07, Dan Merillat <dan.merillat@gmail.com> 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 <ak@suse.de>
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.
next reply other threads:[~2007-08-12 9:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-12 9:44 Dan Merillat [this message]
2007-08-12 11:09 ` Paolo Ornati
2007-08-12 14:03 ` Andi Kleen
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=a56dfcf00708120244x3ae8f4w9183354cf5f33f93@mail.gmail.com \
--to=dan.merillat@gmail.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®