hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }

DISCUSSION John Sigler 4 participants 18 messages Aug 29, 2007 – Sep 3, 2007 2 messages not in the archive libata

lore

Share & tools

lore

John Sigler

author

2007-08-29 16:29 UTC #0 lore raw

Hello,

When my system boots, I get several set_drive_speed_status errors. (Please see attached dmesg output.)

Can someone explain what they mean? How do I get rid of them?

Is there something I need to set in the config? or something I should not have set?

Bonus question: is there some way to turn on DMA for hda?

Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: IDE controller at PCI slot 0000:00:07.1
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
VP_IDE: VIA vt82c686b (rev 40) IDE UDMA100 controller on pci0000:00:07.1

    ide0: BM-DMA at 0xd000-0xd007, BIOS settings: hda:pio, hdb:pio
    ide1: BM-DMA at 0xd008-0xd00f, BIOS settings: hdc:pio, hdd:pio

# hdparm -v /dev/hda

/dev/hda:

 multcount     =  0 (off)
 IO_support    =  1 (32-bit)
 unmaskirq     =  1 (on)
 using_dma     =  0 (off)
 keepsettings  =  0 (off)
 readonly      =  0 (off)
 readahead     = 256 (on)
 geometry      = 500/8/32, sectors = 128000, start = 0

# hdparm -I /dev/hda

/dev/hda:

ATA device, with non-removable media

        Model Number:       PQI IDE DiskOnModule
        Serial Number:      DOM6B00011677
        Firmware Revision:  ra03.00e

Standards:
Likely used: 1
Configuration:
hard sectored
not MFM encoded
head switch time > 15us
fixed drive
disk xfer rate > 5Mbs
Logical max current
cylinders 500 500
heads 8 8
sectors/track 32 32
--
bytes/track: 0 bytes/sector: 528
CHS current addressable sectors: 128000
LBA user addressable sectors: 128000
device size with M = 1024*1024: 62 MBytes
device size with M = 1000*1000: 65 MBytes
Capabilities:
LBA, IORDY not likely
Buffer type: 0002: dual port, multi-sector
Buffer size: 1.0kB bytes avail on r/w long: 4
Cannot perform double-word IO
R/W multiple sector transfer: Max = 1 Current = 0
DMA: not supported
PIO: pio0 pio1 pio2

# lspci
00:00.0 Host bridge: VIA Technologies, Inc. VT82C693A/694x [Apollo PRO133x] (rev c4)
00:01.0 PCI bridge: VIA Technologies, Inc. VT82C598/694x [Apollo MVP3/Pro133x AGP]
00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 40)
00:07.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
00:07.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 1a)
00:07.4 Bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 40)
00:08.0 Ethernet controller: Intel Corporation 82557/8/9 Ethernet Pro 100 (rev 08)
00:09.0 Ethernet controller: Intel Corporation 82557/8/9 Ethernet Pro 100 (rev 08)
00:0a.0 Ethernet controller: Intel Corporation 82557/8/9 Ethernet Pro 100 (rev 08)
00:0b.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27)
00:0d.0 PCI bridge: Intel Corporation 21152 PCI-to-PCI Bridge
02:0f.0 Multimedia video controller: DekTec Digital Video B.V. DTA-105

Regards.

Linux version 2.6.22.1-rt9 (msigler@venus) (gcc version 3.4.4) #2 PREEMPT RT Wed Aug 29 18:02:44 CEST 2007 BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 00000000000a0000 (usable)
BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000000fff0000 (usable)
BIOS-e820: 000000000fff0000 - 000000000fff3000 (ACPI NVS)
BIOS-e820: 000000000fff3000 - 0000000010000000 (ACPI data)
BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
255MB LOWMEM available.
Entering add_active_range(0, 0, 65520) 0 entries of 256 used
Zone PFN ranges:
DMA 0 -> 4096
Normal 4096 -> 65520
early_node_map[1] active PFN ranges

    0:        0 ->    65520

On node 0 totalpages: 65520
DMA zone: 32 pages used for memmap
DMA zone: 0 pages reserved
DMA zone: 4064 pages, LIFO batch:0
Normal zone: 479 pages used for memmap
Normal zone: 60945 pages, LIFO batch:15
DMI 2.3 present.
ACPI: RSDP 000F7110, 0014 (r0 VIA601)
ACPI: RSDT 0FFF3000, 0028 (r1 VIA601 AWRDACPI 42302E31 AWRD 0)
ACPI: FACP 0FFF3040, 0074 (r1 VIA601 AWRDACPI 42302E31 AWRD 0)
ACPI: DSDT 0FFF30C0, 2A03 (r1 VIA601 AWRDACPI 1000 MSFT 100000C)
ACPI: FACS 0FFF0000, 0040
ACPI: PM-Timer IO Port: 0x4008
Allocating PCI resources starting at 20000000 (gap: 10000000:efff0000)
Real-Time Preemption Support (C) 2004-2007 Ingo Molnar
Built 1 zonelists. Total pages: 65009
Kernel command line: ro root=/dev/hda1 console=ttyS0,57600n8 console=tty0 panic=3 lpj=12667000 lapic nmi_watchdog=0 apic=debug Local APIC disabled by BIOS -- reenabling.
Found and enabled local APIC!
mapped APIC to ffffd000 (fee00000)
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
WARNING: experimental RCU implementation.
PID hash table entries: 1024 (order: 10, 4096 bytes)
Detected 1266.700 MHz processor.
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 257104k/262080k available (1461k kernel code, 4480k reserved, 484k data, 144k init, 0k highmem) virtual kernel memory layout:

    fixmap  : 0xffff7000 - 0xfffff000   (  32 kB)
    vmalloc : 0xd0800000 - 0xffff5000   ( 759 MB)
    lowmem  : 0xc0000000 - 0xcfff0000   ( 255 MB)
      .init : 0xc02ea000 - 0xc030e000   ( 144 kB)
      .data : 0xc026d4a9 - 0xc02e662c   ( 484 kB)
      .text : 0xc0100000 - 0xc026d4a9   (1461 kB)

Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay loop (skipped)... 2533.40 BogoMIPS preset
Mount-cache hash table entries: 512
CPU: After generic identify, caps: 0383fbff 00000000 00000000 00000000 00000000 00000000 00000000
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 512K
CPU: After all inits, caps: 0383fbff 00000000 00000000 00000040 00000000 00000000 00000000 Compat vDSO mapped to ffffe000.
CPU: Intel(R) Pentium(R) III CPU - S 1266MHz stepping 04
Checking 'hlt' instruction... OK.
ACPI: Core revision 20070126
ACPI: setting ELCR to 0200 (from 1e20)
Getting VERSION: 40011
Getting VERSION: 40011
Getting ID: 0
Getting LVT0: 700
Getting LVT1: 400
enabled ExtINT on CPU#0
Using local APIC timer interrupts.
calibrating APIC timer ...
... lapic delta = 833376
... PM timer delta = 357960
... PM timer result ok
..... delta 833376
..... mult: 35793226
..... calibration result: 1333401
..... CPU clock speed is 1266.7306 MHz.
..... host bus clock speed is 133.3401 MHz.
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: PCI BIOS revision 2.10 entry at 0xfb210, last bus=2
PCI: Using configuration type 1
Setting up standard PCI resources
ACPI: Interpreter enabled
ACPI: Using PIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI: Probing PCI hardware (bus 00)
PCI quirk: region 6000-607f claimed by vt82c686 HW-mon
PCI quirk: region 5000-500f claimed by vt82c686 SMB
PCI: Firmware left 0000:00:08.0 e100 interrupts enabled, disabling
PCI: Firmware left 0000:00:09.0 e100 interrupts enabled, disabling
PCI: Firmware left 0000:00:0a.0 e100 interrupts enabled, disabling
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 1 3 4 5 6 7 *10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs 1 3 4 5 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKC] (IRQs 1 3 4 5 6 7 10 11 *12 14 15)
ACPI: PCI Interrupt Link [LNKD] (IRQs 1 3 4 *5 6 7 10 11 12 14 15)
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init
ACPI: bus type pnp registered
pnp: PnP ACPI: found 12 devices
ACPI: ACPI bus type pnp unregistered
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
pnp: 00:00: iomem range 0xf0000-0xf3fff could not be reserved
pnp: 00:00: iomem range 0xf4000-0xf7fff could not be reserved
pnp: 00:00: iomem range 0xf8000-0xfbfff could not be reserved
pnp: 00:00: iomem range 0xfc000-0xfffff could not be reserved
PCI: Bridge: 0000:00:01.0
IO window: disabled.
MEM window: disabled.
PREFETCH window: disabled.
PCI: Bridge: 0000:00:0d.0
IO window: disabled.
MEM window: e6300000-e63fffff
PREFETCH window: disabled.
PCI: Setting latency timer of device 0000:00:01.0 to 64
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 6, 294912 bytes)
TCP bind hash table entries: 8192 (order: 5, 229376 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP reno registered
io scheduler noop registered (default)
PCI: VIA PCI bridge detected. Disabling DAC.
Boot video device is 0000:00:0b.0
input: Power Button (FF) as /class/input/input0
ACPI: Power Button (FF) [PWRF]
input: Power Button (CM) as /class/input/input1
ACPI: Power Button (CM) [PWRB]
Real Time Clock Driver v1.12ac
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
00:08: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
00:09: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
eepro100.c:v1.09j-t 9/29/99 Donald Becker
eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V. Savochkin <[email protected]> and others
ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 10
PCI: setting IRQ 10 as level-triggered
ACPI: PCI Interrupt 0000:00:08.0[A] -> Link [LNKA] -> GSI 10 (level, low) -> IRQ 10
eth0: 0000:00:08.0, 00:30:64:02:E8:A1, IRQ 10.
Board assembly 721383-016, Physical connectors present: RJ45
Primary interface chip i82555 PHY #1.
General self-test: passed.
Serial sub-system self-test: passed.
Internal registers self-test: passed.
ROM checksum self-test: passed (0x04f4518b).
ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 11
PCI: setting IRQ 11 as level-triggered
ACPI: PCI Interrupt 0000:00:09.0[A] -> Link [LNKB] -> GSI 11 (level, low) -> IRQ 11
eth1: 0000:00:09.0, 00:30:64:02:E8:A2, IRQ 11.
Board assembly 721383-016, Physical connectors present: RJ45
Primary interface chip i82555 PHY #1.
General self-test: passed.
Serial sub-system self-test: passed.
Internal registers self-test: passed.
ROM checksum self-test: passed (0x04f4518b).
ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 12
PCI: setting IRQ 12 as level-triggered
ACPI: PCI Interrupt 0000:00:0a.0[A] -> Link [LNKC] -> GSI 12 (level, low) -> IRQ 12
eth2: 0000:00:0a.0, 00:30:64:02:E8:A3, IRQ 12.
Board assembly 721383-016, Physical connectors present: RJ45
Primary interface chip i82555 PHY #1.
General self-test: passed.
Serial sub-system self-test: passed.
Internal registers self-test: passed.
ROM checksum self-test: passed (0x04f4518b).
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: IDE controller at PCI slot 0000:00:07.1
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
VP_IDE: VIA vt82c686b (rev 40) IDE UDMA100 controller on pci0000:00:07.1

    ide0: BM-DMA at 0xd000-0xd007, BIOS settings: hda:pio, hdb:pio
    ide1: BM-DMA at 0xd008-0xd00f, BIOS settings: hdc:pio, hdd:pio

Probing IDE interface ide0...
hda: PQI IDE DiskOnModule, ATA DISK drive
hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }
hda: set_drive_speed_status: error=0x04 { DriveStatusError }
hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }
hda: set_drive_speed_status: error=0x04 { DriveStatusError } ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
hda: max request size: 128KiB
hda: 128000 sectors (65 MB) w/1KiB Cache, CHS=500/8/32
hda: hda1 hda2
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
802.1Q VLAN Support v1.8 Ben Greear <[email protected]> All bugs added by David S. Miller <[email protected]>
Using IPI Shortcut mode
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 144k freed

#
# Automatically generated make config: don't edit # Linux kernel version: 2.6.22.1-rt9
# Wed Aug 29 18:02:24 2007
#
CONFIG_X86_32=y
CONFIG_GENERIC_TIME=y
CONFIG_GENERIC_CMOS_UPDATE=y CONFIG_CLOCKSOURCE_WATCHDOG=y CONFIG_GENERIC_CLOCKEVENTS=y CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y CONFIG_NONIRQ_WAKEUP=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_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"

#
# Code maturity level options
#
# CONFIG_EXPERIMENTAL is not set
CONFIG_BROKEN_ON_SMP=y
CONFIG_LOCK_KERNEL=y
CONFIG_INIT_ENV_ARG_LIMIT=32

#
# General setup
#
CONFIG_LOCALVERSION=""
# CONFIG_LOCALVERSION_AUTO is not set
# CONFIG_SWAP is not set
# CONFIG_SYSVIPC is not set
# CONFIG_BSD_PROCESS_ACCT is not set
# CONFIG_TASKSTATS is not set
# CONFIG_UTS_NS is not set
# CONFIG_AUDIT is not set
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
CONFIG_LOG_BUF_SHIFT=14
CONFIG_SYSFS_DEPRECATED=y
# CONFIG_RELAY is not set
# CONFIG_BLK_DEV_INITRD is not set
CONFIG_SYSCTL=y
CONFIG_EMBEDDED=y
CONFIG_UID16=y
CONFIG_SYSCTL_SYSCALL=y
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_EXTRA_PASS is not set
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_SLUB is not set
# CONFIG_SLOB is not set
CONFIG_RT_MUTEXES=y
# CONFIG_TINY_SHMEM is not set
CONFIG_BASE_SMALL=0

#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
CONFIG_MODVERSIONS=y
# CONFIG_MODULE_SRCVERSION_ALL is not set
# CONFIG_KMOD is not set

#
# Block layer
#
CONFIG_BLOCK=y
# CONFIG_LBD is not set
# CONFIG_BLK_DEV_IO_TRACE is not set
# CONFIG_LSF is not set

#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
# CONFIG_IOSCHED_AS is not set
# CONFIG_IOSCHED_DEADLINE is not set
# CONFIG_IOSCHED_CFQ is not set
# CONFIG_DEFAULT_AS is not set
# CONFIG_DEFAULT_DEADLINE is not set
# CONFIG_DEFAULT_CFQ is not set
CONFIG_DEFAULT_NOOP=y
CONFIG_DEFAULT_IOSCHED="noop"

