Re: [-rc7 regression] Block IO/VFS/ext3/timer spinlock lockup?

[Ingo Molnar]

* Ingo Molnar <mingo@xxxxxxxxxx> 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
> 
> 
> So, I've done a partial bisection, the breakage appears to have 
> gone upstream between v3.8-rc3 and v3.8-rc4.
> 
> This roughly coincides with the time frame when I first saw 
> these lockups pop up, so in that sense it's a plausible result - 
> but there weren't all that many commits in -rc4 and none looks 
> really suspicious, so this might be one of those non-bisectable 
> bugs.
> 
> ( Later today I'll try to finish the bisection just in case it
>   results in something useful. )

Managed to squeeze in some more bisection steps - and in fact 
the mm/ changes in -rc4 are still included in the bisection 
window:

 git bisect bad 7c8284c3aa127ffe72a90a1bad52183ec9ad870a
 git bisect good 0a1af1d61edae189b0a81bc46386ab37eb3d9d4d

vega:~/linux/linux> gll 0a1af1..7c8284c3a mm/
8fb74b9fb2b1 mm: compaction: partially revert capture of suitable high-order page
062f1af2170a mm: thp: acquire the anon_vma rwsem for write during split
572043c90db6 mm: mmap: annotate vm_lock_anon_vma locking properly for lockdep
10d73e655cef mm: bootmem: fix free_all_bootmem_core() with odd bitmap alignment
c060f943d092 mm: use aligned zone start for pfn_to_bitidx calculation
7964c06d66c7 mm: compaction: fix echo 1 > compact_memory return error issue
c0232ae861df mm: memblock: fix wrong memmove size in memblock_merge_regions()
04fa5d6a6547 mm: migrate: check page_count of THP before migrating

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.

Thanks,

	Ingo
--
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/