Novell Home

My Favorites

Close

Please to see your favorites.

Generating a Kernel Core Dump Analysis File

This document (7010484) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Linux Enterprise Server 11
SUSE Linux Enterprise Server 10
SUSE Linux Enterprise Desktop

Situation

When the SUSE Linux kernel has core dumped or crashed, the default location for a kernel core file is in the /var/crash directory. What should be done with the vmcore file after it is generated?

Resolution

Run analyzevmcore to generate a kernel core dump analysis file. After running analyzevmcore, upload a supportconfig to SUSE Technical Support or review the core dump analysis file in supportconfig's crash.txt file.

Steps to create the core dump analysis file
1. Make sure your supportutils package is current. The analyzevmcore script is included the supportutils package.
2. Register the server for SUSE online updates. You need the Debuginfo repositories.
3. Enable all the Debuginfo repositories
4. Install the kernel-<flavor>-debuginfo RPM package
5. Run analyzevmcore
6. Run supportconfig


SLES11 SP2 Example

1. Following the Option A instructions at http://www.novell.com/communities/node/2332/supportconfig-linux
2. suse_register -n -a email=your@email.com -a regcode-sles=your_sle11_regcode
# NOTE: Only needed if you have not registered the server. Use your own email address and registration codes.
3. zypper lr  # lists the current repositories; the debuginfo repositories are required

#  | Alias                                            | Name                                             | Enabled | Refresh
---+--------------------------------------------------+--------------------------------------------------+---------+--------
 1 | SUSE-Linux-Enterprise-Server-11-SP2 11.2.2-1.234 | SUSE-Linux-Enterprise-Server-11-SP2 11.2.2-1.234 | Yes     | No    
 2 | nu_novell_com:SLE11-SP1-Debuginfo-Pool           | SLE11-SP1-Debuginfo-Pool                         | No      | Yes   
 3 | nu_novell_com:SLE11-SP1-Debuginfo-Updates        | SLE11-SP1-Debuginfo-Updates                      | No      | Yes   
 4 | nu_novell_com:SLE11-SP2-Debuginfo-Core           | SLE11-SP2-Debuginfo-Core                         | No      | Yes   
 5 | nu_novell_com:SLE11-SP2-Debuginfo-Updates        | SLE11-SP2-Debuginfo-Updates                      | Yes     | Yes   
 6 | nu_novell_com:SLE11-WebYaST-SP2-Pool             | SLE11-WebYaST-SP2-Pool                           | No      | Yes   
 7 | nu_novell_com:SLE11-WebYaST-SP2-Updates          | SLE11-WebYaST-SP2-Updates                        | No      | Yes   
 8 | nu_novell_com:SLES11-Extras                      | SLES11-Extras                                    | No      | Yes   
 9 | nu_novell_com:SLES11-SP1-Pool                    | SLES11-SP1-Pool                                  | Yes     | Yes   
10 | nu_novell_com:SLES11-SP1-Updates                 | SLES11-SP1-Updates                               | Yes     | Yes   
11 | nu_novell_com:SLES11-SP2-Core                    | SLES11-SP2-Core                                  | Yes     | Yes   
12 | nu_novell_com:SLES11-SP2-Extension-Store         | SLES11-SP2-Extension-Store                       | Yes     | Yes   
13 | nu_novell_com:SLES11-SP2-Updates                 | SLES11-SP2-Updates                               | Yes     | Yes   

4. Enable each of the Debuginfo repositories listed
zypper mr -e SLE11-SP1-Debuginfo-Pool
zypper mr -e SLE11-SP1-Debuginfo-Updates
zypper mr -e SLE11-SP2-Debuginfo-Core
zypper mr -e SLE11-SP2-Debuginfo-Updates

5. uname -r  # shows the kernel "flavor" at the end of the string
3.0.34-0.7-pae

6. zypper in kernel-pae-debuginfo
7. analyzevmcore  # generates the kernel core analysis
8. supportconfig  # includes the kernel core analysis in crash.txt


SLES10 SP4 Example

1. Following the Option A instructions at http://www.novell.com/communities/node/2332/supportconfig-linux
2. suse_register -n -a email=your@email.com -a regcode-sles=your_sle10_regcode
# NOTE: Only needed if you have not registered the server. Use your own email address and registration codes.
3. rug ca  # shows a list of all the catalogs; the debuginfo catalogs are required

Sub'd? | Name                                | Service                           
-------+-------------------------------------+------------------------------------
Yes    | SUSE Linux Enterprise Server 10 SP4 | SUSE Linux Enterprise Server 10 SP4
Yes    | SLES10-SP4-Pool                     | https://nu.novell.com             
Yes    | SLES10-SP4-Updates                  | https://nu.novell.com             
       | SLE10-SP4-Debuginfo-Pool            | https://nu.novell.com             
       | SLE10-SP4-Debuginfo-Updates         | https://nu.novell.com             
       | SLES10-GPLv3-Extras                 | https://nu.novell.com             

4. Subscribe to each of the Debuginfo catalogs listed
rug sub SLE10-SP4-Debuginfo-Pool
rug sub SLE10-SP4-Debuginfo-Updates

5. uname -r  # shows the kernel "flavor" at the end of the string
2.6.16.60-0.93.1-default

6. rug in kernel-default-debuginfo
7. analyzevmcore -k /boot/vmlinux-$(uname -r).gz # generates the kernel core analysis
8. supportconfig  # includes the kernel core analysis in crash.txt

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:7010484
  • Creation Date:18-JUL-12
  • Modified Date:19-JUL-12
    • SUSESUSE Linux Enterprise Desktop
      SUSE Linux Enterprise Server

Did this document solve your problem? Provide Feedback