Date: Tue, 21 Aug 2001 17:18:33 -0700 From: Kris Kennaway <kris@obsecurity.org> To: Alfred Perlstein <bright@mu.org> Cc: Kris Kennaway <kris@obsecurity.org>, John Baldwin <jhb@FreeBSD.org>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/kern kern_condvar.c kern_synch.c src/sys/sys proc.h Message-ID: <20010821171832.B22330@xor.obsecurity.org> In-Reply-To: <20010821170420.L81307@elvis.mu.org>; from bright@mu.org on Tue, Aug 21, 2001 at 05:04:21PM -0500 References: <200108211842.f7LIgkp03186@freefall.freebsd.org> <20010821134601.J81307@elvis.mu.org> <20010821124428.B17739@xor.obsecurity.org> <20010821164833.D58026@leviathan.inethouston.net> <20010821170420.L81307@elvis.mu.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--Fba/0zbH8Xs+Fj9o Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Aug 21, 2001 at 05:04:21PM -0500, Alfred Perlstein wrote: > * David W. Chapman Jr. <dwcjr@inethouston.net> [010821 16:48] wrote: > > On Tue, Aug 21, 2001 at 12:44:28PM -0700, Kris Kennaway wrote: > > > On Tue, Aug 21, 2001 at 01:46:01PM -0500, Alfred Perlstein wrote: > > >=20 > > > > How likely are these sort of fixes going to be able to help > > > > the perceived instability of -current? Is -current noticeably > > > > unstable or do we just have the usual crowd of people screaming > > > > sort of like what was going on a couple of months ago. > > > >=20 > > > > "current is broken" > > > > "no it's not" > > > > "yes it is" > > > > "give me a crashdump" > > > > ":P" > > >=20 > > > Most of the problems I was having weren't easily reproducible or didnt > > > cause panics, just lockups :-( > > >=20 > > I am getting some lockups too, but they only last for around 30=20 > > seconds, sometimes they get so bad I get a BUS I/O Error when I try=20 > > to do anything in some applications during the lockup. >=20 > This is a pretty useless bug report. >=20 > Please read the section in the handbook about kernel debugging > and get us a useful traceback/crashdump as well as systat type > info. This is the same problem I have. It's not a panic, so there's no traceback to obtain, and DDB is locked out for the duration of the freeze, and doesn't show anything useful I can determine once the system unfreezes. Kris --Fba/0zbH8Xs+Fj9o Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE7gvpXWry0BWjoQKURAmcfAKDj+1XmnrItzofqA82jnowUGME9JwCgkRgi n96ZhD/oo1jg0fd238JeeUw= =coea -----END PGP SIGNATURE----- --Fba/0zbH8Xs+Fj9o-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010821171832.B22330>