Date: Mon, 03 May 2004 08:35:34 -0600 From: Scott Long <scottl@freebsd.org> To: Mike Tancsa <mike@sentex.net> Cc: freebsd-stable@freebsd.org Subject: Re: [PATCH] Fix for 3ware driver Message-ID: <409658B6.6030208@freebsd.org> In-Reply-To: <6.0.3.0.0.20040503103007.066bfff0@64.7.153.2> References: <40965292.2040608@freebsd.org> <6.0.3.0.0.20040503101628.0831adb8@64.7.153.2> <40965696.4030505@freebsd.org> <6.0.3.0.0.20040503103007.066bfff0@64.7.153.2>
next in thread | previous in thread | raw e-mail | index | archive | help
Mike Tancsa wrote: > At 10:26 AM 03/05/2004, Scott Long wrote: > >> The bugs were introduced into 4.x with the vendor update that happened >> on April 7. So far the only cards that we have tested against have been >> 6xxx series cards. The bugs deal with resource shortage handling, so >> it's likely that the slower 6xxx cards are more likely than the newer >> cards to experience the problems. However, on a fast machine under >> heavy I/O load, I would expect it to happen on any card. > > > OK, I have a few machines on my work bench that I am happy to punish > without worry for data loss. Is there a script that can be run to > re-create the problem ? i.e. so I can test before and after ? > > ---Mike The tests that we were doing involved operating on a lot of small files. Doing something like untaring four or five copies of the FreeBSD source tree in parallel should probably trigger it. Scott
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?409658B6.6030208>