status reports updated
My Linux SATA software/hardware status reports have just been updated. To see where libata (SATA) support stands for a particular piece of hardware, or a particular feature, go to
http://linux.yyz.us/sata/
I've still got several patches from EMC (Brett) and IBM (Albert) to go through, as well as a few scattered ones from random authors.
I'm still working in BitKeeper for the time being.
Jeff
Jeff:
You need to add a comment about the SATAII TX2/TX4 boards indicating users have experienced data corruption with the sata_promise driver and the SATAII TX4 board.
I've posted several emails to linux-ide about this. Why haven't you responded?
Promise TX2/TX4
Summary: No TCQ/NCQ. Full SATA control including hotplug and PM on all.
[snip]
Update 2005/04/15: Support for the NCQ-capable SATAII TX2/TX4 boards was recently added. NCQ support is waiting on libata core.
Quoted 19 lines · Jeff Garzik
My Linux SATA software/hardware status reports have just been updated. To see where libata (SATA) support stands for a particular piece of hardware, or a particular feature, go to
http://linux.yyz.us/sata/I've still got several patches from EMC (Brett) and IBM (Albert) to go through, as well as a few scattered ones from random authors.
I'm still working in BitKeeper for the time being.
Jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Signature · 2 lines
Joe Harvell [email protected]
Quoted 8 lines · Joe Harvell
Jeff:
You need to add a comment about the SATAII TX2/TX4 boards indicating users have experienced data corruption with the
sata_promisedriver and the SATAII TX4 board.I've posted several emails to linux-ide about this. Why haven't you responded?
I've seen reports on the SX4, but not on the SATAII TX4.
URLs to messages you posted?
JEff
http://marc.theaimsgroup.com/?l=linux-ide&m=111029414823303&w=2
http://marc.theaimsgroup.com/?l=linux-ide&m=111054989026053&w=2
http://marc.theaimsgroup.com/?l=linux-ide&m=111214149529209&w=2
http://marc.theaimsgroup.com/?l=linux-ide&m=111230129320297&w=2
Quoted 16 lines · Jeff Garzik
Quoted 8 lines · Joe Harvell
Jeff:
You need to add a comment about the SATAII TX2/TX4 boards indicating users have experienced data corruption with the
sata_promisedriver and the SATAII TX4 board.I've posted several emails to linux-ide about this. Why haven't you responded?
I've seen reports on the SX4, but not on the SATAII TX4.
URLs to messages you posted?
JEff
Signature · 2 lines
Joe Harvell [email protected]
Quoted 3 lines · Joe Harvell
http://marc.theaimsgroup.com/?l=linux-ide&m=111029414823303&w=2
http://marc.theaimsgroup.com/?l=linux-ide&m=111054989026053&w=2
http://marc.theaimsgroup.com/?l=linux-ide&m=111230129320297&w=2
all pretty much the same report (by Joe).
leads to
http://forums.gentoo.org/viewtopic-p-2247734.html
which is somewhat more interesting, though rather fuzzy. there's something about the driver deciding not to handle an interrupt (nobody cared), after which the driver is toast. some claim that this might be dependent on which disk is attached.
fundamentally, the problem is to isolate whether the (few) reported problems are due to peculiarities of the reporting machines or not.
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
You need to add a comment about the SATAII TX2/TX4 boards indicating users have experienced data corruption with the
sata_promisedriver and the SATAII TX4 board.
personally, I don't think this kind of warning is warranted. it's like saying that "rm" should have a warning because users have experienced data deletion when mistyping it...
I can understand the reluctance to put out a warning before verifying the problem.
I would be willing to reproduce the problem if you have some debugging data you want me to collect.
If you are concerned about the data corruption coming from the technique I used (copying the OS installation from a utility boot environment), then it may help you to know the following:
1. that I reproduced the problem 3 or 4 times with the 2.6 sata_promise driver before deciding to try Promise's 2.4 driver; and
2. that I used the same procedure of copying the same source OS from a utility boot environment after switching to the 2.4 kernel and the Promise driver, which resolved the problem.
Quoted 34 lines · Mark Hahn
Quoted 3 lines · Joe Harvell
http://marc.theaimsgroup.com/?l=linux-ide&m=111029414823303&w=2
http://marc.theaimsgroup.com/?l=linux-ide&m=111054989026053&w=2
http://marc.theaimsgroup.com/?l=linux-ide&m=111230129320297&w=2all pretty much the same report (by Joe).
leads to
http://forums.gentoo.org/viewtopic-p-2247734.htmlwhich is somewhat more interesting, though rather fuzzy. there's something about the driver deciding not to handle an interrupt (nobody cared), after which the driver is toast. some claim that this might be dependent on which disk is attached.
fundamentally, the problem is to isolate whether the (few) reported problems are due to peculiarities of the reporting machines or not.
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
You need to add a comment about the SATAII TX2/TX4 boards indicating users have experienced data corruption with the
sata_promisedriver and the SATAII TX4 board.personally, I don't think this kind of warning is warranted. it's like saying that "rm" should have a warning because users have experienced data deletion when mistyping it...
-
To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Signature · 2 lines
Joe Harvell [email protected]
Quoted 4 lines · Jeff Garzik
My Linux SATA software/hardware status reports have just been updated. To see where libata (SATA) support stands for a particular piece of hardware, or a particular feature, go to
http://linux.yyz.us/sata/
A nice thing in FAQ would be some info on problematic (blacklisted) SATA hardware that runs on Linux (vide "poor SATA performance under 2.6.11 (with < 2.6.11 is OK)?" thread), like Silicon Image 311x controllers + some Seagate drives [1].
Tomek
[1] although my drive is blacklisted (Seagate barracuda - ST3200822AS), I "unblacklisted" it to get full performance - it's under heavy stress for 12th hour, and still no error.
------------------------------------------------------------------
Teraz na tapecie mamy najwiekszego z silaczy. Sciagnij >> http://link.interia.pl/f1873 <<
Tomasz Chmielewski wrote:
<
Quoted 1 line
[1] although my drive is blacklisted (Seagate barracuda - ST3200822AS), I "unblacklisted" it to get full performance - it's under heavy stress for 12th hour, and still no error.
It could be that your drive has newer firmware. Too bad firmware upgrades for HD's are hard to come by nowadays.
Signature · 2 lines
Cheers, André Tomt
Quoted 7 lines · Andre Tomt
Tomasz Chmielewski wrote:
<Quoted 1 line
[1] although my drive is blacklisted (Seagate barracuda - ST3200822AS), I "unblacklisted" it to get full performance - it's under heavy stress for 12th hour, and still no error.
It could be that your drive has newer firmware. Too bad firmware upgrades for HD's are hard to come by nowadays.
Is there a way to check what firmware a drive has (either by using some software - which would be the best option, or by reading a label on a drive)?
If so, we might compile some list to be put in the FAQ?
There was also a post on the list - http://www.uwsg.iu.edu/hypermail/linux/kernel/0503.1/0827.html - suggesting that upgrading Silicon Image BIOS helped resolving these problems.
So it might be newer drive firmware, or newer SATA card BIOS (or both) that makes my "sil + seagate" combination usable.
Tomek
----------------------------------------------------------------------
Startuj z INTERIA.PL! >>> http://link.interia.pl/f186c
Quoted 7 lines · Tomasz Chmielewski
Quoted 6 lines · Andre Tomt
Tomasz Chmielewski wrote:
<Quoted 3 lines
[1] although my drive is blacklisted (Seagate barracuda - ST3200822AS), I "unblacklisted" it to get full performance - it's under heavy stress for 12th hour, and still no error.
Quoted 6 lines
Quoted 2 lines
It could be that your drive has newer firmware. Too bad firmware upgrades for HD's are hard to come by nowadays.
Is there a way to check what firmware a drive has (either by using some software - which would be the best option, or by reading a label on a drive)?
Seagate drives have the firmware version printed on the label. The version is also visible in "dmesg" output:
Vendor: ATA Model: ST3160827AS Rev: 3.03
Type: Direct-Access ANSI SCSI revision: 05
The "Rev" number is the firmware version.
Signature · 2 lines
Måns Rullgård [email protected]
Quoted 4 lines · Jeff Garzik
My Linux SATA software/hardware status reports have just been updated. To see where libata (SATA) support stands for a particular piece of hardware, or a particular feature, go to
http://linux.yyz.us/sata/
What's the timeline on getting sata-promise's PATA support into mainline? I've been 2.6.11-gentoo-r2, which includes this feature, for weeks now, and it's been perfectly stable (including md's RAID5) using the PATA port. It would be nice to be able to run my system with a mainline kernel.
The broken-out patch that Gentoo is using is here:
http://dev.gentoo.org/~dsd/gentoo-dev-sources/release-11.01/dist/4320_promise-pdc2037x.patch
Thanks,
Andy