From: Steven Bytnar <sbytnar@users.sourceforge.net>
To: linuxppc-dev@lists.linuxppc.org
Subject: Pseudo Oops for ppc
Date: Sat, 19 Aug 2000 20:39:31 -0500 [thread overview]
Message-ID: <20000819203931.A15224@openprojects.rarcoa.com> (raw)
http://www.stg.com/udi/ppc-oops-1.patch
This simple patch improves the default panic backtraceing
by walking the kernel symbol table to find function names.
It also attempts to kill and cleanup the task that caused
the panic by calling do_exit(SIGKILL). This seems to work
most of the time and leaves the machine in a mostly
usable state, although you should probably reboot soon
thereafter.
The end result... you can panic the machine and keep
working after waiting about 10 seconds. (So you can see
the panic message.)
You will want to tune the delay loop value. Why is there a
delay loop?! I didn't feel like figuring out how to read the
USB keyboard driver.
This patch isn't very useful if you have kgdb or xmon
enabled. Hopefully someone will find this useful. It's
been a time saver for me while I've been working on
developing kernel modules on a G4.
Enjoy,
--Steve
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
reply other threads:[~2000-08-20 1:39 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=20000819203931.A15224@openprojects.rarcoa.com \
--to=sbytnar@users.sourceforge.net \
--cc=linuxppc-dev@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).