Re: linux-next: Tree for July 18: warning at kernel/lockdep.c:2068 trace_hardirqs_on_caller

2008-07-20 Thread Dave Hansen
On Sun, 2008-07-20 at 01:11 +0200, Vegard Nossum wrote: Maybe the firmware memmap code can simply run a little later in the boot sequence? Heh, I'm catching up on this thread... It is possible that it could run later. But, I do know that there are at least a couple of these tables (on various

Re: linux-next: Tree for July 18: warning at kernel/lockdep.c:2068 trace_hardirqs_on_caller

2008-07-20 Thread Thomas Meyer
Am Sonntag, den 20.07.2008, 02:01 -0700 schrieb Dave Hansen: On Sun, 2008-07-20 at 01:11 +0200, Vegard Nossum wrote: Maybe the firmware memmap code can simply run a little later in the boot sequence? Heh, I'm catching up on this thread... On that thread?

Re: linux-next: Tree for July 18: warning at kernel/lockdep.c:2068 trace_hardirqs_on_caller

2008-07-20 Thread Bernhard Walle
* Dave Hansen [EMAIL PROTECTED] [2008-07-20 02:01]: It is possible that it could run later. But, I do know that there are at least a couple of these tables (on various arches) that we toss out of memory or become unavailable later in boot. I do this this: sysfs: add

Re: linux-next: Tree for July 18: warning at kernel/lockdep.c:2068 trace_hardirqs_on_caller

2008-07-20 Thread Bernhard Walle
* Bernhard Walle [EMAIL PROTECTED] [2008-07-20 15:03]: Because I didn't know that interface. And because I don't see that interface on my two systems that I just checked. i386 and x86-64. What do I have to do to enable that interface? That interface depends on CONFIG_MEMORY_HOTPLUG. But