From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: PANIC: early exception 08 rip 246:10 error ffffffff810251b5 cr2 0
Date: Fri, 23 Oct 2009 16:45:13 -0700 [thread overview]
Message-ID: <4AE24009.4090408@gmail.com> (raw)
I was looking into seeing if kdump might be able to log this in, but
after reading up
I realized that kdump is something that needs to be on then if a crash
occurs,
then kexec to the rescue.
Anyways I posted a picture on my facebook page of this, and also will
send a post
manually writing this down.
Basically when I use ohci1394_dma=early on the boot param
this happens. if I don't use that boot option then the system runs fine.
[ 0.000000] [<ffffffff81639995>] start_kernel+0x82/0x34d
[ 0.000000] [<ffffffff816392a5>] x86_64_start_reservations+0xac/0xb0
[ 0.000000] [<ffffffff816393a1>] x86_64_start_kernel+0xf8/0x107
PANIC: early exception 08 rip 246:10 error ffffffff810251b5 cr2 0
[ 0.000000] Pid: 0, comm: swapper Not tainted
2.6.32-rc4-00001-g1896a85 #35
[ 0.000000] Call Trace:
[ 0.000000] [<ffffffff8163919e>] early_idt_handler+0x5e/0x71
[ 0.000000] [<ffffffff813b9958>] ? panic+0x10c/0x12e
[ 0.000000] [<ffffffff8164f777>] ___alloc_bootmem_node+0x0/0x60
[ 0.000000] [<ffffffff8164f8eb>] __alloc_bootmem+0xb/0xd
[ 0.000000] [<ffffffff813aba66>] spp_getpage+0x3a/0x6f
[ 0.000000] [<ffffffff8102770d>] fill_pte+0x22/0xde
[ 0.000000] [<ffffffff810278e7>] set_pte_vaddr_pud+0x2c/0x48
[ 0.000000] [<ffffffff81027963>] set_pte_vaddr+0x60/0x65
[ 0.000000] [<ffffffff8102b82e>] __native_set_fixmap+0x24/0x2c
[ 0.000000] [<ffffffff81660252>]
init_ohci1394_dma_on_all_controllers+0x9b/0x345
[ 0.000000] [<ffffffff8163be6b>] setup_arch+0x543/0x950
[ 0.000000] [<ffffffff813b99b6>] ? printk+0x3c/0x3e
[ 0.000000] [<ffffffff810646b6>] ?
clockevents_register_notifier+0x3e/0x48
[ 0.000000] [<ffffffff81639995>] start_kernel+0x82/0x34d
[ 0.000000] [<ffffffff816392a5>] x86_64_start_reservations+0xac/0xb0
[ 0.000000] [<ffffffff816393a1>] x86_64_start_kernel+0xf8/0x107
[ 0.000000] RIP 0x10
The system is a LFS pure64 build on an imac,macbook(both systems the
same, and both crash like this).
Any ideas on this, and also any ideas on how I could try and grab a
syslog this early in the boot?
Justin P. Mattock
next reply other threads:[~2009-10-23 23:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-23 23:45 Justin P. Mattock [this message]
2009-10-26 18:34 ` PANIC: early exception 08 rip 246:10 error ffffffff810251b5 cr2 0 Justin Mattock
2009-10-26 20:29 ` Valdis.Kletnieks
2009-10-26 21:16 ` Justin P. Mattock
2009-10-27 6:23 ` Valdis.Kletnieks
2009-10-27 18:57 ` Justin P. Mattock
2009-10-27 19:07 ` Justin P. Mattock
2009-10-27 19:35 ` Valdis.Kletnieks
2009-10-27 20:34 ` Justin P. Mattock
2009-10-28 3:56 ` Justin P. Mattock
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=4AE24009.4090408@gmail.com \
--to=justinmattock@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;
as well as URLs for NNTP newsgroup(s).