Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uunet!snorkelwacker!usc!cs.utexas.edu!romp!auschs!awdprime!mathew.austin.ibm.com!matt From: matt@mathew.austin.ibm.com (Mathew Accapadi;3-3517) Newsgroups: comp.unix.aix Subject: Re: Illegal trap instruction interrupt in kernel Message-ID: <3597@awdprime.UUCP> Date: 20 Sep 90 16:00:40 GMT References: Sender: news@awdprime.UUCP Reply-To: matt@reed.UUCP (Mathew Accapadi) Distribution: usa Organization: IBM AWD, Austin, TX Lines: 27 In article csjoey@knuth.MTSU.EDU (mr. joey carruthers) writes: >Maybe someone out there can help me with this problem on the RS/6000. >It occurs mostly at shutdown, or when I have to do a kill on a Smit that >has gotten hung. > The system will go dead, except for the console, which appears to have >a debugging screen. At the top of the screen, I get 4 lines which start >with GPR0, GPR8, GPR16, and GPR24. These GPR numbers are followed by >codes, and the GPR16 has 2 setc of code reading 'DEADBEEF'. >three machines). There is a message at the bottom of the screen saying >"Illegal trap instruction interrupt in kernel", followd by a prompt. > > Has anyone else seen this happen? What causes it, and is there a cure? The best thing to do is to have an IBM SE look at this and take a stack trace to determine what component is causing the problem. Also, they can record the address of the instruction so as to determine the offset into the code that 'asserted'. Another thing you can do is type in "quit dump" instead of just "quit". This will force a dump to your primary dump device which you can then hand over to your IBM rep. Regards, Matt ------------------------------------------------------------------------- Mathew Accapadi ...cs.utexas.edu!ibmaus!auschs!mathew.austin.ibm.com!matt 512-823-3517 Tie Line 793-3517 -------------------------------------------------------------------------