Port-i386 archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: ongoing major problems with NetBSD-5 and LOCKDEBUG on multi-core system




To: Gary Duzan <gary%duzan.org@localhost>

Subject: Re: ongoing major problems with NetBSD-5 and LOCKDEBUG on multi-core system

From: Mindaugas Rasiukevicius <rmind%netbsd.org@localhost>

Date: Thu, 26 Jan 2012 19:18:11 +0000


Gary Duzan <gary%duzan.org@localhost> wrote:
> In Message <m1RmfkI-001ECGC%once.weird.com@localhost>,
>    "Greg A. Woods" <woods%planix.ca@localhost>wrote:
> 
> =>So, I've been wondering, is anyone else running netbsd-5 on a many-core
> =>system with a LOCKDEBUG + DIAGNOSTICS + DEBUG kernel?
> 
>    It has been a while, but as of a few years ago LOCKDEBUG simply
> was incompatible with multiprocessor systems. I don't recall seeing
> anything explicit to indicate that it was working again, so I would
> hesitate to attempt it again.

This is false.  LOCKDEBUG was focused on MP systems in the first place.
It is one of the main tools to debug locking related issues and it is used
by the developers to test pretty much any major change/patch.

As for the bug.. it should be fixed now.

-- 
Mindaugas


Follow-Ups:

FIXED!!! (was: ongoing major problems with NetBSD-5 and LOCKDEBUG on multi-core system)
From: Greg A. Woods


References:

ongoing major problems with NetBSD-5 and LOCKDEBUG on multi-core system
From: Greg A. Woods

Re: ongoing major problems with NetBSD-5 and LOCKDEBUG on multi-core system
From: Gary Duzan




Prev by Date: Re: NetBSD on current AMD motherboards

Next by Date: FIXED!!! (was: ongoing major problems with NetBSD-5 and LOCKDEBUG on multi-core system)

Previous by Thread: Re: ongoing major problems with NetBSD-5 and LOCKDEBUG on multi-core system

Next by Thread: FIXED!!! (was: ongoing major problems with NetBSD-5 and LOCKDEBUG on multi-core system)

Indexes:

reverse Date

reverse Thread

Old Index



Home | Main Index | Thread Index | Old Index