* sata_sil + UDMA CRC errors
@ 2005-08-25 13:51 Alexander Shaposhnikov
0 siblings, 0 replies; 4+ messages in thread
From: Alexander Shaposhnikov @ 2005-08-25 13:51 UTC (permalink / raw)
To: linux-ide; +Cc: htejun
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* sata_sil + UDMA CRC errors
@ 2005-08-25 13:53 Alexander Shaposhnikov
2005-08-25 14:03 ` Yuri Kirsanov
0 siblings, 1 reply; 4+ messages in thread
From: Alexander Shaposhnikov @ 2005-08-25 13:53 UTC (permalink / raw)
To: linux-ide
Cc: Carlos.Pardo@siliconimage.com, lbattraw@insightbb.com,
jgarzik@pobox.com, htejun
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: sata_sil + UDMA CRC errors
2005-08-25 13:53 Alexander Shaposhnikov
@ 2005-08-25 14:03 ` Yuri Kirsanov
0 siblings, 0 replies; 4+ messages in thread
From: Yuri Kirsanov @ 2005-08-25 14:03 UTC (permalink / raw)
To: Alexander Shaposhnikov, linux-ide; +Cc: Carlos.Pardo, lbattraw, jgarzik, htejun
I have exactly the same problem with Silicon controller...
----- Original Message -----
From: "Alexander Shaposhnikov" <shaposh@isp.nsc.ru>
To: <linux-ide@vger.kernel.org>
Cc: <Carlos.Pardo@siliconimage.com>; <lbattraw@insightbb.com>;
<jgarzik@pobox.com>; <htejun@gmail.com>
Sent: Thursday, August 25, 2005 5:53 PM
Subject: sata_sil + UDMA CRC errors
> 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
>
>
>
>
>
>
>
>
>
>
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-ide" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
^ permalink raw reply [flat|nested] 4+ messages in thread
* RE: sata_sil + UDMA CRC errors
@ 2005-08-25 15:00 Carlos Pardo
0 siblings, 0 replies; 4+ messages in thread
From: Carlos Pardo @ 2005-08-25 15:00 UTC (permalink / raw)
To: Yuri Kirsanov, Alexander Shaposhnikov, linux-ide, Paul Taylor
Cc: lbattraw, jgarzik, htejun
Paul,
Are there any issues with the ASUS K8N-DL board that you recall ?
Carlos
-----Original Message-----
From: Yuri Kirsanov [mailto:flash@rccb.ru]
Sent: Thursday, August 25, 2005 7:04 AM
To: Alexander Shaposhnikov; linux-ide@vger.kernel.org
Cc: Carlos Pardo; lbattraw@insightbb.com; jgarzik@pobox.com; htejun@gmail.com
Subject: Re: sata_sil + UDMA CRC errors
I have exactly the same problem with Silicon controller...
----- Original Message -----
From: "Alexander Shaposhnikov" <shaposh@isp.nsc.ru>
To: <linux-ide@vger.kernel.org>
Cc: <Carlos.Pardo@siliconimage.com>; <lbattraw@insightbb.com>;
<jgarzik@pobox.com>; <htejun@gmail.com>
Sent: Thursday, August 25, 2005 5:53 PM
Subject: sata_sil + UDMA CRC errors
> 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
>
>
>
>
>
>
>
>
>
>
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-ide" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2005-08-25 14:57 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-08-25 13:51 sata_sil + UDMA CRC errors Alexander Shaposhnikov
-- strict thread matches above, loose matches on Subject: below --
2005-08-25 13:53 Alexander Shaposhnikov
2005-08-25 14:03 ` Yuri Kirsanov
2005-08-25 15:00 Carlos Pardo
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).