Re: FreeBSD 5.2.1: Mutex/Spinlock starvation?

> There isn't a timeout. Rather, the lock spins so long as the current > owning thread is executing on another CPU. Interesting. Is there a way to 'lock' CPU's so that they always run on 'another' CPU ? Unfortunately as we speak the server is down again :( This all makes me wonder wether I shoul

Re: machine is unusable with panic: vrele: negative ref cnt

On Sat, Jun 05, 2004 at 06:08:31PM -0700, Alan Evans wrote: > On boot I see the following on an IBM T30 laptop: > > Mounting root from ufs:/dev/ad0s1a > WARNING: / was not properly dismounted > ad0: FAILURE - READ_MUL status=59 > error=40 LBA=376639 I would stick that drive in another machine and

Re: Orinoco Gold and Linksys AP

On Sat, Jun 05, 2004 at 12:37:28PM -0600, M. Warner Losh wrote: > What firmware level do you have? Both wi and owi works for all my > lucent/wavelan/orinoco cards. :-( Try changing the WEP information many times. Eventually, the card just goes away and never returns to initialized state, and the

Re: FreeBSD 5.2.1: Mutex/Spinlock starvation?

On Mon, 7 Jun 2004, Ali Niknam wrote: > > There isn't a timeout. Rather, the lock spins so long as the current > > owning thread is executing on another CPU. > > Interesting. Is there a way to 'lock' CPU's so that they always run on > 'another' CPU ? > > Unfortunately as we speak the server is

Re: FreeBSD 5.2.1: Mutex/Spinlock starvation?

On Mon, 7 Jun 2004, Ali Niknam wrote: > > There isn't a timeout. Rather, the lock spins so long as the current > > owning thread is executing on another CPU. > > Interesting. Is there a way to 'lock' CPU's so that they always run on > 'another' CPU ? > > Unfortunately as we speak the server is