Re: ohci1394_dma=early crash since 2.6.32 (was Re: [Bug #14487]PANIC: early exception 08 rip 246:10 error ffffffff810251b5 cr2 0)

[Justin P. Mattock]

On 02/04/10 00:54, Jan Beulich wrote:
> > > > "Justin P. Mattock"<justinmattock@xxxxxxxxx>  04.02.10 00:05>>>
> > [   0.000000] 0100000000 - 0140000000 page 2M
> > [   0.000000] kernel direct mapping tables up to 140000000 @ b000-11000
> > [   0.000000] init_ohci1394_dma: initializing OHCI-1394 at 05:00.0
> > [   0.000000] bootmem alloc of 4096 bytes failed!
> > [   0.000000] Kernel panic - not syncing: Out of memory
> > [   0.000000] Pid: 0, comm: swapper Not tainted
> > 2.6.33-rc6-00072-gab65832 # 39
> > [   0.000000] Call Trace:
> >
> > then the rest shown on the picture on the bug report.
> >
> > Out of memory?
>
> bootmem allocation before bootmem was even initialized. And that's
> likely because the code tries to populate the pmd that (due to the
> issue explained yesterday) isn't statically initialized.
>
> Jan

I'll have a look at this in the morning(late over here),
but one thing I'm seeing is the device numbers:
the error shows 05:00.0 while on a good go
of this I saw the address at **3** something(can grab
the info later for you).

which probably goes to what you are saying:
tries to populate the pmd

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?);


Justin P. Mattock
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/