Date: Fri, 17 Nov 2000 12:55:28 +0100 (CET) From: Soren Schmidt <sos@freebsd.dk> To: sheldonh@uunet.co.za (Sheldon Hearn) Cc: bright@wintelcom.net (Alfred Perlstein), steve@virtual-voodoo.com (Steven E. Ames), bp@butya.kz (Boris Popov), valentin@valcho.net (Valentin Chopov), current@FreeBSD.ORG Subject: Re: CURRENT is freezing again ... Message-ID: <200011171155.MAA92493@freebsd.dk> In-Reply-To: <2967.974461715@axl.fw.uunet.co.za> from Sheldon Hearn at "Nov 17, 2000 01:48:35 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
It seems Sheldon Hearn 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. You are _not_ alone, there has been numerous complains about this on the list, but so far they have not been taken seriously :| > >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. It doesn't help here at least, the machine(s) just lock up solid only reset or a powercycle can bring them back... > Oh, and a couple of deep breaths are probably in order. :-) Yeah like *sigh* .... -Søren 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?200011171155.MAA92493>