2.5.37 lockup with dbench 36 and make -j3 bzImage and PREEMPT=y.

From: Steven Cole (elenstev@mesatop.com)
Date: Fri Sep 20 2002 - 16:05:32 EST

While running 2.5.37 with 36 dbench clients and doing a kernel compile
with make -j3 bzImage, my test machine locked up. Repeating the test,
the box ran up to 80 dbench clients and was doing make clean on a kernel
tree when the freeze occurred. (My dbench ramp-up test runs dbench with
1,2,3,4,6,8,10,12,16,20,24,28,32,36,40,44,48,52,56,64,80,96,112, and 128
clients). When the box froze, it did not even respond to SYSRQ-H (tested
OK before lockup). Each time, I gave the system a few minutes to come
out of its coma, but it didn't.

I also saw this with 2.5.36-bk3, patched with Robert's preempt-fix,
under similar circumstances (dbench 40 and parallel make).

Without doing a kernel compile at the same time, the text box was able
to run up to 128 dbench clients successfully with 2.5.37 and PREEMPT.

The 2.5.37 kernel was patched with this fix for PREEMPT:
and this fix for eepro100:

Both of those kernels were configured with SMP and PREEMPT.

The test box is dual PIII, 1GB, scsi, ext3 fs. The dbench runs and
kernel compiles were both run from the same disk.

I have been unable so far to repeat this failure with plain 2.5.37 and
no PREEMPT. Plain vanilla 2.5.37 no preempt has run up to 112 dbench
clients while doing make -j3 bzImage. At one point, the box appeared to
have frozen, with vmstat -n 1 3600 output stopped printing for a while,
but the system is still responsive to SYSRQ-H, P, T, just slow with
dbench 128 running.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

This archive was generated by hypermail 2b29 : Mon Sep 23 2002 - 22:00:31 EST