From: Tejun Heo <htejun@gmail.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Jeremy Smith <alceste@xmission.com>,
Alexander Shaposhnikov <shaposh@isp.nsc.ru>,
Carlos Pardo <Carlos.Pardo@siliconimage.com>,
Paul Taylor <Paul.Taylor@siliconimage.com>,
linux-ide@vger.kernel.org
Subject: Re: PROBLEM: Silicon Image 3112 Lockups
Date: Wed, 07 Sep 2005 11:34:02 +0900 [thread overview]
Message-ID: <431E519A.2090905@gmail.com> (raw)
In-Reply-To: <431E4CDA.6090909@pobox.com>
Jeff Garzik wrote:
> Tejun Heo wrote:
>
>> In the following mail, I've attached a patch which might alleviate
>> errors during writes (as Alexander was reporting CRC errors with write
>> commands), but it won't do any good if you're getting errors during
>> reading.
>>
>> http://marc.theaimsgroup.com/?l=linux-ide&m=112602112819183&w=2
>
>
> Note that I would put BIG CAPITAL LETTER WARNINGS on that patch, since
> it messes with the voltage.
>
Alexander & Jeremy.
It's as Jeff said.
TRY THE PATCH AT YOUR OWN RISK. IT MIGHT FRY PHY OF YOUR DRIVE.
(enough capitals?)
Even if you're brave enough to try, DO NOT GO OVER 600mV. 600mV is at
least inside specified limits. Also, it won't change anything regarding
read errors. All it does is increasing voltage swing while transmitting
data (writes).
Thanks.
--
tejun
next prev parent reply other threads:[~2005-09-07 2:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-07 1:07 PROBLEM: Silicon Image 3112 Lockups Jeremy Smith
2005-09-07 2:01 ` Tejun Heo
2005-09-07 2:13 ` Jeff Garzik
2005-09-07 2:34 ` Tejun Heo [this message]
2005-09-07 2:42 ` Tejun Heo
2005-09-07 3:21 ` Jeremy Smith
2005-09-07 6:00 ` Tejun Heo
2005-09-07 6:09 ` Jeff Garzik
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=431E519A.2090905@gmail.com \
--to=htejun@gmail.com \
--cc=Carlos.Pardo@siliconimage.com \
--cc=Paul.Taylor@siliconimage.com \
--cc=alceste@xmission.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=shaposh@isp.nsc.ru \
/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).