From: Brad Campbell <brad@wasp.net.au>
To: linux-ide@vger.kernel.org
Subject: Libata VIA woes continue. Worked around
Date: Fri, 27 Aug 2004 17:58:02 +0400 [thread overview]
Message-ID: <412F3DEA.2070307@wasp.net.au> (raw)
Ok, so after a couple of reboots with max_sector set to 200 the problem re-occurs.
It must be something to do with programming the controller or timing or some other issue.
I have worked around it by putting my 2 raid-0 drives on my spare promise ports, and at UDMA100 with
transfers of 2048 sectors they behave fine no matter what I throw at them.
It seems with the VIA interface it either works first time for a big transfer or it does not,
depending on the cold boot.
If I power cycle the machine 5 times it might work perfectly 3 out of 5 and if it works ok for the
first couple of transfers it will work ok for the entire uptime of the machine. If not then it locks
the interface up.
I'm going to sit on it for a few days. It's no longer an issue for me and perhaps I'll stop chasing
it until someone else reports a similar issue with a VIA controller.
I'll see if I can jam my 2 new Maxtors in the machine on these VIA ports and give them a good
workout. I only rebooted the machine 3 times with them connected and I might have been lucky with 3
working reboots. (There is only so many times you want to power cycle a box that has 15 hard disks
in it!)
Regards,
Brad (Dazed, confused and a little narked!)
next reply other threads:[~2004-08-27 13:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-27 13:58 Brad Campbell [this message]
2004-08-29 7:32 ` Libata VIA woes continue. Worked around - *wrong* Brad Campbell
2004-08-29 7:57 ` Jeff Garzik
2004-08-29 8:17 ` Brad Campbell
2004-08-29 9:04 ` Jeff Garzik
2004-08-29 9:24 ` Brad Campbell
2004-08-29 9:38 ` Jeff Garzik
2004-08-30 14:45 ` Larry McVoy
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=412F3DEA.2070307@wasp.net.au \
--to=brad@wasp.net.au \
--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).