sata_sil24 stability and performance

Denys Dmytriyenko

author

2008-02-19 02:09 UTC #0 lore raw

Hi Gurus!

Preamble:

I've been following this list for several months now trying to spot a similar issue or to gain knowledge to resolve mine. I'm pretty sure the problem is with my setup/configuration, but I've been unable to fix it so far. I would be eternally grateful if someone can help me in resolving the issue. Thanks in advance.

Setup:

I'm running a fileserver with array of 10 disks (8 Seagate 500GB 7200.9 and 7200.10 plus 2 Maxtors) on 3 Addonics ADSA4R5 (4-port SATA2 PCI on Sil 3124) cards in JBOD configuration. The host is a little bit outdated and is dual AMD Athlon MP 1900+ on Tyan Tiger MPX (S2466N-4M) with 1GB of RAM. SATA cards are in PCI slots, not PCI-X. Most of the time drives are in standby mode (30min timeout), but it does not make any difference with issues I'm seeing. Filesystem used is XFS and all the disks are shared over NFS. Power supply was originally 550 watt Enermax (should be enough power, according to a wattmeter), but to be sure was replaced to 750 watt Coolermaster. The kernel is currently 2.6.23.9, but I tried many other versions from 2.6.21 to 2.6.24. The system is Gentoo, but the kernel is vanilla.

Issue #1:

I'm seeing lots of resets in the logs for different drives and different exceptions. Sometimes on idle drives, but mostly on those being accessed. Sometimes I can see couple exceptions in a row, but sometimes I don't see any for hours. These are just example exceptions, but I believe I've seen others as well:

ata1: failed to read log page 10h (errno=-2)
ata1.00: exception Emask 0x1 SAct 0x3 SErr 0x0 action 0x0 ata1.00: irq_stat 0x00060002, device error via SDB FIS
ata1.00: cmd 60/80:00:bf:00:00/00:00:00:00:00/40 tag 0 cdb 0x0 data 65536 in

         res 40/00:00:2f:60:38/00:00:3a:00:00/e0 Emask 0x1 (device error)
ata1.00: cmd 60/80:08:3f:00:00/00:00:00:00:00/40 tag 1 cdb 0x0 data 65536 in
         res 40/00:00:2f:60:38/00:00:3a:00:00/e0 Emask 0x1 (device error)

ata1.00: configured for UDMA/100
ata1: EH complete
sd 0:0:0:0: [sda] 976773168 512-byte hardware sectors (500108 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: disabled, read cache: enabled, doesn't support
DPO or FUA

ata12: exception Emask 0x10 SAct 0x0 SErr 0x80000 action 0x2 frozen
ata12: irq_stat 0x01100010, PHY RDY changed
ata12: soft resetting port
ata12: softreset failed (timeout)
ata12: hard resetting port
ata12: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata12.00: configured for UDMA/100
ata12: EH complete
sd 11:0:0:0: [sdj] 976773168 512-byte hardware sectors (500108 MB) sd 11:0:0:0: [sdj] Write Protect is off
sd 11:0:0:0: [sdj] Mode Sense: 00 3a 00 00
sd 11:0:0:0: [sdj] Write cache: enabled, read cache: enabled, doesn't support
DPO or FUA

I'm not sure how critical are those. The side effect of those resets is loosing my standby timeout settings. But I'm rather worried about drives operating optimally and the integrity of my data. Therefore any failure or exception message in the logs is considered bad and means something is wrong and needs attention. Please help me understand/resolve those exceptions.

Issue #2:

I am also having a performance issue with sata_sil24. I can read data at speeds up to 30 MB/s but write only at speeds around 15 MB/s. When I used Supermicro 8-port sata_mv card, I was able to get speeds at around 40-50 MB/s. Unfortunatelly, sata_mv was not stable at that time and I had to replace it with what was claimed to be the most supported SATA2 chipset under Linux - sata_sil24... I bet the problem is with my setup, but I cannot figure out where or how to fix it.

"hdparm -t" reports speeds in the area of 60-80 MB/s though.

What I find strange is that the host controller is only recognized as UDMA/100 and all the drives even though they are UDMA/133 configured for UDMA/100.

Another strange thing is that all the disks are configured for 16-bit IO_support and cannot be changed to 32-bit:

/dev/sda:

 IO_support    =  0 (default 16-bit)
 readonly      =  0 (off)
 readahead     = 256 (on)
 geometry      = 60801/255/63, sectors = 976773168, start = 0

And one more thing - both Maxtor drives have their write cache disabled by default, unlike Seagate drives. Should I be worried about it?

The bootup sequence and lspci dump are attached. Please note there is HPT374 2-channel IDE RAID device in the logs, which runs a small RAID5 array, but I tried w/o it before and had same issues.

I'd really appreciate if anybody can help me resolve my problems. Thanks in advance!

Regards,
Denys

Linux version 2.6.23.9 (root@gandalf) (gcc version 3.4.6 (Gentoo 3.4.6-r2, ssp-3.4.6-1.0, pie-8.7.10)) #1 SMP Wed Dec 5 13:18:48 EST 2007 BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 0000000000096c00 (usable)
BIOS-e820: 0000000000096c00 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000ce000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000003fef0000 (usable)
BIOS-e820: 000000003fef0000 - 000000003feff000 (ACPI data)
BIOS-e820: 000000003feff000 - 000000003ff00000 (ACPI NVS)
BIOS-e820: 000000003ff00000 - 000000003ff80000 (usable)
BIOS-e820: 000000003ff80000 - 0000000040000000 (reserved)
BIOS-e820: 00000000fec00000 - 00000000fec04000 (reserved)
BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved)
127MB HIGHMEM available.
896MB LOWMEM available.
found SMP MP-table at 000f7170
Entering add_active_range(0, 0, 262016) 0 entries of 256 used
Zone PFN ranges:
DMA 0 -> 4096
Normal 4096 -> 229376
HighMem 229376 -> 262016
Movable zone start PFN for each node
early_node_map[1] active PFN ranges

    0:        0 ->   262016

On node 0 totalpages: 262016
DMA zone: 32 pages used for memmap
DMA zone: 0 pages reserved
DMA zone: 4064 pages, LIFO batch:0
Normal zone: 1760 pages used for memmap
Normal zone: 223520 pages, LIFO batch:31
HighMem zone: 255 pages used for memmap
HighMem zone: 32385 pages, LIFO batch:7
Movable zone: 0 pages used for memmap
DMI 2.3 present.
ACPI: RSDP 000F7100, 0014 (r0 PTLTD )
ACPI: RSDT 3FEFCF28, 002C (r1 PTLTD RSDT 6040000 LTP 0)
ACPI: FACP 3FEFEF2E, 0074 (r1 AMD TECATE 6040000 PTL F4240)
ACPI: DSDT 3FEFCF54, 1FDA (r1 AMD AMDACPI 6040000 MSFT 100000D)
ACPI: FACS 3FEFFFC0, 0040
ACPI: APIC 3FEFEFA2, 005E (r1 PTLTD APIC 6040000 LTP 0)
ACPI: PM-Timer IO Port: 0x8008
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x01] enabled)
Processor #1 6:6 APIC version 16
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
Processor #0 6:6 APIC version 16
ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 2, version 17, address 0xfec00000, GSI 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
Enabling APIC mode: Flat. Using 1 I/O APICs
Using ACPI (MADT) for SMP configuration information
Allocating PCI resources starting at 50000000 (gap: 40000000:bec00000)
Built 1 zonelists in Zone order. Total pages: 259969
Kernel command line: root=/dev/hda4
mapped APIC to ffffb000 (fee00000)
mapped IOAPIC to ffffa000 (fec00000)
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 16384 bytes)
Detected 1600.106 MHz processor.
Console: colour VGA+ 80x25
console [tty0] enabled
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 1031468k/1048064k available (4703k kernel code, 15928k reserved, 1492k data, 228k init, 130496k highmem) virtual kernel memory layout:

    fixmap  : 0xfff9b000 - 0xfffff000   ( 400 kB)
    pkmap   : 0xff800000 - 0xffc00000   (4096 kB)
    vmalloc : 0xf8800000 - 0xff7fe000   ( 111 MB)
    lowmem  : 0xc0000000 - 0xf8000000   ( 896 MB)
      .init : 0xc0716000 - 0xc074f000   ( 228 kB)
      .data : 0xc0597fe0 - 0xc070d138   (1492 kB)
      .text : 0xc0100000 - 0xc0597fe0   (4703 kB)

Checking if this processor honours the WP bit even in supervisor mode... Ok.
SLUB: Genslabs=22, HWalign=32, Order=0-1, MinObjects=4, CPUs=2, Nodes=1
Calibrating delay using timer specific routine.. 3203.64 BogoMIPS (lpj=6407286) Mount-cache hash table entries: 512
CPU: After generic identify, caps: 0383fbff c1cbfbff 00000000 00000000 00000000 00000000 00000000 00000000
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 256K (64 bytes/line)
CPU: After all inits, caps: 0383fbff c1cbfbff 00000000 00000420 00000000 00000000 00000000 00000000 Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
Compat vDSO mapped to ffffe000.
Checking 'hlt' instruction... OK.
SMP alternatives: switching to UP code
ACPI: Core revision 20070126
CPU0: AMD Athlon(tm) MP 1900+ stepping 02
SMP alternatives: switching to SMP code
Booting processor 1/0 eip 3000
Initializing CPU#1
Calibrating delay using timer specific routine.. 3200.61 BogoMIPS (lpj=6401239)
CPU: After generic identify, caps: 0383fbff c1cbfbff 00000000 00000000 00000000 00000000 00000000 00000000
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 256K (64 bytes/line)
CPU: After all inits, caps: 0383fbff c1cbfbff 00000000 00000420 00000000 00000000 00000000 00000000 Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#1.
CPU1: AMD Athlon(tm) Processor stepping 02
Total of 2 processors activated (6404.26 BogoMIPS).
ENABLING IO-APIC IRQs
..TIMER: vector=0x31 apic1=0 pin1=2 apic2=0 pin2=0
Brought up 2 CPUs
xor: automatically using best checksumming function: pIII_sse
pIII_sse : 4311.000 MB/sec
xor: using function: pIII_sse (4311.000 MB/sec)
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: PCI BIOS revision 2.10 entry at 0xfd7d0, last bus=2
PCI: Using configuration type 1
Setting up standard PCI resources
mtrr: your CPUs had inconsistent fixed MTRR settings
mtrr: probably your BIOS does not setup all CPUs.
mtrr: corrected configuration.
ACPI: EC: Look up EC in DSDT
ACPI: Interpreter enabled
ACPI: (supports S0 S1 S5)
ACPI: Using IOAPIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (0000:00)
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGP_._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.OP2P._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 *5 10 11)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 5 10 *11)
ACPI: PCI Interrupt Link [LNKC] (IRQs *3 5 10 11)
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 5 *10 11)
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init
ACPI: bus type pnp registered
pnp: PnP ACPI: found 9 devices
ACPI: ACPI bus type pnp unregistered
SCSI subsystem initialized
libata version 2.21 loaded.
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
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 0xfffc0000-0xffffffff could not be reserved
pnp: 00:00: iomem range 0xffc00000-0xfff7ffff has been reserved
pnp: 00:00: iomem range 0x0-0x9ffff could not be reserved
pnp: 00:00: iomem range 0x100000-0x3fffffff could not be reserved
pnp: 00:06: ioport range 0x4d0-0x4d1 has been reserved
PCI: Bridge: 0000:00:01.0
IO window: disabled.
MEM window: f8000000-fbffffff
PREFETCH window: 50000000-500fffff
PCI: Bridge: 0000:00:10.0
IO window: 2000-2fff
MEM window: fc000000-fc0fffff
PREFETCH window: 50100000-502fffff
NET: Registered protocol family 2
Time: acpi_pm clocksource has been installed.
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 8, 1572864 bytes)
TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
Machine check exception polling timer started.
audit: initializing netlink socket (disabled)
audit(1203293519.376:1): initialized
highmem bounce pool size: 64 pages
Installing knfsd (copyright (C) 1996 [email protected]).
NTFS driver 2.1.28 [Flags: R/W].
SGI XFS with large block numbers, no debug enabled
async_tx: api initialized (sync-only)
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
BIOS failed to enable PCI standards compliance, fixing this error.
Boot video device is 0000:01:05.0
input: Power Button (FF) as /class/input/input0
ACPI: Power Button (FF) [PWRF]
input: Sleep Button (FF) as /class/input/input1
ACPI: Sleep Button (FF) [SLPF]
input: Power Button (CM) as /class/input/input2
ACPI: Power Button (CM) [PWRB]
lp: driver loaded but no devices found
Linux agpgart interface v0.102
agpgart: Detected AMD 760MP chipset
agpgart: AGP aperture is 32M @ 0x0
[drm] Initialized drm 1.1.0 20060810
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
Intel(R) PRO/1000 Network Driver - version 7.3.20-k2
Copyright (c) 1999-2006 Intel Corporation.
ACPI: PCI Interrupt 0000:02:04.0[A] -> GSI 16 (level, low) -> IRQ 16
e1000: 0000:02:04.0: e1000_probe: (PCI:33MHz:32-bit) 00:07:e9:0f:54:22
e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
ACPI: PCI Interrupt 0000:02:08.0[A] -> GSI 19 (level, low) -> IRQ 17
3c59x: Donald Becker and others.
0000:02:08.0: 3Com PCI 3c905C Tornado at f8826c00.
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
AMD7441: IDE controller at PCI slot 0000:00:07.1
AMD7441: chipset revision 4
AMD7441: not 100% native mode: will probe irqs later
AMD7441: 0000:00:07.1 (rev 04) UDMA100 controller

    ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA
    ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:pio

