On Sunday 12 January 2003 01:02, Charles Manning wrote: > This looks to me like it is happeing in the NAND mtd. I don't think so. The stacktrace is not really useful. And it seams to be inconsistent. > Trace; c00c4d54 > Trace; c00c6e8c nand_trans_result is called from nand_calculate_ecc, which is called from nand_write_page. So the order in stack is reversed here. What are the OUT_OF_CODE entries. Do you have modules loaded ? Bug in slab.c 1112 seams to be the following: /* * The test for missing atomic flag is performed here, rather than * the more obvious place, simply to reduce the critical path length * in kmem_cache_alloc(). If a caller is seriously mis-behaving they * will eventually be caught here (where it matters). */ if (in_interrupt() && (flags & SLAB_LEVEL_MASK) != SLAB_ATOMIC) BUG(); That's not a nand issue. What version of MTD code do you use ? Latest MTD-CVS or old stuff ? Make sure to use latest MTD-CVS. -- Thomas ________________________________________________________________________ linutronix - competence in embedded & realtime linux http://www.linutronix.de mail: tglx@linutronix.de --------------------------------------------------------------------------------------- This mailing list is hosted by Toby Churchill open software (www.toby-churchill.org). If mailing list membership is no longer wanted you can remove yourself from the list by sending an email to yaffs-request@toby-churchill.org with the text "unsubscribe" (without the quotes) as the subject.