Skip to contentSkip to conversation

libata interface fatal error

DISCUSSION Florian Effenberger 3 participants 26 messages May 26, 2007 – Jun 25, 2007 libata

lore
Share & tools
lore
#0 lore raw

Hi,

it seems that the speed is never lowered, I always see "SATA link up 3.0 Gbps (SStatus 123 SControl 300)".

Can I manually lower the speed via a kernel parameter?

Thanks
Florian

#1 lore raw
Quoted 6 lines · Florian Effenberger

Hi,

it seems that the speed is never lowered, I always see "SATA link up 3.0 Gbps (SStatus 123 SControl 300)".

Can I manually lower the speed via a kernel parameter?

Currently, there is no mechanism to do that but hard drives usually have dip switch to force 1.5Gbps. Please try that. If your harddrive doesn't have that, please lemme know. I'll prepare a simple patch.

Thanks.

Signature · 1 line
tejun
#2 lore raw

Hi Tejun,

Quoted 3 lines

Currently, there is no mechanism to do that but hard drives usually have dip switch to force 1.5Gbps. Please try that. If your harddrive doesn't have that, please lemme know. I'll prepare a simple patch.

thanks a lot, I will try that out and tell you the results. :-)

Florian

#3 lore raw
In reply to Tejun Heo

Hi,

Quoted 3 lines

Currently, there is no mechanism to do that but hard drives usually have dip switch to force 1.5Gbps. Please try that. If your harddrive doesn't have that, please lemme know. I'll prepare a simple patch.

unfortunately, the disks have a jumper board, but the jumpers are missing... could you write a patch for me? Would be much appreciated!

Thanks a lot!
Florian

#4 lore raw
Quoted 8 lines · Florian Effenberger

Hi,

Quoted 3 lines

Currently, there is no mechanism to do that but hard drives usually have dip switch to force 1.5Gbps. Please try that. If your harddrive doesn't have that, please lemme know. I'll prepare a simple patch.

unfortunately, the disks have a jumper board, but the jumpers are missing... could you write a patch for me? Would be much appreciated!

Okay, there was a bug in link speed limit logic. That's probably why speed down to 1.5Gbps didn't kick in. The attached patch contains the fix and hack to force 1.5Gbps. Please give it a shot.

Thanks.

Signature · 1 line
tejun
drivers/ata/ahci.c +16 -2
index 7baeaff..f9550f1 100644
@@ -219,6 +219,7 @@ static int ahci_init_one (struct pci_dev *pdev, const struct pci_device_id *ent)
 static unsigned int ahci_qc_issue(struct ata_queued_cmd *qc);
 static void ahci_irq_clear(struct ata_port *ap);
 static int ahci_port_start(struct ata_port *ap);
+static int ahci_vt8251_port_start(struct ata_port *ap);
 static void ahci_port_stop(struct ata_port *ap);
 static void ahci_tf_read(struct ata_port *ap, struct ata_taskfile *tf);
 static void ahci_qc_prep(struct ata_queued_cmd *qc);
@@ -284,7 +285,7 @@ static const struct ata_port_operations ahci_ops = {
 	.port_resume		= ahci_port_resume,
 #endif
 
-	.port_start		= ahci_port_start,
+	.port_start		= ahci_vt8251_port_start,
 	.port_stop		= ahci_port_stop,
 };
 
@@ -318,7 +319,7 @@ static const struct ata_port_operations ahci_vt8251_ops = {
 	.port_resume		= ahci_port_resume,
 #endif
 
-	.port_start		= ahci_port_start,
+	.port_start		= ahci_vt8251_port_start,
 	.port_stop		= ahci_port_stop,
 };
 
@@ -1558,6 +1559,19 @@ static int ahci_port_start(struct ata_port *ap)
 	return 0;
 }
 
+static int ahci_vt8251_port_start(struct ata_port *ap)
+{
+	struct ahci_host_priv *hpriv = ap->host->private_data;
+
+	if (((hpriv->cap >> 20) & 0xf) != 1) {
+		printk("limiting SATA link speed to 1.5Gbps\n");
+		ap->hw_sata_spd_limit = 1;
+		ap->eh_info.action |= ATA_EH_HARDRESET;
+	}
+
+	return ahci_port_start(ap);
+}
+
 static void ahci_port_stop(struct ata_port *ap)
 {
 	const char *emsg = NULL;
drivers/ata/libata-core.c +2 -1
index 4733f00..57940ba 100644
@@ -6313,7 +6313,8 @@ int ata_host_register(struct ata_host *host, struct scsi_host_template *sht)
 		/* init sata_spd_limit to the current value */
 		if (sata_scr_read(ap, SCR_CONTROL, &scontrol) == 0) {
 			int spd = (scontrol >> 4) & 0xf;
-			ap->hw_sata_spd_limit &= (1 << spd) - 1;
+			if (spd)
+				ap->hw_sata_spd_limit &= (1 << spd) - 1;
 		}
 		ap->sata_spd_limit = ap->hw_sata_spd_limit;
 
#5 lore raw

Hi Tejun,

Quoted 3 lines

Okay, there was a bug in link speed limit logic. That's probably why speed down to 1.5Gbps didn't kick in. The attached patch contains the fix and hack to force 1.5Gbps. Please give it a shot.

thanks a lot for your help, much appreciated! Will test it and let you know if it works.

Florian

#6 lore raw
In reply to Tejun Heo

Hi Tejun,

Quoted 3 lines

Okay, there was a bug in link speed limit logic. That's probably why speed down to 1.5Gbps didn't kick in. The attached patch contains the fix and hack to force 1.5Gbps. Please give it a shot.

thanks a lot for your patch, it seems to work, at least better than without patch. :-)

When rsyncing about 12 GB, no trouble occured. When doing heavy stress tests, I receive errors again, but okay, maybe that's due to a hardware bug.

Will your patch go into the vanilla kernel?

Florian

#7 lore raw
Quoted 6 lines · Florian Effenberger

Hi Tejun,

Quoted 3 lines

Okay, there was a bug in link speed limit logic. That's probably why speed down to 1.5Gbps didn't kick in. The attached patch contains the fix and hack to force 1.5Gbps. Please give it a shot.

Quoted 8 lines

thanks a lot for your patch, it seems to work, at least better than without patch. :-)

When rsyncing about 12 GB, no trouble occured. When doing heavy stress tests, I receive errors again, but okay, maybe that's due to a hardware bug.

Will your patch go into the vanilla kernel?

I'm currently not sure what the root cause is

1. if the controller is at fault, we need to force 1.5Gbps on the controller.

2. if the drive model is broken, we need to blacklist the drives.

3. if your specific configuration is broken (faulty hw, PSU, bad karma), the upstream speed limit fix patch should be enough.

Can you post the result of 'hdparm -I /dev/sdX'?

Signature · 1 line
tejun
#8 lore raw

Hi,

Quoted 1 line

Can you post the result of 'hdparm -I /dev/sdX'?

thanks a lot for your kind support, that is much appreciated!

Attached is some machine output, hope that helps. Let me know I you need more information.

Florian

00:00.0 Host bridge: Intel Corporation P965/G965 Memory Controller Hub (rev 02) 00:01.0 PCI bridge: Intel Corporation P965/G965 PCI Express Root Port (rev 02) 00:1a.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI #4 (rev 02) 00:1a.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI #5 (rev 02) 00:1a.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI #2 (rev 02) 00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02) 00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 02) 00:1c.4 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 5 (rev 02) 00:1c.5 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 6 (rev 02) 00:1d.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI #1 (rev 02) 00:1d.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI #2 (rev 02) 00:1d.2 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI #3 (rev 02) 00:1d.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI #1 (rev 02) 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev f2)
00:1f.0 ISA bridge: Intel Corporation 82801HB/HR (ICH8/R) LPC Interface Controller (rev 02) 00:1f.2 SATA controller: Intel Corporation 82801HB (ICH8) SATA AHCI Controller (rev 02) 00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 02) 01:00.0 VGA compatible controller: nVidia Corporation Unknown device 016a (rev a1) 03:00.0 Ethernet controller: Marvell Technology Group Ltd. Unknown device 4364 (rev 12) 04:00.0 SATA controller: JMicron Technologies, Inc. JMicron 20360/20363 AHCI Controller (rev 02) 04:00.1 IDE interface: JMicron Technologies, Inc. JMicron 20360/20363 AHCI Controller (rev 02) 05:01.0 Ethernet controller: Intel Corporation 82557/8/9 [Ethernet Pro 100] (rev 0c) 05:06.0 FireWire (IEEE 1394): Texas Instruments TSB43AB23 IEEE-1394a-2000 Controller (PHY/Link)

/dev/md0:

        Version : 00.90.03
  Creation Time : Tue May  1 15:56:11 2007
     Raid Level : raid5
     Array Size : 937713408 (894.27 GiB 960.22 GB)
    Device Size : 312571136 (298.09 GiB 320.07 GB)

Raid Devices : 4
Total Devices : 4
Preferred Minor : 0
Persistence : Superblock is persistent

Update Time : Thu Jun 14 12:40:44 2007
State : clean
Active Devices : 4
Working Devices : 4
Failed Devices : 0
Spare Devices : 0

Layout : left-symmetric
Chunk Size : 64K

UUID : 6e3c156d:c91eb028:40daae21:698c531b
Events : 0.62

Number Major Minor RaidDevice State
0 8 16 0 active sync /dev/sdb
1 8 32 1 active sync /dev/sdc
2 8 48 2 active sync /dev/sdd
3 8 64 3 active sync /dev/sde

/dev/sda:

ATA device, with non-removable media

        Model Number:       WDC WD1600YS-01SHB1
        Serial Number:      WD-WCAP01819659
        Firmware Revision:  20.06C06

Standards:
Supported: 7 6 5 4
Likely used: 7
Configuration:

        Logical         max     current
        cylinders       16383   16383
        heads           16      16
        sectors/track   63      63
        --
        CHS current addressable sectors:   16514064
        LBA    user addressable sectors:  268435455
        LBA48  user addressable sectors:  321670847
        device size with M = 1024*1024:      157065 MBytes
        device size with M = 1000*1000:      164695 MBytes (164 GB)

Capabilities:
LBA, IORDY(can be disabled)
Queue depth: 32
Standby timer values: spec'd by Standard, with device specific minimum R/W multiple sector transfer: Max = 16 Current = 0 Recommended acoustic management value: 128, current value: 254
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6
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
Power-Up In Standby feature set
* SET_FEATURES required to spinup after power up
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
* WRITE_{DMA|MULTIPLE}_FUA_EXT
* 64-bit World wide name
* 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
* 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)
unknown 206[12]
Security:
Master password revision code = 65534
supported
not enabled
not locked
not frozen
not expired: security count
not supported: enhanced erase
52min for SECURITY ERASE UNIT.
Checksum: correct

/dev/sdb:

ATA device, with non-removable media

        Model Number:       WDC WD3200YS-01PGB0
        Serial Number:      WD-WCAPD3405080
        Firmware Revision:  21.00M21

Standards:
Supported: 7 6 5 4
Likely used: 7
Configuration:

        Logical         max     current
        cylinders       16383   16383
        heads           16      16
        sectors/track   63      63
        --
        CHS current addressable sectors:   16514064
        LBA    user addressable sectors:  268435455
        LBA48  user addressable sectors:  625142448
        device size with M = 1024*1024:      305245 MBytes
        device size with M = 1000*1000:      320072 MBytes (320 GB)

Capabilities:
LBA, IORDY(can be disabled)
Queue depth: 1
Standby timer values: spec'd by Standard, with device specific minimum R/W multiple sector transfer: Max = 16 Current = 0 Recommended acoustic management value: 128, current value: 254
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6
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
Power-Up In Standby feature set
* SET_FEATURES required to spinup after power up
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
* 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)
unknown 206[12]
Security:
Master password revision code = 65534
supported
not enabled
not locked
not frozen
not expired: security count
not supported: enhanced erase
Checksum: correct

/dev/sdc:

ATA device, with non-removable media

        Model Number:       WDC WD3200YS-01PGB0
        Serial Number:      WD-WCAPD4087913
        Firmware Revision:  21.00M21

Standards:
Supported: 7 6 5 4
Likely used: 7
Configuration:

        Logical         max     current
        cylinders       16383   16383
        heads           16      16
        sectors/track   63      63
        --
        CHS current addressable sectors:   16514064
        LBA    user addressable sectors:  268435455
        LBA48  user addressable sectors:  625142448
        device size with M = 1024*1024:      305245 MBytes
        device size with M = 1000*1000:      320072 MBytes (320 GB)

Capabilities:
LBA, IORDY(can be disabled)
Queue depth: 1
Standby timer values: spec'd by Standard, with device specific minimum R/W multiple sector transfer: Max = 16 Current = 0 Recommended acoustic management value: 128, current value: 254
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6
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
Power-Up In Standby feature set
* SET_FEATURES required to spinup after power up
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
* 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)
unknown 206[12]
Security:
Master password revision code = 65534
supported
not enabled
not locked
not frozen
not expired: security count
not supported: enhanced erase
Checksum: correct

/dev/sdd:

ATA device, with non-removable media

        Model Number:       WDC WD3200YS-01PGB0
        Serial Number:      WD-WCAPD4124047
        Firmware Revision:  21.00M21

Standards:
Supported: 7 6 5 4
Likely used: 7
Configuration:

        Logical         max     current
        cylinders       16383   16383
        heads           16      16
        sectors/track   63      63
        --
        CHS current addressable sectors:   16514064
        LBA    user addressable sectors:  268435455
        LBA48  user addressable sectors:  625142448
        device size with M = 1024*1024:      305245 MBytes
        device size with M = 1000*1000:      320072 MBytes (320 GB)

Capabilities:
LBA, IORDY(can be disabled)
Queue depth: 1
Standby timer values: spec'd by Standard, with device specific minimum R/W multiple sector transfer: Max = 16 Current = 0 Recommended acoustic management value: 128, current value: 254
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6
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
Power-Up In Standby feature set
* SET_FEATURES required to spinup after power up
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
* 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)
unknown 206[12]
Security:
Master password revision code = 65534
supported
not enabled
not locked
not frozen
not expired: security count
not supported: enhanced erase
Checksum: correct

/dev/sde:

ATA device, with non-removable media

        Model Number:       WDC WD3200YS-01PGB0
        Serial Number:      WD-WCAPD3406202
        Firmware Revision:  21.00M21

Standards:
Supported: 7 6 5 4
Likely used: 7
Configuration:

        Logical         max     current
        cylinders       16383   16383
        heads           16      16
        sectors/track   63      63
        --
        CHS current addressable sectors:   16514064
        LBA    user addressable sectors:  268435455
        LBA48  user addressable sectors:  625142448
        device size with M = 1024*1024:      305245 MBytes
        device size with M = 1000*1000:      320072 MBytes (320 GB)

Capabilities:
LBA, IORDY(can be disabled)
Queue depth: 1
Standby timer values: spec'd by Standard, with device specific minimum R/W multiple sector transfer: Max = 16 Current = 0 Recommended acoustic management value: 128, current value: 254
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6
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
Power-Up In Standby feature set
* SET_FEATURES required to spinup after power up
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
* 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)
unknown 206[12]
Security:
Master password revision code = 65534
supported
not enabled
not locked
not frozen
not expired: security count
not supported: enhanced erase
Checksum: correct

#9 lore raw
Quoted 8 lines · Florian Effenberger

Hi,

Quoted 1 line

Can you post the result of 'hdparm -I /dev/sdX'?

thanks a lot for your kind support, that is much appreciated!

Attached is some machine output, hope that helps. Let me know I you need more information.

Okay, ich8. I don't think the chipset is at fault here and you have a lot of disks. My primary suspect is power supply problem but things like this are hard to prove. With the merged speed down fix, libata will do the right thing after a few errors, so ignoring the problem wouldn't be a too bad idea. If you're curious, you can try to connect drives to different SATA ports and power lanes and see whether errors follow the disk, port or power lane.

Signature · 1 line
tejun
#10 lore raw

