From owner-freebsd-bugs@FreeBSD.ORG Thu Mar 16 19:54:07 2006 Return-Path: X-Original-To: freebsd-bugs@freebsd.org Delivered-To: freebsd-bugs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A202616A400; Thu, 16 Mar 2006 19:54:07 +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 5FA4743D46; Thu, 16 Mar 2006 19:54:07 +0000 (GMT) (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 45E261A4EB7; Thu, 16 Mar 2006 11:54:07 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 9D571525C5; Thu, 16 Mar 2006 14:54:06 -0500 (EST) Date: Thu, 16 Mar 2006 14:54:06 -0500 From: Kris Kennaway To: Jason Harmening Message-ID: <20060316195406.GA30669@xor.obsecurity.org> References: <2d1264630603161045t31774a33h9cec88c4b7d6d13d@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="2oS5YaxWCcQjTEyO" Content-Disposition: inline In-Reply-To: <2d1264630603161045t31774a33h9cec88c4b7d6d13d@mail.gmail.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-bugs@freebsd.org, freebsd-stable@freebsd.org Subject: Re: [6.1-PRERELEASE/amd64] Kernel panic during heavy UFS traffic X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Mar 2006 19:54:07 -0000 --2oS5YaxWCcQjTEyO Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Mar 16, 2006 at 12:45:07PM -0600, Jason Harmening wrote: > Last night I ran into a series of kernel panics that seemed to be related= to > heavy UFS traffic. I ran into two consecutive panics when trying to moun= t a > UFS-formatted DVD-RAM as a regular user (though not when I mounted it as > root). The system seemed to actually succeed in mounting the disk, as it > was marked dirty after the ensuing panic. Upon rebooting after the second > panic, I saw another two consecutive panics which happened whenever I tri= ed > to do something fairly disk-intensive (e.g. starting the X server + KDE) > while the bgfsck was still running from the last panic. Ultimately I > rebooted in single-user mode, ran fsck manually, and have experienced no > further panics. I suspect these panics may be related to UFS deadlocks, = as > in all cases the application that was attempting disk access hung for > several seconds before the panic, followed by a few seconds of total syst= em > hang, followed by the automatic reboot. >=20 > I'm running 6.1-PRELEASE/amd64 from 12 March on an Athlon 64 x2 (SMP) with > SCHED_ULE+PREEMPTION--dangerous combination I know, but it's been rock so= lid > for months until now. If anyone is interested, I'll try to reproduce this > panic with a dump/backtrace. It may be one of the UFS deadlock issues > that's already under investigation for 6.1-RELEASE. Yeah, we need a trace. Kris --2oS5YaxWCcQjTEyO Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFEGcJeWry0BWjoQKURApTnAKC7IVWS6WdDqobCrXC/2JgWWQClDACgkMQB 1NDxxxUycz4rRP3dwBFo1Pc= =urCZ -----END PGP SIGNATURE----- --2oS5YaxWCcQjTEyO--