Sponsored Content
Full Discussion: Panic error
Operating Systems Solaris Panic error Post 302563441 by vmcore on Tuesday 11th of October 2011 12:39:55 PM
Old 10-11-2011
Hello there. Panic like this CAN be hardware issue but not always. You did not mention what hardware family this server is, so I would recommend 1st to make sure your firmware is LATEST. Once you have confirmed firmware at highest level, check FMA logs for any CPU issues. Output from: fmdump -eV can be very helpful, narrow it down to date of this panic.

Also, was this 1st panic of this type since upgrading to 147440-02 kernel? If so, you will need to make sure your ILOM/ALOM firmware is also at latest, not close to, but latest.

Can you post panic stack from messages? Few lines before panic, and if possible full stack?

---------- Post updated at 12:39 PM ---------- Previous update was at 08:30 AM ----------

You can reference following Oracle document:

1365975.1

It affects all sun4v systems with 147440-02 / 03
T 1/2/5 xxx

Last edited by vmcore; 10-11-2011 at 09:40 AM..
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Panic

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. UNIX for Advanced & Expert Users

PANIC Error

Hi I have a compaq server and the raid controller has crashed it was a Smart Array 3200 and was replaced with a Samrt Array 5300. The problem I have is that it gets to a certain point in booting and comes up with a error message PANIC - error 19 error loading root dev. I am using sco openserver... (2 Replies)
Discussion started by: nhulley
2 Replies

3. SCO

Panic :

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

4. Red Hat

error : kernel panic: No init found

helo, my system is runing on redhat 9.0. but now when i run my machine i got the following error. Kernel Panic:No init found. try passing init = option to kernel. i dont have any idea about linux administration. can u help me to solve this error Thanks and Regards,... (2 Replies)
Discussion started by: amitpansuria
2 Replies

5. Linux

Kernal panic error& setuproot:error mounting /proc&/sys

Hi all, I am new to redhat/fedora linux. In fedora linux 6,we created one file system(hda3 - /fs). in this mount poing we were installed mounta vista os. while booting we are getting below error messages. 1) Booting 'mountaVisat(2.6.18_pro 500_pc_target-x86_586 smp)' root(hd0,1)... (2 Replies)
Discussion started by: arjunreddy3
2 Replies

6. Solaris

can any body tell me what is the difference between server panic and fatal error.

HI friends can any body tell me what is the difference between server panic and fatal error. (1 Reply)
Discussion started by: tv.praveenkumar
1 Replies

7. SCO

"PANIC: k_trap" error

hi I've virtualized physical SCO 5.0.6 on ESX 4 according to: Blog du DS45: HOWTO SCO P2V in the real life SCO starts with the network, but during shutdown I'm getting this message: PANIC: k_trap. My /etc/default/boot: # cat /etc/default/boot #ScoAdminInit BOOTMNT {RO RW NO} RO... (4 Replies)
Discussion started by: ccc
4 Replies

8. Red Hat

Kernel Panic Error

Hi Guys, I'm working with a down RedHat Server. Whenever the server tries to boot, there's an error stating: Kernel panic: No init found. Try passing init= option to kernel. In addition to this, the "Caps Lock" and "Scroll Lock" lights start flashing. The server doesn't boot pass this... (1 Reply)
Discussion started by: bbbngowc
1 Replies

9. Solaris

"PANIC CPU" ERROR MESSAGE

A server that I am working on (SUN FIRE V240 , SOLARIS 10) doesn't boot because of a corrupted files system. I tried to repair de file system, I also tried to to restore all the files systems with a backup of the server that I have but the message bellow appear panic/thread=30002fc2060:... (8 Replies)
Discussion started by: feg
8 Replies

10. Red Hat

Error: kernal panic not syncing

HI All, server stopped here, we are suspecting server crash, need install new OS. Any suggestions on this. kindly help to us. Thanks Rajesh (0 Replies)
Discussion started by: Rajesh_Apple
0 Replies
fwupgrade(8)						      System Manager's Manual						      fwupgrade(8)

