Mailinglist Archive: opensuse-bugs (4932 mails)

< Previous Next >
[Bug 584554] New: random 61s soft lockups using xenified kernel or even 2.6.33-25
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Tue, 2 Mar 2010 09:34:15 +0000
  • Message-id: <bug-584554-21960@xxxxxxxxxxxxxxxxxxxxxxxx/>

Summary: random 61s soft lockups using xenified kernel or even 2.6.33-25
Classification: openSUSE
Product: openSUSE 11.2
Version: Final
Platform: x86-64
OS/Version: openSUSE 11.2
Status: NEW
Severity: Critical
Priority: P5 - None
Component: Kernel
AssignedTo: kernel-maintainers@xxxxxxxxxxxxxxxxxxxxxx
ReportedBy: samuel.kvasnica@xxxxxxxxx
QAContact: qa@xxxxxxx
Found By: ---
Blocker: ---

Created an attachment (id=345885)
--> (
syslog snippet

User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:
Gecko/20100110 Mandriva Linux/ (2010.0) Firefox/3.5.7

We experience random "61s" CPU soft lockups on kernel We even
verified the same behavior using the last head kernel 2.6.33-25-xen.

We use drbd + xen configuration, 2 drbd partitions + 1 xen pvm guest.
The system is running almost idle.

We can observe (using snmp logging) rapid increase of load during the lockup.
The system does not crash but the corresponding CPU will be loaded/blocked
during this time.

We are not able to determine what really triggers the lockup. High load does
not seem to correlate. Typically, system would run up to 12hours cleanly before
lockup happens. If lockup happens, more lockups will typically follow within
few minutes. Afterwards, system runs cleanly again. Typically, there is the
xen_safe_halt() on stack trace.

The same system gives absolutely no lockups on older hardware (2-core
Pentium-D, 8G RAM), 1 month uptime.

Our hardware:

-Supermicro X8SIL-F
-Chipset Ibex Peak, XEON X3450
-Last BIOS updates applied
-conservative BIOS settings
-setting hyperthreading/turbo/c-states in BIOS make no difference

Log of 2 last events is attached below (for 2.6.33 kernel but 2.6.31 looks very

Reproducible: Sometimes

Steps to Reproduce:
1. let system run
2. wait
3. wait, see above description...

Configure bugmail:
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >