Ubuntu
linux package

  1. Bug #539467
  2. Comment #66

Comment 66 for bug 539467

Revision history for this message
red_hood (chris-red-hood) wrote :

My hardware details:

Lenovo T61, 7664-18G with BIOS Version 2.26

$ lspci -vvnn |grep -i sata
00:1f.2 SATA controller [0106]: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) SATA AHCI Controller [8086:2829] (rev 03) (prog-if 01 [AHCI 1.0])

Hard drive is:

$ smartctl -a /dev/sda

Model Family: Western Digital Scorpio Blue Serial ATA family
Device Model: WDC WD5000BEVT-00ZAT0
Firmware Version: 01.01A01

Kernel is:

$ uname -a
Linux redlap 2.6.35-25-generic #44-Ubuntu SMP Fri Jan 21 17:40:44 UTC 2011 x86_64 GNU/Linux

When I do

$ echo "min_power" > /sys/class/scsi_host/host2/link_power_management_policy

there is no message from the kernel.

Switching back to

$ echo "max_performance" > /sys/class/scsi_host/host2/link_power_management_policy

the following messages appear:

[47694.108618] ata3: exception Emask 0x10 SAct 0x0 SErr 0x50000 action 0xe frozen
[47694.108626] ata3: irq_stat 0x00400000, PHY RDY changed
[47694.108635] ata3: SError: { PHYRdyChg CommWake }
[47694.108646] ata3: hard resetting link
[47694.850173] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[47694.853238] ata3.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
[47694.853250] ata3.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
[47694.853259] ata3.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[47694.860000] ata3.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
[47694.860051] ata3.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
[47694.860062] ata3.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[47694.862814] ata3.00: configured for UDMA/133
[47694.868797] ata3.00: configured for UDMA/133
[47694.868804] ata3: EH complete

Seems it's still the same behavior in Maverick as it was before in Lucid.

The original hard drive delivered with the Notebook was from Hitachi, so maybe there is some kind of incompatibility between the controller/BIOS and the WD drive. If I find some time, I'll insert the original one and repeat the test.