#
# Processor type and features
#
CONFIG_TICK_ONESHOT=y
# CONFIG_NO_HZ is not set
CONFIG_HIGH_RES_TIMERS=y
CONFIG_GENERIC_CLOCKEVENTS_BUILD=y
# CONFIG_SMP is not set
CONFIG_X86_PC=y
# CONFIG_X86_ELAN is not set
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_NUMAQ is not set
# CONFIG_X86_SUMMIT is not set
# CONFIG_X86_BIGSMP is not set
# CONFIG_X86_VISWS is not set
# CONFIG_X86_GENERICARCH is not set
# CONFIG_X86_ES7000 is not set
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMII is not set
CONFIG_MPENTIUMIII=y
# CONFIG_MPENTIUMM is not set
# CONFIG_MCORE2 is not set
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MK8 is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MEFFICEON is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MGEODEGX1 is not set
# CONFIG_MGEODE_LX is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
# CONFIG_MVIAC7 is not set
# CONFIG_X86_GENERIC is not set
CONFIG_X86_CMPXCHG=y
CONFIG_X86_L1_CACHE_SHIFT=5
CONFIG_X86_XADD=y
CONFIG_RWSEM_GENERIC_SPINLOCK=y
CONFIG_ASM_SEMAPHORES=y
# CONFIG_ARCH_HAS_ILOG2_U32 is not set
# CONFIG_ARCH_HAS_ILOG2_U64 is not set
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_GOOD_APIC=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_X86_TSC=y
CONFIG_X86_CMOV=y
CONFIG_X86_MINIMUM_CPU_MODEL=4
# CONFIG_HPET_TIMER is not set
# CONFIG_PREEMPT_NONE is not set
# CONFIG_PREEMPT_VOLUNTARY is not set
# CONFIG_PREEMPT_DESKTOP is not set
CONFIG_PREEMPT_RT=y
CONFIG_PREEMPT=y
CONFIG_PREEMPT_SOFTIRQS=y
CONFIG_PREEMPT_HARDIRQS=y
CONFIG_PREEMPT_BKL=y
# CONFIG_CLASSIC_RCU is not set
CONFIG_PREEMPT_RCU=y
# CONFIG_RCU_TRACE is not set
CONFIG_X86_UP_APIC=y
# CONFIG_X86_UP_IOAPIC is not set
CONFIG_X86_LOCAL_APIC=y
# CONFIG_X86_MCE is not set
# CONFIG_VM86 is not set
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
# CONFIG_X86_REBOOTFIXUPS is not set
# CONFIG_MICROCODE is not set
# CONFIG_X86_MSR is not set
# CONFIG_X86_CPUID is not set

#
# Firmware Drivers
#
# CONFIG_EDD is not set
# CONFIG_DELL_RBU is not set
# CONFIG_DCDBAS is not set
CONFIG_NOHIGHMEM=y
# CONFIG_HIGHMEM4G is not set
# CONFIG_HIGHMEM64G is not set
CONFIG_PAGE_OFFSET=0xC0000000
CONFIG_ARCH_POPULATES_NODE_MAP=y
CONFIG_FLATMEM=y
CONFIG_FLAT_NODE_MEM_MAP=y
# CONFIG_SPARSEMEM_STATIC is not set
CONFIG_SPLIT_PTLOCK_CPUS=4
# CONFIG_RESOURCES_64BIT is not set
CONFIG_ZONE_DMA_FLAG=1
CONFIG_NR_QUICK=1
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
# CONFIG_EFI is not set
CONFIG_REGPARM=y
# CONFIG_SECCOMP is not set
CONFIG_HZ_100=y
# CONFIG_HZ_250 is not set
# CONFIG_HZ_300 is not set
# CONFIG_HZ_1000 is not set
CONFIG_HZ=100
# CONFIG_KEXEC is not set
CONFIG_PHYSICAL_START=0x100000
CONFIG_PHYSICAL_ALIGN=0x100000
# CONFIG_COMPAT_VDSO is not set

#
# Power management options (ACPI, APM)
#
CONFIG_PM=y
# CONFIG_PM_LEGACY is not set
# CONFIG_PM_DEBUG is not set
# CONFIG_PM_SYSFS_DEPRECATED is not set

#
# ACPI (Advanced Configuration and Power Interface) Support #
CONFIG_ACPI=y
# CONFIG_ACPI_SLEEP is not set
# CONFIG_ACPI_PROCFS is not set
# CONFIG_ACPI_AC is not set
# CONFIG_ACPI_BATTERY is not set CONFIG_ACPI_BUTTON=y
# CONFIG_ACPI_FAN is not set
# CONFIG_ACPI_PROCESSOR is not set
# CONFIG_ACPI_ASUS is not set
# CONFIG_ACPI_TOSHIBA is not set CONFIG_ACPI_BLACKLIST_YEAR=0
# CONFIG_ACPI_DEBUG is not set
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_SYSTEM=y
CONFIG_X86_PM_TIMER=y
# CONFIG_APM is not set

#
# CPU Frequency scaling
#
# CONFIG_CPU_FREQ is not set

#
# CPU idle PM support
#
# CONFIG_CPU_IDLE is not set

#
# Bus options (PCI, PCMCIA, EISA, MCA, ISA)
#
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GOMMCONFIG is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_MMCONFIG=y
# CONFIG_PCIEPORTBUS is not set
# CONFIG_ARCH_SUPPORTS_MSI is not set
CONFIG_ISA_DMA_API=y
# CONFIG_ISA is not set
# CONFIG_MCA is not set
# CONFIG_SCx200 is not set

#
# PCCARD (PCMCIA/CardBus) support
#
# CONFIG_PCCARD is not set

#
# Executable file formats
#
CONFIG_BINFMT_ELF=y
# CONFIG_BINFMT_AOUT is not set
# CONFIG_BINFMT_MISC is not set

#
# Networking
#
CONFIG_NET=y

#
# Networking options
#
CONFIG_PACKET=y
CONFIG_PACKET_MMAP=y
CONFIG_UNIX=y
# CONFIG_NET_KEY is not set
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
# CONFIG_IP_ADVANCED_ROUTER is not set
CONFIG_IP_FIB_HASH=y
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_IP_MROUTE is not set
# CONFIG_SYN_COOKIES is not set
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_INET_IPCOMP is not set
# CONFIG_INET_XFRM_TUNNEL is not set
# CONFIG_INET_TUNNEL is not set
# CONFIG_INET_XFRM_MODE_TRANSPORT is not set
# CONFIG_INET_XFRM_MODE_TUNNEL is not set
# CONFIG_INET_XFRM_MODE_BEET is not set
CONFIG_INET_DIAG=y
CONFIG_INET_TCP_DIAG=y
# CONFIG_TCP_CONG_ADVANCED is not set
CONFIG_TCP_CONG_CUBIC=y
CONFIG_DEFAULT_TCP_CONG="cubic"
# CONFIG_IPV6 is not set
# CONFIG_INET6_XFRM_TUNNEL is not set
# CONFIG_INET6_TUNNEL is not set
# CONFIG_NETWORK_SECMARK is not set
# CONFIG_NETFILTER is not set
# CONFIG_BRIDGE is not set
CONFIG_VLAN_8021Q=y
# CONFIG_DECNET is not set
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set

#
# QoS and/or fair queueing
#
# CONFIG_NET_SCHED is not set

#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# CONFIG_HAMRADIO is not set
# CONFIG_IRDA is not set
# CONFIG_BT is not set

#
# Wireless
#
# CONFIG_CFG80211 is not set
# CONFIG_WIRELESS_EXT is not set
# CONFIG_IEEE80211 is not set
# CONFIG_RFKILL is not set

#
# Device Drivers
#

#
# Generic Driver Options
#
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
# CONFIG_FW_LOADER is not set
# CONFIG_SYS_HYPERVISOR is not set

#
# Connector - unified userspace <-> kernelspace linker #
# CONFIG_CONNECTOR is not set
# CONFIG_MTD is not set

#
# Parallel port support
#
# CONFIG_PARPORT is not set

#
# Plug and Play support
#
CONFIG_PNP=y
# CONFIG_PNP_DEBUG is not set

#
# Protocols
#
CONFIG_PNPACPI=y

#
# Block devices
#
# CONFIG_BLK_DEV_FD is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_COW_COMMON is not set
# CONFIG_BLK_DEV_LOOP is not set
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_SX8 is not set
# CONFIG_BLK_DEV_RAM is not set
# CONFIG_CDROM_PKTCDVD is not set
# CONFIG_ATA_OVER_ETH is not set

#
# Misc devices
#
# CONFIG_PHANTOM is not set
# CONFIG_SGI_IOC4 is not set
# CONFIG_SONY_LAPTOP is not set
# CONFIG_THINKPAD_ACPI is not set
CONFIG_IDE=y
CONFIG_IDE_MAX_HWIFS=4
CONFIG_BLK_DEV_IDE=y

#
# Please see Documentation/ide.txt for help/info on IDE drives #
# CONFIG_BLK_DEV_IDE_SATA is not set
# CONFIG_BLK_DEV_HD_IDE is not set CONFIG_BLK_DEV_IDEDISK=y
# CONFIG_IDEDISK_MULTI_MODE is not set
# CONFIG_BLK_DEV_IDECD is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
# CONFIG_BLK_DEV_IDEACPI is not set
# CONFIG_IDE_TASK_IOCTL is not set
# CONFIG_IDE_PROC_FS is not set

#
# IDE chipset support/bugfixes
#
# CONFIG_IDE_GENERIC is not set
# CONFIG_BLK_DEV_CMD640 is not set
# CONFIG_BLK_DEV_IDEPNP is not set
CONFIG_BLK_DEV_IDEPCI=y
# CONFIG_IDEPCI_SHARE_IRQ is not set
CONFIG_IDEPCI_PCIBUS_ORDER=y
# CONFIG_BLK_DEV_OFFBOARD is not set
# CONFIG_BLK_DEV_GENERIC is not set
# CONFIG_BLK_DEV_RZ1000 is not set
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
# CONFIG_IDEDMA_ONLYDISK is not set
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
# CONFIG_BLK_DEV_AMD74XX is not set
# CONFIG_BLK_DEV_ATIIXP is not set
# CONFIG_BLK_DEV_CMD64X is not set
# CONFIG_BLK_DEV_TRIFLEX is not set
# CONFIG_BLK_DEV_CY82C693 is not set
# CONFIG_BLK_DEV_CS5530 is not set
# CONFIG_BLK_DEV_CS5535 is not set
# CONFIG_BLK_DEV_HPT34X is not set
# CONFIG_BLK_DEV_HPT366 is not set
# CONFIG_BLK_DEV_JMICRON is not set
# CONFIG_BLK_DEV_SC1200 is not set
# CONFIG_BLK_DEV_PIIX is not set
# CONFIG_BLK_DEV_IT8213 is not set
# CONFIG_BLK_DEV_IT821X is not set
# CONFIG_BLK_DEV_NS87415 is not set
# CONFIG_BLK_DEV_PDC202XX_OLD is not set
# CONFIG_BLK_DEV_PDC202XX_NEW is not set
# CONFIG_BLK_DEV_SVWKS is not set
# CONFIG_BLK_DEV_SIIMAGE is not set
# CONFIG_BLK_DEV_SIS5513 is not set
# CONFIG_BLK_DEV_SLC90E66 is not set
# CONFIG_BLK_DEV_TRM290 is not set
CONFIG_BLK_DEV_VIA82CXXX=y
# CONFIG_BLK_DEV_TC86C001 is not set
# CONFIG_IDE_ARM is not set
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_IVB is not set
# CONFIG_BLK_DEV_HD is not set

#
# SCSI device support
#
# CONFIG_RAID_ATTRS is not set
# CONFIG_SCSI is not set
# CONFIG_SCSI_NETLINK is not set
# CONFIG_ATA is not set

#
# Multi-device support (RAID and LVM)
#
# CONFIG_MD is not set

#
# Fusion MPT device support
#
# CONFIG_FUSION is not set

#
# IEEE 1394 (FireWire) support
#

#
# An alternative FireWire stack is available with EXPERIMENTAL=y #
# CONFIG_IEEE1394 is not set

#
# I2O device support
#
# CONFIG_I2O is not set
# CONFIG_MACINTOSH_DRIVERS is not set

#
# Network device support
#
CONFIG_NETDEVICES=y
# CONFIG_DUMMY is not set
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
# CONFIG_NET_SB1000 is not set
# CONFIG_ARCNET is not set
# CONFIG_PHYLIB is not set

#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
CONFIG_MII=y
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM is not set
# CONFIG_CASSINI is not set
# CONFIG_NET_VENDOR_3COM is not set

#
# Tulip family network device support
#
# CONFIG_NET_TULIP is not set
# CONFIG_HP100 is not set
CONFIG_NET_PCI=y
# CONFIG_PCNET32 is not set
# CONFIG_AMD8111_ETH is not set
# CONFIG_ADAPTEC_STARFIRE is not set
# CONFIG_B44 is not set
# CONFIG_FORCEDETH is not set
# CONFIG_DGRS is not set
CONFIG_EEPRO100=y
# CONFIG_E100 is not set
# CONFIG_FEALNX is not set
CONFIG_NATSEMI=y
# CONFIG_NE2K_PCI is not set
# CONFIG_8139TOO is not set
# CONFIG_SIS900 is not set
# CONFIG_EPIC100 is not set
# CONFIG_SUNDANCE is not set
# CONFIG_TLAN is not set
# CONFIG_VIA_RHINE is not set
# CONFIG_NETDEV_1000 is not set
# CONFIG_NETDEV_10000 is not set
# CONFIG_TR is not set

#
# Wireless LAN
#
# CONFIG_WLAN_PRE80211 is not set
# CONFIG_WLAN_80211 is not set
# CONFIG_WAN is not set
# CONFIG_FDDI is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set
# CONFIG_NETPOLL is not set
# CONFIG_NET_POLL_CONTROLLER is not set

#
# ISDN subsystem
#
# CONFIG_ISDN is not set

#
# Telephony Support
#
# CONFIG_PHONE is not set

#
# Input device support
#
CONFIG_INPUT=y
# CONFIG_INPUT_FF_MEMLESS is not set
# CONFIG_INPUT_POLLDEV is not set

#
# Userland interfaces
#
# CONFIG_INPUT_MOUSEDEV is not set
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_TSDEV is not set
# CONFIG_INPUT_EVDEV is not set
# CONFIG_INPUT_EVBUG is not set

#
# Input Device Drivers
#
# CONFIG_INPUT_KEYBOARD is not set
# CONFIG_INPUT_MOUSE is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TABLET is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
# CONFIG_INPUT_MISC is not set

#
# Hardware I/O ports
#
# CONFIG_SERIO is not set
# CONFIG_GAMEPORT is not set

#
# Character devices
#
# CONFIG_VT is not set
# CONFIG_SERIAL_NONSTANDARD is not set

#
# Serial drivers
#
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CONSOLE=y
CONFIG_SERIAL_8250_PCI=y
CONFIG_SERIAL_8250_PNP=y
CONFIG_SERIAL_8250_NR_UARTS=4
CONFIG_SERIAL_8250_RUNTIME_UARTS=4
# CONFIG_SERIAL_8250_EXTENDED is not set

#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
# CONFIG_SERIAL_JSM is not set
CONFIG_UNIX98_PTYS=y
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=256

#
# IPMI
#
# CONFIG_IPMI_HANDLER is not set
# CONFIG_WATCHDOG is not set
# CONFIG_HW_RANDOM is not set
# CONFIG_NVRAM is not set
CONFIG_RTC=y
# CONFIG_RTC_HISTOGRAM is not set
# CONFIG_BLOCKER is not set
# CONFIG_LPPTEST is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
# CONFIG_AGP is not set
# CONFIG_DRM is not set
# CONFIG_MWAVE is not set
# CONFIG_PC8736x_GPIO is not set
# CONFIG_NSC_GPIO is not set
# CONFIG_CS5535_GPIO is not set
# CONFIG_RAW_DRIVER is not set
# CONFIG_HPET is not set
# CONFIG_HANGCHECK_TIMER is not set

#
# TPM devices
#
# CONFIG_RMEM is not set
# CONFIG_ALLOC_RTSJ_MEM is not set
CONFIG_DEVPORT=y
# CONFIG_I2C is not set

#
# SPI support
#
# CONFIG_SPI is not set
# CONFIG_SPI_MASTER is not set

#
# Dallas's 1-wire bus
#
# CONFIG_W1 is not set
# CONFIG_HWMON is not set

#
# Multifunction device drivers
#
# CONFIG_MFD_SM501 is not set

#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set
# CONFIG_DVB_CORE is not set
# CONFIG_DAB is not set

#
# Graphics support
#
# CONFIG_BACKLIGHT_LCD_SUPPORT is not set

#
# Display device support
#
# CONFIG_DISPLAY_SUPPORT is not set
# CONFIG_VGASTATE is not set
# CONFIG_FB is not set

#
# Sound
#
# CONFIG_SOUND is not set

#
# HID Devices
#
# CONFIG_HID is not set

#
# USB support
#
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y
CONFIG_USB_ARCH_HAS_EHCI=y
# CONFIG_USB is not set

#
# NOTE: USB_STORAGE enables SCSI, and 'SCSI disk support' #

#
# USB Gadget Support
#
# CONFIG_USB_GADGET is not set
# CONFIG_MMC is not set

#
# LED devices
#
# CONFIG_NEW_LEDS is not set

#
# LED drivers
#

#
# LED Triggers
#

#
# InfiniBand support
#
# CONFIG_INFINIBAND is not set

#
# EDAC - error detection and reporting (RAS) (EXPERIMENTAL) #

#
# Real Time Clock
#

#
# DMA Engine support
#
# CONFIG_DMA_ENGINE is not set

#
# DMA Clients
#

#
# DMA Devices
#

#
# Virtualization
#

#
# File systems
#
CONFIG_EXT2_FS=y
# CONFIG_EXT2_FS_XATTR is not set
# CONFIG_EXT2_FS_XIP is not set
# CONFIG_EXT3_FS is not set
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not set
# CONFIG_FS_POSIX_ACL is not set
# CONFIG_XFS_FS is not set
# CONFIG_OCFS2_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_ROMFS_FS is not set
# CONFIG_INOTIFY is not set
# CONFIG_QUOTA is not set
CONFIG_DNOTIFY=y
# CONFIG_AUTOFS_FS is not set
# CONFIG_AUTOFS4_FS is not set
# CONFIG_FUSE_FS is not set

#
# CD-ROM/DVD Filesystems
#
# CONFIG_ISO9660_FS is not set
# CONFIG_UDF_FS is not set

#
# DOS/FAT/NT Filesystems
#
# CONFIG_MSDOS_FS is not set
# CONFIG_VFAT_FS is not set
# CONFIG_NTFS_FS is not set

#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_PROC_SYSCTL=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
# CONFIG_TMPFS_POSIX_ACL is not set
# CONFIG_HUGETLBFS is not set
# CONFIG_HUGETLB_PAGE is not set
CONFIG_RAMFS=y

#
# Miscellaneous filesystems
#
# CONFIG_HFSPLUS_FS is not set
# CONFIG_CRAMFS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set

#
# Network File Systems
#
# CONFIG_NFS_FS is not set
# CONFIG_NFSD is not set
# CONFIG_SMB_FS is not set
# CONFIG_CIFS is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set

#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y

#
# Native Language Support
#
# CONFIG_NLS is not set

#
# Kernel hacking
#
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
# CONFIG_PRINTK_TIME is not set
# CONFIG_ENABLE_MUST_CHECK is not set
# CONFIG_MAGIC_SYSRQ is not set
# CONFIG_UNUSED_SYMBOLS is not set
# CONFIG_DEBUG_FS is not set
# CONFIG_HEADERS_CHECK is not set
# CONFIG_DEBUG_KERNEL is not set
# CONFIG_EVENT_TRACE is not set
# CONFIG_FUNCTION_TRACE is not set
# CONFIG_WAKEUP_TIMING is not set
# CONFIG_CRITICAL_PREEMPT_TIMING is not set
# CONFIG_CRITICAL_IRQSOFF_TIMING is not set
# CONFIG_DEBUG_BUGVERBOSE is not set
CONFIG_EARLY_PRINTK=y
CONFIG_X86_FIND_SMP_CONFIG=y
CONFIG_X86_MPPARSE=y
CONFIG_DOUBLEFAULT=y

#
# Security options
#
# CONFIG_KEYS is not set
# CONFIG_SECURITY is not set

#
# Cryptographic options
#
# CONFIG_CRYPTO is not set

#
# Library routines
#
CONFIG_BITREVERSE=y
# CONFIG_CRC_CCITT is not set
# CONFIG_CRC16 is not set
# CONFIG_CRC_ITU_T is not set
CONFIG_CRC32=y
# CONFIG_LIBCRC32C is not set
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

Alan Cox

2007-08-29 16:38 UTC #1 lore raw

Quoted 3 lines

Standards:
Likely used: 1

Prehistory

Quoted 1 line

LBA, IORDY not likely

No DMA, nothing above PIO2

Quoted 3 lines

Buffer type: 0002: dual port, multi-sector
Buffer size: 1.0kB bytes avail on r/w long: 4
Cannot perform double-word IO

Can't even do double word I/O

The messages with old IDE should be harmless and the current libata IDE should drive it politely (I debugged a problem the same hardware showed up for someone else).

Basically your dinosaur is working correctly.

Alan

John Sigler

author

2007-08-30 08:17 UTC #2 lore raw

Quoted 6 lines · Alan Cox

Quoted 2 lines · John Sigler
Standards:
Likely used: 1
Prehistory

The tragic bit is that we were sold similar DOMs in 2007... (It's probably time to change suppliers?)

Quoted 3 lines

Quoted 1 line
LBA, IORDY not likely
No DMA, nothing above PIO2

OK. (Grumble)

Quoted 5 lines

Quoted 3 lines
Buffer type: 0002: dual port, multi-sector
Buffer size: 1.0kB bytes avail on r/w long: 4
Cannot perform double-word IO
Can't even do double word I/O

Double word is 32 bits, right? Isn't "Cannot perform double-word IO" in contradiction with the following statements?

IO_support = 1 (32-bit)

Buffer size: 1.0kB bytes avail on r/w long: 4

(Assuming an 8-bit byte, 4 bytes = 32 bits)

Quoted 3 lines

The messages with old IDE should be harmless and the current libata IDE should drive it politely (I debugged a problem the same hardware showed up for someone else).

When you say "the current libata IDE" do you mean PATA_VIA (in my case)?
I've avoided this driver because it is marked EXPERIMENTAL. Would there be any benefit in using it over the legacy ATA/MFM/RLL driver?

Quoted 1 line

Basically your dinosaur is working correctly.

What do the warnings mean? :-)

Regards.

A message that is not in the archive (sent off-list or not yet received): [email protected]

John Sigler

author

2007-08-30 12:30 UTC #4 lore raw

Quoted 8 lines · Petr Vandrovec

Quoted 5 lines · John Sigler
Quoted 1 line · Alan Cox
Basically your dinosaur is working correctly.
What do the warnings mean? :-)

Quoted 7 lines

That your drive does not support set transfer mode/speed command at all, or that value which kernel tried is not supported by the drive...
I would guess that some contractor wrote firmware for device for PQI in one day for $100, and before that somebody else designed ATA-SD bridge for PQI for another $100.
I guess that these two printk()s happen because drive claims to support pio0,1,2 - so Linux tries pio2, drive refuses, Linux tries pio1, drive refuses, and finally as pio0 is default, that one gets used. Which is more or less confirmed by having no '*' sign in front of any pio - with "real" drives you should see '*' in front of one of listed dma/pio modes.
You should ask reseller how they can ship drive which does not conform to any ATA standard...

I took drivers/ide/pci/via82cxxx.c and sprinkled ENTER/EXIT printk's.
http://lxr.linux.no/source/drivers/ide/pci/via82cxxx.c

via82cxxx_tune_drive() and via82cxxx_ide_dma_check() both call via_set_drive() which calls ide_config_drive_speed().

http://lxr.linux.no/source/drivers/ide/ide-iops.c#L769

  if (error)
  {
    (void) ide_dump_status(drive, "set_drive_speed_status", stat);
    printk(KERN_INFO "EXIT %s error\n", __func__);
    return error;
  }

Does someone know why error is not set to 0?

    ide0: BM-DMA at 0xd000-0xd007, BIOS settings: hda:pio, hdb:pio
    ide1: BM-DMA at 0xd008-0xd00f, BIOS settings: hdc:pio, hdd:pio

Probing IDE interface ide0...
hda: PQI IDE DiskOnModule, ATA DISK drive
ENTER via82cxxx_tune_drive
ENTER via_set_drive
ENTER ide_config_drive_speed
hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }
hda: set_drive_speed_status: error=0x04 { DriveStatusError } EXIT ide_config_drive_speed error
ENTER via_set_speed
EXIT via_set_speed
EXIT via_set_drive
EXIT via82cxxx_tune_drive pio == 255
ENTER via82cxxx_ide_dma_check
ENTER via_set_drive
ENTER ide_config_drive_speed
hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }
hda: set_drive_speed_status: error=0x04 { DriveStatusError } EXIT ide_config_drive_speed error
ENTER via_set_speed
EXIT via_set_speed
EXIT via_set_drive
EXIT via82cxxx_ide_dma_check
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
hda: max request size: 128KiB
hda: 128000 sectors (65 MB) w/1KiB Cache, CHS=500/8/32
hda: hda1 hda2

Regards.

John Sigler

author

2007-08-30 15:11 UTC #5 lore raw

Quoted 62 lines · John Sigler

Quoted 8 lines · Petr Vandrovec
Quoted 5 lines · John Sigler
Quoted 1 line · Alan Cox
Basically your dinosaur is working correctly.
What do the warnings mean? :-)
Quoted 7 lines
That your drive does not support set transfer mode/speed command at all, or that value which kernel tried is not supported by the drive...
I would guess that some contractor wrote firmware for device for PQI in one day for $100, and before that somebody else designed ATA-SD bridge for PQI for another $100.
I guess that these two printk()s happen because drive claims to support pio0,1,2 - so Linux tries pio2, drive refuses, Linux tries pio1, drive refuses, and finally as pio0 is default, that one gets used. Which is more or less confirmed by having no '*' sign in front of any pio - with "real" drives you should see '*' in front of one of listed dma/pio modes.
You should ask reseller how they can ship drive which does not conform to any ATA standard...
I took drivers/ide/pci/via82cxxx.c and sprinkled ENTER/EXIT printk's.
http://lxr.linux.no/source/drivers/ide/pci/via82cxxx.c
via82cxxx_tune_drive() and via82cxxx_ide_dma_check() both call via_set_drive() which calls ide_config_drive_speed().
http://lxr.linux.no/source/drivers/ide/ide-iops.c#L769
  if (error)
  {
    (void) ide_dump_status(drive, "set_drive_speed_status", stat);
    printk(KERN_INFO "EXIT %s error\n", __func__);
    return error;
  }
Does someone know why error is not set to 0?
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: IDE controller at PCI slot 0000:00:07.1
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
VP_IDE: VIA vt82c686b (rev 40) IDE UDMA100 controller on pci0000:00:07.1
    ide0: BM-DMA at 0xd000-0xd007, BIOS settings: hda:pio, hdb:pio
    ide1: BM-DMA at 0xd008-0xd00f, BIOS settings: hdc:pio, hdd:pio
Probing IDE interface ide0...
hda: PQI IDE DiskOnModule, ATA DISK drive
ENTER via82cxxx_tune_drive
ENTER via_set_drive
ENTER ide_config_drive_speed
hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }
hda: set_drive_speed_status: error=0x04 { DriveStatusError } EXIT ide_config_drive_speed error
ENTER via_set_speed
EXIT via_set_speed
EXIT via_set_drive
EXIT via82cxxx_tune_drive pio == 255
ENTER via82cxxx_ide_dma_check
ENTER via_set_drive
ENTER ide_config_drive_speed
hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }
hda: set_drive_speed_status: error=0x04 { DriveStatusError } EXIT ide_config_drive_speed error
ENTER via_set_speed

Quoted 8 lines

EXIT via_set_speed
EXIT via_set_drive
EXIT via82cxxx_ide_dma_check
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
hda: max request size: 128KiB
hda: 128000 sectors (65 MB) w/1KiB Cache, CHS=500/8/32
hda: hda1 hda2

According to my supplier, herre is the data sheet for the DOMs:
http://www.pqimemory.com/documents/domdata.pdf

PIO mode 2 is mentioned. Even DMA seems to be supported. Or am I mistaken?

Could there be a bug in my south bridge?

Regards.

Alan Cox

2007-08-30 23:22 UTC #6 lore raw

Quoted 4 lines

PIO mode 2 is mentioned. Even DMA seems to be supported. Or am I mistaken?
Could there be a bug in my south bridge?

Nothing there about DMA support.

The data sheet says the media can only do 4.1MB/second which is consistent with only needing PIO2 (actually its far slower than PIO2)

John Sigler

author

2007-08-31 08:23 UTC #7 lore raw

Quoted 9 lines · Alan Cox

Quoted 5 lines · John Sigler
http://www.pqimemory.com/documents/domdata.pdf
PIO mode 2 is mentioned. Even DMA seems to be supported. Or am I mistaken?
Could there be a bug in my south bridge?
Nothing there about DMA support.

cf. document's page 12.

DMACK- (DMA acknowledge)

This signal shall be used by the host in response to DMARQ to initiate DMA transfers.

DMARQ (DMA request)

This signal, used for DMA data transfer between host and device, shall be asserted by the device when it is ready to transfer data to or from the host. The direction of data transfer is controlled by DIOR- and DIOW-. This signal is used in a handshake manner with DMACK- i.e., the device shall wait until the host asserts DMACK- before negating DMARQ, and re-asserting DMARQ if there is more data to transfer.

This line shall be released (high impedance state) whenever the device is not selected or is selected and no DMA command is in progress. When enabled by DMA transfer, it shall be driven high and low by the device.

When a DMA operation is enabled, CS0- and CS1- shall not be asserted and transfers shall be 16-bits wide.

I took the above to mean the device was designed to support DMA. Where did I err?

Quoted 2 lines

The data sheet says the media can only do 4.1MB/second which is consistent with only needing PIO2 (actually it's far slower than PIO2)

Is such a slow speed typical of DOMs sold today?

Or do DOMs sold today support DMA bus mastering, much higher interface rates, and much higher sustained throughput?

Regards.

n

2007-08-31 09:04 UTC #8 lore raw

PROBLEM: kernel 2.6.22.6 pata_pdc202xx_old.c limiting to UDMA/33 instead of UDMA/100 (UPDATED 2.6.22.6)

Update with kernel 2.6.22.6 i am getting this error now ata2.00: ATA-6: ST3120026A, 3.06, max UDMA/100

here is the new error.
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen ata2.01: cmd ca/00:00:25:9c:fc/00:00:00:00:00/f6 tag 0 cdb 0x0 data 131072 out

        res 40/00:00:3f:00:00/00:00:00:00:00/f0 Emask 0x4 (timeout)

ata2: port is slow to respond, please be patient (Status 0xfe)
ata2: device not ready (errno=-16), forcing hardreset
ata2: soft resetting port
ata2.01: configured for UDMA/25
ata2: EH complete

here is dmseg output
[sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sde: sde1
sd 3:0:0:0: [sde] Attached SCSI disk
scsi 3:0:1:0: Direct-Access ATA Maxtor 6Y120L0 YAR4 PQ: 0 ANSI: 5
sd 3:0:1:0: [sdf] 240121728 512-byte hardware sectors (122942 MB)
sd 3:0:1:0: [sdf] Write Protect is off
sd 3:0:1:0: [sdf] Mode Sense: 00 3a 00 00
sd 3:0:1:0: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sd 3:0:1:0: [sdf] 240121728 512-byte hardware sectors (122942 MB)
sd 3:0:1:0: [sdf] Write Protect is off
sd 3:0:1:0: [sdf] Mode Sense: 00 3a 00 00
sd 3:0:1:0: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdf: sdf1
sd 3:0:1:0: [sdf] Attached SCSI disk
usbmon: debugfs is not available
USB Universal Host Controller Interface driver v3.0
ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11
PCI: setting IRQ 11 as level-triggered
ACPI: PCI Interrupt 0000:00:04.2[D] -> Link [LNKC] -> GSI 11 (level, low) -> IRQ 11 uhci_hcd 0000:00:04.2: UHCI Host Controller
uhci_hcd 0000:00:04.2: new USB bus registered, assigned bus number 1 uhci_hcd 0000:00:04.2: irq 11, io base 0x0000d400
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:04.3[D] -> Link [LNKC] -> GSI 11 (level, low) -> IRQ 11 uhci_hcd 0000:00:04.3: UHCI Host Controller
uhci_hcd 0000:00:04.3: new USB bus registered, assigned bus number 2 uhci_hcd 0000:00:04.3: irq 11, io base 0x0000d000
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1
PNP: PS/2 controller doesn't have AUX irq; using default 12
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60,0x64 irq 12
mice: PS/2 mouse device common for all mice
device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: [email protected]
input: AT Translated Set 2 keyboard as /class/input/input2
usb 1-1: new low speed USB device using uhci_hcd and address 2
usb 1-1: configuration #1 chosen from 1 choice
usb 1-2: new low speed USB device using uhci_hcd and address 3
usb 1-2: configuration #1 chosen from 1 choice
usbcore: registered new interface driver hiddev
hiddev96: USB HID v1.10 Device [CPS UPS AE550] on usb-0000:00:04.2-1
input: Logitech USB Receiver as /class/input/input3
input: USB HID v1.10 Mouse [Logitech USB Receiver] on usb-0000:00:04.2-2
usbcore: registered new interface driver usbhid drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
Advanced Linux Sound Architecture Driver Version 1.0.14 (Thu May 31 09:03:25 2007 UTC).
ACPI: PCI Interrupt 0000:00:04.5[C] -> Link [LNKB] -> GSI 10 (level, low) -> IRQ 10
PCI: Setting latency timer of device 0000:00:04.5 to 64
ALSA device list:
#0: VIA 82C686A/B rev20 with AD1881A at 0xb800, irq 10
TCP cubic registered
Initializing XFRM netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
Using IPI Shortcut mode
XFS mounting filesystem sdc2
Ending clean XFS mount for filesystem: sdc2
VFS: Mounted root (xfs filesystem) readonly.
Freeing unused kernel memory: 208k freed
sd 0:0:0:0: Attached scsi generic sg0 type 0
sd 1:0:1:0: Attached scsi generic sg1 type 0
sd 2:0:0:0: Attached scsi generic sg2 type 0
sd 2:0:1:0: Attached scsi generic sg3 type 0
sd 3:0:0:0: Attached scsi generic sg4 type 0
sd 3:0:1:0: Attached scsi generic sg5 type 0
parport_pc: VIA 686A/8231 detected
parport_pc: probing current configuration
parport_pc: Current parallel port base: 0x378
parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE]
parport_pc: VIA parallel port: io=0x378, irq=7
r8169 Gigabit Ethernet driver 2.2LK-NAPI loaded
ACPI: PCI Interrupt 0000:00:0f.0[A] -> Link [LNKC] -> GSI 11 (level, low) -> IRQ 11
eth0: RTL8169sb/8110sb at 0xe882c000, 00:14:d1:38:5e:25, IRQ 11
8139too Fast Ethernet driver 0.9.28
ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 5
PCI: setting IRQ 5 as level-triggered
ACPI: PCI Interrupt 0000:00:10.0[A] -> Link [LNKD] -> GSI 5 (level, low) -> IRQ 5
eth1: RealTek RTL8139 at 0x8800, 00:40:05:3a:15:c4, IRQ 5
eth1: Identified 8139 chip type 'RTL-8100B/8139D'
via686a 0000:00:04.4: base address not set - upgrade BIOS or use force_addr=0xaddr Adding 390560k swap on /dev/sdc1. Priority:-1 extents:1 across:390560k XFS mounting filesystem sdc3
Ending clean XFS mount for filesystem: sdc3
XFS mounting filesystem sdc4
Ending clean XFS mount for filesystem: sdc4
XFS mounting filesystem sdd1
Ending clean XFS mount for filesystem: sdd1
XFS mounting filesystem sde1
Ending clean XFS mount for filesystem: sde1
XFS mounting filesystem sdf1
Ending clean XFS mount for filesystem: sdf1
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
ata2.01: (BMDMA stat 0x4)
ata2.01: cmd ca/00:01:3f:00:00/00:00:00:00:00/f0 tag 0 cdb 0x0 data 512 out

        res 51/84:00:3f:00:00/00:00:00:00:00/f0 Emask 0x10 (ATA bus error)

ata2: soft resetting port
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 ata2.01: (BMDMA stat 0x4)
ata2.01: cmd ca/00:01:3f:00:00/00:00:00:00:00/f0 tag 0 cdb 0x0 data 512 out

        res 51/84:00:3f:00:00/00:00:00:00:00/f0 Emask 0x10 (ATA bus error)

ata2: soft resetting port
ata2.01: configured for UDMA/33
ata2: EH complete
sd 1:0:1:0: [sdb] 234441648 512-byte hardware sectors (120034 MB) ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 ata2.01: (BMDMA stat 0x4)
ata2.01: cmd ca/00:01:3f:00:00/00:00:00:00:00/f0 tag 0 cdb 0x0 data 512 out

        res 51/84:00:3f:00:00/00:00:00:00:00/f0 Emask 0x10 (ATA bus error)

ata2: soft resetting port
ata2.01: configured for UDMA/33
ata2: EH complete
sd 1:0:1:0: [sdb] Write Protect is off
sd 1:0:1:0: [sdb] Mode Sense: 00 3a 00 00
ata2.01: limiting speed to UDMA/25:PIO4
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 ata2.01: (BMDMA stat 0x4)
ata2.01: cmd ca/00:01:3f:00:00/00:00:00:00:00/f0 tag 0 cdb 0x0 data 512 out

        res 51/84:00:3f:00:00/00:00:00:00:00/f0 Emask 0x10 (ATA bus error)

ata2: soft resetting port
ata2.01: configured for UDMA/25
ata2: EH complete
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 ata2.01: (BMDMA stat 0x4)
ata2.01: cmd ca/00:01:3f:00:00/00:00:00:00:00/f0 tag 0 cdb 0x0 data 512 out

        res 51/84:00:3f:00:00/00:00:00:00:00/f0 Emask 0x10 (ATA bus error)

ata2: soft resetting port
ata2.01: configured for UDMA/25
ata2: EH complete
sd 1:0:1:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
ata2.01: (BMDMA stat 0x4)
ata2.01: cmd ca/00:01:3f:00:00/00:00:00:00:00/f0 tag 0 cdb 0x0 data 512 out

        res 51/84:00:3f:00:00/00:00:00:00:00/f0 Emask 0x10 (ATA bus error)

ata2: soft resetting port
ata2.01: configured for UDMA/25
sd 1:0:1:0: [sdb] Result: hostbyte=0x00 driverbyte=0x08 sd 1:0:1:0: [sdb] Sense Key : 0xb [current] [descriptor] Descriptor sense data with sense descriptors (in hex):

       72 0b 47 00 00 00 00 0c 00 0a 80 00 00 00 00 00
       00 00 00 3f

sd 1:0:1:0: [sdb] ASC=0x47 ASCQ=0x0
end_request: I/O error, dev sdb, sector 63
ata2: EH complete
sd 1:0:1:0: [sdb] 234441648 512-byte hardware sectors (120034 MB) Filesystem "sdb1": Disabling barriers, trial barrier write failed
sd 1:0:1:0: [sdb] Write Protect is off
sd 1:0:1:0: [sdb] Mode Sense: 00 3a 00 00
XFS mounting filesystem sdb1
sd 1:0:1:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sd 1:0:1:0: [sdb] 234441648 512-byte hardware sectors (120034 MB)
sd 1:0:1:0: [sdb] Write Protect is off
sd 1:0:1:0: [sdb] Mode Sense: 00 3a 00 00
sd 1:0:1:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
ata2.01: cmd ca/00:00:25:9c:fc/00:00:00:00:00/f6 tag 0 cdb 0x0 data 131072 out

        res 40/00:00:3f:00:00/00:00:00:00:00/f0 Emask 0x4 (timeout)

ata2: port is slow to respond, please be patient (Status 0xfe)
ata2: device not ready (errno=-16), forcing hardreset
ata2: soft resetting port
ata2.01: configured for UDMA/25
ata2: EH complete
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen ata2.01: cmd ca/00:00:25:9c:fc/00:00:00:00:00/f6 tag 0 cdb 0x0 data 131072 out

        res 40/00:00:3f:00:00/00:00:00:00:00/f0 Emask 0x4 (timeout)

        res 40/00:00:3f:00:00/00:00:00:00:00/f0 Emask 0x4 (timeout)

        res 40/00:00:3f:00:00/00:00:00:00:00/f0 Emask 0x4 (timeout)

        res 40/00:00:3f:00:00/00:00:00:00:00/f0 Emask 0x4 (timeout)

        res 40/00:00:3f:00:00/00:00:00:00:00/f0 Emask 0x4 (timeout)

ata2: port is slow to respond, please be patient (Status 0xfe)
ata2: device not ready (errno=-16), forcing hardreset
ata2: soft resetting port
ata2.01: configured for UDMA/25
sd 1:0:1:0: [sdb] Result: hostbyte=0x00 driverbyte=0x08 sd 1:0:1:0: [sdb] Sense Key : 0xb [current] [descriptor] Descriptor sense data with sense descriptors (in hex):

       72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
       00 00 00 3f

sd 1:0:1:0: [sdb] ASC=0x0 ASCQ=0x0
end_request: I/O error, dev sdb, sector 117218341
ata2: EH complete
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen ata2.01: cmd ca/00:00:25:9d:fc/00:00:00:00:00/f6 tag 0 cdb 0x0 data 131072 out

        res 40/00:00:3f:00:00/00:00:00:00:00/f0 Emask 0x4 (timeout)

ata2: port is slow to respond, please be patient (Status 0xfe)
ata2: device not ready (errno=-16), forcing hardreset
ata2: soft resetting port
ata2.01: configured for UDMA/25
ata2: EH complete
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen ata2.01: cmd ca/00:00:25:9d:fc/00:00:00:00:00/f6 tag 0 cdb 0x0 data 131072 out

        res 40/00:00:3f:00:00/00:00:00:00:00/f0 Emask 0x4 (timeout)

ata2: port is slow to respond, please be patient (Status 0xfe)
ata2: device not ready (errno=-16), forcing hardreset
ata2: soft resetting port
ata2.01: configured for UDMA/25
ata2: EH complete
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen ata2.01: cmd ca/00:00:25:9d:fc/00:00:00:00:00/f6 tag 0 cdb 0x0 data 131072 out

        res 40/00:00:3f:00:00/00:00:00:00:00/f0 Emask 0x4 (timeout)

ata2: port is slow to respond, please be patient (Status 0xfe)
ata2: device not ready (errno=-16), forcing hardreset
ata2: soft resetting port
ata2.01: configured for UDMA/25
ata2: EH complete
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen ata2.01: cmd ca/00:00:25:9d:fc/00:00:00:00:00/f6 tag 0 cdb 0x0 data 131072 out

        res 40/00:00:3f:00:00/00:00:00:00:00/f0 Emask 0x4 (timeout)

ata2: port is slow to respond, please be patient (Status 0xfe)
ata2: device not ready (errno=-16), forcing hardreset
ata2: soft resetting port
ata2.01: configured for UDMA/25
ata2: EH complete
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen ata2.01: cmd ca/00:00:25:9d:fc/00:00:00:00:00/f6 tag 0 cdb 0x0 data 131072 out

        res 40/00:00:3f:00:00/00:00:00:00:00/f0 Emask 0x4 (timeout)

ata2: port is slow to respond, please be patient (Status 0xfe)
ata2: device not ready (errno=-16), forcing hardreset
ata2: soft resetting port
ata2.01: configured for UDMA/25
ata2: EH complete
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen ata2.01: cmd ca/00:00:25:9d:fc/00:00:00:00:00/f6 tag 0 cdb 0x0 data 131072 out

        res 40/00:00:3f:00:00/00:00:00:00:00/f0 Emask 0x4 (timeout)

ata2: port is slow to respond, please be patient (Status 0xfe)
ata2: device not ready (errno=-16), forcing hardreset
ata2: soft resetting port
ata2.01: configured for UDMA/25
sd 1:0:1:0: [sdb] Result: hostbyte=0x00 driverbyte=0x08 sd 1:0:1:0: [sdb] Sense Key : 0xb [current] [descriptor] Descriptor sense data with sense descriptors (in hex):

       72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
       00 00 00 3f

sd 1:0:1:0: [sdb] ASC=0x0 ASCQ=0x0
end_request: I/O error, dev sdb, sector 117218597
ata2: EH complete
xfs_force_shutdown(sdb1,0x1) called from line 423 of file fs/xfs/xfs_rw.c. Return address = 0xc020c098 Filesystem "sdb1": I/O Error Detected. Shutting down filesystem: sdb1
Please umount the filesystem, and rectify the problem(s)
I/O error in filesystem ("sdb1") meta-data dev sdb1 block 0x6fc9be6 ("xlog_bwrite") error 5 buf count 262144
XFS: failed to locate log tail
XFS: log mount/recovery failed: error 5
XFS: log mount failed
sd 1:0:1:0: [sdb] 234441648 512-byte hardware sectors (120034 MB)
sd 1:0:1:0: [sdb] Write Protect is off
sd 1:0:1:0: [sdb] Mode Sense: 00 3a 00 00
sd 1:0:1:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 1:0:1:0: [sdb] 234441648 512-byte hardware sectors (120034 MB)
sd 1:0:1:0: [sdb] Write Protect is off
sd 1:0:1:0: [sdb] Mode Sense: 00 3a 00 00
sd 1:0:1:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA XFS mounting filesystem sda1
Ending clean XFS mount for filesystem: sda1
r8169: eth0: link up
eth1: link up, 100Mbps, full-duplex, lpa 0xC5E1
ata1: soft resetting port
ata1.00: configured for UDMA/100
ata1: EH complete
sd 0:0:0:0: [sda] 398297088 512-byte hardware sectors (203928 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
ata2: soft resetting port
ata2.01: configured for UDMA/25
ata2: EH complete
sd 1:0:1:0: [sdb] 234441648 512-byte hardware sectors (120034 MB)
sd 1:0:1:0: [sdb] Write Protect is off
sd 1:0:1:0: [sdb] Mode Sense: 00 3a 00 00
sd 1:0:1:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
ip_tables: (C) 2000-2006 Netfilter Core Team
Netfilter messages via NETLINK v0.30.
nf_conntrack version 0.5.0 (5119 buckets, 40952 max)
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
Capability LSM initialized
eth1: no IPv6 routers present
eth0: no IPv6 routers present
PPP generic driver version 2.4.2
IPv6 over IPv4 tunneling driver
sit0: Disabled Privacy Extensions
ipv6tb: Disabled Privacy Extensions
ip6_tables: (C) 2000-2006 Netfilter Core Team
PPP BSD Compression module registered

Here is my previous post
(not sure if anyone read it im new to mailing lists also ata1 below is ata2 above since i changed it to port 2 so its the same seagate drive.)

hello, with kernel 2.6.22.5 using the new pata_pdc202xx_old driver it doesn't
detect the cable right on this seagate drive (i tried switching ports / cables ...etc)

it detects the maxtor drive fine no matter what port its on, the seagate doesnt detect correctly on either port

ata1.00: ATA-6: ST3120026A, 3.06, max UDMA/100
ata1.00: 234441648 sectors, multi 16: LBA48
ata1.00: limited to UDMA/33 due to 40-wire cable
ata1.00: configured for UDMA/33
ata2.00: ATA-7: Maxtor 6B200R0, max UDMA/133
ata2.00: 398297088 sectors, multi 16: LBA48
ata2.00: configured for UDMA/100

i was searching goolge and i found other uses with the same problem and had seagate drives (maybe the cable detect code is differnt in seagate?)

btw only devices sda and sdb are on the pata_pdc202xx_old card. sdc-g are on the new via driver.

i also get this error about 50 of them
(dmsg cut top output where it had info about the cable error) anyways if you scroll down you will see errors like this
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 ata1.00: (BMDMA stat 0x4)
ata1.00: cmd ca/00:01:3f:00:00/00:00:00:00:00/e0 tag 0 cdb 0x0 data 512 out

        res 51/84:00:3f:00:00/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)

ata1: soft resetting port
ata1.00: configured for UDMA/33
ata1: EH complete ..etc

.... Ends up here

ata1: EH complete
ata1.00: limiting speed to PIO4
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 ata1.00: (BMDMA stat 0x4)
ata1.00: cmd ca/00:00:21:9d:fc/00:00:00:00:00/e6 tag 0 cdb 0x0 data 131072 out

        res 51/84:00:21:9d:fc/00:00:00:00:00/e6 Emask 0x10 (ATA bus error)

ata1: soft resetting port
ata1.00: configured for PIO4 <- pio4 so is it even going lower?
ata1: EH complete

here is most of output from dmsg if you need it.
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
sd 1:0:0:0: [sdb] Attached SCSI disk
pata_via 0000:00:04.1: version 0.3.1
scsi2 : pata_via
scsi3 : pata_via
ata3: PATA max UDMA/66 cmd 0x000101f0 ctl 0x000103f6 bmdma 0x0001d800 irq 14
ata4: PATA max UDMA/66 cmd 0x00010170 ctl 0x00010376 bmdma 0x0001d808 irq 15 ata3.00: ATA-6: Maxtor 5T040H4, TAH71DP0, max UDMA/100
ata3.00: 80043264 sectors, multi 16: LBA
ata3.01: ATA-6: WDC WD800BB-55JKC0, 05.01C05, max UDMA/100 ata3.01: 156301488 sectors, multi 16: LBA
ata3.00: configured for UDMA/66
ata3.01: configured for UDMA/66
ata4.00: ATA-5: MAXTOR 4K080H4, A08.1500, max UDMA/100
ata4.00: 156301488 sectors, multi 16: LBA
ata4.01: ATA-7: Maxtor 6Y120L0, YAR41VW0, max UDMA/133
ata4.01: 240121728 sectors, multi 16: LBA
ata4.00: configured for UDMA/66
ata4.01: configured for UDMA/66
scsi 2:0:0:0: Direct-Access ATA Maxtor 5T040H4 TAH7 PQ: 0 ANSI: 5
sd 2:0:0:0: [sdc] 80043264 512-byte hardware sectors (40982 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] 80043264 512-byte hardware sectors (40982 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 sdc3 sdc4
sd 2:0:0:0: [sdc] Attached SCSI disk
scsi 2:0:1:0: Direct-Access ATA WDC WD800BB-55JK 05.0 PQ: 0 ANSI: 5
sd 2:0:1:0: [sdd] 156301488 512-byte hardware sectors (80026 MB) sd 2:0:1:0: [sdd] Write Protect is off
sd 2:0:1:0: [sdd] Mode Sense: 00 3a 00 00
sd 2:0:1:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 2:0:1:0: [sdd] 156301488 512-byte hardware sectors (80026 MB) sd 2:0:1:0: [sdd] Write Protect is off
sd 2:0:1:0: [sdd] Mode Sense: 00 3a 00 00
sd 2:0:1:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdd: sdd1
sd 2:0:1:0: [sdd] Attached SCSI disk
scsi 3:0:0:0: Direct-Access ATA MAXTOR 4K080H4 A08. PQ: 0 ANSI: 5
sd 3:0:0:0: [sde] 156301488 512-byte hardware sectors (80026 MB) sd 3:0:0:0: [sde] Write Protect is off
sd 3:0:0:0: [sde] Mode Sense: 00 3a 00 00
sd 3:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 3:0:0:0: [sde] 156301488 512-byte hardware sectors (80026 MB) sd 3:0:0:0: [sde] Write Protect is off
sd 3:0:0:0: [sde] Mode Sense: 00 3a 00 00
sd 3:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sde: sde1
sd 3:0:0:0: [sde] Attached SCSI disk
scsi 3:0:1:0: Direct-Access ATA Maxtor 6Y120L0 YAR4 PQ: 0 ANSI: 5
sd 3:0:1:0: [sdf] 240121728 512-byte hardware sectors (122942 MB) sd 3:0:1:0: [sdf] Write Protect is off
sd 3:0:1:0: [sdf] Mode Sense: 00 3a 00 00
sd 3:0:1:0: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 3:0:1:0: [sdf] 240121728 512-byte hardware sectors (122942 MB) sd 3:0:1:0: [sdf] Write Protect is off
sd 3:0:1:0: [sdf] Mode Sense: 00 3a 00 00
sd 3:0:1:0: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdf: sdf1
sd 3:0:1:0: [sdf] Attached SCSI disk
usbmon: debugfs is not available
USB Universal Host Controller Interface driver v3.0
ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11
PCI: setting IRQ 11 as level-triggered
ACPI: PCI Interrupt 0000:00:04.2[D] -> Link [LNKC] -> GSI 11 (level, low) -> IRQ 11
uhci_hcd 0000:00:04.2: UHCI Host Controller
uhci_hcd 0000:00:04.2: new USB bus registered, assigned bus number 1 uhci_hcd 0000:00:04.2: irq 11, io base 0x0000d400
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:04.3[D] -> Link [LNKC] -> GSI 11 (level, low) -> IRQ 11
uhci_hcd 0000:00:04.3: UHCI Host Controller
uhci_hcd 0000:00:04.3: new USB bus registered, assigned bus number 2 uhci_hcd 0000:00:04.3: irq 11, io base 0x0000d000
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1
PNP: PS/2 controller doesn't have AUX irq; using default 12
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60,0x64 irq 12
mice: PS/2 mouse device common for all mice
device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised:
[email protected]
input: AT Translated Set 2 keyboard as /class/input/input2
usb 1-1: new low speed USB device using uhci_hcd and address 2 usb 1-1: configuration #1 chosen from 1 choice
usb 1-2: new low speed USB device using uhci_hcd and address 3 usb 1-2: configuration #1 chosen from 1 choice
usbcore: registered new interface driver hiddev
hiddev96: USB HID v1.10 Device [CPS UPS AE550] on usb-0000:00:04.2-1
input: Logitech USB Receiver as /class/input/input3
input: USB HID v1.10 Mouse [Logitech USB Receiver] on usb-0000:00:04.2-2
usbcore: registered new interface driver usbhid drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
Advanced Linux Sound Architecture Driver Version 1.0.14 (Thu May 31 09:03:25 2007 UTC).
ACPI: PCI Interrupt 0000:00:04.5[C] -> Link [LNKB] -> GSI 10 (level, low) -> IRQ 10
PCI: Setting latency timer of device 0000:00:04.5 to 64
ALSA device list:
#0: VIA 82C686A/B rev20 with AD1881A at 0xb800, irq 10
TCP cubic registered
Initializing XFRM netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
Using IPI Shortcut mode
XFS mounting filesystem sdc2
Ending clean XFS mount for filesystem: sdc2
VFS: Mounted root (xfs filesystem) readonly.
Freeing unused kernel memory: 224k freed
8139too Fast Ethernet driver 0.9.28
ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 5
PCI: setting IRQ 5 as level-triggered
ACPI: PCI Interrupt 0000:00:10.0[A] -> Link [LNKD] -> GSI 5 (level, low) -> IRQ 5
eth0: RealTek RTL8139 at 0x8800, 00:40:05:3a:15:c4, IRQ 5
eth0: Identified 8139 chip type 'RTL-8100B/8139D'
r8169 Gigabit Ethernet driver 2.2LK-NAPI loaded
ACPI: PCI Interrupt 0000:00:0f.0[A] -> Link [LNKC] -> GSI 11 (level, low) -> IRQ 11
eth1: RTL8169sb/8110sb at 0xe882c000, 00:14:d1:38:5e:25, IRQ 11
parport_pc: VIA 686A/8231 detected
parport_pc: probing current configuration
parport_pc: Current parallel port base: 0x378
parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE]
parport_pc: VIA parallel port: io=0x378, irq=7
via686a 0000:00:04.4: base address not set - upgrade BIOS or use force_addr=0xaddr
Adding 390560k swap on /dev/sdc1. Priority:-1 extents:1 across:390560k XFS mounting filesystem sdc3
Ending clean XFS mount for filesystem: sdc3
XFS mounting filesystem sdc4
Ending clean XFS mount for filesystem: sdc4
XFS mounting filesystem sdd1
Ending clean XFS mount for filesystem: sdd1
XFS mounting filesystem sde1
Ending clean XFS mount for filesystem: sde1
XFS mounting filesystem sdf1
Ending clean XFS mount for filesystem: sdf1
XFS mounting filesystem sdb1
Ending clean XFS mount for filesystem: sdb1
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 ata1.00: (BMDMA stat 0x4)
ata1.00: cmd ca/00:01:3f:00:00/00:00:00:00:00/e0 tag 0 cdb 0x0 data 512 out

        res 51/84:00:3f:00:00/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)

ata1: soft resetting port
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 ata1.00: (BMDMA stat 0x4)
ata1.00: cmd ca/00:01:3f:00:00/00:00:00:00:00/e0 tag 0 cdb 0x0 data 512 out

        res 51/84:00:3f:00:00/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)

ata1: soft resetting port
ata1.00: configured for UDMA/33
ata1: EH complete
sd 0:0:0:0: [sda] 234441648 512-byte hardware sectors (120034 MB) ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 ata1.00: (BMDMA stat 0x4)
ata1.00: cmd ca/00:01:3f:00:00/00:00:00:00:00/e0 tag 0 cdb 0x0 data 512 out

        res 51/84:00:3f:00:00/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)

ata1: soft resetting port
ata1.00: configured for UDMA/33
ata1: EH complete
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
ata1.00: limiting speed to UDMA/25:PIO4
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 ata1.00: (BMDMA stat 0x4)
ata1.00: cmd ca/00:01:3f:00:00/00:00:00:00:00/e0 tag 0 cdb 0x0 data 512 out

        res 51/84:00:3f:00:00/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)

ata1: soft resetting port
ata1.00: configured for UDMA/25
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 ata1.00: (BMDMA stat 0x4)
ata1.00: cmd ca/00:01:3f:00:00/00:00:00:00:00/e0 tag 0 cdb 0x0 data 512 out

        res 51/84:00:3f:00:00/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)

ata1: soft resetting port
ata1.00: configured for UDMA/25
ata1: EH complete
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 ata1.00: (BMDMA stat 0x4)
ata1.00: cmd ca/00:01:3f:00:00/00:00:00:00:00/e0 tag 0 cdb 0x0 data 512 out

        res 51/84:00:3f:00:00/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)

ata1: soft resetting port
ata1.00: configured for UDMA/25
sd 0:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x08 sd 0:0:0:0: [sda] Sense Key : 0xb [current] [descriptor] Descriptor sense data with sense descriptors (in hex):

       72 0b 47 00 00 00 00 0c 00 0a 80 00 00 00 00 00
       00 00 00 3f

