From: "Johny Ågotnes" <johny@agotnes.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Ryan Bourgeois <rgb005@latech.edu>,
Danny Cox <Danny.Cox@ECWeb.com>,
Linux IDE List <linux-ide@vger.kernel.org>
Subject: Re: Which SATA Combos To Consider?
Date: Tue, 22 Feb 2005 09:50:20 +1000 [thread overview]
Message-ID: <421A73BC.9070604@agotnes.com> (raw)
In-Reply-To: <20050218005228.GA1228@havoc.gtf.org>
Jeff,
I swapped cables and tried 3 different RAM chips, so yep, did that :)
Question on that - does the RAM 'matter' as the driver doesn't use it?
I.e. is it used by the onboard control logic as cache?
Also tried moving the card to different PCI slots, still no luck :(
Now that server is my home server running off PATA drives, the SX4 card
is sitting gathering dust (as I said) until I get my old PC operational
again and can put the card in to re-test.
A few people seem to have this problem, so it is definitely worthwhile
having a look at, I'd love to have a go just out of my own curiousity.
Closest I've been to this kinda programming is interfacing with
telephone switches for softphone and ACD functionality, I'm hoping
that'll help me get a grasp in the interrupt driven space of hardware! :)
All I need is a bit of time ;)
:)J
Jeff Garzik wrote:
> On Fri, Feb 18, 2005 at 10:44:57AM +1000, Johny Ågotnes wrote:
>
>>Just a quick note on the SX4 Card - I have seen data corruption on
>>hard-drives too in the simplest possible setup, so I'd stay clear of
>>that card until further notice.
>>
>>Mine is sitting in a cupboard right now, awaiting 'someone' (me, if I
>>get some time to learn low-level kernel drivers) debugging the issue.
>>
>>Basically, accessing two drives via this card causes corruption, I had
>>it working ok when I only accessed 1 drive, which is kinda pointless...
>
>
> I've not need about to reproduce this in the lab.
>
> Have you tried switching out RAM and cables?
>
> Jeff
>
>
>
next prev parent reply other threads:[~2005-02-21 23:50 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-16 4:28 libata oops 2.6.11-rc4 yesterdays BK Brad Campbell
2005-02-16 11:01 ` Brad Campbell
2005-02-16 17:25 ` Jeff Garzik
2005-02-16 20:54 ` Brad Campbell
2005-02-16 21:40 ` Andy Warner
2005-02-16 22:47 ` Jeff Garzik
2005-02-16 23:49 ` Andy Warner
2005-02-16 23:58 ` Jeff Garzik
2005-02-17 0:20 ` Andy Warner
2005-02-17 5:08 ` Jeff Garzik
2005-02-17 14:59 ` Andy Warner
2005-02-17 19:13 ` Jeff Garzik
2005-02-17 19:25 ` Andy Warner
2005-02-17 22:36 ` Jeff Garzik
2005-02-17 19:42 ` Which SATA Combos To Consider? Danny Cox
2005-02-17 20:55 ` Jeff Garzik
2005-02-18 0:25 ` Ryan Bourgeois
2005-02-18 0:44 ` Johny Ågotnes
2005-02-18 0:52 ` Jeff Garzik
2005-02-21 23:50 ` Johny Ågotnes [this message]
2005-02-21 23:50 ` Johny Ågotnes
2005-02-22 1:55 ` Johny Ågotnes
2005-02-18 6:13 ` libata oops 2.6.11-rc4 yesterdays BK Brad Campbell
2005-02-19 4:14 ` Brad Campbell
2005-02-21 4:27 ` Brad Campbell
2005-02-22 10:09 ` Brad Campbell
-- strict thread matches above, loose matches on Subject: below --
2005-02-21 9:25 Which SATA Combos To Consider? linux
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=421A73BC.9070604@agotnes.com \
--to=johny@agotnes.com \
--cc=Danny.Cox@ECWeb.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=rgb005@latech.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).