Hi Tejun,

Quoted 7 lines

Okay, ich8. I don't think the chipset is at fault here and you have a lot of disks. My primary suspect is power supply problem but things like this are hard to prove. With the merged speed down fix, libata will do the right thing after a few errors, so ignoring the problem wouldn't be a too bad idea. If you're curious, you can try to connect drives to different SATA ports and power lanes and see whether errors follow the disk, port or power lane.

exactly, should be four disks in the machine.

What power supply would you recommend for this type of disks? I think we got a 450W Enermax, IIRC.

What do you mean by "merged speed down fix"? Is your fix for the speed down logic implemented in the current kernel, so I don't have to patch anymore (except when I want to force 1.5Gbps right from the beginning)?

All SATA parts are used, so reconnecting is not an option. But I can try to switch the power supply (lanes).

Thanks for all your kind help, that is much appreciated! Florian

#11 lore raw

Hello,

Quoted 2 lines · Florian Effenberger

What power supply would you recommend for this type of disks? I think we got a 450W Enermax, IIRC.

Most power supplies should be able to do 4 disks without any problem unless it's broken.

Quoted 3 lines

What do you mean by "merged speed down fix"? Is your fix for the speed down logic implemented in the current kernel, so I don't have to patch anymore (except when I want to force 1.5Gbps right from the beginning)?

Yeap, kernel will automatically downgrade to 1.5Gbps after several failures.

Signature · 1 line
tejun
#12 lore raw

Hi Tejun,

I've been trying to find a solution for a long time for quite a similar libata errror messages as shown in this thread. Perhaps you might get have some ideas what the actual originator might be:

With the latest 2.6.22-rc4-git4 kernel I still get the following error messages
with high I/O load:

sd 2:0:0:0: [sdc] 976773168 512-byte hardware sectors (500108 MB) sd 2:0:0:0: [sdc] Write Protect is off
sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00
sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 ata3.00: (port_status 0x20080000)
ata3.00: cmd c8/00:08:af:91:49/00:00:00:00:00/e5 tag 0 cdb 0x0 data 4096 in

         res 50/00:00:b6:91:49/00:00:11:00:00/e5 Emask 0x2 (HSM violation)

ata3: soft resetting port
ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata3.00: ata_hpa_resize 1: sectors = 976773168, hpa_sectors = 976773168 ata3.00: ata_hpa_resize 1: sectors = 976773168, hpa_sectors = 976773168 ata3.00: configured for UDMA/133
ata3: EH complete

... and later in the chain ...

sd 2:0:0:0: [sdc] 976773168 512-byte hardware sectors (500108 MB) sd 2:0:0:0: [sdc] Write Protect is off
sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00
sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 ata3.00: (port_status 0x20080000)
ata3.00: cmd c8/00:08:67:74:65/00:00:00:00:00/ec tag 0 cdb 0x0 data 4096 in

         res 50/00:00:6e:74:65/00:00:1b:00:00/ec Emask 0x2 (HSM violation)

ata3: soft resetting port
ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310) ata3.00: ata_hpa_resize 1: sectors = 976773168, hpa_sectors = 976773168 ata3.00: ata_hpa_resize 1: sectors = 976773168, hpa_sectors = 976773168 ata3.00: configured for UDMA/100
ata3: EH complete

--- This goes on until UDMA/33 has been reched

The problematic hardware combination is:

00:00.0 Host bridge: VIA Technologies, Inc. KT880 Host Bridge (rev 80) 00:00.1 Host bridge: VIA Technologies, Inc. KT880 Host Bridge 00:00.2 Host bridge: VIA Technologies, Inc. KT880 Host Bridge 00:00.3 Host bridge: VIA Technologies, Inc. KT880 Host Bridge 00:00.4 Host bridge: VIA Technologies, Inc. KT880 Host Bridge 00:00.7 Host bridge: VIA Technologies, Inc. KT880 Host Bridge 00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI Bridge 00:09.0 Ethernet controller: Marvell Technology Group Ltd. 88E8001 Gigabit Ethernet Controller (rev 13)
00:0a.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
00:0d.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
00:0e.0 Mass storage controller: Promise Technology, Inc. PDC40718 (SATA 300 TX4) (rev 02)
00:0f.0 RAID bus controller: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller (rev 80)
00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) 00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86) 00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge [KT600/K8T800/K8T890 South]
00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 60)
00:11.6 Communication controller: VIA Technologies, Inc. AC'97 Modem Controller (rev 80)
01:00.0 VGA compatible controller: nVidia Corporation NV36.2 [GeForce FX 5700] (rev a1)

and the problems relate only to Seagate 7200.10 SATA-disks, never with the older 7200.7 SATA-disks alll connected to Promise Sata 300TX4-controller.

Because this problem has been around for as long as I've had the Promise Sata300TX4 controller an additional new problem is that after kernel version 2.6.21-rc3-git10 the libata error handling/interface speed downgrade has been fixed ---> these new seagate disks get downgraded from UDMA/133 to UDMA/33 overnight (can the speed downgrade be disabled as a quick and dirty fix in this case somehow ?). For some reason the above mentioned libata error messages don't really do any noticeable harm but it would be very nice to be able to prevent the interface speed downgrade for now.

Quoted 6 lines
Quoted 3 lines

What do you mean by "merged speed down fix"? Is your fix for the speed down logic implemented in the current kernel, so I don't have to patch anymore (except when I want to force 1.5Gbps right from the beginning)?

