On Sat, 10 Jan 2015 19:39:19 -0800
Philip Guenther guent...@gmail.com wrote:
On Mon, 5 Jan 2015, Helg wrote:
The man page for LOCK(9) says that if the kernel option LOCKDEBUG is
enabled, additional facilities are provided to assist in determining
deadlock occurrences.
I created a
On Sat, 10 Jan 2015 19:39:19 -0800
Philip Guenther guent...@gmail.com wrote:
On Mon, 5 Jan 2015, Helg wrote:
The man page for LOCK(9) says that if the kernel option LOCKDEBUG is
enabled, additional facilities are provided to assist in determining
deadlock occurrences.
I created a
Philip Guenther guenther at gmail.com writes:
It's dead, Jim, let's bury LOCKDEBUG.
There is an define AZALIA_LOG_MP and accompanying code in
sys/dev/pci/azalia.c which looks like a debug left-over.
azalia(4) is considered MP-safe for over a year from now.
On Mon, 5 Jan 2015, Helg wrote:
The man page for LOCK(9) says that if the kernel option LOCKDEBUG is
enabled, additional facilities are provided to assist in determining
deadlock occurrences.
I created a copy of /sys/arch/amd64/conf/GENERIC and added option
LOCKDEBUG. Executing config
Hi All,
The man page for LOCK(9) says that if the kernel option LOCKDEBUG is enabled,
additional facilities are provided to assist in determining deadlock
occurrences.
I created a copy of /sys/arch/amd64/conf/GENERIC and added option LOCKDEBUG.
Executing config and then make clean make
