If there's a race why hasn't it been fixed in the main tree?

A swap issue makes sense. If I've been down long enough I get
swamped with email when I come back up. A bug in the latest
procmail yields 130M processes that fill up swap and make
the system be swap bound. The solution is the following
patch to procmail.

<http://www.rosat.mpe-garching.mpg.de/mailing-lists/procmail/2002-04/ms
g00248.html>

--On Sunday, November 10, 2002 7:03 PM +0000 [EMAIL PROTECTED] wrote:

Since going from a SMP to nonSMP kernel the Hard Locks don't
seem to be happening.  However I'm getting panics.

I've gotten 4 'sleeping thread owns a mutex' panics and one each
of 'Assertion i != 0 failed at ../../../kern/subr_witness.c:669'
and 'Duplicate free of item 0xc3895cc0 from zone 0xc0ea63c0(VMSPACE)'
The 'Duplicate free' can be caused by a race between swapout_procs()
and kern_exit()+wait1().

The enclosed patch might help.

Disabling swapping (sysctl vm.swap_enabled=0) can also help.

- Tor Egge



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to