From owner-freebsd-current@FreeBSD.ORG Mon Mar 1 13:09:05 2004 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 5ED0416A4CE; Mon, 1 Mar 2004 13:09:05 -0800 (PST) Received: from rwcrmhc13.comcast.net (rwcrmhc13.comcast.net [204.127.198.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3B01343D31; Mon, 1 Mar 2004 13:09:05 -0800 (PST) (envelope-from julian@elischer.org) Received: from interjet.elischer.org ([24.7.73.28]) by comcast.net (rwcrmhc13) with ESMTP id <200403012109000150049kcse>; Mon, 1 Mar 2004 21:09:04 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id NAA62439; Mon, 1 Mar 2004 13:09:00 -0800 (PST) Date: Mon, 1 Mar 2004 13:08:59 -0800 (PST) From: Julian Elischer To: Scott Long In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Jonathan Weiss 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Mar 2004 21:09:05 -0000 > > On Mon, 1 Mar 2004, Scott Long wrote: > > > 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. At least an errata item referring to a patch > >