Thread View: comp.sys.next.sysadmin
2 messages
2 total messages
Started by james dehnert
Sat, 02 Jan 1993 17:49
Need help on discovering cause of kernel crashes.
Author: james dehnert
Date: Sat, 02 Jan 1993 17:49
Date: Sat, 02 Jan 1993 17:49
15 lines
1134 bytes
1134 bytes
My ususally robust 040' 3.0 system seems to be crashing at will latley. I keep getting "mach: trap:" and "mach: panic: (Cpu 0) illegal instruction" errors in /usr/adm/messages, but I dont know how to discover what is causing these errors. I have been using Mamakos SLIP lately, but I'm sure I would have seen alot of trafic on the subject if that was causing system crashes. Can anyone tell me how to trace these problems, or which FM to R? Thanks, Zeke -- +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ =+ += Eschew Obfuscation Next Mail Welcome =+ += += =+ James "Zeke" Dehnert zeke@znext.cts.com += =+ =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=
Re: Need help on discovering cause of kernel crashes.
Author: Richard Tilley
Date: Tue, 05 Jan 1993 22:42
Date: Tue, 05 Jan 1993 22:42
13 lines
1223 bytes
1223 bytes
In <1993Jan2.174935.418@znext.cts.com> zeke@znext (james dehnert) writes: > My ususally robust 040' 3.0 system seems to be crashing at will latley. I >keep getting "mach: trap:" and "mach: panic: (Cpu 0) illegal instruction" >errors in /usr/adm/messages, but I dont know how to discover what is causing >these errors. I have been using Mamakos SLIP lately, but I'm sure I would have >seen alot of trafic on the subject if that was causing system crashes. > Can anyone tell me how to trace these problems, or which FM to R? I get these if I try to start WindowServer on a headless cube. SLIP not involved. Please summarize anything you find. -- This space is not blank!
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads