Crash!

From: Cyndi Smith <cyn_at_odin.mdacc.tmc.edu>
Date: Wed, 08 Mar 2000 16:08:37 -0600 (CST)

Help!

Our 4100 5/400 crashed this afternoon. All day (up to the crash), it was intermittantly
slow -- to the point where it might be 30 seconds for it to echo your keystrokes.
Since all access to this machine is generally remote, I ran netstat -id and all looked
normal. I also looked at the load and it was, if anything, low.
So, I chalked it up to our intermittant network glitches and didn't worry too much.
Then came the crash....
>From what I can tell from the crash logs (and I am far from an expert on these things),
the crash was caused by
      _panic_string: 0xfffffc00005b5e50 = "simple_lock: time limit exceeded"
The current PID is shown as:
      l3 address 0xffffffffffffffd8 not mapped, pte 0x0
which is frequently repeated in other places in the log as well...

About a week ago, we had a crash that seemed to be caused by
      _panic_string: 0xfffffc0000590898 = "pmap_begin_shared_region timeout"
and I was able to track down the PID and find the program that caused it.

Any clues or ideas as to how I might proceed.

The only change I can think of in the system recently is that I installed ssh2
yesterday.

Thanks for any help.

-- 
-Cyndi Smith			     Programmer Analyst III, Biomathematics
-cyn_at_odin.mdacc.tmc.edu		M.D. Anderson Cancer Center, Houston, Texas
-phone: (713) 794-4938					fax: (713) 792-4262
			<http://odin.mdacc.tmc.edu/~cyn>
Received on Wed Mar 08 2000 - 22:09:32 NZDT

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:40 NZDT