Solaris panics fault instance and Solution

Article Title: panics fault examples and solutions for solaris systems. Linux is a technology channel of the IT lab in China. Includes basic categories such as desktop applications, Linux system management, kernel research, embedded systems, and open source.
　　 I. fault phenomena and Analysis
The automatic restart of the workstation is quite special: irregular and without warning. The most critical impact on users is not only job failure, but also database destruction. This system fault is analyzed carefully, and the system reports the "Panics" error by searching the error log. When the system restarts automatically, the/etc/rc2.d/S75savecore utility will unmount the information to the/var/crash/'hostname'/directory of the file system, this allows the system administrator to analyze and locate faults. For 21 Panics errors, the system automatically generates the following files:
-Rw-r -- 1 root 634041 Feb 3 0:20 unix.0
...........................
-Rw-r -- 1 root 620121 Aug 7 12:35 unix.16
...........................
-Rw-r -- 1 root 622218 Aug 12 09:25 unix.21
　　
-Rw-r -- 1 root 181395456 Feb 3 0:20 vmcore.0
...........................
-Rw-r -- 1 root 237830144 Aug 7 :35 vmcore.16
...........................
-Rw-r -- 1 root 168732916 Aug 12 09:25 vmcore.21
　　
　　 Ii. Panics Error Type Analysis
Based on the technical information provided by the system, Panics errors have two typical error types:
Category 1: reboot)
This type of errors refers to the protection measures taken by the system to avoid expansion of errors when an illegal command is encountered during execution, the access to such illegal commands may be caused by many factors such as the motherboard, memory, and video card, or a BUG in the system's support for a certain hardware. If the hardware is correct, sometimes the operating system has some defects, which may also lead to such faults.
Category 2: system hang)
This type of error occurs when the system does not accept any commands, most of which are caused by user application errors that consume system resources.
From the fault analysis, we can determine that the fault presented by this machine is the first type of situation.
　　
　　 Iii. Fault research and Solution
By analyzing and researching the files unix.16 and vmcore.16 for System Kernel Fault uninstallation, the sun Workstation system with seismic inversion Jason software is unstable.
For reboot faults, in order to find an effective troubleshooting method, we believe that we should start with analyzing the error information of the system when a fault occurs and use the debugging tools provided by the system, (such as adb and crash. Finally, on the sunsolve website, find a software named Act (Automated Crash Analysis Tool) used to analyze the DUMP file generated by Panics errors ).
　　
1. installation and configuration of act Software
The installation of this software will generate the S76ACT_dumpscript script configuration file in/etc/rc2.d for later tracking and analysis.
Detailed installation process (omitted)
2. Run the Act software for code analysis and store the analysis results in the act.16 file.
# Cd/var/crash/'hostname'
#/Opt/CTEact/bin/act? N unix.16? D vmcore.16> act.16
3. Analyze the software result and extract the keyword of the fault information
# More act.16
This file contains a lot of information. The extracted information is as follows:
System booted at: 2003 Aug 7 01:09:37 GMT
System crashed at: 2003 Aug 7 12:33:14 GMT
Crash dump started at: 2003 Aug 7 12:34:54 GMT
Panic: bad trap: type = % x rp = % p addr = % p mmu_fsr = % x occurred in module "% s" due to % s
SunSolve search string: ### SUNSOLVE ###
[Ifb_kernel_dma_pai_data trap type 31 (data mmu miss)] (ifb is the logical device name of the 3D video card)
The keyword [ifb_kernel_dma_pai_data trap type 31 (data mmu miss)] is extracted from the software analysis results. The result is as follows: the current SunOS 5.8 Generic_108528-11 kernel version of X Window and 3D Graphics card support still has a bug, the workstation uses the video card is Elite3D Graphics and Expert3D Graphics, the troubleshooting method is to download the latest patch for this workstation to solve the problem of video card support.
The required patch files are as follows:
108569-08, 108604-32, 108605-33, 108606-31, 108576-41, 108714-05, 108773-08.
4 fault solution
Download all the patch files, and then use the pkgadd or patchadd utility provided by the system to unpackage and install and verify them.
　　
　　 Iv. Key Technologies
1. Locating and analyzing system errors
2. Determination of fault types and Solutions
3. ACT Software Development and Application