[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <4B6A9960020000780002DA6B@vpn.id2.novell.com>
Date: Thu, 04 Feb 2010 08:54:40 +0000
From: "Jan Beulich" <JBeulich@...ell.com>
To: "Justin P. Mattock" <justinmattock@...il.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)
>>> "Justin P. Mattock" <justinmattock@...il.com> 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
--
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