iozone causes soft lockup

Bug #268215 reported by Zeke Harris on 2008-09-09
6
Affects Status Importance Assigned to Milestone
iozone3 (Ubuntu)
Undecided
Unassigned

Bug Description

Running the Phoronix Test Suite (http://www.phoronix-test-suite.com/) universe-cli benchmark (cmdline: phoronix-test-suite run universe-cli) causes a CPU soft lockup during the iozone test. Running the iozone benchmark by itself does not seem to cause this issue. This did not occur when running the same test suite on the same hardware configuration with Ubuntu Server 8.04.01.

Software:
 * Ubuntu Server 8.10 Alpha 5 (uname -a: Linux ibex-test 2.6.27-2-server #1 SMP Thu Aug 28 17:58:24 UTC 2008 x86_64 GNU/Linux)
 * Phoronix Test Suite 1.2.0

Hardware:
 * Supermicro X7SBi Motherboard
 * Intel Q6600 Processor
 * 8GB Crucial memory
 * Areca 1210 SATA Raid Controller
 * (4) 750GB Seagate 7200.10 drives (in a single RAID 5 configuration with two volumes; 300GB / EXT3; 1.9TB /home XFS -- the test was run on the XFS partition)

Here is the serial console output showing the first 4 soft lock messages; after which they repeat infinitely as far as I can tell:
[ 5841.162480] BUG: soft lockup - CPU#2 stuck for 61s! [iozone:29413]

[ 5874.443727] BUG: soft lockup - CPU#3 stuck for 61s! [kstop3:29435]

[ 5874.449998] BUG: soft lockup - CPU#0 stuck for 61s! [kstop0:29432]

[ 5906.661227] BUG: soft lockup - CPU#1 stuck for 61s! [kstop1:29433]

Attached is a partial log of the test suite run.

Zeke Harris (thalin) wrote :
Andres Mujica (andres.mujica) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in IOZONE.
For future reference you might be interested to know that a lot of applications have bug reporting functionality built in to them. This can be accessed via the Report a Problem option in the Help menu for the application with which you are having an issue. You can learn more about this feature at https://wiki.ubuntu.com/ReportingBugs.

Charlie Kravetz (charlie-tca) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. Since you reported this against a development version of Ubuntu Jaunty, we are closing this report. If this can be reproduced using the beta2 version of Ubuntu Lucid, please comment and change the status to 'new' in the yellow line.

Changed in iozone3 (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers