Errors with AHCI and 10K Raptor drive

All of lore.kernel.org
 help / color / mirror / Atom feed

* Errors with AHCI and 10K Raptor drive
@ 2007-03-19 14:53 Stephen Hemminger
  2007-03-19 15:01 ` Jeff Garzik
  0 siblings, 1 reply; 6+ messages in thread
From: Stephen Hemminger @ 2007-03-19 14:53 UTC (permalink / raw)
  To: Jeff Garzik; +Cc: linux-ide

I am getting lots of these errors under moderate load.
This is a new drive, so I suspect some driver incompatibility between the
driver (AHCI) and the hard drive (WD Raptor 10K 74G).

Lspci:
00:1f.2 SATA controller: Intel Corporation 82801FR/FRW (ICH6R/ICH6RW) SATA Controller (rev 03) (prog-if 01 [AHCI 1.0])
	Subsystem: Intel Corporation Unknown device 4356
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Interrupt: pin B routed to IRQ 19
	Region 0: I/O ports at ec00 [size=8]
	Region 1: I/O ports at e800 [size=4]
	Region 2: I/O ports at e400 [size=8]
	Region 3: I/O ports at e000 [size=4]
	Region 4: I/O ports at dc00 [size=16]
	Region 5: Memory at dffffc00 (32-bit, non-prefetchable) [size=1K]

Log:

[  841.645699] ata1.00: exception Emask 0x10 SAct 0x2 SErr 0x400100 action 0x2 frozen
[  841.645708] ata1.00: (irq_stat 0x08000000, interface fatal error)
[  841.645719] ata1.00: cmd 61/00:08:17:31:f1/04:00:03:00:00/40 tag 1 cdb 0x0 data 524288 out
[  841.645721]          res 40/00:18:5f:fa:b9/00:00:01:00:00/40 Emask 0x10 (ATA bus error)
[  841.947855] ata1: soft resetting port
[  842.447515] ata1: softreset failed (1st FIS failed)
[  842.447526] ata1: softreset failed, retrying in 5 secs
[  847.445028] ata1: hard resetting port
[  854.938851] ata1: port is slow to respond, please be patient (Status 0x80)
[  877.923808] ata1: port failed to respond (30 secs, Status 0x80)
[  877.923816] ata1: COMRESET failed (device not ready)
[  877.923822] ata1: hardreset failed, retrying in 5 secs
[  882.921328] ata1: hard resetting port
[  883.377028] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[  883.391971] ata1.00: configured for UDMA/133
[  883.391992] ata1: EH complete
[  883.392186] SCSI device sda: 145226112 512-byte hdwr sectors (74356 MB)
[  883.392381] sda: Write Protect is off
[  883.392387] sda: Mode Sense: 00 3a 00 00
[  883.392594] SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[  970.422983] ata1.00: exception Emask 0x10 SAct 0x7 SErr 0x400100 action 0x2 frozen
[  970.422993] ata1.00: (irq_stat 0x08000000, interface fatal error)
[  970.423005] ata1.00: cmd 61/a8:00:0f:1d:cb/02:00:01:00:00/40 tag 0 cdb 0x0 data 348160 out
[  970.423008]          res 40/00:08:bf:24:cb/00:00:01:00:00/40 Emask 0x10 (ATA bus error)
[  970.423018] ata1.00: cmd 61/a8:08:bf:24:cb/00:00:01:00:00/40 tag 1 cdb 0x0 data 86016 out
[  970.423021]          res 40/00:08:bf:24:cb/00:00:01:00:00/40 Emask 0x10 (ATA bus error)
[  970.423031] ata1.00: cmd 61/08:10:97:41:c5/00:00:03:00:00/40 tag 2 cdb 0x0 data 4096 out
[  970.423034]          res 40/00:08:bf:24:cb/00:00:01:00:00/40 Emask 0x10 (ATA bus error)
[  970.725166] ata1: soft resetting port
[  970.725177] ata1: softreset failed (port busy but CLO unavailable)
[  970.725184] ata1: softreset failed, retrying in 5 secs
[  975.722701] ata1: hard resetting port
[  983.214510] ata1: port is slow to respond, please be patient (Status 0x80)
[ 1006.199471] ata1: port failed to respond (30 secs, Status 0x80)
[ 1006.199478] ata1: COMRESET failed (device not ready)
[ 1006.199485] ata1: hardreset failed, retrying in 5 secs
[ 1011.196989] ata1: hard resetting port
[ 1011.652683] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 1011.667748] ata1.00: configured for UDMA/133
[ 1011.667766] ata1: EH complete
[ 1011.667964] SCSI device sda: 145226112 512-byte hdwr sectors (74356 MB)
[ 1011.668157] sda: Write Protect is off
[ 1011.668163] sda: Mode Sense: 00 3a 00 00
[ 1011.668370] SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Errors with AHCI and 10K Raptor drive
  2007-03-19 14:53 Errors with AHCI and 10K Raptor drive Stephen Hemminger
@ 2007-03-19 15:01 ` Jeff Garzik
  2007-03-19 16:31   ` Stephen Hemminger
  2007-03-19 20:16   ` Stephen Hemminger
  0 siblings, 2 replies; 6+ messages in thread
From: Jeff Garzik @ 2007-03-19 15:01 UTC (permalink / raw)
  To: Stephen Hemminger; +Cc: linux-ide

Stephen Hemminger wrote:
> This is a new drive, so I suspect some driver incompatibility between the
> driver (AHCI) and the hard drive (WD Raptor 10K 74G).

Driver incompatibilities between the driver (LLDD or libata-core) and a 
hard drive are extremely rare.

The most common problem on modern SATA drives is drive firmware bugs, at 
the moment.


> [  841.645699] ata1.00: exception Emask 0x10 SAct 0x2 SErr 0x400100 action 0x2 frozen
> [  841.645708] ata1.00: (irq_stat 0x08000000, interface fatal error)
> [  841.645719] ata1.00: cmd 61/00:08:17:31:f1/04:00:03:00:00/40 tag 1 cdb 0x0 data 524288 out
> [  841.645721]          res 40/00:18:5f:fa:b9/00:00:01:00:00/40 Emask 0x10 (ATA bus error)
> [  841.947855] ata1: soft resetting port
> [  842.447515] ata1: softreset failed (1st FIS failed)
> [  842.447526] ata1: softreset failed, retrying in 5 secs
> [  847.445028] ata1: hard resetting port
> [  854.938851] ata1: port is slow to respond, please be patient (Status 0x80)
> [  877.923808] ata1: port failed to respond (30 secs, Status 0x80)
> [  877.923816] ata1: COMRESET failed (device not ready)
> [  877.923822] ata1: hardreset failed, retrying in 5 secs
> [  882.921328] ata1: hard resetting port
> [  883.377028] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> [  883.391971] ata1.00: configured for UDMA/133
> [  883.391992] ata1: EH complete
> [  883.392186] SCSI device sda: 145226112 512-byte hdwr sectors (74356 MB)
> [  883.392381] sda: Write Protect is off
> [  883.392387] sda: Mode Sense: 00 3a 00 00
> [  883.392594] SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
> [  970.422983] ata1.00: exception Emask 0x10 SAct 0x7 SErr 0x400100 action 0x2 frozen
> [  970.422993] ata1.00: (irq_stat 0x08000000, interface fatal error)
> [  970.423005] ata1.00: cmd 61/a8:00:0f:1d:cb/02:00:01:00:00/40 tag 0 cdb 0x0 data 348160 out
> [  970.423008]          res 40/00:08:bf:24:cb/00:00:01:00:00/40 Emask 0x10 (ATA bus error)
> [  970.423018] ata1.00: cmd 61/a8:08:bf:24:cb/00:00:01:00:00/40 tag 1 cdb 0x0 data 86016 out
> [  970.423021]          res 40/00:08:bf:24:cb/00:00:01:00:00/40 Emask 0x10 (ATA bus error)
> [  970.423031] ata1.00: cmd 61/08:10:97:41:c5/00:00:03:00:00/40 tag 2 cdb 0x0 data 4096 out
> [  970.423034]          res 40/00:08:bf:24:cb/00:00:01:00:00/40 Emask 0x10 (ATA bus error)

