Path: utzoo!utgpu!water!watmath!clyde!att!pacbell!ames!pasteur!agate!ig!uwmcsd1!dogie!uwvax!geowhiz!uwspan!root
From: root@uwspan.UUCP (Sue Peru Sr.)
Newsgroups: comp.unix.microport
Subject: --- A System V/AT crash ---
Message-ID: <3840@uwspan.UUCP>
Date: 22 May 88 00:19:33 GMT
References: <445@zap.UUCP>
Reply-To: root@uwspan.UUCP (Sue Peru Sr.)
Followup-To: comp.unix.microport
Organization: U of Wisconsin - Madison  Spanish Department
Lines: 31

+---- fortin@zap.UUCP (Denis Fortin) writes in <445@zap.UUCP> ----
| After running for a while (anywhere between 5 minutes and an hour), I seem
| to get the a crash dump very similar to the following fairly consistently.
| 
| 	cs=0x200 ds=0x220 es=0x220 ss=0x200 di=0x0 si=0x5BE0
| 	bp=0x37C bx=0x0 dx=0xA1 cx=0x0 ax=0x7 ip=0xEAF flags=0x246
| 	trap type 0xD
| 
| So...  I did what was suggested, and according to `nm -x /system5`, the
| closest thing to 02000eaf is 02000ea6, and that is "clkint1" in "trap.s".
| 
| Does this give you net.gurus any idea what might be wrong?  

  Not me, but I'll pass it along...

| PS. How does one go about looking at the code around "clkint1" in the
|     kernel?  sdb?  crash?  adb isn't there...

  I haven't tried - it's enuf for me to pass the info on to Microport.

| PPS. Is there any way to force a "crash dump" that might be investigated
|      with "crash" afterwards?

  Nope - this is a major gripe of mine...

| Denis Fortin
| fortin@zap.uucp

  -John
-- 
Comp.Unix.Microport is now unmoderated!  Use at your own risk :-)