All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Andi Kleen <ak@suse.de>
Cc: 7091@blargh.com, linux-ide@vger.kernel.org, jgarzik@pobox.com,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: sata_sil, writing bug with multiple cards?
Date: Wed, 04 Jul 2007 17:52:13 +0900	[thread overview]
Message-ID: <468B5FBD.3040104@gmail.com> (raw)
In-Reply-To: <200707041038.57677.ak@suse.de>

Andi Kleen wrote:
> On Wednesday 04 July 2007 10:17:34 7091@blargh.com wrote:
> 
>>> Most likely it is some sort of hardware bug that we might
>>> not be able to do much about. Have you tried contacting SIL or VIA? 
>> No, I haven't.  Like I mentioned above, the OpenBSD drivers seemed to work, 
>> or at least did with similar tests.  I would need to run the more extensive 
>> checks to be positive, but those take a lot of time, obviously.  And 
>> downtime for the box, a lot of which isn't really manageable, at the moment. 
> 
> Perhaps the OpenBSD drivers program the SIL chip in a different way
> that avoids this problem. 
> 
>>> e.g. if you have some other system with a different chipset it might
>>> be useful to test the SIL controllers in those.
>> The previous motherboard was an AMD 760 chipset, and it had the same 
>> problem. 
> 
> Ok this means it's likely a SIL issue, not a chipset issue.

Hmmmm... okay.  I'll take look at the openBSD driver.  I still have no
idea what it can be tho.  Maybe, FIFO setup?

Thanks.

-- 
tejun

  reply	other threads:[~2007-07-04  8:52 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-03  6:42 sata_sil, writing bug with multiple cards? 7091
2007-07-03  8:51 ` Tejun Heo
2007-07-04  1:40   ` 7091
2007-07-04  1:48     ` Tejun Heo
2007-07-04  2:05   ` 7091
2007-07-04  3:22     ` 7091
2007-07-04  3:44       ` 7091
2007-07-04  3:53         ` Tejun Heo
2007-07-04  7:08           ` Andi Kleen
2007-07-04  8:17             ` 7091
2007-07-04  8:38               ` Andi Kleen
2007-07-04  8:52                 ` Tejun Heo [this message]
2007-07-10 10:55                   ` Tejun Heo
2007-07-12  3:21                     ` 7091
2007-07-04  3:41     ` Tejun Heo
2007-07-04  9:18     ` Alan Cox
2007-07-04  9:14       ` Tejun Heo
2007-07-04  9:26       ` 7091
  -- strict thread matches above, loose matches on Subject: below --
2007-06-27 21:36 7091
2007-07-08  8:01 ` Janos Haar

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=468B5FBD.3040104@gmail.com \
    --to=htejun@gmail.com \
    --cc=7091@blargh.com \
    --cc=ak@suse.de \
    --cc=jgarzik@pobox.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.