From owner-freebsd-stable@FreeBSD.ORG Wed Apr 25 03:53:17 2007 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EB64C16A403 for ; Wed, 25 Apr 2007 03:53:17 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id D386F13C469 for ; Wed, 25 Apr 2007 03:53:17 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 0A2F11A4DDC; Tue, 24 Apr 2007 20:53:42 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 08EF4513DD; Tue, 24 Apr 2007 23:53:16 -0400 (EDT) Date: Tue, 24 Apr 2007 23:53:16 -0400 From: Kris Kennaway To: LI Xin Message-ID: <20070425035316.GB44054@xor.obsecurity.org> References: <20070313140848.GA89182@steerpike.hanley.stade.co.uk> <20070423025631.GA33256@steerpike.hanley.stade.co.uk> <20070423113912.GE2052@deviant.kiev.zoral.com.ua> <462DDB4D.8080507@delphij.net> <1177442585.462e5919c71f0@webmail.vsi.ru> <462EC294.3040001@delphij.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="X1bOJ3K7DJ5YkBrT" Content-Disposition: inline In-Reply-To: <462EC294.3040001@delphij.net> User-Agent: Mutt/1.4.2.2i Cc: freebsd-stable@freebsd.org, Oleg Derevenetz Subject: How to report bugs (Re: 6.2-STABLE deadlock?) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Apr 2007 03:53:18 -0000 --X1bOJ3K7DJ5YkBrT Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Apr 25, 2007 at 10:53:08AM +0800, LI Xin wrote: > Hi, Oleg, >=20 > Oleg Derevenetz wrote: > > ??????? LI Xin : > [...] > >> I'm not very sure if this is specific to one disk controller. Actually > >> I got some occasional reports about similar hangs on amd64 6.2-RELEASE > >> (slightly patched version) that most of processes stuck in the 'ufs' > >> state, under very light load, the box was equipped with amr(4) RAID. > >> > >> I was not able to reproduce the problem at my lab, though, it's still > >> unknown that how to trigger the livelock :-( Still need some > >> investigate on their production system. > >=20 > > I reported simular issue for FreeBSD 6.2 in audit-trail for kern/104406: > >=20 > > http://www.freebsd.org/cgi/query-pr.cgi?pr=3D104406&cat=3D > >=20 > > and there should be a thread related to this. Briefly, I suspects that = this is=20 > > related to nullfs filesystems on my server and when I cvsuped to FreeBS= D 6.2- > > STABLE with Daichi's unionfs-related patches and replaced nullfs-mounte= d fs=20 > > with unionfs-mounted (that was done 10.03.07) problem is gone (seems to= be so,=20 > > at least). >=20 > Hmm... Seems to be different issues. The problem I have received was a > pgsql server (no nullfs/unionfs involved), and the hang always happen > when it is not being heavily loaded (usually in the morning, for > instance, and there is no special configuration, like scheduled tasks > which can generate disk load, etc., only the entropy harvesting), so > this is quite confusing. Yes, a large part of the confusion is the unfortunate tendency of people to do the following: my system hangs/panics/etc my system hangs/panics/etc too; it must be the same problem! What we really need is for every FreeBSD user who encounters a hang/panic/etc to avoid jumping to conclusions -- no matter how many superficial similarities there may seem to you -- and instead go through the relevant steps described here: http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kern= eldebug.html Until you (or a developer) have analyzed the resulting information, you cannot definitively determine whether or not your problem is the same as a given random other problem, and you may just confuse the issue by making claims of similarity when you are really reporting a completely separate problem. Thanks, Kris --X1bOJ3K7DJ5YkBrT Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFGLtCsWry0BWjoQKURAsNdAKCwOnlz7oUKCt6jhuARsCMaAwreIgCeMFjd s7m+UjG93cLUCRmah39O2gU= =WQzm -----END PGP SIGNATURE----- --X1bOJ3K7DJ5YkBrT--