Messages in this thread | | | Date | Thu, 14 Feb 2013 18:28:26 +0100 (CET) | From | Thomas Gleixner <> | Subject | Re: [-rc7 regression] Block IO/VFS/ext3/timer spinlock lockup? |
| |
On Thu, 14 Feb 2013, Ingo Molnar wrote: > * Ingo Molnar <mingo@kernel.org> wrote: > > > > CPU0 appears to be idle: > > > > > > [ 118.510000] Call Trace: > > > [ 118.510000] [<7900844b>] cpu_idle+0x86/0xb4 > > > [ 118.510000] [<792a91df>] rest_init+0x103/0x108 > > > [ 118.510000] [<794558cc>] start_kernel+0x2c7/0x2cc
Weird.
> > So, I've done a partial bisection, the breakage appears to have > > gone upstream between v3.8-rc3 and v3.8-rc4. > > these three: > > 10d73e655cef mm: bootmem: fix free_all_bootmem_core() with odd bitmap alignment > c060f943d092 mm: use aligned zone start for pfn_to_bitidx calculation > c0232ae861df mm: memblock: fix wrong memmove size in memblock_merge_regions() > > might have highmem=512m boot parameter sensitivity.
Is highmem=512 the boot parameter which makes it come and go ?
Thanks,
tglx
| |