Probing IDE interface ide0...
hda: WDC WD300BB-00AUA1, ATA DISK drive
hdb: PIONEER DVD-RW DVR-112D, ATAPI CD/DVD-ROM drive
hda: selected mode 0x45
hdb: selected mode 0x44
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
hdc: WDC WD800JB-00CRA1, ATA DISK drive
hdc: selected mode 0x45
ide1 at 0x170-0x177,0x376 on irq 15
hda: max request size: 128KiB
hda: 58633344 sectors (30020 MB) w/2048KiB Cache, CHS=58168/16/63, UDMA(100)
hda: cache flushes not supported
hda: hda1 hda2 hda3 hda4
hdc: max request size: 128KiB
hdc: 156301488 sectors (80026 MB) w/8192KiB Cache, CHS=65535/16/63, UDMA(100)
hdc: cache flushes not supported
hdc: hdc1
hdb: ATAPI 40X DVD-ROM DVD-R CD-R/RW drive, 2000kB Cache, UDMA(66)
Uniform CD-ROM driver Revision: 3.20
sata_sil24 0000:02:05.0: version 1.0
ACPI: PCI Interrupt 0000:02:05.0[A] -> GSI 17 (level, low) -> IRQ 18
scsi0 : sata_sil24
scsi1 : sata_sil24
scsi2 : sata_sil24
scsi3 : sata_sil24
ata1: SATA max UDMA/100 cmd 0xf8830000 ctl 0x00000000 bmdma 0x00000000 irq 18
ata2: SATA max UDMA/100 cmd 0xf8832000 ctl 0x00000000 bmdma 0x00000000 irq 18
ata3: SATA max UDMA/100 cmd 0xf8834000 ctl 0x00000000 bmdma 0x00000000 irq 18
ata4: SATA max UDMA/100 cmd 0xf8836000 ctl 0x00000000 bmdma 0x00000000 irq 18
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata1.00: ATA-7: Maxtor 7H500F0, HA431DN0, max UDMA/133
ata1.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32)
ata1.00: configured for UDMA/100
ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata2.00: ATA-7: ST3500630AS, 3.AAE, max UDMA/133
ata2.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32)
ata2.00: configured for UDMA/100
ata3: SATA link down (SStatus 0 SControl 300)
ata4: SATA link down (SStatus 0 SControl 300)
scsi 0:0:0:0: Direct-Access ATA Maxtor 7H500F0 HA43 PQ: 0 ANSI: 5
sd 0:0:0:0: [sda] 976773168 512-byte hardware sectors (500108 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: disabled, read cache: enabled, doesn't support DPO or FUA
sd 0:0:0:0: [sda] 976773168 512-byte hardware sectors (500108 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: disabled, read cache: enabled, doesn't support DPO or FUA
sda: sda1
sd 0:0:0:0: [sda] Attached SCSI disk
sd 0:0:0:0: Attached scsi generic sg0 type 0
scsi 1:0:0:0: Direct-Access ATA ST3500630AS 3.AA PQ: 0 ANSI: 5
sd 1:0:0:0: [sdb] 976773168 512-byte hardware sectors (500108 MB)
sd 1:0:0:0: [sdb] Write Protect is off
sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 1:0:0:0: [sdb] 976773168 512-byte hardware sectors (500108 MB)
sd 1:0:0:0: [sdb] Write Protect is off
sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdb: sdb1
sd 1:0:0:0: [sdb] Attached SCSI disk
sd 1:0:0:0: Attached scsi generic sg1 type 0
ACPI: PCI Interrupt 0000:02:06.0[A] -> GSI 18 (level, low) -> IRQ 19
scsi4 : sata_sil24
scsi5 : sata_sil24
scsi6 : sata_sil24
scsi7 : sata_sil24
ata5: SATA max UDMA/100 cmd 0xf8870000 ctl 0x00000000 bmdma 0x00000000 irq 19
ata6: SATA max UDMA/100 cmd 0xf8872000 ctl 0x00000000 bmdma 0x00000000 irq 19
ata7: SATA max UDMA/100 cmd 0xf8874000 ctl 0x00000000 bmdma 0x00000000 irq 19
ata8: SATA max UDMA/100 cmd 0xf8876000 ctl 0x00000000 bmdma 0x00000000 irq 19
ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata5.00: ATA-7: ST3500630AS, 3.AAE, max UDMA/133
ata5.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32)
ata5.00: configured for UDMA/100
ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata6.00: ATA-7: Maxtor 7H500F0, HA431DN0, max UDMA/133
ata6.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32)
ata6.00: configured for UDMA/100
ata7: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata7.00: ATA-7: ST3500641AS, 3.AAH, max UDMA/133
ata7.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32)
ata7.00: configured for UDMA/100
ata8: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata8.00: ATA-7: ST3500641AS, 3.AAJ, max UDMA/133
ata8.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32)
ata8.00: configured for UDMA/100
scsi 4:0:0:0: Direct-Access ATA ST3500630AS 3.AA PQ: 0 ANSI: 5
sd 4:0:0:0: [sdc] 976773168 512-byte hardware sectors (500108 MB)
sd 4:0:0:0: [sdc] Write Protect is off
sd 4:0:0:0: [sdc] Mode Sense: 00 3a 00 00
sd 4:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 4:0:0:0: [sdc] 976773168 512-byte hardware sectors (500108 MB)
sd 4:0:0:0: [sdc] Write Protect is off
sd 4:0:0:0: [sdc] Mode Sense: 00 3a 00 00
sd 4:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdc: sdc1
sd 4:0:0:0: [sdc] Attached SCSI disk
sd 4:0:0:0: Attached scsi generic sg2 type 0
scsi 5:0:0:0: Direct-Access ATA Maxtor 7H500F0 HA43 PQ: 0 ANSI: 5
sd 5:0:0:0: [sdd] 976773168 512-byte hardware sectors (500108 MB)
sd 5:0:0:0: [sdd] Write Protect is off
sd 5:0:0:0: [sdd] Mode Sense: 00 3a 00 00
sd 5:0:0:0: [sdd] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
sd 5:0:0:0: [sdd] 976773168 512-byte hardware sectors (500108 MB)
sd 5:0:0:0: [sdd] Write Protect is off
sd 5:0:0:0: [sdd] Mode Sense: 00 3a 00 00
sd 5:0:0:0: [sdd] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
sdd: sdd1
sd 5:0:0:0: [sdd] Attached SCSI disk
sd 5:0:0:0: Attached scsi generic sg3 type 0
scsi 6:0:0:0: Direct-Access ATA ST3500641AS 3.AA PQ: 0 ANSI: 5
sd 6:0:0:0: [sde] 976773168 512-byte hardware sectors (500108 MB)
sd 6:0:0:0: [sde] Write Protect is off
sd 6:0:0:0: [sde] Mode Sense: 00 3a 00 00
sd 6:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 6:0:0:0: [sde] 976773168 512-byte hardware sectors (500108 MB)
sd 6:0:0:0: [sde] Write Protect is off
sd 6:0:0:0: [sde] Mode Sense: 00 3a 00 00
sd 6:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sde: sde1
sd 6:0:0:0: [sde] Attached SCSI disk
sd 6:0:0:0: Attached scsi generic sg4 type 0
scsi 7:0:0:0: Direct-Access ATA ST3500641AS 3.AA PQ: 0 ANSI: 5
sd 7:0:0:0: [sdf] 976773168 512-byte hardware sectors (500108 MB)
sd 7:0:0:0: [sdf] Write Protect is off
sd 7:0:0:0: [sdf] Mode Sense: 00 3a 00 00
sd 7:0:0:0: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 7:0:0:0: [sdf] 976773168 512-byte hardware sectors (500108 MB)
sd 7:0:0:0: [sdf] Write Protect is off
sd 7:0:0:0: [sdf] Mode Sense: 00 3a 00 00
sd 7:0:0:0: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdf: sdf1
sd 7:0:0:0: [sdf] Attached SCSI disk
sd 7:0:0:0: Attached scsi generic sg5 type 0
ACPI: PCI Interrupt 0000:02:07.0[A] -> GSI 19 (level, low) -> IRQ 17
scsi8 : sata_sil24
scsi9 : sata_sil24
scsi10 : sata_sil24
scsi11 : sata_sil24
ata9: SATA max UDMA/100 cmd 0xf8880000 ctl 0x00000000 bmdma 0x00000000 irq 17
ata10: SATA max UDMA/100 cmd 0xf8882000 ctl 0x00000000 bmdma 0x00000000 irq 17
ata11: SATA max UDMA/100 cmd 0xf8884000 ctl 0x00000000 bmdma 0x00000000 irq 17
ata12: SATA max UDMA/100 cmd 0xf8886000 ctl 0x00000000 bmdma 0x00000000 irq 17
ata9: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata9.00: ATA-7: ST3500630AS, 3.AAK, max UDMA/133
ata9.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32)
ata9.00: configured for UDMA/100
ata10: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata10.00: ATA-7: ST3500630AS, 3.AAK, max UDMA/133
ata10.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32)
ata10.00: configured for UDMA/100
ata11: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata11.00: ATA-7: ST3500641AS, 3.AAJ, max UDMA/133
ata11.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32)
ata11.00: configured for UDMA/100
ata12: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata12.00: ATA-7: ST3500630AS, 3.AAK, max UDMA/133
ata12.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32)
ata12.00: configured for UDMA/100
scsi 8:0:0:0: Direct-Access ATA ST3500630AS 3.AA PQ: 0 ANSI: 5
sd 8:0:0:0: [sdg] 976773168 512-byte hardware sectors (500108 MB)
sd 8:0:0:0: [sdg] Write Protect is off
sd 8:0:0:0: [sdg] Mode Sense: 00 3a 00 00
sd 8:0:0:0: [sdg] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 8:0:0:0: [sdg] 976773168 512-byte hardware sectors (500108 MB)
sd 8:0:0:0: [sdg] Write Protect is off
sd 8:0:0:0: [sdg] Mode Sense: 00 3a 00 00
sd 8:0:0:0: [sdg] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdg: sdg1
sd 8:0:0:0: [sdg] Attached SCSI disk
sd 8:0:0:0: Attached scsi generic sg6 type 0
scsi 9:0:0:0: Direct-Access ATA ST3500630AS 3.AA PQ: 0 ANSI: 5
sd 9:0:0:0: [sdh] 976773168 512-byte hardware sectors (500108 MB)
sd 9:0:0:0: [sdh] Write Protect is off
sd 9:0:0:0: [sdh] Mode Sense: 00 3a 00 00
sd 9:0:0:0: [sdh] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 9:0:0:0: [sdh] 976773168 512-byte hardware sectors (500108 MB)
sd 9:0:0:0: [sdh] Write Protect is off
sd 9:0:0:0: [sdh] Mode Sense: 00 3a 00 00
sd 9:0:0:0: [sdh] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdh: sdh1
sd 9:0:0:0: [sdh] Attached SCSI disk
sd 9:0:0:0: Attached scsi generic sg7 type 0
scsi 10:0:0:0: Direct-Access ATA ST3500641AS 3.AA PQ: 0 ANSI: 5
sd 10:0:0:0: [sdi] 976773168 512-byte hardware sectors (500108 MB)
sd 10:0:0:0: [sdi] Write Protect is off
sd 10:0:0:0: [sdi] Mode Sense: 00 3a 00 00
sd 10:0:0:0: [sdi] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 10:0:0:0: [sdi] 976773168 512-byte hardware sectors (500108 MB)
sd 10:0:0:0: [sdi] Write Protect is off
sd 10:0:0:0: [sdi] Mode Sense: 00 3a 00 00
sd 10:0:0:0: [sdi] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdi: sdi1
sd 10:0:0:0: [sdi] Attached SCSI disk
sd 10:0:0:0: Attached scsi generic sg8 type 0
scsi 11:0:0:0: Direct-Access ATA ST3500630AS 3.AA PQ: 0 ANSI: 5
sd 11:0:0:0: [sdj] 976773168 512-byte hardware sectors (500108 MB)
sd 11:0:0:0: [sdj] Write Protect is off
sd 11:0:0:0: [sdj] Mode Sense: 00 3a 00 00
sd 11:0:0:0: [sdj] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 11:0:0:0: [sdj] 976773168 512-byte hardware sectors (500108 MB)
sd 11:0:0:0: [sdj] Write Protect is off
sd 11:0:0:0: [sdj] Mode Sense: 00 3a 00 00
sd 11:0:0:0: [sdj] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdj: sdj1
sd 11:0:0:0: [sdj] Attached SCSI disk
sd 11:0:0:0: Attached scsi generic sg9 type 0
ieee1394: raw1394: /dev/raw1394 device initialized
usbmon: debugfs is not available
ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver
ACPI: PCI Interrupt 0000:02:00.0[D] -> GSI 19 (level, low) -> IRQ 17
ohci_hcd 0000:02:00.0: OHCI Host Controller
ohci_hcd 0000:02:00.0: new USB bus registered, assigned bus number 1
ohci_hcd 0000:02:00.0: irq 17, io mem 0xfc018000
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 4 ports detected
usb 1-4: new low speed USB device using ohci_hcd and address 2
usb 1-4: device descriptor read/64, error -62
usb 1-4: device descriptor read/64, error -62
usb 1-4: new low speed USB device using ohci_hcd and address 3
usb 1-4: device descriptor read/64, error -62
usb 1-4: device descriptor read/64, error -62
usb 1-4: new low speed USB device using ohci_hcd and address 4
usb 1-4: device not accepting address 4, error -62
usb 1-4: new low speed USB device using ohci_hcd and address 5
usb 1-4: device not accepting address 5, error -62
usbcore: registered new interface driver usblp
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1
PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
serio: i8042 KBD port at 0x60,0x64 irq 1
mice: PS/2 mouse device common for all mice
input: AT Translated Set 2 keyboard as /class/input/input3
md: raid0 personality registered for level 0
md: raid1 personality registered for level 1
md: raid10 personality registered for level 10
raid6: int32x1 658 MB/s
raid6: int32x2 853 MB/s
raid6: int32x4 549 MB/s
raid6: int32x8 508 MB/s
raid6: mmxx1 1311 MB/s
raid6: mmxx2 2258 MB/s
raid6: sse1x1 468 MB/s
raid6: sse1x2 936 MB/s
raid6: using algorithm sse1x2 (936 MB/s)
md: raid6 personality registered for level 6
md: raid5 personality registered for level 5
md: raid4 personality registered for level 4
device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: [email protected]
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 (Fri Jul 20 09:12:58 2007 UTC).
ALSA device list:
No soundcards found.
Netfilter messages via NETLINK v0.30.
nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
ctnetlink v0.93: registering with nfnetlink.
ip_tables: (C) 2000-2006 Netfilter Core Team
ClusterIP Version 0.8 loaded successfully
arp_tables: (C) 2002 David S. Miller
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
Starting balanced_irq
Using IPI No-Shortcut mode
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
ReiserFS: hda4: found reiserfs format "3.6" with standard journal
ReiserFS: hda4: using ordered data mode
ReiserFS: hda4: journal params: device hda4, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: hda4: checking transaction log (hda4)
ReiserFS: hda4: Using r5 hash to sort names
VFS: Mounted root (reiserfs filesystem) readonly.
Freeing unused kernel memory: 228k freed
AMD768 RNG detected
Real Time Clock Driver v1.12ac
floppy0: no floppy controllers found
hpt374: module license 'Proprietary' taints kernel.
HPT374 UDMA/ATA133 RAID Controller driver
Version 2.17, Compiled Dec 9 2007 18:19:24
RAID5 write-back enabled
ACPI: PCI Interrupt 0000:00:09.0[A] -> GSI 21 (level, low) -> IRQ 20
ACPI: PCI Interrupt 0000:00:09.1[A] -> GSI 21 (level, low) -> IRQ 20
scsi12 : hpt374
scsi 12:0:0:0: Direct-Access HPT3xx RAID 5 Array 3.00 PQ: 0 ANSI: 0
sd 12:0:0:0: [sdk] 976793600 512-byte hardware sectors (500118 MB)
sd 12:0:0:0: [sdk] Write Protect is off
sd 12:0:0:0: [sdk] Mode Sense: 2f 00 00 00
sd 12:0:0:0: [sdk] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 12:0:0:0: [sdk] 976793600 512-byte hardware sectors (500118 MB)
sd 12:0:0:0: [sdk] Write Protect is off
sd 12:0:0:0: [sdk] Mode Sense: 2f 00 00 00
sd 12:0:0:0: [sdk] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdk: sdk1
sd 12:0:0:0: [sdk] Attached SCSI disk
sd 12:0:0:0: Attached scsi generic sg10 type 0
w83781d 0-002c: The W83627HF chip is better supported by the w83627hf driver, support will be dropped from the w83781d driver soon aufs 20071203
kjournald starting. Commit interval 5 seconds
EXT3 FS on hda3, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
EXT3 FS on hdc1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
XFS mounting filesystem sdk1
Ending clean XFS mount for filesystem: sdk1
XFS mounting filesystem sdj1
Ending clean XFS mount for filesystem: sdj1
XFS mounting filesystem sdc1
Ending clean XFS mount for filesystem: sdc1
XFS mounting filesystem sdi1
Ending clean XFS mount for filesystem: sdi1
XFS mounting filesystem sdh1
Ending clean XFS mount for filesystem: sdh1
XFS mounting filesystem sdg1
Ending clean XFS mount for filesystem: sdg1
XFS mounting filesystem sdf1
Ending clean XFS mount for filesystem: sdf1
XFS mounting filesystem sda1
Ending clean XFS mount for filesystem: sda1
XFS mounting filesystem sdb1
Ending clean XFS mount for filesystem: sdb1
XFS mounting filesystem sde1
Ending clean XFS mount for filesystem: sde1
XFS mounting filesystem sdd1
Ending clean XFS mount for filesystem: sdd1
Adding 530136k swap on /dev/hda2. Priority:-1 extents:1 across:530136k
hda: selected mode 0x45
hdb: selected mode 0x44
hdc: selected mode 0x45
e1000: eth0: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
eth1: setting half-duplex.
NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
NFSD: starting 90-second grace period
w83627hf: Found W83627HF chip at 0xc00
PPP generic driver version 2.4.2
PPP BSD Compression module registered

00:00.0 Host bridge: Advanced Micro Devices [AMD] AMD-760 MP [IGD4-2P] System Controller (rev 11)

	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ >SERR- <PERR- INTx-
	Latency: 32
	Region 0: Memory at <unassigned> (32-bit, prefetchable)
	Region 1: Memory at fc300000 (32-bit, prefetchable) [size=4K]
	Region 2: I/O ports at 1810 [disabled] [size=4]
	Capabilities: [a0] AGP version 2.0
		Status: RQ=16 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW- AGP3- Rate=x1,x2
		Command: RQ=1 ArqSz=0 Cal=0 SBA+ AGP+ GART64- 64bit- FW- Rate=<none>
	Kernel driver in use: agpgart-amdk7

