From: Kenneth Johansson <kenneth.johansson@etx.ericsson.se>
To: Brian Kuschak <bkuschak@yahoo.com>
Cc: "linuxppc-embedded@lists.linuxppc.org"
<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: 4xx critical exceptions
Date: 06 Dec 2002 10:22:33 +0100 [thread overview]
Message-ID: <1039166553.24797.44.camel@spawn> (raw)
In-Reply-To: <20021204230047.98430.qmail@web40912.mail.yahoo.com>
On Thu, 2002-12-05 at 00:00, Brian Kuschak wrote:
>
> I'm interested in using the watchdog interrupt as a
> critical exception. I have somthing that sort-of
> works, in that I get wdt interrupts and service them
> appropriately, but I'm getting panics on a regular
> basis.
I thought this was strange as I had seen a watchdog driver in the kernel
for 405 but after reading the source of said driver I no longer think
that:(
I have not tried the driver but from the look of it I would say it's not
doing anything useful.
> I'm guessing we don't have any unused SPRGx registers
> to use here. I was thinking about temporarily
> disabling CE until saving SPRG0,1, but that can't be
> done without using at least one register, and none of
> them are saved at that point.
>
> Any ideas?
Not really. Do you want to try to set up a c environment or do you plan
on just doing the thing in asm directly? The code in the exception
handler do not have to do much something like
if(wdt_count++ < max_wdt_loops)
clear_wdt_ENW();
return
should do. Then if userspace or whatever it is that kicks the dog has
not reset the wdt_count we let the hardware just do the reset.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2002-12-06 9:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-04 23:00 4xx critical exceptions Brian Kuschak
2002-12-05 0:11 ` Matt Porter
2002-12-06 9:22 ` Kenneth Johansson [this message]
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=1039166553.24797.44.camel@spawn \
--to=kenneth.johansson@etx.ericsson.se \
--cc=bkuschak@yahoo.com \
--cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).