From: raz0@tiscali.dk
To: linux-kernel@vger.kernel.org
Subject: Re: dma errors with sata_sil and Seagate disk
Date: Sat, 25 Dec 2004 22:02:28 +0100 [thread overview]
Message-ID: <41C1920E0000073B@cpfe6.be.tisc.dk> (raw)
Hi,
I was wondering whether you know how this bug is dealt with in the siI Windows
drivers. Are they also using some fix that limits the performance? I remember
my friend pulling a file via a cross-over cable (ie: no switch) with some
26megs/s, so I guess not? Would you be so kind to explain this to me? :)
I'm running 2.6.10-rc3 with the blacklisted ST3120026A on the SiI 3512A
controller. When I try 'hdparm -t /dev/sda', I get this:
raz0:/home/morten# hdparm -t /dev/sda
/dev/sda:
Timing buffered disk reads: 46 MB in 3.08 seconds = 14.94 MB/sec
HDIO_DRIVE_CMD(null) (wait for flush complete) failed: Inappropriate ioctl
for device
Is this the same bug? I haven't noticed any problems other than the hdparm
one.
Please CC me if you reply; I am not on the list.
Morten
>> I've never been able to get a non NDA list of the affected drives. Got
>> to love vendors some days
>
>I seriously doubt a complete list exists, NDA or no. You'd have to poll
>each vendor.
>
>I also suspect that a few of the more recent Seagate additions are
>simply masking a problem in the BIOS.
>
>SiI 311x problems have a history of resolving themselves through BIOS
>updates and tweaks. Most recently a lockup was solved by tweaking a
>'byte enable' setting in an nForce mobo BIOS.
>
> Jeff
next reply other threads:[~2004-12-25 21:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-25 21:02 raz0 [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-01 17:50 dma errors with sata_sil and Seagate disk John Lash
2004-12-01 23:41 ` Alan Cox
2004-12-02 4:28 ` John Lash
2004-12-02 10:01 ` Måns Rullgård
2004-12-02 23:33 ` Alan Cox
2004-12-03 1:14 ` Måns Rullgård
2004-12-03 4:07 ` Jeff Garzik
2004-12-03 4:19 ` John Lash
2004-12-03 4:05 ` Jeff Garzik
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=41C1920E0000073B@cpfe6.be.tisc.dk \
--to=raz0@tiscali.dk \
--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.