SLES11 SP2 XEN crash dump will trigger SEL: DMI Config Error

SUSE Linux Enterprise Server SLES Virtualization
1

Hi,

On our Romley platform, we install SLES11 SP2 with XEN. The GRUB entry in /boot/grub/menu.lst looks like the following .


###Don't change this comment - YaST2 identifier: Original name: linux###
title SUSE Linux Enterprise Server 11 SP2 - 3.0.13-0.27 (default)
    root (hd0,0)
    kernel /boot/vmlinuz-3.0.13-0.27-default root=/dev/disk/by-id/ata-ST2000NM0011_Z1P0A123-part1 ip=dhcp resume=/dev/disk/by-id/ata-ST2000NM0011_Z1P0A123-part3 splash=silent showopts crashkernel=256M-:128M
    initrd /boot/initrd-3.0.13-0.27-default

###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- SUSE Linux Enterprise Server 11 SP2 - 3.0.13-0.27
    root (hd0,0)
    kernel /boot/vmlinuz-3.0.13-0.27-default root=/dev/disk/by-id/ata-ST2000NM0011_Z1P0A123-part1 showopts ide=nodma apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset x11failsafe
    initrd /boot/initrd-3.0.13-0.27-default

###Don't change this comment - YaST2 identifier: Original name: xen###
title Xen -- SUSE Linux Enterprise Server 11 SP2 - 3.0.13-0.27
    root (hd0,0)
    kernel /boot/xen.gz crashkernel=256M-:128M
    module /boot/vmlinuz-3.0.13-0.27-xen root=/dev/disk/by-id/ata-ST2000NM0011_Z1P0A123-part1 ip=dhcp resume=/dev/disk/by-id/ata-ST2000NM0011_Z1P0A123-part3 splash=silent showopts
    module /boot/initrd-3.0.13-0.27-xen

  After triggerring trigger crash dump via the command “echo c > /proc/sysrq-trigger” , a lot of “DMI Configuration Error” SEL (system event log) will be generated to the BMC like the following entries.

001 2012-06-20 07:43:14 6F1002FFFF-8A Event Log        LogAreaReset/Cleared-Asserted
002 2012-06-20 07:50:19 6F07A500A0-00 Processor        ConfigurationError-Asserted
003 2012-06-20 07:50:19 6F07A500A0-00 Processor        ConfigurationError-Asserted
...
...
...
909 2012-06-20 07:52:35 6F1004FFFF-8A Event Log        SELFull-Asserted

Afterwards, we try to use “Yast2 kdump” to generate 256M kdump settings and then manually edit the GRUB boot entry as below.


###Don't change this comment - YaST2 identifier: Original name: xen###
title Xen -- SUSE Linux Enterprise Server 11 SP2 - 3.0.13-0.27 [try]
    root (hd0,0)
    kernel /boot/xen.gz [COLOR="#800080"]crashkernel=256M@16M[/COLOR]
    module /boot/vmlinuz-3.0.13-0.27-xen root=/dev/disk/by-id/ata-ST2000NM0011_Z1P0A123-part1 ip=dhcp resume=/dev/disk/by-id/ata-ST2000NM0011_Z1P0A123-part3 showopts [COLOR="#800080"]crashkernel=256M@16M[/COLOR]
    module /boot/initrd-3.0.13-0.27-xen

Please notice that “[COLOR="#800080"]crashkernel=256M@16M[/COLOR]” is appended to the line of “vmlinuz-3.0.13-0.27-xen” . Afte triggerring crash dump via the command “echo c > /proc/sysrq-trigger” again, the following files will be caught in /var/crash directory . The captured files are compatible with the “xen” environment which make sense . Besides, no SEL will be generated to BMC in this case.

-rw-r--r-- 1 root root         179 Jun 27 15:45 README.txt
-rw-r--r-- 1 root root     1848796 Jun 27 15:45 System.map-3.0.13-0.27-xen
-rw-r--r-- 1 root root 34066342928 Jun 27 15:45 vmcore
-rw-r--r-- 1 root root     4041433 Jun 27 15:45 vmlinux-3.0.13-0.27-xen.gz

Does GRUB entry need to update as above to make crash dump correct ? Please kindly help to clarify this problem.

2

lavator,

It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.

Has your issue been resolved? If not, you might try one of the following options:

Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.suse.com/faq.php

If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.

Good luck!

Your SUSE Forums Team
http://forums.suse.com