Hello, I wrote:
>>I guess there may be more of these gotchas, but my patch places
>>protections against the cases I've seen. Thanks for taking a look.
> Yeah, there are more... :-)
> Consider KGDBoE specific one where the networking drivers usually call
> disable_irq() in their poll_controller() methods: for example, if you happen
> to set a breakpoint into an interrupt handler for a device sharing an IRQ
> with
> the device you're using for KGDBoE, you're going to get a lockup since KGDB
> stops all CPUs and that interrupt's handling will never complete...
Well, shared interrupts are not the only danger: another CPU may actually
be servicing this driver's own interrupts...
> And in RT
> kernel, you'll additionally get a loong stack trace as a bonus. :-)
That's what we're actually getting, even in non-RT mode, just with
threaded hardirqs...
>>Tim Nguyen
WBR, Sergei
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Kgdb-bugreport mailing list
Kgdb-bugreport@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kgdb-bugreport
