From owner-freebsd-hackers@FreeBSD.ORG Fri Dec 5 08:46:45 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1D1B916A4CE for ; Fri, 5 Dec 2003 08:46:45 -0800 (PST) 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 21CC643F93 for ; Fri, 5 Dec 2003 08:46:44 -0800 (PST) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id CABF666D1F; Fri, 5 Dec 2003 08:46:43 -0800 (PST) Date: Fri, 5 Dec 2003 08:46:43 -0800 From: Kris Kennaway To: Dwayne MacKinnon Message-ID: <20031205164643.GB3672@xor.obsecurity.org> References: <200311262104.hAQL4ICN024652@spider.deepcore.dk> <200311282057.hASKvUOM002734@apollo.backplane.com> <3FD0AF18.9020304@xwave.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="s/l3CgOIzMHHjg/5" Content-Disposition: inline In-Reply-To: <3FD0AF18.9020304@xwave.com> User-Agent: Mutt/1.4.1i cc: Matthew Dillon cc: hackers@freebsd.org cc: Soren Schmidt Subject: Re: Problems with use of M_NOWWAIT in ATA X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Dec 2003 16:46:45 -0000 --s/l3CgOIzMHHjg/5 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Dec 05, 2003 at 11:15:20AM -0500, Dwayne MacKinnon wrote: > Hi, >=20 > I'm wondering if this could possibly be related to a problem I was=20 > having with my 4.9-RELEASE box. Twice in two days it hung on me=20 > completely, and started spouting the following error messages: Well, the error condition Matt is talking about only occurs if you had run your system completely out of kernel memory. That's not likely; far more likely is that you have a dodgy drive, controller or cabling. Kris --s/l3CgOIzMHHjg/5 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQE/0LZzWry0BWjoQKURAvs1AJ0SivwT7SmTJ16AZn/QMm7V2J4CbwCeLFBq Tc4B9AOh+iH+0Z3HmS3l7EI= =rpUA -----END PGP SIGNATURE----- --s/l3CgOIzMHHjg/5--