Yeap, kernel will automatically downgrade to 1.5Gbps after several failures.

Yes, this feature seems to work quite nicely as the included logs show.

Regards,
Tomi Orava

PS. These problems are not special to this single machine as a friend at work
has the same Promise Sata300TX4 card with exactly the same Seagate
7200.10
SATA-disks on an intel-based P4 machine with similar problems under
I/O-load.

---------------------------------------------------------
scsi0 : sata_promise
scsi1 : sata_promise
scsi2 : sata_promise
scsi3 : sata_promise
ata1: SATA max UDMA/133 cmd 0xf880a380 ctl 0xf880a3b8 bmdma 0x00000000 irq 0
ata2: SATA max UDMA/133 cmd 0xf880a280 ctl 0xf880a2b8 bmdma 0x00000000 irq 0
ata3: SATA max UDMA/133 cmd 0xf880a200 ctl 0xf880a238 bmdma 0x00000000 irq 0
ata4: SATA max UDMA/133 cmd 0xf880a300 ctl 0xf880a338 bmdma 0x00000000 irq 0 Switched to high resolution mode on CPU 0
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata1.00: ata_hpa_resize 1: sectors = 390721968, hpa_sectors = 390721968 ata1.00: ATA-6: ST3200822AS, 3.01, max UDMA/133
ata1.00: 390721968 sectors, multi 0: LBA48
ata1.00: ata_hpa_resize 1: sectors = 390721968, hpa_sectors = 390721968 ata1.00: configured for UDMA/133
ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata2.00: ata_hpa_resize 1: sectors = 390721968, hpa_sectors = 390721968 ata2.00: ATA-6: ST3200822AS, 3.01, max UDMA/133
ata2.00: 390721968 sectors, multi 0: LBA48
ata2.00: ata_hpa_resize 1: sectors = 390721968, hpa_sectors = 390721968 ata2.00: configured for UDMA/133
ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata3.00: ata_hpa_resize 1: sectors = 976773168, hpa_sectors = 976773168 ata3.00: ATA-7: ST3500630AS, 3.AAK, max UDMA/133
ata3.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 0/32) ata3.00: ata_hpa_resize 1: sectors = 976773168, hpa_sectors = 976773168 ata3.00: configured for UDMA/133
ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata4.00: ata_hpa_resize 1: sectors = 976773168, hpa_sectors = 976773168 ata4.00: ATA-7: ST3500630AS, 3.AAK, max UDMA/133
ata4.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 0/32) ata4.00: ata_hpa_resize 1: sectors = 976773168, hpa_sectors = 976773168 ata4.00: configured for UDMA/133
scsi 0:0:0:0: Direct-Access ATA ST3200822AS 3.01 PQ: 0 ANSI: 5
sd 0:0:0:0: [sda] 390721968 512-byte hardware sectors (200050 MB) sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 0:0:0:0: [sda] 390721968 512-byte hardware sectors (200050 MB) sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sda: sda1 sda2
sd 0:0:0:0: [sda] Attached SCSI disk
sd 0:0:0:0: Attached scsi generic sg0 type 0
scsi 1:0:0:0: Direct-Access ATA ST3200822AS 3.01 PQ: 0 ANSI: 5
sd 1:0:0:0: [sdb] 390721968 512-byte hardware sectors (200050 MB) sd 1:0:0:0: [sdb] Write Protect is off
sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 1:0:0:0: [sdb] 390721968 512-byte hardware sectors (200050 MB) sd 1:0:0:0: [sdb] Write Protect is off
sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdb: sdb1 sdb2
sd 1:0:0:0: [sdb] Attached SCSI disk
sd 1:0:0:0: Attached scsi generic sg1 type 0
scsi 2:0:0:0: Direct-Access ATA ST3500630AS 3.AA PQ: 0 ANSI: 5
sd 2:0:0:0: [sdc] 976773168 512-byte hardware sectors (500108 MB) sd 2:0:0:0: [sdc] Write Protect is off
sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00
sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 2:0:0:0: [sdc] 976773168 512-byte hardware sectors (500108 MB) sd 2:0:0:0: [sdc] Write Protect is off
sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00
sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdc: sdc1 sdc2
sd 2:0:0:0: [sdc] Attached SCSI disk
sd 2:0:0:0: Attached scsi generic sg2 type 0
scsi 3:0:0:0: Direct-Access ATA ST3500630AS 3.AA PQ: 0 ANSI: 5
sd 3:0:0:0: [sdd] 976773168 512-byte hardware sectors (500108 MB) sd 3:0:0:0: [sdd] Write Protect is off
sd 3:0:0:0: [sdd] Mode Sense: 00 3a 00 00
sd 3:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 3:0:0:0: [sdd] 976773168 512-byte hardware sectors (500108 MB) sd 3:0:0:0: [sdd] Write Protect is off
sd 3:0:0:0: [sdd] Mode Sense: 00 3a 00 00
sd 3:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdd: sdd1 sdd2
sd 3:0:0:0: [sdd] Attached SCSI disk
sd 3:0:0:0: Attached scsi generic sg3 type 0

#13 lore raw

Hello,

Yeah, it seems promise has some problem with 3G link. Cc'ing Mikael Pettersson and quoting whole body for him. Mikael, does this look familiar?

Quoted 206 lines · Tomi Orava

Hi Tejun,

I've been trying to find a solution for a long time for quite a similar libata errror messages as shown in this thread. Perhaps you might get have some ideas what the actual originator might be:

