Date: Thu, 16 Oct 2008 10:51:32 -0700 From: Jeremy Chadwick <koitsu@FreeBSD.org> To: "Andrey V. Elsukov" <bu7cher@yandex.ru> Cc: freebsd-stable@freebsd.org, kib@freebsd.org, sos@freebsd.org Subject: Re: Request for testing: ata(4) MFC Message-ID: <20081016175132.GA16172@icarus.home.lan> In-Reply-To: <20081016174525.GA16035@icarus.home.lan> References: <676151223134689@webmail38.yandex.ru> <20081005004808.GA70137@icarus.home.lan> <48E99C18.6070602@yandex.ru> <20081006051211.GA10542@icarus.home.lan> <20081010115855.GA31707@icarus.home.lan> <20081016071700.GA2793@icarus.home.lan> <20081016174525.GA16035@icarus.home.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Oct 16, 2008 at 10:45:25AM -0700, Jeremy Chadwick wrote: > On Thu, Oct 16, 2008 at 12:17:00AM -0700, Jeremy Chadwick wrote: > > On Fri, Oct 10, 2008 at 04:58:55AM -0700, Jeremy Chadwick wrote: > > > On Sun, Oct 05, 2008 at 10:12:11PM -0700, Jeremy Chadwick wrote: > > > > On Mon, Oct 06, 2008 at 09:03:20AM +0400, Andrey V. Elsukov wrote: > > > > > Jeremy Chadwick wrote: > > > > >> Also, does your patch include any fixes (intentional or inadvertent) for > > > > >> Intel MatrixRAID? This has been a sore spot for FreeBSD for quite > > > > >> some time, and I'm curious to know if that has been fixed. > > > > > > > > > > There is only one fix for Intel Matrix RAID: > > > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/121899 > > > > > > > > Ahh, yeah, I've seen that one as well. I'll apply the patch and let you > > > > know if the behaviour documented in the PR happens. > > > > > > I'm sorry I haven't gotten around to testing this -- my day (night) job > > > has kept me incredibly busy, and I've had hardly any time at home to > > > work on personal projects. It sucks. > > > > > > I'll try to make time for testing either today or tomorrow. > > > > I finally got around to testing this patch tonight on my P4SCE box. > > And I just ran into a problem with the new patch. First time I've ever > seen this. Machine has been rebooted a couple times this morning, > nothing out of the ordinary > where (machine has been rebooted a few times, had no problem). First > time I've seen it: I'm having vim problems too, apparently. :-) I wish I knew why "gq}" behaves differently depending upon the amount of time between hitting the "q" key and the "}" key. My quoted paragraph should have read: > And I just ran into a problem with the new patch. First time I've ever > seen this. Machine has been rebooted a couple times this morning, > nothing out of the ordinary. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20081016175132.GA16172>