home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!ames!agate!cogsci.Berkeley.EDU!ag
- From: ag@cogsci.Berkeley.EDU (Keith Gabryelski)
- Newsgroups: comp.unix.amiga
- Subject: What to do when you get a panic.
- Message-ID: <16q0p0INNkm@agate.berkeley.edu>
- Date: 18 Aug 92 05:10:56 GMT
- References: <1992Aug17.213613.28703@nntpd.lkg.dec.com>
- Organization: Institute of Cognitive Studies, U.C. Berkeley
- Lines: 38
- NNTP-Posting-Host: cogsci.berkeley.edu
-
- In article <1992Aug17.213613.28703@nntpd.lkg.dec.com> barrett@pamsrc.enet.dec.com writes:
- >You could do what I do. Add a crontab entry that reboots your system
- >every night at 3am. Since I added that, I see a panic perhaps once
- >a month now rather than once a week.
-
- Or you could write down the panic message (the middle of the three
- column list is the most important part) along with the line
- containing the `pc' address and send it to the net.
-
- At least then you have a chance of getting the problem fixed.
-
- To increase your chances of getting a response you can:
-
- mention any modifications you have made to the machine
- and your current configuration.
-
- write down what you were doing at the time.
-
- Instead of sending just the center column of numbers
- you could send the output of:
-
- sed 's:$:/i:' LISTONUMBERS | adb -k
-
- Where LISTONUMBERS is a file containing one address
- per line from the center column of the panic backtrace.
- (This will create a symbolic backtrace which will
- allow the observer to tell immediately if this is
- a well known panic or not).
-
- Send Hersey's Peanut Butter Cups or Bass Ale
- with your request.
-
- Pax, Keith
-
- Ps, For the backtrace officionado: you needn't copy down the first
- five lines of the backtrace. They are usually the call to `k_trap'
- and `panic' itself. You will note this after looking at the output
- from the sed line above from several backtraces.
-