From: Vegard Nossum <vegard.nossum@gmail.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.30-rc8 does not boot
Date: Mon, 8 Jun 2009 13:06:19 +0200 [thread overview]
Message-ID: <19f34abd0906080406xd5ed8cwbd4193f2bbf97699@mail.gmail.com> (raw)
In-Reply-To: <4A2CEC5B.3000001@msgid.tls.msk.ru>
2009/6/8 Michael Tokarev <mjt@tls.msk.ru>:
> Michael Tokarev wrote:
>>
>> Hello.
>>
>> I just gave 2.6.30-rc a try, taken from Linus git, tag v2.6.29-rc8.
>> And this one does not want to boot on my test machine which is an
>> AMD X2-64 with AMD780G chipset. Neither 64 nor 32bit kernel boots.
>> I even tried in kvm virtual machine, -- same effect. It freezes right
>> after displaying "Verifying BIOS data successful" message -- nothing
>> more is on the screen.
[...]
> PANIC: early exception 0e rip: 10:ffffffff802c9abd error 0 cr2 0
That seems to be a NULL dereference (0e = page fault, cr2 0 =
dereferenced address).
Try:
$ addr2line -e vmlinux -i ffffffff802c9abd
This should print the name of the function that crashed. If you enable
CONFIG_DEBUG_INFO you can get the exact line number info too (but
remember to replace the ffffffff802c9abd with the new value if you
recompile and run it again).
Vegard
--
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
-- E. W. Dijkstra, EWD1036
prev parent reply other threads:[~2009-06-08 11:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-08 10:23 Michael Tokarev
2009-06-08 10:47 ` Michael Tokarev
2009-06-08 11:00 ` solved: " Michael Tokarev
2009-06-08 11:06 ` Vegard Nossum [this message]
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=19f34abd0906080406xd5ed8cwbd4193f2bbf97699@mail.gmail.com \
--to=vegard.nossum@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjt@tls.msk.ru \
/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®