System reboots while loading qlaxxx module on xen Kernel

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


SUSE Linux Enterprise Server 11


The xen Kernel fails to load the qlaxxx module and does immediately reboot the system. This issue appears on SLES11 64-bit System after an update of the kernel-*, kernel-xen ( and  xen-* (3.3.1_18546_16-0.1.1) packages. With a serial console attached on the system, one can see the following:
QLogic Fibre Channel HBA Driver:
vendor=1014 device=0308
qla2xxx 0000:18:00.0: PCI INT A -> GSI 79 (level, low) -> IRQ 79
qla2xxx 0000:18:00.0: Found an ISP2432, irq 79, iobase 0xffffc20002f84000
qla2xxx 0000:18:00.0: Configuring PCI space...
qla2xxx 0000:18:00.0: Configure NVRAM parameters...
qla2xxx 0000:18:00.0: Verifying loaded RISC code...
firmware: requesting ql2400_fw.bin
ACPI: Power Button (FF) [PWRF]
qla2xxx 0000:18:00.0: Allocated (64 KB) for EFT...
qla2xxx 0000:18:00.0: Allocated (1413 KB) for firmware dump...
(XEN) ----[ Xen-3.3.1_18546_16-0.1.1  x86_64  debug=n  Not tainted ]----
(XEN) CPU:    1
(XEN) RIP:    e008:[<ffff828c80140199>] write_msi_msg+0xd9/0x130
(XEN) RFLAGS: 0000000000010046   CONTEXT: hypervisor
(XEN) rax: 00000000fee08000   rbx: ffff8300bec24600   rcx: 0000000000000035
(XEN) rdx: ffff828bcffff000   rsi: ffff8300bfcf7d78   rdi: ffff8300bec24600
(XEN) rbp: ffff8300bfcf7d78   rsp: ffff8300bfcf7cf8   r8:  0000000000000000
(XEN) r9:  ffff8300bfcf7d58   r10: ffff8300bfcf7ec8   r11: 0000000000000246
(XEN) r12: 0000000000000000   r13: ffff8300bec24480   r14: ffff8300bec24600
(XEN) r15: 0000000000000000   cr0: 000000008005003b   cr4: 00000000000026b0
(XEN) cr3: 00000000094c8000   cr2: ffff828bcffff000
(XEN) ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: e010   cs: e008
(XEN) Xen stack trace from rsp=ffff8300bfcf7cf8:
(XEN)    0000000000000001 ffff8300bec24600 0000000000000035 0000000000000000
(XEN)    ffff8300bec24480 ffff8300bec24600 0000000000000000 ffff828c801402ea
(XEN)    0000000000000001 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000001 0000000000000000 0000000000000000 0000000000000000
(XEN)    00000000fee08000 ffff830000004035 00000000fffffff4 ffff8300bec244a0
(XEN)    ffff8300bfcf7ec8 ffff828c8014102d 000000000000f800 0000000000000001
(XEN)    0000000000000001 000000188022e120 0000000000000000 ffff8300bec24608
(XEN)    0000007c000fe0b0 000000000000007e 0000000200000000 ffff828c80466600
(XEN)    0000000000000035 00000000000000fe ffff8300bfcd0080 00000000000000fe
(XEN)    0000000000000035 ffff828c801421f1 ffff8300bfcf7ec8 ffff830000000000
(XEN)    0000000000000202 0000000000000455 ffff8300bfcf7e98 ffff880bd35edb18
(XEN)    00000000000000fe ffff8300bfcd0080 0000000000000035 ffff828c80151705
(XEN)    0000000001c9c380 ffff8300bfcf7f28 ffff8300bfcf7ec8 ffff8300bfcd01f8
(XEN)    0000000000007ff0 ffffffffffffffff 0000000000000018 0000000000000000
(XEN)    00000000f6340000 ffff828c80110eed 0000000000000018 0000000000000035
(XEN)    00000000f6340000 00a0fb00bfcf7f28 ffff828c8022e030 ffff8300bec3e080
(XEN)    0000000000007ff0 0000000000000000 00000000f6340000 00000000f6340000
(XEN)    ffff880bd27472c0 ffff828c801b9169 ffff880bd27472c0 00000000f6340000
(XEN)    00000000f6340000 0000000000000000 0000000000007ff0 ffff880bd4f96800
(XEN)    0000000000000246 00005353d4f92800 ffff880bd35edb54 0000000000000004
(XEN) Xen call trace:
(XEN)    [<ffff828c80140199>] write_msi_msg+0xd9/0x130
(XEN)    [<ffff828c801402ea>] setup_msi_irq+0xfa/0x130
(XEN)    [<ffff828c8014102d>] pci_enable_msi+0x33d/0x630
(XEN)    [<ffff828c801421f1>] map_domain_pirq+0x1d1/0x220
(XEN)    [<ffff828c80151705>] do_physdev_op+0x725/0xe58
(XEN)    [<ffff828c80110eed>] do_multicall+0x28d/0x330
(XEN)    [<ffff828c801b9169>] syscall_enter+0xa9/0xae
(XEN) Pagetable walk from ffff828bcffff000:
(XEN)  L4[0x105] = 00000000bf042027 5555555555555555
(XEN)  L3[0x02f] = 0000000c3fdfe063 5555555555555555
(XEN)  L2[0x07f] = 0000000000000000 ffffffffffffffff 
(XEN) ****************************************
(XEN) Panic on CPU 1:
(XEN) [error_code=0002]
(XEN) Faulting linear address: ffff828bcffff000
(XEN) ****************************************
(XEN) Reboot in five seconds...
(XEN)  L3[0x02f] = 0000000


The issue has been fixed and released in November, 2009.
Download and install latest or recent xen-* packages.


This Support Knowledgebase provides a valuable tool for 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:7004431
  • Creation Date: 11-Sep-2009
  • Modified Date:14-Oct-2022
    • SUSE Linux Enterprise Server

< Back to Support Search

For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]

SUSE Support Forums

Get your questions answered by experienced Sys Ops or interact with other SUSE community experts.

Join Our Community

Support Resources

Learn how to get the most from the technical support you receive with your SUSE Subscription, Premium Support, Academic Program, or Partner Program.

SUSE Customer Support Quick Reference Guide SUSE Technical Support Handbook Update Advisories
Support FAQ

Open an Incident

Open an incident with SUSE Technical Support, manage your subscriptions, download patches, or manage user access.

Go to Customer Center