08-23-2004
We'd need to see the whole message to be sure, but usually when you get that kind of random panic it is due to uncorrectable memory errors, or CPU errors. In either case the solution probably involves getting the failed hardware replaced. If you have Sun support it is time to get a trouble ticket started so they can analyze it for you.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi All,
When I came officce this morning I saw this error messages on the screen
-----
PANIC:srmountfun - Error 6 mounting rootdev hd (1/42)
Cannot dump 32639 pages to dumpdev hd (1/41) : space for only 0 pages
Dump not completed
--------
and machine was reboot mode. Why this problem... (3 Replies)
Discussion started by: alisev
3 Replies
2. SCO
Hi Friends ,
i am getting the following error when iam booting a sco unix system.
------------------
H init
PANIC : srmountfun --Error 22 mounting rootdev hd(1/42)
cannot dump 40863 pages to dempdev hd(1/41) : space for only 0 pages.
Dump not completed.
Safe to power off.... (1 Reply)
Discussion started by: sveera
1 Replies
3. UNIX for Advanced & Expert Users
One of our servers keeps crashing.
Here is the following message that we get:
11:01 Thu Aug 31 2006. Reboot after panic: fcpbh_scsi_comp: Inbound data overf
low
12:28 Wed Sep 6, 2006. Reboot:
16:12 Wed Sep 06 2006. Reboot after panic: , isr.ior = 0'10240070.0'dcf72938
Does anyone... (1 Reply)
Discussion started by: shoultsc
1 Replies
4. Solaris
Hi Guru's
Can any want here could explain to me the different between soft reboot and hard reboot .
Best Regards
Seelan (3 Replies)
Discussion started by: seelan3
3 Replies
5. HP-UX
Hi all,
Does anybody know what kinds of events can prompt the following?
I found our test db box had rebooted itself. I'd like to know how I can go about finding our why. Thanks folks... (1 Reply)
Discussion started by: Kozmo
1 Replies
6. Red Hat
Could you please help with problem with megaraid controller and Dell PowerEdge 2850, all that I can see on thi screenshot:
All drives successfuly passed verifing from LSI controllers (Ctrl+A at startup), also I tried to boot from rescue llive cd and mount all the morrored drives and check... (22 Replies)
Discussion started by: nikkadim
22 Replies
7. Solaris
Hi all,
solaris 10 system crashed, /var/adm/messages file:
panic/thread=3003ccaa060:
unix: mutex_exit: not owner, lp=60057340d28
owner=deadbeefdeadbee8 thread=3003ccaa06
0
unix:
genunix: 000002a10c4b1a00 sockfs:accept+1a8 (0, 3, 83,
5f03, 8c, 5c00)
genunix: %l0-3:... (1 Reply)
Discussion started by: Mehmet_Karaca
1 Replies
8. Solaris
Hi All,
I am getting the below error after login to box.
SunOS Release 5.10 Version Generic_147440-02 64-bit
Copyright (c) 1983, 2011, Oracle and/or its affiliates. All rights reserved.
os-io Cross trap sync timeout: at cpu_sync.xword: 0x1010panic: failed to sto
p cpu8
panic: failed to... (1 Reply)
Discussion started by: chetansingh23
1 Replies
9. UNIX for Dummies Questions & Answers
Hi all,
I am running SCO6 in a VMWare environment. For the past two Sunday's during the system's automatic reboot I have received a Panic and the system has locked up. I have had to power off the VM and back on. I have never run into this sort of thing. Can someone help direct me to where... (1 Reply)
Discussion started by: Carlitos71
1 Replies
10. SCO
Hello
when i booting my SCO Server I become this Message
PLS can anyone help me?
Cheers
Christoph (1 Reply)
Discussion started by: cga
1 Replies
crash(8v) crash(8v)
Name
crash - what happens when the system crashes
Description
This section explains what happens when the system crashes and shows how to analyze crash dumps.
When the system crashes voluntarily it prints a message on the console in the form:
panic: explanation
The system takes a dump on a mass storage peripheral device or the network, and then invokes an automatic reboot procedure as described in
Unless there is some unexpected inconsistency in the state of the file systems due to hardware or software failure, the system then resumes
multi-user operations. If auto-reboot is disabled, the system halts at this point.
The system has a large number of internal consistency checks; if one of these fails, it prints a short message indicating which one failed.
The most common cause of system failures is hardware failure. In all cases there is the possibility that hardware or software error pro-
duced the message in some unexpected way. These messages are the ones you are likely to encounter:
IO err in push
hard IO err in swap
The system encountered an error when trying to write to the paging device or an error in reading critical information from a disk
drive. Fix your disk if it is broken or unreliable.
timeout table overflow
Due to the current data structure, running out of entries causes a crash. If this happens, make the timeout table bigger.
Exception Condition
An unexpected system error has occurred. The exception types are as follows:
---------------------------------------------------------------
Mnemonic Description
---------------------------------------------------------------
INT External interrupt
MOD TLB modification exception
TLBL TLB miss exception (load or instruction fetch)
TLBS TLB miss exception (store)
AdEL Address error exception (load or instruction fetch)
AdES Address error exception (store)
IBE Bus error exception (for an instruction fetch)
DBE Bus error exception (for a data load or store)
Sys Sys call exception
Bp Breakpoint exception
CpU Coprocessor unusable exception
Ovf Arithmetic overflow exception
---------------------------------------------------------------
KSP not valid
This indicates either a problem in the system or failing hardware.
init died
The system initialization process has exited. The only solution is the automatic reboot procedure described in Until this is done,
new users cannot log in.
When the system crashes, it attempts to write an image of memory into the back end of the primary swap area. After the system is rebooted,
the program runs and preserves a copy of this core image and the current system in a specified directory for later access. See for
details.
To analyze a dump, you should begin by running with the flag on the core dump.
See Also
dbx(1), reboot(8), savecore(8)
RISC crash(8v)