With the latest 2.6.22-rc4-git4 kernel I still get the following error messages
with high I/O load:

sd 2:0:0:0: [sdc] 976773168 512-byte hardware sectors (500108 MB) sd 2:0:0:0: [sdc] Write Protect is off
sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00
sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 ata3.00: (port_status 0x20080000)
ata3.00: cmd c8/00:08:af:91:49/00:00:00:00:00/e5 tag 0 cdb 0x0 data 4096 in

         res 50/00:00:b6:91:49/00:00:11:00:00/e5 Emask 0x2 (HSM violation)

ata3: soft resetting port
ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata3.00: ata_hpa_resize 1: sectors = 976773168, hpa_sectors = 976773168 ata3.00: ata_hpa_resize 1: sectors = 976773168, hpa_sectors = 976773168 ata3.00: configured for UDMA/133
ata3: EH complete

... and later in the chain ...

sd 2:0:0:0: [sdc] 976773168 512-byte hardware sectors (500108 MB) sd 2:0:0:0: [sdc] Write Protect is off
sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00
sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 ata3.00: (port_status 0x20080000)
ata3.00: cmd c8/00:08:67:74:65/00:00:00:00:00/ec tag 0 cdb 0x0 data 4096 in

         res 50/00:00:6e:74:65/00:00:1b:00:00/ec Emask 0x2 (HSM violation)

ata3: soft resetting port
ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310) ata3.00: ata_hpa_resize 1: sectors = 976773168, hpa_sectors = 976773168 ata3.00: ata_hpa_resize 1: sectors = 976773168, hpa_sectors = 976773168 ata3.00: configured for UDMA/100
ata3: EH complete

--- This goes on until UDMA/33 has been reched

The problematic hardware combination is:

00:00.0 Host bridge: VIA Technologies, Inc. KT880 Host Bridge (rev 80) 00:00.1 Host bridge: VIA Technologies, Inc. KT880 Host Bridge 00:00.2 Host bridge: VIA Technologies, Inc. KT880 Host Bridge 00:00.3 Host bridge: VIA Technologies, Inc. KT880 Host Bridge 00:00.4 Host bridge: VIA Technologies, Inc. KT880 Host Bridge 00:00.7 Host bridge: VIA Technologies, Inc. KT880 Host Bridge 00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI Bridge 00:09.0 Ethernet controller: Marvell Technology Group Ltd. 88E8001 Gigabit Ethernet Controller (rev 13)
00:0a.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
00:0d.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
00:0e.0 Mass storage controller: Promise Technology, Inc. PDC40718 (SATA 300 TX4) (rev 02)
00:0f.0 RAID bus controller: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller (rev 80)
00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) 00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86) 00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge [KT600/K8T800/K8T890 South]
00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 60)
00:11.6 Communication controller: VIA Technologies, Inc. AC'97 Modem Controller (rev 80)
01:00.0 VGA compatible controller: nVidia Corporation NV36.2 [GeForce FX 5700] (rev a1)

and the problems relate only to Seagate 7200.10 SATA-disks, never with the older 7200.7 SATA-disks alll connected to Promise Sata 300TX4-controller.

Because this problem has been around for as long as I've had the Promise Sata300TX4 controller an additional new problem is that after kernel version 2.6.21-rc3-git10 the libata error handling/interface speed downgrade has been fixed ---> these new seagate disks get downgraded from UDMA/133 to UDMA/33 overnight (can the speed downgrade be disabled as a quick and dirty fix in this case somehow ?). For some reason the above mentioned libata error messages don't really do any noticeable harm but it would be very nice to be able to prevent the interface speed downgrade for now.

Quoted 5 lines
Quoted 3 lines

What do you mean by "merged speed down fix"? Is your fix for the speed down logic implemented in the current kernel, so I don't have to patch anymore (except when I want to force 1.5Gbps right from the beginning)?

Yeap, kernel will automatically downgrade to 1.5Gbps after several failures.

Yes, this feature seems to work quite nicely as the included logs show.

Regards,
Tomi Orava

PS. These problems are not special to this single machine as a friend at work
has the same Promise Sata300TX4 card with exactly the same Seagate
7200.10
SATA-disks on an intel-based P4 machine with similar problems under
I/O-load.

