Mailinglist Archive: opensuse-bugs (6633 mails)

< Previous Next >
[Bug 535682] New: kernel-xen x86_64 2.6.27.25-0.1.1 & 2.6.27.29-0.1.1 panic at boot
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Mon, 31 Aug 2009 11:44:49 -0600
  • Message-id: <bug-535682-21960@xxxxxxxxxxxxxxxxxxxxxxxx/>
http://bugzilla.novell.com/show_bug.cgi?id=535682


Summary: kernel-xen x86_64 2.6.27.25-0.1.1 & 2.6.27.29-0.1.1
panic at boot
Classification: openSUSE
Product: openSUSE 11.1
Version: Final
Platform: x86-64
OS/Version: openSUSE 11.1
Status: NEW
Severity: Critical
Priority: P5 - None
Component: Xen
AssignedTo: jdouglas@xxxxxxxxxx
ReportedBy: rbsmith@xxxxxxxxxx
QAContact: qa@xxxxxxx
Found By: ---


Created an attachment (id=316037)
--> (http://bugzilla.novell.com/attachment.cgi?id=316037)
serial console boot log

User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.13)
Gecko/2009080200 SUSE/3.0.13-0.1.2 Firefox/3.0.13

The x86_64 kernel-xen panics on boot on our HP Proliant DL360-G5 boxes when an
Intel Gigabyte CT desktop adapter (EXPI930CTBLK, 82574L controller) is
installed.

All kernel-default kernels properly boot with the Intel NIC installed.
kernel-xen-2.6.27.21-0.1.2 properly boots with the Intel NIC installed.
Have not tested kernel-xen-2.6.27.23-0.1.1

We were trying out the Intel NICs on these DL360-G5's in an effort to determine
if a stability problem we've experienced with the 2.6.27.21-0.1-xen is
associated with the DL360-G5 broadcomm (bnx2) drivers.

The Xen stability problem is in the form of dom0 block and network devices
simply disappearing every few days, requiring a sysrq reboot. That will have to
be another bug report.

Reproducible: Always

Steps to Reproduce:
1.Install the Intel Gigabyte CT desktop adapter
2.Install the x86_64 2.6.27.29-0.1.1 kernel-xen
3.Boot your HP Proliant DL360-G5
Actual Results:
Kernel panic in write_msi_msg followed by an immediate reboot.

--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >
Follow Ups