ia64/xen-unstable

changeset 9285:e3e4c8b564e2

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>
author kaf24@firebug.cl.cam.ac.uk
date Wed Mar 15 11:07:26 2006 +0100 (2006-03-15)
parents 5618b13ac97f
children 06e3c5ef2979
files xen/drivers/char/console.c
line diff
     1.1 --- a/xen/drivers/char/console.c	Wed Mar 15 11:06:45 2006 +0100
     1.2 +++ b/xen/drivers/char/console.c	Wed Mar 15 11:07:26 2006 +0100
     1.3 @@ -683,8 +683,6 @@ void panic(const char *fmt, ...)
     1.4      (void)vsnprintf(buf, sizeof(buf), fmt, args);
     1.5      va_end(args);
     1.6  
     1.7 -    debugger_trap_immediate();
     1.8 -
     1.9      /* Spit out multiline message in one go. */
    1.10      spin_lock_irqsave(&lock, flags);
    1.11      printk("\n****************************************\n");
    1.12 @@ -694,6 +692,8 @@ void panic(const char *fmt, ...)
    1.13      printk("Reboot in five seconds...\n");
    1.14      spin_unlock_irqrestore(&lock, flags);
    1.15  
    1.16 +    debugger_trap_immediate();
    1.17 +
    1.18      watchdog_disable();
    1.19      mdelay(5000);
    1.20      machine_restart(0);