No, CONFIG_4KSTACKS is not enabled.
That shouldn't happen. Are you enabling CONFIG_4KSTACKS?
Does it repeat if you disable preempt? It'd be useful to know what CONFIG_DEBUG_STACKOVERFLOW says, too.
That chunk of code was just dropping the lock, doing preempt processing, then accessing the stack. Preempt should have been a NOP given that the code holds ehci->lock and IRQs are blocked. And even if it weren't, it's not supposed to be able to break the stack. But maybe because of some other bug, it wasn't; something sure seemed to be corrupting stack state, and just now I can't quite see that being USB.
- Dave
------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
