linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Ethan Chen <thanatoz@ucla.edu>,
	linux-kernel@vger.kernel.org,
	Carlos Pardo <Carlos.Pardo@siliconimage.com>,
	Linux-ide <linux-ide@vger.kernel.org>
Subject: Re: SIL_QUIRK_MOD15WRITE workaround problem on 2.6.14
Date: Mon, 05 Dec 2005 01:44:15 +0900	[thread overview]
Message-ID: <43931CDF.3080202@gmail.com> (raw)
In-Reply-To: <438FAADC.6060907@pobox.com>

Jeff Garzik wrote:
> Tejun Heo wrote:
> 
>> Ethan confirmed that it's 1095:3114.  Arghhh....  Maybe we should keep 
>> m15w quirk for 3114's for the time being?  Better be slow than hang. 
>> Whatever bug the m15w quirk was hiding.
> 
> 
> A generic 'slow_down_io' module option is reasonable.
> 
> It is not appropriate to apply mod15write quirk to hardware that isn't 
> affected by the chip bug.
> 
> A better solution is to write a 311x-specific interrupt handler.
> 

Hello, Jeff.  Hello, Carlos.

I bought a sii3114 controller yesterday and took out my ST3120026AS for 
testing.  The drive times out during a WRITE_EXT, and locks up.

* The ST3120026AS works perfectly on a VIA controller.
* The sii3114 controller works perfectly with Maxtor 6B080M0 drives.

I don't know.  It acts and smells like m15w problem.  What are the odds 
of having the same symptom on the same combination?

Also, I've asked one of my friends who has a sii3512 onboard controller 
and an affected seagate drive to test.  The harddisk works on 2.6.13 
with the quirk, but it freezes on 2.6.14.  m15w affected seagate drives 
does _NOT_ work on 3512 and 3114 on 2.6.14, be it m15w or something else.

-- 
tejun

  reply	other threads:[~2005-12-04 16:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <438BD351.60902@ucla.edu>
2005-11-30  4:16 ` SIL_QUIRK_MOD15WRITE workaround problem on 2.6.14 Tejun Heo
2005-11-30  4:42   ` Jeff Garzik
2005-11-30  5:37     ` Tejun Heo
2005-12-02  2:01       ` Jeff Garzik
2005-12-04 16:44         ` Tejun Heo [this message]
2005-12-05 18:41           ` Jeff Garzik
2005-11-30  4:48   ` Ethan Chen

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=43931CDF.3080202@gmail.com \
    --to=htejun@gmail.com \
    --cc=Carlos.Pardo@siliconimage.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thanatoz@ucla.edu \
    /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).