From owner-freebsd-current@FreeBSD.ORG Sat Apr 16 02:56:50 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 C6FC416A4CE for ; Sat, 16 Apr 2005 02:56:50 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id A56F943D41 for ; Sat, 16 Apr 2005 02:56:50 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 9709F72DE4; Fri, 15 Apr 2005 19:56:50 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 917EB72DDB; Fri, 15 Apr 2005 19:56:50 -0700 (PDT) Date: Fri, 15 Apr 2005 19:56:50 -0700 (PDT) From: Doug White To: Daniel Eriksson In-Reply-To: Message-ID: <20050415195545.W38788@carver.gumbysoft.com> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: 'FreeBSD Current' 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 02:56:50 -0000 On Fri, 15 Apr 2005, Daniel Eriksson wrote: > 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. Sorry, we don't guarantee 4 hour response -- that costs money. :) > 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? I don't think so... nullfs has it sown problems, but not random memory corruption. Next time, could you make the crashdump and debug kernel available for download? -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org