On Fri, Apr 02, 2010 at 11:51:33AM +0800, TAO HU wrote: > On Thu, Apr 1, 2010 at 12:05 PM, TAO HU <tghk48@xxxxxxxxxxxx> wrote: > > We got a panic on our ARM (OMAP) based HW. > > Our code is based on 2.6.29 kernel (last commit for mm/page_alloc.c is > > cc2559bccc72767cb446f79b071d96c30c26439b) > > > > It appears to crash while going through pcp->list in > > buffered_rmqueue() of mm/page_alloc.c after checking vmlinux. > > "00100100" implies LIST_POISON1 that suggests a race condition between > > list_add() and list_del() in my personal view. > > However we not yet figure out locking problem regarding page.lru. I'm sure this is just a memory corruption which is unrelated to code in the the memory management area. The code there just happens to trigger it as it is called frequently and is very sensitive to bogus data Did you see the other thread I started off yesterday? http://lkml.indiana.edu/hypermail/linux/kernel/1004.0/00157.html We could well see the same problem here. Not sure though as any kind of memory corruption ends up in Ooopses like the ones you see, but it could be a hint. Daniel -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxxx For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>