sd 0:0:0:0: [sda] ASC=0x47 ASCQ=0x0
end_request: I/O error, dev sda, sector 63
ata1: EH complete
sd 0:0:0:0: [sda] 234441648 512-byte hardware sectors (120034 MB) Filesystem "sda1": Disabling barriers, trial barrier write failed sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
XFS mounting filesystem sda1
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 0:0:0:0: [sda] 234441648 512-byte hardware sectors (120034 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
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 ata1.00: (BMDMA stat 0x4)
ata1.00: cmd ca/00:00:21:9c:fc/00:00:00:00:00/e6 tag 0 cdb 0x0 data 131072 out

        res 51/84:00:21:9c:fc/00:00:00:00:00/e6 Emask 0x10 (ATA bus error)

ata1: soft resetting port
ata1.00: configured for UDMA/25
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 ata1.00: (BMDMA stat 0x4)
ata1.00: cmd ca/00:00:21:9c:fc/00:00:00:00:00/e6 tag 0 cdb 0x0 data 131072 out

        res 51/84:00:21:9c:fc/00:00:00:00:00/e6 Emask 0x10 (ATA bus error)

ata1: soft resetting port
ata1.00: configured for UDMA/25
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 ata1.00: (BMDMA stat 0x4)
ata1.00: cmd ca/00:00:21:9c:fc/00:00:00:00:00/e6 tag 0 cdb 0x0 data 131072 out

        res 51/84:00:21:9c:fc/00:00:00:00:00/e6 Emask 0x10 (ATA bus error)

ata1: soft resetting port
ata1.00: configured for UDMA/25
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 ata1.00: (BMDMA stat 0x4)
ata1.00: cmd ca/00:00:21:9c:fc/00:00:00:00:00/e6 tag 0 cdb 0x0 data 131072 out

        res 51/84:00:21:9c:fc/00:00:00:00:00/e6 Emask 0x10 (ATA bus error)

ata1: soft resetting port
ata1.00: configured for UDMA/25
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 ata1.00: (BMDMA stat 0x4)
ata1.00: cmd ca/00:00:21:9c:fc/00:00:00:00:00/e6 tag 0 cdb 0x0 data 131072 out

        res 51/84:00:21:9c:fc/00:00:00:00:00/e6 Emask 0x10 (ATA bus error)

ata1: soft resetting port
ata1.00: configured for UDMA/25
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 ata1.00: (BMDMA stat 0x4)
ata1.00: cmd ca/00:00:21:9c:fc/00:00:00:00:00/e6 tag 0 cdb 0x0 data 131072 out

        res 51/84:00:21:9c:fc/00:00:00:00:00/e6 Emask 0x10 (ATA bus error)

       72 0b 47 00 00 00 00 0c 00 0a 80 00 00 00 00 00
       06 fc 9c 21

sd 0:0:0:0: [sda] ASC=0x47 ASCQ=0x0
end_request: I/O error, dev sda, sector 117218337
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 ata1.00: (BMDMA stat 0x4)
ata1.00: cmd ca/00:00:21:9d:fc/00:00:00:00:00/e6 tag 0 cdb 0x0 data 131072 out

        res 51/84:00:21:9d:fc/00:00:00:00:00/e6 Emask 0x10 (ATA bus error)

ata1: soft resetting port
ata1.00: configured for UDMA/25
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 ata1.00: (BMDMA stat 0x4)
ata1.00: cmd ca/00:00:21:9d:fc/00:00:00:00:00/e6 tag 0 cdb 0x0 data 131072 out

        res 51/84:00:21:9d:fc/00:00:00:00:00/e6 Emask 0x10 (ATA bus error)

ata1: soft resetting port
ata1.00: configured for UDMA/25
ata1: EH complete
ata1.00: limiting speed to PIO4
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 ata1.00: (BMDMA stat 0x4)
ata1.00: cmd ca/00:00:21:9d:fc/00:00:00:00:00/e6 tag 0 cdb 0x0 data 131072 out

        res 51/84:00:21:9d:fc/00:00:00:00:00/e6 Emask 0x10 (ATA bus error)

ata1: soft resetting port
ata1.00: configured for PIO4
ata1: EH complete
sd 0:0:0:0: [sda] 234441648 512-byte hardware sectors (120034 MB) xfs_force_shutdown(sda1,0x1) called from line 423 of file fs/xfs/xfs_rw.c. Return address = 0xc020cea8
Filesystem "sda1": I/O Error Detected. Shutting down filesystem: sda1 Please umount the filesystem, and rectify the problem(s)
I/O error in filesystem ("sda1") meta-data dev sda1 block 0x6fc9be2 ("xlog_bwrite") error 5 buf count 262144
XFS: failed to locate log tail
XFS: log mount/recovery failed: error 5
XFS: log mount failed
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] 234441648 512-byte hardware sectors (120034 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
end of dmesg

there is nothing wrong with the xfs filesystem it mounts fine on the system ide ports so this might be another bug in the new pdc driver xfs_force_shutdown(sda1,0x1) called from line 423 of file fs/xfs/xfs_rw.c. Return address = 0xc020cea8
Filesystem "sda1": I/O Error Detected. Shutting down filesystem: sda1 Please umount the filesystem, and rectify the problem(s)
I/O error in filesystem ("sda1") meta-data dev sda1 block 0x6fc9be2 ("xlog_bwrite") error 5 buf count 262144
XFS: failed to locate log tail
XFS: log mount/recovery failed: error 5
XFS: log mount failed
###

after the kernel finnishes booting i can mount that drive fine (also all the xfs_check xfs_repair ..etc say there is no errors) but i think the drive is in pio4 by the time its done.

the ide old driver seemed to work ok with this drive also the system mainboard ide ports work too.
i tried changing the drive jumpers around and that also didnt help

just to add i tried switching my drives around i moved a wd drive to port 2 of the pdc controller and it worked fine so if a maxtor and a wd drive is hooked up it detects as udma100, this seems to be a error with seagate drives only, and i should also note i tried the seagate on the mainboard chipset (uses the pata_via.c driver) and it detected the seagate fine and set udma 100 on it.

Im not sure whats differnt in pata_via.c and pata_pdc202xx_old.c but somethings wrong with the cable / or mode set in the pdc driver, atleast with seagate drives.

----------------------------------------------------------------------
Finally - A spam blocker that actually works.
http://www.bluebottle.com/tag/4

n

2007-08-31 10:05 UTC #9 lore raw

PROBLEM: kernel 2.6.22.6 pata_pdc202xx_old.c limiting to UDMA/33 instead of UDMA/100 (UPDATED 2.6.22.6)

In reply to John Sigler

Update with kernel 2.6.22.6 i am getting this error now ata2.00: ATA-6: ST3120026A, 3.06, max UDMA/100

here is the new error.
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen ata2.01: cmd ca/00:00:25:9c:fc/00:00:00:00:00/f6 tag 0 cdb 0x0 data 131072 out

        res 40/00:00:3f:00:00/00:00:00:00:00/f0 Emask 0x4 (timeout)

ata2: port is slow to respond, please be patient (Status 0xfe)
ata2: device not ready (errno=-16), forcing hardreset
ata2: soft resetting port
ata2.01: configured for UDMA/25
ata2: EH complete

        res 51/84:00:3f:00:00/00:00:00:00:00/f0 Emask 0x10 (ATA bus error)

        res 51/84:00:3f:00:00/00:00:00:00:00/f0 Emask 0x10 (ATA bus error)

        res 51/84:00:3f:00:00/00:00:00:00:00/f0 Emask 0x10 (ATA bus error)

        res 51/84:00:3f:00:00/00:00:00:00:00/f0 Emask 0x10 (ATA bus error)

        res 51/84:00:3f:00:00/00:00:00:00:00/f0 Emask 0x10 (ATA bus error)

        res 51/84:00:3f:00:00/00:00:00:00:00/f0 Emask 0x10 (ATA bus error)

       72 0b 47 00 00 00 00 0c 00 0a 80 00 00 00 00 00
       00 00 00 3f

        res 40/00:00:3f:00:00/00:00:00:00:00/f0 Emask 0x4 (timeout)

        res 40/00:00:3f:00:00/00:00:00:00:00/f0 Emask 0x4 (timeout)

        res 40/00:00:3f:00:00/00:00:00:00:00/f0 Emask 0x4 (timeout)

        res 40/00:00:3f:00:00/00:00:00:00:00/f0 Emask 0x4 (timeout)

        res 40/00:00:3f:00:00/00:00:00:00:00/f0 Emask 0x4 (timeout)

        res 40/00:00:3f:00:00/00:00:00:00:00/f0 Emask 0x4 (timeout)

ata2: port is slow to respond, please be patient (Status 0xfe)
ata2: device not ready (errno=-16), forcing hardreset
ata2: soft resetting port
ata2.01: configured for UDMA/25
sd 1:0:1:0: [sdb] Result: hostbyte=0x00 driverbyte=0x08 sd 1:0:1:0: [sdb] Sense Key : 0xb [current] [descriptor] Descriptor sense data with sense descriptors (in hex):

       72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
       00 00 00 3f

        res 40/00:00:3f:00:00/00:00:00:00:00/f0 Emask 0x4 (timeout)

ata2: port is slow to respond, please be patient (Status 0xfe)
ata2: device not ready (errno=-16), forcing hardreset
ata2: soft resetting port
ata2.01: configured for UDMA/25
ata2: EH complete
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen ata2.01: cmd ca/00:00:25:9d:fc/00:00:00:00:00/f6 tag 0 cdb 0x0 data 131072 out

        res 40/00:00:3f:00:00/00:00:00:00:00/f0 Emask 0x4 (timeout)

ata2: port is slow to respond, please be patient (Status 0xfe)
ata2: device not ready (errno=-16), forcing hardreset
ata2: soft resetting port
ata2.01: configured for UDMA/25
ata2: EH complete
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen ata2.01: cmd ca/00:00:25:9d:fc/00:00:00:00:00/f6 tag 0 cdb 0x0 data 131072 out

        res 40/00:00:3f:00:00/00:00:00:00:00/f0 Emask 0x4 (timeout)

ata2: port is slow to respond, please be patient (Status 0xfe)
ata2: device not ready (errno=-16), forcing hardreset
ata2: soft resetting port
ata2.01: configured for UDMA/25
ata2: EH complete
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen ata2.01: cmd ca/00:00:25:9d:fc/00:00:00:00:00/f6 tag 0 cdb 0x0 data 131072 out

        res 40/00:00:3f:00:00/00:00:00:00:00/f0 Emask 0x4 (timeout)

ata2: port is slow to respond, please be patient (Status 0xfe)
ata2: device not ready (errno=-16), forcing hardreset
ata2: soft resetting port
ata2.01: configured for UDMA/25
ata2: EH complete
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen ata2.01: cmd ca/00:00:25:9d:fc/00:00:00:00:00/f6 tag 0 cdb 0x0 data 131072 out

        res 40/00:00:3f:00:00/00:00:00:00:00/f0 Emask 0x4 (timeout)

ata2: port is slow to respond, please be patient (Status 0xfe)
ata2: device not ready (errno=-16), forcing hardreset
ata2: soft resetting port
ata2.01: configured for UDMA/25
ata2: EH complete
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen ata2.01: cmd ca/00:00:25:9d:fc/00:00:00:00:00/f6 tag 0 cdb 0x0 data 131072 out

        res 40/00:00:3f:00:00/00:00:00:00:00/f0 Emask 0x4 (timeout)

ata2: port is slow to respond, please be patient (Status 0xfe)
ata2: device not ready (errno=-16), forcing hardreset
ata2: soft resetting port
ata2.01: configured for UDMA/25
sd 1:0:1:0: [sdb] Result: hostbyte=0x00 driverbyte=0x08 sd 1:0:1:0: [sdb] Sense Key : 0xb [current] [descriptor] Descriptor sense data with sense descriptors (in hex):

       72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
       00 00 00 3f

Here is my previous post
(not sure if anyone read it im new to mailing lists also ata1 below is ata2 above since i changed it to port 2 so its the same seagate drive.)

hello, with kernel 2.6.22.5 using the new pata_pdc202xx_old driver it doesn't
detect the cable right on this seagate drive (i tried switching ports / cables ...etc)

it detects the maxtor drive fine no matter what port its on, the seagate doesnt detect correctly on either port

i was searching goolge and i found other uses with the same problem and had seagate drives (maybe the cable detect code is differnt in seagate?)

btw only devices sda and sdb are on the pata_pdc202xx_old card. sdc-g are on the new via driver.

        res 51/84:00:3f:00:00/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)

ata1: soft resetting port
ata1.00: configured for UDMA/33
ata1: EH complete ..etc

.... Ends up here

        res 51/84:00:21:9d:fc/00:00:00:00:00/e6 Emask 0x10 (ATA bus error)

ata1: soft resetting port
ata1.00: configured for PIO4 <- pio4 so is it even going lower?
ata1: EH complete

        res 51/84:00:3f:00:00/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)

        res 51/84:00:3f:00:00/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)

        res 51/84:00:3f:00:00/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)

        res 51/84:00:3f:00:00/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)

        res 51/84:00:3f:00:00/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)

        res 51/84:00:3f:00:00/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)

       72 0b 47 00 00 00 00 0c 00 0a 80 00 00 00 00 00
       00 00 00 3f

        res 51/84:00:21:9c:fc/00:00:00:00:00/e6 Emask 0x10 (ATA bus error)

ata1: soft resetting port
ata1.00: configured for UDMA/25
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 ata1.00: (BMDMA stat 0x4)
ata1.00: cmd ca/00:00:21:9c:fc/00:00:00:00:00/e6 tag 0 cdb 0x0 data 131072 out

        res 51/84:00:21:9c:fc/00:00:00:00:00/e6 Emask 0x10 (ATA bus error)

ata1: soft resetting port
ata1.00: configured for UDMA/25
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 ata1.00: (BMDMA stat 0x4)
ata1.00: cmd ca/00:00:21:9c:fc/00:00:00:00:00/e6 tag 0 cdb 0x0 data 131072 out

        res 51/84:00:21:9c:fc/00:00:00:00:00/e6 Emask 0x10 (ATA bus error)

ata1: soft resetting port
ata1.00: configured for UDMA/25
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 ata1.00: (BMDMA stat 0x4)
ata1.00: cmd ca/00:00:21:9c:fc/00:00:00:00:00/e6 tag 0 cdb 0x0 data 131072 out

        res 51/84:00:21:9c:fc/00:00:00:00:00/e6 Emask 0x10 (ATA bus error)

ata1: soft resetting port
ata1.00: configured for UDMA/25
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 ata1.00: (BMDMA stat 0x4)
ata1.00: cmd ca/00:00:21:9c:fc/00:00:00:00:00/e6 tag 0 cdb 0x0 data 131072 out

        res 51/84:00:21:9c:fc/00:00:00:00:00/e6 Emask 0x10 (ATA bus error)

ata1: soft resetting port
ata1.00: configured for UDMA/25
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 ata1.00: (BMDMA stat 0x4)
ata1.00: cmd ca/00:00:21:9c:fc/00:00:00:00:00/e6 tag 0 cdb 0x0 data 131072 out

        res 51/84:00:21:9c:fc/00:00:00:00:00/e6 Emask 0x10 (ATA bus error)

       72 0b 47 00 00 00 00 0c 00 0a 80 00 00 00 00 00
       06 fc 9c 21

        res 51/84:00:21:9d:fc/00:00:00:00:00/e6 Emask 0x10 (ATA bus error)

ata1: soft resetting port
ata1.00: configured for UDMA/25
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 ata1.00: (BMDMA stat 0x4)
ata1.00: cmd ca/00:00:21:9d:fc/00:00:00:00:00/e6 tag 0 cdb 0x0 data 131072 out

        res 51/84:00:21:9d:fc/00:00:00:00:00/e6 Emask 0x10 (ATA bus error)

        res 51/84:00:21:9d:fc/00:00:00:00:00/e6 Emask 0x10 (ATA bus error)

after the kernel finnishes booting i can mount that drive fine (also all the xfs_check xfs_repair ..etc say there is no errors) but i think the drive is in pio4 by the time its done.

the ide old driver seemed to work ok with this drive also the system mainboard ide ports work too.
i tried changing the drive jumpers around and that also didnt help

Im not sure whats differnt in pata_via.c and pata_pdc202xx_old.c but somethings wrong with the cable / or mode set in the pdc driver, atleast with seagate drives.

----------------------------------------------------------------------
Finally - A spam blocker that actually works.
http://www.bluebottle.com/tag/4

Sergei Shtylyov

2007-09-01 14:55 UTC #10 lore raw

Re: PROBLEM: kernel 2.6.22.6 pata_pdc202xx_old.c limiting to UDMA/33 instead of UDMA/100 (UPDATED 2.6.22.6)

Dear n:

Please do *not* follow-up to a completely inderended thread. Start your
own, please. :-/

Quoted 2 lines

Update with kernel 2.6.22.6 i am getting this error now ata2.00: ATA-6: ST3120026A, 3.06, max UDMA/100

Gathering courage and reply to libata bug report -- I'm more of the
drivers/ide/ guy with some SCSI background too... :-)

Quoted 3 lines

here is the new error.
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen ata2.01: cmd ca/00:00:25:9c:fc/00:00:00:00:00/f6 tag 0 cdb 0x0 data

That was an attempt to read 1 sector from LBA 0xfc9c25 of rhe drive #1...

Quoted 6 lines

131072 out
        res 40/00:00:3f:00:00/00:00:00:00:00/f0 Emask 0x4 (timeout)
ata2: port is slow to respond, please be patient (Status 0xfe)
ata2: device not ready (errno=-16), forcing hardreset
ata2: soft resetting port
ata2.01: configured for UDMA/25

    Whee! :-)

Quoted 3 lines

ata2: EH complete
here is dmseg output

[...]

Quoted 5 lines

parport_pc: Current parallel port base: 0x378
parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE]
parport_pc: VIA parallel port: io=0x378, irq=7
r8169 Gigabit Ethernet driver 2.2LK-NAPI loaded
ACPI: PCI Interrupt 0000:00:0f.0[A] -> Link [LNKC] -> GSI 11 (level, low) -> IRQ 11

Quoted 8 lines

eth0: RTL8169sb/8110sb at 0xe882c000, 00:14:d1:38:5e:25, IRQ 11 8139too Fast Ethernet driver 0.9.28
ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 5
PCI: setting IRQ 5 as level-triggered
ACPI: PCI Interrupt 0000:00:10.0[A] -> Link [LNKD] -> GSI 5 (level, low) -> IRQ 5
eth1: RealTek RTL8139 at 0x8800, 00:40:05:3a:15:c4, IRQ 5
eth1: Identified 8139 chip type 'RTL-8100B/8139D'

RTL8139 are PoS chips (unless it's 8139D probably)... :-)

Quoted 1 line

via686a 0000:00:04.4: base address not set - upgrade BIOS or use force_addr=0xaddr

Hmmm, I'd assume that after that DMA wouldn't be possible but...

Quoted 14 lines

Adding 390560k swap on /dev/sdc1. Priority:-1 extents:1 across:390560k XFS mounting filesystem sdc3
Ending clean XFS mount for filesystem: sdc3
XFS mounting filesystem sdc4
Ending clean XFS mount for filesystem: sdc4
XFS mounting filesystem sdd1
Ending clean XFS mount for filesystem: sdd1
XFS mounting filesystem sde1
Ending clean XFS mount for filesystem: sde1
XFS mounting filesystem sdf1
Ending clean XFS mount for filesystem: sdf1
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 ata2.01: (BMDMA stat 0x4)

Quoted 1 line

ata2.01: cmd ca/00:01:3f:00:00/00:00:00:00:00/f0 tag 0 cdb 0x0 data 512 out

That was an attempt to read the 1st sector from LBA 0x3f of the drive...

Quoted 1 line

        res 51/84:00:3f:00:00/00:00:00:00:00/f0 Emask 0x10 (ATA bus error)

... which failed miserably, with UltraDMA CRC error. Hmmm...

Quoted 7 lines

ata2: soft resetting port
ata2.01: configured for UDMA/33
ata2: EH complete
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 ata2.01: (BMDMA stat 0x4)
ata2.01: cmd ca/00:01:3f:00:00/00:00:00:00:00/f0 tag 0 cdb 0x0 data 512 out
        res 51/84:00:3f:00:00/00:00:00:00:00/f0 Emask 0x10 (ATA bus error)

... same sh!t happened again at UDNA/33 presumbly...

Quoted 8 lines

ata2: soft resetting port
ata2.01: configured for UDMA/33
ata2: EH complete
sd 1:0:1:0: [sdb] 234441648 512-byte hardware sectors (120034 MB) ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 ata2.01: (BMDMA stat 0x4)
ata2.01: cmd ca/00:01:3f:00:00/00:00:00:00:00/f0 tag 0 cdb 0x0 data 512 out
        res 51/84:00:3f:00:00/00:00:00:00:00/f0 Emask 0x10 (ATA bus error)

But the DMA write failed again with the same CRC error...

Quoted 10 lines

ata2: soft resetting port
ata2.01: configured for UDMA/33
ata2: EH complete
sd 1:0:1:0: [sdb] Write Protect is off
sd 1:0:1:0: [sdb] Mode Sense: 00 3a 00 00
ata2.01: limiting speed to UDMA/25:PIO4
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 ata2.01: (BMDMA stat 0x4)
ata2.01: cmd ca/00:01:3f:00:00/00:00:00:00:00/f0 tag 0 cdb 0x0 data 512 out
        res 51/84:00:3f:00:00/00:00:00:00:00/f0 Emask 0x10 (ATA bus error)

... and again.

Quoted 7 lines

ata2: soft resetting port
ata2.01: configured for UDMA/25
ata2: EH complete
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 ata2.01: (BMDMA stat 0x4)
ata2.01: cmd ca/00:01:3f:00:00/00:00:00:00:00/f0 tag 0 cdb 0x0 data 512 out
        res 51/84:00:3f:00:00/00:00:00:00:00/f0 Emask 0x10 (ATA bus error)

... and again, even with UDMA 25.

Quoted 8 lines

ata2: soft resetting port
ata2.01: configured for UDMA/25
ata2: EH complete
sd 1:0:1:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
ata2.01: (BMDMA stat 0x4)
ata2.01: cmd ca/00:01:3f:00:00/00:00:00:00:00/f0 tag 0 cdb 0x0 data 512 out
        res 51/84:00:3f:00:00/00:00:00:00:00/f0 Emask 0x10 (ATA bus error)

Bug is quite persistent... something's up!

Quoted 9 lines

ata2: soft resetting port
ata2.01: configured for UDMA/25
sd 1:0:1:0: [sdb] Result: hostbyte=0x00 driverbyte=0x08 sd 1:0:1:0: [sdb] Sense Key : 0xb [current] [descriptor] Descriptor sense data with sense descriptors (in hex):
       72 0b 47 00 00 00 00 0c 00 0a 80 00 00 00 00 00
       00 00 00 3f
sd 1:0:1:0: [sdb] ASC=0x47 ASCQ=0x0
end_request: I/O error, dev sdb, sector 63

Yeah, 63 == 0x3f.

Quoted 5 lines

ata2: EH complete
sd 1:0:1:0: [sdb] 234441648 512-byte hardware sectors (120034 MB) Filesystem "sdb1": Disabling barriers, trial barrier write failed sd 1:0:1:0: [sdb] Write Protect is off
sd 1:0:1:0: [sdb] Mode Sense: 00 3a 00 00

Quoted 8 lines

XFS mounting filesystem sdb1
sd 1:0:1:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sd 1:0:1:0: [sdb] 234441648 512-byte hardware sectors (120034 MB)
sd 1:0:1:0: [sdb] Write Protect is off
sd 1:0:1:0: [sdb] Mode Sense: 00 3a 00 00
sd 1:0:1:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
ata2.01: cmd ca/00:00:25:9c:fc/00:00:00:00:00/f6 tag 0 cdb 0x0 data 131072 out

Thrying to DMA write 0 sectors at 0xc9c25.

Quoted 1 line

        res 40/00:00:3f:00:00/00:00:00:00:00/f0 Emask 0x4 (timeout)

Hm, 0x40 is not normal a status value... usually, it's 0x50. But it's
alright anyway.

Quoted 2 lines

ata2: port is slow to respond, please be patient (Status 0xfe)
ata2: device not ready (errno=-16), forcing hardreset

Hm...

Quoted 6 lines

ata2: soft resetting port
ata2.01: configured for UDMA/25
ata2: EH complete
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen ata2.01: cmd ca/00:00:25:9c:fc/00:00:00:00:00/f6 tag 0 cdb 0x0 data 131072 out
        res 40/00:00:3f:00:00/00:00:00:00:00/f0 Emask 0x4 (timeout)

Same here.

Quoted 8 lines

ata2: port is slow to respond, please be patient (Status 0xfe)
ata2: device not ready (errno=-16), forcing hardreset
ata2: soft resetting port
ata2.01: configured for UDMA/25
ata2: EH complete
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen ata2.01: cmd ca/00:00:25:9c:fc/00:00:00:00:00/f6 tag 0 cdb 0x0 data 131072 out
        res 40/00:00:3f:00:00/00:00:00:00:00/f0 Emask 0x4 (timeout)

Again strange status after writinng 0 sectors the same LBA.

[The same us repeating over and over again...]

Quoted 4 lines

sd 1:0:1:0: [sdb] Result: hostbyte=0x00 driverbyte=0x08 sd 1:0:1:0: [sdb] Sense Key : 0xb [current] [descriptor] Descriptor sense data with sense descriptors (in hex):
       72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00

Hm, never seen sense format 0x72... :-) The 2nd byte is prolly a sense key ABORTED COMMAND?

Quoted 1 line

       00 00 00 3f

Aha, 0x3f again, this time in the SCSI sense... I've looked thru the SCSI
spacs and found nought aboutthis format. :-(

Quoted 6 lines

sd 1:0:1:0: [sdb] ASC=0x0 ASCQ=0x0
end_request: I/O error, dev sdb, sector 117218341
ata2: EH complete
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen ata2.01: cmd ca/00:00:25:9d:fc/00:00:00:00:00/f6 tag 0 cdb 0x0 data 131072 out
        res 40/00:00:3f:00:00/00:00:00:00:00/f0 Emask 0x4 (timeout)

Then everything happily continues in the same vein but t UDMA/25 mode.
[...]

Quoted 7 lines

Here is my previous post
(not sure if anyone read it im new to mailing lists also ata1 below is ata2 above since i changed it to port 2 so its the same seagate drive.)
hello, with kernel 2.6.22.5 using the new pata_pdc202xx_old driver it doesn't
detect the cable right on this seagate drive (i tried switching ports / cables ...etc)

Probably host side detecton is borked. The drived is residing alone on
that cable?

Quoted 2 lines

it detects the maxtor drive fine no matter what port its on, the seagate doesnt detect correctly on either port

Hrm, then maybe it's indeed device side problem (but IIRC, libata used to
ignore device side reporting)./

Quoted 10 lines

ata1.00: ATA-6: ST3120026A, 3.06, max UDMA/100
ata1.00: 234441648 sectors, multi 16: LBA48
ata1.00: limited to UDMA/33 due to 40-wire cable
ata1.00: configured for UDMA/33
ata2.00: ATA-7: Maxtor 6B200R0, max UDMA/133
ata2.00: 398297088 sectors, multi 16: LBA48
ata2.00: configured for UDMA/100
i was searching goolge and i found other uses with the same problem and had seagate drives (maybe the cable detect code is differnt in seagate?)

Hardly so...

Quoted 1 line

btw only devices sda and sdb are on the pata_pdc202xx_old card.

Not on the same cable?

Quoted 7 lines

i also get this error about 50 of them
(dmsg cut top output where it had info about the cable error) anyways if you scroll down you will see errors like this
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 ata1.00: (BMDMA stat 0x4)
ata1.00: cmd ca/00:01:3f:00:00/00:00:00:00:00/e0 tag 0 cdb 0x0 data 512 out
        res 51/84:00:3f:00:00/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)

Write of single sector 63 fails miserably with UltraDMA CRC... although,
if you're not using UltraDMA at this moment, 0x84 may mean something different: bad/uncortrectable sector.

Quoted 6 lines

ata1: soft resetting port
ata1.00: configured for UDMA/33
ata1: EH complete ..etc
.... Ends up here

Quoted 7 lines

ata1: EH complete
ata1.00: limiting speed to PIO4
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 ata1.00: (BMDMA stat 0x4)
ata1.00: cmd ca/00:00:21:9d:fc/00:00:00:00:00/e6 tag 0 cdb 0x0 data 131072 out
        res 51/84:00:21:9d:fc/00:00:00:00:00/e6 Emask 0x10 (ATA bus error)

Hmmm, the driver had just lied to you saying that it downgraded to PIO4 --
it still issues WRITE DMA command which failed as usual...

Quoted 11 lines

ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 ata1.00: (BMDMA stat 0x4)
ata1.00: cmd ca/00:01:3f:00:00/00:00:00:00:00/e0 tag 0 cdb 0x0 data 512 out
        res 51/84:00:3f:00:00/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)
ata1: soft resetting port
ata1.00: configured for UDMA/33
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 ata1.00: (BMDMA stat 0x4)
ata1.00: cmd ca/00:01:3f:00:00/00:00:00:00:00/e0 tag 0 cdb 0x0 data 512 out
        res 51/84:00:3f:00:00/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)

"Then it strted all over again..."

Quoted 8 lines

ata1: soft resetting port
ata1.00: configured for UDMA/25
sd 0:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x08 sd 0:0:0:0: [sda] Sense Key : 0xb [current] [descriptor] Descriptor sense data with sense descriptors (in hex):
       72 0b 47 00 00 00 00 0c 00 0a 80 00 00 00 00 00
       00 00 00 3f
sd 0:0:0:0: [sda] ASC=0x47 ASCQ=0x0

Hh, SCSI msgs cleared the forat up for me: byte 1 is a sense key, byte 2
is ASQ (0x47 means SCSI parity error)...

Quoted 18 lines

end_request: I/O error, dev sda, sector 63
ata1: EH complete
sd 0:0:0:0: [sda] 234441648 512-byte hardware sectors (120034 MB) Filesystem "sda1": Disabling barriers, trial barrier write failed sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
XFS mounting filesystem sda1
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 0:0:0:0: [sda] 234441648 512-byte hardware sectors (120034 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
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 ata1.00: (BMDMA stat 0x4)
ata1.00: cmd ca/00:00:21:9c:fc/00:00:00:00:00/e6 tag 0 cdb 0x0 data 131072 out

Quoted 1 line

        res 51/84:00:21:9c:fc/00:00:00:00:00/e6 Emask 0x10 (ATA bus error)

Again failinig DMA write of 0 sectors at LBA 826401...

Quoted 23 lines

ata1: soft resetting port
ata1.00: configured for UDMA/25
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 ata1.00: (BMDMA stat 0x4)
ata1.00: cmd ca/00:00:21:9c:fc/00:00:00:00:00/e6 tag 0 cdb 0x0 data 131072 out
        res 51/84:00:21:9c:fc/00:00:00:00:00/e6 Emask 0x10 (ATA bus error)
ata1: soft resetting port
ata1.00: configured for UDMA/25
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 ata1.00: (BMDMA stat 0x4)
ata1.00: cmd ca/00:00:21:9c:fc/00:00:00:00:00/e6 tag 0 cdb 0x0 data 131072 out
        res 51/84:00:21:9c:fc/00:00:00:00:00/e6 Emask 0x10 (ATA bus error)
ata1: soft resetting port
ata1.00: configured for UDMA/25
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 ata1.00: (BMDMA stat 0x4)
ata1.00: cmd ca/00:00:21:9c:fc/00:00:00:00:00/e6 tag 0 cdb 0x0 data 131072 out

Quoted 6 lines

        res 51/84:00:21:9c:fc/00:00:00:00:00/e6 Emask 0x10 (ATA bus error)
ata1: soft resetting port
ata1.00: configured for UDMA/25
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 ata1.00: (BMDMA stat 0x4)

It means that IDE DMA has signalled an interrupt

Quoted 10 lines

ata1.00: cmd ca/00:00:21:9c:fc/00:00:00:00:00/e6 tag 0 cdb 0x0 data 131072 out
        res 51/84:00:21:9c:fc/00:00:00:00:00/e6 Emask 0x10 (ATA bus error)
ata1: soft resetting port
ata1.00: configured for UDMA/25
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 ata1.00: (BMDMA stat 0x4)
ata1.00: cmd ca/00:00:21:9c:fc/00:00:00:00:00/e6 tag 0 cdb 0x0 data 131072 out

Quoted 8 lines

        res 51/84:00:21:9c:fc/00:00:00:00:00/e6 Emask 0x10 (ATA bus error)
ata1: soft resetting port
ata1.00: configured for UDMA/25
sd 0:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x08 sd 0:0:0:0: [sda] Sense Key : 0xb [current] [descriptor] Descriptor sense data with sense descriptors (in hex):
       72 0b 47 00 00 00 00 0c 00 0a 80 00 00 00 00 00
       06 fc 9c 21

Aha, those last 4 bytes a big-endian address of a requested LBA to write to

Quoted 2 lines

after the kernel finnishes booting i can mount that drive fine (also all the xfs_check xfs_repair ..etc say there is no errors) but i think the drive is in pio4 by the time its done.

From looking at the logs I got a feeling that the speed downgraded didn't
work all the way to PIO...

Quoted 2 lines

the ide old driver seemed to work ok with this drive also the system mainboard ide ports work too.

Aha, thanks! :-)

Quoted 8 lines

i tried changing the drive jumpers around and that also didnt help
just to add i tried switching my drives around i moved a wd drive to port 2 of the pdc controller and it worked fine so if a maxtor and a wd drive is hooked up it detects as udma100, this seems to be a error with seagate drives only, and i should also note i tried the seagate on the mainboard chipset (uses the pata_via.c driver) and it detected the seagate fine and set udma 100 on it.

Yeah, all that is very confusing...

MBR, Sergei

Alan Cox

2007-08-31 11:41 UTC #11 lore raw

In reply to John Sigler

Quoted 5 lines

When a DMA operation is enabled, CS0- and CS1- shall not be asserted and transfers shall be 16-bits wide.
I took the above to mean the device was designed to support DMA. Where did I err?

The bus is specified for DMA, not the device.

Quoted 8 lines

Quoted 3 lines
The data sheet says the media can only do 4.1MB/second which is consistent with only needing PIO2 (actually it's far slower than PIO2)
Is such a slow speed typical of DOMs sold today?
Or do DOMs sold today support DMA bus mastering, much higher interface rates, and much higher sustained throughput?

Most CF is pretty slow but the newer CF cards do DMA and are getting far better.

And yes I'd expect your real time app to deal for 3 or 4mS

(Mind you you'll get 1mS normal operating worst cases off even a fast DMA IDE disk)

A message that is not in the archive (sent off-list or not yet received): [email protected]

John Sigler

author

2007-08-31 08:41 UTC #13 lore raw

Quoted 10 lines · Eric

Quoted 5 lines · John Sigler
According to my supplier, herre is the data sheet for the DOMs:
http://www.pqimemory.com/documents/domdata.pdf
PIO mode 2 is mentioned. Even DMA seems to be supported. Or am I mistaken?
Page 3 states max interface burst speed is 8.3MB/s in PIO2. I wouldn't assume it supports DMA

The reason I suspected DMA support is because I noticed the description of DMACK- (DMA acknowledge) and DMARQ (DMA request).

Quoted 3 lines

Based on the quoted media transfer rates (1.2MB/s write and 4.1MB/s read), DMA would buy you a transfer checksum but probably not much performance, unless your embedded application is CPU bound.

What I fear is that programmed I/O will tie up the CPU and add non-deterministic latency to my real-time apps.

Suppose that an app is waiting for an acknowledgement from a PCI device when the OS suddenly decides it is time to write 4 KB to disk. Typical write rate is quoted as 1.2 MB/s i.e. the write would require at least 3.4 ms to complete.

My fear is that the entire transfer is done in a non-preemptible critical section. In other words, my real-time app would be delayed several milliseconds, which is unacceptable.

Am I mistaken?

Regards.

Sergei Shtylyov

2007-09-01 15:45 UTC #14 lore raw

In reply to John Sigler

Quoted 3 lines · John Sigler

Quoted 3 lines
Quoted 1 line
What do the warnings mean? :-)
That your drive does not support set transfer mode/speed command at

Which is perfectly valid in the original ATA spec.

Quoted 1 line

Quoted 1 line
all, or that value which kernel tried is not supported by the drive...

They just should skip programming the drive in this case, and set its
default speed to the chipset.

Quoted 1 line

Quoted 1 line
I would guess that some contractor wrote firmware for device for PQI in one day for $100, and before that somebody else designed ATA-SD bridge for PQI for another $100.

Hehe.

Quoted 1 line

Quoted 1 line
I guess that these two printk()s happen because drive claims to support pio0,1,2 - so Linux tries pio2, drive refuses, Linux tries

Which it shuldn't do since the drive only indicates its default mode (modes
0-2 aren't included in the PIO support mask -- there's only 3 and 4 there).

Quoted 3 lines

Quoted 3 lines
pio1, drive refuses, and finally as pio0 is default, that one gets used. Which is more or less confirmed by having no '*' sign in front of any pio - with "real" drives you should see '*' in front of one of listed dma/pio modes.
You should ask reseller how they can ship drive which does not conform to any ATA standard...

Doesn't it conform to ATA? :-)

Quoted 7 lines

I took drivers/ide/pci/via82cxxx.c and sprinkled ENTER/EXIT printk's.
http://lxr.linux.no/source/drivers/ide/pci/via82cxxx.c
via82cxxx_tune_drive() and via82cxxx_ide_dma_check() both call via_set_drive() which calls ide_config_drive_speed().
http://lxr.linux.no/source/drivers/ide/ide-iops.c#L769

Quoted 8 lines

  if (error)
  {
    (void) ide_dump_status(drive, "set_drive_speed_status", stat);
    printk(KERN_INFO "EXIT %s error\n", __func__);
    return error;
  }

Does someone know why error is not set to 0?

Why it *does* set to one, you wanted to ask? Because it *does* get set
after a loop above exits.

Quoted 8 lines

Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: IDE controller at PCI slot 0000:00:07.1
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
VP_IDE: VIA vt82c686b (rev 40) IDE UDMA100 controller on pci0000:00:07.1
    ide0: BM-DMA at 0xd000-0xd007, BIOS settings: hda:pio, hdb:pio
    ide1: BM-DMA at 0xd008-0xd00f, BIOS settings: hdc:pio, hdd:pio

Quoted 12 lines

Probing IDE interface ide0...
hda: PQI IDE DiskOnModule, ATA DISK drive
ENTER via82cxxx_tune_drive
ENTER via_set_drive
ENTER ide_config_drive_speed
hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }
hda: set_drive_speed_status: error=0x04 { DriveStatusError } EXIT ide_config_drive_speed error
ENTER via_set_speed
EXIT via_set_speed
EXIT via_set_drive
EXIT via82cxxx_tune_drive pio == 255

255 is PIO auto-tuning request.

Quoted 5 lines

ENTER via82cxxx_ide_dma_check
ENTER via_set_drive
ENTER ide_config_drive_speed
hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }
hda: set_drive_speed_status: error=0x04 { DriveStatusError }

MBR, Sergei

Alan Cox

2007-08-30 13:57 UTC #15 lore raw

In reply to John Sigler

Quoted 3 lines

Buffer size: 1.0kB bytes avail on r/w long: 4
(Assuming an 8-bit byte, 4 bytes = 32 bits)

R/W Long is a different thing.

Quoted 3 lines

When you say "the current libata IDE" do you mean PATA_VIA (in my case)? I've avoided this driver because it is marked EXPERIMENTAL. Would there be any benefit in using it over the legacy ATA/MFM/RLL driver?

Just less warning messages

Quoted 3 lines

Quoted 1 line
Basically your dinosaur is working correctly.
What do the warnings mean? :-)

Old IDE wrongly tries to issue a set features command for PIO2 to the device. It rejects it and old IDE carries on happy

Sergei Shtylyov

2007-08-31 20:20 UTC #16 lore raw

In reply to Alan Cox

Quoted 8 lines · Alan Cox

Quoted 2 lines
Standards:
Likely used: 1
Prehistory
Quoted 1 line
LBA, IORDY not likely
No DMA, nothing above PIO2

Cool! :-)

Quoted 5 lines

Quoted 3 lines
Buffer type: 0002: dual port, multi-sector
Buffer size: 1.0kB bytes avail on r/w long: 4
Cannot perform double-word IO
Can't even do double word I/O

I have alwayas wondered what the drive's part in 32-bit I/O... this seems
to be controller's problem exclusively. B-)

WBR, Sergei

Sergei Shtylyov

2007-09-01 15:35 UTC #17 lore raw

In reply to John Sigler

Hello.

Quoted 4 lines · John Sigler

When my system boots, I get several set_drive_speed_status errors. (Please see attached dmesg output.)
Can someone explain what they mean? How do I get rid of them?

IDE code attempts to autotune PIO mode and fails at that because your
device is too old (or its manufacturer was too lazy) to support ATA-2 (or EIDE from marketing PoV) is its full glory.

Quoted 1 line

Is there something I need to set in the config? or something I should not have set?

No, it just means that the IDE code is *too young* to support such
pre-EIDE devices. :-D

Quoted 8 lines

Bonus question: is there some way to turn on DMA for hda?
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: IDE controller at PCI slot 0000:00:07.1
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
VP_IDE: VIA vt82c686b (rev 40) IDE UDMA100 controller on pci0000:00:07.1

Quoted 8 lines

    ide0: BM-DMA at 0xd000-0xd007, BIOS settings: hda:pio, hdb:pio
    ide1: BM-DMA at 0xd008-0xd00f, BIOS settings: hdc:pio, hdd:pio
Probing IDE interface ide0...
hda: PQI IDE DiskOnModule, ATA DISK drive
hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }
hda: set_drive_speed_status: error=0x04 { DriveStatusError }
hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }
hda: set_drive_speed_status: error=0x04 { DriveStatusError }

That means that you've managed to find pre-EIDE/ATA hardware which doesn't
support setting arbitrary PIO modes. What's funny is that resently being discussed here, so expect a patch RSN. :-)

Quoted 9 lines

ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
hda: max request size: 128KiB
hda: 128000 sectors (65 MB) w/1KiB Cache, CHS=500/8/32
hda: hda1 hda2
# hdparm -v /dev/hda
/dev/hda:

Quoted 8 lines

 multcount     =  0 (off)
 IO_support    =  1 (32-bit)
 unmaskirq     =  1 (on)
 using_dma     =  0 (off)
 keepsettings  =  0 (off)
 readonly      =  0 (off)
 readahead     = 256 (on)
 geometry      = 500/8/32, sectors = 128000, start = 0

Oh, interesting geometery, and the size too. :-)

Quoted 6 lines

# hdparm -I /dev/hda
/dev/hda:
ATA device, with non-removable media
Model Number: PQI IDE DiskOnModule

That explains it. :-)

Quoted 17 lines

Serial Number: DOM6B00011677
Firmware Revision: ra03.00e
Standards:
Likely used: 1
Configuration:
hard sectored
not MFM encoded
head switch time > 15us
fixed drive
disk xfer rate > 5Mbs
Logical max current
cylinders 500 500
heads 8 8
sectors/track 32 32
--
bytes/track: 0 bytes/sector: 528
CHS current addressable sectors: 128000

Quoted 8 lines

LBA user addressable sectors: 128000
device size with M = 1024*1024: 62 MBytes
device size with M = 1000*1000: 65 MBytes
Capabilities:
LBA, IORDY not likely
Buffer type: 0002: dual port, multi-sector
Buffer size: 1.0kB bytes avail on r/w long: 4
Cannot perform double-word IO

That's generally not the device task (although there probably were IDE
devices with 32-bit data bus?.. :-O

Quoted 3 lines

R/W multiple sector transfer: Max = 1 Current = 0
DMA: not supported
PIO: pio0 pio1 pio2

[the rest of logs didn't show anything particurarly interesting]

MBR, Sergei

John Sigler

author

2007-09-03 13:18 UTC #18 lore raw

Quoted 9 lines · Sergei Shtylyov

Quoted 4 lines · John Sigler
When my system boots, I get several set_drive_speed_status errors. (Please see attached dmesg output.)
Can someone explain what they mean? How do I get rid of them?
IDE code attempts to autotune PIO mode and fails at that because your
device is too old (or its manufacturer was too lazy) to support ATA-2 (or EIDE from marketing PoV) is its full glory.

But the data sheet seems to state the drive supports PIO modes 1 and 2?

Quoted 4 lines

Quoted 1 line
Is there something I need to set in the config? or something I should not have set?
No, it just means that the IDE code is *too young* to support such
pre-EIDE devices. :-D

Wow! This is a device that was purchased only a few months ago...

Quoted 15 lines

Quoted 6 lines
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: IDE controller at PCI slot 0000:00:07.1
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
VP_IDE: VIA vt82c686b (rev 40) IDE UDMA100 controller on pci0000:00:07.1
Quoted 8 lines
    ide0: BM-DMA at 0xd000-0xd007, BIOS settings: hda:pio, hdb:pio
    ide1: BM-DMA at 0xd008-0xd00f, BIOS settings: hdc:pio, hdd:pio
Probing IDE interface ide0...
hda: PQI IDE DiskOnModule, ATA DISK drive
hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }
hda: set_drive_speed_status: error=0x04 { DriveStatusError }
hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }
hda: set_drive_speed_status: error=0x04 { DriveStatusError }

Quoted 2 lines

That means that you've managed to find pre-EIDE/ATA hardware which
doesn't support setting arbitrary PIO modes. What's funny is that recently being discussed here, so expect a patch RSN. :-)

In 2.6.23?

Regards.

Sergei Shtylyov

2007-09-03 13:37 UTC #19 lore raw

Hello.

Quoted 9 lines · John Sigler

Quoted 7 lines
Quoted 4 lines
When my system boots, I get several set_drive_speed_status errors. (Please see attached dmesg output.)
Can someone explain what they mean? How do I get rid of them?
IDE code attempts to autotune PIO mode and fails at that because
your device is too old (or its manufacturer was too lazy) to support ATA-2 (or EIDE from marketing PoV) is its full glory.
But the data sheet seems to state the drive supports PIO modes 1 and 2?

So what? PIO mode != ATA spec version. ATA-1 specified modes 0 thru 2.

Quoted 6 lines

Quoted 4 lines
Quoted 1 line
Is there something I need to set in the config? or something I should not have set?
No, it just means that the IDE code is *too young* to support such
pre-EIDE devices. :-D
Wow! This is a device that was purchased only a few months ago...

I think we'll take care of it soon -- as I said we've discovered pre-EIDE
disk support lately, just before your report...

Quoted 15 lines

Quoted 14 lines
Quoted 14 lines
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: IDE controller at PCI slot 0000:00:07.1
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
VP_IDE: VIA vt82c686b (rev 40) IDE UDMA100 controller on pci0000:00:07.1
    ide0: BM-DMA at 0xd000-0xd007, BIOS settings: hda:pio, hdb:pio
    ide1: BM-DMA at 0xd008-0xd00f, BIOS settings: hdc:pio, hdd:pio
Probing IDE interface ide0...
hda: PQI IDE DiskOnModule, ATA DISK drive
hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }
hda: set_drive_speed_status: error=0x04 { DriveStatusError }
hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }
hda: set_drive_speed_status: error=0x04 { DriveStatusError }

Quoted 4 lines

Quoted 2 lines
That means that you've managed to find pre-EIDE/ATA hardware which
doesn't support setting arbitrary PIO modes. What's funny is that recently being discussed here, so expect a patch RSN. :-)
In 2.6.23?

Yeah, hopefully.
The mode interesting question is how to diable IORDY throrling on host if
a device doesn't have it connected (that was addressed by Alan in libata, IIRC.

Quoted 1 line

Regards.

MBR as well. :-)