We have a script that forks a bunch of children (up to ten) and runs some transformations on images.
Since upgrading from 2.6.22-r9 to 2.6.23-r8 we have noticed soft lockups, such as:
BUG: soft lockup - CPU#1 stuck for 11s! [watchdirectory:21493]
Pid: 21493, comm: watchdirectory
EIP: 0060:[<c039f78b>] CPU: 1
EIP is at __write_lock_failed+0x7/0x1c
EFLAGS: 00200287 Tainted: G D (2.6.23-gentoo-r8 #1)
EAX: c0570410 EBX: f6c6f6c0 ECX: c057049c EDX: f6c6f6ec
ESI: f74845c0 EDI: dc9e7eb2 EBP: f7b0d740 DS: 007b ES: 007b FS: 00d8
CR0: 8005003b CR2: b7d396cb CR3: 303fd000 CR4: 000006d0
DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000
DR6: ffff0ff0 DR7: 00000400
How easy is it to reproduce?
Can you post the script?
Can you reproduce it on 2.6.24?
Can you reproduce it on a filesystem other than CIFS?
Is this a local or network based CIFS mount?
One more thing, can you reproduce it on an untainted kernel?
It happened several times in one night, but has not happened since.
I can't reproduce it at the moment, the script is not able to be posted, and the problem only occurs with CIFS. So we can close for the moment I think..
How is our kernel tainted? VMware perhaps?
Yes, vmware would taint your kernel.
If this is not reproducible then I'll close this for now.