All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Chris Boot <bootc@bootc.net>
Cc: Jeff Garzik <jgarzik@pobox.com>,
	Linux-ide <linux-ide@vger.kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: SiI 3112A + Seagate HDs = still no go?
Date: Sat, 13 Aug 2005 23:59:26 +0900	[thread overview]
Message-ID: <42FE0ACE.6010506@gmail.com> (raw)
In-Reply-To: <EB750DA5-854F-4387-A5D7-F646EB8E7AAC@bootc.net>

Chris Boot wrote:
> Some interesting developments!
> 
> I installed a fresh copy of Windows, and all the VIA and nVidia and  so 
> on drivers. At some point during all this (a period of relatively  heavy 
> disk IO), the computer seemed to crash and I rebooted it. It  then 
> worked fine for a while, but during my perfmon testing it seemed  to do 
> the same thing. This time I left it for a while and it did  eventually 
> wake up again, so I'm guessing the controller is a bit  fubared. Perfmon 
> did indeed show several dips down to or very close  to 0 during the 
> write operation, with peaks up to 48 MB/sec, which is  pretty 
> respectable. So, time to replace the brand-new controller I  guess.
> 
> Now, do you think this is just my one particular controller card and  a 
> simple return would fix the problem, or is it more likely a problem  
> with the whole range? It's an Innovision EIO SATA controller: http:// 
> www.ivmm.com/eio/products/index.htm
> 
> Would it be a safer bet to go for the Adaptec controller of the same  
> variety? How reliable are they?

  I frankly don't know.  Maybe it's just one faulty controller, 
connector or whatever.  Maybe the card manufacturer screwed up 
somewhere.  I mean, the only course I took in electronics is 
introductory digital circuits which used 74xx chips and push triggered 
clock on a breadboard.  What would I know about gigahertz signaling 
error.  :-p

  Though, one thing I can say is majority of 311x controllers don't seem 
to suffer from this problem.  So, take your pick.

-- 
tejun

  reply	other threads:[~2005-08-13 14:59 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-11 21:55 SiI 3112A + Seagate HDs = still no go? Chris Boot
2005-08-12  3:24 ` Tejun Heo
2005-08-12 10:57   ` Chris Boot
2005-08-12 11:28     ` Tejun Heo
2005-08-12 11:33       ` Chris Boot
2005-08-12 13:23         ` Chris Boot
2005-08-12 14:08           ` Tejun Heo
2005-08-12 16:27             ` Chris Boot
2005-08-12 16:27             ` Chris Boot
2005-08-13  1:13               ` Tejun Heo
2005-08-13 12:14                 ` Chris Boot
2005-08-13 14:59                   ` Tejun Heo [this message]
2005-08-17 10:32                     ` SiI 3112A + Seagate HDs = still no go? [SOLVED] Chris Boot
2005-08-12 15:19 ` SiI 3112A + Seagate HDs = still no go? Roger Heflin
2005-08-12 15:19   ` Roger Heflin
2005-08-12 15:20   ` Chris Boot
2005-08-12 15:20     ` Chris Boot

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=42FE0ACE.6010506@gmail.com \
    --to=htejun@gmail.com \
    --cc=bootc@bootc.net \
    --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.