00:01.0 PCI bridge: Advanced Micro Devices [AMD] AMD-760 MP [IGD4-2P] AGP Bridge (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 99
Bus: primary=00, secondary=01, subordinate=01, sec-latency=64
I/O behind bridge: 0000f000-00000fff
Memory behind bridge: f8000000-fbffffff
Prefetchable memory behind bridge: 50000000-500fffff
Secondary status: 66MHz+ FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
BridgeCtl: Parity- SERR- NoISA+ VGA+ MAbort- >Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-

00:07.0 ISA bridge: Advanced Micro Devices [AMD] AMD-768 [Opus] ISA (rev 05)
Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0

00:07.1 IDE interface: Advanced Micro Devices [AMD] AMD-768 [Opus] IDE (rev 04) (prog-if 8a [Master SecP PriP])

	Subsystem: Advanced Micro Devices [AMD] AMD-768 [Opus] IDE
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Region 0: [virtual] Memory at 000001f0 (32-bit, non-prefetchable) [disabled] [size=8]
	Region 1: [virtual] Memory at 000003f0 (type 3, non-prefetchable) [disabled] [size=1]
	Region 2: [virtual] Memory at 00000170 (32-bit, non-prefetchable) [disabled] [size=8]
	Region 3: [virtual] Memory at 00000370 (type 3, non-prefetchable) [disabled] [size=1]
	Region 4: I/O ports at f000 [size=16]
	Kernel driver in use: AMD_IDE

00:07.3 Bridge: Advanced Micro Devices [AMD] AMD-768 [Opus] ACPI (rev 03)
Subsystem: Advanced Micro Devices [AMD] AMD-768 [Opus] ACPI
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Kernel driver in use: amd756_smbus
Kernel modules: i2c-amd756, amd-rng

00:09.0 RAID bus controller: Triones Technologies, Inc. HPT374 (rev 07)

	Subsystem: Triones Technologies, Inc. Unknown device 0001
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 64 (2000ns min, 2000ns max)
	Interrupt: pin A routed to IRQ 20
	Region 0: I/O ports at 1828 [size=8]
	Region 1: I/O ports at 1820 [size=4]
	Region 2: I/O ports at 1818 [size=8]
	Region 3: I/O ports at 1814 [size=4]
	Region 4: I/O ports at 1000 [size=256]
	[virtual] Expansion ROM at 50300000 [disabled] [size=128K]
	Capabilities: [60] Power Management version 2
		Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:09.1 RAID bus controller: Triones Technologies, Inc. HPT374 (rev 07)

	Subsystem: Triones Technologies, Inc. Unknown device 0001
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 64 (2000ns min, 2000ns max)
	Interrupt: pin A routed to IRQ 20
	Region 0: I/O ports at 1840 [size=8]
	Region 1: I/O ports at 1838 [size=4]
	Region 2: I/O ports at 1830 [size=8]
	Region 3: I/O ports at 1824 [size=4]
	Region 4: I/O ports at 1400 [size=256]
	Capabilities: [60] Power Management version 2
		Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:10.0 PCI bridge: Advanced Micro Devices [AMD] AMD-768 [Opus] PCI (rev 05) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ >SERR- <PERR- INTx-
Latency: 64
Bus: primary=00, secondary=02, subordinate=02, sec-latency=168
I/O behind bridge: 00002000-00002fff
Memory behind bridge: fc000000-fc0fffff
Prefetchable memory behind bridge: 50100000-502fffff
Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- <SERR- <PERR-
BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-

01:05.0 VGA compatible controller: S3 Inc. 86c368 [Trio 3D/2X] (rev 02) (prog-if 00 [VGA controller])
Subsystem: S3 Inc. Trio3D/2X
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Region 0: Memory at f8000000 (32-bit, non-prefetchable) [size=64M]
[virtual] Expansion ROM at 50000000 [disabled] [size=64K]
Capabilities: [dc] Power Management version 1
Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [80] AGP version 1.0
Status: RQ=32 Iso- ArqSz=0 Cal=0 SBA- ITACoh- GART64- HTrans- 64bit- FW- AGP3- Rate=x1,x2
Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW- Rate=x2

02:00.0 USB Controller: Advanced Micro Devices [AMD] AMD-768 [Opus] USB (rev 07) (prog-if 10 [OHCI])
Subsystem: Advanced Micro Devices [AMD] AMD-768 [Opus] USB
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 64 (20000ns max)
Interrupt: pin D routed to IRQ 17
Region 0: Memory at fc018000 (32-bit, non-prefetchable) [size=4K]
Kernel driver in use: ohci_hcd

02:04.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet Controller (rev 02)

	Subsystem: Intel Corporation PRO/1000 MT Desktop Adapter
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 64 (63750ns min), Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 16
	Region 0: Memory at fc040000 (32-bit, non-prefetchable) [size=128K]
	Region 1: Memory at fc020000 (32-bit, non-prefetchable) [size=128K]
	Region 2: I/O ports at 2080 [size=64]
	[virtual] Expansion ROM at 50280000 [disabled] [size=128K]
	Capabilities: [dc] Power Management version 2
		Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=1 PME-
	Capabilities: [e4] PCI-X non-bridge device
		Command: DPERE- ERO+ RBC=512 OST=1
		Status: Dev=00:00.0 64bit- 133MHz- SCD- USC- DC=simple DMMRBC=2048 DMOST=1 DMCRS=16 RSCEM- 266MHz- 533MHz-
	Capabilities: [f0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
		Address: 0000000000000000  Data: 0000
	Kernel driver in use: e1000

02:05.0 RAID bus controller: Silicon Image, Inc. SiI 3124 PCI-X Serial ATA Controller (rev 02)
Subsystem: Silicon Image, Inc. Unknown device 7124
Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV+ VGASnoop- ParErr- Stepping+ SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 64, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 18
Region 0: Memory at fc019000 (64-bit, non-prefetchable) [size=128]
Region 2: Memory at fc000000 (64-bit, non-prefetchable) [size=32K]
Region 4: I/O ports at 20c0 [size=16]
[virtual] Expansion ROM at 50100000 [disabled] [size=512K]
Capabilities: [64] Power Management version 2
Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=1 PME-
Capabilities: [40] PCI-X non-bridge device
Command: DPERE- ERO+ RBC=512 OST=12
Status: Dev=ff:1f.0 64bit+ 133MHz+ SCD- USC- DC=simple DMMRBC=2048 DMOST=12 DMCRS=128 RSCEM- 266MHz- 533MHz-
Capabilities: [54] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
Address: 0000000000000000 Data: 0000
Kernel driver in use: sata_sil24

02:06.0 RAID bus controller: Silicon Image, Inc. SiI 3124 PCI-X Serial ATA Controller (rev 02)
Subsystem: Silicon Image, Inc. Unknown device 7124
Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV+ VGASnoop- ParErr- Stepping+ SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 64, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 19
Region 0: Memory at fc019400 (64-bit, non-prefetchable) [size=128]
Region 2: Memory at fc008000 (64-bit, non-prefetchable) [size=32K]
Region 4: I/O ports at 20d0 [size=16]
[virtual] Expansion ROM at 50180000 [disabled] [size=512K]
Capabilities: [64] Power Management version 2
Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=1 PME-
Capabilities: [40] PCI-X non-bridge device
Command: DPERE- ERO+ RBC=512 OST=12
Status: Dev=ff:1f.0 64bit+ 133MHz+ SCD- USC- DC=simple DMMRBC=2048 DMOST=12 DMCRS=128 RSCEM- 266MHz- 533MHz-
Capabilities: [54] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
Address: 0000000000000000 Data: 0000
Kernel driver in use: sata_sil24

02:07.0 RAID bus controller: Silicon Image, Inc. SiI 3124 PCI-X Serial ATA Controller (rev 02)
Subsystem: Silicon Image, Inc. Unknown device 7124
Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV+ VGASnoop- ParErr- Stepping+ SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 64, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 17
Region 0: Memory at fc019800 (64-bit, non-prefetchable) [size=128]
Region 2: Memory at fc010000 (64-bit, non-prefetchable) [size=32K]
Region 4: I/O ports at 20e0 [size=16]
[virtual] Expansion ROM at 50200000 [disabled] [size=512K]
Capabilities: [64] Power Management version 2
Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=1 PME-
Capabilities: [40] PCI-X non-bridge device
Command: DPERE- ERO+ RBC=512 OST=12
Status: Dev=ff:1f.0 64bit+ 133MHz+ SCD- USC- DC=simple DMMRBC=2048 DMOST=12 DMCRS=128 RSCEM- 266MHz- 533MHz-
Capabilities: [54] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
Address: 0000000000000000 Data: 0000
Kernel driver in use: sata_sil24

02:08.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev 78)
Subsystem: Tyan Computer Tiger MPX S2466 (3C920 Integrated Fast Ethernet Controller)
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 80 (2500ns min, 2500ns max), Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 17
Region 0: I/O ports at 2000 [size=128]
Region 1: Memory at fc019c00 (32-bit, non-prefetchable) [size=128]
[virtual] Expansion ROM at 502a0000 [disabled] [size=128K]
Capabilities: [dc] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=2 PME-
Kernel driver in use: 3c59x

Jim Paris

2008-02-19 04:37 UTC #1 lore raw

Quoted 2 lines · Denys Dmytriyenko

I've been following this list for several months now trying to spot a similar issue or to gain knowledge to resolve mine.

..

Quoted 2 lines

I'm running a fileserver with array of 10 disks (8 Seagate 500GB 7200.9 and 7200.10 plus 2 Maxtors)

..

Quoted 3 lines

Power supply was
originally 550 watt Enermax (should be enough power, according to a wattmeter), but to be sure was replaced to 750 watt Coolermaster.

Hi,

As you may have noticed on this list, power supplies are very frequently a problem. Just taking what you said, a ST3500630AS 7200.10 disk requires up to 2.8A peak on the +12V line, which is 28A total for 10 disks. The Coolermaster Real Power Pro 750 has three separate 12V rails and each can only go up to 19A. So that might already be the answer, depending on how the rails match up with your wiring.

I suggest hooking up a couple of the disks to your old power supply and powering them up separately [1]. If you don't see any problems on those disks then it was likely power related.

-jim

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

Denys Dmytriyenko

author

2008-02-19 06:39 UTC #2 lore raw

Quoted 21 lines · Jim Paris

Quoted 2 lines · Denys Dmytriyenko
I've been following this list for several months now trying to spot a similar issue or to gain knowledge to resolve mine.
..
Quoted 2 lines
I'm running a fileserver with array of 10 disks (8 Seagate 500GB 7200.9 and 7200.10 plus 2 Maxtors)
..
Quoted 3 lines
Power supply was
originally 550 watt Enermax (should be enough power, according to a wattmeter), but to be sure was replaced to 750 watt Coolermaster.
Hi,
As you may have noticed on this list, power supplies are very frequently a problem. Just taking what you said, a ST3500630AS 7200.10 disk requires up to 2.8A peak on the +12V line, which is 28A total for 10 disks. The Coolermaster Real Power Pro 750 has three separate 12V rails and each can only go up to 19A. So that might already be the answer, depending on how the rails match up with your wiring.

Quoted 3 lines

I suggest hooking up a couple of the disks to your old power supply and powering them up separately [1]. If you don't see any problems on those disks then it was likely power related.

Hi,

Thanks for the reply. Power supply was the first thing to check, that's why I mentioned that it was upgraded. The Coolermaster Real Power Pro 750 actually has 4 separate 12V rails, but AFAIK 2 of them only available to the PCIe connectors and not to the regular Molex/SATA connectors. Others I distributed equally among the drives. BTW, I should probably get some PCIe 6-pin/8-pin to Molex 4-pin adapters to utilize those unused 12V rails...

2.8A peak is used mainly during spin up, which is staggered in my case (ICY Dock SATA enclosure). Even when all disks were spun up at the same time, wattmeter never showed anything close to 500 watt. During normal operation no more than 2 disks are accessed at a time, plus most of them are in standby, as I mentioned. And good PSUs, like previous Enermax and current Coolermaster can withstand additional 100-150 watt of peak load...

I used to run the system with fewer (4) drives and was still experiencing problems. Not to mention that power problem would not cause the second issue of poor performance.

Thanks again.

Regards,
Denys

Mark Lord

2008-02-19 15:32 UTC #3 lore raw

In reply to Jim Paris

Quoted 3 lines · Jim Paris

..
As you may have noticed on this list, power supplies are very frequently a problem.

..

Actually, no, I haven't noticed that. :)

I do see them more frequently being suggested as a possible problem, and then after some time and expense on the part of the reporters it nearly always turns out to have been a device driver bug, or (less often) a firmware quirk of the device.

Yes, PSUs are often suggested as a problem here,
but only rarely has that been true.

Especially nowadays, as PSUs are becoming much larger than they historically once were.

Cheers
(been around here since 1993 or so)

Denys Dmytriyenko

author

2008-03-02 06:15 UTC #4 lore raw

Quoted 13 lines · Mark Lord

Quoted 3 lines · Jim Paris
..
As you may have noticed on this list, power supplies are very frequently a problem.
..
Actually, no, I haven't noticed that. :)
I do see them more frequently being suggested as a possible problem, and then after some time and expense on the part of the reporters it nearly always turns out to have been a device driver bug, or (less often) a firmware quirk of the device.

Quoted 5 lines

Yes, PSUs are often suggested as a problem here,
but only rarely has that been true.
Especially nowadays, as PSUs are becoming much larger than they historically once were.

Hi again. Thanks for your replies and sorry for bringing this up again. I am still trying to resolve those 2 issues I mentioned in the first email. While playing with different power options lately, I decided to replace the PSU again for a single-rail Silencer 750 EPS12V, which is rated at 60A (!) for a single 12V rail. Does anybody have any experience with it? Can anyone suggest anything better?

That is assuming the first issue with exceptions and resets is due to the power being maxed out...

Meanwhile I would still like to resolve the low performance issue with SiI 3124, which shows only 17 MB/s write speed doing "dd if=/dev/zero", while Intel ICH7 based PC writes at 44 MB/s sustained rate. I'd really appreciate any ideas/suggestions towards solving this issue. Please let me know if any other information is needed. I'm attaching the original email with logs. Thanks in advance!

Signature · 1 line

Denys

Hi Gurus!

Preamble:

I've been following this list for several months now trying to spot a similar issue or to gain knowledge to resolve mine. I'm pretty sure the problem is with my setup/configuration, but I've been unable to fix it so far. I would be eternally grateful if someone can help me in resolving the issue. Thanks in advance.

Setup:

I'm running a fileserver with array of 10 disks (8 Seagate 500GB 7200.9 and 7200.10 plus 2 Maxtors) on 3 Addonics ADSA4R5 (4-port SATA2 PCI on Sil 3124) cards in JBOD configuration. The host is a little bit outdated and is dual AMD Athlon MP 1900+ on Tyan Tiger MPX (S2466N-4M) with 1GB of RAM. SATA cards are in PCI slots, not PCI-X. Most of the time drives are in standby mode (30min timeout), but it does not make any difference with issues I'm seeing. Filesystem used is XFS and all the disks are shared over NFS. Power supply was originally 550 watt Enermax (should be enough power, according to a wattmeter), but to be sure was replaced to 750 watt Coolermaster. The kernel is currently 2.6.23.9, but I tried many other versions from 2.6.21 to 2.6.24. The system is Gentoo, but the kernel is vanilla.

Issue #1:

I'm seeing lots of resets in the logs for different drives and different exceptions. Sometimes on idle drives, but mostly on those being accessed. Sometimes I can see couple exceptions in a row, but sometimes I don't see any for hours. These are just example exceptions, but I believe I've seen others as well:

ata1: failed to read log page 10h (errno=-2)
ata1.00: exception Emask 0x1 SAct 0x3 SErr 0x0 action 0x0 ata1.00: irq_stat 0x00060002, device error via SDB FIS
ata1.00: cmd 60/80:00:bf:00:00/00:00:00:00:00/40 tag 0 cdb 0x0 data 65536 in

         res 40/00:00:2f:60:38/00:00:3a:00:00/e0 Emask 0x1 (device error)
ata1.00: cmd 60/80:08:3f:00:00/00:00:00:00:00/40 tag 1 cdb 0x0 data 65536 in
         res 40/00:00:2f:60:38/00:00:3a:00:00/e0 Emask 0x1 (device error)

ata1.00: configured for UDMA/100
ata1: EH complete
sd 0:0:0:0: [sda] 976773168 512-byte hardware sectors (500108 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: disabled, read cache: enabled, doesn't support
DPO or FUA

ata12: exception Emask 0x10 SAct 0x0 SErr 0x80000 action 0x2 frozen
ata12: irq_stat 0x01100010, PHY RDY changed
ata12: soft resetting port
ata12: softreset failed (timeout)
ata12: hard resetting port
ata12: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata12.00: configured for UDMA/100
ata12: EH complete
sd 11:0:0:0: [sdj] 976773168 512-byte hardware sectors (500108 MB) sd 11:0:0:0: [sdj] Write Protect is off
sd 11:0:0:0: [sdj] Mode Sense: 00 3a 00 00
sd 11:0:0:0: [sdj] Write cache: enabled, read cache: enabled, doesn't support
DPO or FUA

I'm not sure how critical are those. The side effect of those resets is loosing my standby timeout settings. But I'm rather worried about drives operating optimally and the integrity of my data. Therefore any failure or exception message in the logs is considered bad and means something is wrong and needs attention. Please help me understand/resolve those exceptions.

Issue #2:

I am also having a performance issue with sata_sil24. I can read data at speeds up to 30 MB/s but write only at speeds around 15 MB/s. When I used Supermicro 8-port sata_mv card, I was able to get speeds at around 40-50 MB/s. Unfortunatelly, sata_mv was not stable at that time and I had to replace it with what was claimed to be the most supported SATA2 chipset under Linux - sata_sil24... I bet the problem is with my setup, but I cannot figure out where or how to fix it.

"hdparm -t" reports speeds in the area of 60-80 MB/s though.

What I find strange is that the host controller is only recognized as UDMA/100 and all the drives even though they are UDMA/133 configured for UDMA/100.

Another strange thing is that all the disks are configured for 16-bit IO_support and cannot be changed to 32-bit:

/dev/sda:

 IO_support    =  0 (default 16-bit)
 readonly      =  0 (off)
 readahead     = 256 (on)
 geometry      = 60801/255/63, sectors = 976773168, start = 0

And one more thing - both Maxtor drives have their write cache disabled by default, unlike Seagate drives. Should I be worried about it?

The bootup sequence and lspci dump are attached. Please note there is HPT374 2-channel IDE RAID device in the logs, which runs a small RAID5 array, but I tried w/o it before and had same issues.

I'd really appreciate if anybody can help me resolve my problems. Thanks in advance!

Regards,
Denys

00:00.0 Host bridge: Advanced Micro Devices [AMD] AMD-760 MP [IGD4-2P] System Controller (rev 11)

	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ >SERR- <PERR- INTx-
	Latency: 32
	Region 0: Memory at <unassigned> (32-bit, prefetchable)
	Region 1: Memory at fc300000 (32-bit, prefetchable) [size=4K]
	Region 2: I/O ports at 1810 [disabled] [size=4]
	Capabilities: [a0] AGP version 2.0
		Status: RQ=16 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW- AGP3- Rate=x1,x2
		Command: RQ=1 ArqSz=0 Cal=0 SBA+ AGP+ GART64- 64bit- FW- Rate=<none>
	Kernel driver in use: agpgart-amdk7

00:01.0 PCI bridge: Advanced Micro Devices [AMD] AMD-760 MP [IGD4-2P] AGP Bridge (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 99
Bus: primary=00, secondary=01, subordinate=01, sec-latency=64
I/O behind bridge: 0000f000-00000fff
Memory behind bridge: f8000000-fbffffff
Prefetchable memory behind bridge: 50000000-500fffff
Secondary status: 66MHz+ FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
BridgeCtl: Parity- SERR- NoISA+ VGA+ MAbort- >Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-

00:07.0 ISA bridge: Advanced Micro Devices [AMD] AMD-768 [Opus] ISA (rev 05)
Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0

00:07.1 IDE interface: Advanced Micro Devices [AMD] AMD-768 [Opus] IDE (rev 04) (prog-if 8a [Master SecP PriP])

	Subsystem: Advanced Micro Devices [AMD] AMD-768 [Opus] IDE
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Region 0: [virtual] Memory at 000001f0 (32-bit, non-prefetchable) [disabled] [size=8]
	Region 1: [virtual] Memory at 000003f0 (type 3, non-prefetchable) [disabled] [size=1]
	Region 2: [virtual] Memory at 00000170 (32-bit, non-prefetchable) [disabled] [size=8]
	Region 3: [virtual] Memory at 00000370 (type 3, non-prefetchable) [disabled] [size=1]
	Region 4: I/O ports at f000 [size=16]
	Kernel driver in use: AMD_IDE

00:07.3 Bridge: Advanced Micro Devices [AMD] AMD-768 [Opus] ACPI (rev 03)
Subsystem: Advanced Micro Devices [AMD] AMD-768 [Opus] ACPI
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Kernel driver in use: amd756_smbus
Kernel modules: i2c-amd756, amd-rng

00:09.0 RAID bus controller: Triones Technologies, Inc. HPT374 (rev 07)

	Subsystem: Triones Technologies, Inc. Unknown device 0001
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 64 (2000ns min, 2000ns max)
	Interrupt: pin A routed to IRQ 20
	Region 0: I/O ports at 1828 [size=8]
	Region 1: I/O ports at 1820 [size=4]
	Region 2: I/O ports at 1818 [size=8]
	Region 3: I/O ports at 1814 [size=4]
	Region 4: I/O ports at 1000 [size=256]
	[virtual] Expansion ROM at 50300000 [disabled] [size=128K]
	Capabilities: [60] Power Management version 2
		Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:09.1 RAID bus controller: Triones Technologies, Inc. HPT374 (rev 07)

	Subsystem: Triones Technologies, Inc. Unknown device 0001
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 64 (2000ns min, 2000ns max)
	Interrupt: pin A routed to IRQ 20
	Region 0: I/O ports at 1840 [size=8]
	Region 1: I/O ports at 1838 [size=4]
	Region 2: I/O ports at 1830 [size=8]
	Region 3: I/O ports at 1824 [size=4]
	Region 4: I/O ports at 1400 [size=256]
	Capabilities: [60] Power Management version 2
		Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:10.0 PCI bridge: Advanced Micro Devices [AMD] AMD-768 [Opus] PCI (rev 05) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ >SERR- <PERR- INTx-
Latency: 64
Bus: primary=00, secondary=02, subordinate=02, sec-latency=168
I/O behind bridge: 00002000-00002fff
Memory behind bridge: fc000000-fc0fffff
Prefetchable memory behind bridge: 50100000-502fffff
Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- <SERR- <PERR-
BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-

01:05.0 VGA compatible controller: S3 Inc. 86c368 [Trio 3D/2X] (rev 02) (prog-if 00 [VGA controller])
Subsystem: S3 Inc. Trio3D/2X
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Region 0: Memory at f8000000 (32-bit, non-prefetchable) [size=64M]
[virtual] Expansion ROM at 50000000 [disabled] [size=64K]
Capabilities: [dc] Power Management version 1
Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [80] AGP version 1.0
Status: RQ=32 Iso- ArqSz=0 Cal=0 SBA- ITACoh- GART64- HTrans- 64bit- FW- AGP3- Rate=x1,x2
Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW- Rate=x2

02:00.0 USB Controller: Advanced Micro Devices [AMD] AMD-768 [Opus] USB (rev 07) (prog-if 10 [OHCI])
Subsystem: Advanced Micro Devices [AMD] AMD-768 [Opus] USB
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 64 (20000ns max)
Interrupt: pin D routed to IRQ 17
Region 0: Memory at fc018000 (32-bit, non-prefetchable) [size=4K]
Kernel driver in use: ohci_hcd

02:04.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet Controller (rev 02)

	Subsystem: Intel Corporation PRO/1000 MT Desktop Adapter
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 64 (63750ns min), Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 16
	Region 0: Memory at fc040000 (32-bit, non-prefetchable) [size=128K]
	Region 1: Memory at fc020000 (32-bit, non-prefetchable) [size=128K]
	Region 2: I/O ports at 2080 [size=64]
	[virtual] Expansion ROM at 50280000 [disabled] [size=128K]
	Capabilities: [dc] Power Management version 2
		Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=1 PME-
	Capabilities: [e4] PCI-X non-bridge device
		Command: DPERE- ERO+ RBC=512 OST=1
		Status: Dev=00:00.0 64bit- 133MHz- SCD- USC- DC=simple DMMRBC=2048 DMOST=1 DMCRS=16 RSCEM- 266MHz- 533MHz-
	Capabilities: [f0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
		Address: 0000000000000000  Data: 0000
	Kernel driver in use: e1000

02:05.0 RAID bus controller: Silicon Image, Inc. SiI 3124 PCI-X Serial ATA Controller (rev 02)
Subsystem: Silicon Image, Inc. Unknown device 7124
Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV+ VGASnoop- ParErr- Stepping+ SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 64, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 18
Region 0: Memory at fc019000 (64-bit, non-prefetchable) [size=128]
Region 2: Memory at fc000000 (64-bit, non-prefetchable) [size=32K]
Region 4: I/O ports at 20c0 [size=16]
[virtual] Expansion ROM at 50100000 [disabled] [size=512K]
Capabilities: [64] Power Management version 2
Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=1 PME-
Capabilities: [40] PCI-X non-bridge device
Command: DPERE- ERO+ RBC=512 OST=12
Status: Dev=ff:1f.0 64bit+ 133MHz+ SCD- USC- DC=simple DMMRBC=2048 DMOST=12 DMCRS=128 RSCEM- 266MHz- 533MHz-
Capabilities: [54] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
Address: 0000000000000000 Data: 0000
Kernel driver in use: sata_sil24

02:06.0 RAID bus controller: Silicon Image, Inc. SiI 3124 PCI-X Serial ATA Controller (rev 02)
Subsystem: Silicon Image, Inc. Unknown device 7124
Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV+ VGASnoop- ParErr- Stepping+ SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 64, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 19
Region 0: Memory at fc019400 (64-bit, non-prefetchable) [size=128]
Region 2: Memory at fc008000 (64-bit, non-prefetchable) [size=32K]
Region 4: I/O ports at 20d0 [size=16]
[virtual] Expansion ROM at 50180000 [disabled] [size=512K]
Capabilities: [64] Power Management version 2
Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=1 PME-
Capabilities: [40] PCI-X non-bridge device
Command: DPERE- ERO+ RBC=512 OST=12
Status: Dev=ff:1f.0 64bit+ 133MHz+ SCD- USC- DC=simple DMMRBC=2048 DMOST=12 DMCRS=128 RSCEM- 266MHz- 533MHz-
Capabilities: [54] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
Address: 0000000000000000 Data: 0000
Kernel driver in use: sata_sil24

02:07.0 RAID bus controller: Silicon Image, Inc. SiI 3124 PCI-X Serial ATA Controller (rev 02)
Subsystem: Silicon Image, Inc. Unknown device 7124
Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV+ VGASnoop- ParErr- Stepping+ SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 64, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 17
Region 0: Memory at fc019800 (64-bit, non-prefetchable) [size=128]
Region 2: Memory at fc010000 (64-bit, non-prefetchable) [size=32K]
Region 4: I/O ports at 20e0 [size=16]
[virtual] Expansion ROM at 50200000 [disabled] [size=512K]
Capabilities: [64] Power Management version 2
Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=1 PME-
Capabilities: [40] PCI-X non-bridge device
Command: DPERE- ERO+ RBC=512 OST=12
Status: Dev=ff:1f.0 64bit+ 133MHz+ SCD- USC- DC=simple DMMRBC=2048 DMOST=12 DMCRS=128 RSCEM- 266MHz- 533MHz-
Capabilities: [54] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
Address: 0000000000000000 Data: 0000
Kernel driver in use: sata_sil24

02:08.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev 78)
Subsystem: Tyan Computer Tiger MPX S2466 (3C920 Integrated Fast Ethernet Controller)
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 80 (2500ns min, 2500ns max), Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 17
Region 0: I/O ports at 2000 [size=128]
Region 1: Memory at fc019c00 (32-bit, non-prefetchable) [size=128]
[virtual] Expansion ROM at 502a0000 [disabled] [size=128K]
Capabilities: [dc] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=2 PME-
Kernel driver in use: 3c59x

Linux version 2.6.23.9 (root@gandalf) (gcc version 3.4.6 (Gentoo 3.4.6-r2, ssp-3.4.6-1.0, pie-8.7.10)) #1 SMP Wed Dec 5 13:18:48 EST 2007 BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 0000000000096c00 (usable)
BIOS-e820: 0000000000096c00 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000ce000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000003fef0000 (usable)
BIOS-e820: 000000003fef0000 - 000000003feff000 (ACPI data)
BIOS-e820: 000000003feff000 - 000000003ff00000 (ACPI NVS)
BIOS-e820: 000000003ff00000 - 000000003ff80000 (usable)
BIOS-e820: 000000003ff80000 - 0000000040000000 (reserved)
BIOS-e820: 00000000fec00000 - 00000000fec04000 (reserved)
BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved)
127MB HIGHMEM available.
896MB LOWMEM available.
found SMP MP-table at 000f7170
Entering add_active_range(0, 0, 262016) 0 entries of 256 used
Zone PFN ranges:
DMA 0 -> 4096
Normal 4096 -> 229376
HighMem 229376 -> 262016
Movable zone start PFN for each node
early_node_map[1] active PFN ranges

    0:        0 ->   262016

On node 0 totalpages: 262016
DMA zone: 32 pages used for memmap
DMA zone: 0 pages reserved
DMA zone: 4064 pages, LIFO batch:0
Normal zone: 1760 pages used for memmap
Normal zone: 223520 pages, LIFO batch:31
HighMem zone: 255 pages used for memmap
HighMem zone: 32385 pages, LIFO batch:7
Movable zone: 0 pages used for memmap
DMI 2.3 present.
ACPI: RSDP 000F7100, 0014 (r0 PTLTD )
ACPI: RSDT 3FEFCF28, 002C (r1 PTLTD RSDT 6040000 LTP 0)
ACPI: FACP 3FEFEF2E, 0074 (r1 AMD TECATE 6040000 PTL F4240)
ACPI: DSDT 3FEFCF54, 1FDA (r1 AMD AMDACPI 6040000 MSFT 100000D)
ACPI: FACS 3FEFFFC0, 0040
ACPI: APIC 3FEFEFA2, 005E (r1 PTLTD APIC 6040000 LTP 0)
ACPI: PM-Timer IO Port: 0x8008
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x01] enabled)
Processor #1 6:6 APIC version 16
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
Processor #0 6:6 APIC version 16
ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 2, version 17, address 0xfec00000, GSI 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
Enabling APIC mode: Flat. Using 1 I/O APICs
Using ACPI (MADT) for SMP configuration information
Allocating PCI resources starting at 50000000 (gap: 40000000:bec00000)
Built 1 zonelists in Zone order. Total pages: 259969
Kernel command line: root=/dev/hda4
mapped APIC to ffffb000 (fee00000)
mapped IOAPIC to ffffa000 (fec00000)
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 16384 bytes)
Detected 1600.106 MHz processor.
Console: colour VGA+ 80x25
console [tty0] enabled
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 1031468k/1048064k available (4703k kernel code, 15928k reserved, 1492k data, 228k init, 130496k highmem) virtual kernel memory layout:

    fixmap  : 0xfff9b000 - 0xfffff000   ( 400 kB)
    pkmap   : 0xff800000 - 0xffc00000   (4096 kB)
    vmalloc : 0xf8800000 - 0xff7fe000   ( 111 MB)
    lowmem  : 0xc0000000 - 0xf8000000   ( 896 MB)
      .init : 0xc0716000 - 0xc074f000   ( 228 kB)
      .data : 0xc0597fe0 - 0xc070d138   (1492 kB)
      .text : 0xc0100000 - 0xc0597fe0   (4703 kB)

Checking if this processor honours the WP bit even in supervisor mode... Ok.
SLUB: Genslabs=22, HWalign=32, Order=0-1, MinObjects=4, CPUs=2, Nodes=1
Calibrating delay using timer specific routine.. 3203.64 BogoMIPS (lpj=6407286) Mount-cache hash table entries: 512
CPU: After generic identify, caps: 0383fbff c1cbfbff 00000000 00000000 00000000 00000000 00000000 00000000
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 256K (64 bytes/line)
CPU: After all inits, caps: 0383fbff c1cbfbff 00000000 00000420 00000000 00000000 00000000 00000000 Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
Compat vDSO mapped to ffffe000.
Checking 'hlt' instruction... OK.
SMP alternatives: switching to UP code
ACPI: Core revision 20070126
CPU0: AMD Athlon(tm) MP 1900+ stepping 02
SMP alternatives: switching to SMP code
Booting processor 1/0 eip 3000
Initializing CPU#1
Calibrating delay using timer specific routine.. 3200.61 BogoMIPS (lpj=6401239)
CPU: After generic identify, caps: 0383fbff c1cbfbff 00000000 00000000 00000000 00000000 00000000 00000000
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 256K (64 bytes/line)
CPU: After all inits, caps: 0383fbff c1cbfbff 00000000 00000420 00000000 00000000 00000000 00000000 Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#1.
CPU1: AMD Athlon(tm) Processor stepping 02
Total of 2 processors activated (6404.26 BogoMIPS).
ENABLING IO-APIC IRQs
..TIMER: vector=0x31 apic1=0 pin1=2 apic2=0 pin2=0
Brought up 2 CPUs
xor: automatically using best checksumming function: pIII_sse
pIII_sse : 4311.000 MB/sec
xor: using function: pIII_sse (4311.000 MB/sec)
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: PCI BIOS revision 2.10 entry at 0xfd7d0, last bus=2
PCI: Using configuration type 1
Setting up standard PCI resources
mtrr: your CPUs had inconsistent fixed MTRR settings
mtrr: probably your BIOS does not setup all CPUs.
mtrr: corrected configuration.
ACPI: EC: Look up EC in DSDT
ACPI: Interpreter enabled
ACPI: (supports S0 S1 S5)
ACPI: Using IOAPIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (0000:00)
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGP_._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.OP2P._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 *5 10 11)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 5 10 *11)
ACPI: PCI Interrupt Link [LNKC] (IRQs *3 5 10 11)
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 5 *10 11)
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init
ACPI: bus type pnp registered
pnp: PnP ACPI: found 9 devices
ACPI: ACPI bus type pnp unregistered
SCSI subsystem initialized
libata version 2.21 loaded.
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
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 0xfffc0000-0xffffffff could not be reserved
pnp: 00:00: iomem range 0xffc00000-0xfff7ffff has been reserved
pnp: 00:00: iomem range 0x0-0x9ffff could not be reserved
pnp: 00:00: iomem range 0x100000-0x3fffffff could not be reserved
pnp: 00:06: ioport range 0x4d0-0x4d1 has been reserved
PCI: Bridge: 0000:00:01.0
IO window: disabled.
MEM window: f8000000-fbffffff
PREFETCH window: 50000000-500fffff
PCI: Bridge: 0000:00:10.0
IO window: 2000-2fff
MEM window: fc000000-fc0fffff
PREFETCH window: 50100000-502fffff
NET: Registered protocol family 2
Time: acpi_pm clocksource has been installed.
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 8, 1572864 bytes)
TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
Machine check exception polling timer started.
audit: initializing netlink socket (disabled)
audit(1203293519.376:1): initialized
highmem bounce pool size: 64 pages
Installing knfsd (copyright (C) 1996 [email protected]).
NTFS driver 2.1.28 [Flags: R/W].
SGI XFS with large block numbers, no debug enabled
async_tx: api initialized (sync-only)
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
BIOS failed to enable PCI standards compliance, fixing this error.
Boot video device is 0000:01:05.0
input: Power Button (FF) as /class/input/input0
ACPI: Power Button (FF) [PWRF]
input: Sleep Button (FF) as /class/input/input1
ACPI: Sleep Button (FF) [SLPF]
input: Power Button (CM) as /class/input/input2
ACPI: Power Button (CM) [PWRB]
lp: driver loaded but no devices found
Linux agpgart interface v0.102
agpgart: Detected AMD 760MP chipset
agpgart: AGP aperture is 32M @ 0x0
[drm] Initialized drm 1.1.0 20060810
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
Intel(R) PRO/1000 Network Driver - version 7.3.20-k2
Copyright (c) 1999-2006 Intel Corporation.
ACPI: PCI Interrupt 0000:02:04.0[A] -> GSI 16 (level, low) -> IRQ 16
e1000: 0000:02:04.0: e1000_probe: (PCI:33MHz:32-bit) 00:07:e9:0f:54:22
e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
ACPI: PCI Interrupt 0000:02:08.0[A] -> GSI 19 (level, low) -> IRQ 17
3c59x: Donald Becker and others.
0000:02:08.0: 3Com PCI 3c905C Tornado at f8826c00.
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
AMD7441: IDE controller at PCI slot 0000:00:07.1
AMD7441: chipset revision 4
AMD7441: not 100% native mode: will probe irqs later
AMD7441: 0000:00:07.1 (rev 04) UDMA100 controller

    ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA
    ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:pio

Probing IDE interface ide0...
hda: WDC WD300BB-00AUA1, ATA DISK drive
hdb: PIONEER DVD-RW DVR-112D, ATAPI CD/DVD-ROM drive
hda: selected mode 0x45
hdb: selected mode 0x44
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
hdc: WDC WD800JB-00CRA1, ATA DISK drive
hdc: selected mode 0x45
ide1 at 0x170-0x177,0x376 on irq 15
hda: max request size: 128KiB
hda: 58633344 sectors (30020 MB) w/2048KiB Cache, CHS=58168/16/63, UDMA(100)
hda: cache flushes not supported
hda: hda1 hda2 hda3 hda4
hdc: max request size: 128KiB
hdc: 156301488 sectors (80026 MB) w/8192KiB Cache, CHS=65535/16/63, UDMA(100)
hdc: cache flushes not supported
hdc: hdc1
hdb: ATAPI 40X DVD-ROM DVD-R CD-R/RW drive, 2000kB Cache, UDMA(66)
Uniform CD-ROM driver Revision: 3.20
sata_sil24 0000:02:05.0: version 1.0
ACPI: PCI Interrupt 0000:02:05.0[A] -> GSI 17 (level, low) -> IRQ 18
scsi0 : sata_sil24
scsi1 : sata_sil24
scsi2 : sata_sil24
scsi3 : sata_sil24
ata1: SATA max UDMA/100 cmd 0xf8830000 ctl 0x00000000 bmdma 0x00000000 irq 18
ata2: SATA max UDMA/100 cmd 0xf8832000 ctl 0x00000000 bmdma 0x00000000 irq 18
ata3: SATA max UDMA/100 cmd 0xf8834000 ctl 0x00000000 bmdma 0x00000000 irq 18
ata4: SATA max UDMA/100 cmd 0xf8836000 ctl 0x00000000 bmdma 0x00000000 irq 18
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata1.00: ATA-7: Maxtor 7H500F0, HA431DN0, max UDMA/133
ata1.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32)
ata1.00: configured for UDMA/100
ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata2.00: ATA-7: ST3500630AS, 3.AAE, max UDMA/133
ata2.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32)
ata2.00: configured for UDMA/100
ata3: SATA link down (SStatus 0 SControl 300)
ata4: SATA link down (SStatus 0 SControl 300)
scsi 0:0:0:0: Direct-Access ATA Maxtor 7H500F0 HA43 PQ: 0 ANSI: 5
sd 0:0:0:0: [sda] 976773168 512-byte hardware sectors (500108 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: disabled, read cache: enabled, doesn't support DPO or FUA
sd 0:0:0:0: [sda] 976773168 512-byte hardware sectors (500108 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: disabled, read cache: enabled, doesn't support DPO or FUA
sda: sda1
sd 0:0:0:0: [sda] Attached SCSI disk
sd 0:0:0:0: Attached scsi generic sg0 type 0
scsi 1:0:0:0: Direct-Access ATA ST3500630AS 3.AA PQ: 0 ANSI: 5
sd 1:0:0:0: [sdb] 976773168 512-byte hardware sectors (500108 MB)
sd 1:0:0:0: [sdb] Write Protect is off
sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 1:0:0:0: [sdb] 976773168 512-byte hardware sectors (500108 MB)
sd 1:0:0:0: [sdb] Write Protect is off
sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdb: sdb1
sd 1:0:0:0: [sdb] Attached SCSI disk
sd 1:0:0:0: Attached scsi generic sg1 type 0
ACPI: PCI Interrupt 0000:02:06.0[A] -> GSI 18 (level, low) -> IRQ 19
scsi4 : sata_sil24
scsi5 : sata_sil24
scsi6 : sata_sil24
scsi7 : sata_sil24
ata5: SATA max UDMA/100 cmd 0xf8870000 ctl 0x00000000 bmdma 0x00000000 irq 19
ata6: SATA max UDMA/100 cmd 0xf8872000 ctl 0x00000000 bmdma 0x00000000 irq 19
ata7: SATA max UDMA/100 cmd 0xf8874000 ctl 0x00000000 bmdma 0x00000000 irq 19
ata8: SATA max UDMA/100 cmd 0xf8876000 ctl 0x00000000 bmdma 0x00000000 irq 19
ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata5.00: ATA-7: ST3500630AS, 3.AAE, max UDMA/133
ata5.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32)
ata5.00: configured for UDMA/100
ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata6.00: ATA-7: Maxtor 7H500F0, HA431DN0, max UDMA/133
ata6.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32)
ata6.00: configured for UDMA/100
ata7: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata7.00: ATA-7: ST3500641AS, 3.AAH, max UDMA/133
ata7.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32)
ata7.00: configured for UDMA/100
ata8: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata8.00: ATA-7: ST3500641AS, 3.AAJ, max UDMA/133
ata8.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32)
ata8.00: configured for UDMA/100
scsi 4:0:0:0: Direct-Access ATA ST3500630AS 3.AA PQ: 0 ANSI: 5
sd 4:0:0:0: [sdc] 976773168 512-byte hardware sectors (500108 MB)
sd 4:0:0:0: [sdc] Write Protect is off
sd 4:0:0:0: [sdc] Mode Sense: 00 3a 00 00
sd 4:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 4:0:0:0: [sdc] 976773168 512-byte hardware sectors (500108 MB)
sd 4:0:0:0: [sdc] Write Protect is off
sd 4:0:0:0: [sdc] Mode Sense: 00 3a 00 00
sd 4:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdc: sdc1
sd 4:0:0:0: [sdc] Attached SCSI disk
sd 4:0:0:0: Attached scsi generic sg2 type 0
scsi 5:0:0:0: Direct-Access ATA Maxtor 7H500F0 HA43 PQ: 0 ANSI: 5
sd 5:0:0:0: [sdd] 976773168 512-byte hardware sectors (500108 MB)
sd 5:0:0:0: [sdd] Write Protect is off
sd 5:0:0:0: [sdd] Mode Sense: 00 3a 00 00
sd 5:0:0:0: [sdd] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
sd 5:0:0:0: [sdd] 976773168 512-byte hardware sectors (500108 MB)
sd 5:0:0:0: [sdd] Write Protect is off
sd 5:0:0:0: [sdd] Mode Sense: 00 3a 00 00
sd 5:0:0:0: [sdd] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
sdd: sdd1
sd 5:0:0:0: [sdd] Attached SCSI disk
sd 5:0:0:0: Attached scsi generic sg3 type 0
scsi 6:0:0:0: Direct-Access ATA ST3500641AS 3.AA PQ: 0 ANSI: 5
sd 6:0:0:0: [sde] 976773168 512-byte hardware sectors (500108 MB)
sd 6:0:0:0: [sde] Write Protect is off
sd 6:0:0:0: [sde] Mode Sense: 00 3a 00 00
sd 6:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 6:0:0:0: [sde] 976773168 512-byte hardware sectors (500108 MB)
sd 6:0:0:0: [sde] Write Protect is off
sd 6:0:0:0: [sde] Mode Sense: 00 3a 00 00
sd 6:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sde: sde1
sd 6:0:0:0: [sde] Attached SCSI disk
sd 6:0:0:0: Attached scsi generic sg4 type 0
scsi 7:0:0:0: Direct-Access ATA ST3500641AS 3.AA PQ: 0 ANSI: 5
sd 7:0:0:0: [sdf] 976773168 512-byte hardware sectors (500108 MB)
sd 7:0:0:0: [sdf] Write Protect is off
sd 7:0:0:0: [sdf] Mode Sense: 00 3a 00 00
sd 7:0:0:0: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 7:0:0:0: [sdf] 976773168 512-byte hardware sectors (500108 MB)
sd 7:0:0:0: [sdf] Write Protect is off
sd 7:0:0:0: [sdf] Mode Sense: 00 3a 00 00
sd 7:0:0:0: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdf: sdf1
sd 7:0:0:0: [sdf] Attached SCSI disk
sd 7:0:0:0: Attached scsi generic sg5 type 0
ACPI: PCI Interrupt 0000:02:07.0[A] -> GSI 19 (level, low) -> IRQ 17
scsi8 : sata_sil24
scsi9 : sata_sil24
scsi10 : sata_sil24
scsi11 : sata_sil24
ata9: SATA max UDMA/100 cmd 0xf8880000 ctl 0x00000000 bmdma 0x00000000 irq 17
ata10: SATA max UDMA/100 cmd 0xf8882000 ctl 0x00000000 bmdma 0x00000000 irq 17
ata11: SATA max UDMA/100 cmd 0xf8884000 ctl 0x00000000 bmdma 0x00000000 irq 17
ata12: SATA max UDMA/100 cmd 0xf8886000 ctl 0x00000000 bmdma 0x00000000 irq 17
ata9: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata9.00: ATA-7: ST3500630AS, 3.AAK, max UDMA/133
ata9.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32)
ata9.00: configured for UDMA/100
ata10: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata10.00: ATA-7: ST3500630AS, 3.AAK, max UDMA/133
ata10.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32)
ata10.00: configured for UDMA/100
ata11: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata11.00: ATA-7: ST3500641AS, 3.AAJ, max UDMA/133
ata11.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32)
ata11.00: configured for UDMA/100
ata12: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata12.00: ATA-7: ST3500630AS, 3.AAK, max UDMA/133
ata12.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32)
ata12.00: configured for UDMA/100
scsi 8:0:0:0: Direct-Access ATA ST3500630AS 3.AA PQ: 0 ANSI: 5
sd 8:0:0:0: [sdg] 976773168 512-byte hardware sectors (500108 MB)
sd 8:0:0:0: [sdg] Write Protect is off
sd 8:0:0:0: [sdg] Mode Sense: 00 3a 00 00
sd 8:0:0:0: [sdg] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 8:0:0:0: [sdg] 976773168 512-byte hardware sectors (500108 MB)
sd 8:0:0:0: [sdg] Write Protect is off
sd 8:0:0:0: [sdg] Mode Sense: 00 3a 00 00
sd 8:0:0:0: [sdg] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdg: sdg1
sd 8:0:0:0: [sdg] Attached SCSI disk
sd 8:0:0:0: Attached scsi generic sg6 type 0
scsi 9:0:0:0: Direct-Access ATA ST3500630AS 3.AA PQ: 0 ANSI: 5
sd 9:0:0:0: [sdh] 976773168 512-byte hardware sectors (500108 MB)
sd 9:0:0:0: [sdh] Write Protect is off
sd 9:0:0:0: [sdh] Mode Sense: 00 3a 00 00
sd 9:0:0:0: [sdh] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 9:0:0:0: [sdh] 976773168 512-byte hardware sectors (500108 MB)
sd 9:0:0:0: [sdh] Write Protect is off
sd 9:0:0:0: [sdh] Mode Sense: 00 3a 00 00
sd 9:0:0:0: [sdh] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdh: sdh1
sd 9:0:0:0: [sdh] Attached SCSI disk
sd 9:0:0:0: Attached scsi generic sg7 type 0
scsi 10:0:0:0: Direct-Access ATA ST3500641AS 3.AA PQ: 0 ANSI: 5
sd 10:0:0:0: [sdi] 976773168 512-byte hardware sectors (500108 MB)
sd 10:0:0:0: [sdi] Write Protect is off
sd 10:0:0:0: [sdi] Mode Sense: 00 3a 00 00
sd 10:0:0:0: [sdi] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 10:0:0:0: [sdi] 976773168 512-byte hardware sectors (500108 MB)
sd 10:0:0:0: [sdi] Write Protect is off
sd 10:0:0:0: [sdi] Mode Sense: 00 3a 00 00
sd 10:0:0:0: [sdi] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdi: sdi1
sd 10:0:0:0: [sdi] Attached SCSI disk
sd 10:0:0:0: Attached scsi generic sg8 type 0
scsi 11:0:0:0: Direct-Access ATA ST3500630AS 3.AA PQ: 0 ANSI: 5
sd 11:0:0:0: [sdj] 976773168 512-byte hardware sectors (500108 MB)
sd 11:0:0:0: [sdj] Write Protect is off
sd 11:0:0:0: [sdj] Mode Sense: 00 3a 00 00
sd 11:0:0:0: [sdj] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 11:0:0:0: [sdj] 976773168 512-byte hardware sectors (500108 MB)
sd 11:0:0:0: [sdj] Write Protect is off
sd 11:0:0:0: [sdj] Mode Sense: 00 3a 00 00
sd 11:0:0:0: [sdj] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdj: sdj1
sd 11:0:0:0: [sdj] Attached SCSI disk
sd 11:0:0:0: Attached scsi generic sg9 type 0
ieee1394: raw1394: /dev/raw1394 device initialized
usbmon: debugfs is not available
ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver
ACPI: PCI Interrupt 0000:02:00.0[D] -> GSI 19 (level, low) -> IRQ 17
ohci_hcd 0000:02:00.0: OHCI Host Controller
ohci_hcd 0000:02:00.0: new USB bus registered, assigned bus number 1
ohci_hcd 0000:02:00.0: irq 17, io mem 0xfc018000
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 4 ports detected
usb 1-4: new low speed USB device using ohci_hcd and address 2
usb 1-4: device descriptor read/64, error -62
usb 1-4: device descriptor read/64, error -62
usb 1-4: new low speed USB device using ohci_hcd and address 3
usb 1-4: device descriptor read/64, error -62
usb 1-4: device descriptor read/64, error -62
usb 1-4: new low speed USB device using ohci_hcd and address 4
usb 1-4: device not accepting address 4, error -62
usb 1-4: new low speed USB device using ohci_hcd and address 5
usb 1-4: device not accepting address 5, error -62
usbcore: registered new interface driver usblp
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1
PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
serio: i8042 KBD port at 0x60,0x64 irq 1
mice: PS/2 mouse device common for all mice
input: AT Translated Set 2 keyboard as /class/input/input3
md: raid0 personality registered for level 0
md: raid1 personality registered for level 1
md: raid10 personality registered for level 10
raid6: int32x1 658 MB/s
raid6: int32x2 853 MB/s
raid6: int32x4 549 MB/s
raid6: int32x8 508 MB/s
raid6: mmxx1 1311 MB/s
raid6: mmxx2 2258 MB/s
raid6: sse1x1 468 MB/s
raid6: sse1x2 936 MB/s
raid6: using algorithm sse1x2 (936 MB/s)
md: raid6 personality registered for level 6
md: raid5 personality registered for level 5
md: raid4 personality registered for level 4
device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: [email protected]
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 (Fri Jul 20 09:12:58 2007 UTC).
ALSA device list:
No soundcards found.
Netfilter messages via NETLINK v0.30.
nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
ctnetlink v0.93: registering with nfnetlink.
ip_tables: (C) 2000-2006 Netfilter Core Team
ClusterIP Version 0.8 loaded successfully
arp_tables: (C) 2002 David S. Miller
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
Starting balanced_irq
Using IPI No-Shortcut mode
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
ReiserFS: hda4: found reiserfs format "3.6" with standard journal
ReiserFS: hda4: using ordered data mode
ReiserFS: hda4: journal params: device hda4, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: hda4: checking transaction log (hda4)
ReiserFS: hda4: Using r5 hash to sort names
VFS: Mounted root (reiserfs filesystem) readonly.
Freeing unused kernel memory: 228k freed
AMD768 RNG detected
Real Time Clock Driver v1.12ac
floppy0: no floppy controllers found
hpt374: module license 'Proprietary' taints kernel.
HPT374 UDMA/ATA133 RAID Controller driver
Version 2.17, Compiled Dec 9 2007 18:19:24
RAID5 write-back enabled
ACPI: PCI Interrupt 0000:00:09.0[A] -> GSI 21 (level, low) -> IRQ 20
ACPI: PCI Interrupt 0000:00:09.1[A] -> GSI 21 (level, low) -> IRQ 20
scsi12 : hpt374
scsi 12:0:0:0: Direct-Access HPT3xx RAID 5 Array 3.00 PQ: 0 ANSI: 0
sd 12:0:0:0: [sdk] 976793600 512-byte hardware sectors (500118 MB)
sd 12:0:0:0: [sdk] Write Protect is off
sd 12:0:0:0: [sdk] Mode Sense: 2f 00 00 00
sd 12:0:0:0: [sdk] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 12:0:0:0: [sdk] 976793600 512-byte hardware sectors (500118 MB)
sd 12:0:0:0: [sdk] Write Protect is off
sd 12:0:0:0: [sdk] Mode Sense: 2f 00 00 00
sd 12:0:0:0: [sdk] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdk: sdk1
sd 12:0:0:0: [sdk] Attached SCSI disk
sd 12:0:0:0: Attached scsi generic sg10 type 0
w83781d 0-002c: The W83627HF chip is better supported by the w83627hf driver, support will be dropped from the w83781d driver soon aufs 20071203
kjournald starting. Commit interval 5 seconds
EXT3 FS on hda3, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
EXT3 FS on hdc1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
XFS mounting filesystem sdk1
Ending clean XFS mount for filesystem: sdk1
XFS mounting filesystem sdj1
Ending clean XFS mount for filesystem: sdj1
XFS mounting filesystem sdc1
Ending clean XFS mount for filesystem: sdc1
XFS mounting filesystem sdi1
Ending clean XFS mount for filesystem: sdi1
XFS mounting filesystem sdh1
Ending clean XFS mount for filesystem: sdh1
XFS mounting filesystem sdg1
Ending clean XFS mount for filesystem: sdg1
XFS mounting filesystem sdf1
Ending clean XFS mount for filesystem: sdf1
XFS mounting filesystem sda1
Ending clean XFS mount for filesystem: sda1
XFS mounting filesystem sdb1
Ending clean XFS mount for filesystem: sdb1
XFS mounting filesystem sde1
Ending clean XFS mount for filesystem: sde1
XFS mounting filesystem sdd1
Ending clean XFS mount for filesystem: sdd1
Adding 530136k swap on /dev/hda2. Priority:-1 extents:1 across:530136k
hda: selected mode 0x45
hdb: selected mode 0x44
hdc: selected mode 0x45
e1000: eth0: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
eth1: setting half-duplex.
NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
NFSD: starting 90-second grace period
w83627hf: Found W83627HF chip at 0xc00
PPP generic driver version 2.4.2
PPP BSD Compression module registered

Gabor FUNK

2008-03-02 09:59 UTC #5 lore raw

I have/had a similar (hard resetting) problem (2+8 disks, kernel 2.6.24), see thread:
http://www.mail-archive.com/[email protected]/msg15950.html

I tried replacing the PSU and also run the system with two 650W PSU-s, also failed. I also think that PSU shouldn't be the problem as I see they eat much less in operation than at spinup.

Now I replaced the MB and it runs with a different Gigabyte MB with the 8 disk in SW RAID6 connected to the 2*4 on board SATA connectors (these now use 2+4*ata_piix and 2 ahci kernel drivers) and the 2 system disk is on an add-on Silicon Image SiI 3512 card.

Since the problem is not seen immediately I can't tell whether it is better now. It is running cp 1 2, cp 2 3... to 2500 or so, with 1GB files then md5sums them, so far the problem not exhibiting. The 1st copy didn't finish in a day, so accidentally a second one got started (cron) and yesterday an "md: data-check" also started, so the system is quite busy now doing disk reads/writes...

G.

----- Original Message ----- From: "Denys Dmytriyenko" <[email protected]>
To: <[email protected]>
Cc: "Jim Paris" <[email protected]>; "Mark Lord" <[email protected]>
Sent: Sunday, March 02, 2008 7:14 AM
Subject: Re: sata_sil24 stability and performance

Quoted 40 lines · Mark Lord

Quoted 13 lines
Quoted 3 lines · Jim Paris
..
As you may have noticed on this list, power supplies are very frequently a problem.
..
Actually, no, I haven't noticed that. :)
I do see them more frequently being suggested as a possible problem, and then after some time and expense on the part of the reporters it nearly always turns out to have been a device driver bug, or (less often) a firmware quirk of the device.
Quoted 5 lines
Yes, PSUs are often suggested as a problem here,
but only rarely has that been true.
Especially nowadays, as PSUs are becoming much larger than they historically once were.
Hi again. Thanks for your replies and sorry for bringing this up again. I am still trying to resolve those 2 issues I mentioned in the first email. While playing with different power options lately, I decided to replace the PSU again for a single-rail Silencer 750 EPS12V, which is rated at 60A (!) for a single 12V rail. Does anybody have any experience with it? Can anyone suggest anything better?
That is assuming the first issue with exceptions and resets is due to the power being maxed out...
Meanwhile I would still like to resolve the low performance issue with SiI 3124, which shows only 17 MB/s write speed doing "dd if=/dev/zero", while Intel ICH7 based PC writes at 44 MB/s sustained rate. I'd really appreciate any ideas/suggestions towards solving this issue. Please let me know if any other information is needed. I'm attaching the original email with logs. Thanks in advance!
Signature · 1 line
Denys

Tejun Heo

2008-03-04 00:02 UTC #6 lore raw

Hello, Gabor.

Quoted 7 lines · Gabor FUNK

I have/had a similar (hard resetting) problem (2+8 disks, kernel 2.6.24), see thread:
http://www.mail-archive.com/[email protected]/msg15950.html
I tried replacing the PSU and also run the system with two 650W PSU-s, also failed. I also think that PSU shouldn't be the problem as I see they eat much less in operation than at spinup.

It's not that simple tho. Some PSUs which happily spin up all the drives simultaneously have problems maintaining stable operation afterwards. Anyways, if you used two separate PSUs, and didn't see any change in failure pattern (ie. drives connected to certain PSU fails or swapping to which PSU the board is connected alleviates the problem), it's probably safe to say it's not PSU problem.

Quoted 11 lines

Now I replaced the MB and it runs with a different Gigabyte MB with the 8 disk in SW RAID6 connected to the 2*4 on board SATA connectors (these now use 2+4*ata_piix and 2 ahci kernel drivers) and the 2 system disk is on an add-on Silicon Image SiI 3512 card.
Since the problem is not seen immediately I can't tell whether it is better now. It is running cp 1 2, cp 2 3... to 2500 or so, with 1GB files then md5sums them, so far the problem not exhibiting. The 1st copy didn't finish in a day, so accidentally a second one got started (cron) and yesterday an "md: data-check" also started, so the system is quite busy now doing disk reads/writes...

Hmmm... Is it still okay?

Signature · 1 line

tejun

Denys Dmytriyenko

author

2008-03-04 00:22 UTC #7 lore raw

Quoted 11 lines · Tejun Heo

Hello, Gabor.
Quoted 7 lines · Gabor FUNK
I have/had a similar (hard resetting) problem (2+8 disks, kernel 2.6.24), see thread:
http://www.mail-archive.com/[email protected]/msg15950.html
I tried replacing the PSU and also run the system with two 650W PSU-s, also failed. I also think that PSU shouldn't be the problem as I see they eat much less in operation than at spinup.

Quoted 6 lines

It's not that simple tho. Some PSUs which happily spin up all the drives simultaneously have problems maintaining stable operation afterwards. Anyways, if you used two separate PSUs, and didn't see any change in failure pattern (ie. drives connected to certain PSU fails or swapping to which PSU the board is connected alleviates the problem), it's probably safe to say it's not PSU problem.

Gabor,

I am pretty much convinced at this point that my exceptions/resetting problem is due to the PSU. I've been testing different configurations lately and was able to get stable system powering 14 (!) drives by both PSUs together. The limiting factor is Amps on a single +12V rail:
Coolermaster 750 limits single rail to 19A (6 drives @ 2.8A/drive) and my old Enermax 550 has 24A limit (8 drives @ 2.8A/drive). Even though Coolermaster 750 has 4 rails, the wiring is not optimal and only 1 rail is available for the hard drives...

See item #8 here:
http://www.pcpower.com/technology/myths/

I am going to try their single-rail Silencer 750, rated at 60A.

That said, I'm still puzzled with the low write performance issue.

Tejun,

As one of the Gurus on this list, can you suggest any tweaks/settings to try out to improve/resolve my 17 MB/s write speed limit?

I played with different PCI latencies, read FAQ topic on 32-bit I/O support in libata and ran out of ideas... Please help :)

Regards,
Denys

Tejun Heo

2008-03-04 03:28 UTC #8 lore raw

Hello, Denys.

Quoted 21 lines · Denys Dmytriyenko

Quoted 9 lines
Quoted 3 lines
I tried replacing the PSU and also run the system with two 650W PSU-s, also failed. I also think that PSU shouldn't be the problem as I see they eat much less in operation than at spinup.
It's not that simple tho. Some PSUs which happily spin up all the drives simultaneously have problems maintaining stable operation afterwards. Anyways, if you used two separate PSUs, and didn't see any change in failure pattern (ie. drives connected to certain PSU fails or swapping to which PSU the board is connected alleviates the problem), it's probably safe to say it's not PSU problem.
Gabor,
I am pretty much convinced at this point that my exceptions/resetting problem is due to the PSU. I've been testing different configurations lately and was able to get stable system powering 14 (!) drives by both PSUs together. The limiting factor is Amps on a single +12V rail:
Coolermaster 750 limits single rail to 19A (6 drives @ 2.8A/drive) and my old Enermax 550 has 24A limit (8 drives @ 2.8A/drive). Even though Coolermaster 750 has 4 rails, the wiring is not optimal and only 1 rail is available for the hard drives...

Quoted 2 lines

See item #8 here:
http://www.pcpower.com/technology/myths/

Ah... yeah, that's what I've been saying all along. Fancy powers w/ multiple 12v rails suck for storage array. My 15$ no name single lane PSU works much better than 40$ dual lane one.

Another interesting test to perform is to test drive hotplugging while all other drives are running. Good PSU should be able to hold the voltage and all other drives won't be affected but many PSUs fail to hold the 12v voltage and other drives sharing lane looses power briefly causing PHY events and brief spin downs (clicking sound) which usually result in loss of data in write buffer. Again, on my test setup, the $15 no name single lane one is most stable.

If anyone has some contacts to sites which perform PSU benchmarking, I would love to see PSUs tested for disk hotplugging which is a common operation nowadays and can cause serious file system failure if PSU isn't adequate.

Quoted 11 lines

I am going to try their single-rail Silencer 750, rated at 60A.
That said, I'm still puzzled with the low write performance issue.
Tejun,
As one of the Gurus on this list, can you suggest any tweaks/settings to try out to improve/resolve my 17 MB/s write speed limit?
I played with different PCI latencies, read FAQ topic on 32-bit I/O support in libata and ran out of ideas... Please help :)

How did you test? W/ dd? hdparm?

Signature · 1 line

tejun

Denys Dmytriyenko

author

2008-03-04 06:30 UTC #9 lore raw

Quoted 9 lines · Tejun Heo

Quoted 9 lines
I am pretty much convinced at this point that my exceptions/resetting problem is due to the PSU. I've been testing different configurations lately and was able to get stable system powering 14 (!) drives by both PSUs together. The limiting factor is Amps on a single +12V rail:
Coolermaster 750 limits single rail to 19A (6 drives @ 2.8A/drive) and my old Enermax 550 has 24A limit (8 drives @ 2.8A/drive). Even though Coolermaster 750 has 4 rails, the wiring is not optimal and only 1 rail is available for the hard drives...

Quoted 6 lines

Quoted 2 lines
See item #8 here:
http://www.pcpower.com/technology/myths/
Ah... yeah, that's what I've been saying all along. Fancy powers w/ multiple 12v rails suck for storage array. My 15$ no name single lane PSU works much better than 40$ dual lane one.

I've got the first exception (but not reset) in several days running in the above configuration:

Mar  3 19:09:04 [kernel] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Mar  3 19:09:04 [kernel] ata1.00: irq_stat 0x00020002, device error via D2H FIS
Mar  3 19:09:04 [kernel] ata1.00: cmd ef/42:fe:00:00:00/00:00:00:00:00/40 tag 0 cdb 0x0 data 0
Mar  3 19:09:04 [kernel]          res 51/04:fe:00:00:00/00:00:00:00:00/40 Emask 0x1 (device error)
Mar  3 19:09:04 [kernel] ata1.00: configured for UDMA/100
Mar  3 19:09:04 [kernel] ata1: EH complete
Mar  3 19:09:04 [kernel] sd 0:0:0:0: [sda] 976773168 512-byte hardware sectors (500108 MB)
Mar  3 19:09:04 [kernel] sd 0:0:0:0: [sda] Write Protect is off
Mar  3 19:09:04 [kernel] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Mar  3 19:09:04 [kernel] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

Is it something I should be worried about?

Quoted 6 lines

Quoted 4 lines
Tejun,
As one of the Gurus on this list, can you suggest any tweaks/settings to try out to improve/resolve my 17 MB/s write speed limit?
How did you test? W/ dd? hdparm?

# hdparm -t /dev/sda

/dev/sda:
Timing buffered disk reads: 170 MB in 3.03 seconds = 56.16 MB/sec

# dd if=/dev/zero of=file bs=100M count=20
20+0 records in
20+0 records out
2097152000 bytes (2.1 GB) copied, 117.053 s, 17.9 MB/s

# dd if=file of=file1 bs=100M count=20
20+0 records in
20+0 records out
2097152000 bytes (2.1 GB) copied, 161.721 s, 13.0 MB/s

# dd if=file of=/dev/null bs=100M count=20
20+0 records in
20+0 records out
2097152000 bytes (2.1 GB) copied, 34.6141 s, 60.6 MB/s

A similar drive in an ICH7 box shows more consistent results:

# hdparm -t /dev/sda

/dev/sda:
Timing buffered disk reads: 182 MB in 3.01 seconds = 60.48 MB/sec

# dd if=/dev/zero of=file bs=100M count=100
100+0 records in
100+0 records out
10485760000 bytes (10 GB) copied, 242.908 s, 43.2 MB/s

# dd if=file of=/dev/null bs=100M count=100
100+0 records in
100+0 records out
10485760000 bytes (10 GB) copied, 211.132 s, 49.7 MB/s

Please let me know if you need more details/logs. Thanks in advance!

Regards,
Denys

Tejun Heo

2008-03-05 08:11 UTC #10 lore raw

Quoted 14 lines · Denys Dmytriyenko

I've got the first exception (but not reset) in several days running in the above configuration:

Mar  3 19:09:04 [kernel] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Mar  3 19:09:04 [kernel] ata1.00: irq_stat 0x00020002, device error via D2H FIS
Mar  3 19:09:04 [kernel] ata1.00: cmd ef/42:fe:00:00:00/00:00:00:00:00/40 tag 0 cdb 0x0 data 0
Mar  3 19:09:04 [kernel]          res 51/04:fe:00:00:00/00:00:00:00:00/40 Emask 0x1 (device error)
Mar  3 19:09:04 [kernel] ata1.00: configured for UDMA/100
Mar  3 19:09:04 [kernel] ata1: EH complete
Mar  3 19:09:04 [kernel] sd 0:0:0:0: [sda] 976773168 512-byte hardware sectors (500108 MB)
Mar  3 19:09:04 [kernel] sd 0:0:0:0: [sda] Write Protect is off
Mar  3 19:09:04 [kernel] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Mar  3 19:09:04 [kernel] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

Quoted 1 line

Is it something I should be worried about?

That's the drive rejecting acoustic setting command probably because the drive doesn't support it. Nothing to worry about. More recent kernels won't whine about those anymore.

Quoted 8 lines

Quoted 3 lines
Quoted 2 lines
As one of the Gurus on this list, can you suggest any tweaks/settings to try out to improve/resolve my 17 MB/s write speed limit?
How did you test? W/ dd? hdparm?
# hdparm -t /dev/sda
/dev/sda:
Timing buffered disk reads: 170 MB in 3.03 seconds = 56.16 MB/sec

This doesn't look too bad.

Quoted 9 lines

# dd if=/dev/zero of=file bs=100M count=20
20+0 records in
20+0 records out
2097152000 bytes (2.1 GB) copied, 117.053 s, 17.9 MB/s

# dd if=file of=file1 bs=100M count=20
20+0 records in
20+0 records out
2097152000 bytes (2.1 GB) copied, 161.721 s, 13.0 MB/s

Write seems awfully sluggish. Does turning off NCQ help? You can turn off NCQ by echoing 1 to /sys/block/sdX/device/queue_depth. Also, which kernel is this test result from?

Quoted 4 lines

# dd if=file of=/dev/null bs=100M count=20
20+0 records in
20+0 records out
2097152000 bytes (2.1 GB) copied, 34.6141 s, 60.6 MB/s

Read looks okay.

Quoted 12 lines

A similar drive in an ICH7 box shows more consistent results:
# hdparm -t /dev/sda
/dev/sda:
Timing buffered disk reads: 182 MB in 3.01 seconds = 60.48 MB/sec
# dd if=/dev/zero of=file bs=100M count=100
100+0 records in
100+0 records out
10485760000 bytes (10 GB) copied, 242.908 s, 43.2 MB/s

Quoted 4 lines

# dd if=file of=/dev/null bs=100M count=100
100+0 records in
100+0 records out
10485760000 bytes (10 GB) copied, 211.132 s, 49.7 MB/s

Hmmm... indeed. Same kernel version? Can you post "hdparm -I" results of both drives?

Signature · 1 line

tejun

Denys Dmytriyenko

author

2008-03-06 04:15 UTC #11 lore raw

Quoted 3 lines · Tejun Heo

That's the drive rejecting acoustic setting command probably because the drive doesn't support it. Nothing to worry about. More recent kernels won't whine about those anymore.

Oh, thanks. I forgot that I tried to change acoustic setting.

Quoted 5 lines

# dd if=/dev/zero of=file bs=100M count=20
20+0 records in
20+0 records out
2097152000 bytes (2.1 GB) copied, 117.053 s, 17.9 MB/s

Quoted 8 lines

Quoted 4 lines
# dd if=file of=file1 bs=100M count=20
20+0 records in
20+0 records out
2097152000 bytes (2.1 GB) copied, 161.721 s, 13.0 MB/s
Write seems awfully sluggish. Does turning off NCQ help? You can turn off NCQ by echoing 1 to /sys/block/sdX/device/queue_depth. Also, which kernel is this test result from?

Turning off NCQ does not help. I am currently on 2.6.23.9, but I just tried 2.6.25-rc4 and it is the same.

Quoted 12 lines

Quoted 12 lines
A similar drive in an ICH7 box shows more consistent results:
# hdparm -t /dev/sda
/dev/sda:
Timing buffered disk reads: 182 MB in 3.01 seconds = 60.48 MB/sec
# dd if=/dev/zero of=file bs=100M count=100
100+0 records in
100+0 records out
10485760000 bytes (10 GB) copied, 242.908 s, 43.2 MB/s

Quoted 7 lines

Quoted 4 lines
# dd if=file of=/dev/null bs=100M count=100
100+0 records in
100+0 records out
10485760000 bytes (10 GB) copied, 211.132 s, 49.7 MB/s
Hmmm... indeed. Same kernel version? Can you post "hdparm -I" results of both drives?

The kernel on the second box is also 2.6.23.9. Here are hdparm results for identical drives:

1. Connected to SiI 3124/sata_sil24 w/ slow write:

# hdparm -I /dev/sda

/dev/sda:

ATA device, with non-removable media

        Model Number:       WDC WD1600JS-75NCB1
        Serial Number:      WD-WCANM1344866
        Firmware Revision:  10.02E01

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

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

Capabilities:
LBA, IORDY(can be disabled)
Queue depth: 32
Standby timer values: spec'd by Standard, with device specific minimum R/W multiple sector transfer: Max = 16 Current = 16 Recommended acoustic management value: 128, current value: 128
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5 udma6
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=120ns IORDY flow control=120ns
Commands/features:
Enabled Supported:
* SMART feature set
Security Mode feature set
* Power Management feature set
* Write cache
* Look-ahead
* Host Protected Area feature set
* WRITE_BUFFER command
* READ_BUFFER command
* NOP cmd
* DOWNLOAD_MICROCODE
SET_MAX security extension
* Automatic Acoustic Management feature set
* 48-bit Address feature set
* Device Configuration Overlay feature set
* Mandatory FLUSH_CACHE
* FLUSH_CACHE_EXT
* SMART error logging
* SMART self-test
* General Purpose Logging feature set
* SATA-I signaling speed (1.5Gb/s)
* SATA-II signaling speed (3.0Gb/s)
* Native Command Queueing (NCQ)
* Host-initiated interface power management
* Phy event counters
DMA Setup Auto-Activate optimization Device-initiated interface power management
* Software settings preservation
* SMART Command Transport (SCT) feature set
* SCT Long Sector Access (AC1)
* SCT LBA Segment Access (AC2)
* SCT Error Recovery Control (AC3)
* SCT Features Control (AC4)
* SCT Data Tables (AC5)
unknown 206[12]
Security:
supported
not enabled
not locked
not frozen
not expired: security count
not supported: enhanced erase
Checksum: correct

2. Connected to ICH7/ata_piix w/ normal write:

# hdparm -I /dev/sda

/dev/sda:

ATA device, with non-removable media

        Model Number:       WDC WD1600JS-75NCB1
        Serial Number:      WD-WCANM1356774
        Firmware Revision:  10.02E01

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

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

Capabilities:
LBA, IORDY(can be disabled)
Queue depth: 32
Standby timer values: spec'd by Standard, with device specific minimum R/W multiple sector transfer: Max = 16 Current = 16 Recommended acoustic management value: 128, current value: 254
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=120ns IORDY flow control=120ns
Commands/features:
Enabled Supported:
* SMART feature set
Security Mode feature set
* Power Management feature set
* Write cache
* Look-ahead
* Host Protected Area feature set
* WRITE_BUFFER command
* READ_BUFFER command
* NOP cmd
* DOWNLOAD_MICROCODE
SET_MAX security extension
* Automatic Acoustic Management feature set
* 48-bit Address feature set
* Device Configuration Overlay feature set
* Mandatory FLUSH_CACHE
* FLUSH_CACHE_EXT
* SMART error logging
* SMART self-test
* General Purpose Logging feature set
* SATA-I signaling speed (1.5Gb/s)
* SATA-II signaling speed (3.0Gb/s)
* Native Command Queueing (NCQ)
* Host-initiated interface power management
* Phy event counters
DMA Setup Auto-Activate optimization Device-initiated interface power management
* Software settings preservation
* SMART Command Transport (SCT) feature set
* SCT Long Sector Access (AC1)
* SCT LBA Segment Access (AC2)
* SCT Error Recovery Control (AC3)
* SCT Features Control (AC4)
* SCT Data Tables (AC5)
unknown 206[12]
Security:
supported
not enabled
not locked
frozen
not expired: security count
not supported: enhanced erase
Checksum: correct

Also, few months ago instead of sata_sil24 I had my drives connected to sata_mv (Supermicro 8-port) and performance was normal...

Thank you for your time. Please let me know what else to try.

Regards,
Denys

Tejun Heo

2008-03-06 04:25 UTC #12 lore raw

Quoted 60 lines · Denys Dmytriyenko

Quoted 3 lines · Tejun Heo
That's the drive rejecting acoustic setting command probably because the drive doesn't support it. Nothing to worry about. More recent kernels won't whine about those anymore.
Oh, thanks. I forgot that I tried to change acoustic setting.
Quoted 5 lines
Quoted 5 lines
# dd if=/dev/zero of=file bs=100M count=20
20+0 records in
20+0 records out
2097152000 bytes (2.1 GB) copied, 117.053 s, 17.9 MB/s
Quoted 7 lines
Quoted 4 lines
# dd if=file of=file1 bs=100M count=20
20+0 records in
20+0 records out
2097152000 bytes (2.1 GB) copied, 161.721 s, 13.0 MB/s
Write seems awfully sluggish. Does turning off NCQ help? You can turn off NCQ by echoing 1 to /sys/block/sdX/device/queue_depth. Also, which kernel is this test result from?
Turning off NCQ does not help. I am currently on 2.6.23.9, but I just tried 2.6.25-rc4 and it is the same.
Quoted 12 lines
Quoted 12 lines
A similar drive in an ICH7 box shows more consistent results:
# hdparm -t /dev/sda
/dev/sda:
Timing buffered disk reads: 182 MB in 3.01 seconds = 60.48 MB/sec
# dd if=/dev/zero of=file bs=100M count=100
100+0 records in
100+0 records out
10485760000 bytes (10 GB) copied, 242.908 s, 43.2 MB/s
Quoted 6 lines
Quoted 4 lines
# dd if=file of=/dev/null bs=100M count=100
100+0 records in
100+0 records out
10485760000 bytes (10 GB) copied, 211.132 s, 49.7 MB/s
Hmmm... indeed. Same kernel version? Can you post "hdparm -I" results of both drives?
The kernel on the second box is also 2.6.23.9. Here are hdparm results for identical drives:
1. Connected to SiI 3124/sata_sil24 w/ slow write:
# hdparm -I /dev/sda
/dev/sda:
ATA device, with non-removable media
        Model Number:       WDC WD1600JS-75NCB1
        Serial Number:      WD-WCANM1344866
        Firmware Revision:  10.02E01
# hdparm -I /dev/sda
/dev/sda:

Quoted 7 lines

ATA device, with non-removable media
        Model Number:       WDC WD1600JS-75NCB1
        Serial Number:      WD-WCANM1356774
        Firmware Revision:  10.02E01
Also, few months ago instead of sata_sil24 I had my drives connected to sata_mv (Supermicro 8-port) and performance was normal...

Everything seems okay. I wonder where the difference is. Does "dd if=/dev/zero of=file oflags=direct bs=1M" make any difference? And can you vacate a raw partition and try it on there?

Signature · 1 line

tejun

Denys Dmytriyenko

author

2008-03-06 06:55 UTC #13 lore raw

Quoted 47 lines · Tejun Heo

Quoted 46 lines · Denys Dmytriyenko
Turning off NCQ does not help. I am currently on 2.6.23.9, but I just tried 2.6.25-rc4 and it is the same.
Quoted 12 lines
Quoted 12 lines
A similar drive in an ICH7 box shows more consistent results:
# hdparm -t /dev/sda
/dev/sda:
Timing buffered disk reads: 182 MB in 3.01 seconds = 60.48 MB/sec
# dd if=/dev/zero of=file bs=100M count=100
100+0 records in
100+0 records out
10485760000 bytes (10 GB) copied, 242.908 s, 43.2 MB/s
Quoted 6 lines
Quoted 4 lines
# dd if=file of=/dev/null bs=100M count=100
100+0 records in
100+0 records out
10485760000 bytes (10 GB) copied, 211.132 s, 49.7 MB/s
Hmmm... indeed. Same kernel version? Can you post "hdparm -I" results of both drives?
The kernel on the second box is also 2.6.23.9. Here are hdparm results for identical drives:
1. Connected to SiI 3124/sata_sil24 w/ slow write:
# hdparm -I /dev/sda
/dev/sda:
ATA device, with non-removable media
        Model Number:       WDC WD1600JS-75NCB1
        Serial Number:      WD-WCANM1344866
        Firmware Revision:  10.02E01
# hdparm -I /dev/sda
/dev/sda:
ATA device, with non-removable media
        Model Number:       WDC WD1600JS-75NCB1
        Serial Number:      WD-WCANM1356774
        Firmware Revision:  10.02E01

Quoted 6 lines

Quoted 2 lines
Also, few months ago instead of sata_sil24 I had my drives connected to sata_mv (Supermicro 8-port) and performance was normal...
Everything seems okay. I wonder where the difference is. Does "dd if=/dev/zero of=file oflags=direct bs=1M" make any difference? And can you vacate a raw partition and try it on there?

oflag=direct has no effect - same speed. Tried it on a raw /dev/sda device and still no difference. It maybe slighly better, giving me 18 MB/s.

Can it be something with the way SiI 3124 controller is configured in the system?

Regards,
Denys

Tejun Heo

2008-03-06 07:08 UTC #14 lore raw

Quoted 11 lines · Denys Dmytriyenko

Quoted 5 lines
Quoted 2 lines
Also, few months ago instead of sata_sil24 I had my drives connected to sata_mv (Supermicro 8-port) and performance was normal...
Everything seems okay. I wonder where the difference is. Does "dd if=/dev/zero of=file oflags=direct bs=1M" make any difference? And can you vacate a raw partition and try it on there?
oflag=direct has no effect - same speed. Tried it on a raw /dev/sda device and still no difference. It maybe slighly better, giving me 18 MB/s.
Can it be something with the way SiI 3124 controller is configured in the system?

Hmmm... That's strange you did specify the "bs" parameter, right? It should essentially give the same performance as "hdparm -t". I wonder where the difference comes from.

Signature · 1 line

tejun

Denys Dmytriyenko

author

2008-03-15 21:44 UTC #15 lore raw

Quoted 10 lines · Tejun Heo

Quoted 9 lines · Denys Dmytriyenko
Quoted 5 lines
Quoted 2 lines
Also, few months ago instead of sata_sil24 I had my drives connected to sata_mv (Supermicro 8-port) and performance was normal...
Everything seems okay. I wonder where the difference is. Does "dd if=/dev/zero of=file oflags=direct bs=1M" make any difference? And can you vacate a raw partition and try it on there?
oflag=direct has no effect - same speed. Tried it on a raw /dev/sda device and still no difference. It maybe slighly better, giving me 18 MB/s.

Quoted 6 lines

Quoted 2 lines
Can it be something with the way SiI 3124 controller is configured in the system?
Hmmm... That's strange you did specify the "bs" parameter, right? It should essentially give the same performance as "hdparm -t". I wonder where the difference comes from.

Ok, after countless night-hours trying different configurations and peripheral combinations, it seems I can get good write performance (55 MB/s) from SATA card sitting in PCI-X slot, but bad write performance (18 MB/s) when it sits in PCI slot. And it is far from the PCI bandwidth limit.

I did some research and found out that apparently it is a known issue of AMD-760 MPX chipset. PCI-X bus is on the AMD-762 north bridge, while PCI bus is on the AMD-768 south bridge, which has a write bandwidth limit of 25 MB/s "bug", acknowledged by AMD. See these discussion threads:

http://forums.2cpu.com/showthread.php?s=c8040a4e9c9b6390dd389f1b3cca32de&threadid=31211
http://episteme.arstechnica.com/eve/forums/a/tpc/f/77909774/m/1160910035
http://forums.2cpu.com/showthread.php?s=66da493f719e8e64d15dc974cd567192&threadid=23379

Now, I have 2 options:

1. Keep existing system, but utilize 2 PCI-X slots for SATA controllers. This requires using 8-port adapters, like the one I already have Supermicro Marvell based. The question is - how stable sata_mv these days? It still says HIGHLY EXPERIMENTAL...

2. Replace MoBo+CPU+RAM (at least) and keep using SiI3124 based 4-port SATA adapters, as sata_sil24 is supposedly the most stable solution I can get.

I'm leaning towards the second option, but it would cost me more, compared to getting the second Marvell based PCI-X SATA card. Can you please advise? Thanks in advance.

Regards,
Denys

Mark Lord

2008-03-17 03:09 UTC #16 lore raw

Quoted 2 lines · Denys Dmytriyenko

1. Keep existing system, but utilize 2 PCI-X slots for SATA controllers. This requires using 8-port adapters, like the one I already have Supermicro Marvell based. The question is - how stable sata_mv these days? It still says HIGHLY EXPERIMENTAL...

..

It will lose that status early in the 2.6.26 timeframe.

Currently it does seem to work reasonably, with NCQ even, but there are still errata for me to get round to fixing, and the IRQ/EH/Reset code needs some work to ensure it can always recover when something weird happens.

Port multiplier support is working now, and will be pushed for 2.6.26 along with other fixes and stuff.

ATAPI support may yet follow before the summer.

Cheers

-ml

Denys Dmytriyenko

author

2008-03-18 00:15 UTC #17 lore raw

Quoted 15 lines · Mark Lord

Quoted 5 lines · Denys Dmytriyenko
1. Keep existing system, but utilize 2 PCI-X slots for SATA controllers. This requires using 8-port adapters, like the one I already have Supermicro Marvell based. The question is - how stable sata_mv these days? It still says HIGHLY EXPERIMENTAL...
..
It will lose that status early in the 2.6.26 timeframe.
Currently it does seem to work reasonably, with NCQ even, but there are still errata for me to get round to fixing, and the IRQ/EH/Reset code needs some work to ensure it can always recover when something weird happens.

Quoted 4 lines

Port multiplier support is working now, and will be pushed for 2.6.26 along with other fixes and stuff.
ATAPI support may yet follow before the summer.

Thanks for the update.

Meanwhile my system was quite stable lately, except for a few times when it threw some exceptions below. Can you please help me interpret them and also point out to how I can do it myself in the future. Thanks in advance.

Mar  8 02:09:49 [kernel] ata8: illegal qc_active transition (00000019->00000038)
Mar  8 02:09:49 [kernel] ata8.00: exception Emask 0x2 SAct 0x19 SErr 0x0 action 0x2 frozen
Mar  8 02:09:49 [kernel] ata8.00: cmd 60/08:00:87:77:62/00:00:0c:00:00/40 tag 0 cdb 0x0 data 4096 in
Mar  8 02:09:49 [kernel]          res 50/00:ff:00:00:00/00:00:00:00:00/40 Emask 0x2 (HSM violation)
Mar  8 02:09:49 [kernel] ata8.00: cmd 60/08:18:97:77:62/00:00:0c:00:00/40 tag 3 cdb 0x0 data 4096 in
Mar  8 02:09:49 [kernel]          res 50/00:ff:00:00:00/00:00:00:00:00/40 Emask 0x2 (HSM violation)
Mar  8 02:09:49 [kernel] ata8.00: cmd 60/08:20:a7:77:62/00:00:0c:00:00/40 tag 4 cdb 0x0 data 4096 in
Mar  8 02:09:49 [kernel]          res 50/00:ff:00:00:00/00:00:00:00:00/40 Emask 0x2 (HSM violation)
Mar  8 02:09:50 [kernel] ata8: soft resetting port
Mar  8 02:09:50 [kernel] ata8: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Mar  8 02:09:50 [kernel] ata8.00: ata_hpa_resize 1: hpa sectors (0) is smaller than sectors (976773168)
Mar  8 02:09:50 [kernel] ata8.00: configured for UDMA/100
Mar  8 02:09:50 [kernel] ata8: EH pending after completion, repeating EH (cnt=4)
Mar  8 02:09:50 [kernel] ata8: soft resetting port
Mar  8 02:09:50 [kernel] ata8: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Mar  8 02:09:50 [kernel] ata8.00: configured for UDMA/100
Mar  8 02:09:50 [kernel] ata8: EH complete
Mar  8 02:09:50 [kernel] sd 7:0:0:0: [sdf] 976773168 512-byte hardware sectors (500108 MB)
Mar  8 02:09:50 [kernel] sd 7:0:0:0: [sdf] Write Protect is off
Mar  8 02:09:50 [kernel] sd 7:0:0:0: [sdf] Mode Sense: 00 3a 00 00
Mar  8 02:09:50 [kernel] sd 7:0:0:0: [sdf] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Mar  8 02:09:50 [kernel] sd 7:0:0:0: [sdf] 976773168 512-byte hardware sectors (500108 MB)
Mar  8 02:09:50 [kernel] sd 7:0:0:0: [sdf] Write Protect is off
Mar  8 02:09:50 [kernel] sd 7:0:0:0: [sdf] Mode Sense: 00 3a 00 00
Mar  8 02:09:50 [kernel] sd 7:0:0:0: [sdf] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA

Mar  8 03:19:33 [kernel] ata8: illegal qc_active transition (000000ff->000001f7)
Mar  8 03:19:33 [kernel] ata8.00: exception Emask 0x2 SAct 0xff SErr 0x0 action 0x2 frozen
Mar  8 03:19:33 [kernel] ata8.00: cmd 60/08:00:3f:60:51/00:00:18:00:00/40 tag 0 cdb 0x0 data 4096 in
Mar  8 03:19:33 [kernel]          res 50/00:00:2f:60:38/00:00:3a:00:00/e0 Emask 0x2 (HSM violation)
Mar  8 03:19:33 [kernel] ata8.00: cmd 60/08:08:47:60:51/00:00:18:00:00/40 tag 1 cdb 0x0 data 4096 in
Mar  8 03:19:33 [kernel]          res 50/00:00:2f:60:38/00:00:3a:00:00/e0 Emask 0x2 (HSM violation)
Mar  8 03:19:33 [kernel] ata8.00: cmd 60/08:10:57:60:51/00:00:18:00:00/40 tag 2 cdb 0x0 data 4096 in
Mar  8 03:19:33 [kernel]          res 50/00:00:2f:60:38/00:00:3a:00:00/e0 Emask 0x2 (HSM violation)
Mar  8 03:19:33 [kernel] ata8.00: cmd 60/08:18:9f:60:51/00:00:18:00:00/40 tag 3 cdb 0x0 data 4096 in
Mar  8 03:19:33 [kernel]          res 50/00:00:2f:60:38/00:00:3a:00:00/e0 Emask 0x2 (HSM violation)
Mar  8 03:19:33 [kernel] ata8.00: cmd 60/18:20:67:60:51/00:00:18:00:00/40 tag 4 cdb 0x0 data 12288 in
Mar  8 03:19:33 [kernel]          res 50/00:00:2f:60:38/00:00:3a:00:00/e0 Emask 0x2 (HSM violation)
Mar  8 03:19:33 [kernel] ata8.00: cmd 60/08:28:87:60:51/00:00:18:00:00/40 tag 5 cdb 0x0 data 4096 in
Mar  8 03:19:33 [kernel]          res 50/00:00:2f:60:38/00:00:3a:00:00/e0 Emask 0x2 (HSM violation)
Mar  8 03:19:33 [kernel] ata8.00: cmd 60/08:30:97:60:51/00:00:18:00:00/40 tag 6 cdb 0x0 data 4096 in
Mar  8 03:19:33 [kernel]          res 50/00:00:2f:60:38/00:00:3a:00:00/e0 Emask 0x2 (HSM violation)
Mar  8 03:19:33 [kernel] ata8.00: cmd 60/10:38:a7:60:51/00:00:18:00:00/40 tag 7 cdb 0x0 data 8192 in
Mar  8 03:19:33 [kernel]          res 50/00:00:2f:60:38/00:00:3a:00:00/e0 Emask 0x2 (HSM violation)
Mar  8 03:19:33 [kernel] ata8: soft resetting port
Mar  8 03:19:34 [kernel] ata8: softreset failed (port not ready)
Mar  8 03:19:34 [kernel] ata8: reset failed (errno=-5), retrying in 10 secs
Mar  8 03:19:43 [kernel] ata8: hard resetting port
Mar  8 03:19:46 [kernel] ata8: softreset failed (SRST command error)
Mar  8 03:19:46 [kernel] ata8: reset failed (errno=-5), retrying in 8 secs
Mar  8 03:19:53 [kernel] ata8: hard resetting port
Mar  8 03:19:56 [kernel] ata8: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Mar  8 03:19:56 [kernel] ata8.00: configured for UDMA/100
Mar  8 03:19:56 [kernel] ata8: EH complete
Mar  8 03:19:56 [kernel] sd 7:0:0:0: [sdf] 976773168 512-byte hardware sectors (500108 MB)
Mar  8 03:19:56 [kernel] sd 7:0:0:0: [sdf] Write Protect is off
Mar  8 03:19:56 [kernel] sd 7:0:0:0: [sdf] Mode Sense: 00 3a 00 00
Mar  8 03:19:56 [kernel] sd 7:0:0:0: [sdf] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA

Mar 14 23:51:43 [kernel] ata3: illegal qc_active transition (0000001b->0000002b)
Mar 14 23:51:43 [kernel] ata3.00: exception Emask 0x2 SAct 0x1b SErr 0x0 action 0x6 frozen
Mar 14 23:51:43 [kernel] ata3.00: cmd 60/08:00:3f:af:a9/00:00:05:00:00/40 tag 0 cdb 0x0 data 4096 in
Mar 14 23:51:43 [kernel]          res 50/00:00:00:00:00/00:00:00:00:00/40 Emask 0x2 (HSM violation)
Mar 14 23:51:43 [kernel] ata3.00: cmd 60/20:08:7f:af:a9/00:00:05:00:00/40 tag 1 cdb 0x0 data 16384 in
Mar 14 23:51:43 [kernel]          res 50/00:00:00:00:00/00:00:00:00:00/40 Emask 0x2 (HSM violation)
Mar 14 23:51:43 [kernel] ata3.00: cmd 60/08:18:4f:af:a9/00:00:05:00:00/40 tag 3 cdb 0x0 data 4096 in
Mar 14 23:51:43 [kernel]          res 50/00:00:00:00:00/00:00:00:00:00/40 Emask 0x2 (HSM violation)
Mar 14 23:51:43 [kernel] ata3.00: cmd 60/08:20:5f:af:a9/00:00:05:00:00/40 tag 4 cdb 0x0 data 4096 in
Mar 14 23:51:43 [kernel]          res 50/00:00:00:00:00/00:00:00:00:00/40 Emask 0x2 (HSM violation)
Mar 14 23:51:43 [kernel] ata3: hard resetting port
Mar 14 23:51:45 [kernel] ata3: softreset failed (SRST command error)
Mar 14 23:51:45 [kernel] ata3: reset failed (errno=-5), retrying in 8 secs
Mar 14 23:51:53 [kernel] ata3: hard resetting port
Mar 14 23:51:55 [kernel] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Mar 14 23:51:55 [kernel] ata3.00: configured for UDMA/100
Mar 14 23:51:55 [kernel] ata3: EH complete
Mar 14 23:51:55 [kernel] sd 2:0:0:0: [sdc] 976773168 512-byte hardware sectors (500108 MB)
Mar 14 23:51:55 [kernel] sd 2:0:0:0: [sdc] Write Protect is off
Mar 14 23:51:55 [kernel] sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00
Mar 14 23:51:55 [kernel] sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

Mar 14 23:51:55 [kernel] ata3: failed to read log page 10h (errno=-2)
Mar 14 23:51:55 [kernel] ata3.00: exception Emask 0x1 SAct 0x3f SErr 0x0 action 0x0
Mar 14 23:51:55 [kernel] ata3.00: irq_stat 0x00020002, device error via SDB FIS
Mar 14 23:51:55 [kernel] ata3.00: cmd 60/08:00:5f:af:a9/00:00:05:00:00/40 tag 0 cdb 0x0 data 4096 in
Mar 14 23:51:55 [kernel]          res 50/00:00:2f:60:38/00:00:3a:00:00/e0 Emask 0x1 (device error)
Mar 14 23:51:55 [kernel] ata3.00: cmd 60/08:08:4f:af:a9/00:00:05:00:00/40 tag 1 cdb 0x0 data 4096 in
Mar 14 23:51:55 [kernel]          res 50/00:00:2f:60:38/00:00:3a:00:00/e0 Emask 0x1 (device error)
Mar 14 23:51:55 [kernel] ata3.00: cmd 60/20:10:7f:af:a9/00:00:05:00:00/40 tag 2 cdb 0x0 data 16384 in
Mar 14 23:51:55 [kernel]          res 50/00:00:2f:60:38/00:00:3a:00:00/e0 Emask 0x1 (device error)
Mar 14 23:51:55 [kernel] ata3.00: cmd 60/08:18:3f:af:a9/00:00:05:00:00/40 tag 3 cdb 0x0 data 4096 in
Mar 14 23:51:55 [kernel]          res 50/00:00:2f:60:38/00:00:3a:00:00/e0 Emask 0x1 (device error)
Mar 14 23:51:55 [kernel] ata3.00: cmd 60/30:20:9f:af:a9/00:00:05:00:00/40 tag 4 cdb 0x0 data 24576 in
Mar 14 23:51:55 [kernel]          res 50/00:00:2f:60:38/00:00:3a:00:00/e0 Emask 0x1 (device error)
Mar 14 23:51:55 [kernel] ata3.00: cmd 60/30:28:cf:af:a9/00:00:05:00:00/40 tag 5 cdb 0x0 data 24576 in
Mar 14 23:51:55 [kernel]          res 50/00:00:2f:60:38/00:00:3a:00:00/e0 Emask 0x1 (device error)
Mar 14 23:51:55 [kernel] ata3.00: configured for UDMA/100
Mar 14 23:51:55 [kernel] ata3: EH complete
Mar 14 23:51:55 [kernel] sd 2:0:0:0: [sdc] 976773168 512-byte hardware sectors (500108 MB)
Mar 14 23:51:55 [kernel] sd 2:0:0:0: [sdc] Write Protect is off
Mar 14 23:51:55 [kernel] sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00
Mar 14 23:51:55 [kernel] sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

Regards,
Denys

Tejun Heo

2008-03-18 04:09 UTC #18 lore raw

Quoted 5 lines · Denys Dmytriyenko

Meanwhile my system was quite stable lately, except for a few times when it threw some exceptions below. Can you please help me interpret them and also point out to how I can do it myself in the future. Thanks in advance.
Mar  8 02:09:49 [kernel] ata8: illegal qc_active transition (00000019->00000038)

Hmmm... This is first. Which driver is it? It means that controller is reporting that NCQ command tags which are not issued (or already completed) are in-flight. Due to the way hdd reports NCQ command completion, it's not possible for the drive to cause this. This gotta be a bug on the host side (be it controller chip or more likely the driver). The command tag in question is 5. Only 0, 3 and 4 were in flight.

Quoted 1 line

Mar  8 03:19:33 [kernel] ata8: illegal qc_active transition (000000ff->000001f7)

The same but problematic tag is 8.

Quoted 1 line

Mar 14 23:51:43 [kernel] ata3: illegal qc_active transition (0000001b->0000002b)

Ditto but with tag 5.

Quoted 3 lines

Mar 14 23:51:55 [kernel] ata3: failed to read log page 10h (errno=-2)
Mar 14 23:51:55 [kernel] ata3.00: exception Emask 0x1 SAct 0x3f SErr 0x0 action 0x0
Mar 14 23:51:55 [kernel] ata3.00: irq_stat 0x00020002, device error via SDB FIS

This one is different. The drive reported device error but the driver couldn't get more information about the error (log page 10h contains it). What does smartctl -a on the drive say?

Signature · 1 line

tejun

Denys Dmytriyenko

author

2008-03-18 04:53 UTC #19 lore raw

Quoted 5 lines · Tejun Heo

Quoted 4 lines · Denys Dmytriyenko
Meanwhile my system was quite stable lately, except for a few times when it threw some exceptions below. Can you please help me interpret them and also point out to how I can do it myself in the future. Thanks in advance.

Quoted 8 lines

Quoted 1 line
Mar  8 02:09:49 [kernel] ata8: illegal qc_active transition (00000019->00000038)
Hmmm... This is first. Which driver is it? It means that controller is reporting that NCQ command tags which are not issued (or already completed) are in-flight. Due to the way hdd reports NCQ command completion, it's not possible for the drive to cause this. This gotta be a bug on the host side (be it controller chip or more likely the driver). The command tag in question is 5. Only 0, 3 and 4 were in flight.

It is sata_sil24 on 2.6.23.9. If there were related fixes in the recent versions, I can retest it.

Quoted 8 lines

Quoted 1 line
Mar  8 03:19:33 [kernel] ata8: illegal qc_active transition (000000ff->000001f7)
The same but problematic tag is 8.
Quoted 1 line
Mar 14 23:51:43 [kernel] ata3: illegal qc_active transition (0000001b->0000002b)
Ditto but with tag 5.

Quoted 7 lines

Quoted 3 lines
Mar 14 23:51:55 [kernel] ata3: failed to read log page 10h (errno=-2)
Mar 14 23:51:55 [kernel] ata3.00: exception Emask 0x1 SAct 0x3f SErr 0x0 action 0x0
Mar 14 23:51:55 [kernel] ata3.00: irq_stat 0x00020002, device error via SDB FIS
This one is different. The drive reported device error but the driver couldn't get more information about the error (log page 10h contains it). What does smartctl -a on the drive say?

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

=== START OF INFORMATION SECTION ===

Model Family:     Maxtor MaXLine Pro 500 family
Device Model:     Maxtor 7H500F0
Serial Number:    H81DAX1H
Firmware Version: HA431DN0
User Capacity:    500,107,862,016 bytes
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   7
ATA Standard is:  ATA/ATAPI-7 T13 1532D revision 0
Local Time is:    Tue Mar 18 00:40:28 2008 EDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status: (0x80) Offline data collection activity
was never started.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 32) The self-test routine was interrupted
by the host with a hard or soft reset.
Total time to complete Offline
data collection: (9003) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off support. Suspend Offline collection upon new command.
Offline surface scan supported. Self-test supported.
No Conveyance Self-test supported. Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 206) minutes.

SMART Attributes Data Structure revision number: 32 Vendor Specific SMART Attributes with Thresholds:

ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  3 Spin_Up_Time            0x0027   169   168   063    Pre-fail  Always       -       16613
  4 Start_Stop_Count        0x0032   249   249   000    Old_age   Always       -       8406
  5 Reallocated_Sector_Ct   0x0033   253   253   063    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000a   253   252   000    Old_age   Always       -       0
  8 Seek_Time_Performance   0x0027   251   241   187    Pre-fail  Always       -       33007
  9 Power_On_Hours          0x0032   242   242   000    Old_age   Always       -       3941
 10 Spin_Retry_Count        0x002b   253   252   157    Pre-fail  Always       -       0
 11 Calibration_Retry_Count 0x002b   253   252   223    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   253   253   000    Old_age   Always       -       263
189 Unknown_Attribute       0x003a   100   100   000    Old_age   Always       -       0
190 Temperature_Celsius     0x0022   063   050   000    Old_age   Always       -       689700901
192 Power-Off_Retract_Count 0x0032   253   253   000    Old_age   Always       -       0
193 Load_Cycle_Count        0x0032   253   253   000    Old_age   Always       -       0
194 Temperature_Celsius     0x0032   039   253   000    Old_age   Always       -       37
195 Hardware_ECC_Recovered  0x000a   253   252   000    Old_age   Always       -       1912
196 Reallocated_Event_Count 0x0008   253   253   000    Old_age   Offline      -       0
197 Current_Pending_Sector  0x0008   253   253   000    Old_age   Offline      -       0
198 Offline_Uncorrectable   0x0008   253   253   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0008   002   001   000    Old_age   Offline      -       798
200 Multi_Zone_Error_Rate   0x000a   253   252   000    Old_age   Always       -       0
201 Soft_Read_Error_Rate    0x000a   253   252   000    Old_age   Always       -       0
202 TA_Increase_Count       0x000a   253   252   000    Old_age   Always       -       0
203 Run_Out_Cancel          0x000b   253   252   180    Pre-fail  Always       -       0
204 Shock_Count_Write_Opern 0x000a   253   252   000    Old_age   Always       -       0
205 Shock_Rate_Write_Opern  0x000a   253   252   000    Old_age   Always       -       0
207 Spin_High_Current       0x002a   253   252   000    Old_age   Always       -       0
208 Spin_Buzz               0x002a   253   252   000    Old_age   Always       -       0
210 Unknown_Attribute       0x0032   253   252   000    Old_age   Always       -       0
211 Unknown_Attribute       0x0032   253   252   000    Old_age   Always       -       0
212 Unknown_Attribute       0x0032   253   252   000    Old_age   Always       -       0

SMART Error Log Version: 1
ATA Error Count: 42 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 42 occurred at disk power-on lifetime: 3444 hours (143 days + 12 hours)
When the command that caused the error occurred, the device was in an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
84 41 28 ff 46 5a 40

Commands leading to the command that caused the error were:

  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 08 28 ff 46 5a 40 00   2d+07:38:11.073  READ FPDMA QUEUED
  60 08 28 ff 46 5a 40 00   2d+07:38:11.073  READ FPDMA QUEUED
  60 08 28 ff 46 5a 40 00   2d+07:38:11.073  READ FPDMA QUEUED
  60 10 20 2f 47 5a 40 00   2d+07:38:11.073  READ FPDMA QUEUED
  60 08 18 1f 47 5a 40 00   2d+07:38:11.073  READ FPDMA QUEUED

Error 41 occurred at disk power-on lifetime: 3405 hours (141 days + 21 hours)
When the command that caused the error occurred, the device was in an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
00 41 01 10 00 00 a0 Error:

Commands leading to the command that caused the error were:

  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  2f 00 01 10 00 00 a0 00      12:51:00.112  READ LOG EXT
  60 20 20 7f 32 4c 40 00      12:51:00.081  READ FPDMA QUEUED
  60 08 18 6f 32 4c 40 00      12:51:00.081  READ FPDMA QUEUED
  60 30 10 9f 32 4c 40 00      12:51:00.081  READ FPDMA QUEUED
  60 08 08 5f 32 4c 40 00      12:51:00.081  READ FPDMA QUEUED

SMART Self-test log structure revision number 1

Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Offline             Interrupted (host reset)      00%      3941         -
# 2  Offline             Interrupted (host reset)      00%      1940         -
# 3  Offline             Interrupted (host reset)      00%      1894         -

SMART Selective self-test log data structure revision number 1

 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing

Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

Signature · 1 line

Denys

Tejun Heo

2008-03-18 06:40 UTC #20 lore raw

Hello,

Quoted 9 lines · Denys Dmytriyenko

Quoted 6 lines
Hmmm... This is first. Which driver is it? It means that controller is reporting that NCQ command tags which are not issued (or already completed) are in-flight. Due to the way hdd reports NCQ command completion, it's not possible for the drive to cause this. This gotta be a bug on the host side (be it controller chip or more likely the driver). The command tag in question is 5. Only 0, 3 and 4 were in flight.
It is sata_sil24 on 2.6.23.9. If there were related fixes in the recent versions, I can retest it.

No, not that I know of.

Quoted 9 lines

Quoted 3 lines
This one is different. The drive reported device error but the driver couldn't get more information about the error (log page 10h contains it). What does smartctl -a on the drive say?
# smartctl -a /dev/sdc
smartctl version 5.37 [i686-pc-linux-gnu] Copyright (C) 2002-6 Bruce Allen
Home page is http://smartmontools.sourceforge.net/
9 Power_On_Hours 0x0032 242 242 000 Old_age Always - 3941

Okay, power on hours is 3941.

Quoted 8 lines

Error 42 occurred at disk power-on lifetime: 3444 hours (143 days + 12 hours)
When the command that caused the error occurred, the device was in an unknown state.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
84 41 28 ff 46 5a 40

Quoted 8 lines

Commands leading to the command that caused the error were:

  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 08 28 ff 46 5a 40 00   2d+07:38:11.073  READ FPDMA QUEUED
  60 08 28 ff 46 5a 40 00   2d+07:38:11.073  READ FPDMA QUEUED
  60 08 28 ff 46 5a 40 00   2d+07:38:11.073  READ FPDMA QUEUED
  60 10 20 2f 47 5a 40 00   2d+07:38:11.073  READ FPDMA QUEUED
  60 08 18 1f 47 5a 40 00   2d+07:38:11.073  READ FPDMA QUEUED

Error 42 occurred about 21days ago. Unless your clock is off, I don't think this is what you've seen but the error is UNC (uncorrectable media error), so it does mean that your drive has some bad sectors which can explain the device error you saw.

Quoted 8 lines

Error 41 occurred at disk power-on lifetime: 3405 hours (141 days + 21 hours)
When the command that caused the error occurred, the device was in an unknown state.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
00 41 01 10 00 00 a0 Error:

Quoted 8 lines

Commands leading to the command that caused the error were:

  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  2f 00 01 10 00 00 a0 00      12:51:00.112  READ LOG EXT
  60 20 20 7f 32 4c 40 00      12:51:00.081  READ FPDMA QUEUED
  60 08 18 6f 32 4c 40 00      12:51:00.081  READ FPDMA QUEUED
  60 30 10 9f 32 4c 40 00      12:51:00.081  READ FPDMA QUEUED
  60 08 08 5f 32 4c 40 00      12:51:00.081  READ FPDMA QUEUED

Hmm.. this one less clear. Maybe the device wasn't expecting READ LOG EXT as it was still in NCQ command phase and got surprised?

Currently you're the first and only one to report illegal qc_active transition problem. I'd like to know what precedes the error which isn't exactly easy in retrospect. For now, please keep an eye on those errors and report if you can see any pattern. And just in case, can you get 2.6.24 on the machine and see anything changes?

Signature · 1 line

tejun

Denys Dmytriyenko

author

2008-03-20 22:37 UTC #21 lore raw

Hi,

Quoted 39 lines · Tejun Heo

Quoted 8 lines
Error 42 occurred at disk power-on lifetime: 3444 hours (143 days + 12 hours)
When the command that caused the error occurred, the device was in an unknown state.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
84 41 28 ff 46 5a 40
Quoted 8 lines
Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 08 28 ff 46 5a 40 00   2d+07:38:11.073  READ FPDMA QUEUED
  60 08 28 ff 46 5a 40 00   2d+07:38:11.073  READ FPDMA QUEUED
  60 08 28 ff 46 5a 40 00   2d+07:38:11.073  READ FPDMA QUEUED
  60 10 20 2f 47 5a 40 00   2d+07:38:11.073  READ FPDMA QUEUED
  60 08 18 1f 47 5a 40 00   2d+07:38:11.073  READ FPDMA QUEUED
Error 42 occurred about 21days ago. Unless your clock is off, I don't think this is what you've seen but the error is UNC (uncorrectable media error), so it does mean that your drive has some bad sectors which can explain the device error you saw.
Quoted 8 lines
Error 41 occurred at disk power-on lifetime: 3405 hours (141 days + 21 hours)
When the command that caused the error occurred, the device was in an unknown state.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
00 41 01 10 00 00 a0 Error:
Quoted 8 lines
Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  2f 00 01 10 00 00 a0 00      12:51:00.112  READ LOG EXT
  60 20 20 7f 32 4c 40 00      12:51:00.081  READ FPDMA QUEUED
  60 08 18 6f 32 4c 40 00      12:51:00.081  READ FPDMA QUEUED
  60 30 10 9f 32 4c 40 00      12:51:00.081  READ FPDMA QUEUED
  60 08 08 5f 32 4c 40 00      12:51:00.081  READ FPDMA QUEUED

Quoted 8 lines

Hmm.. this one less clear. Maybe the device wasn't expecting READ LOG EXT as it was still in NCQ command phase and got surprised?
Currently you're the first and only one to report illegal qc_active transition problem. I'd like to know what precedes the error which isn't exactly easy in retrospect. For now, please keep an eye on those errors and report if you can see any pattern. And just in case, can you get 2.6.24 on the machine and see anything changes?

Thanks for the info. As Gabor suggested, I watched UDMA_CRC_Error_Count and it slowly grows only on this particular drive. And here is another recent exception for the same drive, which is somewhat strange looking:

Mar 19 22:24:29 [kernel] ata3.00: exception Emask 0x40 SAct 0x3f SErr 0x0 action 0x6 frozen
Mar 19 22:24:29 [kernel] ata3.00: irq_stat 0x00060002, PRB not on qword boundary
Mar 19 22:24:29 [kernel] ata3.00: cmd 60/08:00:27:32:f3/00:00:2c:00:00/40 tag 0 cdb 0x0 data 4096 in
Mar 19 22:24:29 [kernel]          res 50/00:00:00:00:00/00:00:00:00:00/40 Emask 0x40 (internal error)
Mar 19 22:24:29 [kernel] ata3.00: cmd 60/08:08:6f:32:f3/00:00:2c:00:00/40 tag 1 cdb 0x0 data 4096 in
Mar 19 22:24:29 [kernel]          res 50/00:00:00:00:00/00:00:00:00:00/40 Emask 0x40 (internal error)
Mar 19 22:24:29 [kernel] ata3.00: cmd 60/08:10:67:32:f3/00:00:2c:00:00/40 tag 2 cdb 0x0 data 4096 in
Mar 19 22:24:29 [kernel]          res 50/00:00:00:00:00/00:00:00:00:00/40 Emask 0x40 (internal error)
Mar 19 22:24:29 [kernel] ata3.00: cmd 60/08:18:37:32:f3/00:00:2c:00:00/40 tag 3 cdb 0x0 data 4096 in
Mar 19 22:24:29 [kernel]          res 50/00:00:00:00:00/00:00:00:00:00/40 Emask 0x40 (internal error)
Mar 19 22:24:29 [kernel] ata3.00: cmd 60/08:20:47:32:f3/00:00:2c:00:00/40 tag 4 cdb 0x0 data 4096 in
Mar 19 22:24:29 [kernel]          res 50/00:00:00:00:00/00:00:00:00:00/40 Emask 0x40 (internal error)
Mar 19 22:24:29 [kernel] ata3.00: cmd 60/10:28:77:32:f3/00:00:2c:00:00/40 tag 5 cdb 0x0 data 8192 in
Mar 19 22:24:29 [kernel]          res 50/00:00:00:00:00/00:00:00:00:00/40 Emask 0x40 (internal error)
Mar 19 22:24:29 [kernel] ata3: hard resetting port
Mar 19 22:24:31 [kernel] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Mar 19 22:24:31 [kernel] ata3.00: configured for UDMA/100
Mar 19 22:24:31 [kernel] ata3: EH pending after completion, repeating EH (cnt=4)
Mar 19 22:24:31 [kernel] ata3: exception Emask 0x2 SAct 0x0 SErr 0x0 action 0x2
Mar 19 22:24:31 [kernel] ata3: irq_stat 0x00060002, protocol mismatch
Mar 19 22:24:31 [kernel] ata3: soft resetting port
Mar 19 22:24:31 [kernel] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Mar 19 22:24:31 [kernel] ata3.00: configured for UDMA/100
Mar 19 22:24:31 [kernel] ata3: EH complete
Mar 19 22:24:31 [kernel] sd 2:0:0:0: [sdc] 976773168 512-byte hardware sectors (500108 MB)
Mar 19 22:24:31 [kernel] sd 2:0:0:0: [sdc] Write Protect is off
Mar 19 22:24:31 [kernel] sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00
Mar 19 22:24:31 [kernel] sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Mar 19 22:24:31 [kernel] sd 2:0:0:0: [sdc] 976773168 512-byte hardware sectors (500108 MB)
Mar 19 22:24:31 [kernel] sd 2:0:0:0: [sdc] Write Protect is off
Mar 19 22:24:31 [kernel] sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00
Mar 19 22:24:31 [kernel] sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

Any ieas what this might be? I'll definitely try to replace the cable and see what happens.

BTW, issuing "smartctl -a" on a drive in standby, throws this exception:

Mar 20 18:16:53 [kernel] ata10.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
Mar 20 18:16:53 [kernel] ata10.00: cmd b0/da:00:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 0 
Mar 20 18:16:53 [kernel]          res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Mar 20 18:16:53 [kernel] ata10: soft resetting port
Mar 20 18:16:54 [kernel] ata10: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Mar 20 18:16:54 [kernel] ata10.00: configured for UDMA/100
Mar 20 18:16:54 [kernel] ata10: EH complete
Mar 20 18:16:54 [kernel] sd 9:0:0:0: [sdj] 976773168 512-byte hardware sectors (500108 MB)
Mar 20 18:16:54 [kernel] sd 9:0:0:0: [sdj] Write Protect is off
Mar 20 18:16:54 [kernel] sd 9:0:0:0: [sdj] Mode Sense: 00 3a 00 00
Mar 20 18:16:54 [kernel] sd 9:0:0:0: [sdj] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

Signature · 1 line

Denys

Tejun Heo

2008-03-21 00:18 UTC #22 lore raw

Hello,

Quoted 6 lines · Denys Dmytriyenko

Thanks for the info. As Gabor suggested, I watched UDMA_CRC_Error_Count and it slowly grows only on this particular drive. And here is another recent exception for the same drive, which is somewhat strange looking:
Mar 19 22:24:29 [kernel] ata3.00: exception Emask 0x40 SAct 0x3f SErr 0x0 action 0x6 frozen
Mar 19 22:24:29 [kernel] ata3.00: irq_stat 0x00060002, PRB not on qword boundary

Oh... That means the data structure fed to the controller by the driver is misaligned which AFAIK can NOT happen. All PRBs are allocated during controller initialization and they're properly aligned. It could be that the drive is telling weird things to the controller and got it confused.

Quoted 2 lines

Mar 19 22:24:31 [kernel] ata3: exception Emask 0x2 SAct 0x0 SErr 0x0 action 0x2
Mar 19 22:24:31 [kernel] ata3: irq_stat 0x00060002, protocol mismatch

This is controller complaining that what the drive is saying is gibberish.

Quoted 2 lines

Any ieas what this might be? I'll definitely try to replace the cable and see what happens.

What happens if you connect the drive to different port on the controller? Do errors follow the drive?

Quoted 13 lines

BTW, issuing "smartctl -a" on a drive in standby, throws this exception:

Mar 20 18:16:53 [kernel] ata10.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
Mar 20 18:16:53 [kernel] ata10.00: cmd b0/da:00:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 0 
Mar 20 18:16:53 [kernel]          res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Mar 20 18:16:53 [kernel] ata10: soft resetting port
Mar 20 18:16:54 [kernel] ata10: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Mar 20 18:16:54 [kernel] ata10.00: configured for UDMA/100
Mar 20 18:16:54 [kernel] ata10: EH complete
Mar 20 18:16:54 [kernel] sd 9:0:0:0: [sdj] 976773168 512-byte hardware sectors (500108 MB)
Mar 20 18:16:54 [kernel] sd 9:0:0:0: [sdj] Write Protect is off
Mar 20 18:16:54 [kernel] sd 9:0:0:0: [sdj] Mode Sense: 00 3a 00 00
Mar 20 18:16:54 [kernel] sd 9:0:0:0: [sdj] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

Which kernel version and how did you put the drive into sleep?

Signature · 1 line

tejun

Denys Dmytriyenko

author

2008-04-14 01:19 UTC #23 lore raw

Tejun et al,

I wanted to thank you all for the support you provided. I ended up replacing MoBo+CPU to Intel based ones (and previously mentioned single-rail PSU) and now everything works rock solid for over a week now! Thanks again.

Quoted 14 lines

Quoted 13 lines

BTW, issuing "smartctl -a" on a drive in standby, throws this exception:

Mar 20 18:16:53 [kernel] ata10.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
Mar 20 18:16:53 [kernel] ata10.00: cmd b0/da:00:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 0 
Mar 20 18:16:53 [kernel]          res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Mar 20 18:16:53 [kernel] ata10: soft resetting port
Mar 20 18:16:54 [kernel] ata10: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Mar 20 18:16:54 [kernel] ata10.00: configured for UDMA/100
Mar 20 18:16:54 [kernel] ata10: EH complete
Mar 20 18:16:54 [kernel] sd 9:0:0:0: [sdj] 976773168 512-byte hardware sectors (500108 MB)
Mar 20 18:16:54 [kernel] sd 9:0:0:0: [sdj] Write Protect is off
Mar 20 18:16:54 [kernel] sd 9:0:0:0: [sdj] Mode Sense: 00 3a 00 00
Mar 20 18:16:54 [kernel] sd 9:0:0:0: [sdj] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

Quoted 1 line

Which kernel version and how did you put the drive into sleep?

This timeout exception is still there - 2.6.24.4, drive goes to sleep on timeout of 30 minutes (hdpram -S 241)

Signature · 1 line

Denys

Tejun Heo

2008-04-14 02:49 UTC #24 lore raw

Quoted 16 lines · Denys Dmytriyenko

Tejun et al,

I wanted to thank you all for the support you provided. I ended up replacing MoBo+CPU to Intel based ones (and previously mentioned single-rail PSU) and now everything works rock solid for over a week now! Thanks again.

Quoted 12 lines

BTW, issuing "smartctl -a" on a drive in standby, throws this exception:

Mar 20 18:16:53 [kernel] ata10.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
Mar 20 18:16:53 [kernel] ata10.00: cmd b0/da:00:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 0 Mar 20 18:16:53 [kernel]          res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Mar 20 18:16:53 [kernel] ata10: soft resetting port
Mar 20 18:16:54 [kernel] ata10: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Mar 20 18:16:54 [kernel] ata10.00: configured for UDMA/100
Mar 20 18:16:54 [kernel] ata10: EH complete
Mar 20 18:16:54 [kernel] sd 9:0:0:0: [sdj] 976773168 512-byte hardware sectors (500108 MB)
Mar 20 18:16:54 [kernel] sd 9:0:0:0: [sdj] Write Protect is off
Mar 20 18:16:54 [kernel] sd 9:0:0:0: [sdj] Mode Sense: 00 3a 00 00
Mar 20 18:16:54 [kernel] sd 9:0:0:0: [sdj] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

Quoted 3 lines

Quoted 1 line
Which kernel version and how did you put the drive into sleep?
This timeout exception is still there - 2.6.24.4, drive goes to sleep on timeout of 30 minutes (hdpram -S 241)

Yeah, this is still under discussion. It seems smartd will need to issue CHECK POWER before issuing other commands.

Signature · 1 line

tejun

Gabor FUNK

2008-04-14 10:57 UTC #25 lore raw

In reply to Denys Dmytriyenko

Since you brought it up, several days ago I got informed, that the "original problem" (exception/hard resetting port) could be related to kernel option IRQBALANCE.
See more at:
http://forums.gentoo.org:80/viewtopic-t-641372-highlight-.html

As Dmytri and me as well both replaced the MB finally which now runs fine, we will probably not going to "play" again with this, but if anyone runs into this in the near future, this can be a thing to try. I can imagine that this could've helped, as in my case failing was purely limited one controller [*4 disks] at the time, eg. no other disk on other controller, nor just only one or some disk on a controller, but all disks on only 1 controller.

And if anyone have any theoretical imagination why it could be the cause - and where to fix :-] - don't hesitate to write...

Cheers,

G.

----- Original Message ----- From: "Denys Dmytriyenko" <[email protected]>
To: "Tejun Heo" <[email protected]>
Cc: "Mark Lord" <[email protected]>; "Gabor FUNK" <[email protected]>; <[email protected]>; "Jim Paris" <[email protected]>
Sent: Monday, April 14, 2008 3:19 AM
Subject: Re: sata_sil24 stability and performance

Quoted 28 lines

Tejun et al,
I wanted to thank you all for the support you provided. I ended up replacing MoBo+CPU to Intel based ones (and previously mentioned single-rail PSU) and now everything works rock solid for over a week now! Thanks again.
Quoted 14 lines
Quoted 13 lines
BTW, issuing "smartctl -a" on a drive in standby, throws this exception:
Mar 20 18:16:53 [kernel] ata10.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
Mar 20 18:16:53 [kernel] ata10.00: cmd b0/da:00:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 0
Mar 20 18:16:53 [kernel]          res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Mar 20 18:16:53 [kernel] ata10: soft resetting port
Mar 20 18:16:54 [kernel] ata10: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Mar 20 18:16:54 [kernel] ata10.00: configured for UDMA/100
Mar 20 18:16:54 [kernel] ata10: EH complete
Mar 20 18:16:54 [kernel] sd 9:0:0:0: [sdj] 976773168 512-byte hardware sectors (500108 MB)
Mar 20 18:16:54 [kernel] sd 9:0:0:0: [sdj] Write Protect is off
Mar 20 18:16:54 [kernel] sd 9:0:0:0: [sdj] Mode Sense: 00 3a 00 00
Mar 20 18:16:54 [kernel] sd 9:0:0:0: [sdj] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Quoted 1 line
Which kernel version and how did you put the drive into sleep?
This timeout exception is still there - 2.6.24.4, drive goes to sleep on timeout of 30 minutes (hdpram -S 241)
Signature · 1 line
Denys

Gabor FUNK

2008-03-18 09:14 UTC #26 lore raw

In reply to Denys Dmytriyenko

Quoted 1 line

Quoted 1 line
199 UDMA_CRC_Error_Count 0x0008 002 001 000 Old_age line - 798

Denys,
I did a smartctl check on 12 disks in 5 differrent servers (usually pairs of disks sw mirrorred), and all of those - except one - had
0-s at UDMA_CRC_Error_Count.
Only one had 16 in it, this one is SAMSUNG HD300LD installed
at 2006.09.12, running 24/7, so its uptime is about 13200 hours. However, it's pair (same disk, same uptime) have 0, which makes
me think, that it is not motherboard/controller, but cable or HDD. (wiki says, it is: "The number of errors in data transfer via the interface cable as determined by ICRC (Interface Cyclic Redundancy Check)."
http://en.wikipedia.org/wiki/Self-Monitoring,_Analysis,_and_Reporting_Technology )

Is that value is growing at your server?

+

Related to my original issue (exception / hard resetting link), which later Denys also experienced and countinued on this thread, my current status is, that

Quoted 3 lines · he

Quoted 3 lines
I have a similar problem with an N680SLI, as posted here:
http://forums.gentoo.org/viewtopic-t-641372-highlight-.html
Short version - 2.6.22 seems stable, anything later, unstable.

Since exhibiting the problem takes days, weeks or even months, he can't know more, promised to write to list if he finds out anything.

2) I replaced the MB to a different one, now it is a Gigabyte as well, but it has no nvidia/jmicron contollers but ata_piix and achi onboard, and - ironically - an addon sil24 card...
So far, the system running well [knock-knock], under heavy stress test, for 3 weeks now, without problems.
I believe Tejun suggested to try to remove one of the HDD-s online to see what happens, I will try this today later on, when I am at the server and let you know.

(for those who need refreshment, my initial thread was on
http://www.mail-archive.com/[email protected]/msg15950.html
and it continued on
http://www.opensubscriber.com/message/[email protected]/8633679.html my latest mail on this topic is at: http://www.opensubscriber.com/message/[email protected]/8718520.html )G.

Gabor FUNK

2008-03-18 13:06 UTC #27 lore raw

Quoted 8 lines

2) I replaced the MB to a different one, now it is a Gigabyte as well, but it has no nvidia/jmicron contollers but ata_piix and achi onboard, and - ironically - an addon sil24 card...
So far, the system running well [knock-knock], under heavy stress test, for 3 weeks now, without problems.
I believe Tejun suggested to try to remove one of the HDD-s online to see what happens, I will try this today later on, when I am at the server and let you know.

I removed power from one of the drives in question, and besides losing that disk, nothing extra happened - eg. the rest 7 drives stayed operational, raid was operational, etc.

G.

Mark Lord

2008-03-19 19:44 UTC #28 lore raw

In reply to Tejun Heo

Quoted 1 line · Tejun Heo

Denys Dmytriyenko wrote:

..

Quoted 6 lines

Quoted 3 lines
Mar 14 23:51:55 [kernel] ata3: failed to read log page 10h (errno=-2)
Mar 14 23:51:55 [kernel] ata3.00: exception Emask 0x1 SAct 0x3f SErr 0x0 action 0x0
Mar 14 23:51:55 [kernel] ata3.00: irq_stat 0x00020002, device error via SDB FIS
This one is different. The drive reported device error but the driver couldn't get more information about the error (log page 10h contains it).

..

That, is one of the known errata that has yet to be fixed in the driver. The READ LOG EXT command cannot be used in the normal fashion after an NCQ error.

I've been waiting for more information for a couple of weeks from Marvell, and now have the necessary info. I don't think it will be fixed in 2.6.25, though -- the workaround may be rather complex.

We'll see.. depends how things go this week.

Cheers

Mark Lord

2008-03-19 19:44 UTC #29 lore raw

Quoted 7 lines · Mark Lord

Quoted 1 line · Tejun Heo

Denys Dmytriyenko wrote:

..

Quoted 4 lines

Quoted 3 lines

Mar 14 23:51:55 [kernel] ata3: failed to read log page 10h (errno=-2)
Mar 14 23:51:55 [kernel] ata3.00: exception Emask 0x1 SAct 0x3f SErr 0x0 action 0x0
Mar 14 23:51:55 [kernel] ata3.00: irq_stat 0x00020002, device error via SDB FIS

Quoted 6 lines

Quoted 2 lines
This one is different. The drive reported device error but the driver couldn't get more information about the error (log page 10h contains it).
..
That, is one of the known errata that has yet to be fixed in the driver. The READ LOG EXT command cannot be used in the normal fashion after an NCQ error.

..

Whoops.. scratch that.. I thought Denys was trialing sata_mv there, not sata_sil24 as it turns out.

-ml