All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Shaposhnikov <shaposh@isp.nsc.ru>
To: linux-ide@vger.kernel.org
Cc: htejun@gmail.com
Subject: sata_sil + UDMA CRC errors
Date: Thu, 25 Aug 2005 20:51:15 +0700	[thread overview]
Message-ID: <1124977875.2949.10.camel@m00> (raw)

Good time of the day.
I think this might be a bug in sata_sil driver.

I have ASUS K8N-DL board with onborad sil3114 controller. As support for
nVidia Nforce 2200 SATA is broken in current sata_nv driver, i have to
use sil3114. Kernel is 2.6.13-rc6 + "sata_sil Mod15Write
quirk workaround" patch of TeJun Heo. OS is Fedora4 x86_64

There are two SATA drives, Seagate 7200.7 160Gb and Samsung SP0812C
80Gb. 

Here is the problem: 
Any intensive read/write activity results in alot of UDMA CRC errors for both drives.
I am getting :
ata1: status=0x51 { DriveReady SeekComplete Error }
ata1: error=0x04 { DriveStatusError }
kernel messages. With the patch applied, error rate is significantly low
for Seagate drive; Samsung is still virtually unusable. 
I checked SMART attributes, and the count of  UDMA CRC errors is ~200
for Seagate and more than 1000 for Samsung. Every time i get new
"status=0x51" errors for any drive, number of UDMA CRC errors grow
accordingly. 

But there seems to be no problems under Windows. Even highest read/write
activity do not generate any new CRC errors. 

Sorry for bad english.

Best Regards,
Alexander Shaposhnikov


 










             reply	other threads:[~2005-08-25 13:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-25 13:51 Alexander Shaposhnikov [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-08-25 13:53 sata_sil + UDMA CRC errors Alexander Shaposhnikov
2005-08-25 14:03 ` Yuri Kirsanov
2005-08-25 15:00 Carlos Pardo

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=1124977875.2949.10.camel@m00 \
    --to=shaposh@isp.nsc.ru \
    --cc=htejun@gmail.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 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.