Resolving The Problem

Operating System errors and Stop Codes (called Blue Screens in Microsoft Windows, Abends in Novell NetWare, Kernel Panics in UNIX) are often the result of application and/or file corruption that can occur as a result of poor application programming or known bugs that exist in all software. Fixes to these issues are periodically released in software patches known as Service Packs, Fix Packs, or Hot Fixes. However, there are instances when errors and Stop Codes may indicate a hardware source or problem. The following lists detail the most common hardware-related error codes and actions to take when they occur.

Note: If IBM hardware has recently been added or changed or if hardware errors (during POST/Startup) are occurring with the Operating System errors, please refer to the appropriate IBM hardware section for troubleshooting. These suggestions are provided as a best-effort service and should in no way be viewed as a replacement for direct support from an operating system vendor on their product.

Due to the complex nature of kernel panic debugging in UNIX and Linux, IBM recommends gathering as much of the panic information as possible and then searching the vendor's support site for help. There are many software supplements and security patches for almost all UNIX and Linux distributions. Make sure the system is at the latest levels of software and has all applicable patches applied.

• Caldera SCO Support Site (Openserver / Unixware / Openlinux)
• Red Hat Linux Support Site
• SUSE LINUX Support Site
• TurboLinux Support Site

Support forums

Before you call IBM Service

Return to the main Troubleshooting page