![]() | |||||||||||||
Messages in this thread |
Andi Kleen wrote: > On Tue, Mar 02, 2004 at 01:27:51PM -0800, Andrew Morton wrote: > >>George Anzinger <george@mvista.com> wrote: >> >>> Often it is not clear just why we are in the stub, given that >>>we trap such things as kernel page faults, NMI watchdog, BUG macros and such. >> >>Yes, that can be confusing. A little printk on the console prior to >>entering the debugger would be nice. > > > What I did for kdb and panic some time ago was to flash the keyboard > lights. If you use a unique frequency (different from kdb > and from panic) it works quite nicely. Assuming a key board and a clear (no spin locks) path to it. Still it only says we are in kgdb, now why. -- George Anzinger george@mvista.com High-res-timers: http://sourceforge.net/projects/high-res-timers/ Preemption patch: http://www.kernel.org/pub/linux/kernel/people/rml - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||||
| Last update: 2005-03-22 13:01 [from the cache] ©2003-2008 | |||||||||||||