From owner-freebsd-current@FreeBSD.ORG  Mon Mar  1 12:47:20 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 B60CA16A4CE
	for <freebsd-current@freebsd.org>;
	Mon,  1 Mar 2004 12:47:20 -0800 (PST)
Received: from smtp.mho.com (smtp.mho.net [64.58.4.5])
	by mx1.FreeBSD.org (Postfix) with SMTP id 7140E43D2D
	for <freebsd-current@freebsd.org>;
	Mon,  1 Mar 2004 12:47:20 -0800 (PST)
	(envelope-from scottl@freebsd.org)
Received: (qmail 74795 invoked by uid 1002); 1 Mar 2004 20:47:19 -0000
Received: from unknown (HELO ?10.4.1.17?) (64.58.1.252)
  by smtp.mho.net with SMTP; 1 Mar 2004 20:47:19 -0000
Date: Mon, 1 Mar 2004 13:49:33 -0700 (MST)
From: Scott Long <scottl@freebsd.org>
X-X-Sender: scottl@pooker.samsco.home
To: Jonathan Weiss <tomonage2@gmx.de>
In-Reply-To: <BC695E88.DE6A%tomonage2@gmx.de>
Message-ID: <20040301134622.I12830@pooker.samsco.home>
References: <BC695E88.DE6A%tomonage2@gmx.de>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: freebsd-current@freebsd.org
Subject: Re: mlx driver related kernel panic in Freebsd 5.2.1-RELEASE
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Mar 2004 20:47:20 -0000

On Mon, 1 Mar 2004, Jonathan Weiss wrote:
> >
> > Great to hear, thanks a lot for testing it.  It looks like the problem can
> > manifest itself when a whole lot of I/O comes into the driver at once.  An
> > easy way that I've found to generate a pattern like this is to turn
> > softupdates off, then start 5-10 concurrent copies of large trees with
> > lots of files.  Then when the pagedaemon does its 30-second interval run,
> > it'll likely send 500-1000 i/o requests at once to the card.
> >
> > Scott
>
> Hi Scott,
>
>
> Can you please backport the patch to 5.2.1?
>
> Thanks,
> Jonathan

Unfortunately, no.  The RELENG_5_2 branch is closed to all but security
fixes from now on.  Had I known about this problem before 5.2.1 was
released then I would have made sure that it was fixed before the release.

Scott