Debugging an oops

David Woodhouse dwmw2 at infradead.org
Tue Nov 21 11:50:46 EST 2000



mark.langsdorf at amd.com said:
>  The EIP  shows that the oops is occurring in my version of write32,
> called from vsprintf(?) and cfi_amdext_write_bytes_32,

> Aiee, killing interrupt handler
> Scheduling in interrupt

Does your map write32 function schedule? Try to obtain a semaphore?

--
dwmw2




To unsubscribe, send "unsubscribe mtd" to majordomo at infradead.org



More information about the linux-mtd mailing list