[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4B6A90BB.7090405@gmail.com>
Date: Thu, 04 Feb 2010 01:17:47 -0800
From: "Justin P. Mattock" <justinmattock@...il.com>
To: Jan Beulich <JBeulich@...ell.com>
CC: Ingo Molnar <mingo@...e.hu>, Dan Carpenter <error27@...il.com>,
bernhard.kaindl@....net, Thomas Gleixner <tglx@...utronix.de>,
linux1394-devel@...ts.sourceforge.net,
Stefan Richter <stefanr@...6.in-berlin.de>,
Rafael Wysocki <rjw@...k.pl>,
Kernel Testers List <kernel-testers@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
ebiderman@...ssion.com, hpa@...or.com
Subject: Re: ohci1394_dma=early crash since 2.6.32 (was Re: [Bug #14487]
PANIC: early exception 08 rip 246:10 error ffffffff810251b5 cr2 0)
On 02/04/10 01:11, Jan Beulich wrote:
>>>> "Justin P. Mattock"<justinmattock@...il.com> 04.02.10 10:04>>>
>> a quick google on this showed somewhere
>> at bootmem.c any ideas on this or where
>> this might be caused besides fixmap?
>> (or is fixmap the main location?);
>
> __native_set_fixmap() -> set_pte_vaddr() -> set_pte_vaddr_pud() ->
> fill_pte() -> spp_getpage() -> alloc_bootmem_pages() -> panic().
>
> Jan
>
>
so something is using __native_set_fixmap
that's hitting some memory address then
set_fixmap_nocache(ohci1394_dma=early)
fires off hitting the same?
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