Nick Piggin wrote:
I can't really work it out. It seems to be the kmem_cache_cache which has a problem, but there have already been lots of caches created and even this samw cache_node already used right beforehand with no problem. Unless a CPU or node comes up or something right at this point or the caller is scheduled onto a different CPU... oopses seem to all have CPU#1, wheras boot CPU is probably #0 (these CPUs are node 0 and memory is only on node 1 and 2 where there are no CPUs if I read correctly). I still can't see the reason for the failure, but can you try this patch please and show dmesg?
I was able to boot yesterday's next (20090611) on this machine. Not sure what changed(may be because of merge with linus tree), but i can no longer recreate this issue with next 20090611. I was consistently able to recreate the problem till June 10th next tree. Thanks -Sachin -- --------------------------------- Sachin Sant IBM Linux Technology Center India Systems and Technology Labs Bangalore, India --------------------------------- -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
