Re: [BUG 2.6.21-rc3-git9] SATA NCQ failure with Samsum HD401LJ
Christian wrote: I've tested multiple kernels (including -mm series) in the range of 2.6.19.7 (before sata_nv adma support went in) up to 2.6.20-rc4. Every NCQ enabled kernel I've tested showed ata errors in dmesg. So I came to the conclusion that my system was faulty. I ran memtest86+ for a long time, but no errors were found. After some fiddling with my HW I discovered that the nforce chipset fan induced some kind of electro magnetic interference to the southbridge, which could clearly be heard as a low frequency noise if I plugged in my speakers to the onboard sound. After replacing the fan, my system is stable again. Now running 2.6.21-rc3-mm2+rsdlv31 without errors. Really strange problem he ;-) Man, that's the strangest way to solve ATA command failures I've ever heard of. Kudos to you for finding it out. :-) -- tejun - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [BUG 2.6.21-rc3-git9] SATA NCQ failure with Samsum HD401LJ
On Monday 19 March 2007 08:39:15 Tejun Heo wrote: > Christian wrote: > > Yes, for me the problem was introduced recently. I have moved around > > terabytes (sic!) on my discs with older kernels and I never got errors. > > There is always the possibility of disk going bad, so it would be great > if you can boot an older kernel and verify that the problem doesn't > occur on it. > > Thanks. I've tested multiple kernels (including -mm series) in the range of 2.6.19.7 (before sata_nv adma support went in) up to 2.6.20-rc4. Every NCQ enabled kernel I've tested showed ata errors in dmesg. So I came to the conclusion that my system was faulty. I ran memtest86+ for a long time, but no errors were found. After some fiddling with my HW I discovered that the nforce chipset fan induced some kind of electro magnetic interference to the southbridge, which could clearly be heard as a low frequency noise if I plugged in my speakers to the onboard sound. After replacing the fan, my system is stable again. Now running 2.6.21-rc3-mm2+rsdlv31 without errors. Really strange problem he ;-) -Christian - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [BUG 2.6.21-rc3-git9] SATA NCQ failure with Samsum HD401LJ
On Monday 19 March 2007 08:39:15 Tejun Heo wrote: Christian wrote: Yes, for me the problem was introduced recently. I have moved around terabytes (sic!) on my discs with older kernels and I never got errors. There is always the possibility of disk going bad, so it would be great if you can boot an older kernel and verify that the problem doesn't occur on it. Thanks. I've tested multiple kernels (including -mm series) in the range of 2.6.19.7 (before sata_nv adma support went in) up to 2.6.20-rc4. Every NCQ enabled kernel I've tested showed ata errors in dmesg. So I came to the conclusion that my system was faulty. I ran memtest86+ for a long time, but no errors were found. After some fiddling with my HW I discovered that the nforce chipset fan induced some kind of electro magnetic interference to the southbridge, which could clearly be heard as a low frequency noise if I plugged in my speakers to the onboard sound. After replacing the fan, my system is stable again. Now running 2.6.21-rc3-mm2+rsdlv31 without errors. Really strange problem he ;-) -Christian - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [BUG 2.6.21-rc3-git9] SATA NCQ failure with Samsum HD401LJ
Christian wrote: I've tested multiple kernels (including -mm series) in the range of 2.6.19.7 (before sata_nv adma support went in) up to 2.6.20-rc4. Every NCQ enabled kernel I've tested showed ata errors in dmesg. So I came to the conclusion that my system was faulty. I ran memtest86+ for a long time, but no errors were found. After some fiddling with my HW I discovered that the nforce chipset fan induced some kind of electro magnetic interference to the southbridge, which could clearly be heard as a low frequency noise if I plugged in my speakers to the onboard sound. After replacing the fan, my system is stable again. Now running 2.6.21-rc3-mm2+rsdlv31 without errors. Really strange problem he ;-) Man, that's the strangest way to solve ATA command failures I've ever heard of. Kudos to you for finding it out. :-) -- tejun - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [BUG 2.6.21-rc3-git9] SATA NCQ failure with Samsum HD401LJ
On 2007/03/19 13:09, Jeff Garzik <[EMAIL PROTECTED]> wrote: > I may have missed the answer to this before, but: does the problem > go away if you disable preempt? On my system (same problem, original bug report), preemption is disabled. Max - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [BUG 2.6.21-rc3-git9] SATA NCQ failure with Samsum HD401LJ
On 2007/03/19 13:09, Jeff Garzik [EMAIL PROTECTED] wrote: I may have missed the answer to this before, but: does the problem go away if you disable preempt? On my system (same problem, original bug report), preemption is disabled. Max - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [BUG 2.6.21-rc3-git9] SATA NCQ failure with Samsum HD401LJ
Christian wrote: On Sunday 18 March 2007 06:43:09 you wrote: Christian wrote: This does indeed look like a drive side issue to me (the controller is reporting CPBs with response flags 2 which as far as I can tell indicates it's still waiting for the drive to complete the request). I have been using this hw-config (SATA II, NCQ) since the nvidia ADMA support made it in the -mm kernel (maybe around 2.6.19-mm? or even earlyer). I'm seeing this problem excessively since I upgraded to 2.6.21-rc3-mm1. I think something got broken recently... Can you post the result of "hdparm -I /dev/sdX"? Output generated on 2.6.21-rc3-mm1 #3 SMP PREEMPT [EMAIL PROTECTED]:~$ sudo hdparm -I /dev/sda /dev/sda: ATA device, with non-removable media Model Number: SAMSUNG HD401LJ Serial Number: S0HVJ1FL900207 Firmware Revision: ZZ100-15 Standards: Used: ATA/ATAPI-7 T13 1532D revision 4a Supported: 7 6 5 4 Configuration: Logical max current cylinders 16383 16383 heads 16 16 sectors/track 63 63 -- CHS current addressable sectors: 16514064 LBAuser addressable sectors: 268435455 LBA48 user addressable sectors: 781422768 device size with M = 1024*1024: 381554 MBytes device size with M = 1000*1000: 400088 MBytes (400 GB) Capabilities: LBA, IORDY(can be disabled) Queue depth: 32 Standby timer values: spec'd by Standard, no device specific minimum R/W multiple sector transfer: Max = 16 Current = 16 Recommended acoustic management value: 254, current value: 0 DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6 udma7 Cycle time: min=120ns recommended=120ns PIO: pio0 pio1 pio2 pio3 pio4 Cycle time: no flow control=120ns IORDY flow control=120ns Commands/features: Enabled Supported: *SMART feature set Security Mode feature set *Power Management feature set *Write cache *Look-ahead *Host Protected Area feature set *WRITE_BUFFER command *READ_BUFFER command *NOP cmd *DOWNLOAD_MICROCODE SET_MAX security extension Automatic Acoustic Management feature set *48-bit Address feature set *Device Configuration Overlay feature set *Mandatory FLUSH_CACHE *FLUSH_CACHE_EXT *SMART error logging *SMART self-test *General Purpose Logging feature set *SATA-I signaling speed (1.5Gb/s) *SATA-II signaling speed (3.0Gb/s) *Native Command Queueing (NCQ) *Host-initiated interface power management *Phy event counters DMA Setup Auto-Activate optimization Device-initiated interface power management *Software settings preservation *SMART Command Transport (SCT) feature set *SCT Long Sector Access (AC1) *SCT LBA Segment Access (AC2) *SCT Error Recovery Control (AC3) *SCT Features Control (AC4) *SCT Data Tables (AC5) Security: Master password revision code = 65534 supported not enabled not locked frozen not expired: security count supported: enhanced erase 228min for SECURITY ERASE UNIT. 228min for ENHANCED SECURITY ERASE UNIT. Checksum: correct [EMAIL PROTECTED]:~$ sudo hdparm -I /dev/sdb /dev/sdb: ATA device, with non-removable media Model Number: SAMSUNG SP2504C Serial Number: S09QJ1LYC06381 Firmware Revision: VT100-33 Standards: Used: ATA/ATAPI-7 T13 1532D revision 4a Supported: 7 6 5 4 Configuration: Logical max current cylinders 16383 16383 heads 16 16 sectors/track 63 63 -- CHS current addressable sectors: 16514064 LBAuser addressable sectors: 268435455 LBA48 user addressable sectors: 488397168 device size with M = 1024*1024: 238475 MBytes device size with M = 1000*1000: 250059 MBytes (250 GB) Capabilities: LBA, IORDY(can be disabled) Queue depth: 32 Standby timer values: spec'd by Standard, no device specific minimum R/W multiple sector transfer: Max = 16 Current = 16 Recommended acoustic management value: 254, current value: 254 DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6 udma7 Cycle time: min=120ns recommended=120ns PIO: pio0 pio1 pio2 pio3 pio4
Re: [BUG 2.6.21-rc3-git9] SATA NCQ failure with Samsum HD401LJ
Christian wrote: On Monday 19 March 2007 03:48:14 you wrote: Christian wrote: On Sunday 18 March 2007 06:43:09 you wrote: Christian wrote: This does indeed look like a drive side issue to me (the controller is reporting CPBs with response flags 2 which as far as I can tell indicates it's still waiting for the drive to complete the request). I have been using this hw-config (SATA II, NCQ) since the nvidia ADMA support made it in the -mm kernel (maybe around 2.6.19-mm? or even earlyer). I'm seeing this problem excessively since I upgraded to 2.6.21-rc3-mm1. I think something got broken recently... Can you post the result of "hdparm -I /dev/sdX"? Output generated on 2.6.21-rc3-mm1 #3 SMP PREEMPT [EMAIL PROTECTED]:~$ sudo hdparm -I /dev/sda /dev/sda: ATA device, with non-removable media Model Number: SAMSUNG HD401LJ Serial Number: S0HVJ1FL900207 Firmware Revision: ZZ100-15 Standards: Used: ATA/ATAPI-7 T13 1532D revision 4a Supported: 7 6 5 4 Configuration: Logical max current cylinders 16383 16383 heads 16 16 sectors/track 63 63 -- CHS current addressable sectors: 16514064 LBAuser addressable sectors: 268435455 LBA48 user addressable sectors: 781422768 device size with M = 1024*1024: 381554 MBytes device size with M = 1000*1000: 400088 MBytes (400 GB) That's a fairly recent drive. Does the problem go away if you downgrade the kernel? Yes, for me the problem was introduced recently. I have moved around terabytes (sic!) on my discs with older kernels and I never got errors. I may have missed the answer to this before, but: does the problem go away if you disable preempt? Jeff - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [BUG 2.6.21-rc3-git9] SATA NCQ failure with Samsum HD401LJ
Christian wrote: > Yes, for me the problem was introduced recently. I have moved around > terabytes > (sic!) on my discs with older kernels and I never got errors. There is always the possibility of disk going bad, so it would be great if you can boot an older kernel and verify that the problem doesn't occur on it. Thanks. -- tejun - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [BUG 2.6.21-rc3-git9] SATA NCQ failure with Samsum HD401LJ
On Monday 19 March 2007 03:48:14 you wrote: > Christian wrote: > > On Sunday 18 March 2007 06:43:09 you wrote: > >> Christian wrote: > This does indeed look like a drive side issue to me (the controller is > reporting CPBs with response flags 2 which as far as I can tell > indicates it's still waiting for the drive to complete the request). > >>> > >>> I have been using this hw-config (SATA II, NCQ) since the nvidia ADMA > >>> support made it in the -mm kernel (maybe around 2.6.19-mm? or even > >>> earlyer). I'm seeing this problem excessively since I upgraded to > >>> 2.6.21-rc3-mm1. I think something got broken recently... > >> > >> Can you post the result of "hdparm -I /dev/sdX"? > > > > Output generated on 2.6.21-rc3-mm1 #3 SMP PREEMPT > > > > [EMAIL PROTECTED]:~$ sudo hdparm -I /dev/sda > > > > /dev/sda: > > > > ATA device, with non-removable media > > Model Number: SAMSUNG HD401LJ > > Serial Number: S0HVJ1FL900207 > > Firmware Revision: ZZ100-15 > > Standards: > > Used: ATA/ATAPI-7 T13 1532D revision 4a > > Supported: 7 6 5 4 > > Configuration: > > Logical max current > > cylinders 16383 16383 > > heads 16 16 > > sectors/track 63 63 > > -- > > CHS current addressable sectors: 16514064 > > LBAuser addressable sectors: 268435455 > > LBA48 user addressable sectors: 781422768 > > device size with M = 1024*1024: 381554 MBytes > > device size with M = 1000*1000: 400088 MBytes (400 GB) > > That's a fairly recent drive. Does the problem go away if you downgrade > the kernel? Yes, for me the problem was introduced recently. I have moved around terabytes (sic!) on my discs with older kernels and I never got errors. -Christian - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [BUG 2.6.21-rc3-git9] SATA NCQ failure with Samsum HD401LJ
On Monday 19 March 2007 03:48:14 you wrote: Christian wrote: On Sunday 18 March 2007 06:43:09 you wrote: Christian wrote: This does indeed look like a drive side issue to me (the controller is reporting CPBs with response flags 2 which as far as I can tell indicates it's still waiting for the drive to complete the request). I have been using this hw-config (SATA II, NCQ) since the nvidia ADMA support made it in the -mm kernel (maybe around 2.6.19-mm? or even earlyer). I'm seeing this problem excessively since I upgraded to 2.6.21-rc3-mm1. I think something got broken recently... Can you post the result of hdparm -I /dev/sdX? Output generated on 2.6.21-rc3-mm1 #3 SMP PREEMPT [EMAIL PROTECTED]:~$ sudo hdparm -I /dev/sda /dev/sda: ATA device, with non-removable media Model Number: SAMSUNG HD401LJ Serial Number: S0HVJ1FL900207 Firmware Revision: ZZ100-15 Standards: Used: ATA/ATAPI-7 T13 1532D revision 4a Supported: 7 6 5 4 Configuration: Logical max current cylinders 16383 16383 heads 16 16 sectors/track 63 63 -- CHS current addressable sectors: 16514064 LBAuser addressable sectors: 268435455 LBA48 user addressable sectors: 781422768 device size with M = 1024*1024: 381554 MBytes device size with M = 1000*1000: 400088 MBytes (400 GB) That's a fairly recent drive. Does the problem go away if you downgrade the kernel? Yes, for me the problem was introduced recently. I have moved around terabytes (sic!) on my discs with older kernels and I never got errors. -Christian - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [BUG 2.6.21-rc3-git9] SATA NCQ failure with Samsum HD401LJ
Christian wrote: Yes, for me the problem was introduced recently. I have moved around terabytes (sic!) on my discs with older kernels and I never got errors. There is always the possibility of disk going bad, so it would be great if you can boot an older kernel and verify that the problem doesn't occur on it. Thanks. -- tejun - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [BUG 2.6.21-rc3-git9] SATA NCQ failure with Samsum HD401LJ
Christian wrote: On Monday 19 March 2007 03:48:14 you wrote: Christian wrote: On Sunday 18 March 2007 06:43:09 you wrote: Christian wrote: This does indeed look like a drive side issue to me (the controller is reporting CPBs with response flags 2 which as far as I can tell indicates it's still waiting for the drive to complete the request). I have been using this hw-config (SATA II, NCQ) since the nvidia ADMA support made it in the -mm kernel (maybe around 2.6.19-mm? or even earlyer). I'm seeing this problem excessively since I upgraded to 2.6.21-rc3-mm1. I think something got broken recently... Can you post the result of hdparm -I /dev/sdX? Output generated on 2.6.21-rc3-mm1 #3 SMP PREEMPT [EMAIL PROTECTED]:~$ sudo hdparm -I /dev/sda /dev/sda: ATA device, with non-removable media Model Number: SAMSUNG HD401LJ Serial Number: S0HVJ1FL900207 Firmware Revision: ZZ100-15 Standards: Used: ATA/ATAPI-7 T13 1532D revision 4a Supported: 7 6 5 4 Configuration: Logical max current cylinders 16383 16383 heads 16 16 sectors/track 63 63 -- CHS current addressable sectors: 16514064 LBAuser addressable sectors: 268435455 LBA48 user addressable sectors: 781422768 device size with M = 1024*1024: 381554 MBytes device size with M = 1000*1000: 400088 MBytes (400 GB) That's a fairly recent drive. Does the problem go away if you downgrade the kernel? Yes, for me the problem was introduced recently. I have moved around terabytes (sic!) on my discs with older kernels and I never got errors. I may have missed the answer to this before, but: does the problem go away if you disable preempt? Jeff - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [BUG 2.6.21-rc3-git9] SATA NCQ failure with Samsum HD401LJ
Christian wrote: On Sunday 18 March 2007 06:43:09 you wrote: Christian wrote: This does indeed look like a drive side issue to me (the controller is reporting CPBs with response flags 2 which as far as I can tell indicates it's still waiting for the drive to complete the request). I have been using this hw-config (SATA II, NCQ) since the nvidia ADMA support made it in the -mm kernel (maybe around 2.6.19-mm? or even earlyer). I'm seeing this problem excessively since I upgraded to 2.6.21-rc3-mm1. I think something got broken recently... Can you post the result of hdparm -I /dev/sdX? Output generated on 2.6.21-rc3-mm1 #3 SMP PREEMPT [EMAIL PROTECTED]:~$ sudo hdparm -I /dev/sda /dev/sda: ATA device, with non-removable media Model Number: SAMSUNG HD401LJ Serial Number: S0HVJ1FL900207 Firmware Revision: ZZ100-15 Standards: Used: ATA/ATAPI-7 T13 1532D revision 4a Supported: 7 6 5 4 Configuration: Logical max current cylinders 16383 16383 heads 16 16 sectors/track 63 63 -- CHS current addressable sectors: 16514064 LBAuser addressable sectors: 268435455 LBA48 user addressable sectors: 781422768 device size with M = 1024*1024: 381554 MBytes device size with M = 1000*1000: 400088 MBytes (400 GB) Capabilities: LBA, IORDY(can be disabled) Queue depth: 32 Standby timer values: spec'd by Standard, no device specific minimum R/W multiple sector transfer: Max = 16 Current = 16 Recommended acoustic management value: 254, current value: 0 DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6 udma7 Cycle time: min=120ns recommended=120ns PIO: pio0 pio1 pio2 pio3 pio4 Cycle time: no flow control=120ns IORDY flow control=120ns Commands/features: Enabled Supported: *SMART feature set Security Mode feature set *Power Management feature set *Write cache *Look-ahead *Host Protected Area feature set *WRITE_BUFFER command *READ_BUFFER command *NOP cmd *DOWNLOAD_MICROCODE SET_MAX security extension Automatic Acoustic Management feature set *48-bit Address feature set *Device Configuration Overlay feature set *Mandatory FLUSH_CACHE *FLUSH_CACHE_EXT *SMART error logging *SMART self-test *General Purpose Logging feature set *SATA-I signaling speed (1.5Gb/s) *SATA-II signaling speed (3.0Gb/s) *Native Command Queueing (NCQ) *Host-initiated interface power management *Phy event counters DMA Setup Auto-Activate optimization Device-initiated interface power management *Software settings preservation *SMART Command Transport (SCT) feature set *SCT Long Sector Access (AC1) *SCT LBA Segment Access (AC2) *SCT Error Recovery Control (AC3) *SCT Features Control (AC4) *SCT Data Tables (AC5) Security: Master password revision code = 65534 supported not enabled not locked frozen not expired: security count supported: enhanced erase 228min for SECURITY ERASE UNIT. 228min for ENHANCED SECURITY ERASE UNIT. Checksum: correct [EMAIL PROTECTED]:~$ sudo hdparm -I /dev/sdb /dev/sdb: ATA device, with non-removable media Model Number: SAMSUNG SP2504C Serial Number: S09QJ1LYC06381 Firmware Revision: VT100-33 Standards: Used: ATA/ATAPI-7 T13 1532D revision 4a Supported: 7 6 5 4 Configuration: Logical max current cylinders 16383 16383 heads 16 16 sectors/track 63 63 -- CHS current addressable sectors: 16514064 LBAuser addressable sectors: 268435455 LBA48 user addressable sectors: 488397168 device size with M = 1024*1024: 238475 MBytes device size with M = 1000*1000: 250059 MBytes (250 GB) Capabilities: LBA, IORDY(can be disabled) Queue depth: 32 Standby timer values: spec'd by Standard, no device specific minimum R/W multiple sector transfer: Max = 16 Current = 16 Recommended acoustic management value: 254, current value: 254 DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6 udma7 Cycle time: min=120ns recommended=120ns PIO: pio0 pio1 pio2 pio3 pio4
Re: [BUG 2.6.21-rc3-git9] SATA NCQ failure with Samsum HD401LJ
Christian wrote: > On Sunday 18 March 2007 06:43:09 you wrote: >> Christian wrote: This does indeed look like a drive side issue to me (the controller is reporting CPBs with response flags 2 which as far as I can tell indicates it's still waiting for the drive to complete the request). >>> I have been using this hw-config (SATA II, NCQ) since the nvidia ADMA >>> support made it in the -mm kernel (maybe around 2.6.19-mm? or even >>> earlyer). I'm seeing this problem excessively since I upgraded to >>> 2.6.21-rc3-mm1. I think something got broken recently... >> Can you post the result of "hdparm -I /dev/sdX"? > > Output generated on 2.6.21-rc3-mm1 #3 SMP PREEMPT > > [EMAIL PROTECTED]:~$ sudo hdparm -I /dev/sda > > /dev/sda: > > ATA device, with non-removable media > Model Number: SAMSUNG HD401LJ > Serial Number: S0HVJ1FL900207 > Firmware Revision: ZZ100-15 > Standards: > Used: ATA/ATAPI-7 T13 1532D revision 4a > Supported: 7 6 5 4 > Configuration: > Logical max current > cylinders 16383 16383 > heads 16 16 > sectors/track 63 63 > -- > CHS current addressable sectors: 16514064 > LBAuser addressable sectors: 268435455 > LBA48 user addressable sectors: 781422768 > device size with M = 1024*1024: 381554 MBytes > device size with M = 1000*1000: 400088 MBytes (400 GB) That's a fairly recent drive. Does the problem go away if you downgrade the kernel? -- tejun - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [BUG 2.6.21-rc3-git9] SATA NCQ failure with Samsum HD401LJ
On Sunday 18 March 2007 06:43:09 you wrote: > Christian wrote: > >> This does indeed look like a drive side issue to me (the controller is > >> reporting CPBs with response flags 2 which as far as I can tell > >> indicates it's still waiting for the drive to complete the request). > > > > I have been using this hw-config (SATA II, NCQ) since the nvidia ADMA > > support made it in the -mm kernel (maybe around 2.6.19-mm? or even > > earlyer). I'm seeing this problem excessively since I upgraded to > > 2.6.21-rc3-mm1. I think something got broken recently... > > Can you post the result of "hdparm -I /dev/sdX"? Output generated on 2.6.21-rc3-mm1 #3 SMP PREEMPT [EMAIL PROTECTED]:~$ sudo hdparm -I /dev/sda /dev/sda: ATA device, with non-removable media Model Number: SAMSUNG HD401LJ Serial Number: S0HVJ1FL900207 Firmware Revision: ZZ100-15 Standards: Used: ATA/ATAPI-7 T13 1532D revision 4a Supported: 7 6 5 4 Configuration: Logical max current cylinders 16383 16383 heads 16 16 sectors/track 63 63 -- CHS current addressable sectors: 16514064 LBAuser addressable sectors: 268435455 LBA48 user addressable sectors: 781422768 device size with M = 1024*1024: 381554 MBytes device size with M = 1000*1000: 400088 MBytes (400 GB) Capabilities: LBA, IORDY(can be disabled) Queue depth: 32 Standby timer values: spec'd by Standard, no device specific minimum R/W multiple sector transfer: Max = 16 Current = 16 Recommended acoustic management value: 254, current value: 0 DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6 udma7 Cycle time: min=120ns recommended=120ns PIO: pio0 pio1 pio2 pio3 pio4 Cycle time: no flow control=120ns IORDY flow control=120ns Commands/features: Enabled Supported: *SMART feature set Security Mode feature set *Power Management feature set *Write cache *Look-ahead *Host Protected Area feature set *WRITE_BUFFER command *READ_BUFFER command *NOP cmd *DOWNLOAD_MICROCODE SET_MAX security extension Automatic Acoustic Management feature set *48-bit Address feature set *Device Configuration Overlay feature set *Mandatory FLUSH_CACHE *FLUSH_CACHE_EXT *SMART error logging *SMART self-test *General Purpose Logging feature set *SATA-I signaling speed (1.5Gb/s) *SATA-II signaling speed (3.0Gb/s) *Native Command Queueing (NCQ) *Host-initiated interface power management *Phy event counters DMA Setup Auto-Activate optimization Device-initiated interface power management *Software settings preservation *SMART Command Transport (SCT) feature set *SCT Long Sector Access (AC1) *SCT LBA Segment Access (AC2) *SCT Error Recovery Control (AC3) *SCT Features Control (AC4) *SCT Data Tables (AC5) Security: Master password revision code = 65534 supported not enabled not locked frozen not expired: security count supported: enhanced erase 228min for SECURITY ERASE UNIT. 228min for ENHANCED SECURITY ERASE UNIT. Checksum: correct [EMAIL PROTECTED]:~$ sudo hdparm -I /dev/sdb /dev/sdb: ATA device, with non-removable media Model Number: SAMSUNG SP2504C Serial Number: S09QJ1LYC06381 Firmware Revision: VT100-33 Standards: Used: ATA/ATAPI-7 T13 1532D revision 4a Supported: 7 6 5 4 Configuration: Logical max current cylinders 16383 16383 heads 16 16 sectors/track 63 63 -- CHS current addressable sectors: 16514064 LBAuser addressable sectors: 268435455 LBA48 user addressable sectors: 488397168 device size with M = 1024*1024: 238475 MBytes device size with M = 1000*1000: 250059 MBytes (250 GB) Capabilities: LBA, IORDY(can be disabled) Queue depth: 32 Standby timer values: spec'd by Standard, no device specific minimum R/W multiple sector transfer: Max = 16 Current = 16 Recommended acoustic management value: 254, current value: 254 DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6 udma7 Cycle time: min=120ns recommended=120ns PIO: pio0 pio1 pio2 pio3 pio4 Cycle
Re: [BUG 2.6.21-rc3-git9] SATA NCQ failure with Samsum HD401LJ
On Sunday 18 March 2007 06:43:09 you wrote: Christian wrote: This does indeed look like a drive side issue to me (the controller is reporting CPBs with response flags 2 which as far as I can tell indicates it's still waiting for the drive to complete the request). I have been using this hw-config (SATA II, NCQ) since the nvidia ADMA support made it in the -mm kernel (maybe around 2.6.19-mm? or even earlyer). I'm seeing this problem excessively since I upgraded to 2.6.21-rc3-mm1. I think something got broken recently... Can you post the result of hdparm -I /dev/sdX? Output generated on 2.6.21-rc3-mm1 #3 SMP PREEMPT [EMAIL PROTECTED]:~$ sudo hdparm -I /dev/sda /dev/sda: ATA device, with non-removable media Model Number: SAMSUNG HD401LJ Serial Number: S0HVJ1FL900207 Firmware Revision: ZZ100-15 Standards: Used: ATA/ATAPI-7 T13 1532D revision 4a Supported: 7 6 5 4 Configuration: Logical max current cylinders 16383 16383 heads 16 16 sectors/track 63 63 -- CHS current addressable sectors: 16514064 LBAuser addressable sectors: 268435455 LBA48 user addressable sectors: 781422768 device size with M = 1024*1024: 381554 MBytes device size with M = 1000*1000: 400088 MBytes (400 GB) Capabilities: LBA, IORDY(can be disabled) Queue depth: 32 Standby timer values: spec'd by Standard, no device specific minimum R/W multiple sector transfer: Max = 16 Current = 16 Recommended acoustic management value: 254, current value: 0 DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6 udma7 Cycle time: min=120ns recommended=120ns PIO: pio0 pio1 pio2 pio3 pio4 Cycle time: no flow control=120ns IORDY flow control=120ns Commands/features: Enabled Supported: *SMART feature set Security Mode feature set *Power Management feature set *Write cache *Look-ahead *Host Protected Area feature set *WRITE_BUFFER command *READ_BUFFER command *NOP cmd *DOWNLOAD_MICROCODE SET_MAX security extension Automatic Acoustic Management feature set *48-bit Address feature set *Device Configuration Overlay feature set *Mandatory FLUSH_CACHE *FLUSH_CACHE_EXT *SMART error logging *SMART self-test *General Purpose Logging feature set *SATA-I signaling speed (1.5Gb/s) *SATA-II signaling speed (3.0Gb/s) *Native Command Queueing (NCQ) *Host-initiated interface power management *Phy event counters DMA Setup Auto-Activate optimization Device-initiated interface power management *Software settings preservation *SMART Command Transport (SCT) feature set *SCT Long Sector Access (AC1) *SCT LBA Segment Access (AC2) *SCT Error Recovery Control (AC3) *SCT Features Control (AC4) *SCT Data Tables (AC5) Security: Master password revision code = 65534 supported not enabled not locked frozen not expired: security count supported: enhanced erase 228min for SECURITY ERASE UNIT. 228min for ENHANCED SECURITY ERASE UNIT. Checksum: correct [EMAIL PROTECTED]:~$ sudo hdparm -I /dev/sdb /dev/sdb: ATA device, with non-removable media Model Number: SAMSUNG SP2504C Serial Number: S09QJ1LYC06381 Firmware Revision: VT100-33 Standards: Used: ATA/ATAPI-7 T13 1532D revision 4a Supported: 7 6 5 4 Configuration: Logical max current cylinders 16383 16383 heads 16 16 sectors/track 63 63 -- CHS current addressable sectors: 16514064 LBAuser addressable sectors: 268435455 LBA48 user addressable sectors: 488397168 device size with M = 1024*1024: 238475 MBytes device size with M = 1000*1000: 250059 MBytes (250 GB) Capabilities: LBA, IORDY(can be disabled) Queue depth: 32 Standby timer values: spec'd by Standard, no device specific minimum R/W multiple sector transfer: Max = 16 Current = 16 Recommended acoustic management value: 254, current value: 254 DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6 udma7 Cycle time: min=120ns recommended=120ns PIO: pio0 pio1 pio2 pio3 pio4 Cycle time: no flow control=120ns
Re: [BUG 2.6.21-rc3-git9] SATA NCQ failure with Samsum HD401LJ
Christian wrote: On Sunday 18 March 2007 06:43:09 you wrote: Christian wrote: This does indeed look like a drive side issue to me (the controller is reporting CPBs with response flags 2 which as far as I can tell indicates it's still waiting for the drive to complete the request). I have been using this hw-config (SATA II, NCQ) since the nvidia ADMA support made it in the -mm kernel (maybe around 2.6.19-mm? or even earlyer). I'm seeing this problem excessively since I upgraded to 2.6.21-rc3-mm1. I think something got broken recently... Can you post the result of hdparm -I /dev/sdX? Output generated on 2.6.21-rc3-mm1 #3 SMP PREEMPT [EMAIL PROTECTED]:~$ sudo hdparm -I /dev/sda /dev/sda: ATA device, with non-removable media Model Number: SAMSUNG HD401LJ Serial Number: S0HVJ1FL900207 Firmware Revision: ZZ100-15 Standards: Used: ATA/ATAPI-7 T13 1532D revision 4a Supported: 7 6 5 4 Configuration: Logical max current cylinders 16383 16383 heads 16 16 sectors/track 63 63 -- CHS current addressable sectors: 16514064 LBAuser addressable sectors: 268435455 LBA48 user addressable sectors: 781422768 device size with M = 1024*1024: 381554 MBytes device size with M = 1000*1000: 400088 MBytes (400 GB) That's a fairly recent drive. Does the problem go away if you downgrade the kernel? -- tejun - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [BUG 2.6.21-rc3-git9] SATA NCQ failure with Samsum HD401LJ
Christian wrote: >> This does indeed look like a drive side issue to me (the controller is >> reporting CPBs with response flags 2 which as far as I can tell >> indicates it's still waiting for the drive to complete the request). > > I have been using this hw-config (SATA II, NCQ) since the nvidia ADMA support > made it in the -mm kernel (maybe around 2.6.19-mm? or even earlyer). I'm > seeing this problem excessively since I upgraded to 2.6.21-rc3-mm1. I think > something got broken recently... Can you post the result of "hdparm -I /dev/sdX"? -- tejun - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [BUG 2.6.21-rc3-git9] SATA NCQ failure with Samsum HD401LJ
Christian wrote: This does indeed look like a drive side issue to me (the controller is reporting CPBs with response flags 2 which as far as I can tell indicates it's still waiting for the drive to complete the request). I have been using this hw-config (SATA II, NCQ) since the nvidia ADMA support made it in the -mm kernel (maybe around 2.6.19-mm? or even earlyer). I'm seeing this problem excessively since I upgraded to 2.6.21-rc3-mm1. I think something got broken recently... Can you post the result of hdparm -I /dev/sdX? -- tejun - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [BUG 2.6.21-rc3-git9] SATA NCQ failure with Samsum HD401LJ
> This does indeed look like a drive side issue to me (the controller is > reporting CPBs with response flags 2 which as far as I can tell > indicates it's still waiting for the drive to complete the request). I have been using this hw-config (SATA II, NCQ) since the nvidia ADMA support made it in the -mm kernel (maybe around 2.6.19-mm? or even earlyer). I'm seeing this problem excessively since I upgraded to 2.6.21-rc3-mm1. I think something got broken recently... -Christian - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [BUG 2.6.21-rc3-git9] SATA NCQ failure with Samsum HD401LJ
On Friday 16 March 2007 12:20:02 Max Kellermann wrote: > Hi, > > I have been trying to upgrade my 2.6.19 kernel for a while now, > without success. All kernel versions since 2.6.20 failed with a > timeout while trying to write to my SATA hard disk. After I wait for > a while (during which all I/O to the hard disk blocks), the kernel > message "NCQ disabled due to excessive errors" appears, and the system > seems to work perfectly. > > My system is an Athlon64 X2 on an Asus A8N-Premium. I'm using the > sata_nv driver for the on-board SATA controller. My only hard disk is > a Samsum HD401LJ (400 GB). > > The kernel is build statically, and the only module is nvidia.ko. If > someone believes it may make a difference, I can try the kernel > without the proprietary module. > > Please see the kernel config and dmesg attached to this email. > > I don't know the libata subsystem well, but I suspect my hard drive > has to be added to the NCQ blacklist. > > Max Hi, I have the same HW ;-) And the same problem on 2.6.21-rc3-mm1. [ 8212.682404] ata1: EH in ADMA mode, notifier 0x0 notifier_error 0x0 gen_ctl 0x1501000 status 0x400 next cpb count 0x0 next cpb idx 0x0 [ 8212.682409] ata1: CPB 1: ctl_flags 0x1f, resp_flags 0x2 [ 8212.682411] ata1: CPB 2: ctl_flags 0x1f, resp_flags 0x2 [ 8212.682413] ata1: CPB 3: ctl_flags 0x1f, resp_flags 0x2 [ 8212.682416] ata1: EH in ADMA mode, notifier 0x0 notifier_error 0x0 gen_ctl 0x1501000 status 0x400 [ 8212.682419] ata1: CPB 1: ctl_flags 0x1f, resp_flags 0x2 [ 8212.682420] ata1: CPB 2: ctl_flags 0x1f, resp_flags 0x2 [ 8212.682422] ata1: CPB 3: ctl_flags 0x1f, resp_flags 0x2 [ 8212.682427] ata1: timeout waiting for ADMA IDLE, stat=0x400 [ 8212.682432] ata1: timeout waiting for ADMA LEGACY, stat=0x400 [ 8212.682439] ata1.00: exception Emask 0x0 SAct 0xe SErr 0x20 action 0x2 frozen [ 8212.682445] ata1.00: cmd 61/00:08:df:90:f7/02:00:02:00:00/40 tag 1 cdb 0x0 data 262144 out [ 8212.682446] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) [ 8212.682451] ata1.00: cmd 61/00:10:df:92:f7/02:00:02:00:00/40 tag 2 cdb 0x0 data 262144 out [ 8212.682453] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) [ 8212.682457] ata1.00: cmd 61/00:18:df:94:f7/02:00:02:00:00/40 tag 3 cdb 0x0 data 262144 out [ 8212.682459] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) [ 8212.833749] ata1: soft resetting port [ 8212.941187] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 8212.992763] ata1.00: configured for UDMA/133 [ 8212.992837] ata1: EH complete [ 8212.992906] SCSI device sda: 781422768 512-byte hdwr sectors (400088 MB) [ 8212.992936] sda: Write Protect is off [ 8212.992938] sda: Mode Sense: 00 3a 00 00 [ 8212.993048] SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 8227.981905] ata1: EH in ADMA mode, notifier 0x0 notifier_error 0x0 gen_ctl 0x1501000 status 0x400 next cpb count 0x2 next cpb idx 0x0 [ 8227.981910] ata1: CPB 0: ctl_flags 0x1f, resp_flags 0x0 [ 8227.981912] ata1: CPB 1: ctl_flags 0x1f, resp_flags 0x0 [ 8227.981914] ata1: CPB 2: ctl_flags 0x1f, resp_flags 0x0 [ 8227.981917] ata1: EH in ADMA mode, notifier 0x0 notifier_error 0x0 gen_ctl 0x1501000 status 0x400 [ 8227.981919] ata1: CPB 0: ctl_flags 0x1f, resp_flags 0x0 [ 8227.981921] ata1: CPB 1: ctl_flags 0x1f, resp_flags 0x0 [ 8227.981923] ata1: CPB 2: ctl_flags 0x1f, resp_flags 0x0 [ 8227.981928] ata1: timeout waiting for ADMA IDLE, stat=0x400 [ 8227.981933] ata1: timeout waiting for ADMA LEGACY, stat=0x400 [ 8227.981940] ata1.00: exception Emask 0x0 SAct 0x7 SErr 0x0 action 0x2 frozen [ 8227.981945] ata1.00: cmd 61/00:00:df:94:f7/02:00:02:00:00/40 tag 0 cdb 0x0 data 262144 out [ 8227.981947] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) [ 8227.981952] ata1.00: cmd 61/00:08:df:92:f7/02:00:02:00:00/40 tag 1 cdb 0x0 data 262144 out [ 8227.981953] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) [ 8227.981958] ata1.00: cmd 61/00:10:df:90:f7/02:00:02:00:00/40 tag 2 cdb 0x0 data 262144 out [ 8227.981959] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) [ 8228.133306] ata1: soft resetting port [ 8228.208763] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 8228.258729] ata1.00: configured for UDMA/133 [ 8228.258824] ata1: EH complete [ 8228.258926] SCSI device sda: 781422768 512-byte hdwr sectors (400088 MB) [ 8228.259021] sda: Write Protect is off [ 8228.259023] sda: Mode Sense: 00 3a 00 00 [ 8228.259132] SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 8243.247980] ata1: EH in ADMA mode, notifier 0x0 notifier_error 0x0 gen_ctl 0x1501000 status 0x400 next cpb count 0x2 next cpb idx 0x0 [ 8243.247985] ata1: CPB 0: ctl_flags 0x1f, resp_flags 0x0 [ 8243.247987] ata1: CPB 1: ctl_flags 0x1f, resp_flags 0x0 [ 8243.247989] ata1: CPB 2: ctl_flags 0x1f, resp_flags 0x0 [ 8243.247992] ata1: EH in ADMA mode,
Re: [BUG 2.6.21-rc3-git9] SATA NCQ failure with Samsum HD401LJ
(linux-ide cc'ed) Max Kellermann wrote: Hi, I have been trying to upgrade my 2.6.19 kernel for a while now, without success. All kernel versions since 2.6.20 failed with a timeout while trying to write to my SATA hard disk. After I wait for a while (during which all I/O to the hard disk blocks), the kernel message "NCQ disabled due to excessive errors" appears, and the system seems to work perfectly. My system is an Athlon64 X2 on an Asus A8N-Premium. I'm using the sata_nv driver for the on-board SATA controller. My only hard disk is a Samsum HD401LJ (400 GB). The kernel is build statically, and the only module is nvidia.ko. If someone believes it may make a difference, I can try the kernel without the proprietary module. Please see the kernel config and dmesg attached to this email. I don't know the libata subsystem well, but I suspect my hard drive has to be added to the NCQ blacklist. Max This does indeed look like a drive side issue to me (the controller is reporting CPBs with response flags 2 which as far as I can tell indicates it's still waiting for the drive to complete the request). -- Robert Hancock Saskatoon, SK, Canada To email, remove "nospam" from [EMAIL PROTECTED] Home Page: http://www.roberthancock.com/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [BUG 2.6.21-rc3-git9] SATA NCQ failure with Samsum HD401LJ
On Friday 16 March 2007 12:20:02 Max Kellermann wrote: Hi, I have been trying to upgrade my 2.6.19 kernel for a while now, without success. All kernel versions since 2.6.20 failed with a timeout while trying to write to my SATA hard disk. After I wait for a while (during which all I/O to the hard disk blocks), the kernel message NCQ disabled due to excessive errors appears, and the system seems to work perfectly. My system is an Athlon64 X2 on an Asus A8N-Premium. I'm using the sata_nv driver for the on-board SATA controller. My only hard disk is a Samsum HD401LJ (400 GB). The kernel is build statically, and the only module is nvidia.ko. If someone believes it may make a difference, I can try the kernel without the proprietary module. Please see the kernel config and dmesg attached to this email. I don't know the libata subsystem well, but I suspect my hard drive has to be added to the NCQ blacklist. Max Hi, I have the same HW ;-) And the same problem on 2.6.21-rc3-mm1. [ 8212.682404] ata1: EH in ADMA mode, notifier 0x0 notifier_error 0x0 gen_ctl 0x1501000 status 0x400 next cpb count 0x0 next cpb idx 0x0 [ 8212.682409] ata1: CPB 1: ctl_flags 0x1f, resp_flags 0x2 [ 8212.682411] ata1: CPB 2: ctl_flags 0x1f, resp_flags 0x2 [ 8212.682413] ata1: CPB 3: ctl_flags 0x1f, resp_flags 0x2 [ 8212.682416] ata1: EH in ADMA mode, notifier 0x0 notifier_error 0x0 gen_ctl 0x1501000 status 0x400 [ 8212.682419] ata1: CPB 1: ctl_flags 0x1f, resp_flags 0x2 [ 8212.682420] ata1: CPB 2: ctl_flags 0x1f, resp_flags 0x2 [ 8212.682422] ata1: CPB 3: ctl_flags 0x1f, resp_flags 0x2 [ 8212.682427] ata1: timeout waiting for ADMA IDLE, stat=0x400 [ 8212.682432] ata1: timeout waiting for ADMA LEGACY, stat=0x400 [ 8212.682439] ata1.00: exception Emask 0x0 SAct 0xe SErr 0x20 action 0x2 frozen [ 8212.682445] ata1.00: cmd 61/00:08:df:90:f7/02:00:02:00:00/40 tag 1 cdb 0x0 data 262144 out [ 8212.682446] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) [ 8212.682451] ata1.00: cmd 61/00:10:df:92:f7/02:00:02:00:00/40 tag 2 cdb 0x0 data 262144 out [ 8212.682453] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) [ 8212.682457] ata1.00: cmd 61/00:18:df:94:f7/02:00:02:00:00/40 tag 3 cdb 0x0 data 262144 out [ 8212.682459] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) [ 8212.833749] ata1: soft resetting port [ 8212.941187] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 8212.992763] ata1.00: configured for UDMA/133 [ 8212.992837] ata1: EH complete [ 8212.992906] SCSI device sda: 781422768 512-byte hdwr sectors (400088 MB) [ 8212.992936] sda: Write Protect is off [ 8212.992938] sda: Mode Sense: 00 3a 00 00 [ 8212.993048] SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 8227.981905] ata1: EH in ADMA mode, notifier 0x0 notifier_error 0x0 gen_ctl 0x1501000 status 0x400 next cpb count 0x2 next cpb idx 0x0 [ 8227.981910] ata1: CPB 0: ctl_flags 0x1f, resp_flags 0x0 [ 8227.981912] ata1: CPB 1: ctl_flags 0x1f, resp_flags 0x0 [ 8227.981914] ata1: CPB 2: ctl_flags 0x1f, resp_flags 0x0 [ 8227.981917] ata1: EH in ADMA mode, notifier 0x0 notifier_error 0x0 gen_ctl 0x1501000 status 0x400 [ 8227.981919] ata1: CPB 0: ctl_flags 0x1f, resp_flags 0x0 [ 8227.981921] ata1: CPB 1: ctl_flags 0x1f, resp_flags 0x0 [ 8227.981923] ata1: CPB 2: ctl_flags 0x1f, resp_flags 0x0 [ 8227.981928] ata1: timeout waiting for ADMA IDLE, stat=0x400 [ 8227.981933] ata1: timeout waiting for ADMA LEGACY, stat=0x400 [ 8227.981940] ata1.00: exception Emask 0x0 SAct 0x7 SErr 0x0 action 0x2 frozen [ 8227.981945] ata1.00: cmd 61/00:00:df:94:f7/02:00:02:00:00/40 tag 0 cdb 0x0 data 262144 out [ 8227.981947] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) [ 8227.981952] ata1.00: cmd 61/00:08:df:92:f7/02:00:02:00:00/40 tag 1 cdb 0x0 data 262144 out [ 8227.981953] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) [ 8227.981958] ata1.00: cmd 61/00:10:df:90:f7/02:00:02:00:00/40 tag 2 cdb 0x0 data 262144 out [ 8227.981959] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) [ 8228.133306] ata1: soft resetting port [ 8228.208763] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 8228.258729] ata1.00: configured for UDMA/133 [ 8228.258824] ata1: EH complete [ 8228.258926] SCSI device sda: 781422768 512-byte hdwr sectors (400088 MB) [ 8228.259021] sda: Write Protect is off [ 8228.259023] sda: Mode Sense: 00 3a 00 00 [ 8228.259132] SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 8243.247980] ata1: EH in ADMA mode, notifier 0x0 notifier_error 0x0 gen_ctl 0x1501000 status 0x400 next cpb count 0x2 next cpb idx 0x0 [ 8243.247985] ata1: CPB 0: ctl_flags 0x1f, resp_flags 0x0 [ 8243.247987] ata1: CPB 1: ctl_flags 0x1f, resp_flags 0x0 [ 8243.247989] ata1: CPB 2: ctl_flags 0x1f, resp_flags 0x0 [ 8243.247992] ata1: EH in ADMA mode, notifier 0x0
Re: [BUG 2.6.21-rc3-git9] SATA NCQ failure with Samsum HD401LJ
This does indeed look like a drive side issue to me (the controller is reporting CPBs with response flags 2 which as far as I can tell indicates it's still waiting for the drive to complete the request). I have been using this hw-config (SATA II, NCQ) since the nvidia ADMA support made it in the -mm kernel (maybe around 2.6.19-mm? or even earlyer). I'm seeing this problem excessively since I upgraded to 2.6.21-rc3-mm1. I think something got broken recently... -Christian - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [BUG 2.6.21-rc3-git9] SATA NCQ failure with Samsum HD401LJ
(linux-ide cc'ed) Max Kellermann wrote: Hi, I have been trying to upgrade my 2.6.19 kernel for a while now, without success. All kernel versions since 2.6.20 failed with a timeout while trying to write to my SATA hard disk. After I wait for a while (during which all I/O to the hard disk blocks), the kernel message NCQ disabled due to excessive errors appears, and the system seems to work perfectly. My system is an Athlon64 X2 on an Asus A8N-Premium. I'm using the sata_nv driver for the on-board SATA controller. My only hard disk is a Samsum HD401LJ (400 GB). The kernel is build statically, and the only module is nvidia.ko. If someone believes it may make a difference, I can try the kernel without the proprietary module. Please see the kernel config and dmesg attached to this email. I don't know the libata subsystem well, but I suspect my hard drive has to be added to the NCQ blacklist. Max This does indeed look like a drive side issue to me (the controller is reporting CPBs with response flags 2 which as far as I can tell indicates it's still waiting for the drive to complete the request). -- Robert Hancock Saskatoon, SK, Canada To email, remove nospam from [EMAIL PROTECTED] Home Page: http://www.roberthancock.com/ - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
