From owner-freebsd-current@FreeBSD.ORG Sat Apr 16 18:33:13 2005 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 0F91716A4CE for ; Sat, 16 Apr 2005 18:33:13 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.111]) by mx1.FreeBSD.org (Postfix) with ESMTP id AAF4243D55 for ; Sat, 16 Apr 2005 18:33:12 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id D6BD652048; Sat, 16 Apr 2005 11:33:11 -0700 (PDT) Date: Sat, 16 Apr 2005 11:33:11 -0700 From: Kris Kennaway To: Doug White Message-ID: <20050416183311.GA61065@xor.obsecurity.org> References: <20050415195545.W38788@carver.gumbysoft.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="MGYHOYXEY6WxJCY8" Content-Disposition: inline In-Reply-To: <20050415195545.W38788@carver.gumbysoft.com> User-Agent: Mutt/1.4.2.1i cc: 'FreeBSD Current' cc: Daniel Eriksson Subject: Re: task queue: supervisor write, page not present 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: Sat, 16 Apr 2005 18:33:13 -0000 --MGYHOYXEY6WxJCY8 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Apr 15, 2005 at 07:56:50PM -0700, Doug White wrote: > On Fri, 15 Apr 2005, Daniel Eriksson wrote: >=20 > > Doug White wrote: > > > > > Can you get a crashdump and inspect the taskq with gdb? I'm assuming > > > there's a bogus entry thats getting tripped over. > > > > Dang, I was running low on space and removed the dump I had just a few = hours > > ago since nobody had replied yet. >=20 > Sorry, we don't guarantee 4 hour response -- that costs money. :) >=20 > > Right now I'm back to running CURRENT as of 2005.03.11.12.00.00 (over a > > month old) because I know it works pretty well for me. > > > > I'm not very good with gdb. Are there any specific steps I should take = to > > get the information needed to track this down (if I upgrade to latest > > CURRENT again)? Could this be related to me using a lot of r/w nullfs > > mounts? >=20 > I don't think so... nullfs has it sown problems, but not random memory > corruption. Actually r/w nullfs used to work in 5.x and 6.x (and r/o still does), so if someone is seeing otherwise they need to report it. Kris --MGYHOYXEY6WxJCY8 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCYVpnWry0BWjoQKURAngjAJ9TlQOJgPPMf4v9WiWojLywmUnHEgCaAwUE ZrLkq/NMDYoiR1XPGLR6P00= =jyjP -----END PGP SIGNATURE----- --MGYHOYXEY6WxJCY8--