hard drives and system freezing

muxman · 02-10-2006, 03:56 PM

I have the following system and I'm having some problems with the system freezing up. It stays up for days or even weeks at a time but when I transfer large amounts of data from one of the hard drives on the motherboards controller to the hard drive that is on a ultra133tx2 Promise controller the system freezes. By large amounts of data I'm talking 500MB to 4-5GB or more. Some smaller transfers don't seem to have the problem. I have transfered 500MB to 1 or 2GB before without this happening, but most of the time it does. I'd say 90% or more the system does freeze. It doesn't seem to do it when reading files from the drive on the controller, only when putting them there.

It's a Sempron 2400 with 512MB RAM running debian with kernel 2.6.8-1-386.

lspci:

Code:

0000:00:00.0 Host bridge: VIA Technologies, Inc. VT8378 [KM400] Chipset Host Bridge
0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI Bridge
0000:00:08.0 Unknown mass storage controller: Promise Technology, Inc. 20269 (rev 02)
0000:00:09.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
0000:00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80)
0000:00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80)
0000:00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82)
0000:00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge
0000:00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
0000:00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 50)
0000:01:00.0 VGA compatible controller: VIA Technologies, Inc. VT8378 [S3 UniChrome] Integrated Video (rev 01)

lspci -v:

Code:

0000:00:00.0 Host bridge: VIA Technologies, Inc. VT8378 [KM400] Chipset Host Bridge
	Subsystem: VIA Technologies, Inc. VT8378 [KM400] Chipset Host Bridge
	Flags: bus master, 66MHz, medium devsel, latency 8
	Memory at e4000000 (32-bit, prefetchable) [size=64M]
	Capabilities: [80] AGP version 3.5
	Capabilities: [c0] Power Management version 2

0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI Bridge (prog-if 00 [Normal decode])
	Flags: bus master, 66MHz, medium devsel, latency 0
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
	Memory behind bridge: ec000000-edffffff
	Prefetchable memory behind bridge: e8000000-ebffffff
	Capabilities: [80] Power Management version 2

0000:00:08.0 Unknown mass storage controller: Promise Technology, Inc. 20269 (rev 02) (prog-if 85)
	Subsystem: Promise Technology, Inc. Ultra133TX2
	Flags: bus master, 66MHz, slow devsel, latency 32, IRQ 11
	I/O ports at db00 [size=8]
	I/O ports at e000 [size=4]
	I/O ports at d800 [size=8]
	I/O ports at d900 [size=4]
	I/O ports at da00 [size=16]
	Memory at ee010000 (32-bit, non-prefetchable) [size=16K]
	Capabilities: [60] Power Management version 1

0000:00:09.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
	Subsystem: Realtek Semiconductor Co., Ltd. RT8139
	Flags: bus master, medium devsel, latency 32, IRQ 10
	I/O ports at d000 [size=256]
	Memory at ee015000 (32-bit, non-prefetchable) [size=256]
	Capabilities: [50] Power Management version 2

0000:00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80) (prog-if 00 [UHCI])
	Subsystem: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller
	Flags: bus master, medium devsel, latency 32, IRQ 10
	I/O ports at dc00 [size=32]
	Capabilities: [80] Power Management version 2

0000:00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80) (prog-if 00 [UHCI])
	Subsystem: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller
	Flags: bus master, medium devsel, latency 32, IRQ 11
	I/O ports at dd00 [size=32]
	Capabilities: [80] Power Management version 2

0000:00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82) (prog-if 20 [EHCI])
	Subsystem: VIA Technologies, Inc. USB 2.0
	Flags: bus master, medium devsel, latency 32, IRQ 7
	Memory at ee014000 (32-bit, non-prefetchable) [size=256]
	Capabilities: [80] Power Management version 2

0000:00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge
	Subsystem: VIA Technologies, Inc. VT8235 ISA Bridge
	Flags: bus master, stepping, medium devsel, latency 0
	Capabilities: [c0] Power Management version 2

0000:00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) (prog-if 8a [Master SecP PriP])
	Subsystem: VIA Technologies, Inc. VT82C586/B/VT82C686/A/B/VT8233/A/C/VT8235 PIPC Bus Master IDE
	Flags: bus master, medium devsel, latency 32, IRQ 10
	I/O ports at df00 [size=16]
	Capabilities: [c0] Power Management version 2

0000:00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 50)
	Subsystem: Unknown device 16f3:4170
	Flags: medium devsel, IRQ 10
	I/O ports at d400 [size=256]
	Capabilities: [c0] Power Management version 2

0000:01:00.0 VGA compatible controller: VIA Technologies, Inc. VT8378 [S3 UniChrome] Integrated Video (rev 01) (prog-if 00 [VGA])
	Subsystem: VIA Technologies, Inc. VT8378 [S3 UniChrome] Integrated Video
	Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 10
	Memory at e8000000 (32-bit, prefetchable) [size=64M]
	Memory at ec000000 (32-bit, non-prefetchable) [size=16M]
	Capabilities: [60] Power Management version 2
	Capabilities: [70] AGP version 2.0

hdparm output for all 4 hard drives:

Code:

/dev/hda:
 multcount    =  0 (off)
 IO_support   =  1 (32-bit)
 unmaskirq    =  1 (on)
 using_dma    =  1 (on)
 keepsettings =  0 (off)
 readonly     =  0 (off)
 readahead    = 256 (on)
 geometry     = 65535/16/63, sectors = 120060864, start = 0


/dev/hdb:
 multcount    =  0 (off)
 IO_support   =  1 (32-bit)
 unmaskirq    =  1 (on)
 using_dma    =  1 (on)
 keepsettings =  0 (off)
 readonly     =  0 (off)
 readahead    = 256 (on)
 geometry     = 36483/255/63, sectors = 586114704, start = 0


/dev/hdd:
 multcount    =  0 (off)
 IO_support   =  1 (32-bit)
 unmaskirq    =  1 (on)
 using_dma    =  1 (on)
 keepsettings =  0 (off)
 readonly     =  0 (off)
 readahead    = 256 (on)
 geometry     = 36483/255/63, sectors = 586114704, start = 0


/dev/hde:
 multcount    =  0 (off)
 IO_support   =  0 (default 16-bit)
 unmaskirq    =  0 (off)
 using_dma    =  1 (on)
 keepsettings =  0 (off)
 readonly     =  0 (off)
 readahead    = 256 (on)
 geometry     = 36483/255/63, sectors = 586114704, start = 0

Device hdc is the dvd-r drive for a total of 5 ide devices.

Now I'm wondering, the first 3 hard drives are all set the same but the 4th, the one on the controller is not. If I turn on unmaskirq and put IO_support up to 32-bit so the settings for the drive match the others, would that solve this? I'm going to try this tonight or tomorrow and see. If so how do I set hdparm to always set the drive to use those settings? The changes made will only be good until the system is rebooted.

If those settings aren't the cause and they don't solve this please give me some other suggesttions that may fix this. If you need any more info let me know and I'll post it.

current dmesg:

Code:

Linux version 2.6.8-1-386 (joshk@trollwife) (gcc version 3.3.5 (Debian 1:3.3.5-2)) #1 Thu Nov 25 04:24:08 UTC 2004
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 000000000009e000 (usable)
 BIOS-e820: 000000000009e000 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 000000001bff0000 (usable)
 BIOS-e820: 000000001bff0000 - 000000001bff3000 (ACPI NVS)
 BIOS-e820: 000000001bff3000 - 000000001c000000 (ACPI data)
 BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
447MB LOWMEM available.
On node 0 totalpages: 114672
  DMA zone: 4096 pages, LIFO batch:1
  Normal zone: 110576 pages, LIFO batch:16
  HighMem zone: 0 pages, LIFO batch:1
DMI 2.3 present.
ACPI: RSDP (v000 KM266P                                    ) @ 0x000f6b10
ACPI: RSDT (v001 KM266P AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x1bff3040
ACPI: FADT (v001 KM266P AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x1bff30c0
ACPI: DSDT (v001 KM266P AWRDACPI 0x00001000 MSFT 0x0100000e) @ 0x00000000
ACPI: PM-Timer IO Port: 0x4008
Built 1 zonelists
Kernel command line: root=/dev/hda1 ro acpi=force 
Local APIC disabled by BIOS -- reenabling.
Found and enabled local APIC!
Initializing CPU#0
PID hash table entries: 2048 (order 11: 16384 bytes)
Detected 1650.002 MHz processor.
Using pmtmr for high-res timesource
Console: colour VGA+ 80x25
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 447104k/458688k available (1332k kernel code, 10788k reserved, 729k data, 204k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay loop... 3276.80 BogoMIPS
Security Scaffold v1.0.0 initialized
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
CPU: After generic identify, caps: 0383fbff c1cbfbff 00000000 00000000
CPU: After vendor identify, caps:  0383fbff c1cbfbff 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 00000020
CPU: AMD Sempron(tm)   2400+ stepping 01
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
Checking for popad bug... OK.
enabled ExtINT on CPU#0
ESR value before enabling vector: 00000000
ESR value after enabling vector: 00000000
Using local APIC timer interrupts.
calibrating APIC timer ...
..... CPU clock speed is 1649.0732 MHz.
..... host bus clock speed is 329.0946 MHz.
checking if image is initramfs...it isn't (ungzip failed); looks like an initrd
Freeing initrd memory: 4260k freed
NET: Registered protocol family 16
EISA bus registered
PCI: PCI BIOS revision 2.10 entry at 0xfb750, last bus=1
PCI: Using configuration type 1
mtrr: v2.0 (20020519)
ACPI: Subsystem revision 20040326
ACPI: IRQ9 SCI: Level Trigger.
spurious 8259A interrupt: IRQ7.
ACPI: Interpreter enabled
ACPI: Using PIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (00:00)
PCI: Probing PCI hardware (bus 00)
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 6 7 *10 11 12)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 6 7 10 *11 12)
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 6 7 10 11 12) *5
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 6 *7 10 11 12)
ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 6 7 10 11 12) *0, disabled.
ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 6 7 10 11 12) *0, disabled.
ACPI: PCI Interrupt Link [LNK0] (IRQs 3 4 6 7 10 11 12) *0, disabled.
ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 6 7 10 11 12) *0, disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
PnPBIOS: Scanning system for PnP BIOS support...
PnPBIOS: Found PnP BIOS installation structure at 0xc00fc190
PnPBIOS: PnP BIOS version 1.0, entry 0xf0000:0xc1c0, dseg 0xf0000
PnPBIOS: 11 nodes reported by PnP BIOS; 11 recorded by driver
PCI: Using ACPI for IRQ routing
ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 11
ACPI: PCI interrupt 0000:00:08.0[A] -> GSI 11 (level, low) -> IRQ 11
ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 10
ACPI: PCI interrupt 0000:00:09.0[A] -> GSI 10 (level, low) -> IRQ 10
ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 10
ACPI: PCI interrupt 0000:00:10.0[A] -> GSI 10 (level, low) -> IRQ 10
ACPI: PCI interrupt 0000:00:10.1[B] -> GSI 11 (level, low) -> IRQ 11
ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 7
ACPI: PCI interrupt 0000:00:10.3[D] -> GSI 7 (level, low) -> IRQ 7
ACPI: PCI interrupt 0000:00:11.1[A] -> GSI 10 (level, low) -> IRQ 10
ACPI: PCI interrupt 0000:00:11.5[C] -> GSI 10 (level, low) -> IRQ 10
ACPI: PCI interrupt 0000:01:00.0[A] -> GSI 10 (level, low) -> IRQ 10
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
devfs: 2004-01-31 Richard Gooch (rgooch@atnf.csiro.au)
devfs: boot_options: 0x0
Initializing Cryptographic API
PCI: Via IRQ fixup for 0000:00:11.5, from 5 to 10
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Serial: 8250/16550 driver $Revision: 1.90 $ 54 ports, IRQ sharing enabled
RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
input: AT Translated Set 2 keyboard on isa0060/serio0
EISA: Probing bus 0 at eisa0
EISA: Detected 0 cards.
NET: Registered protocol family 2
IP: routing cache hash table of 4096 buckets, 32Kbytes
TCP: Hash tables configured (established 32768 bind 65536)
NET: Registered protocol family 8
NET: Registered protocol family 20
ACPI: (supports S0 S1 S4 S5)
RAMDISK: cramfs filesystem found at block 0
RAMDISK: Loading 4260 blocks [1 disk] into ram disk... |/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-done.
VFS: Mounted root (cramfs filesystem) readonly.
Freeing unused kernel memory: 204k freed
vesafb: probe of vesafb0 failed with error -6
NET: Registered protocol family 1
SCSI subsystem initialized
libata version 1.02 loaded.
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
PDC20269: IDE controller at PCI slot 0000:00:08.0
ACPI: PCI interrupt 0000:00:08.0[A] -> GSI 11 (level, low) -> IRQ 11
PDC20269: chipset revision 2
PDC20269: 100% native mode on irq 11
    ide2: BM-DMA at 0xda00-0xda07, BIOS settings: hde:pio, hdf:pio
    ide3: BM-DMA at 0xda08-0xda0f, BIOS settings: hdg:pio, hdh:pio
hde: Maxtor 6L300R0, ATA DISK drive
Using anticipatory io scheduler
ide2 at 0xdb00-0xdb07,0xe002 on irq 11
hde: max request size: 1024KiB
hde: 586114704 sectors (300090 MB) w/16384KiB Cache, CHS=36483/255/63, UDMA(133)
 /dev/ide/host2/bus0/target0/lun0: p1
VP_IDE: IDE controller at PCI slot 0000:00:11.1
ACPI: PCI interrupt 0000:00:11.1[A] -> GSI 10 (level, low) -> IRQ 10
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
VP_IDE: VIA vt8235 (rev 00) IDE UDMA133 controller on pci0000:00:11.1
    ide0: BM-DMA at 0xdf00-0xdf07, BIOS settings: hda:DMA, hdb:DMA
    ide1: BM-DMA at 0xdf08-0xdf0f, BIOS settings: hdc:DMA, hdd:DMA
hda: Maxtor 96147U8, ATA DISK drive
hdb: Maxtor 6B300R0, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hda: max request size: 128KiB
hda: 120060864 sectors (61471 MB) w/2048KiB Cache, CHS=65535/16/63, UDMA(66)
 /dev/ide/host0/bus0/target0/lun0: p1 p2 p3 < p5 >
hdb: max request size: 1024KiB
hdb: 586114704 sectors (300090 MB) w/16384KiB Cache, CHS=36483/255/63, UDMA(133)
 /dev/ide/host0/bus0/target1/lun0: p1
hdc: TOSHIBA DVD-ROM SD-R5112, ATAPI CD/DVD-ROM drive
hdd: Maxtor 6B300R0, ATA DISK drive
ide1 at 0x170-0x177,0x376 on irq 15
hdd: max request size: 1024KiB
hdd: 586114704 sectors (300090 MB) w/16384KiB Cache, CHS=36483/255/63, UDMA(133)
 /dev/ide/host0/bus1/target1/lun0: p1
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
Adding 1044184k swap on /dev/hda5.  Priority:-1 extents:1
EXT3 FS on hda1, internal journal
Real Time Clock Driver v1.12
hdc: ATAPI 40X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
Capability LSM initialized
kjournald starting.  Commit interval 5 seconds
EXT3 FS on hda2, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
SGI XFS with ACLs, security attributes, realtime, large block numbers, no debug enabled
SGI XFS Quota Management subsystem
XFS mounting filesystem hdb1
Ending clean XFS mount for filesystem: hdb1
XFS mounting filesystem hdd1
Ending clean XFS mount for filesystem: hdd1
XFS mounting filesystem hde1
Ending clean XFS mount for filesystem: hde1
8139too Fast Ethernet driver 0.9.27
ACPI: PCI interrupt 0000:00:09.0[A] -> GSI 10 (level, low) -> IRQ 10
eth0: RealTek RTL8139 at 0xd000, 00:90:47:04:2f:31, IRQ 10
eth0:  Identified 8139 chip type 'RTL-8100B/8139D'
usbcore: registered new driver usbfs
usbcore: registered new driver hub
USB Universal Host Controller Interface driver v2.2
ACPI: PCI interrupt 0000:00:10.0[A] -> GSI 10 (level, low) -> IRQ 10
uhci_hcd 0000:00:10.0: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller
uhci_hcd 0000:00:10.0: irq 10, io base 0000dc00
uhci_hcd 0000:00:10.0: new USB bus registered, assigned bus number 1
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
ACPI: PCI interrupt 0000:00:10.1[B] -> GSI 11 (level, low) -> IRQ 11
uhci_hcd 0000:00:10.1: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (#2)
uhci_hcd 0000:00:10.1: irq 11, io base 0000dd00
uhci_hcd 0000:00:10.1: new USB bus registered, assigned bus number 2
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
ACPI: PCI interrupt 0000:00:10.3[D] -> GSI 7 (level, low) -> IRQ 7
ehci_hcd 0000:00:10.3: VIA Technologies, Inc. USB 2.0
ehci_hcd 0000:00:10.3: irq 7, pci mem dc82d000
ehci_hcd 0000:00:10.3: new USB bus registered, assigned bus number 3
ehci_hcd 0000:00:10.3: USB 2.0 enabled, EHCI 1.00, driver 2004-May-10
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 4 ports detected
irda_init()
NET: Registered protocol family 23
via82xx: Assuming DXS channels with 48k fixed sample rate.
         Please try dxs_support=1 or dxs_support=4 option
         and report if it works on your machine.
ACPI: PCI interrupt 0000:00:11.5[C] -> GSI 10 (level, low) -> IRQ 10
PCI: Setting latency timer of device 0000:00:11.5 to 64
Linux agpgart interface v0.100 (c) Dave Jones
agpgart: Detected VIA KM400/KM400A chipset
agpgart: Maximum main memory to use for agp memory: 380M
agpgart: AGP aperture is 64M @ 0xe4000000
cpci_hotplug: CompactPCI Hot Plug Core version: 0.2
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: acpi_shpchprm:\_SB_.PCI0 evaluate _BBN fail=0x5
shpchp: acpi_shpchprm:get_device PCI ROOT HID fail=0x5
pciehp: acpi_pciehprm:\_SB_.PCI0 evaluate _BBN fail=0x5
pciehp: acpi_pciehprm:get_device PCI ROOT HID fail=0x5
8139cp: 10/100 PCI Ethernet driver v1.2 (Mar 22, 2004)
input: PC Speaker
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
ttyS0: LSR safety check engaged!
ttyS0: LSR safety check engaged!
NET: Registered protocol family 10
Disabled Privacy Extensions on device c02ca840(lo)
IPv6 over IPv4 tunneling driver
eth0: no IPv6 routers present
apm: BIOS version 1.2 Flags 0x07 (Driver version 1.16ac)
apm: overridden by ACPI.
input: ImPS/2 Logitech Wheel Mouse on isa0060/serio1
ts: Compaq touchscreen protocol output
mice: PS/2 mouse device common for all mice
apm: BIOS version 1.2 Flags 0x07 (Driver version 1.16ac)
apm: overridden by ACPI.
devfs_mk_dev: could not append to parent for sound/audio
apm: BIOS version 1.2 Flags 0x07 (Driver version 1.16ac)
apm: overridden by ACPI.

aus9 · 02-11-2006, 08:14 AM

your lspci listing for promise is not good.....i wonder if you have a pci card based scsi/raid drive? and that your bios has not been configured properly for that setting?

were you going to use the card to connect 2 drives and raid them?

if you read the forum not good support such as
http://www.linuxquestions.org/questi...ht=ultra133tx2
http://www.linuxquestions.org/questi...ht=ultra133tx2

muxman · 02-11-2006, 09:26 AM

Quote:

Originally Posted by aus9

your lspci listing for promise is not good.....i wonder if you have a pci card based scsi/raid drive? and that your bios has not been configured properly for that setting?

were you going to use the card to connect 2 drives and raid them?

if you read the forum not good support such as
http://www.linuxquestions.org/questi...ht=ultra133tx2
http://www.linuxquestions.org/questi...ht=ultra133tx2

What's not good about the lspci listing? I've seen others with lspci output that looks the same. Any suggestions on how to fix it? I'm not doind raid, just using it as a controller for more drives. The drive shows as device hde which is an ide device, not sde which would be scsi.

aus9 · 02-13-2006, 07:34 AM

1 I was alluding to line 3 listing unknowm mass storage and my links were talking about others who found their defaults kernels not good and I think one stayed with a 2.4 series and it worked.

2 umm, does your bios have an option like my gigabyte that allows the card to be detected as a scsi....even if its not eg
advanced bios feature...change sata/raid/scsi to scsi for the card connected drive PLUS
advanced bios feature ......your boot order X (for card) changes to scsi in lieu of probably IDE

3 I have waffled on in the past about the kernel 2.4 seeing a sata drive (even if yours is not) as a hde and in the 2.6 series my sata is see as a hda.

my point is that you can help it be seen differently by using a live cd to format it differently

fdisk /dev/sdX or hdX will affect the kernels way of seeing it.

Do not try this unless you grasp my point as I do not want to be responsible for wasting your time.
However, I am replying in the hope I help...like all my posts.

4 btw you could try a vanilla kernel?

5 And wasting your money you could search the HCL and see if there is a card that is more promising ...no pun intended. but then if you have money buying a big drive is more bang than buying 2 smalls

muxman · 02-13-2006, 09:52 AM

I've tried 2.6 and 2.4 kernels and both show the same lspci and work the same. I am running a vanilla kernel, not an amd specific one or anything special. Just plain with standard modules, nothing special in them or patched to them.

I don't have any options in the bios to change the drive recognition either.

I've checked the HCL, and I've even posted for this card, prematurely. It worked great for several weeks and then I posted. Soon afterwards I started having issues. Unfortunatly there is no edit option in the HCL so I can't change my post and add anything to it.

As far as drives go I'm running this card for storage purposes. The computer is a fileserver with about 1TB storage and needs the controller for the large drives and the growing number of them. There is no single drive available that has the capacity of any two of these storage drives combined. I don't believe there are 600GB drives out yet, 500GB is available though. But for the price of 1 500GB drive I can get 2 300GB drives, save money and have 100GB more storage. The case is large and can hold many more drives so controllers and less expensive drives are the way to go for large amounts of storage. Costs will end up being much less this way rather than going for fewer, larger drives.

Thanks for the try but unfortunatly none of the things you mentioned that I've already tried have worked or are available (bios settings).

I think the way to go, hopefully, is with hdparm. The drive on the contoller is the only one whose settings are different from the other drives. It's unmaskirq and IO_support settings are not set where the other drives have those set. Once I get the time to backup the data I will try this and see if that will work.

WhatsHisName · 02-13-2006, 11:36 AM

aus9: The “unknown mass storage controller” lspci line is normal in Sarge. Here are the outputs for the Promise Ultra100 TX2 (the ATA100 sibling of the ATA133 card):

Sarge 2.6.8-2-686:

Code:

Sarge:~# lspci
0000:00:0d.0 Unknown mass storage controller: Promise Technology, Inc. PDC20268 (Ultra100 TX2) (rev 02)

Etch 2.6.12-1-686:

Code:

Etch:~# lspci
0000:00:0d.0 Mass storage controller: Promise Technology, Inc. PDC20268 (Ultra100 TX2) (rev 02)

Both cards work fine.

aus9 · 02-14-2006, 06:44 AM

for HCL you can email one of the moderators and they can fix

muxman · 02-14-2006, 08:15 AM

Quote:

Originally Posted by WhatsHisName

aus9: The “unknown mass storage controller” lspci line is normal in Sarge. Here are the outputs for the Promise Ultra100 TX2 (the ATA100 sibling of the ATA133 card):

Sarge 2.6.8-2-686:

Code:

Sarge:~# lspci
0000:00:0d.0 Unknown mass storage controller: Promise Technology, Inc. PDC20268 (Ultra100 TX2) (rev 02)

Etch 2.6.12-1-686:

Code:

Etch:~# lspci
0000:00:0d.0 Mass storage controller: Promise Technology, Inc. PDC20268 (Ultra100 TX2) (rev 02)

Both cards work fine.

Just out of curiosity do you have the output from hdparm for the settings on any of your drives? The ones on the controller vs. the motherboard.

The reason I'm wondering is because the one I have on the controller is an identical drive to two others I have on the motherboard but the default settings as displayed by hdparm are different. I'm hoping this is the issue and when I set the controllered drive to match the motherboard drives it will solve it.

As you can see in my first post unmaskirq and IO_support are set different on the controller vs. the all motherboard drives. The identical drives on the motherboard have those set so I know the drive is capable of it and I'd imagine the controller is aslo, being an ultra133 controller. It just doesn't do it by default for some reason. Probably just to be conservative with the settings in hopes of stability.

WhatsHisName · 02-14-2006, 09:58 AM

muxman: The only Sarge hard drive is on the Promise card. Here are some hdparm outputs for that drive:

Sarge 2.6.8-2-686:

Code:

Sarge:~# hdparm /dev/hde
/dev/hde:
 multcount    =  0 (off)
 IO_support   =  0 (default 16-bit)
 unmaskirq    =  0 (off)
 using_dma    =  1 (on)
 keepsettings =  0 (off)
 readonly     =  0 (off)
 readahead    = 256 (on)
 geometry     = 65535/16/63, sectors = 156301488, start = 0

Sarge:~# hdparm -tT /dev/hde
/dev/hde:
 Timing cached reads:   564 MB in  2.00 seconds = 281.62 MB/sec
 Timing buffered disk reads:  132 MB in  3.03 seconds =  43.60 MB/sec

Sarge:~# hdparm -I /dev/hde
/dev/hde:
ATA device, with non-removable media
        Model Number:       WDC WD800JB-00JJA0
        Serial Number:      (deleted before posting)
        Firmware Revision:  05.01C05
Standards:
        Supported: 6 5 4 3
        Likely used: 6
Configuration:
        Logical         max     current
        cylinders       16383   16383
        heads           16      16
        sectors/track   63      63
        --
        CHS current addressable sectors:   16514064
        LBA    user addressable sectors:  156301488
        device size with M = 1024*1024:       76319 MBytes
        device size with M = 1000*1000:       80026 MBytes (80 GB)
Capabilities:
        LBA, IORDY(can be disabled)
        bytes avail on r/w long: 66     Queue depth: 1
        Standby timer values: spec'd by Standard, with device specific minimum
        R/W multiple sector transfer: Max = 16  Current = 0
        Recommended acoustic management value: 128, current value: 254
        DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5
             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:
           *    READ BUFFER cmd
           *    WRITE BUFFER cmd
           *    Host Protected Area feature set
           *    Look-ahead
           *    Write cache
           *    Power Management feature set
                Security Mode feature set
           *    SMART feature set
           *    Mandatory FLUSH CACHE command
           *    Device Configuration Overlay feature set
                Automatic Acoustic Management feature set
                SET MAX security extension
           *    DOWNLOAD MICROCODE cmd
           *    SMART self-test
           *    SMART error logging
Security:
        Master password revision code = 65534
                supported
        not     enabled
        not     locked
        not     frozen
        not     expired: security count
        not     supported: enhanced erase
HW reset results:
        CBLID- above Vih
        Device num = 0 determined by CSEL
Checksum: correct

muxman · 02-14-2006, 07:48 PM

Those are the same settings mine has for hde. Do the settings for that drive match the others on you system? Or is it different?

WhatsHisName · 02-14-2006, 11:51 PM

Sorry, but there’s only one drive on that system, so nothing to compare it to.

muxman · 03-05-2006, 12:55 PM

I've tried reinstalling the system. I put in another drive and reinstalled and get the same results. I've tried turning off the usb ports thinking that the controller was sharing and irq and that may do it also. Doesn't. The controller is now on it's own irq, not shared with anything else and it still freezes.

I've even tried moving the contoller to another pci slot to see if that may effect it's irq or something. Didn't change anything.

I'm going to juggle the drives around a little and see what that does. They are all about the same thing, 300gb maxtors. Two are the exact same model and the 3rd is the same thing, 300gb but slightly different model. Maybe something there may work. Maybe one drive is bad or has something wrong with it?

muxman · 03-08-2006, 08:32 PM

So far nothing seems to be making the difference. I read another post about the ide cables and how they can make a differnce. I was using rounded cables, 24 inch. I since put the 18 inch standard ide cables in, the enhanced ones, not regular 40 wire. The 80 wire ones. I've seen no difference there either. The promise controller I'm using must have issues with my kernel or my drives. I don't know which but it's sure annoying what it's doing here.

Any other suggestions? Or alternatives to the controller I'm using? Any recommendations? This instability is getting to be a pain and I just want to get the system to run without this freezing issue.

Maybe there are settings I can use to turn down my drives? Their performance is set higher on the onboard drives than the controllered drive. Any suggestions there? I'm open to about anything here to get this thing to be stable.

quackyo · 03-21-2006, 02:32 PM

I have the excact same problem - only that I first used some cheapass Silicon Image UDMA133 controllers.

My setup was as follows : AMD Athlon system.
onboard IDE : system disk (80gb)

3 extra controllers, to be able to control 6 x 200gb disks in a RAID5.
I use 3 controllers to be able to run each disk as master and therefore get the highest possible performance.

Like you, it all worked fine at the beginning. But after a while It started hanging. The whole system hang, and I had to reboot system physically.

After a long time of fiddling with the setup, I started changing hardware. I had a celeron 2,4GHz setup laying around so I switched mainboard, cpu and RAM. Didn't help.
I've tried every possible setup of PCI slots (IRQ sharing???).
I've changed PSU - I have even tried to run a second PSU to power some of the harddrives , just to be sure that not both of them were too weak.
I've changed some IDE cables.
Today I even changed all 3 controllers - from Silicon Image controllers to new Promise ULTRA100 TX2.

but *I STILL HAVE THE SAME PROBLEM* - the computer locks up when I use the disks. It seems to hang under high load - I haven't been able to confirm if it's when I write or read from the array, as my best way to test if the system fails or not is to unpack a 4 gigabyte archive through gigabit network - I read the archive from the array and writes is directly back to the array....

Now I don't have any more things left to try.... Can it be the discs ? They report no defects, but even if one of them HAD a defect the computer shouldn' hard-lock - just fail the current transfer ???