linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Francois Payette <francoisp@netmosphere.net>
Cc: Jeff Garzik <jgarzik@pobox.com>,
	linux-ide@vger.kernel.org, Eric Mudama <edmudama@gmail.com>
Subject: Re: SATA150TX4 atat1:command timeout
Date: Fri, 18 Feb 2005 11:40:52 -0500	[thread overview]
Message-ID: <42161A94.1020404@netmosphere.net> (raw)
In-Reply-To: <421360ED.2040505@netmosphere.net>

It seems that the locking problem we were experiencing was related to 
the disparities of drives in a raid 0 array; when we replaced the 
6Y200M0 with another 6B200S0 the problem never reappeared even after 1.8 
TB of io. Thanks a buch to Eric for pointing out the differences; the 
promise card and/or driver must have a problem with the bridge chip on 
that drive when interfacing with another drive that does not have that 
chip. We also tested for performance improvements with

writel(tmp, mmio + PDC_TBG_MODE);

commented out from pdc_host_init, but it does not cause a significant 
difference when benchmarked with bonnie++.

Thanks for your help,
Francois

  reply	other threads:[~2005-02-18 16:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-14 21:41 SATA150TX4 atat1:command timeout Francois Payette
2005-02-14 22:35 ` Jeff Garzik
2005-02-16 15:04   ` Francois Payette
2005-02-18 16:40     ` Francois Payette [this message]
2005-09-30 10:40       ` Robin Bowes
2005-10-06  9:55         ` Ian Oliver
2005-10-06 10:44           ` Erik Slagter
2005-10-13 20:37             ` Ian Oliver
2005-10-13 21:04               ` Mark Lord
2005-10-14 10:17                 ` Ian Oliver
2005-10-14 13:07                   ` Mark Lord
2005-10-14 10:00               ` Erik Slagter
2005-10-14 16:00                 ` Ian Oliver
2005-10-17 10:08                   ` Erik Slagter
2005-10-17 13:01                     ` Ian Oliver

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=42161A94.1020404@netmosphere.net \
    --to=francoisp@netmosphere.net \
    --cc=edmudama@gmail.com \
    --cc=jgarzik@pobox.com \
    --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).