kdb
[Top] [All Lists]

Re: [PATCH] fix KDB backtrace for ppc64

To: Haren Myneni <hbabu@xxxxxxxxxx>
Subject: Re: [PATCH] fix KDB backtrace for ppc64
From: Keith Owens <kaos@xxxxxxx>
Date: Thu, 06 May 2004 08:50:46 +1000
Cc: linas@xxxxxxxxxxxxxx, Ananth N Mavinakayanahalli <ananth@xxxxxxxxxx>, anton@xxxxxxxxx, kdb@xxxxxxxxxxx, linuxppc64-dev@xxxxxxxxxxxxxxxxxx
In-reply-to: Your message of "Wed, 05 May 2004 12:54:59 MST." <OF24594023.A02888C3-ON87256E8B.006CFF4F-88256E8B.006D6B8F@us.ibm.com>
Sender: kdb-bounce@xxxxxxxxxxx
On Wed, 5 May 2004 12:54:59 -0700, 
Haren Myneni <hbabu@xxxxxxxxxx> wrote:
>regs will be NULL if we use sysrq-trigger to invoke SysRq key. Noticed on 
>LKCD, but not sure whether it could apply on KDB.
>Example: echo 'd' > /proc/sysrq-trigger.

IA64 SN2 console had the same problem, not running in the interrupt
handler so no registers.  drivers/char/sn_serial.c uses KDB_ENTER() to
get registers.


#ifdef CONFIG_KDB
                if (kdb_on) {
                        if (ch == *kdb_serial_ptr) {
                                if (!(*++kdb_serial_ptr)) {
                                        spin_unlock_irqrestore(&sn_sal_lock, 
*flags);
                                        if (!regs)
                                                KDB_ENTER();    /* to get some 
registers */
                                        else
                                                kdb(KDB_REASON_KEYBOARD, 0, 
regs);
                                        kdb_serial_ptr = (char *)kdb_serial_str;
                                        spin_lock_irqsave(&sn_sal_lock, *flags);
                                        break;
                                }
                        }
                        else
                                kdb_serial_ptr = (char *)kdb_serial_str;
                }
#endif /* CONFIG_KDB */

---------------------------
Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe.
<Prev in Thread] Current Thread [Next in Thread>