> On Mon, Feb 20, 2012 at 11:11:05AM +0200, Meelis Roos wrote: > > Finished bisecting on the other machine too (Sun Fire V100 where strlen > > crashes): > > > > 7bd0b0f0da3b1ec11cbcc798eb0ef747a1184077 is the first bad commit > > commit 7bd0b0f0da3b1ec11cbcc798eb0ef747a1184077 > > Author: Tejun Heo <tj@xxxxxxxxxx> > > Date: Thu Dec 8 10:22:09 2011 -0800 > > > > memblock: Reimplement memblock allocation using reverse free area iterator > > > > Now that all early memory information is in memblock when enabled, we > > can implement reverse free area iterator and use it to implement NUMA > > aware allocator which is then wrapped for simpler variants instead of > > the confusing and inefficient mending of information in separate NUMA > > aware allocator. > > > > Implement for_each_free_mem_range_reverse(), use it to reimplement > > memblock_find_in_range_node() which in turn is used by all allocators. > > > > The visible allocator interface is inconsistent and can probably use > > some cleanup too. > > > > Signed-off-by: Tejun Heo <tj@xxxxxxxxxx> > > Cc: Benjamin Herrenschmidt <benh@xxxxxxxxxxxxxxxxxxx> > > Cc: Yinghai Lu <yinghai@xxxxxxxxxx> > > Hmmm.... So, different bisection results from two machines? That's a > bit weird. I *think* this bisection result makes more sense. Can you > please verify the bisection result on e2500 once more? You were right. The first machine now bisects down to the same commit - I was confused by "0 revisions to test" and did not run the last step whe first bisecting. -- Meelis Roos (mroos@xxxxxxxx) -- To unsubscribe from this list: send the line "unsubscribe sparclinux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
