From: Tejun Heo <htejun@gmail.com>
To: Florian Effenberger <florian@effenberger.org>
Cc: linux-ide@vger.kernel.org, jeff@garzik.org
Subject: Re: libata interface fatal error
Date: Thu, 14 Jun 2007 18:43:56 +0900 [thread overview]
Message-ID: <46710DDC.1030900@gmail.com> (raw)
In-Reply-To: <466FC901.4060907@effenberger.org>
Florian Effenberger wrote:
> Hi Tejun,
>
>> Okay, there was a bug in link speed limit logic. That's probably why
>> speed down to 1.5Gbps didn't kick in. The attached patch contains the
>> fix and hack to force 1.5Gbps. Please give it a shot.
>
> thanks a lot for your patch, it seems to work, at least better than
> without patch. :-)
>
> When rsyncing about 12 GB, no trouble occured. When doing heavy stress
> tests, I receive errors again, but okay, maybe that's due to a hardware
> bug.
>
> Will your patch go into the vanilla kernel?
I'm currently not sure what the root cause is
1. if the controller is at fault, we need to force 1.5Gbps on the
controller.
2. if the drive model is broken, we need to blacklist the drives.
3. if your specific configuration is broken (faulty hw, PSU, bad karma),
the upstream speed limit fix patch should be enough.
Can you post the result of 'hdparm -I /dev/sdX'?
--
tejun
next prev parent reply other threads:[~2007-06-14 9:44 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-26 9:43 libata interface fatal error Florian Effenberger
2007-05-29 9:16 ` Tejun Heo
2007-05-29 14:16 ` Florian Effenberger
2007-06-06 21:23 ` Florian Effenberger
2007-06-07 9:50 ` Tejun Heo
2007-06-07 14:08 ` Florian Effenberger
2007-06-13 10:37 ` Florian Effenberger
2007-06-14 9:43 ` Tejun Heo [this message]
2007-06-14 11:12 ` Florian Effenberger
2007-06-14 12:25 ` Tejun Heo
2007-06-14 15:12 ` Florian Effenberger
2007-06-18 3:10 ` Tejun Heo
2007-06-18 6:08 ` Tomi Orava
2007-06-18 6:28 ` Tejun Heo
2007-06-18 10:38 ` Florian Effenberger
2007-06-18 10:44 ` Tejun Heo
2007-06-16 10:23 ` Florian Effenberger
2007-06-18 3:13 ` Tejun Heo
2007-06-18 10:44 ` Florian Effenberger
2007-06-18 10:56 ` Tejun Heo
2007-06-18 11:28 ` Florian Effenberger
2007-06-18 11:30 ` Tejun Heo
2007-06-18 11:32 ` Florian Effenberger
2007-06-24 11:32 ` Florian Effenberger
2007-06-25 2:49 ` Tejun Heo
2007-06-25 8:47 ` Florian Effenberger
-- strict thread matches above, loose matches on Subject: below --
2007-06-18 7:05 Mikael Pettersson
2007-06-18 7:13 ` Tejun Heo
2007-06-18 10:47 ` Florian Effenberger
2007-06-18 17:14 ` Ansgar Knappheide
2007-06-18 18:54 ` Tomi Orava
2007-05-24 13:25 Florian Effenberger
2007-05-24 13:45 ` Tejun Heo
2007-05-24 14:08 ` Florian Effenberger
2007-05-24 14:21 ` Tejun Heo
2007-05-24 14:47 ` Florian Effenberger
2007-05-24 14:53 ` Tejun Heo
2007-05-24 15:28 ` Florian Effenberger
2007-05-24 14:55 ` Greg Freemyer
2007-05-24 14:59 ` Tejun Heo
2007-05-24 15:00 ` Florian Effenberger
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=46710DDC.1030900@gmail.com \
--to=htejun@gmail.com \
--cc=florian@effenberger.org \
--cc=jeff@garzik.org \
--cc=linux-ide@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).