---------------------------------------------------------
scsi0 : sata_promise
scsi1 : sata_promise
scsi2 : sata_promise
scsi3 : sata_promise
ata1: SATA max UDMA/133 cmd 0xf880a380 ctl 0xf880a3b8 bmdma 0x00000000 irq 0
ata2: SATA max UDMA/133 cmd 0xf880a280 ctl 0xf880a2b8 bmdma 0x00000000 irq 0
ata3: SATA max UDMA/133 cmd 0xf880a200 ctl 0xf880a238 bmdma 0x00000000 irq 0
ata4: SATA max UDMA/133 cmd 0xf880a300 ctl 0xf880a338 bmdma 0x00000000 irq 0 Switched to high resolution mode on CPU 0
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata1.00: ata_hpa_resize 1: sectors = 390721968, hpa_sectors = 390721968 ata1.00: ATA-6: ST3200822AS, 3.01, max UDMA/133
ata1.00: 390721968 sectors, multi 0: LBA48
ata1.00: ata_hpa_resize 1: sectors = 390721968, hpa_sectors = 390721968 ata1.00: configured for UDMA/133
ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata2.00: ata_hpa_resize 1: sectors = 390721968, hpa_sectors = 390721968 ata2.00: ATA-6: ST3200822AS, 3.01, max UDMA/133
ata2.00: 390721968 sectors, multi 0: LBA48
ata2.00: ata_hpa_resize 1: sectors = 390721968, hpa_sectors = 390721968 ata2.00: configured for UDMA/133
ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata3.00: ata_hpa_resize 1: sectors = 976773168, hpa_sectors = 976773168 ata3.00: ATA-7: ST3500630AS, 3.AAK, max UDMA/133
ata3.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 0/32) ata3.00: ata_hpa_resize 1: sectors = 976773168, hpa_sectors = 976773168 ata3.00: configured for UDMA/133
ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata4.00: ata_hpa_resize 1: sectors = 976773168, hpa_sectors = 976773168 ata4.00: ATA-7: ST3500630AS, 3.AAK, max UDMA/133
ata4.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 0/32) ata4.00: ata_hpa_resize 1: sectors = 976773168, hpa_sectors = 976773168 ata4.00: configured for UDMA/133
scsi 0:0:0:0: Direct-Access ATA ST3200822AS 3.01 PQ: 0 ANSI: 5
sd 0:0:0:0: [sda] 390721968 512-byte hardware sectors (200050 MB) sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 0:0:0:0: [sda] 390721968 512-byte hardware sectors (200050 MB) sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sda: sda1 sda2
sd 0:0:0:0: [sda] Attached SCSI disk
sd 0:0:0:0: Attached scsi generic sg0 type 0
scsi 1:0:0:0: Direct-Access ATA ST3200822AS 3.01 PQ: 0 ANSI: 5
sd 1:0:0:0: [sdb] 390721968 512-byte hardware sectors (200050 MB) sd 1:0:0:0: [sdb] Write Protect is off
sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 1:0:0:0: [sdb] 390721968 512-byte hardware sectors (200050 MB) sd 1:0:0:0: [sdb] Write Protect is off
sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdb: sdb1 sdb2
sd 1:0:0:0: [sdb] Attached SCSI disk
sd 1:0:0:0: Attached scsi generic sg1 type 0
scsi 2:0:0:0: Direct-Access ATA ST3500630AS 3.AA PQ: 0 ANSI: 5
sd 2:0:0:0: [sdc] 976773168 512-byte hardware sectors (500108 MB) sd 2:0:0:0: [sdc] Write Protect is off
sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00
sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 2:0:0:0: [sdc] 976773168 512-byte hardware sectors (500108 MB) sd 2:0:0:0: [sdc] Write Protect is off
sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00
sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdc: sdc1 sdc2
sd 2:0:0:0: [sdc] Attached SCSI disk
sd 2:0:0:0: Attached scsi generic sg2 type 0
scsi 3:0:0:0: Direct-Access ATA ST3500630AS 3.AA PQ: 0 ANSI: 5
sd 3:0:0:0: [sdd] 976773168 512-byte hardware sectors (500108 MB) sd 3:0:0:0: [sdd] Write Protect is off
sd 3:0:0:0: [sdd] Mode Sense: 00 3a 00 00
sd 3:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 3:0:0:0: [sdd] 976773168 512-byte hardware sectors (500108 MB) sd 3:0:0:0: [sdd] Write Protect is off
sd 3:0:0:0: [sdd] Mode Sense: 00 3a 00 00
sd 3:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdd: sdd1 sdd2
sd 3:0:0:0: [sdd] Attached SCSI disk
sd 3:0:0:0: Attached scsi generic sg3 type 0

Signature · 1 line
tejun
#14 lore raw
In reply to Tejun Heo

Hi,

Quoted 1 line

Yeap, kernel will automatically downgrade to 1.5Gbps after several failures.

is there also a boot-time option to force 1.5Gbps right from booting up?

Florian

#15 lore raw
Quoted 6 lines · Florian Effenberger

Hi,

Quoted 2 lines

Yeap, kernel will automatically downgrade to 1.5Gbps after several failures.

is there also a boot-time option to force 1.5Gbps right from booting up?

Nope.

Signature · 1 line
tejun
#16 lore raw
In reply to Tejun Heo

Hi there,

we tested out two 600W Fortron PSUs, also tried a BIOS update. Didn't work out.

We also tried the jumper on the disks labelled SSP (Spread Spectrum Clocking), didn't work out out as well.

What seemed to help at least a little bit is to use the 12V connector on the board, that is normally dedicated for graphic cards.

The best test to reproduce the problem, according to a colleague also working on the machine, is a cat /dev/zero > zero.bin

Do you still think it is a PSU or hardware problem? Do you need more details/logs?

Thanks!
Florian

#17 lore raw

Hello,

Quoted 2 lines · Florian Effenberger

we tested out two 600W Fortron PSUs, also tried a BIOS update. Didn't work out.

I see.

Quoted 5 lines

We also tried the jumper on the disks labelled SSP (Spread Spectrum Clocking), didn't work out out as well.

What seemed to help at least a little bit is to use the 12V connector on the board, that is normally dedicated for graphic cards.

Hmmmmm....

Quoted 5 lines

The best test to reproduce the problem, according to a colleague also working on the machine, is a cat /dev/zero > zero.bin

Do you still think it is a PSU or hardware problem? Do you need more details/logs?

The controller being ich8, I'm pretty sure it isn't a driver problem. Do the errors occur on all four drives? Also, if things work after speed is downgraded to 1.5Gbps, it doesn't really matter. There's no noticeable performance difference for single disk anyway.

