Date: Fri, 17 Nov 2000 13:48:35 +0200 From: Sheldon Hearn <sheldonh@uunet.co.za> To: Alfred Perlstein <bright@wintelcom.net> Cc: "Steven E. Ames" <steve@virtual-voodoo.com>, Soren Schmidt <sos@freebsd.dk>, Boris Popov <bp@butya.kz>, Valentin Chopov <valentin@valcho.net>, current@freebsd.org Subject: Re: CURRENT is freezing again ... Message-ID: <2967.974461715@axl.fw.uunet.co.za> In-Reply-To: Your message of "Thu, 16 Nov 2000 10:42:51 PST." <20001116104251.D830@fw.wintelcom.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 16 Nov 2000 10:42:51 PST, Alfred Perlstein wrote: > I would try a new kernel, and perhaps some collabaration with John > to debug these problems rather than just complaining about the > situation. I see at least two experianced developers in the CC > list, there's no reason for these poor bug reports. The problem with a hard lock-up out of which you can't escape into the debugger is that it makes meaningful bug reports impossible. My non-SMP workstation has exhibited apparently arbitrary lock-ups since the advent of SMPng. I thought I was the only one, since my question on the freebsd-current mailing list went unanswered. From my understanding, John's WITNESS code allows us to break into the debugger from within interrupt context. If the lock-ups are happening in there, then this may help us provide better bug reports. Oh, and a couple of deep breaths are probably in order. :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2967.974461715>