I've found it useful to display the panic message *before* dropping into the

debugger. Once there it may be very difficult to find the original message, 
and often a debugger isn't even needed if you can see what panicked.

Signed-off-by: Hollis Blanchard <hollisb@us.ibm.com>
This commit is contained in:
kaf24@firebug.cl.cam.ac.uk committed 2006-03-15 11:07:26 +01:00
1 parent 72e3f22324
commit 2c8dbad938
1 file changed
+2 -2
+2 -2
View File
@@ -683,8 +683,6 @@ void panic(const char *fmt, ...)
(void)vsnprintf(buf, sizeof(buf), fmt, args);
va_end(args);
debugger_trap_immediate();
/* Spit out multiline message in one go. */
spin_lock_irqsave(&lock, flags);
printk("\n****************************************\n");
@@ -694,6 +692,8 @@ void panic(const char *fmt, ...)
printk("Reboot in five seconds...\n");
spin_unlock_irqrestore(&lock, flags);
debugger_trap_immediate();
watchdog_disable();
mdelay(5000);
machine_restart(0);
Reference in new issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.