NAME
fwupgrade - Updates the system firmware from a loadable firmware image (*.exe or *.sys) SYNOPSIS
/sbin/fwupgrade [-a] [-e] [-ignore] [-q] [-r] [-s] [-v] [-t CD-ROM_path] [-i path] /sbin/fwupgrade [-v] -f firmware_filename OPTIONS
Forces a firmware update without comparing the current firmware with the source firmware. Updates only if the current firmware is not equivalent to the source firmware. Specifies the path of the (*.exe or *.sys) firmware image. This is only used when you use a firmware image that is not on the distribution CD-ROM. For example, an image obtained from a web site download. You must ensure that the firmware image is the correct one for the target system, and verify that the image has the necessary support. This is indicated by bit1 and bit2 in the Flags column of the smmtable.txt file. Specifies the mount point of the target disk during an installation. This switch is to be used exclusively by the Tru64 UNIX install program. This switch suppresses error messages that are displayed if no firmware files are found on the distribution media, and causes the fwupgrade program to exit successfully. Does not upgrade the firmware, but displays information about the success of the desired operation. This enables you to to query fwupgrade to verify planned actions, such as ensuring whether the firmware really needs to be upgraded, or finding out if the target system supports a soft-reset. Resets the machine by software and reboots after the upgrade. The utility will exit with an error status if the system hardware does not support this feature. Sets silent mode, in which the firmware is upgraded without prompting you. If there is an error, the program also exits silently without prompting you. When this switch is used, you are not prompted for confirmation for the upgrade to proceed. Specifies the path of the mounted Firmware CD. If the -s option is not specified, you will be prompted to enter this path. Sets verbose mode, in which additional information is dis- played. DESCRIPTION
The fwupgrade command provides a means of updating the system firmware when a (*.exe or *.sys) loadable firmware update image is available. A firmware upgrade will shut down the system and require a full hardware reset. If the source firmware image does not support the loadable firmware update functionality, fwupgrade will exit with error status. The system must provide a SAVE_ENV callback that complies with the Alpha SRM. You can tell if the SAVE_ENV callback exists by executing the command: # consvar -a The SAVE_ENV is supported on the target system if the following message is displayed: Console environment variables saved If the SAVE_ENV is not supported on the target system, the following message is displayed: Failed to save environment variables Your programs can either check the return status of consvar -a or the return status of: setsysinfo(SSI_PROM_SAVE_ENV,...). See the setsysinfo(2) reference page for more information. EXIT STATUS
If you confirm that the firmware is to be upgraded, and no errors occur setting up the upgrade process, then fwupgrade will reboot the sys- tem rather than exit. An exception is that there is no reboot performed when the -i option is used. Instead, a status of 0 is returned. If you query whether the process would be successful, or if an upgrade request fails, the exit values are: Success. Firmware is adequate and supported. Failure. Firmware is not supported. Firmware needs to updated (when queried). EXAMPLES
To find out all information about your current firmware, platform, and the source firmware: # /sbin/fwupgrade -v -q Current Firmware: 4.10-0 Platform: 17-2-1091 Unable to open smmtable.txt at '/'. What is the mount point for the firmware CD? /mnt Firmware CD Version: 4.0 Distribution Firmware: 4.10-0 LFU File: /dev/rz2a at alpha1000/as1000_e4_v4_8.exe LFU Support: Y Soft Reset: Y System Firmware does not need to be upgraded To upgrade the firmware: # ./fwupgrade -t /mnt Current Firmware: 4.7-0 Are you sure that you wish to update the system firmware from 4.7-0 to 4.10-0?(yes/no)yes fwupgrade:Rebooting to update the system firmware... Terminated # syncing disks... done rebooting.... (transferring to monitor) FILES
The loadable firmware update images provided by Compaq. Typically, these are distributed on a firmware CD-ROM. If you obtain firmware images from a source other than the firmware CD-ROM (such as a www server) you should verify that they are the correct images for the tar- get system. A file provided with the firmware CD-ROM, used to determine the presence of the firmware CD-ROM and information about source firmware. SEE ALSO
Commands: consvar(8) Functions: setsysinfo(2) fwupgrade(8)
All times are GMT -4. The time now is 12:49 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy