From: Dave Jiang <djiang@mvista.com>
To: galak@kernel.crashing.org
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org
Subject: [PATCH/RFC 1/2] powerpc: BOOKE watchdog handler dump additional info
Date: Tue, 29 May 2007 17:53:36 -0700 [thread overview]
Message-ID: <20070530005336.GA8239@blade.az.mvista.com> (raw)
Have the watchdog handler to call die(). This allows some system information
such as registers, stack dump, and etc to be displayed. The die() handler
should handle the situation appropriately (i.e. kill process, call panic,
or call crash_kexec)
The follow on patch will address any issues in regards to watchdog following the
call of panic.
We have to keep the watchdog interrupt enabled because die() can just kill a
process and return the system to a running state instead of panic().
This will allow us to catch any new watchdog timeout exceptions if the system
hangs again.
Signed-off-by: Dave Jiang <djiang@mvista.com>
---
traps.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/arch/powerpc/kernel/traps.c b/arch/powerpc/kernel/traps.c
index bf6445a..837f742 100644
--- a/arch/powerpc/kernel/traps.c
+++ b/arch/powerpc/kernel/traps.c
@@ -1095,8 +1095,7 @@ void unrecoverable_exception(struct pt_regs *regs)
void __attribute__ ((weak)) WatchdogHandler(struct pt_regs *regs)
{
/* Generic WatchdogHandler, implement your own */
- mtspr(SPRN_TCR, mfspr(SPRN_TCR)&(~TCR_WIE));
- return;
+ die("PowerPC Book-E Watchdog Exception", regs, SIGSEGV);
}
void WatchdogException(struct pt_regs *regs)
reply other threads:[~2007-05-30 0:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070530005336.GA8239@blade.az.mvista.com \
--to=djiang@mvista.com \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox