* Sata Sil3512 bug?
@ 2007-09-27 13:51 MisterE
2007-09-28 12:25 ` Tejun Heo
0 siblings, 1 reply; 14+ messages in thread
From: MisterE @ 2007-09-27 13:51 UTC (permalink / raw)
To: jgarzik, linux-ide, benh
[-- Attachment #1: Type: text/plain, Size: 1037 bytes --]
Hello,
First off, i'm quite new to linux. I don't know the official way's to
report bugs. I'm not even sure that the bug is sata driver related. I
hope you can do some suggestions.
I recently bought 2 Sweex Sata controllers (without raid). This device
contains the Sil3512 chip.
I connected it to my D815EEA motherboard with a samsung hard drive.
When i mounted it and connected to it with WinScp or samba i got
"hangs"; a couple of seconds the filetransfer stopped.
The logs in var and the screen are spooled with errors like in "samsung error.txt".
I now have bought some Western Digitals drives. I get similar problems
(wd error.txt), but nog "hangs".
I've tried the controller in another motherboard, the ASUS CUSL2 (with similar specs)
and i don't have any problems. Can you help? I've included some logs
with may be of use.
btw: i use Debian unstable. I use the same hd with the OS (IDE drive)
on both systems, so we can exclude a faulty OS.
--
Best regards,
MisterE mailto:MisterE2002@zonnet.nl
[-- Attachment #2: samsung error.txt --]
[-- Type: text/plain, Size: 3880 bytes --]
Sep 24 17:42:43 fileserver kernel: NTFS driver 2.1.28 [Flags: R/W MODULE].
Sep 24 17:42:43 fileserver kernel: NTFS volume version 3.1.
Sep 24 17:44:05 fileserver kernel: NTFS volume version 3.1.
Sep 24 17:44:36 fileserver kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Sep 24 17:44:36 fileserver kernel: ata2.00: (BMDMA2 stat 0x6c0009)
Sep 24 17:44:36 fileserver kernel: ata2.00: cmd c8/00:0c:a8:01:bd/00:00:00:00:00/e1 tag 0 cdb 0x0 data 6144 in
Sep 24 17:44:36 fileserver kernel: res 51/04:00:b3:01:bd/00:00:00:00:00/e1 Emask 0x1 (device error)
Sep 24 17:44:36 fileserver kernel: ata2.00: configured for UDMA/100
Sep 24 17:44:36 fileserver kernel: ata2: EH complete
Sep 24 17:44:36 fileserver kernel: sd 1:0:0:0: [sda] 488397168 512-byte hardware sectors (250059 MB)
Sep 24 17:44:36 fileserver kernel: sd 1:0:0:0: [sda] Write Protect is off
Sep 24 17:44:36 fileserver kernel: sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00
Sep 24 17:44:36 fileserver kernel: sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Sep 24 17:44:36 fileserver kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Sep 24 17:44:36 fileserver kernel: ata2.00: (BMDMA2 stat 0x6d0009)
Sep 24 17:44:36 fileserver kernel: ata2.00: cmd c8/00:07:38:19:bd/00:00:00:00:00/e1 tag 0 cdb 0x0 data 3584 in
Sep 24 17:44:36 fileserver kernel: res 51/04:00:3e:19:bd/00:00:00:00:00/e1 Emask 0x1 (device error)
Sep 24 17:44:36 fileserver kernel: ata2.00: configured for UDMA/100
Sep 24 17:44:36 fileserver kernel: ata2: EH complete
Sep 24 17:44:36 fileserver kernel: sd 1:0:0:0: [sda] 488397168 512-byte hardware sectors (250059 MB)
Sep 24 17:44:36 fileserver kernel: sd 1:0:0:0: [sda] Write Protect is off
Sep 24 17:44:36 fileserver kernel: sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00
Sep 24 17:44:36 fileserver kernel: sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Sep 24 17:45:06 fileserver kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
Sep 24 17:45:06 fileserver kernel: ata2.00: cmd c8/00:80:3f:21:bd/00:00:00:00:00/e1 tag 0 cdb 0x0 data 65536 in
Sep 24 17:45:06 fileserver kernel: res 40/00:00:3e:19:bd/00:00:00:00:00/e1 Emask 0x4 (timeout)
Sep 24 17:45:07 fileserver kernel: ata2: soft resetting port
Sep 24 17:45:07 fileserver kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Sep 24 17:45:07 fileserver kernel: ata2.00: configured for UDMA/100
Sep 24 17:45:07 fileserver kernel: ata2: EH complete
Sep 24 17:45:07 fileserver kernel: sd 1:0:0:0: [sda] 488397168 512-byte hardware sectors (250059 MB)
Sep 24 17:45:07 fileserver kernel: sd 1:0:0:0: [sda] Write Protect is off
Sep 24 17:45:07 fileserver kernel: sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00
Sep 24 17:45:07 fileserver kernel: sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Sep 24 17:45:37 fileserver kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
Sep 24 17:45:37 fileserver kernel: ata2.00: cmd c8/00:80:3f:24:bd/00:00:00:00:00/e1 tag 0 cdb 0x0 data 65536 in
Sep 24 17:45:37 fileserver kernel: res 40/00:00:3e:19:bd/00:00:00:00:00/e1 Emask 0x4 (timeout)
Sep 24 17:45:37 fileserver kernel: ata2: soft resetting port
Sep 24 17:45:37 fileserver kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Sep 24 17:45:37 fileserver kernel: ata2.00: configured for UDMA/100
Sep 24 17:45:37 fileserver kernel: ata2: EH complete
Sep 24 17:45:37 fileserver kernel: sd 1:0:0:0: [sda] 488397168 512-byte hardware sectors (250059 MB)
Sep 24 17:45:37 fileserver kernel: sd 1:0:0:0: [sda] Write Protect is off
Sep 24 17:45:37 fileserver kernel: sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00
Sep 24 17:45:37 fileserver kernel: sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[-- Attachment #3: wd error.txt --]
[-- Type: text/plain, Size: 883 bytes --]
Sep 25 14:09:57 fileserver kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x2400000 action 0x0
Sep 25 14:09:57 fileserver kernel: ata2.00: (BMDMA2 stat 0x650001)
Sep 25 14:09:57 fileserver kernel: ata2.00: cmd ca/00:00:9b:39:02/00:00:00:00:00/e0 tag 0 cdb 0x0 data 131072 out
Sep 25 14:09:57 fileserver kernel: res 51/04:20:7b:3a:02/00:00:00:00:00/e0 Emask 0x1 (device error)
Sep 25 14:09:57 fileserver kernel: ata2.00: configured for UDMA/33
Sep 25 14:09:57 fileserver kernel: ata2: EH complete
Sep 25 14:09:57 fileserver kernel: sd 1:0:0:0: [sda] 976773168 512-byte hardware sectors (500108 MB)
Sep 25 14:09:57 fileserver kernel: sd 1:0:0:0: [sda] Write Protect is off
Sep 25 14:09:57 fileserver kernel: sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00
Sep 25 14:09:57 fileserver kernel: sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[-- Attachment #4: lshw asus.txt --]
[-- Type: text/plain, Size: 10549 bytes --]
fileserver
description: Tower Computer
product: System Name
vendor: System Manufacturer
version: System Version
serial: SYS-1234567890
width: 32 bits
capabilities: smbios-2.3 dmi-2.3
configuration: boot=normal chassis=tower
*-core
description: Motherboard
product: CUSL2-C
vendor: ASUSTeK Computer INC.
physical id: 0
version: REV 1.xx
serial: xxxxxxxxxxx
*-firmware
description: BIOS
vendor: Award Software, Inc.
physical id: 0
version: ASUS CUSL2-C ACPI BIOS Revision 1014 Beta 001 (09/20/2002)
size: 64KB
capacity: 448KB
capabilities: pci pnp apm upgrade shadowing escd cdboot bootselect socketedrom edd int13floppy360 int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int9keyboard int14serial int17printer int10video acpi usb agp ls120boot zipboot
*-cpu
description: CPU
product: Pentium III (Coppermine)
vendor: Intel Corp.
physical id: 4
bus info: cpu@0
version: 6.8.10
slot: PGA 370
size: 1GHz
capacity: 1600MHz
width: 32 bits
clock: 133MHz
capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pat pse36 mmx fxsr sse up
*-cache:0
description: L1 cache
physical id: 9
slot: L1 Cache
size: 32KB
capacity: 32KB
capabilities: pipeline-burst synchronous internal write-back data
*-cache:1
description: L2 cache
physical id: a
slot: L2 Cache
size: 256KB
capacity: 256KB
capabilities: pipeline-burst synchronous internal write-back data
*-memory
description: System Memory
physical id: 22
slot: System board or motherboard
size: 512MB
capacity: 512MB
*-bank:0
description: DIMM DRAM Synchronous
physical id: 0
slot: DIMM 1
size: 256MB
width: 64 bits
*-bank:1
description: DIMM DRAM Synchronous
physical id: 1
slot: DIMM 2
size: 256MB
width: 64 bits
*-bank:2
description: DIMM DRAM Synchronous [empty]
physical id: 2
slot: DIMM 3
*-pci
description: Host bridge
product: 82815 815 Chipset Host Bridge and Memory Controller Hub
vendor: Intel Corporation
physical id: 100
bus info: pci@0000:00:00.0
version: 02
width: 32 bits
clock: 33MHz
configuration: driver=agpgart-intel module=intel_agp
*-pci:0
description: PCI bridge
product: 82815 815 Chipset AGP Bridge
vendor: Intel Corporation
physical id: 1
bus info: pci@0000:00:01.0
version: 02
width: 32 bits
clock: 66MHz
capabilities: pci normal_decode bus_master
*-display
description: VGA compatible controller
product: MGA G400/G450
vendor: Matrox Graphics, Inc.
physical id: 0
bus info: pci@0000:01:00.0
version: 82
width: 32 bits
clock: 33MHz
capabilities: pm agp agp-2.0 vga bus_master cap_list
configuration: latency=64 maxlatency=32 mingnt=16
*-pci:1
description: PCI bridge
product: 82801 PCI Bridge
vendor: Intel Corporation
physical id: 1e
bus info: pci@0000:00:1e.0
version: 02
width: 32 bits
clock: 33MHz
capabilities: pci normal_decode bus_master
*-storage
description: Mass storage controller
product: SiI 3512 [SATALink/SATARaid] Serial ATA Controller
vendor: Silicon Image, Inc.
physical id: b
bus info: pci@0000:02:0b.0
version: 01
width: 32 bits
clock: 66MHz
capabilities: storage pm bus_master cap_list
configuration: driver=sata_sil latency=32 module=sata_sil
*-network
description: Ethernet interface
product: 83c170 EPIC/100 Fast Ethernet Adapter
vendor: Standard Microsystems Corp [SMC]
physical id: d
bus info: pci@0000:02:0d.0
logical name: eth2
version: 08
serial: 00:e0:29:6c:26:d2
size: 100MB/s
capacity: 100MB/s
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=epic100 driverversion=2.1 duplex=full ip=10.0.0.12 latency=32 link=yes maxlatency=28 mingnt=8 module=epic100 multicast=yes port=MII speed=100MB/s
*-isa
description: ISA bridge
product: 82801BA ISA Bridge (LPC)
vendor: Intel Corporation
physical id: 1f
bus info: pci@0000:00:1f.0
version: 02
width: 32 bits
clock: 33MHz
capabilities: isa bus_master
configuration: latency=0
*-ide
description: IDE interface
product: 82801BA IDE U100
vendor: Intel Corporation
physical id: 1f.1
bus info: pci@0000:00:1f.1
version: 02
width: 32 bits
clock: 33MHz
capabilities: ide bus_master
configuration: driver=PIIX_IDE latency=0 module=piix
*-ide:0
description: IDE Channel 0
physical id: 0
bus info: ide@0
logical name: ide0
clock: 33MHz
*-disk
description: ATA Disk
product: WDC AC36400L
vendor: Western Digital
physical id: 0
bus info: ide@0.0
logical name: /dev/hda
version: 09.09M08
serial: WD-WM4200668163
size: 6149MB
capacity: 6149MB
capabilities: ata dma lba iordy smart pm partitioned partitioned:dos
configuration: mode=udma2 smart=on
*-volume:0
description: Linux filesystem partition
physical id: 1
bus info: ide@0.0,1
logical name: /dev/hda1
capacity: 5828MB
capabilities: primary bootable
*-volume:1
description: Extended partition
physical id: 2
bus info: ide@0.0,2
logical name: /dev/hda2
size: 321MB
capacity: 321MB
capabilities: primary extended partitioned partitioned:extended
*-logicalvolume
description: Linux swap / Solaris partition
physical id: 5
logical name: /dev/hda5
capacity: 321MB
capabilities: nofs
*-ide:1
description: IDE Channel 1
physical id: 1
bus info: ide@1
logical name: ide1
clock: 33MHz
*-cdrom
description: DVD-RAM writer
product: HL-DT-ST DVDRAM GSA-H42L
physical id: 0
bus info: ide@1.0
logical name: /dev/hdc
version: SL00
serial: K176CJ80810
capabilities: packet atapi cdrom removable nonmagnetic dma lba iordy pm audio cd-r cd-rw dvd dvd-r dvd-ram
configuration: mode=udma4 status=nodisc
*-usb:0
description: USB Controller
product: 82801BA/BAM USB (Hub #1)
vendor: Intel Corporation
physical id: 1f.2
bus info: pci@0000:00:1f.2
version: 02
width: 32 bits
clock: 33MHz
capabilities: uhci bus_master
configuration: driver=uhci_hcd latency=0 module=uhci_hcd
*-usbhost
product: UHCI Host Controller
vendor: Linux 2.6.22-2-686 uhci_hcd
physical id: 1
bus info: usb@1
logical name: usb1
version: 2.06
capabilities: usb-1.10
configuration: maxpower=0mA slots=2 speed=12.0MB/s
*-serial
description: SMBus
product: 82801BA/BAM SMBus
vendor: Intel Corporation
physical id: 1f.3
bus info: pci@0000:00:1f.3
version: 02
width: 32 bits
clock: 33MHz
configuration: driver=i801_smbus latency=0 module=i2c_i801
*-usb:1
description: USB Controller
product: 82801BA/BAM USB (Hub #2)
vendor: Intel Corporation
physical id: 1f.4
bus info: pci@0000:00:1f.4
version: 02
width: 32 bits
clock: 33MHz
capabilities: uhci bus_master
configuration: driver=uhci_hcd latency=0 module=uhci_hcd
*-usbhost
product: UHCI Host Controller
vendor: Linux 2.6.22-2-686 uhci_hcd
physical id: 1
bus info: usb@2
logical name: usb2
version: 2.06
capabilities: usb-1.10
configuration: maxpower=0mA slots=2 speed=12.0MB/s
[-- Attachment #5: lspci asus.txt --]
[-- Type: text/plain, Size: 908 bytes --]
00:00.0 Host bridge: Intel Corporation 82815 815 Chipset Host Bridge and Memory Controller Hub (rev 02)
00:01.0 PCI bridge: Intel Corporation 82815 815 Chipset AGP Bridge (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 02)
00:1f.0 ISA bridge: Intel Corporation 82801BA ISA Bridge (LPC) (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801BA IDE U100 (rev 02)
00:1f.2 USB Controller: Intel Corporation 82801BA/BAM USB (Hub #1) (rev 02)
00:1f.3 SMBus: Intel Corporation 82801BA/BAM SMBus (rev 02)
00:1f.4 USB Controller: Intel Corporation 82801BA/BAM USB (Hub #2) (rev 02)
01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G400/G450 (rev 82)
02:0b.0 Mass storage controller: Silicon Image, Inc. SiI 3512 [SATALink/SATARaid] Serial ATA Controller (rev 01)
02:0d.0 Ethernet controller: Standard Microsystems Corp [SMC] 83c170 EPIC/100 Fast Ethernet Adapter (rev 08)
[-- Attachment #6: lshw intel.txt --]
[-- Type: text/plain, Size: 9902 bytes --]
fileserver
description: Computer
width: 32 bits
capabilities: smbios-2.3 dmi-2.3
configuration: boot=normal uuid=82F98A6F-1F59-11D5-BDC8-001083FDCE08
*-core
description: Motherboard
product: D815EEA
vendor: Intel Corporation
physical id: 0
version: AAA10378-405
serial: BLEA11230259
slot: LPT1
*-firmware
description: BIOS
vendor: Intel Corp.
physical id: 0
version: EA81510A.86A.0051.P11.0106190714 (06/19/2001)
size: 64KB
capacity: 448KB
capabilities: pci pnp apm upgrade shadowing escd cdboot bootselect edd int13floppynec int13floppytoshiba int13floppy360 int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int9keyboard int14serial int17printer int10video acpi usb agp ls120boot zipboot biosbootspecification
*-cpu
description: CPU
product: Pentium III (Coppermine)
vendor: Intel Corp.
physical id: 4
bus info: cpu@0
version: 6.8.6
slot: J4L1
size: 933MHz
capacity: 1100MHz
width: 32 bits
clock: 133MHz
capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pat pse36 mmx fxsr sse up
*-cache:0
description: L1 cache
physical id: 5
slot: None
size: 32KB
capacity: 32KB
clock: 25MHz (40.0ns)
capabilities: pipeline-burst synchronous internal write-back unified
*-cache:1
description: L2 cache
physical id: 6
slot: None
size: 256KB
capacity: 256KB
capabilities: synchronous internal write-back unified
*-memory
description: System Memory
physical id: 2e
slot: System board or motherboard
size: 256MB
*-bank:0
description: [empty]
physical id: 0
slot: DIMM0
*-bank:1
description: DIMM DRAM Synchronous 100 MHz (10.0 ns)
physical id: 1
slot: DIMM1
size: 128MB
width: 64 bits
clock: 100MHz (10.0ns)
*-bank:2
description: DIMM DRAM Synchronous 100 MHz (10.0 ns)
physical id: 2
slot: DIMM2
size: 128MB
width: 64 bits
clock: 100MHz (10.0ns)
*-pci
description: Host bridge
product: 82815 815 Chipset Host Bridge and Memory Controller Hub
vendor: Intel Corporation
physical id: 100
bus info: pci@0000:00:00.0
version: 02
width: 32 bits
clock: 33MHz
configuration: driver=agpgart-intel module=intel_agp
*-display
description: VGA compatible controller
product: 82815 CGC [Chipset Graphics Controller]
vendor: Intel Corporation
physical id: 2
bus info: pci@0000:00:02.0
version: 02
width: 32 bits
clock: 66MHz
capabilities: pm vga bus_master cap_list
configuration: latency=0
*-pci
description: PCI bridge
product: 82801 PCI Bridge
vendor: Intel Corporation
physical id: 1e
bus info: pci@0000:00:1e.0
version: 02
width: 32 bits
clock: 33MHz
capabilities: pci normal_decode bus_master
*-multimedia
description: Multimedia audio controller
product: ES1371 [AudioPCI-97]
vendor: Ensoniq
physical id: 7
bus info: pci@0000:01:07.0
version: 08
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list
configuration: driver=ENS1371 latency=32 maxlatency=128 mingnt=12 module=snd_ens1371
*-storage
description: Mass storage controller
product: SiI 3512 [SATALink/SATARaid] Serial ATA Controller
vendor: Silicon Image, Inc.
physical id: 9
bus info: pci@0000:01:09.0
version: 01
width: 32 bits
clock: 66MHz
capabilities: storage pm bus_master cap_list
configuration: driver=sata_sil latency=32 module=sata_sil
*-network
description: Ethernet interface
product: 3c905C-TX/TX-M [Tornado]
vendor: 3Com Corporation
physical id: c
bus info: pci@0000:01:0c.0
logical name: eth0
version: 78
serial: 00:01:02:e3:12:bb
size: 100MB/s
capacity: 100MB/s
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=3c59x duplex=full ip=10.0.0.8 latency=32 link=yes maxlatency=10 mingnt=10 module=3c59x multicast=yes port=MII speed=100MB/s
*-isa
description: ISA bridge
product: 82801BA ISA Bridge (LPC)
vendor: Intel Corporation
physical id: 1f
bus info: pci@0000:00:1f.0
version: 02
width: 32 bits
clock: 33MHz
capabilities: isa bus_master
configuration: latency=0
*-ide
description: IDE interface
product: 82801BA IDE U100
vendor: Intel Corporation
physical id: 1f.1
bus info: pci@0000:00:1f.1
version: 02
width: 32 bits
clock: 33MHz
capabilities: ide bus_master
configuration: driver=PIIX_IDE latency=0 module=piix
*-ide
description: IDE Channel 0
physical id: 0
bus info: ide@0
logical name: ide0
clock: 33MHz
*-disk
description: ATA Disk
product: WDC AC36400L
vendor: Western Digital
physical id: 0
bus info: ide@0.0
logical name: /dev/hda
version: 09.09M08
serial: WD-WM4200668163
size: 6149MB
capacity: 6149MB
capabilities: ata dma lba iordy smart pm partitioned partitioned:dos
configuration: mode=udma2 smart=on
*-volume:0
description: Linux filesystem partition
physical id: 1
bus info: ide@0.0,1
logical name: /dev/hda1
capacity: 5828MB
capabilities: primary bootable
*-volume:1
description: Extended partition
physical id: 2
bus info: ide@0.0,2
logical name: /dev/hda2
size: 321MB
capacity: 321MB
capabilities: primary extended partitioned partitioned:extended
*-logicalvolume
description: Linux swap / Solaris partition
physical id: 5
logical name: /dev/hda5
capacity: 321MB
capabilities: nofs
*-usb:0
description: USB Controller
product: 82801BA/BAM USB (Hub #1)
vendor: Intel Corporation
physical id: 1f.2
bus info: pci@0000:00:1f.2
version: 02
width: 32 bits
clock: 33MHz
capabilities: uhci bus_master
configuration: driver=uhci_hcd latency=0 module=uhci_hcd
*-usbhost
product: UHCI Host Controller
vendor: Linux 2.6.22-2-686 uhci_hcd
physical id: 1
bus info: usb@1
logical name: usb1
version: 2.06
capabilities: usb-1.10
configuration: maxpower=0mA slots=2 speed=12.0MB/s
*-serial
description: SMBus
product: 82801BA/BAM SMBus
vendor: Intel Corporation
physical id: 1f.3
bus info: pci@0000:00:1f.3
version: 02
width: 32 bits
clock: 33MHz
configuration: driver=i801_smbus latency=0 module=i2c_i801
*-usb:1
description: USB Controller
product: 82801BA/BAM USB (Hub #2)
vendor: Intel Corporation
physical id: 1f.4
bus info: pci@0000:00:1f.4
version: 02
width: 32 bits
clock: 33MHz
capabilities: uhci bus_master
configuration: driver=uhci_hcd latency=0 module=uhci_hcd
*-usbhost
product: UHCI Host Controller
vendor: Linux 2.6.22-2-686 uhci_hcd
physical id: 1
bus info: usb@2
logical name: usb2
version: 2.06
capabilities: usb-1.10
configuration: maxpower=0mA slots=2 speed=12.0MB/s
[-- Attachment #7: lspci intel.txt --]
[-- Type: text/plain, Size: 900 bytes --]
00:00.0 Host bridge: Intel Corporation 82815 815 Chipset Host Bridge and Memory Controller Hub (rev 02)
00:02.0 VGA compatible controller: Intel Corporation 82815 CGC [Chipset Graphics Controller] (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 02)
00:1f.0 ISA bridge: Intel Corporation 82801BA ISA Bridge (LPC) (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801BA IDE U100 (rev 02)
00:1f.2 USB Controller: Intel Corporation 82801BA/BAM USB (Hub #1) (rev 02)
00:1f.3 SMBus: Intel Corporation 82801BA/BAM SMBus (rev 02)
00:1f.4 USB Controller: Intel Corporation 82801BA/BAM USB (Hub #2) (rev 02)
01:07.0 Multimedia audio controller: Ensoniq ES1371 [AudioPCI-97] (rev 08)
01:09.0 Mass storage controller: Silicon Image, Inc. SiI 3512 [SATALink/SATARaid] Serial ATA Controller (rev 01)
01:0c.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev 78)
^ permalink raw reply [flat|nested] 14+ messages in thread* Re: Sata Sil3512 bug? 2007-09-27 13:51 Sata Sil3512 bug? MisterE @ 2007-09-28 12:25 ` Tejun Heo 2007-09-28 15:25 ` Re[2]: " MisterE 0 siblings, 1 reply; 14+ messages in thread From: Tejun Heo @ 2007-09-28 12:25 UTC (permalink / raw) To: MisterE; +Cc: jgarzik, linux-ide, benh Hello, MisterE wrote: > I've tried the controller in another motherboard, the ASUS CUSL2 (with similar specs) > and i don't have any problems. Can you help? I've included some logs > with may be of use. Did you use the same cable on both machines? Also, does the problem go away if you power the hard drive from the power supply of the other machine? -- tejun ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re[2]: Sata Sil3512 bug? 2007-09-28 12:25 ` Tejun Heo @ 2007-09-28 15:25 ` MisterE 2007-09-28 15:51 ` Alan Cox 0 siblings, 1 reply; 14+ messages in thread From: MisterE @ 2007-09-28 15:25 UTC (permalink / raw) To: Tejun Heo; +Cc: jgarzik, linux-ide, benh Hello Tejun, I've tried with 2 sata cables. Cables which don't give problems with the Asus motherboard. I also now use a new decent power supply (corsair vx450) for the intel. Before it, i used an Fortron supply. But it had no sata connectors so i used converter adapters. But replacing the supply did'nt solve it. btw. If i copy/delete from the Western Digital to my Windows pc (via winscp or samba) i don't get error messages. Only when i write to it. The data itself seems to get corrupted; tested with par2. uploaded with winscp (windows) to the western digital (sda1). Uploaded the same data to hda1. Tested the data on both drives with par2verify. Most files on sda1 are corrupted (2 to 4 blocks missing). Copying that data back to Windows and it give the same results in Quickpar. So reading does not have problems. The data written to hda1 is correct. I now inserted a videocard, instead of using the onboard card. And at first hand it looked solved, but some (much less) errors still happens. I did not change anything in the bios. The card: 02:00.0 VGA compatible controller: nVidia Corporation NV10 [GeForce 256 SDR] (rev 10) How can a videocard influence this? I wanted to build a fileserver, using the intel motherboard. Bacause of the fact that it has a onboard videocard. I can use the asus if i have to. But if it is a bug it can better be solved :) I have some other similar motherboards like the intel laying around. With and without onboard videocard. I also have a second D815EEA (probably still has an older BIOS, i have updated the current one because when i inserted my second 128MB memory it did not gave any picture on the onboard video card). So i can do some experiments if i have to. Hope, this helps... Friday, September 28, 2007, 2:25:05 PM, you wrote: > Hello, > MisterE wrote: >> I've tried the controller in another motherboard, the ASUS CUSL2 (with similar specs) >> and i don't have any problems. Can you help? I've included some logs >> with may be of use. > Did you use the same cable on both machines? Also, does the problem go > away if you power the hard drive from the power supply of the other machine? -- Best regards, MisterE mailto:MisterE2002@zonnet.nl ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Sata Sil3512 bug? 2007-09-28 15:25 ` Re[2]: " MisterE @ 2007-09-28 15:51 ` Alan Cox 2007-09-28 16:55 ` Tejun Heo 0 siblings, 1 reply; 14+ messages in thread From: Alan Cox @ 2007-09-28 15:51 UTC (permalink / raw) To: MisterE; +Cc: Tejun Heo, jgarzik, linux-ide, benh > sda1 are corrupted (2 to 4 blocks missing). Copying that data back to > Windows and it give the same results in Quickpar. So reading does not > have problems. The data written to hda1 is correct. We've got a whole pile of reports like this with the 3512 and almost always Nvidia chipset, plus reports of BIOS updates fixing it. That you see something similar on intel boards is a bit worrying. Alan ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Sata Sil3512 bug? 2007-09-28 15:51 ` Alan Cox @ 2007-09-28 16:55 ` Tejun Heo 2007-10-02 19:20 ` Re[2]: " MisterE 0 siblings, 1 reply; 14+ messages in thread From: Tejun Heo @ 2007-09-28 16:55 UTC (permalink / raw) To: Alan Cox; +Cc: MisterE, jgarzik, linux-ide, benh Alan Cox wrote: >> sda1 are corrupted (2 to 4 blocks missing). Copying that data back to >> Windows and it give the same results in Quickpar. So reading does not >> have problems. The data written to hda1 is correct. > > We've got a whole pile of reports like this with the 3512 and almost > always Nvidia chipset, plus reports of BIOS updates fixing it. That you > see something similar on intel boards is a bit worrying. Multiple sil3112/3512 + nvidia chipset problem doesn't usually involve device errors or timeouts. It usually corrupts data silently. And, yeah, data corruption on intel board is really disturbing. MisterE, do you have any processor powersaving mechanism enabled? If so, can you disable all and see whether that changes anything? -- tejun ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re[2]: Sata Sil3512 bug? 2007-09-28 16:55 ` Tejun Heo @ 2007-10-02 19:20 ` MisterE 2007-10-04 1:27 ` Tejun Heo 0 siblings, 1 reply; 14+ messages in thread From: MisterE @ 2007-10-02 19:20 UTC (permalink / raw) To: Tejun Heo; +Cc: Alan Cox, jgarzik, linux-ide, benh Hello Tejun, I build another setup with almost the same hardware. This motherboard had already the latest bios. I notice that the computer does almost never find the hard drive although the controller is found every time (with lspci). So i get no drive (sda) assigned. I don't always see the "bios" screen from the controller at startup. And in the past it showed the hard drive. So i could not experiment with this motherboard. After that i installed Windows XP and used the orginal (sweex) drivers with the first motherboard. This also makes the data corrupt. So it seems not to be an linux problem. So there is something wrong with the motherboard or the 3512 controller. After that i plugged both hard drives (ide with windows and sata disk) to the Asus board. No data corruption. So the hard disks are'nt the problem either. I'm thinking of replacing both 3512 controllers with a Promise SATA300 TX4. Do you know if there are problems with this device? Friday, September 28, 2007, 6:55:47 PM, you wrote: > Alan Cox wrote: >>> sda1 are corrupted (2 to 4 blocks missing). Copying that data back to >>> Windows and it give the same results in Quickpar. So reading does not >>> have problems. The data written to hda1 is correct. >> >> We've got a whole pile of reports like this with the 3512 and almost >> always Nvidia chipset, plus reports of BIOS updates fixing it. That you >> see something similar on intel boards is a bit worrying. > Multiple sil3112/3512 + nvidia chipset problem doesn't usually involve > device errors or timeouts. It usually corrupts data silently. And, > yeah, data corruption on intel board is really disturbing. > MisterE, do you have any processor powersaving mechanism enabled? If > so, can you disable all and see whether that changes anything? -- Best regards, MisterE mailto:MisterE2002@zonnet.nl ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Sata Sil3512 bug? 2007-10-02 19:20 ` Re[2]: " MisterE @ 2007-10-04 1:27 ` Tejun Heo 2007-10-04 19:03 ` Re[2]: " MisterE 2007-10-13 16:36 ` MisterE 0 siblings, 2 replies; 14+ messages in thread From: Tejun Heo @ 2007-10-04 1:27 UTC (permalink / raw) To: MisterE; +Cc: Alan Cox, jgarzik, linux-ide, benh Hello, MisterE wrote: > I build another setup with almost the same hardware. > This motherboard had already the latest bios. > I notice that the computer does almost never find the hard drive > although the controller is found every time (with lspci). What do you mean by "almost never"? Does it find the harddisk sometimes? Also, please post kernel boot log after disk detection failure. lspci result just indicates only that the PCI device is present. > So i get no > drive (sda) assigned. I don't always see the "bios" screen from the > controller at startup. And in the past it showed the hard drive. > So i could not experiment with this motherboard. Can you re-seat the controller or move it to another slot and see whether things change? > After that i installed Windows XP and used the orginal (sweex) > drivers with the first motherboard. This also makes the data corrupt. > So it seems not to be an linux problem. So there is something wrong with > the motherboard or the 3512 controller. > > After that i plugged both hard drives (ide with windows and sata disk) > to the Asus board. No data corruption. So the hard disks are'nt the > problem either. Hmmm... It's relieving to know that the problem isn't caused by sata_sil but I don't have much idea than it seems like something goes wrong on the PCI bus. :-( > I'm thinking of replacing both 3512 controllers with a Promise SATA300 > TX4. Do you know if there are problems with this device? I see occasional bug reports on sata_promise but AFAIK there haven't been any data corruption report. Mikael knows much better about promise controllers. Thanks. -- tejun ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re[2]: Sata Sil3512 bug? 2007-10-04 1:27 ` Tejun Heo @ 2007-10-04 19:03 ` MisterE 2007-10-13 16:36 ` MisterE 1 sibling, 0 replies; 14+ messages in thread From: MisterE @ 2007-10-04 19:03 UTC (permalink / raw) To: Tejun Heo; +Cc: Alan Cox, jgarzik, linux-ide, benh [-- Attachment #1: Type: text/plain, Size: 3086 bytes --] Hello Tejun, I made some new logs. Probably to many :) The number corresponded with the directory in the archive. 1: Much errors. I aborted the transfer after a while. 2: First i copied a movie (multiple archives) with winscp. After a while i got a time-out and the transfer stopped. And winscp crashed. After that i did some concurrent transfers; 3 movies at the same time with samba. 4: I had tried slot changing and insertion of videocard before. Now it looks to work. Don't know why it now works, probably a bios setting i changed in combination with the right slot. After it recognized the sda i did test for corruption. It looks if it gives more errors than the other board (when the videocard is also inserted). Probably amount of errors comparable with intel 1 withhout videocard. According to lshw is motherboard 1 vAAA10378-405 and motherboard 2 vAAA10378-402. I must say that i also had sometimes problems with the first intel not finding the hard drive. So, i really don't trust the motherboard anymore. And i had it with those boards.... :( Tomorrow i will stress-test the 2 sata controllers with the Asus board with 4 wd's sata drives connected. If it gives any corruption i will let you know... I would like to thank you all for helping me... :) Thursday, October 4, 2007, 3:27:18 AM, you wrote: > Hello, > MisterE wrote: >> I build another setup with almost the same hardware. >> This motherboard had already the latest bios. >> I notice that the computer does almost never find the hard drive >> although the controller is found every time (with lspci). > What do you mean by "almost never"? Does it find the harddisk > sometimes? Also, please post kernel boot log after disk detection > failure. lspci result just indicates only that the PCI device is present. >> So i get no >> drive (sda) assigned. I don't always see the "bios" screen from the >> controller at startup. And in the past it showed the hard drive. >> So i could not experiment with this motherboard. > Can you re-seat the controller or move it to another slot and see > whether things change? >> After that i installed Windows XP and used the orginal (sweex) >> drivers with the first motherboard. This also makes the data corrupt. >> So it seems not to be an linux problem. So there is something wrong with >> the motherboard or the 3512 controller. >> >> After that i plugged both hard drives (ide with windows and sata disk) >> to the Asus board. No data corruption. So the hard disks are'nt the >> problem either. > Hmmm... It's relieving to know that the problem isn't caused by sata_sil > but I don't have much idea than it seems like something goes wrong on > the PCI bus. :-( >> I'm thinking of replacing both 3512 controllers with a Promise SATA300 >> TX4. Do you know if there are problems with this device? > I see occasional bug reports on sata_promise but AFAIK there haven't > been any data corruption report. Mikael knows much better about promise > controllers. > Thanks. -- Best regards, MisterE mailto:MisterE2002@zonnet.nl [-- Attachment #2: LOGS.rar --] [-- Type: APPLICATION/OCTET-STREAM, Size: 264822 bytes --] ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re[2]: Sata Sil3512 bug? 2007-10-04 1:27 ` Tejun Heo 2007-10-04 19:03 ` Re[2]: " MisterE @ 2007-10-13 16:36 ` MisterE 2007-10-18 3:29 ` Tejun Heo 1 sibling, 1 reply; 14+ messages in thread From: MisterE @ 2007-10-13 16:36 UTC (permalink / raw) To: Tejun Heo; +Cc: Alan Cox, jgarzik, linux-ide, benh [-- Attachment #1: Type: text/plain, Size: 4559 bytes --] Hello Tejun, unfortunately. I today tried to build the array (4x500GB, so it is still building) and i got again a error: Oct 13 12:17:56 fileserver kernel: raid5: device sdc1 operational as raid disk 2 Oct 13 12:17:56 fileserver kernel: raid5: device sdb1 operational as raid disk 1 Oct 13 12:17:56 fileserver kernel: raid5: device sda1 operational as raid disk 0 Oct 13 12:17:56 fileserver kernel: raid5: allocated 4204kB for md0 Oct 13 12:17:56 fileserver kernel: raid5: raid level 5 set md0 active with 3 out of 4 devices, algorithm 2 Oct 13 12:17:56 fileserver kernel: RAID5 conf printout: Oct 13 12:17:56 fileserver kernel: --- rd:4 wd:3 Oct 13 12:17:56 fileserver kernel: disk 0, o:1, dev:sda1 Oct 13 12:17:56 fileserver kernel: disk 1, o:1, dev:sdb1 Oct 13 12:17:56 fileserver kernel: disk 2, o:1, dev:sdc1 Oct 13 12:18:24 fileserver kernel: RAID5 conf printout: Oct 13 12:18:24 fileserver kernel: --- rd:4 wd:3 Oct 13 12:18:24 fileserver kernel: disk 0, o:1, dev:sda1 Oct 13 12:18:24 fileserver kernel: disk 1, o:1, dev:sdb1 Oct 13 12:18:24 fileserver kernel: disk 2, o:1, dev:sdc1 Oct 13 12:18:24 fileserver kernel: disk 3, o:1, dev:sdd1 Oct 13 12:18:24 fileserver kernel: md: recovery of RAID array md0 Oct 13 12:18:24 fileserver kernel: md: minimum _guaranteed_ speed: 1000 KB/sec/disk. Oct 13 12:18:24 fileserver kernel: md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for recovery. Oct 13 12:18:24 fileserver kernel: md: using 128k window, over a total of 488383936 blocks. Oct 13 13:01:26 fileserver kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x2400000 action 0x0 Oct 13 13:01:26 fileserver kernel: ata4.00: (BMDMA2 stat 0x650001) Oct 13 13:01:26 fileserver kernel: ata4.00: cmd ca/00:f8:47:e1:5e/00:00:00:00:00/e4 tag 0 cdb 0x0 data 126976 out Oct 13 13:01:26 fileserver kernel: res 51/04:98:a7:e1:5e/00:00:00:00:00/e4 Emask 0x1 (device error) Oct 13 13:01:26 fileserver kernel: ata4.00: configured for UDMA/100 Oct 13 13:01:26 fileserver kernel: ata4: EH complete Oct 13 13:01:26 fileserver kernel: sd 3:0:0:0: [sdd] 976773168 512-byte hardware sectors (500108 MB) Oct 13 13:01:26 fileserver kernel: sd 3:0:0:0: [sdd] Write Protect is off Oct 13 13:01:26 fileserver kernel: sd 3:0:0:0: [sdd] Mode Sense: 00 3a 00 00 Oct 13 13:01:26 fileserver kernel: sd 3:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA I'm not sure if it will result in corrupt data? But i don't trust it anymore. You people advise me to not buy the Promise SATA300 TX4 controller and this Sweex PU102 (3512) seems to have problems. Not much choices left except the really expensive solutions. Is it really so hard to build a controller without problems?!? :( Thursday, October 4, 2007, 3:27:18 AM, you wrote: > Hello, > MisterE wrote: >> I build another setup with almost the same hardware. >> This motherboard had already the latest bios. >> I notice that the computer does almost never find the hard drive >> although the controller is found every time (with lspci). > What do you mean by "almost never"? Does it find the harddisk > sometimes? Also, please post kernel boot log after disk detection > failure. lspci result just indicates only that the PCI device is present. >> So i get no >> drive (sda) assigned. I don't always see the "bios" screen from the >> controller at startup. And in the past it showed the hard drive. >> So i could not experiment with this motherboard. > Can you re-seat the controller or move it to another slot and see > whether things change? >> After that i installed Windows XP and used the orginal (sweex) >> drivers with the first motherboard. This also makes the data corrupt. >> So it seems not to be an linux problem. So there is something wrong with >> the motherboard or the 3512 controller. >> >> After that i plugged both hard drives (ide with windows and sata disk) >> to the Asus board. No data corruption. So the hard disks are'nt the >> problem either. > Hmmm... It's relieving to know that the problem isn't caused by sata_sil > but I don't have much idea than it seems like something goes wrong on > the PCI bus. :-( >> I'm thinking of replacing both 3512 controllers with a Promise SATA300 >> TX4. Do you know if there are problems with this device? > I see occasional bug reports on sata_promise but AFAIK there haven't > been any data corruption report. Mikael knows much better about promise > controllers. > Thanks. -- Best regards, MisterE mailto:MisterE2002@zonnet.nl [-- Attachment #2: kern.log --] [-- Type: APPLICATION/OCTET-STREAM, Size: 36137 bytes --] Oct 13 12:05:45 fileserver kernel: Kernel logging (proc) stopped. Oct 13 12:05:45 fileserver kernel: Kernel log daemon terminating. Oct 13 12:06:56 fileserver kernel: klogd 1.5.0#1, log source = /proc/kmsg started. Oct 13 12:06:56 fileserver kernel: Linux version 2.6.22-2-686 (Debian 2.6.22-4) (waldi@debian.org) (gcc version 4.1.3 20070812 (prerelease) (Debian 4.1.2-15)) #1 SMP Fri Aug 31 00:24:01 UTC 2007 Oct 13 12:06:56 fileserver kernel: BIOS-provided physical RAM map: Oct 13 12:06:56 fileserver kernel: BIOS-e820: 0000000000000000 - 000000000009ec00 (usable) Oct 13 12:06:56 fileserver kernel: BIOS-e820: 000000000009ec00 - 00000000000a0000 (reserved) Oct 13 12:06:56 fileserver kernel: BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved) Oct 13 12:06:56 fileserver kernel: BIOS-e820: 0000000000100000 - 000000000ffeb000 (usable) Oct 13 12:06:56 fileserver kernel: BIOS-e820: 000000000ffeb000 - 000000000ffef000 (ACPI data) Oct 13 12:06:56 fileserver kernel: BIOS-e820: 000000000ffef000 - 000000000ffff000 (reserved) Oct 13 12:06:56 fileserver kernel: BIOS-e820: 000000000ffff000 - 0000000010000000 (ACPI NVS) Oct 13 12:06:56 fileserver kernel: BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved) Oct 13 12:06:56 fileserver kernel: 0MB HIGHMEM available. Oct 13 12:06:56 fileserver kernel: 255MB LOWMEM available. Oct 13 12:06:56 fileserver kernel: Entering add_active_range(0, 0, 65515) 0 entries of 256 used Oct 13 12:06:56 fileserver kernel: Zone PFN ranges: Oct 13 12:06:56 fileserver kernel: DMA 0 -> 4096 Oct 13 12:06:56 fileserver kernel: Normal 4096 -> 65515 Oct 13 12:06:56 fileserver kernel: HighMem 65515 -> 65515 Oct 13 12:06:56 fileserver kernel: early_node_map[1] active PFN ranges Oct 13 12:06:56 fileserver kernel: 0: 0 -> 65515 Oct 13 12:06:56 fileserver kernel: On node 0 totalpages: 65515 Oct 13 12:06:56 fileserver kernel: DMA zone: 32 pages used for memmap Oct 13 12:06:56 fileserver kernel: DMA zone: 0 pages reserved Oct 13 12:06:56 fileserver kernel: DMA zone: 4064 pages, LIFO batch:0 Oct 13 12:06:56 fileserver kernel: Normal zone: 479 pages used for memmap Oct 13 12:06:56 fileserver kernel: Normal zone: 60940 pages, LIFO batch:15 Oct 13 12:06:56 fileserver kernel: HighMem zone: 0 pages used for memmap Oct 13 12:06:56 fileserver kernel: DMI 2.3 present. Oct 13 12:06:56 fileserver kernel: ACPI: RSDP 000F7880, 0014 (r0 ASUS ) Oct 13 12:06:56 fileserver kernel: ACPI: RSDT 0FFEB000, 002C (r1 ASUS CUSL2-C 30303031 MSFT 31313031) Oct 13 12:06:56 fileserver kernel: ACPI: FACP 0FFEB080, 0074 (r1 ASUS CUSL2-C 30303031 MSFT 31313031) Oct 13 12:06:56 fileserver kernel: ACPI: DSDT 0FFEB100, 34D4 (r1 ASUS CUSL2-C 1000 MSFT 100000B) Oct 13 12:06:56 fileserver kernel: ACPI: FACS 0FFFF000, 0040 Oct 13 12:06:56 fileserver kernel: ACPI: BOOT 0FFEB040, 0028 (r1 ASUS CUSL2-C 30303031 MSFT 31313031) Oct 13 12:06:56 fileserver kernel: ACPI: PM-Timer IO Port: 0xe408 Oct 13 12:06:56 fileserver kernel: Allocating PCI resources starting at 20000000 (gap: 10000000:eff80000) Oct 13 12:06:56 fileserver kernel: Built 1 zonelists. Total pages: 65004 Oct 13 12:06:56 fileserver kernel: Kernel command line: root=/dev/hda1 ro Oct 13 12:06:56 fileserver kernel: Local APIC disabled by BIOS -- you can enable it with "lapic" Oct 13 12:06:56 fileserver kernel: mapped APIC to ffffd000 (0120b000) Oct 13 12:06:56 fileserver kernel: Enabling fast FPU save and restore... done. Oct 13 12:06:56 fileserver kernel: Enabling unmasked SIMD FPU exception support... done. Oct 13 12:06:56 fileserver kernel: Initializing CPU#0 Oct 13 12:06:56 fileserver kernel: PID hash table entries: 1024 (order: 10, 4096 bytes) Oct 13 12:06:56 fileserver kernel: Detected 1005.056 MHz processor. Oct 13 12:06:56 fileserver kernel: Console: colour VGA+ 80x25 Oct 13 12:06:56 fileserver kernel: Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) Oct 13 12:06:56 fileserver kernel: Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) Oct 13 12:06:56 fileserver kernel: Memory: 250756k/262060k available (1688k kernel code, 10776k reserved, 653k data, 244k init, 0k highmem) Oct 13 12:06:56 fileserver kernel: virtual kernel memory layout: Oct 13 12:06:56 fileserver kernel: fixmap : 0xfff4e000 - 0xfffff000 ( 708 kB) Oct 13 12:06:56 fileserver kernel: pkmap : 0xff800000 - 0xffc00000 (4096 kB) Oct 13 12:06:56 fileserver kernel: vmalloc : 0xd0800000 - 0xff7fe000 ( 751 MB) Oct 13 12:06:56 fileserver kernel: lowmem : 0xc0000000 - 0xcffeb000 ( 255 MB) Oct 13 12:06:56 fileserver kernel: .init : 0xc034f000 - 0xc038c000 ( 244 kB) Oct 13 12:06:56 fileserver kernel: .data : 0xc02a62bf - 0xc03497e4 ( 653 kB) Oct 13 12:06:56 fileserver kernel: .text : 0xc0100000 - 0xc02a62bf (1688 kB) Oct 13 12:06:56 fileserver kernel: Checking if this processor honours the WP bit even in supervisor mode... Ok. Oct 13 12:06:56 fileserver kernel: Calibrating delay using timer specific routine.. 2011.66 BogoMIPS (lpj=4023321) Oct 13 12:06:56 fileserver kernel: Security Framework v1.0.0 initialized Oct 13 12:06:56 fileserver kernel: SELinux: Disabled at boot. Oct 13 12:06:56 fileserver kernel: Capability LSM initialized Oct 13 12:06:56 fileserver kernel: Mount-cache hash table entries: 512 Oct 13 12:06:56 fileserver kernel: CPU: After generic identify, caps: 0383f9ff 00000000 00000000 00000000 00000000 00000000 00000000 Oct 13 12:06:56 fileserver kernel: CPU: L1 I cache: 16K, L1 D cache: 16K Oct 13 12:06:56 fileserver kernel: CPU: L2 cache: 256K Oct 13 12:06:56 fileserver kernel: CPU: After all inits, caps: 0383f9ff 00000000 00000000 00000040 00000000 00000000 00000000 Oct 13 12:06:56 fileserver kernel: Intel machine check architecture supported. Oct 13 12:06:56 fileserver kernel: Intel machine check reporting enabled on CPU#0. Oct 13 12:06:56 fileserver kernel: Compat vDSO mapped to ffffe000. Oct 13 12:06:56 fileserver kernel: Checking 'hlt' instruction... OK. Oct 13 12:06:56 fileserver kernel: SMP alternatives: switching to UP code Oct 13 12:06:56 fileserver kernel: Freeing SMP alternatives: 11k freed Oct 13 12:06:56 fileserver kernel: ACPI: Core revision 20070126 Oct 13 12:06:56 fileserver kernel: ACPI: setting ELCR to 0200 (from 0e20) Oct 13 12:06:56 fileserver kernel: CPU0: Intel Pentium III (Coppermine) stepping 0a Oct 13 12:06:56 fileserver kernel: SMP motherboard not detected. Oct 13 12:06:56 fileserver kernel: Local APIC not detected. Using dummy APIC emulation. Oct 13 12:06:56 fileserver kernel: Brought up 1 CPUs Oct 13 12:06:56 fileserver kernel: Booting paravirtualized kernel on bare hardware Oct 13 12:06:56 fileserver kernel: NET: Registered protocol family 16 Oct 13 12:06:56 fileserver kernel: ACPI: bus type pci registered Oct 13 12:06:56 fileserver kernel: PCI: PCI BIOS revision 2.10 entry at 0xf0df0, last bus=2 Oct 13 12:06:56 fileserver kernel: PCI: Using configuration type 1 Oct 13 12:06:56 fileserver kernel: Setting up standard PCI resources Oct 13 12:06:56 fileserver kernel: ACPI: Interpreter enabled Oct 13 12:06:56 fileserver kernel: ACPI: (supports S0 S1 S4 S5) Oct 13 12:06:56 fileserver kernel: ACPI: Using PIC for interrupt routing Oct 13 12:06:56 fileserver kernel: ACPI: PCI Root Bridge [PCI0] (0000:00) Oct 13 12:06:56 fileserver kernel: PCI: Probing PCI hardware (bus 00) Oct 13 12:06:56 fileserver kernel: PCI quirk: region e400-e47f claimed by ICH4 ACPI/GPIO/TCO Oct 13 12:06:56 fileserver kernel: PCI quirk: region ec00-ec3f claimed by ICH4 GPIO Oct 13 12:06:56 fileserver kernel: PCI: Transparent bridge - 0000:00:1e.0 Oct 13 12:06:56 fileserver kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] Oct 13 12:06:56 fileserver kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCI1._PRT] Oct 13 12:06:56 fileserver kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCI2._PRT] Oct 13 12:06:56 fileserver kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 *11 12 14 15) Oct 13 12:06:56 fileserver kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 *10 11 12 14 15) Oct 13 12:06:56 fileserver kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled. Oct 13 12:06:56 fileserver kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 *5 6 7 9 10 11 12 14 15) Oct 13 12:06:56 fileserver kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled. Oct 13 12:06:56 fileserver kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 *9 10 11 12 14 15) Oct 13 12:06:56 fileserver kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 *9 10 11 12 14 15) Oct 13 12:06:56 fileserver kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 *9 10 11 12 14 15) Oct 13 12:06:56 fileserver kernel: Linux Plug and Play Support v0.97 (c) Adam Belay Oct 13 12:06:56 fileserver kernel: pnp: PnP ACPI init Oct 13 12:06:56 fileserver kernel: ACPI: bus type pnp registered Oct 13 12:06:56 fileserver kernel: pnp: PnP ACPI: found 14 devices Oct 13 12:06:56 fileserver kernel: ACPI: ACPI bus type pnp unregistered Oct 13 12:06:56 fileserver kernel: PnPBIOS: Disabled by ACPI PNP Oct 13 12:06:56 fileserver kernel: PCI: Using ACPI for IRQ routing Oct 13 12:06:56 fileserver kernel: PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report Oct 13 12:06:56 fileserver kernel: NET: Registered protocol family 8 Oct 13 12:06:56 fileserver kernel: NET: Registered protocol family 20 Oct 13 12:06:56 fileserver kernel: ACPI: RTC can wake from S4 Oct 13 12:06:56 fileserver kernel: pnp: 00:00: iomem range 0x0-0x9ffff could not be reserved Oct 13 12:06:56 fileserver kernel: pnp: 00:00: iomem range 0xf0000-0xfffff could not be reserved Oct 13 12:06:56 fileserver kernel: pnp: 00:00: iomem range 0x100000-0xfffffff could not be reserved Oct 13 12:06:56 fileserver kernel: pnp: 00:00: iomem range 0xffb80000-0xffbfffff has been reserved Oct 13 12:06:56 fileserver kernel: pnp: 00:03: ioport range 0xe400-0xe47f has been reserved Oct 13 12:06:56 fileserver kernel: pnp: 00:03: ioport range 0xec00-0xec3f has been reserved Oct 13 12:06:56 fileserver kernel: Time: tsc clocksource has been installed. Oct 13 12:06:56 fileserver kernel: PCI: Bridge: 0000:00:01.0 Oct 13 12:06:56 fileserver kernel: IO window: d000-dfff Oct 13 12:06:56 fileserver kernel: MEM window: f6000000-f6cfffff Oct 13 12:06:56 fileserver kernel: PREFETCH window: f6f00000-f7ffffff Oct 13 12:06:56 fileserver kernel: PCI: Bridge: 0000:00:1e.0 Oct 13 12:06:56 fileserver kernel: IO window: 8000-bfff Oct 13 12:06:56 fileserver kernel: MEM window: f4800000-f5ffffff Oct 13 12:06:56 fileserver kernel: PREFETCH window: f6d00000-f6efffff Oct 13 12:06:56 fileserver kernel: PCI: Setting latency timer of device 0000:00:01.0 to 64 Oct 13 12:06:56 fileserver kernel: PCI: Setting latency timer of device 0000:00:1e.0 to 64 Oct 13 12:06:56 fileserver kernel: NET: Registered protocol family 2 Oct 13 12:06:56 fileserver kernel: IP route cache hash table entries: 2048 (order: 1, 8192 bytes) Oct 13 12:06:56 fileserver kernel: TCP established hash table entries: 8192 (order: 4, 98304 bytes) Oct 13 12:06:56 fileserver kernel: TCP bind hash table entries: 8192 (order: 4, 65536 bytes) Oct 13 12:06:56 fileserver kernel: TCP: Hash tables configured (established 8192 bind 8192) Oct 13 12:06:56 fileserver kernel: TCP reno registered Oct 13 12:06:56 fileserver kernel: checking if image is initramfs...<6>Switched to high resolution mode on CPU 0 Oct 13 12:06:56 fileserver kernel: it is Oct 13 12:06:56 fileserver kernel: Freeing initrd memory: 5543k freed Oct 13 12:06:56 fileserver kernel: Simple Boot Flag at 0x3a set to 0x1 Oct 13 12:06:56 fileserver kernel: audit: initializing netlink socket (disabled) Oct 13 12:06:56 fileserver kernel: audit(1192291588.204:1): initialized Oct 13 12:06:56 fileserver kernel: VFS: Disk quotas dquot_6.5.1 Oct 13 12:06:56 fileserver kernel: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) Oct 13 12:06:56 fileserver kernel: io scheduler noop registered Oct 13 12:06:56 fileserver kernel: io scheduler anticipatory registered Oct 13 12:06:56 fileserver kernel: io scheduler deadline registered Oct 13 12:06:56 fileserver kernel: io scheduler cfq registered (default) Oct 13 12:06:56 fileserver kernel: Boot video device is 0000:01:00.0 Oct 13 12:06:56 fileserver kernel: isapnp: Scanning for PnP cards... Oct 13 12:06:56 fileserver kernel: isapnp: No Plug & Play device found Oct 13 12:06:56 fileserver kernel: Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled Oct 13 12:06:56 fileserver kernel: serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A Oct 13 12:06:56 fileserver kernel: serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A Oct 13 12:06:56 fileserver kernel: 00:0a: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A Oct 13 12:06:56 fileserver kernel: 00:0b: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A Oct 13 12:06:56 fileserver kernel: RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize Oct 13 12:06:56 fileserver kernel: PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12 Oct 13 12:06:56 fileserver kernel: serio: i8042 KBD port at 0x60,0x64 irq 1 Oct 13 12:06:56 fileserver kernel: serio: i8042 AUX port at 0x60,0x64 irq 12 Oct 13 12:06:56 fileserver kernel: mice: PS/2 mouse device common for all mice Oct 13 12:06:56 fileserver kernel: TCP bic registered Oct 13 12:06:56 fileserver kernel: NET: Registered protocol family 1 Oct 13 12:06:56 fileserver kernel: NET: Registered protocol family 17 Oct 13 12:06:56 fileserver kernel: Using IPI No-Shortcut mode Oct 13 12:06:56 fileserver kernel: Freeing unused kernel memory: 244k freed Oct 13 12:06:56 fileserver kernel: input: AT Translated Set 2 keyboard as /class/input/input0 Oct 13 12:06:56 fileserver kernel: ACPI: Invalid PBLK length [5] Oct 13 12:06:56 fileserver kernel: SCSI subsystem initialized Oct 13 12:06:56 fileserver kernel: libata version 2.21 loaded. Oct 13 12:06:56 fileserver kernel: usbcore: registered new interface driver usbfs Oct 13 12:06:56 fileserver kernel: usbcore: registered new interface driver hub Oct 13 12:06:56 fileserver kernel: usbcore: registered new device driver usb Oct 13 12:06:56 fileserver kernel: Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 Oct 13 12:06:56 fileserver kernel: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx Oct 13 12:06:56 fileserver kernel: ICH2: IDE controller at PCI slot 0000:00:1f.1 Oct 13 12:06:56 fileserver kernel: ICH2: chipset revision 2 Oct 13 12:06:56 fileserver kernel: ICH2: not 100% native mode: will probe irqs later Oct 13 12:06:56 fileserver kernel: ide0: BM-DMA at 0x7800-0x7807, BIOS settings: hda:DMA, hdb:DMA Oct 13 12:06:56 fileserver kernel: ide1: BM-DMA at 0x7808-0x780f, BIOS settings: hdc:pio, hdd:pio Oct 13 12:06:56 fileserver kernel: Probing IDE interface ide0... Oct 13 12:06:56 fileserver kernel: USB Universal Host Controller Interface driver v3.0 Oct 13 12:06:56 fileserver kernel: hda: WDC AC36400L, ATA DISK drive Oct 13 12:06:56 fileserver kernel: Floppy drive(s): fd0 is 1.44M Oct 13 12:06:56 fileserver kernel: FDC 0 is a post-1991 82077 Oct 13 12:06:56 fileserver kernel: hdb: _NEC DVD_RW ND-3500AG, ATAPI CD/DVD-ROM drive Oct 13 12:06:56 fileserver kernel: hda: selected mode 0x42 Oct 13 12:06:56 fileserver kernel: hdb: selected mode 0x42 Oct 13 12:06:56 fileserver kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 Oct 13 12:06:56 fileserver kernel: Probing IDE interface ide1... Oct 13 12:06:56 fileserver kernel: ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 5 Oct 13 12:06:56 fileserver kernel: PCI: setting IRQ 5 as level-triggered Oct 13 12:06:56 fileserver kernel: ACPI: PCI Interrupt 0000:00:1f.2[D] -> Link [LNKD] -> GSI 5 (level, low) -> IRQ 5 Oct 13 12:06:56 fileserver kernel: PCI: Setting latency timer of device 0000:00:1f.2 to 64 Oct 13 12:06:56 fileserver kernel: uhci_hcd 0000:00:1f.2: UHCI Host Controller Oct 13 12:06:56 fileserver kernel: uhci_hcd 0000:00:1f.2: new USB bus registered, assigned bus number 1 Oct 13 12:06:56 fileserver kernel: uhci_hcd 0000:00:1f.2: irq 5, io base 0x00007400 Oct 13 12:06:56 fileserver kernel: usb usb1: configuration #1 chosen from 1 choice Oct 13 12:06:56 fileserver kernel: hub 1-0:1.0: USB hub found Oct 13 12:06:56 fileserver kernel: hub 1-0:1.0: 2 ports detected Oct 13 12:06:56 fileserver kernel: hda: max request size: 128KiB Oct 13 12:06:56 fileserver kernel: hda: 12594960 sectors (6448 MB) w/256KiB Cache, CHS=13328/15/63, UDMA(33) Oct 13 12:06:56 fileserver kernel: hda: cache flushes not supported Oct 13 12:06:56 fileserver kernel: hda: hda1 hda2 <ACPI: PCI Interrupt Link [LNKH] enabled at IRQ 9 Oct 13 12:06:56 fileserver kernel: PCI: setting IRQ 9 as level-triggered Oct 13 12:06:56 fileserver kernel: ACPI: PCI Interrupt 0000:00:1f.4[C] -> Link [LNKH] -> GSI 9 (level, low) -> IRQ 9 Oct 13 12:06:56 fileserver kernel: PCI: Setting latency timer of device 0000:00:1f.4 to 64 Oct 13 12:06:56 fileserver kernel: uhci_hcd 0000:00:1f.4: UHCI Host Controller Oct 13 12:06:56 fileserver kernel: uhci_hcd 0000:00:1f.4: new USB bus registered, assigned bus number 2 Oct 13 12:06:56 fileserver kernel: uhci_hcd 0000:00:1f.4: irq 9, io base 0x00007000 Oct 13 12:06:56 fileserver kernel: usb usb2: configuration #1 chosen from 1 choice Oct 13 12:06:56 fileserver kernel: hub 2-0:1.0: USB hub found Oct 13 12:06:56 fileserver kernel: hub 2-0:1.0: 2 ports detected Oct 13 12:06:56 fileserver kernel: hda5 > Oct 13 12:06:56 fileserver kernel: hdb: ATAPI 48X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33) Oct 13 12:06:56 fileserver kernel: Uniform CD-ROM driver Revision: 3.20 Oct 13 12:06:56 fileserver kernel: sata_sil 0000:02:0a.0: version 2.2 Oct 13 12:06:56 fileserver kernel: ACPI: PCI Interrupt Link [LNKG] enabled at IRQ 9 Oct 13 12:06:56 fileserver kernel: ACPI: PCI Interrupt 0000:02:0a.0[A] -> Link [LNKG] -> GSI 9 (level, low) -> IRQ 9 Oct 13 12:06:56 fileserver kernel: scsi0 : sata_sil Oct 13 12:06:56 fileserver kernel: scsi1 : sata_sil Oct 13 12:06:56 fileserver kernel: ata1: SATA max UDMA/100 cmd 0xd081a080 ctl 0xd081a08a bmdma 0xd081a000 irq 9 Oct 13 12:06:56 fileserver kernel: ata2: SATA max UDMA/100 cmd 0xd081a0c0 ctl 0xd081a0ca bmdma 0xd081a008 irq 9 Oct 13 12:06:56 fileserver kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Oct 13 12:06:56 fileserver kernel: ata1.00: ATA-7: WDC WD5000AAKS-00TMA0, 12.01C01, max UDMA/133 Oct 13 12:06:56 fileserver kernel: ata1.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 0/32) Oct 13 12:06:56 fileserver kernel: ata1.00: configured for UDMA/100 Oct 13 12:06:56 fileserver kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Oct 13 12:06:56 fileserver kernel: ata2.00: ATA-7: WDC WD5000AAKS-00TMA0, 12.01C01, max UDMA/133 Oct 13 12:06:56 fileserver kernel: ata2.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 0/32) Oct 13 12:06:56 fileserver kernel: ata2.00: configured for UDMA/100 Oct 13 12:06:56 fileserver kernel: scsi 0:0:0:0: Direct-Access ATA WDC WD5000AAKS-0 12.0 PQ: 0 ANSI: 5 Oct 13 12:06:56 fileserver kernel: scsi 1:0:0:0: Direct-Access ATA WDC WD5000AAKS-0 12.0 PQ: 0 ANSI: 5 Oct 13 12:06:56 fileserver kernel: ACPI: PCI Interrupt 0000:02:0b.0[A] -> Link [LNKH] -> GSI 9 (level, low) -> IRQ 9 Oct 13 12:06:56 fileserver kernel: scsi2 : sata_sil Oct 13 12:06:56 fileserver kernel: scsi3 : sata_sil Oct 13 12:06:56 fileserver kernel: ata3: SATA max UDMA/100 cmd 0xd0834080 ctl 0xd083408a bmdma 0xd0834000 irq 9 Oct 13 12:06:56 fileserver kernel: ata4: SATA max UDMA/100 cmd 0xd08340c0 ctl 0xd08340ca bmdma 0xd0834008 irq 9 Oct 13 12:06:56 fileserver kernel: ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Oct 13 12:06:56 fileserver kernel: ata3.00: ATA-7: WDC WD5000AAKS-00TMA0, 12.01C01, max UDMA/133 Oct 13 12:06:56 fileserver kernel: ata3.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 0/32) Oct 13 12:06:56 fileserver kernel: ata3.00: configured for UDMA/100 Oct 13 12:06:56 fileserver kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Oct 13 12:06:56 fileserver kernel: ata4.00: ATA-7: WDC WD5000AAKS-00TMA0, 12.01C01, max UDMA/133 Oct 13 12:06:56 fileserver kernel: ata4.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 0/32) Oct 13 12:06:56 fileserver kernel: ata4.00: configured for UDMA/100 Oct 13 12:06:56 fileserver kernel: scsi 2:0:0:0: Direct-Access ATA WDC WD5000AAKS-0 12.0 PQ: 0 ANSI: 5 Oct 13 12:06:56 fileserver kernel: scsi 3:0:0:0: Direct-Access ATA WDC WD5000AAKS-0 12.0 PQ: 0 ANSI: 5 Oct 13 12:06:56 fileserver kernel: ACPI: PCI Interrupt Link [LNKF] enabled at IRQ 9 Oct 13 12:06:56 fileserver kernel: ACPI: PCI Interrupt 0000:02:0d.0[A] -> Link [LNKF] -> GSI 9 (level, low) -> IRQ 9 Oct 13 12:06:56 fileserver kernel: 3c59x: Donald Becker and others. Oct 13 12:06:56 fileserver kernel: 0000:02:0d.0: 3Com PCI 3c905C Tornado at d0836000. Oct 13 12:06:56 fileserver kernel: sd 0:0:0:0: [sda] 976773168 512-byte hardware sectors (500108 MB) Oct 13 12:06:56 fileserver kernel: sd 0:0:0:0: [sda] Write Protect is off Oct 13 12:06:56 fileserver kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 Oct 13 12:06:56 fileserver kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Oct 13 12:06:56 fileserver kernel: sd 0:0:0:0: [sda] 976773168 512-byte hardware sectors (500108 MB) Oct 13 12:06:56 fileserver kernel: sd 0:0:0:0: [sda] Write Protect is off Oct 13 12:06:56 fileserver kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 Oct 13 12:06:56 fileserver kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Oct 13 12:06:56 fileserver kernel: sda: sda1 Oct 13 12:06:56 fileserver kernel: sd 0:0:0:0: [sda] Attached SCSI disk Oct 13 12:06:56 fileserver kernel: sd 1:0:0:0: [sdb] 976773168 512-byte hardware sectors (500108 MB) Oct 13 12:06:56 fileserver kernel: sd 1:0:0:0: [sdb] Write Protect is off Oct 13 12:06:56 fileserver kernel: sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00 Oct 13 12:06:56 fileserver kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Oct 13 12:06:56 fileserver kernel: sd 1:0:0:0: [sdb] 976773168 512-byte hardware sectors (500108 MB) Oct 13 12:06:56 fileserver kernel: sd 1:0:0:0: [sdb] Write Protect is off Oct 13 12:06:56 fileserver kernel: sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00 Oct 13 12:06:56 fileserver kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Oct 13 12:06:56 fileserver kernel: sdb: sdb1 Oct 13 12:06:56 fileserver kernel: sd 1:0:0:0: [sdb] Attached SCSI disk Oct 13 12:06:56 fileserver kernel: sd 2:0:0:0: [sdc] 976773168 512-byte hardware sectors (500108 MB) Oct 13 12:06:56 fileserver kernel: sd 2:0:0:0: [sdc] Write Protect is off Oct 13 12:06:56 fileserver kernel: sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00 Oct 13 12:06:56 fileserver kernel: sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Oct 13 12:06:56 fileserver kernel: sd 2:0:0:0: [sdc] 976773168 512-byte hardware sectors (500108 MB) Oct 13 12:06:56 fileserver kernel: sd 2:0:0:0: [sdc] Write Protect is off Oct 13 12:06:56 fileserver kernel: sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00 Oct 13 12:06:56 fileserver kernel: sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Oct 13 12:06:56 fileserver kernel: sdc: sdc1 Oct 13 12:06:56 fileserver kernel: sd 2:0:0:0: [sdc] Attached SCSI disk Oct 13 12:06:56 fileserver kernel: sd 3:0:0:0: [sdd] 976773168 512-byte hardware sectors (500108 MB) Oct 13 12:06:56 fileserver kernel: sd 3:0:0:0: [sdd] Write Protect is off Oct 13 12:06:56 fileserver kernel: sd 3:0:0:0: [sdd] Mode Sense: 00 3a 00 00 Oct 13 12:06:56 fileserver kernel: sd 3:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Oct 13 12:06:56 fileserver kernel: sd 3:0:0:0: [sdd] 976773168 512-byte hardware sectors (500108 MB) Oct 13 12:06:56 fileserver kernel: sd 3:0:0:0: [sdd] Write Protect is off Oct 13 12:06:56 fileserver kernel: sd 3:0:0:0: [sdd] Mode Sense: 00 3a 00 00 Oct 13 12:06:56 fileserver kernel: sd 3:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Oct 13 12:06:56 fileserver kernel: sdd: sdd1 Oct 13 12:06:56 fileserver kernel: sd 3:0:0:0: [sdd] Attached SCSI disk Oct 13 12:06:56 fileserver kernel: raid5: automatically using best checksumming function: pIII_sse Oct 13 12:06:56 fileserver kernel: pIII_sse : 1990.000 MB/sec Oct 13 12:06:56 fileserver kernel: raid5: using function: pIII_sse (1990.000 MB/sec) Oct 13 12:06:56 fileserver kernel: raid6: int32x1 308 MB/s Oct 13 12:06:56 fileserver kernel: raid6: int32x2 359 MB/s Oct 13 12:06:56 fileserver kernel: raid6: int32x4 286 MB/s Oct 13 12:06:56 fileserver kernel: raid6: int32x8 254 MB/s Oct 13 12:06:56 fileserver kernel: raid6: mmxx1 923 MB/s Oct 13 12:06:56 fileserver kernel: raid6: mmxx2 1152 MB/s Oct 13 12:06:56 fileserver kernel: raid6: sse1x1 833 MB/s Oct 13 12:06:56 fileserver kernel: raid6: sse1x2 1150 MB/s Oct 13 12:06:56 fileserver kernel: raid6: using algorithm sse1x2 (1150 MB/s) Oct 13 12:06:56 fileserver kernel: md: raid6 personality registered for level 6 Oct 13 12:06:56 fileserver kernel: md: raid5 personality registered for level 5 Oct 13 12:06:56 fileserver kernel: md: raid4 personality registered for level 4 Oct 13 12:06:56 fileserver kernel: md: md0 stopped. Oct 13 12:06:56 fileserver kernel: md: bind<sdb1> Oct 13 12:06:56 fileserver kernel: md: bind<sdc1> Oct 13 12:06:56 fileserver kernel: md: bind<sdd1> Oct 13 12:06:56 fileserver kernel: md: bind<sda1> Oct 13 12:06:56 fileserver kernel: raid5: device sda1 operational as raid disk 0 Oct 13 12:06:56 fileserver kernel: raid5: device sdd1 operational as raid disk 3 Oct 13 12:06:56 fileserver kernel: raid5: device sdc1 operational as raid disk 2 Oct 13 12:06:56 fileserver kernel: raid5: device sdb1 operational as raid disk 1 Oct 13 12:06:56 fileserver kernel: raid5: allocated 4204kB for md0 Oct 13 12:06:56 fileserver kernel: raid5: raid level 5 set md0 active with 4 out of 4 devices, algorithm 2 Oct 13 12:06:56 fileserver kernel: RAID5 conf printout: Oct 13 12:06:56 fileserver kernel: --- rd:4 wd:4 Oct 13 12:06:56 fileserver kernel: disk 0, o:1, dev:sda1 Oct 13 12:06:56 fileserver kernel: disk 1, o:1, dev:sdb1 Oct 13 12:06:56 fileserver kernel: disk 2, o:1, dev:sdc1 Oct 13 12:06:56 fileserver kernel: disk 3, o:1, dev:sdd1 Oct 13 12:06:56 fileserver kernel: Attempting manual resume Oct 13 12:06:56 fileserver kernel: kjournald starting. Commit interval 5 seconds Oct 13 12:06:56 fileserver kernel: EXT3-fs: mounted filesystem with ordered data mode. Oct 13 12:06:56 fileserver kernel: udev: renamed network interface eth0 to eth1 Oct 13 12:06:56 fileserver kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5 Oct 13 12:06:56 fileserver kernel: shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 Oct 13 12:06:56 fileserver kernel: intel_rng: FWH not detected Oct 13 12:06:56 fileserver kernel: Linux agpgart interface v0.102 (c) Dave Jones Oct 13 12:06:56 fileserver kernel: agpgart: Detected an Intel i815 Chipset. Oct 13 12:06:56 fileserver kernel: agpgart: AGP aperture is 64M @ 0xf8000000 Oct 13 12:06:56 fileserver kernel: iTCO_wdt: Intel TCO WatchDog Timer Driver v1.01 (21-Jan-2007) Oct 13 12:06:56 fileserver kernel: iTCO_wdt: Found a ICH2 TCO device (Version=1, TCOBASE=0xe460) Oct 13 12:06:56 fileserver kernel: iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0) Oct 13 12:06:56 fileserver kernel: Real Time Clock Driver v1.12ac Oct 13 12:06:56 fileserver kernel: ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 10 Oct 13 12:06:56 fileserver kernel: PCI: setting IRQ 10 as level-triggered Oct 13 12:06:56 fileserver kernel: ACPI: PCI Interrupt 0000:00:1f.3[B] -> Link [LNKB] -> GSI 10 (level, low) -> IRQ 10 Oct 13 12:06:56 fileserver kernel: input: PC Speaker as /class/input/input1 Oct 13 12:06:56 fileserver kernel: input: ImPS/2 Generic Wheel Mouse as /class/input/input2 Oct 13 12:06:56 fileserver kernel: parport_pc 00:09: reported by Plug and Play ACPI Oct 13 12:06:56 fileserver kernel: parport0: PC-style at 0x378 (0x778), irq 7, dma 3 [PCSPP,TRISTATE,COMPAT,ECP,DMA] Oct 13 12:06:56 fileserver kernel: Adding 329292k swap on /dev/hda5. Priority:-1 extents:1 across:329292k Oct 13 12:06:56 fileserver kernel: EXT3 FS on hda1, internal journal Oct 13 12:06:56 fileserver kernel: loop: module loaded Oct 13 12:06:56 fileserver kernel: device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: dm-devel@redhat.com Oct 13 12:06:56 fileserver kernel: eth1: setting full-duplex. Oct 13 12:06:57 fileserver kernel: NET: Registered protocol family 10 Oct 13 12:06:57 fileserver kernel: lo: Disabled Privacy Extensions Oct 13 12:06:58 fileserver kernel: input: Power Button (FF) as /class/input/input3 Oct 13 12:06:58 fileserver kernel: ACPI: Power Button (FF) [PWRF] Oct 13 12:06:58 fileserver kernel: input: Power Button (CM) as /class/input/input4 Oct 13 12:06:58 fileserver kernel: ACPI: Power Button (CM) [PWRB] Oct 13 12:07:07 fileserver kernel: eth1: no IPv6 routers present Oct 13 12:10:37 fileserver kernel: md: md0 stopped. Oct 13 12:10:37 fileserver kernel: md: unbind<sda1> Oct 13 12:10:37 fileserver kernel: md: export_rdev(sda1) Oct 13 12:10:37 fileserver kernel: md: unbind<sdd1> Oct 13 12:10:37 fileserver kernel: md: export_rdev(sdd1) Oct 13 12:10:37 fileserver kernel: md: unbind<sdc1> Oct 13 12:10:37 fileserver kernel: md: export_rdev(sdc1) Oct 13 12:10:37 fileserver kernel: md: unbind<sdb1> Oct 13 12:10:37 fileserver kernel: md: export_rdev(sdb1) Oct 13 12:13:08 fileserver kernel: sd 0:0:0:0: [sda] 976773168 512-byte hardware sectors (500108 MB) Oct 13 12:13:08 fileserver kernel: sd 0:0:0:0: [sda] Write Protect is off Oct 13 12:13:08 fileserver kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 Oct 13 12:13:08 fileserver kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Oct 13 12:13:08 fileserver kernel: sda: sda1 Oct 13 12:13:10 fileserver kernel: sd 0:0:0:0: [sda] 976773168 512-byte hardware sectors (500108 MB) Oct 13 12:13:10 fileserver kernel: sd 0:0:0:0: [sda] Write Protect is off Oct 13 12:13:10 fileserver kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 Oct 13 12:13:10 fileserver kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Oct 13 12:13:10 fileserver kernel: sda: sda1 Oct 13 12:13:33 fileserver kernel: sd 1:0:0:0: [sdb] 976773168 512-byte hardware sectors (500108 MB) Oct 13 12:13:33 fileserver kernel: sd 1:0:0:0: [sdb] Write Protect is off Oct 13 12:13:33 fileserver kernel: sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00 Oct 13 12:13:33 fileserver kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Oct 13 12:13:33 fileserver kernel: sdb: sdb1 Oct 13 12:13:35 fileserver kernel: sd 1:0:0:0: [sdb] 976773168 512-byte hardware sectors (500108 MB) Oct 13 12:13:35 fileserver kernel: sd 1:0:0:0: [sdb] Write Protect is off Oct 13 12:13:35 fileserver kernel: sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00 Oct 13 12:13:35 fileserver kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Oct 13 12:13:35 fileserver kernel: sdb: sdb1 Oct 13 12:13:52 fileserver kernel: sd 2:0:0:0: [sdc] 976773168 512-byte hardware sectors (500108 MB) Oct 13 12:13:52 fileserver kernel: sd 2:0:0:0: [sdc] Write Protect is off Oct 13 12:13:52 fileserver kernel: sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00 Oct 13 12:13:52 fileserver kernel: sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Oct 13 12:13:52 fileserver kernel: sdc: sdc1 Oct 13 12:13:54 fileserver kernel: sd 2:0:0:0: [sdc] 976773168 512-byte hardware sectors (500108 MB) Oct 13 12:13:54 fileserver kernel: sd 2:0:0:0: [sdc] Write Protect is off Oct 13 12:13:54 fileserver kernel: sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00 Oct 13 12:13:54 fileserver kernel: sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Oct 13 12:13:55 fileserver kernel: sdc: sdc1 Oct 13 12:14:12 fileserver kernel: sd 3:0:0:0: [sdd] 976773168 512-byte hardware sectors (500108 MB) Oct 13 12:14:12 fileserver kernel: sd 3:0:0:0: [sdd] Write Protect is off Oct 13 12:14:12 fileserver kernel: sd 3:0:0:0: [sdd] Mode Sense: 00 3a 00 00 Oct 13 12:14:12 fileserver kernel: sd 3:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Oct 13 12:14:12 fileserver kernel: sdd: sdd1 Oct 13 12:14:14 fileserver kernel: sd 3:0:0:0: [sdd] 976773168 512-byte hardware sectors (500108 MB) Oct 13 12:14:14 fileserver kernel: sd 3:0:0:0: [sdd] Write Protect is off Oct 13 12:14:14 fileserver kernel: sd 3:0:0:0: [sdd] Mode Sense: 00 3a 00 00 Oct 13 12:14:14 fileserver kernel: sd 3:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Oct 13 12:14:14 fileserver kernel: sdd: sdd1 Oct 13 12:17:34 fileserver kernel: md: md0 stopped. Oct 13 12:17:56 fileserver kernel: md: bind<sda1> Oct 13 12:17:56 fileserver kernel: md: bind<sdb1> Oct 13 12:17:56 fileserver kernel: md: bind<sdc1> Oct 13 12:17:56 fileserver kernel: md: bind<sdd1> Oct 13 12:17:56 fileserver kernel: raid5: device sdc1 operational as raid disk 2 Oct 13 12:17:56 fileserver kernel: raid5: device sdb1 operational as raid disk 1 Oct 13 12:17:56 fileserver kernel: raid5: device sda1 operational as raid disk 0 Oct 13 12:17:56 fileserver kernel: raid5: allocated 4204kB for md0 Oct 13 12:17:56 fileserver kernel: raid5: raid level 5 set md0 active with 3 out of 4 devices, algorithm 2 Oct 13 12:17:56 fileserver kernel: RAID5 conf printout: Oct 13 12:17:56 fileserver kernel: --- rd:4 wd:3 Oct 13 12:17:56 fileserver kernel: disk 0, o:1, dev:sda1 Oct 13 12:17:56 fileserver kernel: disk 1, o:1, dev:sdb1 Oct 13 12:17:56 fileserver kernel: disk 2, o:1, dev:sdc1 Oct 13 12:18:24 fileserver kernel: RAID5 conf printout: Oct 13 12:18:24 fileserver kernel: --- rd:4 wd:3 Oct 13 12:18:24 fileserver kernel: disk 0, o:1, dev:sda1 Oct 13 12:18:24 fileserver kernel: disk 1, o:1, dev:sdb1 Oct 13 12:18:24 fileserver kernel: disk 2, o:1, dev:sdc1 Oct 13 12:18:24 fileserver kernel: disk 3, o:1, dev:sdd1 Oct 13 12:18:24 fileserver kernel: md: recovery of RAID array md0 Oct 13 12:18:24 fileserver kernel: md: minimum _guaranteed_ speed: 1000 KB/sec/disk. Oct 13 12:18:24 fileserver kernel: md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for recovery. Oct 13 12:18:24 fileserver kernel: md: using 128k window, over a total of 488383936 blocks. Oct 13 13:01:26 fileserver kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x2400000 action 0x0 Oct 13 13:01:26 fileserver kernel: ata4.00: (BMDMA2 stat 0x650001) Oct 13 13:01:26 fileserver kernel: ata4.00: cmd ca/00:f8:47:e1:5e/00:00:00:00:00/e4 tag 0 cdb 0x0 data 126976 out Oct 13 13:01:26 fileserver kernel: res 51/04:98:a7:e1:5e/00:00:00:00:00/e4 Emask 0x1 (device error) Oct 13 13:01:26 fileserver kernel: ata4.00: configured for UDMA/100 Oct 13 13:01:26 fileserver kernel: ata4: EH complete Oct 13 13:01:26 fileserver kernel: sd 3:0:0:0: [sdd] 976773168 512-byte hardware sectors (500108 MB) Oct 13 13:01:26 fileserver kernel: sd 3:0:0:0: [sdd] Write Protect is off Oct 13 13:01:26 fileserver kernel: sd 3:0:0:0: [sdd] Mode Sense: 00 3a 00 00 Oct 13 13:01:26 fileserver kernel: sd 3:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Sata Sil3512 bug? 2007-10-13 16:36 ` MisterE @ 2007-10-18 3:29 ` Tejun Heo 0 siblings, 0 replies; 14+ messages in thread From: Tejun Heo @ 2007-10-18 3:29 UTC (permalink / raw) To: MisterE; +Cc: Alan Cox, jgarzik, linux-ide, benh MisterE wrote: > Oct 13 13:01:26 fileserver kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x2400000 action 0x0 > Oct 13 13:01:26 fileserver kernel: ata4.00: (BMDMA2 stat 0x650001) > Oct 13 13:01:26 fileserver kernel: ata4.00: cmd ca/00:f8:47:e1:5e/00:00:00:00:00/e4 tag 0 cdb 0x0 data 126976 out > Oct 13 13:01:26 fileserver kernel: res 51/04:98:a7:e1:5e/00:00:00:00:00/e4 Emask 0x1 (device error) > Oct 13 13:01:26 fileserver kernel: ata4.00: configured for UDMA/100 > Oct 13 13:01:26 fileserver kernel: ata4: EH complete > Oct 13 13:01:26 fileserver kernel: sd 3:0:0:0: [sdd] 976773168 512-byte hardware sectors (500108 MB) > Oct 13 13:01:26 fileserver kernel: sd 3:0:0:0: [sdd] Write Protect is off > Oct 13 13:01:26 fileserver kernel: sd 3:0:0:0: [sdd] Mode Sense: 00 3a 00 00 > Oct 13 13:01:26 fileserver kernel: sd 3:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA > > I'm not sure if it will result in corrupt data? But i don't trust it > anymore. That looks like a data transmission error. When you're transferring massive amount of data, things like that can happen and it won't cause data corruption. > You people advise me to not buy the Promise SATA300 TX4 controller and > this Sweex PU102 (3512) seems to have problems. Not much choices left > except the really expensive solutions. > > Is it really so hard to build a controller without problems?!? :( It seems so. :-( -- tejun ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Re[2]: Sata Sil3512 bug? @ 2007-10-03 7:26 Mikael Pettersson 2007-10-03 8:31 ` Alexander Sabourenkov 0 siblings, 1 reply; 14+ messages in thread From: Mikael Pettersson @ 2007-10-03 7:26 UTC (permalink / raw) To: MisterE2002, htejun; +Cc: alan, benh, jgarzik, linux-ide On Tue, 2 Oct 2007 21:20:23 +0200, MisterE wrote: > I build another setup with almost the same hardware. > This motherboard had already the latest bios. > I notice that the computer does almost never find the hard drive > although the controller is found every time (with lspci). So i get no > drive (sda) assigned. I don't always see the "bios" screen from the > controller at startup. And in the past it showed the hard drive. > So i could not experiment with this motherboard. > > After that i installed Windows XP and used the orginal (sweex) > drivers with the first motherboard. This also makes the data corrupt. > So it seems not to be an linux problem. So there is something wrong with > the motherboard or the 3512 controller. > > After that i plugged both hard drives (ide with windows and sata disk) > to the Asus board. No data corruption. So the hard disks are'nt the > problem either. > > I'm thinking of replacing both 3512 controllers with a Promise SATA300 > TX4. Do you know if there are problems with this device? (please don't top-post) There are no known data-corruption issues with Promise SATA cards. However, some of them, especially the 2nd generation SATA300 TX4, are known to trigger intermittent error interrupts (that are dealt with but may cause a speed reduction) in some systems. We're still scratching our heads on that issue. /Mikael > Friday, September 28, 2007, 6:55:47 PM, you wrote: > > > Alan Cox wrote: > >>> sda1 are corrupted (2 to 4 blocks missing). Copying that data back to > >>> Windows and it give the same results in Quickpar. So reading does not > >>> have problems. The data written to hda1 is correct. > >> > >> We've got a whole pile of reports like this with the 3512 and almost > >> always Nvidia chipset, plus reports of BIOS updates fixing it. That you > >> see something similar on intel boards is a bit worrying. > > > Multiple sil3112/3512 + nvidia chipset problem doesn't usually involve > > device errors or timeouts. It usually corrupts data silently. And, > > yeah, data corruption on intel board is really disturbing. > > > MisterE, do you have any processor powersaving mechanism enabled? If > > so, can you disable all and see whether that changes anything? ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Sata Sil3512 bug? 2007-10-03 7:26 Re[2]: " Mikael Pettersson @ 2007-10-03 8:31 ` Alexander Sabourenkov 2007-10-03 14:45 ` Re[2]: " MisterE 2007-10-14 12:07 ` Re[2]: " MisterE 0 siblings, 2 replies; 14+ messages in thread From: Alexander Sabourenkov @ 2007-10-03 8:31 UTC (permalink / raw) To: Mikael Pettersson; +Cc: MisterE2002, htejun, alan, benh, jgarzik, linux-ide Mikael Pettersson wrote: >> >> I'm thinking of replacing both 3512 controllers with a Promise SATA300 >> TX4. Do you know if there are problems with this device? > > (please don't top-post) > > There are no known data-corruption issues with Promise SATA cards. > However, some of them, especially the 2nd generation SATA300 TX4, > are known to trigger intermittent error interrupts (that are dealt > with but may cause a speed reduction) in some systems. We're still > scratching our heads on that issue. > But see this thread: http://marc.info/?l=linux-ide&m=119122463403033&w=2 http://www.spinics.net/lists/linux-ide/msg14868.html Personally I would not recommend Promise SATA300 TX4 at the moment. -- ./lxnt ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re[2]: Sata Sil3512 bug? 2007-10-03 8:31 ` Alexander Sabourenkov @ 2007-10-03 14:45 ` MisterE 2007-10-03 14:50 ` Alan Cox 2007-10-14 12:07 ` Re[2]: " MisterE 1 sibling, 1 reply; 14+ messages in thread From: MisterE @ 2007-10-03 14:45 UTC (permalink / raw) To: Alexander Sabourenkov Cc: Mikael Pettersson, htejun, alan, benh, jgarzik, linux-ide Hello Alexander, Wednesday, October 3, 2007, 10:31:17 AM, you wrote: > Mikael Pettersson wrote: >>> >>> I'm thinking of replacing both 3512 controllers with a Promise SATA300 >>> TX4. Do you know if there are problems with this device? >> >> (please don't top-post) >> >> There are no known data-corruption issues with Promise SATA cards. >> However, some of them, especially the 2nd generation SATA300 TX4, >> are known to trigger intermittent error interrupts (that are dealt >> with but may cause a speed reduction) in some systems. We're still >> scratching our heads on that issue. >> > But see this thread: > http://marc.info/?l=linux-ide&m=119122463403033&w=2 > http://www.spinics.net/lists/linux-ide/msg14868.html > Personally I would not recommend Promise SATA300 TX4 at the moment. That is not hopefull. Highpoint does not have sata controllers (Except softraid controllers). Other (real raid controllers) brands are too expensive or/and does not have a PCI interface. Maybe i should keep those 3512 cards? How are the user experiences with these controllers (except nvidia boards)? Because i don't really trust the intel boards so using the Asus would be an option. -- Best regards, MisterE mailto:MisterE2002@zonnet.nl ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Sata Sil3512 bug? 2007-10-03 14:45 ` Re[2]: " MisterE @ 2007-10-03 14:50 ` Alan Cox 0 siblings, 0 replies; 14+ messages in thread From: Alan Cox @ 2007-10-03 14:50 UTC (permalink / raw) To: MisterE Cc: Alexander Sabourenkov, Mikael Pettersson, htejun, benh, jgarzik, linux-ide > That is not hopefull. Highpoint does not have sata controllers (Except > softraid controllers). Other (real raid controllers) brands are too There are pretty much no "real" RAID controllers in the ATA world except the very high end pricy ones. ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re[2]: Sata Sil3512 bug? 2007-10-03 8:31 ` Alexander Sabourenkov 2007-10-03 14:45 ` Re[2]: " MisterE @ 2007-10-14 12:07 ` MisterE 2007-10-15 8:44 ` Alexander Sabourenkov 1 sibling, 1 reply; 14+ messages in thread From: MisterE @ 2007-10-14 12:07 UTC (permalink / raw) To: Alexander Sabourenkov Cc: Mikael Pettersson, htejun, alan, benh, jgarzik, linux-ide Hello, Alexander, does these problems with the Promise SATA300 TX4 happen to everyone? The only alternatives are using soft-raid products as normal controllers. Does anyone have experiences with the following products? * Highpoint RocketRAID 1640 (150 MB/s) * Highpoint RocketRAID 1740 (300 MB/s) * Adaptec 1210SA Wednesday, October 3, 2007, 10:31:17 AM, you wrote: > Mikael Pettersson wrote: >>> >>> I'm thinking of replacing both 3512 controllers with a Promise SATA300 >>> TX4. Do you know if there are problems with this device? >> >> (please don't top-post) >> >> There are no known data-corruption issues with Promise SATA cards. >> However, some of them, especially the 2nd generation SATA300 TX4, >> are known to trigger intermittent error interrupts (that are dealt >> with but may cause a speed reduction) in some systems. We're still >> scratching our heads on that issue. >> > But see this thread: > http://marc.info/?l=linux-ide&m=119122463403033&w=2 > http://www.spinics.net/lists/linux-ide/msg14868.html > Personally I would not recommend Promise SATA300 TX4 at the moment. -- Best regards, MisterE mailto:MisterE2002@zonnet.nl ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Sata Sil3512 bug? 2007-10-14 12:07 ` Re[2]: " MisterE @ 2007-10-15 8:44 ` Alexander Sabourenkov 0 siblings, 0 replies; 14+ messages in thread From: Alexander Sabourenkov @ 2007-10-15 8:44 UTC (permalink / raw) To: MisterE; +Cc: Mikael Pettersson, htejun, alan, benh, jgarzik, linux-ide MisterE wrote: > Hello, > > Alexander, does these problems with the Promise SATA300 TX4 happen to > everyone? > Most probably not, as I think it would have been fixed much faster then. I was waiting for a) release of 2.6.23, and b) me completing the move to another flat to retest all the latest developments in mainline and libata-dev. With a) done and b) almost done, I'll retest and report any issues quite soon. Besides, there is a report of TX4 and 2.6.23 not showing problems that were there with 2.6.22, ( see "Bug is fixed in 2.6.23.1: sata_promise: port is slow to respond, reset failed" thread). > The only alternatives are > using soft-raid products as normal controllers. Does anyone have experiences > with the following products? > * Highpoint RocketRAID 1640 (150 MB/s) > * Highpoint RocketRAID 1740 (300 MB/s) > * Adaptec 1210SA > For any kind of non-hobby task I'd skip trying to build a disk array to buying a SATA-SCSI/SATA-iSCSI box. While I had many mind-boggling issues with various combinations of SATA HDDs, onboard and standalone controllers, Promise and Infortrend disk arrays worked quite reliably. -- ./lxnt ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Sata Sil3512 bug?
@ 2007-10-04 0:46 Richard Scobie
0 siblings, 0 replies; 14+ messages in thread
From: Richard Scobie @ 2007-10-04 0:46 UTC (permalink / raw)
To: linux-ide
> There are pretty much no "real" RAID controllers in the ATA world
> except the very high end pricy ones.
Can anyone comment on the reliability or otherwise of Marvell 885X6081
controllers?
Supermicro do a reasonably priced non-RAID 8 drive SATA card using it:
http://www.supermicro.com/products/accessories/addon/AoC-SAT2-MV8.cfm
Regards,
Richard
^ permalink raw reply [flat|nested] 14+ messages in threadend of thread, other threads:[~2007-10-18 3:29 UTC | newest] Thread overview: 14+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2007-09-27 13:51 Sata Sil3512 bug? MisterE 2007-09-28 12:25 ` Tejun Heo 2007-09-28 15:25 ` Re[2]: " MisterE 2007-09-28 15:51 ` Alan Cox 2007-09-28 16:55 ` Tejun Heo 2007-10-02 19:20 ` Re[2]: " MisterE 2007-10-04 1:27 ` Tejun Heo 2007-10-04 19:03 ` Re[2]: " MisterE 2007-10-13 16:36 ` MisterE 2007-10-18 3:29 ` Tejun Heo -- strict thread matches above, loose matches on Subject: below -- 2007-10-03 7:26 Re[2]: " Mikael Pettersson 2007-10-03 8:31 ` Alexander Sabourenkov 2007-10-03 14:45 ` Re[2]: " MisterE 2007-10-03 14:50 ` Alan Cox 2007-10-14 12:07 ` Re[2]: " MisterE 2007-10-15 8:44 ` Alexander Sabourenkov 2007-10-04 0:46 Richard Scobie
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).