Subject: kern/37531: lockdebug appears broken
To: None <email@example.com, firstname.lastname@example.org,>
From: None <email@example.com>
Date: 12/13/2007 09:55:00
>Synopsis: lockdebug appears broken
>Arrival-Date: Thu Dec 13 09:55:00 +0000 2007
>Originator: Andrew Doran
The NetBSD Project
Dual core cpu.
LOCKDEBUG frequently reports bogus errors, usually "already initialized"
or "freeing active lock". Very often, it happens on two CPUs at once
which suggests major corruption.
The quickest way I have found is to run SGI fsstress on /tmp, using
a kernel from the vmlocking branch.
fsstress -p 10 -d /tmp -n 100000 will usually break it.
I have tried backing out the spinning rwlock changes and replacing the
libkern rbtree with one built on sys/tree.h but that does not fix it.
A variety of paranoid changes and assertions do not help.
Unknown as yet.