From owner-freebsd-current@FreeBSD.ORG Mon Mar 1 13:06:23 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 C3AFE16A4CE; Mon, 1 Mar 2004 13:06:23 -0800 (PST) Received: from sccrmhc13.comcast.net (sccrmhc13.comcast.net [204.127.202.64]) by mx1.FreeBSD.org (Postfix) with ESMTP id 51BA743D1D; Mon, 1 Mar 2004 13:06:23 -0800 (PST) (envelope-from julian@elischer.org) Received: from interjet.elischer.org ([24.7.73.28]) by comcast.net (sccrmhc13) with ESMTP id <20040301210622016005fpcje>; Mon, 1 Mar 2004 21:06:22 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id NAA62424; Mon, 1 Mar 2004 13:06:19 -0800 (PST) Date: Mon, 1 Mar 2004 13:06:18 -0800 (PST) From: Julian Elischer To: Scott Long In-Reply-To: <20040301134622.I12830@pooker.samsco.home> 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:06:23 -0000 isn't crashing the system a security problem :-) 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. > > Scott > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >