2.6.22.6 sata_sil device errors & timeouts

2.6.22.6 sata_sil device errors & timeouts

[Andrew Paprocki]

I have a sata_sil 3114 integrated chipset with 2 Hitachi 250gb sata
drives connected, and I'm seeing errors print out during use. The
problems seem to get much worse when I switch from these 250gb drives
to brand new Hitachi HDS721010KLA330 1tb drives, and eventually the
system hangs. With the 250gb drives, I haven't seen a hang, but I
still see the errors below.

Also, I'm seeing two other "issues":

1) When built with modules disabled, and libata handling the sata +
pata (AMD CS5536) connections, the pata drives come _after_ the sata
drives (i.e. w/ 2 sata drives, the first IDE drive is sdc). This makes
boot configuration more complicated if booting off the pata drive. Is
there any way to control which order the drives are assigned when not
building w/ modules?

2) The drives display that they support udma6 in hdparm -I, but only
udma5 is being used. And hdparm -i only shows up to udma2.. ?

Any ideas? Thanks, -Andrew


ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x2400000 action 0x2 frozen
ata2.00: cmd 35/00:00:80:31:54/00:04:02:00:00/e0 tag 0 cdb 0x0 data 524288 out
         res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
ata2: soft resetting port
ata2: port is slow to respond, please be patient (Status 0xd1)
ata2: SRST failed (errno=-16)
ata2: hard resetting port
ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
ata2.00: configured for UDMA/100
ata2: EH complete
sd 1:0:0:0: [sdb] 488397168 512-byte hardware sectors (250059 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


ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x280000 action 0x0
ata1.00: (BMDMA2 stat 0x617d9009)
ata1.00: cmd 25/00:80:00:d6:bd/00:02:0b:00:00/e0 tag 0 cdb 0x0 data 327680 in
         res 51/04:e0:9f:d7:bd/00:00:0b:00:00/eb Emask 0x1 (device error)
ata1.00: configured for UDMA/100
ata1: EH complete
sd 0:0:0:0: [sda] 488397168 512-byte hardware sectors (250059 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


# hdparm -i /dev/sda

/dev/sda:

 Model=HDT722525DLA380                         , FwRev=V44OA96A,
SerialNo=      VDK41GT5F3S4JK
 Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
 RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=52
 BuffType=DualPortCache, BuffSize=7674kB, MaxMultSect=16, MultSect=?16?
 CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=268435455
 IORDY=on/off, tPIO={min:240,w/IORDY:120}, tDMA={min:120,rec:120}
 PIO modes:  pio0 pio1 pio2 pio3 pio4
 DMA modes:  mdma0 mdma1 mdma2
 UDMA modes: udma0 udma1 udma2
 AdvancedPM=yes: disabled (255) WriteCache=enabled
 Drive conforms to: ATA/ATAPI-7 T13 1532D revision 1:  ATA/ATAPI-2
ATA/ATAPI-3 ATA/ATAPI-4 ATA/ATAPI-5 ATA/ATAPI-6 ATA/ATAPI-7

# hdparm -I /dev/sda | grep udma
        DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5 udma6

# lspci -vv -d 1095:3114
0000:00:11.0 0180: 1095:3114 (rev 02)
        Subsystem: 1095:3114
        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: 64, Cache Line Size: 0x08 (32 bytes)
        Interrupt: pin A routed to IRQ 11
        Region 0: I/O ports at fd00 [size=8]
        Region 1: I/O ports at fc00 [size=4]
        Region 2: I/O ports at fb00 [size=8]
        Region 3: I/O ports at fa00 [size=4]
        Region 4: I/O ports at f900 [size=16]
        Region 5: Memory at efffb000 (32-bit, non-prefetchable) [size=1K]
        Expansion ROM at 20000000 [disabled] [size=512K]
        Capabilities: [60] Power Management version 2
                Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=2 PME-


CONFIG_X86_32=y
CONFIG_GENERIC_TIME=y
CONFIG_CLOCKSOURCE_WATCHDOG=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_SEMAPHORE_SLEEPERS=y
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_ZONE_DMA=y
CONFIG_QUICKLIST=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
CONFIG_GENERIC_BUG=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
CONFIG_DMI=y
CONFIG_EXPERIMENTAL=y
CONFIG_BROKEN_ON_SMP=y
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_SYSVIPC_SYSCTL=y
CONFIG_POSIX_MQUEUE=y
CONFIG_SYSFS_DEPRECATED=y
CONFIG_BLK_DEV_INITRD=y
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
CONFIG_SYSCTL=y
CONFIG_UID16=y
CONFIG_SYSCTL_SYSCALL=y
CONFIG_KALLSYMS=y
CONFIG_HOTPLUG=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_ANON_INODES=y
CONFIG_EPOLL=y
CONFIG_SIGNALFD=y
CONFIG_TIMERFD=y
CONFIG_EVENTFD=y
CONFIG_SHMEM=y
CONFIG_VM_EVENT_COUNTERS=y
CONFIG_SLAB=y
CONFIG_RT_MUTEXES=y
CONFIG_BLOCK=y
CONFIG_LBD=y
CONFIG_LSF=y
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
CONFIG_DEFAULT_CFQ=y
CONFIG_TICK_ONESHOT=y
CONFIG_NO_HZ=y
CONFIG_X86_PC=y
CONFIG_MGEODE_LX=y
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_X86_USE_3DNOW=y
CONFIG_X86_TSC=y
CONFIG_HPET_TIMER=y
CONFIG_HPET_EMULATE_RTC=y
CONFIG_PREEMPT_NONE=y
CONFIG_X86_UP_APIC=y
CONFIG_X86_UP_IOAPIC=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_MCE=y
CONFIG_VM86=y
CONFIG_X86_REBOOTFIXUPS=y
CONFIG_X86_MSR=y
CONFIG_X86_CPUID=y
CONFIG_EDD=y
CONFIG_EFI_VARS=y
CONFIG_NOHIGHMEM=y
CONFIG_ARCH_FLATMEM_ENABLE=y
CONFIG_ARCH_SPARSEMEM_ENABLE=y
CONFIG_ARCH_SELECT_MEMORY_MODEL=y
CONFIG_ARCH_POPULATES_NODE_MAP=y
CONFIG_SELECT_MEMORY_MODEL=y
CONFIG_FLATMEM_MANUAL=y
CONFIG_FLATMEM=y
CONFIG_FLAT_NODE_MEM_MAP=y
CONFIG_SPARSEMEM_STATIC=y
CONFIG_MATH_EMULATION=y
CONFIG_MTRR=y
CONFIG_EFI=y
CONFIG_BOOT_IOREMAP=y
CONFIG_HZ_250=y
CONFIG_KEXEC=y
CONFIG_COMPAT_VDSO=y
CONFIG_PM=y
CONFIG_SOFTWARE_SUSPEND=y
CONFIG_ACPI=y
CONFIG_ACPI_SLEEP=y
CONFIG_ACPI_SLEEP_PROC_FS=y
CONFIG_ACPI_PROCFS=y
CONFIG_ACPI_AC=y
CONFIG_ACPI_BATTERY=y
CONFIG_ACPI_BUTTON=y
CONFIG_ACPI_FAN=y
CONFIG_ACPI_PROCESSOR=y
CONFIG_ACPI_THERMAL=y
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_SYSTEM=y
CONFIG_X86_PM_TIMER=y
CONFIG_ACPI_CONTAINER=y
CONFIG_ACPI_SBS=y
CONFIG_CPU_FREQ=y
CONFIG_CPU_FREQ_TABLE=y
CONFIG_CPU_FREQ_STAT=y
CONFIG_CPU_FREQ_STAT_DETAILS=y
CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
CONFIG_CPU_FREQ_GOV_POWERSAVE=y
CONFIG_CPU_FREQ_GOV_USERSPACE=y
CONFIG_CPU_FREQ_GOV_ONDEMAND=y
CONFIG_CPU_FREQ_GOV_CONSERVATIVE=y
CONFIG_X86_ACPI_CPUFREQ=y
CONFIG_PCI=y
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_MMCONFIG=y
CONFIG_PCIEPORTBUS=y
CONFIG_PCIEAER=y
CONFIG_ARCH_SUPPORTS_MSI=y
CONFIG_PCI_MSI=y
CONFIG_HT_IRQ=y
CONFIG_ISA_DMA_API=y
CONFIG_ISA=y
CONFIG_BINFMT_ELF=y
CONFIG_NET=y
CONFIG_PACKET=y
CONFIG_PACKET_MMAP=y
CONFIG_UNIX=y
CONFIG_XFRM=y
CONFIG_XFRM_USER=y
CONFIG_NET_KEY=y
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
CONFIG_IP_ADVANCED_ROUTER=y
CONFIG_ASK_IP_FIB_HASH=y
CONFIG_IP_FIB_HASH=y
CONFIG_IP_MULTIPLE_TABLES=y
CONFIG_IP_ROUTE_MULTIPATH=y
CONFIG_NET_IPIP=y
CONFIG_INET_TUNNEL=y
CONFIG_TCP_CONG_CUBIC=y
CONFIG_FIB_RULES=y
CONFIG_WIRELESS_EXT=y
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_FW_LOADER=y
CONFIG_CONNECTOR=y
CONFIG_PROC_EVENTS=y
CONFIG_MTD=y
CONFIG_MTD_CONCAT=y
CONFIG_MTD_PARTITIONS=y
CONFIG_MTD_REDBOOT_PARTS=y
CONFIG_MTD_CHAR=y
CONFIG_MTD_BLKDEVS=y
CONFIG_MTD_BLOCK=y
CONFIG_FTL=y
CONFIG_NFTL=y
CONFIG_NFTL_RW=y
CONFIG_INFTL=y
CONFIG_MTD_CFI=y
CONFIG_MTD_JEDECPROBE=y
CONFIG_MTD_GEN_PROBE=y
CONFIG_MTD_MAP_BANK_WIDTH_1=y
CONFIG_MTD_MAP_BANK_WIDTH_2=y
CONFIG_MTD_MAP_BANK_WIDTH_4=y
CONFIG_MTD_CFI_I1=y
CONFIG_MTD_CFI_I2=y
CONFIG_MTD_CFI_INTELEXT=y
CONFIG_MTD_CFI_AMDSTD=y
CONFIG_MTD_CFI_STAA=y
CONFIG_MTD_CFI_UTIL=y
CONFIG_MTD_RAM=y
CONFIG_MTD_ROM=y
CONFIG_MTD_ABSENT=y
CONFIG_MTD_COMPLEX_MAPPINGS=y
CONFIG_MTD_PHYSMAP=y
CONFIG_MTD_PCI=y
CONFIG_MTD_PLATRAM=y
CONFIG_MTD_SLRAM=y
CONFIG_MTD_PHRAM=y
CONFIG_MTD_MTDRAM=y
CONFIG_MTD_BLOCK2MTD=y
CONFIG_MTD_NAND=y
CONFIG_MTD_NAND_IDS=y
CONFIG_MTD_NAND_CS553X=y
CONFIG_PNP=y
CONFIG_PNPBIOS=y
CONFIG_PNPBIOS_PROC_FS=y
CONFIG_PNPACPI=y
CONFIG_BLK_DEV_LOOP=y
CONFIG_BLK_DEV_CRYPTOLOOP=y
CONFIG_BLK_DEV_RAM=y
CONFIG_RAID_ATTRS=y
CONFIG_SCSI=y
CONFIG_SCSI_PROC_FS=y
CONFIG_BLK_DEV_SD=y
CONFIG_BLK_DEV_SR=y
CONFIG_BLK_DEV_SR_VENDOR=y
CONFIG_CHR_DEV_SG=y
CONFIG_SCSI_MULTI_LUN=y
CONFIG_SCSI_CONSTANTS=y
CONFIG_SCSI_LOGGING=y
CONFIG_ATA=y
CONFIG_ATA_ACPI=y
CONFIG_SATA_AHCI=y
CONFIG_SATA_SIL=y
CONFIG_PATA_AMD=y
CONFIG_ATA_GENERIC=y
CONFIG_MD=y
CONFIG_BLK_DEV_MD=y
CONFIG_MD_LINEAR=y
CONFIG_MD_RAID0=y
CONFIG_MD_RAID1=y
CONFIG_MD_RAID10=y
CONFIG_MD_RAID456=y
CONFIG_MD_RAID5_RESHAPE=y
CONFIG_MD_MULTIPATH=y
CONFIG_MD_FAULTY=y
CONFIG_BLK_DEV_DM=y
CONFIG_DM_CRYPT=y
CONFIG_DM_SNAPSHOT=y
CONFIG_DM_MIRROR=y
CONFIG_DM_ZERO=y
CONFIG_I2O=y
CONFIG_I2O_LCT_NOTIFY_ON_CHANGES=y
CONFIG_I2O_EXT_ADAPTEC=y
CONFIG_I2O_CONFIG=y
CONFIG_I2O_CONFIG_OLD_IOCTL=y
CONFIG_I2O_BUS=y
CONFIG_I2O_BLOCK=y
CONFIG_I2O_SCSI=y
CONFIG_I2O_PROC=y
CONFIG_NETDEVICES=y
CONFIG_DUMMY=y
CONFIG_NETDEV_1000=y
CONFIG_R8169=y
CONFIG_NETCONSOLE=y
CONFIG_NETPOLL=y
CONFIG_NET_POLL_CONTROLLER=y
CONFIG_INPUT=y
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_EVDEV=y
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
CONFIG_MOUSE_PS2_ALPS=y
CONFIG_MOUSE_PS2_LOGIPS2PP=y
CONFIG_MOUSE_PS2_SYNAPTICS=y
CONFIG_MOUSE_PS2_LIFEBOOK=y
CONFIG_MOUSE_PS2_TRACKPOINT=y
CONFIG_INPUT_MISC=y
CONFIG_INPUT_PCSPKR=y
CONFIG_INPUT_UINPUT=y
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
CONFIG_SERIO_SERPORT=y
CONFIG_SERIO_LIBPS2=y
CONFIG_SERIO_RAW=y
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CONSOLE=y
CONFIG_SERIAL_8250_PCI=y
CONFIG_SERIAL_8250_PNP=y
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
CONFIG_UNIX98_PTYS=y
CONFIG_LEGACY_PTYS=y
CONFIG_IPMI_HANDLER=y
CONFIG_IPMI_DEVICE_INTERFACE=y
CONFIG_IPMI_SI=y
CONFIG_IPMI_WATCHDOG=y
CONFIG_IPMI_POWEROFF=y
CONFIG_WATCHDOG=y
CONFIG_SOFT_WATCHDOG=y
CONFIG_W83627HF_WDT=y
CONFIG_HW_RANDOM=y
CONFIG_HW_RANDOM_GEODE=y
CONFIG_NVRAM=y
CONFIG_RTC=y
CONFIG_AGP=y
CONFIG_DRM=y
CONFIG_CS5535_GPIO=y
CONFIG_HPET=y
CONFIG_HPET_MMAP=y
CONFIG_HANGCHECK_TIMER=y
CONFIG_DEVPORT=y
CONFIG_I2C=y
CONFIG_I2C_BOARDINFO=y
CONFIG_I2C_CHARDEV=y
CONFIG_I2C_ALGOBIT=y
CONFIG_I2C_ALGOPCF=y
CONFIG_I2C_ALGOPCA=y
CONFIG_I2C_AMD8111=y
CONFIG_SCx200_ACB=y
CONFIG_SENSORS_DS1337=y
CONFIG_SENSORS_DS1374=y
CONFIG_SENSORS_EEPROM=y
CONFIG_SENSORS_PCF8574=y
CONFIG_SENSORS_PCA9539=y
CONFIG_SENSORS_PCF8591=y
CONFIG_SENSORS_MAX6875=y
CONFIG_SPI=y
CONFIG_SPI_MASTER=y
CONFIG_SPI_BITBANG=y
CONFIG_HWMON=y
CONFIG_HWMON_VID=y
CONFIG_SENSORS_W83627HF=y
CONFIG_FB=y
CONFIG_FIRMWARE_EDID=y
CONFIG_FB_CFB_FILLRECT=y
CONFIG_FB_CFB_COPYAREA=y
CONFIG_FB_CFB_IMAGEBLIT=y
CONFIG_FB_DEFERRED_IO=y
CONFIG_FB_MODE_HELPERS=y
CONFIG_FB_TILEBLITTING=y
CONFIG_FB_VESA=y
CONFIG_FB_GEODE=y
CONFIG_FB_GEODE_GX=y
CONFIG_FB_GEODE_GX1=y
CONFIG_VGA_CONSOLE=y
CONFIG_VGACON_SOFT_SCROLLBACK=y
CONFIG_VIDEO_SELECT=y
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE_ROTATION=y
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
CONFIG_SOUND=y
CONFIG_SND=y
CONFIG_SND_TIMER=y
CONFIG_SND_PCM=y
CONFIG_SND_SEQUENCER=y
CONFIG_SND_SEQ_DUMMY=y
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=y
CONFIG_SND_PCM_OSS=y
CONFIG_SND_PCM_OSS_PLUGINS=y
CONFIG_SND_SEQUENCER_OSS=y
CONFIG_SND_RTCTIMER=y
CONFIG_SND_SEQ_RTCTIMER_DEFAULT=y
CONFIG_SND_SUPPORT_OLD_API=y
CONFIG_SND_VERBOSE_PROCFS=y
CONFIG_SND_AC97_CODEC=y
CONFIG_SND_CS5535AUDIO=y
CONFIG_SND_INTEL8X0=y
CONFIG_SND_AC97_POWER_SAVE=y
CONFIG_AC97_BUS=y
CONFIG_HID=y
CONFIG_USB_HID=y
CONFIG_USB_HIDINPUT_POWERBOOK=y
CONFIG_USB_HIDDEV=y
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y
CONFIG_USB_ARCH_HAS_EHCI=y
CONFIG_USB=y
CONFIG_USB_DEVICEFS=y
CONFIG_USB_DEVICE_CLASS=y
CONFIG_USB_SUSPEND=y
CONFIG_USB_EHCI_HCD=y
CONFIG_USB_EHCI_SPLIT_ISO=y
CONFIG_USB_EHCI_ROOT_HUB_TT=y
CONFIG_USB_OHCI_HCD=y
CONFIG_USB_OHCI_LITTLE_ENDIAN=y
CONFIG_USB_UHCI_HCD=y
CONFIG_USB_STORAGE=y
CONFIG_RTC_LIB=y
CONFIG_RTC_CLASS=y
CONFIG_RTC_HCTOSYS=y
CONFIG_RTC_INTF_SYSFS=y
CONFIG_RTC_INTF_PROC=y
CONFIG_RTC_INTF_DEV=y
CONFIG_RTC_DRV_DS1307=y
CONFIG_RTC_DRV_DS1672=y
CONFIG_RTC_DRV_RS5C372=y
CONFIG_RTC_DRV_ISL1208=y
CONFIG_RTC_DRV_X1205=y
CONFIG_RTC_DRV_PCF8563=y
CONFIG_RTC_DRV_PCF8583=y
CONFIG_RTC_DRV_RS5C348=y
CONFIG_RTC_DRV_MAX6902=y
CONFIG_RTC_DRV_CMOS=y
CONFIG_RTC_DRV_DS1553=y
CONFIG_RTC_DRV_DS1742=y
CONFIG_RTC_DRV_M48T86=y
CONFIG_RTC_DRV_V3020=y
CONFIG_EXT2_FS=y
CONFIG_EXT2_FS_XATTR=y
CONFIG_EXT2_FS_POSIX_ACL=y
CONFIG_EXT2_FS_SECURITY=y
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
CONFIG_EXT3_FS_SECURITY=y
CONFIG_JBD=y
CONFIG_FS_MBCACHE=y
CONFIG_FS_POSIX_ACL=y
CONFIG_INOTIFY=y
CONFIG_INOTIFY_USER=y
CONFIG_DNOTIFY=y
CONFIG_FUSE_FS=y
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
CONFIG_UDF_FS=y
CONFIG_UDF_NLS=y
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=y
CONFIG_VFAT_FS=y
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_PROC_SYSCTL=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
CONFIG_RAMFS=y
CONFIG_CONFIGFS_FS=y
CONFIG_JFFS2_FS=y
CONFIG_JFFS2_FS_WRITEBUFFER=y
CONFIG_JFFS2_FS_XATTR=y
CONFIG_JFFS2_FS_POSIX_ACL=y
CONFIG_JFFS2_FS_SECURITY=y
CONFIG_JFFS2_ZLIB=y
CONFIG_JFFS2_RTIME=y
CONFIG_CRAMFS=y
CONFIG_SMB_FS=y
CONFIG_CIFS=y
CONFIG_MSDOS_PARTITION=y
CONFIG_NLS=y
CONFIG_NLS_CODEPAGE_437=y
CONFIG_NLS_CODEPAGE_1250=y
CONFIG_NLS_ASCII=y
CONFIG_NLS_ISO8859_1=y
CONFIG_NLS_ISO8859_2=y
CONFIG_NLS_ISO8859_3=y
CONFIG_NLS_ISO8859_4=y
CONFIG_NLS_ISO8859_5=y
CONFIG_NLS_ISO8859_6=y
CONFIG_NLS_ISO8859_7=y
CONFIG_NLS_ISO8859_9=y
CONFIG_NLS_ISO8859_13=y
CONFIG_NLS_ISO8859_14=y
CONFIG_NLS_ISO8859_15=y
CONFIG_NLS_KOI8_R=y
CONFIG_NLS_KOI8_U=y
CONFIG_NLS_UTF8=y
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
CONFIG_MAGIC_SYSRQ=y
CONFIG_DEBUG_BUGVERBOSE=y
CONFIG_EARLY_PRINTK=y
CONFIG_X86_FIND_SMP_CONFIG=y
CONFIG_X86_MPPARSE=y
CONFIG_DOUBLEFAULT=y
CONFIG_CRYPTO=y
CONFIG_CRYPTO_ALGAPI=y
CONFIG_CRYPTO_BLKCIPHER=y
CONFIG_CRYPTO_HASH=y
CONFIG_CRYPTO_MANAGER=y
CONFIG_CRYPTO_HMAC=y
CONFIG_CRYPTO_NULL=y
CONFIG_CRYPTO_MD4=y
CONFIG_CRYPTO_MD5=y
CONFIG_CRYPTO_SHA1=y
CONFIG_CRYPTO_SHA256=y
CONFIG_CRYPTO_SHA512=y
CONFIG_CRYPTO_WP512=y
CONFIG_CRYPTO_TGR192=y
CONFIG_CRYPTO_ECB=y
CONFIG_CRYPTO_CBC=y
CONFIG_CRYPTO_PCBC=y
CONFIG_CRYPTO_DES=y
CONFIG_CRYPTO_BLOWFISH=y
CONFIG_CRYPTO_TWOFISH=y
CONFIG_CRYPTO_TWOFISH_COMMON=y
CONFIG_CRYPTO_SERPENT=y
CONFIG_CRYPTO_AES=y
CONFIG_CRYPTO_AES_586=y
CONFIG_CRYPTO_CAST5=y
CONFIG_CRYPTO_CAST6=y
CONFIG_CRYPTO_TEA=y
CONFIG_CRYPTO_ARC4=y
CONFIG_CRYPTO_KHAZAD=y
CONFIG_CRYPTO_ANUBIS=y
CONFIG_CRYPTO_DEFLATE=y
CONFIG_CRYPTO_MICHAEL_MIC=y
CONFIG_CRYPTO_CRC32C=y
CONFIG_CRYPTO_DEV_GEODE=y
CONFIG_BITREVERSE=y
CONFIG_CRC_CCITT=y
CONFIG_CRC16=y
CONFIG_CRC32=y
CONFIG_LIBCRC32C=y
CONFIG_ZLIB_INFLATE=y
CONFIG_ZLIB_DEFLATE=y
CONFIG_PLIST=y
CONFIG_HAS_IOMEM=y
CONFIG_HAS_IOPORT=y
CONFIG_HAS_DMA=y
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_X86_BIOS_REBOOT=y
CONFIG_KTIME_SCALAR=y

Re: 2.6.22.6 sata_sil device errors & timeouts

[Tejun Heo]

Andrew Paprocki wrote:
> 1) When built with modules disabled, and libata handling the sata +
> pata (AMD CS5536) connections, the pata drives come _after_ the sata
> drives (i.e. w/ 2 sata drives, the first IDE drive is sdc). This makes
> boot configuration more complicated if booting off the pata drive. Is
> there any way to control which order the drives are assigned when not
> building w/ modules?

Please use mount-by-LABEL or UUID.

> 2) The drives display that they support udma6 in hdparm -I, but only
> udma5 is being used. And hdparm -i only shows up to udma2.. ?

For SATA, UDMA mode doesn't matter at all.  As long as you're in DMA
mode, the only thing that matters is PHY link speed and whether NCQ is
enabled.

> ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x2400000 action 0x2 frozen

> ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x280000 action 0x0

In both cases, SError is indicating transmission problem. Handshake
error and Unrecognized FIS type in the first case, 10b to 8b decode
error and CRC error on the second case.  I can't tell why but signals
flying through those redish cables are getting corrupted.

There have been quite a few cases of bad PSU causing transmission
failures on SATA or you might have a bad controller and/or cables.  The
best way to debug this kind of problem is by elimination - by swapping
hardware piece by piece you can find out which one is causing the problem.

-- 
tejun

Re: 2.6.22.6 sata_sil device errors & timeouts

[Andrew Paprocki]

On 9/17/07, Tejun Heo <htejun@gmail.com> wrote:
> Andrew Paprocki wrote:
> > boot configuration more complicated if booting off the pata drive. Is
> > there any way to control which order the drives are assigned when not
> > building w/ modules?
>
> Please use mount-by-LABEL or UUID.

Thanks, wasn't aware of that functionality. Works like a charm.

> > ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x2400000 action 0x2 frozen
> > ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x280000 action 0x0
>
> In both cases, SError is indicating transmission problem. Handshake
> error and Unrecognized FIS type in the first case, 10b to 8b decode
> error and CRC error on the second case.  I can't tell why but signals
> flying through those redish cables are getting corrupted.

I've replaced the cables with a different brand I had laying around,
and I haven't seen a problem yet. I'll need to test it heavily, though
to see if I can trigger anything to pop up.

I didn't mention it before, but I'm also getting these errors every
time I boot. I'm thinking they're related to the drive not supporting
cmds that smartd is sending it. If so, is there any way that
libata/smartd can handle this more gracefully? This stuff spews into
dmesg and gives a scare that there is a real hardware problem that may
cause data corruption. I get exactly 6 instances of each of these two
blocks of output prior to reaching the login prompt:

ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: cmd b0/db:f8:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 0
         res 51/04:f8:00:4f:c2/00:00:00:00:00/00 Emask 0x1 (device error)
ata1.00: configured for UDMA/100
ata1: EH complete

ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd b0/db:f8:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 0
         res 51/04:f8:00:4f:c2/00:00:00:00:00/00 Emask 0x1 (device error)
ata2.00: configured for UDMA/100
ata2: EH complete

Thanks, -Andrew

Re: 2.6.22.6 sata_sil device errors & timeouts

[Tejun Heo]

[cc'ing Bruce Allen]

Andrew Paprocki wrote:
> I didn't mention it before, but I'm also getting these errors every
> time I boot. I'm thinking they're related to the drive not supporting
> cmds that smartd is sending it. If so, is there any way that
> libata/smartd can handle this more gracefully? This stuff spews into
> dmesg and gives a scare that there is a real hardware problem that may
> cause data corruption. I get exactly 6 instances of each of these two
> blocks of output prior to reaching the login prompt:
> 
> ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
> ata1.00: cmd b0/db:f8:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 0
>          res 51/04:f8:00:4f:c2/00:00:00:00:00/00 Emask 0x1 (device error)
> ata1.00: configured for UDMA/100
> ata1: EH complete
> 
> ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
> ata2.00: cmd b0/db:f8:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 0
>          res 51/04:f8:00:4f:c2/00:00:00:00:00/00 Emask 0x1 (device error)
> ata2.00: configured for UDMA/100
> ata2: EH complete

Upgrading smartd should fix it.  Which version are you using?

-- 
tejun

Re: 2.6.22.6 sata_sil device errors & timeouts

[Andrew Paprocki]

On 9/17/07, Tejun Heo <htejun@gmail.com> wrote:
> [cc'ing Bruce Allen]
>
> Andrew Paprocki wrote:
> > ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
> > ata2.00: cmd b0/db:f8:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 0
> >          res 51/04:f8:00:4f:c2/00:00:00:00:00/00 Emask 0x1 (device error)
> > ata2.00: configured for UDMA/100
> > ata2: EH complete
>
> Upgrading smartd should fix it.  Which version are you using?

smartmontools release 5.36 dated 2006/04/12 at 17:39:01 UTC
smartmontools configure arguments: '--prefix=/opt/smartmontools'

I see a newer experimental 5.37 is out. I'll give it a go and see if
the trace goes away.

Thanks, -Andrew

Re: 2.6.22.6 sata_sil device errors & timeouts

[Andrew Paprocki]

On 9/17/07, Andrew Paprocki <andrew@ishiboo.com> wrote:
> On 9/17/07, Tejun Heo <htejun@gmail.com> wrote:
> > Upgrading smartd should fix it.  Which version are you using?
>
> smartmontools release 5.36 dated 2006/04/12 at 17:39:01 UTC
> smartmontools configure arguments: '--prefix=/opt/smartmontools'
>
> I see a newer experimental 5.37 is out. I'll give it a go and see if
> the trace goes away.

Upgrading made it worse.. I now receive the same device errors as well
as a slew of new "HSM violation" errors when smartd starts up:

smartmontools release 5.37 dated 2006/12/20 at 20:37:59 UTC
smartmontools configure arguments:  '--prefix=/opt/smartmontools'

ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
ata5.00: cmd b0/db:f8:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 126976 in
         res 50/00:f8:00:4f:c2/00:00:00:00:00/a0 Emask 0x202 (HSM violation)
ata5: soft resetting port
ata5.00: configured for UDMA/100
ata5: EH complete

# smartctl -i /dev/sda
smartctl version 5.37 [i686-pc-linux-gnu] Copyright (C) 2002-6 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF INFORMATION SECTION ===
Model Family:     Hitachi Deskstar T7K250 series
Device Model:     HDT722525DLA380
Serial Number:    VDK41GT5F3S4JK
Firmware Version: V44OA96A
User Capacity:    250,059,350,016 bytes
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   7
ATA Standard is:  ATA/ATAPI-7 T13 1532D revision 1
Local Time is:    Mon Sep 17 15:25:29 2007 EDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

Thanks, -Andrew

Re: 2.6.22.6 sata_sil device errors & timeouts

[Bruce Allen]

Hi Andrew,

Please build the CVS version (unreleased) of smartmontools.  The versions 
below are dated 2006/12/20 and 2006/04/12.  You need to build a code 
version based on the past few weeks of code.

Cheers,
 	Bruce


On Mon, 17 Sep 2007, Andrew Paprocki wrote:

> On 9/17/07, Andrew Paprocki <andrew@ishiboo.com> wrote:
>> On 9/17/07, Tejun Heo <htejun@gmail.com> wrote:
>>> Upgrading smartd should fix it.  Which version are you using?
>>
>> smartmontools release 5.36 dated 2006/04/12 at 17:39:01 UTC
>> smartmontools configure arguments: '--prefix=/opt/smartmontools'
>>
>> I see a newer experimental 5.37 is out. I'll give it a go and see if
>> the trace goes away.
>
> Upgrading made it worse.. I now receive the same device errors as well
> as a slew of new "HSM violation" errors when smartd starts up:>
> smartmontools release 5.37 dated 2006/12/20 at 20:37:59 UTC
> smartmontools configure arguments:  '--prefix=/opt/smartmontools'
>
> ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
> ata5.00: cmd b0/db:f8:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 126976 in
>         res 50/00:f8:00:4f:c2/00:00:00:00:00/a0 Emask 0x202 (HSM violation)
> ata5: soft resetting port
> ata5.00: configured for UDMA/100
> ata5: EH complete
>
> # smartctl -i /dev/sda
> smartctl version 5.37 [i686-pc-linux-gnu] Copyright (C) 2002-6 Bruce Allen
> Home page is http://smartmontools.sourceforge.net/
>
> === START OF INFORMATION SECTION ===
> Model Family:     Hitachi Deskstar T7K250 series
> Device Model:     HDT722525DLA380
> Serial Number:    VDK41GT5F3S4JK
> Firmware Version: V44OA96A
> User Capacity:    250,059,350,016 bytes
> Device is:        In smartctl database [for details use: -P show]
> ATA Version is:   7
> ATA Standard is:  ATA/ATAPI-7 T13 1532D revision 1
> Local Time is:    Mon Sep 17 15:25:29 2007 EDT
> SMART support is: Available - device has SMART capability.
> SMART support is: Enabled
>
> Thanks, -Andrew
>

Re: 2.6.22.6 sata_sil device errors & timeouts

[Andrew Paprocki]

Bruce,

Just built it -- it eliminated the HSM violations, but I still get the
device errors:

smartmontools release 5.38 dated 2006/12/20 at 20:37:59 UTC
(I see the above date, even though I verified it is built from CVS head)

ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd b0/db:f8:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 0
         res 51/04:f8:00:4f:c2/00:00:00:00:00/00 Emask 0x1 (device error)
ata2.00: configured for UDMA/100
ata2: EH complete

This is what it is in smartd.conf:
/dev/sda -d ata -a -o on -S on
/dev/sdb -d ata -a -o on -S on
/dev/sdc -d ata -a -o on -S on

Thanks, -Andrew

On 9/17/07, Bruce Allen <ballen@gravity.phys.uwm.edu> wrote:
> Hi Andrew,
>
> Please build the CVS version (unreleased) of smartmontools.  The versions
> below are dated 2006/12/20 and 2006/04/12.  You need to build a code
> version based on the past few weeks of code.
>
> Cheers,
>         Bruce

Re: 2.6.22.6 sata_sil device errors & timeouts

[Bruce Allen]

Does removing '-o on' and/or '-S on' eliminate the errors?


On Mon, 17 Sep 2007, Andrew Paprocki wrote:

> Bruce,
>
> Just built it -- it eliminated the HSM violations, but I still get the
> device errors:
>
> smartmontools release 5.38 dated 2006/12/20 at 20:37:59 UTC
> (I see the above date, even though I verified it is built from CVS head)
>
> ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
> ata2.00: cmd b0/db:f8:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 0
>         res 51/04:f8:00:4f:c2/00:00:00:00:00/00 Emask 0x1 (device error)
> ata2.00: configured for UDMA/100
> ata2: EH complete
>
> This is what it is in smartd.conf:
> /dev/sda -d ata -a -o on -S on
> /dev/sdb -d ata -a -o on -S on
> /dev/sdc -d ata -a -o on -S on
>
> Thanks, -Andrew
>
> On 9/17/07, Bruce Allen <ballen@gravity.phys.uwm.edu> wrote:
>> Hi Andrew,
>>
>> Please build the CVS version (unreleased) of smartmontools.  The versions
>> below are dated 2006/12/20 and 2006/04/12.  You need to build a code
>> version based on the past few weeks of code.
>>
>> Cheers,
>>         Bruce
>

Re: 2.6.22.6 sata_sil device errors & timeouts

[Andrew Paprocki]

It appears to be the '-o on' causing the problem. If I remove that,
the errors go away. The strange part is that according to the smartctl
documentation, my drives support it:

# smartctl -c /dev/sda
smartctl version 5.38 [i686-pc-linux-gnu] Copyright (C) 2002-7 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF READ SMART DATA SECTION ===
General SMART Values:
Offline data collection status:  (0x00) Offline data collection activity
                                        was never started.
                                        Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0) The previous self-test routine completed
                                        without error or no self-test has ever
                                        been run.
Total time to complete Offline
data collection:                 (4797) seconds.
Offline data collection
capabilities:                    (0x5b) SMART execute Offline immediate.
                                        Auto Offline data collection
on/off support.
                                        Suspend Offline collection upon new
                                        command.
                                        Offline surface scan supported.
                                        Self-test supported.
                                        No Conveyance Self-test supported.
                                        Selective Self-test supported.
SMART capabilities:            (0x0003) Saves SMART data before entering
                                        power-saving mode.
                                        Supports SMART auto save timer.
Error logging capability:        (0x01) Error logging supported.
                                        General Purpose Logging supported.
Short self-test routine
recommended polling time:        (   1) minutes.
Extended self-test routine
recommended polling time:        (  80) minutes.

Thanks, -Andrew

On 9/18/07, Bruce Allen <ballen@gravity.phys.uwm.edu> wrote:
> Does removing '-o on' and/or '-S on' eliminate the errors?
>
>
> On Mon, 17 Sep 2007, Andrew Paprocki wrote:
>
> > Bruce,
> >
> > Just built it -- it eliminated the HSM violations, but I still get the
> > device errors:
> >
> > smartmontools release 5.38 dated 2006/12/20 at 20:37:59 UTC
> > (I see the above date, even though I verified it is built from CVS head)
> >
> > ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
> > ata2.00: cmd b0/db:f8:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 0
> >         res 51/04:f8:00:4f:c2/00:00:00:00:00/00 Emask 0x1 (device error)
> > ata2.00: configured for UDMA/100
> > ata2: EH complete
> >
> > This is what it is in smartd.conf:
> > /dev/sda -d ata -a -o on -S on
> > /dev/sdb -d ata -a -o on -S on
> > /dev/sdc -d ata -a -o on -S on
> >
> > Thanks, -Andrew

Re: 2.6.22.6 sata_sil device errors & timeouts

[Bruce Allen]

Andrew: thanks for isolating this problem.

Tejun: any thoughts?  The STRANGE_BUFFER_LENGTH problem is fixed in the 
code that Andrew is running.  The problem is provoked with '-o on' which 
goes via a TASKFILE ioctl.

Cheers,
 	Bruce

On Tue, 18 Sep 2007, Andrew Paprocki wrote:

> It appears to be the '-o on' causing the problem. If I remove that,
> the errors go away. The strange part is that according to the smartctl
> documentation, my drives support it:
>
> # smartctl -c /dev/sda
> smartctl version 5.38 [i686-pc-linux-gnu] Copyright (C) 2002-7 Bruce Allen
> Home page is http://smartmontools.sourceforge.net/
>
> === START OF READ SMART DATA SECTION ===
> General SMART Values:
> Offline data collection status:  (0x00) Offline data collection activity
>                                        was never started.
>                                        Auto Offline Data Collection: Disabled.
> Self-test execution status:      (   0) The previous self-test routine completed
>                                        without error or no self-test has ever
>                                        been run.
> Total time to complete Offline
> data collection:                 (4797) seconds.
> Offline data collection
> capabilities:                    (0x5b) SMART execute Offline immediate.
>                                        Auto Offline data collection
> on/off support.
>                                        Suspend Offline collection upon new
>                                        command.
>                                        Offline surface scan supported.
>                                        Self-test supported.
>                                        No Conveyance Self-test supported.
>                                        Selective Self-test supported.
> SMART capabilities:            (0x0003) Saves SMART data before entering
>                                        power-saving mode.
>                                        Supports SMART auto save timer.
> Error logging capability:        (0x01) Error logging supported.
>                                        General Purpose Logging supported.
> Short self-test routine
> recommended polling time:        (   1) minutes.
> Extended self-test routine
> recommended polling time:        (  80) minutes.
>
> Thanks, -Andrew
>
> On 9/18/07, Bruce Allen <ballen@gravity.phys.uwm.edu> wrote:
>> Does removing '-o on' and/or '-S on' eliminate the errors?
>>
>>
>> On Mon, 17 Sep 2007, Andrew Paprocki wrote:
>>
>>> Bruce,
>>>
>>> Just built it -- it eliminated the HSM violations, but I still get the
>>> device errors:
>>>
>>> smartmontools release 5.38 dated 2006/12/20 at 20:37:59 UTC
>>> (I see the above date, even though I verified it is built from CVS head)
>>>
>>> ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
>>> ata2.00: cmd b0/db:f8:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 0
>>>         res 51/04:f8:00:4f:c2/00:00:00:00:00/00 Emask 0x1 (device error)
>>> ata2.00: configured for UDMA/100
>>> ata2: EH complete
>>>
>>> This is what it is in smartd.conf:
>>> /dev/sda -d ata -a -o on -S on
>>> /dev/sdb -d ata -a -o on -S on
>>> /dev/sdc -d ata -a -o on -S on
>>>
>>> Thanks, -Andrew
>

Re: 2.6.22.6 sata_sil device errors & timeouts

[Tejun Heo]

Bruce Allen wrote:
> Andrew: thanks for isolating this problem.
> 
> Tejun: any thoughts?  The STRANGE_BUFFER_LENGTH problem is fixed in the
> code that Andrew is running.  The problem is provoked with '-o on' which
> goes via a TASKFILE ioctl.

I suppose you mean HDIO_DRIVE_TASK, right?  libata doesn't implement
HDIO_DRIVE_TASKFILE and it probably never will.  I'll test it next week
when I get back.  Thanks.

-- 
tejun

Re: 2.6.22.6 sata_sil device errors & timeouts

[Bruce Allen]

Hi Tejun,

Thanks! Yes I meant HDIO_DRIVE_TASK.  Please let me know what your tests 
reveal.

Cheers,
 	Bruce


On Thu, 27 Sep 2007, Tejun Heo wrote:

> Bruce Allen wrote:
>> Andrew: thanks for isolating this problem.
>>
>> Tejun: any thoughts?  The STRANGE_BUFFER_LENGTH problem is fixed in the
>> code that Andrew is running.  The problem is provoked with '-o on' which
>> goes via a TASKFILE ioctl.
>
> I suppose you mean HDIO_DRIVE_TASK, right?  libata doesn't implement
> HDIO_DRIVE_TASKFILE and it probably never will.  I'll test it next week
> when I get back.  Thanks.
>
>