Signature · 1 line
tejun
#18 lore raw

Hi,

Quoted 1 line

The controller being ich8, I'm pretty sure it isn't a driver problem.

I think so, too. The Intel chipsets have shown to be very good in the past.

Quoted 3 lines

Do the errors occur on all four drives? Also, if things work after speed is downgraded to 1.5Gbps, it doesn't really matter. There's no noticeable performance difference for single disk anyway.

Yes, they do occur on all drives, as far as I know. With 1.5Gbps, the error doesn't occur much as often and not under normal circumstances, only when doing a real hard stress test.

Would it make sense to downgrade to 1.5 Gbps via a boot option?

Florian

#19 lore raw
Quoted 6 lines · Florian Effenberger

Hi,

Quoted 1 line

The controller being ich8, I'm pretty sure it isn't a driver problem.

I think so, too. The Intel chipsets have shown to be very good in the past.

Quoted 7 lines
Quoted 3 lines

Do the errors occur on all four drives? Also, if things work after speed is downgraded to 1.5Gbps, it doesn't really matter. There's no noticeable performance difference for single disk anyway.

Yes, they do occur on all drives, as far as I know. With 1.5Gbps, the error doesn't occur much as often and not under normal circumstances, only when doing a real hard stress test.

Hmmm... Can you use a separate PSU to power two of the four drives and see what happens? Just power up a PSU as directed in the following webpage and connect two of the harddrives to the PSU.

http://modtown.co.uk/mt/article2.php?id=psumod

Quoted 1 line

Would it make sense to downgrade to 1.5 Gbps via a boot option?

I don't know. Till now all the problem cases have been isolated to a specific controller / drive combination (sata_promise and newer seagate drives) or hardware configuration problem (most of them being PSU issues), so I don't think we need such option yet. If you have a problematic hardware which pukes on 3.0Gbps, libata should do the right thing after complaining a bit which IMHO isn't too bad.

Signature · 1 line
tejun
#20 lore raw

Hi Tejun,

Quoted 5 lines

Hmmm... Can you use a separate PSU to power two of the four drives and see what happens? Just power up a PSU as directed in the following webpage and connect two of the harddrives to the PSU.

http://modtown.co.uk/mt/article2.php?id=psumod

thanks for that link, we will try that and keep you updated what happens!

Quoted 6 lines

I don't know. Till now all the problem cases have been isolated to a specific controller / drive combination (sata_promise and newer seagate drives) or hardware configuration problem (most of them being PSU issues), so I don't think we need such option yet. If you have a problematic hardware which pukes on 3.0Gbps, libata should do the right thing after complaining a bit which IMHO isn't too bad.

So, loss of data or data corruption can't occur, even when we have to wait until the speed is limited?

Florian

#21 lore raw
Quoted 9 lines · Florian Effenberger
Quoted 6 lines

I don't know. Till now all the problem cases have been isolated to a specific controller / drive combination (sata_promise and newer seagate drives) or hardware configuration problem (most of them being PSU issues), so I don't think we need such option yet. If you have a problematic hardware which pukes on 3.0Gbps, libata should do the right thing after complaining a bit which IMHO isn't too bad.

So, loss of data or data corruption can't occur, even when we have to wait until the speed is limited?

Nope, there's nothing to worry about.

Signature · 1 line
tejun
#22 lore raw

Hi,

Quoted 1 line

Nope, there's nothing to worry about.

okay, thanks a lot so far, it is good to know that developers are there to help. ;-)

I will let you know how it turned out with the second PSU.

Florian

#23 lore raw
In reply to Tejun Heo

Hi there,

sorry, it seems it was all a false alert and our mainboard was defective. At the end, it turned on only sometimes. To test it, we wanted to install Windows, which didn't work as well.

Now the dealer changed the motherboard, and we are just fine with 3.0 Gbps and Kernel 2.6.21.5.

Sorry for the big confusion and for your great help! I didn't know the board was defective in the first place, there have been no indications like that...

Florian

#24 lore raw
Quoted 10 lines · Florian Effenberger

sorry, it seems it was all a false alert and our mainboard was defective. At the end, it turned on only sometimes. To test it, we wanted to install Windows, which didn't work as well.

Now the dealer changed the motherboard, and we are just fine with 3.0 Gbps and Kernel 2.6.21.5.

Sorry for the big confusion and for your great help! I didn't know the board was defective in the first place, there have been no indications like that...

Yeah, things like these are tricky. SATA is usually the first one to suffer from hardware defect including power fluctuation due to input power, PSU or on-board voltage regulator problems because the link is relatively long and runs at very high speed. I also heard that SATA cables should have been made more resistant to interference but I'm no expert in that area.

It's interesting to see how it got solved. Thanks for another data point to blame hardware when I don't have a clue. :-)

Signature · 1 line
tejun
#25 lore raw

Hi Tejun,

Quoted 6 lines

Yeah, things like these are tricky. SATA is usually the first one to suffer from hardware defect including power fluctuation due to input power, PSU or on-board voltage regulator problems because the link is relatively long and runs at very high speed. I also heard that SATA cables should have been made more resistant to interference but I'm no expert in that area.

me neither. I first thought of a driver issue, because the machine just ran fine and started to have mysterious effects some weeks later...

Quoted 2 lines

It's interesting to see how it got solved. Thanks for another data point to blame hardware when I don't have a clue. :-)

Hehe, you're welcome. ;-)

Thanks for all your efforts, I really appreciate them!

Florian