The PHY is crapping itself.  The port headers may be damaged on the 
drive or motherboard, or (most likely) you need a new cable.  SATA 
cables in particular are known to be lame.

Try different ports and cables.

You can also see what happens if you disable NCQ 
(http://linux-ata.org/faq.html#ncq).  Though given the interface errors, 
if disabling NCQ solves problems, it /may/ just be that you slowed 
things down enough to work, not that the drive firmware is bad.

	Jeff



^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Errors with AHCI and 10K Raptor drive
  2007-03-19 15:01 ` Jeff Garzik
@ 2007-03-19 16:31   ` Stephen Hemminger
  2007-03-19 20:16   ` Stephen Hemminger
  1 sibling, 0 replies; 6+ messages in thread
From: Stephen Hemminger @ 2007-03-19 16:31 UTC (permalink / raw)
  To: Jeff Garzik; +Cc: linux-ide

On Mon, 19 Mar 2007 11:01:37 -0400
Jeff Garzik <jgarzik@pobox.com> wrote:

> Stephen Hemminger wrote:
> > This is a new drive, so I suspect some driver incompatibility between the
> > driver (AHCI) and the hard drive (WD Raptor 10K 74G).
> 
> Driver incompatibilities between the driver (LLDD or libata-core) and a 
> hard drive are extremely rare.
> 
> The most common problem on modern SATA drives is drive firmware bugs, at 
> the moment.
> 
> 
> > [  841.645699] ata1.00: exception Emask 0x10 SAct 0x2 SErr 0x400100 action 0x2 frozen
> > [  841.645708] ata1.00: (irq_stat 0x08000000, interface fatal error)
> > [  841.645719] ata1.00: cmd 61/00:08:17:31:f1/04:00:03:00:00/40 tag 1 cdb 0x0 data 524288 out
> > [  841.645721]          res 40/00:18:5f:fa:b9/00:00:01:00:00/40 Emask 0x10 (ATA bus error)
> > [  841.947855] ata1: soft resetting port
> > [  842.447515] ata1: softreset failed (1st FIS failed)
> > [  842.447526] ata1: softreset failed, retrying in 5 secs
> > [  847.445028] ata1: hard resetting port
> > [  854.938851] ata1: port is slow to respond, please be patient (Status 0x80)
> > [  877.923808] ata1: port failed to respond (30 secs, Status 0x80)
> > [  877.923816] ata1: COMRESET failed (device not ready)
> > [  877.923822] ata1: hardreset failed, retrying in 5 secs
> > [  882.921328] ata1: hard resetting port
> > [  883.377028] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> > [  883.391971] ata1.00: configured for UDMA/133
> > [  883.391992] ata1: EH complete
> > [  883.392186] SCSI device sda: 145226112 512-byte hdwr sectors (74356 MB)
> > [  883.392381] sda: Write Protect is off
> > [  883.392387] sda: Mode Sense: 00 3a 00 00
> > [  883.392594] SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
> > [  970.422983] ata1.00: exception Emask 0x10 SAct 0x7 SErr 0x400100 action 0x2 frozen
> > [  970.422993] ata1.00: (irq_stat 0x08000000, interface fatal error)
> > [  970.423005] ata1.00: cmd 61/a8:00:0f:1d:cb/02:00:01:00:00/40 tag 0 cdb 0x0 data 348160 out
> > [  970.423008]          res 40/00:08:bf:24:cb/00:00:01:00:00/40 Emask 0x10 (ATA bus error)
> > [  970.423018] ata1.00: cmd 61/a8:08:bf:24:cb/00:00:01:00:00/40 tag 1 cdb 0x0 data 86016 out
> > [  970.423021]          res 40/00:08:bf:24:cb/00:00:01:00:00/40 Emask 0x10 (ATA bus error)
> > [  970.423031] ata1.00: cmd 61/08:10:97:41:c5/00:00:03:00:00/40 tag 2 cdb 0x0 data 4096 out
> > [  970.423034]          res 40/00:08:bf:24:cb/00:00:01:00:00/40 Emask 0x10 (ATA bus error)
> 
> The PHY is crapping itself.  The port headers may be damaged on the 
> drive or motherboard, or (most likely) you need a new cable.  SATA 
> cables in particular are known to be lame.
> 
> Try different ports and cables.
> 
> You can also see what happens if you disable NCQ 
> (http://linux-ata.org/faq.html#ncq).  Though given the interface errors, 
> if disabling NCQ solves problems, it /may/ just be that you slowed 
> things down enough to work, not that the drive firmware is bad.
>

Switched ports and cables and get these errors (looks the same):

[ 1903.410837] ata3.00: exception Emask 0x10 SAct 0x2 SErr 0x400100 action 0x2 frozen
[ 1903.410848] ata3.00: (irq_stat 0x08000000, interface fatal error)
[ 1903.410861] ata3.00: cmd 61/a0:08:e7:40:f3/03:00:03:00:00/40 tag 1 cdb 0x0 data 475136 out
[ 1903.410863]          res 40/00:08:e7:40:f3/00:00:03:00:00/40 Emask 0x10 (ATA bus error)
[ 1903.713203] ata3: soft resetting port
[ 1904.212843] ata3: softreset failed (1st FIS failed)
[ 1904.212851] ata3: softreset failed, retrying in 5 secs
[ 1909.210271] ata3: hard resetting port
[ 1916.702946] ata3: port is slow to respond, please be patient (Status 0x80)
[ 1939.687476] ata3: port failed to respond (30 secs, Status 0x80)
[ 1939.687483] ata3: COMRESET failed (device not ready)
[ 1939.687490] ata3: hardreset failed, retrying in 5 secs
[ 1944.684903] ata3: hard resetting port
[ 1945.140596] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 1945.155581] ata3.00: configured for UDMA/133
[ 1945.155596] ata3: EH complete
[ 1945.155794] SCSI device sda: 145226112 512-byte hdwr sectors (74356 MB)
[ 1945.155989] sda: Write Protect is off
[ 1945.155995] sda: Mode Sense: 00 3a 00 00
[ 1945.156231] SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 2020.315838] ata3.00: qc timeout (cmd 0x2f)
[ 2020.315847] ata3: failed to read log page 10h (errno=-5)
[ 2020.315859] ata3.00: exception Emask 0x1 SAct 0xf SErr 0x0 action 0x2 frozen
[ 2020.315863] ata3.00: (irq_stat 0x40000008)
[ 2020.315873] ata3.00: cmd 61/00:00:5f:7a:f3/02:00:03:00:00/40 tag 0 cdb 0x0 data 262144 out
[ 2020.315878]          res 40/00:08:5f:7e:f3/00:00:03:00:00/40 Emask 0x1 (device error)
[ 2020.315891] ata3.00: cmd 61/e0:08:5f:7e:f3/01:00:03:00:00/40 tag 1 cdb 0x0 data 245760 out
[ 2020.315896]          res 40/00:08:5f:7e:f3/00:00:03:00:00/40 Emask 0x1 (device error)
[ 2020.315908] ata3.00: cmd 61/80:10:3f:83:f3/00:00:03:00:00/40 tag 2 cdb 0x0 data 65536 out
[ 2020.315913]          res 40/00:08:5f:7e:f3/00:00:03:00:00/40 Emask 0x1 (device error)
[ 2020.315925] ata3.00: cmd 61/00:18:c7:83:f3/04:00:03:00:00/40 tag 3 cdb 0x0 data 524288 out
[ 2020.315930]          res 40/00:08:5f:7e:f3/00:00:03:00:00/40 Emask 0x1 (device error)
[ 2020.618605] ata3: soft resetting port
[ 2020.773508] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 2020.788490] ata3.00: configured for UDMA/133
[ 2020.788502] ata3: EH pending after completion, repeating EH (cnt=4)
[ 2020.788513] ata3: exception Emask 0x1 SAct 0x0 SErr 0x0 action 0x1
[ 2020.788519] ata3: (irq_stat 0x40000001)
[ 2020.804222] ata3.00: configured for UDMA/133
[ 2020.804240] ata3: EH complete
[ 2020.804453] SCSI device sda: 145226112 512-byte hdwr sectors (74356 MB)
[ 2020.804657] sda: Write Protect is off
[ 2020.804663] sda: Mode Sense: 00 3a 00 00
[ 2020.804870] SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 2020.805107] SCSI device sda: 145226112 512-byte hdwr sectors (74356 MB)
[ 2020.805276] sda: Write Protect is off
[ 2020.805281] sda: Mode Sense: 00 3a 00 00
[ 2020.805494] SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 2025.458771] ata3.00: exception Emask 0x10 SAct 0xc SErr 0x400100 action 0x2 frozen
[ 2025.458781] ata3.00: (irq_stat 0x08000000, interface fatal error)
[ 2025.458793] ata3.00: cmd 61/00:10:c7:f2:f3/04:00:03:00:00/40 tag 2 cdb 0x0 data 524288 out
[ 2025.458796]          res 40/00:18:c7:f6:f3/00:00:03:00:00/40 Emask 0x10 (ATA bus error)
[ 2025.458809] ata3.00: cmd 61/00:18:c7:f6:f3/04:00:03:00:00/40 tag 3 cdb 0x0 data 524288 out
[ 2025.458814]          res 40/00:18:c7:f6:f3/00:00:03:00:00/40 Emask 0x10 (ATA bus error)
[ 2025.760930] ata3: soft resetting port
[ 2026.260583] ata3: softreset failed (1st FIS failed)
[ 2026.260592] ata3: softreset failed, retrying in 5 secs
[ 2031.258000] ata3: hard resetting port
[ 2038.749670] ata3: port is slow to respond, please be patient (Status 0x80)
[ 2061.734216] ata3: port failed to respond (30 secs, Status 0x80)
[ 2061.734223] ata3: COMRESET failed (device not ready)
[ 2061.734229] ata3: hardreset failed, retrying in 5 secs
[ 2066.731632] ata3: hard resetting port
[ 2067.187333] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 2067.202311] ata3.00: configured for UDMA/133
[ 2067.202327] ata3: EH complete
[ 2067.202528] SCSI device sda: 145226112 512-byte hdwr sectors (74356 MB)
[ 2067.202720] sda: Write Protect is off
[ 2067.202726] sda: Mode Sense: 00 3a 00 00
[ 2067.202931] SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Errors with AHCI and 10K Raptor drive
  2007-03-19 15:01 ` Jeff Garzik
  2007-03-19 16:31   ` Stephen Hemminger
@ 2007-03-19 20:16   ` Stephen Hemminger
  2007-03-19 20:46     ` Jeff Garzik
  1 sibling, 1 reply; 6+ messages in thread
From: Stephen Hemminger @ 2007-03-19 20:16 UTC (permalink / raw)
  To: Jeff Garzik; +Cc: linux-ide

On Mon, 19 Mar 2007 11:01:37 -0400
Jeff Garzik <jgarzik@pobox.com> wrote:

> Stephen Hemminger wrote:
> > This is a new drive, so I suspect some driver incompatibility between the
> > driver (AHCI) and the hard drive (WD Raptor 10K 74G).
> 
> Driver incompatibilities between the driver (LLDD or libata-core) and a 
> hard drive are extremely rare.
> 
> The most common problem on modern SATA drives is drive firmware bugs, at 
> the moment.
> 

I moved the drive to another machine with ICH7 and it seems to work fine
there. Strange?


-- 
Stephen Hemminger <shemminger@linux-foundation.org>

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Errors with AHCI and 10K Raptor drive
  2007-03-19 20:16   ` Stephen Hemminger
@ 2007-03-19 20:46     ` Jeff Garzik
  2007-03-19 21:17       ` Stephen Hemminger
  0 siblings, 1 reply; 6+ messages in thread
From: Jeff Garzik @ 2007-03-19 20:46 UTC (permalink / raw)
  To: Stephen Hemminger; +Cc: linux-ide

Stephen Hemminger wrote:
> On Mon, 19 Mar 2007 11:01:37 -0400
> Jeff Garzik <jgarzik@pobox.com> wrote:
> 
>> Stephen Hemminger wrote:
>>> This is a new drive, so I suspect some driver incompatibility between the
>>> driver (AHCI) and the hard drive (WD Raptor 10K 74G).
>> Driver incompatibilities between the driver (LLDD or libata-core) and a 
>> hard drive are extremely rare.
>>
>> The most common problem on modern SATA drives is drive firmware bugs, at 
>> the moment.
>>
> 
> I moved the drive to another machine with ICH7 and it seems to work fine
> there. Strange?

Does dmesg reflect any difference in AHCI version or PHY speed, on 
either machine?  Did you use the same cables in both tests?

AHCI version ("0001.0100" == AHCI 1.1):
...
ahci 0000:00:1f.2: AHCI 0001.0100 32 slots 4 ports 3 Gbps 0xf impl SATA mode
...

PHY configuration and speed:
...
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
...

SATA headers (ports) on the motherboard and SATA cables are known to be 
weak links in the chain, commonly.

Regards,

	Jeff



^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Errors with AHCI and 10K Raptor drive
  2007-03-19 20:46     ` Jeff Garzik
@ 2007-03-19 21:17       ` Stephen Hemminger
  0 siblings, 0 replies; 6+ messages in thread
From: Stephen Hemminger @ 2007-03-19 21:17 UTC (permalink / raw)
  To: Jeff Garzik; +Cc: linux-ide

On Mon, 19 Mar 2007 16:46:40 -0400
Jeff Garzik <jeff@garzik.org> wrote:

> Stephen Hemminger wrote:
> > On Mon, 19 Mar 2007 11:01:37 -0400
> > Jeff Garzik <jgarzik@pobox.com> wrote:
> > 
> >> Stephen Hemminger wrote:
> >>> This is a new drive, so I suspect some driver incompatibility between the
> >>> driver (AHCI) and the hard drive (WD Raptor 10K 74G).
> >> Driver incompatibilities between the driver (LLDD or libata-core) and a 
> >> hard drive are extremely rare.
> >>
> >> The most common problem on modern SATA drives is drive firmware bugs, at 
> >> the moment.
> >>
> > 
> > I moved the drive to another machine with ICH7 and it seems to work fine
> > there. Strange?
> 
> Does dmesg reflect any difference in AHCI version or PHY speed, on 
> either machine?  Did you use the same cables in both tests?
> 
> AHCI version ("0001.0100" == AHCI 1.1):
> ...
> ahci 0000:00:1f.2: AHCI 0001.0100 32 slots 4 ports 3 Gbps 0xf impl SATA mode
> ...

On the good machine:

[   30.728849] ata1: SATA max UDMA/133 cmd 0x000000000001e400 ctl 0x000000000001e082 bmdma 0x000000000001d880 irq 23
[   30.890918] ata1.00: ATA-7: WDC WD740ADFD-00NLR1, 20.07P20, max UDMA/133
[   30.890966] ata1.00: 145226112 sectors, multi 16: LBA48 NCQ (depth 0/32)
[   30.900957] ata1.00: configured for UDMA/133

Maybe since AHCI isn't enabled in the BIOS on the good machine,
we aren't doing NCQ?

> PHY configuration and speed:
> ...
> ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ...
> 
> SATA headers (ports) on the motherboard and SATA cables are known to be 
> weak links in the chain, commonly.

I tried a port and cable swap on the bad machine. The good machine
had a new cable, so it still could be the cable.


-- 
Stephen Hemminger <shemminger@linux-foundation.org>

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2007-03-19 21:17 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-03-19 14:53 Errors with AHCI and 10K Raptor drive Stephen Hemminger
2007-03-19 15:01 ` Jeff Garzik
2007-03-19 16:31   ` Stephen Hemminger
2007-03-19 20:16   ` Stephen Hemminger
2007-03-19 20:46     ` Jeff Garzik
2007-03-19 21:17       ` Stephen Hemminger

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.