[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4B6A97ED.6080605@gmail.com>
Date: Thu, 04 Feb 2010 01:48:29 -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:35, Jan Beulich wrote:
>>>> "Justin P. Mattock"<justinmattock@...il.com> 04.02.10 10:17>>>
>> 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?
>
> No, afaict it is the ohci1394_dma=early code itself hitting that path.
>
> Jan
>
>
alright.. looking at init_ohci1394_dma.c
I see:
ohci.registers = (void *)fix_to_virt(FIX_OHCI1394_BASE);
then I think it calls:
set_fixmap_nocache(FIX_OHCI1394_BASE, ohci_base);
I'm guessing somewhere with the fix_to_virt might be something
(but could be wrong);
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