lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 26 Oct 2009 11:34:20 -0700 From: Justin Mattock <justinmattock@...il.com> To: Linux Kernel <linux-kernel@...r.kernel.org> Cc: Bernhard Kaindl <bk@...e.de> Subject: Re: PANIC: early exception 08 rip 246:10 error ffffffff810251b5 cr2 0 On Fri, Oct 23, 2009 at 4:45 PM, Justin P. Mattock <justinmattock@...il.com> wrote: > 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 > > > I can't seem to locate a right mailing list for ieee1394 for Linux. Anyways here is a url to flickr which has the image of the PANIC: http://www.flickr.com/photos/44066293@N08/4046711653/ (hopefully you don't need to sign up to view) As for the problem, interesting thing here is if I add a printk to: if ((class == 0xffffffff)) printk(KERN_BUG "init_ohci1394_dma: finished initializing OHCI DMA\n"); continue; /* No device at this func */ the system will boot-up, and the PANIC will not occur. -- Justin P. Mattock -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists