Re: sata_promise ata exceptions (2.6.20.6)
Hi, My theory is that either TBG clocking (which drives the SATA interfaces) or SET FEATURE snooping (which adjusts internal parameters for different PIO/(U)DMA modes) is borked for SATAII/3Gbps. I hope to have time to investigate that soon. If you can limit transfer speeds to 1.5Gpbs then that may provide a workaround for now. For your information, a friend of mine has the exact same SATA-card hard-disk combination (Promise Sata300TX4 + 2*Seagate 7200.10) with Intel P4 875P chipset and gets similar error messages every once in a while when there is above average disk I/O in the system (for example raid-recheck). ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 ata4.00: cmd 25/00:00:bf:0f:87/00:04:05:00:00/e0 tag 0 cdb 0x0 data 524288 in res 50/00:00:be:13:87/00:00:05:00:00/e0 Emask 0x1 (device error) So at least it doesn't seem like my hard-disks or SATA-card are faulty/broken. Regards, Tomi Orava - 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
Re: sata_promise ata exceptions (2.6.20.6)
Given that the last one was a hardware issue, I bought a new controller. Despite my bad luck, given my price-range promise still seemed to be the one with the most good reports, so I went with that. I was going to go with a sil, but I couldn't find one.. Anyway, things are MUCH better now... but about once a week, I get: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen ata2.00: (port_status 0x1000) ata2.00: cmd c8/00:80:9a:71:d0/00:00:00:00:00/ea tag 0 cdb 0x0 data 65536 in res 40/00:00:06:4f:c2/00:00:00:00:00/00 Emask 0x24 (host bus error) ata2: soft resetting port ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata2.00: configured for UDMA/133 ata2: EH complete SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB) sda: Write Protect is off sda: Mode Sense: 00 3a 00 00 SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA It's the same port_status and Emask/SAct/SErr/action each time... only the cmd/res and data change (obviously those would change)... Can anyone tell me what that means? -- Phil Dibowitz [EMAIL PROTECTED] Open Source software and tech docsInsanity Palace of Metallica http://www.phildev.net/ http://www.ipom.com/ Never write it in C if you can do it in 'awk'; Never do it in 'awk' if 'sed' can handle it; Never use 'sed' when 'tr' can do the job; Never invoke 'tr' when 'cat' is sufficient; Avoid using 'cat' whenever possible -- Taylor's Laws of Programming signature.asc Description: OpenPGP digital signature
Re: sata_promise ata exceptions (2.6.20.6)
Hi, Given that the last one was a hardware issue, I bought a new controller. Despite my bad luck, given my price-range promise still seemed to be the one with the most good reports, so I went with that. I was going to go with a sil, but I couldn't find one.. Unfortunately, I don't have a solution/fix for you, but out of curiosity, what hard-disks you have problems with ? Also what is the exact model of your SATA-controller ? Anyway, things are MUCH better now... but about once a week, I get: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen ata2.00: (port_status 0x1000) ata2.00: cmd c8/00:80:9a:71:d0/00:00:00:00:00/ea tag 0 cdb 0x0 data 65536 in res 40/00:00:06:4f:c2/00:00:00:00:00/00 Emask 0x24 (host bus error) ata2: soft resetting port ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata2.00: configured for UDMA/133 ata2: EH complete SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB) sda: Write Protect is off sda: Mode Sense: 00 3a 00 00 SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA Regards, Tomi Orava - 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
Re: sata_promise ata exceptions (2.6.20.6)
On Sun, 15 Apr 2007 23:55:31 -0700, Phil Dibowitz wrote: Given that the last one was a hardware issue, I bought a new controller. Despite my bad luck, given my price-range promise still seemed to be the = one with the most good reports, so I went with that. I was going to go with a= sil, but I couldn't find one.. Anyway, things are MUCH better now... but about once a week, I get: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen ata2.00: (port_status 0x1000) ata2.00: cmd c8/00:80:9a:71:d0/00:00:00:00:00/ea tag 0 cdb 0x0 data 65536= in res 40/00:00:06:4f:c2/00:00:00:00:00/00 Emask 0x24 (host bus err= or) ata2: soft resetting port ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata2.00: configured for UDMA/133 ata2: EH complete SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB) sda: Write Protect is off sda: Mode Sense: 00 3a 00 00 SCSI device sda: write cache: enabled, read cache: enabled, doesn't suppo= rt DPO or FUA It's the same port_status and Emask/SAct/SErr/action each time... only th= e cmd/res and data change (obviously those would change)... Can anyone tell me what that means? port_status 0x1000 is host bus timeout, which the manual defines as the host bus being busy for more than 256 clock cycles during an ATA I/O transfer. I have no idea what would cause this error, and I've never seen it myself. As long as libata recovers and doesn't downgrade your transfer speed it shouldn't pose too much of a problem. /Mikael - 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
Re: sata_promise ata exceptions (2.6.20.6)
Tomi Orava wrote: Hi, Given that the last one was a hardware issue, I bought a new controller. Despite my bad luck, given my price-range promise still seemed to be the one with the most good reports, so I went with that. I was going to go with a sil, but I couldn't find one.. Unfortunately, I don't have a solution/fix for you, but out of curiosity, what hard-disks you have problems with ? Also what is the exact model of your SATA-controller ? Whoops, forgot that bit. Sorry! 02:0c.0 Mass storage controller: Promise Technology, Inc. PDC40718 (SATA 300 TX4) (rev 02) Subsystem: Promise Technology, Inc. PDC40718 (SATA 300 TX4) Flags: bus master, 66MHz, medium devsel, latency 72, IRQ 17 I/O ports at d480 [size=128] I/O ports at d000 [size=256] Memory at feafd000 (32-bit, non-prefetchable) [size=4K] Memory at fea8 (32-bit, non-prefetchable) [size=128K] Expansion ROM at 5002 [disabled] [size=32K] Capabilities: [60] Power Management version 2 My disks are WD WD1600JS 160GB drives (2 of them in linux software RAID 1). -- Phil Dibowitz [EMAIL PROTECTED] Open Source software and tech docsInsanity Palace of Metallica http://www.phildev.net/ http://www.ipom.com/ Never write it in C if you can do it in 'awk'; Never do it in 'awk' if 'sed' can handle it; Never use 'sed' when 'tr' can do the job; Never invoke 'tr' when 'cat' is sufficient; Avoid using 'cat' whenever possible -- Taylor's Laws of Programming signature.asc Description: OpenPGP digital signature
Re: sata_promise ata exceptions (2.6.20.6)
Related to my previous tests, it seems that after I changed the order of the hard-disks connected to Promise Sata300TX4 the errors followed both of the 7200.10 disks. I swapped the power supply and the SATA-cables at the same time and still get the following kind of errors (and only with 7200.10, _never_ with the older 7200.7 disks): ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 ata3.00: cmd c8/00:08:77:7a:68/00:00:00:00:00/e7 tag 0 cdb 0x0 data 4096 in res 50/00:00:7e:7a:68/00:00:00:00:00/e7 Emask 0x1 (device error) ata3.00: configured for UDMA/133 ata3: EH complete SCSI device sdc: 976773168 512-byte hdwr sectors (500108 MB) sdc: Write Protect is off sdc: Mode Sense: 00 3a 00 00 SCSI device sdc: write cache: enabled, read cache: enabled, doesn't support DPO or FUA ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 ata3.00: cmd c8/00:08:57:bb:6a/00:00:00:00:00/e7 tag 0 cdb 0x0 data 4096 in res 50/00:00:5e:bb:6a/00:00:00:00:00/e7 Emask 0x1 (device error) ata3.00: configured for UDMA/133 ata3: EH complete SCSI device sdc: 976773168 512-byte hdwr sectors (500108 MB) sdc: Write Protect is off sdc: Mode Sense: 00 3a 00 00 SCSI device sdc: write cache: enabled, read cache: enabled, doesn't support DPO or FUA ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 ata4.00: cmd c8/00:20:2f:86:90/00:00:00:00:00/ea tag 0 cdb 0x0 data 16384 in res 50/00:00:4e:86:90/00:00:00:00:00/ea Emask 0x1 (device error) ata4.00: configured for UDMA/133 ata4: EH complete SCSI device sdd: 976773168 512-byte hdwr sectors (500108 MB) sdd: Write Protect is off sdd: Mode Sense: 00 3a 00 00 SCSI device sdd: write cache: enabled, read cache: enabled, doesn't support DPO or FUA ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 ata4.00: cmd c8/00:50:e7:f3:98/00:00:00:00:00/ea tag 0 cdb 0x0 data 40960 in res 50/00:00:36:f4:98/00:00:00:00:00/ea Emask 0x1 (device error) ata4.00: configured for UDMA/133 ata4: EH complete SCSI device sdd: 976773168 512-byte hdwr sectors (500108 MB) sdd: Write Protect is off sdd: Mode Sense: 00 3a 00 00 SCSI device sdd: write cache: enabled, read cache: enabled, doesn't support DPO or FUA ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 ata4.00: cmd c8/00:48:57:c8:9e/00:00:00:00:00/ea tag 0 cdb 0x0 data 36864 in res 50/00:00:9e:c8:9e/00:00:00:00:00/ea Emask 0x1 (device error) ata4.00: configured for UDMA/133 ata4: EH complete The problems seem to be generated from simple ATA-READ commands: ATA_CMD_READ= 0xC8, ATA_CMD_READ_EXT = 0x25, but I have absolutely no idea what is causing them ... The both disks have nothing special in their SMART-records: SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 104 100 006Pre-fail Always - 6873586 3 Spin_Up_Time0x0003 093 093 000Pre-fail Always - 0 4 Start_Stop_Count0x0032 100 100 020Old_age Always - 11 5 Reallocated_Sector_Ct 0x0033 100 100 036Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 076 061 030Pre-fail Always - 44625875 9 Power_On_Hours 0x0032 099 099 000Old_age Always - 1236 10 Spin_Retry_Count0x0013 100 100 097Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020Old_age Always - 11 187 Unknown_Attribute 0x0032 100 100 000Old_age Always - 0 189 Unknown_Attribute 0x003a 100 100 000Old_age Always - 0 190 Unknown_Attribute 0x0022 063 060 045Old_age Always - 639631397 194 Temperature_Celsius 0x0022 037 040 000Old_age Always - 37 (Lifetime Min/Max 0/27) 195 Hardware_ECC_Recovered 0x001a 076 054 000Old_age Always - 194225 197 Current_Pending_Sector 0x0012 100 100 000Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000Old_age Offline - 0 199 UDMA_CRC_Error_Count0x003e 200 200 000Old_age Always - 0 200 Multi_Zone_Error_Rate 0x 100 253 000Old_age Offline - 0 202 TA_Increase_Count 0x0032 100 253 000Old_age Always - 0 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 Num Test_DescriptionStatus Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offlineCompleted without error 00% 1181 - # 2 Extended offlineCompleted without error 00% 231 - Any good ideas from where to search for the solution to this error messages ?
Re: sata_promise ata exceptions (2.6.20.6)
Hi, I just ran a test with the 2.6.21-rc6-git1 + your patches below and got the following errors (bottom of the mail). Do you have any idea what they might be trying to tell ? My configuration contains Promise Sata300TX4-pci card: 00:0e.0 Mass storage controller: Promise Technology, Inc. PDC40718 (SATA 300 TX4) (rev 02) Subsystem: Promise Technology, Inc. PDC40718 (SATA 300 TX4) Flags: bus master, 66MHz, medium devsel, latency 72, IRQ 16 I/O ports at ec00 [size=128] I/O ports at e000 [size=256] Memory at fe90 (32-bit, non-prefetchable) [size=4K] Memory at fe80 (32-bit, non-prefetchable) [size=128K] Expansion ROM at fe60 [disabled] [size=32K] Capabilities: [60] Power Management version 2 Asus A7V880 / AMD Athlon XP 2.8MHz Antec truepower II 550W power supply 2 * Seagate 7200.7 disks 200GB (no errors with these two) 2 * Seagate 7200.10 disks 500GB (these ones generate all the errors) (jumpered into 3.0Gbs mode) I've seen reports of issues like these with second-generation Promise SATA chips and SATAII (3Gbps) drives, but this is the first time I've seen any issues with a first-generation chip. 1. Please try 2.6.21-rc6 plus the following two patches: http://user.it.uu.se/~mikpe/linux/patches/2.6/patch-sata_promise-1-separate-sata-pata-ops-2.6.21-rc6 http://user.it.uu.se/~mikpe/linux/patches/2.6/patch-sata_promise-2-error_intr-2.6.21-rc6 This probably won't eliminate the errors, but should improve the level of detail in the error messages. 2. Try with a better power supply and verify that cooling is OK. Also verify that the SATA data and power cables are firmly attached. We've seen several reports of mysterious issues that eventually were traced to insufficient power supplies or poorly seated PCI cards (but in your case the chip is integrated on the mobo). On my system, cooling is OK. The power supply however has been changed twice because previous Antec supplies have died under stress :( Regards, Tomi Orava --- ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen ata2.00: (port_status 0x2008) ata2.00: cmd c8/00:68:27:ea:7c/00:00:00:00:00/e7 tag 0 cdb 0x0 data 53248 in res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x6 (timeout) ata2: soft resetting port ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata2.00: configured for UDMA/133 ata2: EH complete SCSI device sdb: 976773168 512-byte hdwr sectors (500108 MB) sdb: Write Protect is off sdb: Mode Sense: 00 3a 00 00 SCSI device sdb: write cache: enabled, read cache: enabled, doesn't support DPO or FUA ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen ata2.00: (port_status 0x2008) ata2.00: cmd c8/00:a8:5f:95:87/00:00:00:00:00/e7 tag 0 cdb 0x0 data 86016 in res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x6 (timeout) ata2: soft resetting port ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata2.00: configured for UDMA/133 ata2: EH complete SCSI device sdb: 976773168 512-byte hdwr sectors (500108 MB) sdb: Write Protect is off sdb: Mode Sense: 00 3a 00 00 SCSI device sdb: write cache: enabled, read cache: enabled, doesn't support DPO or FUA ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen ata2.00: (port_status 0x2008) ata2.00: cmd c8/00:00:3f:6f:b3/00:00:00:00:00/e7 tag 0 cdb 0x0 data 131072 in res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x6 (timeout) ata2: soft resetting port ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata2.00: configured for UDMA/133 ata2: EH complete SCSI device sdb: 976773168 512-byte hdwr sectors (500108 MB) sdb: Write Protect is off sdb: Mode Sense: 00 3a 00 00 SCSI device sdb: write cache: enabled, read cache: enabled, doesn't support DPO or FUA ata2.00: limiting speed to UDMA/100:PIO4 ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen ata2.00: (port_status 0x2008) ata2.00: cmd 25/00:00:2f:2b:b3/00:02:07:00:00/e0 tag 0 cdb 0x0 data 262144 in res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x6 (timeout) ata2: soft resetting port ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata2.00: configured for UDMA/100 ata2: EH complete SCSI device sdb: 976773168 512-byte hdwr sectors (500108 MB) sdb: Write Protect is off sdb: Mode Sense: 00 3a 00 00 SCSI device sdb: write cache: enabled, read cache: enabled, doesn't support DPO or FUA --- -- - 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
Re: sata_promise ata exceptions (2.6.20.6)
On Sat, 07 Apr 2007 16:41:04 -0700, Phil Dibowitz wrote: I've recently moved to a Promise Sata controller with two SATA drives in a RAID1 mirror. But I get lots of ata exceptions and the kernel eventually slows down my drive to UDMA/33. It usually happens on ata1 (sda), but sometimes it'll kick in on ata2 (sdb). I can definitely cause this to happen more by increasing load on the disks. But even low load (checking email) causes this. Full hardware and software specs are below, but first, the errors: ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x180100 action 0x2 ata1.00: cmd c8/00:d0:8a:31:ae/00:00:00:00:00/e0 tag 0 cdb 0x0 data 106496 in res 51/0c:0f:4b:32:ae/00:00:00:00:00/e0 Emask 0x10 (ATA bus error) ata1: soft resetting port ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata1.00: configured for UDMA/133 ata1: EH complete SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB) sda: Write Protect is off sda: Mode Sense: 00 3a 00 00 SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA ... Kernel: 2.6.20.6 (PREEMT SMP) SATA Controller: 02:04.0 RAID bus controller: Promise Technology, Inc. PDC20378 (FastTrak 378/SATA 378) (rev 02) Subsystem: ASUSTeK Computer Inc. K8V Deluxe/PC-DL Deluxe motherboard Flags: bus master, 66MHz, medium devsel, latency 96, IRQ 16 I/O ports at df00 [size=64] I/O ports at dfa0 [size=16] I/O ports at dc00 [size=128] Memory at feafe000 (32-bit, non-prefetchable) [size=4K] Memory at feac (32-bit, non-prefetchable) [size=128K] Capabilities: [60] Power Management version 2 Drives: 2 x Western Digital WD1600JS-00N I've seen reports of issues like these with second-generation Promise SATA chips and SATAII (3Gbps) drives, but this is the first time I've seen any issues with a first-generation chip. 1. Please try 2.6.21-rc6 plus the following two patches: http://user.it.uu.se/~mikpe/linux/patches/2.6/patch-sata_promise-1-separate-sata-pata-ops-2.6.21-rc6 http://user.it.uu.se/~mikpe/linux/patches/2.6/patch-sata_promise-2-error_intr-2.6.21-rc6 This probably won't eliminate the errors, but should improve the level of detail in the error messages. 2. Try with a better power supply and verify that cooling is OK. Also verify that the SATA data and power cables are firmly attached. We've seen several reports of mysterious issues that eventually were traced to insufficient power supplies or poorly seated PCI cards (but in your case the chip is integrated on the mobo). /Mikael - 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
Re: sata_promise ata exceptions (2.6.20.6)
Mikael Pettersson wrote: I've seen reports of issues like these with second-generation Promise SATA chips and SATAII (3Gbps) drives, but this is the first time I've seen any issues with a first-generation chip. 1. Please try 2.6.21-rc6 plus the following two patches: http://user.it.uu.se/~mikpe/linux/patches/2.6/patch-sata_promise-1-separate-sata-pata-ops-2.6.21-rc6 http://user.it.uu.se/~mikpe/linux/patches/2.6/patch-sata_promise-2-error_intr-2.6.21-rc6 This probably won't eliminate the errors, but should improve the level of detail in the error messages. I'll do this tonight and send updated logs, thanks. 2. Try with a better power supply and verify that cooling is OK. Also verify that the SATA data and power cables are firmly attached. My power supply is well over-sized for my machine (Antec 480W), so that shouldn't be a problem. I double checked all my SATA data and power cables. I also tried switching from SATA-power to PATA-power cables (my drives support both) to see if that made a difference (it didn't). I've reseated my cables, switched cable order, etc. to see if I had a bad cable, but no evidence I do. We've seen several reports of mysterious issues that eventually were traced to insufficient power supplies or poorly seated PCI cards (but in your case the chip is integrated on the mobo). Understandable. I saw several reports like that on the list, and hence tried the above. Thanks for your time, I'll get you updated logs tonight. -- Phil Dibowitz [EMAIL PROTECTED] Open Source software and tech docsInsanity Palace of Metallica http://www.phildev.net/ http://www.ipom.com/ Never write it in C if you can do it in 'awk'; Never do it in 'awk' if 'sed' can handle it; Never use 'sed' when 'tr' can do the job; Never invoke 'tr' when 'cat' is sufficient; Avoid using 'cat' whenever possible -- Taylor's Laws of Programming signature.asc Description: OpenPGP digital signature
Re: sata_promise ata exceptions (2.6.20.6)
On Mon, Apr 09, 2007 at 12:18:09PM +0200, Mikael Pettersson wrote: I've seen reports of issues like these with second-generation Promise SATA chips and SATAII (3Gbps) drives, but this is the first time I've seen any issues with a first-generation chip. 1. Please try 2.6.21-rc6 plus the following two patches: http://user.it.uu.se/~mikpe/linux/patches/2.6/patch-sata_promise-1-separate-sata-pata-ops-2.6.21-rc6 http://user.it.uu.se/~mikpe/linux/patches/2.6/patch-sata_promise-2-error_intr-2.6.21-rc6 This probably won't eliminate the errors, but should improve the level of detail in the error messages. It doesn't appear to have changed much. After a reboot, I have: ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x380100 action 0x2 frozen ata1.00: (port_status 0x2020) ata1.00: cmd c8/00:90:f2:fb:a6/00:00:00:00:00/e0 tag 0 cdb 0x0 data 73728 in res 40/00:00:01:4f:c2/00:00:00:00:00/00 Emask 0x14 (ATA bus error) ata1: soft resetting port ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata1.00: configured for UDMA/133 ata1: EH complete SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB) sda: Write Protect is off sda: Mode Sense: 00 3a 00 00 SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x380100 action 0x2 frozen ata1.00: (port_status 0x2020) ata1.00: cmd c8/00:88:1a:f5:a6/00:00:00:00:00/e0 tag 0 cdb 0x0 data 69632 in res 40/00:00:01:4f:c2/00:00:00:00:00/00 Emask 0x14 (ATA bus error) ata1: soft resetting port ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata1.00: configured for UDMA/133 ata1: EH complete SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB) sda: Write Protect is off sda: Mode Sense: 00 3a 00 00 SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA ata1.00: limiting speed to UDMA/100:PIO4 ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x380100 action 0x2 frozen ata1.00: (port_status 0x2020) ata1.00: cmd c8/00:80:7a:b8:a9/00:00:00:00:00/e0 tag 0 cdb 0x0 data 65536 in res 40/00:00:01:4f:c2/00:00:00:00:00/00 Emask 0x14 (ATA bus error) ata1: soft resetting port ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata1.00: configured for UDMA/100 ata1: EH complete SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB) sda: Write Protect is off sda: Mode Sense: 00 3a 00 00 SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA Any other info I can provide? -- Phil Dibowitz [EMAIL PROTECTED] Open Source software and tech docsInsanity Palace of Metallica http://www.phildev.net/ http://www.ipom.com/ Never write it in C if you can do it in 'awk'; Never do it in 'awk' if 'sed' can handle it; Never use 'sed' when 'tr' can do the job; Never invoke 'tr' when 'cat' is sufficient; Avoid using 'cat' whenever possible -- Taylor's Laws of Programming signature.asc Description: Digital signature
Re: sata_promise ata exceptions (2.6.20.6)
On 4/9/07, Phil Dibowitz [EMAIL PROTECTED] wrote: Mikael, Thanks for the quick response. I appreciate your help. I guess I'm buying a SATA PCI card! Looks like my choice of reasonably-priced known-brands is Highpoint and Promise (specifically a Highpoint ROCKETRAID1520 or a Promise SATA300 TX4) - are one of these brands better from a Linux compatibility or hardware-bug standpoint? Quoting an old e-mail from Tejun Heo: === I primarily work on sil controllers and ICH7R piix/ahci because I have access to the hardware and docs. So, those tend to get new features first and get a lot of testing. If you're planning on using Port Multiplier, sil3124/32 would be the best bet ATM. === Greg -- Greg Freemyer The Norcross Group Forensics for the 21st Century - 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
Re: sata_promise ata exceptions (2.6.20.6)
Phil Dibowitz schrieb: ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x180100 action 0x2 ata1.00: cmd c8/00:d0:8a:31:ae/00:00:00:00:00/e0 tag 0 cdb 0x0 data 106496 in res 51/0c:0f:4b:32:ae/00:00:00:00:00/e0 Emask 0x10 (ATA bus error) ata1: soft resetting port ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata1.00: configured for UDMA/133 ata1: EH complete SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB) sda: Write Protect is off sda: Mode Sense: 00 3a 00 00 SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x380100 action 0x2 ata1.00: cmd c8/00:a0:12:fa:bc/00:00:00:00:00/e0 tag 0 cdb 0x0 data 81920 in res 51/0c:1f:93:fa:bc/00:00:00:00:00/e0 Emask 0x10 (ATA bus error) ata1: soft resetting port ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata1.00: configured for UDMA/133 ata1: EH complete SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB) sda: Write Protect is off sda: Mode Sense: 00 3a 00 00 SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA ata1.00: limiting speed to UDMA/100 ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x380100 action 0x2 ata1.00: cmd c8/00:48:2a:27:ac/00:00:00:00:00/e0 tag 0 cdb 0x0 data 36864 in res 51/0c:27:4b:27:ac/00:00:00:00:00/e0 Emask 0x10 (ATA bus error) ata1: soft resetting port ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata1.00: configured for UDMA/100 ata1: EH complete SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB) sda: Write Protect is off sda: Mode Sense: 00 3a 00 00 SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA ata1.00: limiting speed to UDMA/66 ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x180100 action 0x2 ata1.00: cmd c8/00:f8:6a:7a:ae/00:00:00:00:00/e0 tag 0 cdb 0x0 data 126976 in res 51/0c:97:cb:7a:ae/00:00:00:00:00/e0 Emask 0x10 (ATA bus error) ata1: soft resetting port ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata1.00: configured for UDMA/66 ata1: EH complete SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB) sda: Write Protect is off sda: Mode Sense: 00 3a 00 00 SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA I got similar errors since kernel 2.6.20-xx and the LBA48/EH fix between 2.6.21-rc5-git10 and 2.6.21-rc5-git13 seems to fix it. I'm no developer, but you should perhaps try kernel 2.6.21-rc5-git13 or later. Greetings Ansgar Knappheide - 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
