Re: Heads up: -current sucks today :-)
On 18-Apr-2002 Hiten Pandya wrote: --- Robert Watson [EMAIL PROTECTED] wrote: I've had four seperate and distinct panics on my -current box from yesterday in the last twenty minutes. -CURRENT appears to be somewhat unstable. Yes, this is -CURRENT; please wear a hard hat and avoid manipulating critical data using you -CURRENT box until things settle down. I have been seeing a 'witness_get exhausted' message for quite a long time. I have disabled SMP on my kernel as of now, but still have to figure out where and why this message is coming. The witness_get thing was fixed a week or so ago with the lock descriptions added to mtx_init(). -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve! - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Heads up: -current sucks today :-)
--- John Baldwin [EMAIL PROTECTED] wrote: I have been seeing a 'witness_get exhausted' message for quite a long time. I have disabled SMP on my kernel as of now, but still have to figure out where and why this message is coming. The witness_get thing was fixed a week or so ago with the lock descriptions added to mtx_init(). Which reminds me!, HITEN, read the cvs-all lists regularly. :-) Thanks for the info. :) -- Hiten __ Do You Yahoo!? Yahoo! Games - play chess, backgammon, pool and more http://games.yahoo.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Heads up: -current sucks today :-)
--- Robert Watson [EMAIL PROTECTED] wrote: I've had four seperate and distinct panics on my -current box from yesterday in the last twenty minutes. -CURRENT appears to be somewhat unstable. Yes, this is -CURRENT; please wear a hard hat and avoid manipulating critical data using you -CURRENT box until things settle down. I have been seeing a 'witness_get exhausted' message for quite a long time. I have disabled SMP on my kernel as of now, but still have to figure out where and why this message is coming. -- Hiten __ Do You Yahoo!? Yahoo! Tax Center - online filing with TurboTax http://taxes.yahoo.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Heads up: -current sucks today :-)
On Thu, 18 Apr 2002, Hiten Pandya wrote: --- Robert Watson [EMAIL PROTECTED] wrote: I've had four seperate and distinct panics on my -current box from yesterday in the last twenty minutes. -CURRENT appears to be somewhat unstable. Yes, this is -CURRENT; please wear a hard hat and avoid manipulating critical data using you -CURRENT box until things settle down. I have been seeing a 'witness_get exhausted' message for quite a long time. I have disabled SMP on my kernel as of now, but still have to figure out where and why this message is coming. Dunno what version of -CURRENT you are using, but in theory John's recent mutex class commits should help with that by reducing the number of locks that WITNESS has to treat as unique. If this is still happening on a -CURRENT from the last two days, you may want to drop him an e-mail. The output of vmstat -m might also be useful, since locks are usually associated with structures, and some indication of the quantity of structures should help identify what locks are being over-used. The output from the ddb 'show witness' command may also be useful. Robert N M Watson FreeBSD Core Team, TrustedBSD Project [EMAIL PROTECTED] NAI Labs, Safeport Network Services To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Heads up: -current sucks today :-)
I've had four seperate and distinct panics on my -current box from yesterday in the last twenty minutes. -CURRENT appears to be somewhat unstable. Yes, this is -CURRENT; please wear a hard hat and avoid manipulating critical data using you -CURRENT box until things settle down. Robert N M Watson FreeBSD Core Team, TrustedBSD Project [EMAIL PROTECTED] NAI Labs, Safeport Network Services To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
