From owner-freebsd-stable@FreeBSD.ORG Thu Mar 16 18:45:18 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4692216A433 for ; Thu, 16 Mar 2006 18:45:18 +0000 (UTC) (envelope-from jason.harmening@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id B98C143D4C for ; Thu, 16 Mar 2006 18:45:08 +0000 (GMT) (envelope-from jason.harmening@gmail.com) Received: by zproxy.gmail.com with SMTP id 8so393809nzo for ; Thu, 16 Mar 2006 10:45:08 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=F/wfNVKvJ7dyz7yKnVB4AUWkuju0Al4cn3OsVslHKBXqcZH82fLkyX9yNP3SuTgnMYWDgEYKJhYU+7P60eN86Ukk4ca4HoPcB2gu41xsMT0s1i8t6GvFVOJh/eOanRi+DpesCc4pzOwOinBJ55jKFhbKGCKxSAzmEzN+9BfC90U= Received: by 10.36.251.80 with SMTP id y80mr2661234nzh; Thu, 16 Mar 2006 10:45:07 -0800 (PST) Received: by 10.36.158.4 with HTTP; Thu, 16 Mar 2006 10:45:07 -0800 (PST) Message-ID: <2d1264630603161045t31774a33h9cec88c4b7d6d13d@mail.gmail.com> Date: Thu, 16 Mar 2006 12:45:07 -0600 From: "Jason Harmening" To: freebsd-stable@freebsd.org, freebsd-bugs@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: [6.1-PRERELEASE/amd64] Kernel panic during heavy UFS traffic X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Mar 2006 18:45:18 -0000 Last night I ran into a series of kernel panics that seemed to be related t= o heavy UFS traffic. I ran into two consecutive panics when trying to mount = 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 tried 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 system hang, followed by the automatic reboot. 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 soli= d 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. Thanks, Jason Harmening