From: Jeff Garzik <jeff@garzik.org>
To: Dave Dillow <dave@thedillows.org>
Cc: dean gaudet <dean@arctic.org>,
linux-ide@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH, RFT, v4] sata_mv: convert to new EH
Date: Sat, 26 May 2007 17:38:38 -0400 [thread overview]
Message-ID: <4658A8DE.80107@garzik.org> (raw)
In-Reply-To: <1180213892.19231.6.camel@obelisk.thedillows.org>
Dave Dillow wrote:
> On Sat, 2007-05-26 at 16:56 -0400, Jeff Garzik wrote:
>> Dave, any chance you could try 2.6.22-rc3 + my v4 patch, on a different
>> hard drive? Preferably a non-Maxtor, or at least not another Maxtor
>> 6L200S0. If that's a big deal, don't worry about it. I just want to
>> rule out buggy firmware and/or bad hard drive in your case.
>
> It is likely I can come up with at least one, and maybe two if I
> cannibalize my main machine... do you want results under all three
> kernels or just the v4 patch?
Mainly the v4 patch, but an it-works test on 2.6.22-rc3 just for
sanity's sake would be useful as well.
If you have time, check both new and old drives with SMART
smartctl -d ata -t long /dev/blahblah
to make sure the extended tests don't find anything wrong. Extended
tests usually take 30-90 minutes. You can access the hard drive while
the extended test is running, but I/O will be slower for obvious reasons.
Jeff
next prev parent reply other threads:[~2007-05-26 21:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-25 23:34 [PATCH, RFT, v2] sata_mv: convert to new EH Jeff Garzik
2007-03-02 0:54 ` Andre Tomt
2007-03-02 1:11 ` Jeff Garzik
2007-03-06 5:16 ` Dave Dillow
2007-03-06 5:26 ` Jeff Garzik
2007-03-06 6:01 ` Jeff Garzik
2007-03-06 6:53 ` dean gaudet
2007-03-06 6:57 ` Dave Dillow
2007-05-25 13:56 ` [PATCH, RFT, v3] " Jeff Garzik
2007-05-26 3:16 ` [PATCH, RFT, v4] " Jeff Garzik
2007-05-26 7:53 ` dean gaudet
2007-05-26 20:56 ` Jeff Garzik
2007-05-26 21:11 ` Dave Dillow
2007-05-26 21:38 ` Jeff Garzik [this message]
2007-05-27 1:46 ` Dave Dillow
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4658A8DE.80107@garzik.org \
--to=jeff@garzik.org \
--cc=dave@thedillows.org \
--cc=dean@arctic.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).