From owner-freebsd-current@FreeBSD.ORG Tue Oct 21 14:50:58 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 797D116A4B3; Tue, 21 Oct 2003 14:50:58 -0700 (PDT) Received: from obsecurity.dyndns.org (adsl-63-207-60-234.dsl.lsan03.pacbell.net [63.207.60.234]) by mx1.FreeBSD.org (Postfix) with ESMTP id 55CFA43FB1; Tue, 21 Oct 2003 14:50:57 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: from rot13.obsecurity.org (rot13.obsecurity.org [10.0.0.5]) by obsecurity.dyndns.org (Postfix) with ESMTP id D259666C9E; Tue, 21 Oct 2003 14:50:56 -0700 (PDT) Received: by rot13.obsecurity.org (Postfix, from userid 1000) id C09BBDB2; Tue, 21 Oct 2003 14:50:56 -0700 (PDT) Date: Tue, 21 Oct 2003 14:50:56 -0700 From: Kris Kennaway To: Matthew Jacob Message-ID: <20031021215056.GA67499@rot13.obsecurity.org> References: <20031021160559.GA65882@rot13.obsecurity.org> <000801c3981a$8abc6540$23a610ac@win2k> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="cNdxnHkX5QqsyA0e" Content-Disposition: inline In-Reply-To: <000801c3981a$8abc6540$23a610ac@win2k> User-Agent: Mutt/1.4.1i cc: alpha@FreeBSD.org cc: current@FreeBSD.org cc: 'Kris Kennaway' Subject: Re: Sleeping on "isp_mboxwaiting" with the following non-sleepablelocks held: X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Oct 2003 21:50:58 -0000 --cNdxnHkX5QqsyA0e Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Oct 21, 2003 at 02:30:21PM -0700, Matthew Jacob wrote: > So? How about some details and context? Um, what more "details and context" do you need? I provided the log of the system activity (specifically, media errors and swap read failure) leading up to the panic, and the ddb backtrace. > I thought was told that being able to use locks in HBAs is fine. I had > them on for a while, and then had them off. I turned them on again over > a month ago. I'm somewhat surprised to see that a problem shows up now. This was apparently triggered by the disk failure, which is not a commonly exercised code path. > *I* do the right thing with locks, IMO. I hold them in my module when I > enter and release them if/when I leave. Seeing a lock held by some > random caller causing me to blow up to me seems to be a hole in the > architecture, but I'd be the first to admit that I hardly am up to date > on what the rules of the road are now so such an opinion is > ill-informed. >=20 > Comment out ISP_SMPLOCK in isp_freebsd.h. If the problem goes away, > we'll make the change back again. I'll do what I can. > -matt >=20 > p.s.: you have *way* more issues here than locking- you've a bad disk. I know, but the system shouldn't blow up with a lock assertion in this failure mode. > Anyway, isn't alpha desupported? No. Kris --cNdxnHkX5QqsyA0e Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQE/lapAWry0BWjoQKURAmdmAJ4jlxkFzJyM6iclAjw94kcZNfiemACgikx8 kpyk8Vqu/bnkjeScNLeK6YI= =mv+T -----END PGP SIGNATURE----- --cNdxnHkX5QqsyA0e--