I recently went through a major overhaul of my 1U server where we replaced a failing HD (hdb) but ended up replacing the MB as well as it seems the IDE controller was goofy on the original MB.

So I've been watching the logs since coming up..I need a little help understanding what the entries from may 22 mean.

Also note at this time the server was going through a high load for whatever reason.

~~~~~~~
May 19 07:45:20 startbox kernel: ide0: BM-DMA at 0xff00-0xff07, BIOS settings: hdaMA, hdbMA
May 19 07:45:20 startbox kernel: hdb: Maxtor 6Y080L0, ATA DISK drive
May 19 07:45:21 startbox kernel: hdb: attached ide-disk driver.
May 19 07:45:21 startbox kernel: hdb: host protected area => 1
May 19 07:45:21 startbox kernel: hdb: 160086528 sectors (81964 MB) w/2048KiB Cache, CHS=9964/255/63, UDMA(133)
May 19 07:45:21 startbox kernel: hdb: hdb1 hdb2
May 20 14:02:41 startbox kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
May 20 14:02:41 startbox kernel: hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
May 21 23:44:57 startbox kernel: hdb: dma_timer_expiry: dma status == 0x61
May 22 05:44:59 startbox kernel: hdb: dma_timer_expiry: dma status == 0x61
May 22 06:25:30 startbox kernel: hdb: dma_timer_expiry: dma status == 0x61
May 22 06:43:39 startbox kernel: hdb: dma_timer_expiry: dma status == 0x61
May 22 11:24:52 startbox kernel: hdb: dma_timer_expiry: dma status == 0x61
May 22 11:25:09 startbox kernel: hdb: error waiting for DMA
May 22 11:25:09 startbox kernel: hdb: dma timeout retry: status=0xd0 { Busy }
May 22 11:25:09 startbox kernel: hdb: set_drive_speed_status: status=0x58 { DriveReady SeekComplete DataRequest }

May 22 11:25:09 startbox kernel: hda: DMA disabled

"I need a little help understanding what the entries from may 22 mean."

Each line represents an I/O error on hdb. An I/O command was issued and no reponse was received. Eventually (dma_timer_expiry) the kernel gave up on the command and tried again. This could be a problem with either your hard drive or your IDE controller chipset with the culprit more likely to be the chipset. Eventually the kernel cleared the problem by disabling DMA. While this appearantly solved the problem your disk runs much slower with DMA disabled.

You can also get this problem if you are using the wrong IDE driver or hard drive driver. Much hardware has design bugs in it. Each driver compensates for the hardware bugs in the equipment the driver is written for. If you have the wrong driver then you are correcting for the wrong hardware bugs.

"Also note at this time the server was going through a high load for whatever reason."

One common IDE chipset bug, especially in Promise chipsets, is that the chipset craps out when trying to run both IDE0 and IDE1 simultaneously. Thus failures are much more common under high load. The drivers for Promise have never done a perfect job of fixing this bug because Promise refuses to release the chipset specs.

___________________________________
Be prepared. Create a LifeBoat CD.
http://users.rcn.com/srstites/LifeBo...home.page.html

Steve Stites

Well..is this considered a slow disk read?
[root@startbox log]# hdparm -tT /dev/hdb

/dev/hdb:
Timing buffer-cache reads: 1264 MB in 2.11 seconds = 599.05 MB/sec
Timing buffered disk reads: 2 MB in 10.28 seconds = 199.22 kB/sec

[root@startbox sysconfig]# hdparm /dev/hdb

/dev/hdb:
multcount = 16 (on)
IO_support = 1 (32-bit)
unmaskirq = 1 (on)
using_dma = 1 (on)
keepsettings = 0 (off)
readonly = 0 (off)
readahead = 8 (on)
geometry = 9964/255/63, sectors = 160086528, start = 0

I'm seeing a really high server load being driven by a phpBB site which is hitting hdb hard. I'm not sure that hdb (where the MySQL tables are housed for virtual host) is keeping up?

Today the server load just climbed until I could even ssh into the server. if i turn this one site off (htaccess rewrite rules) then the server load drops to less than 1 with my other 20 production sites.


[root@startbox sysconfig]# dmesg
Linux version 2.4.22-1.2115.nptl (bhcompile@daffy.perf.redhat.com) (gcc version 3.2.3 20030422 (Red Hat Linux 3.2.3-6)) #1 Wed Oct 29 15:42:51 EST 2003
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000cc000 - 00000000000d0000 (reserved)
BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000003dff0000 (usable)
BIOS-e820: 000000003dff0000 - 000000003dff8000 (ACPI data)
BIOS-e820: 000000003dff8000 - 000000003e000000 (ACPI NVS)
BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
BIOS-e820: 00000000ffee0000 - 00000000fff00000 (reserved)
BIOS-e820: 00000000fffc0000 - 0000000100000000 (reserved)
95MB HIGHMEM available.
896MB LOWMEM available.
ACPI: have wakeup address 0xc0001000
On node 0 totalpages: 253936
zone(0): 4096 pages.
zone(1): 225280 pages.
zone(2): 24560 pages.
ACPI: RSDP (v000 AMI ) @ 0x000fa480
ACPI: RSDT (v001 AMIINT SiS740XX 0x00001000 MSFT 0x0100000b) @ 0x3dff0000
ACPI: FADT (v001 AMIINT SiS740XX 0x00000011 MSFT 0x0100000b) @ 0x3dff0030
ACPI: MADT (v001 AMIINT SiS740XX 0x00001000 MSFT 0x0100000b) @ 0x3dff00c0
ACPI: DSDT (v001 SiS 746 0x00000100 MSFT 0x0100000d) @ 0x00000000
Kernel command line: ro root=LABEL=/ rhgb
Initializing CPU#0
Detected 2405.475 MHz processor.
Console: colour VGA+ 80x25
Calibrating delay loop... 4797.23 BogoMIPS
Memory: 999984k/1015744k available (1503k kernel code, 15372k reserved, 1110k data, 136k init, 98240k highmem)
Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes)
Inode cache hash table entries: 65536 (order: 7, 524288 bytes)
Mount cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer cache hash table entries: 65536 (order: 6, 262144 bytes)
Page-cache hash table entries: 262144 (order: 8, 1048576 bytes)
CPU: Trace cache: 12K uops, L1 D cache: 8K
CPU: L2 cache: 512K
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU: After generic, caps: bfebfbff 00000000 00000000 00000000
CPU: Common caps: bfebfbff 00000000 00000000 00000000
CPU: Intel(R) Pentium(R) 4 CPU 2.40GHz stepping 09
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
mtrr: v1.40 (20010327) Richard Gooch (rgooch@atnf.csiro.au)
mtrr: detected mtrr type: Intel
ACPI: Subsystem revision 20031002
ACPI: Interpreter disabled.
PCI: PCI BIOS revision 2.10 entry at 0xfdb31, last bus=2
PCI: Using configuration type 1
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
PCI: Using IRQ router SIS96x [1039/0008] at 00:02.0
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
apm: BIOS not found.
Starting kswapd
allocated 32 pages and 32 bhs reserved for the highmem bounces
VFS: Disk quotas vdquot_6.5.1
pty: 2048 Unix98 ptys configured
Serial driver version 5.05c (2001-07-08) with MANY_PORTS MULTIPORT SHARE_IRQ SERIAL_PCI ISAPNP enabled
ttyS0 at 0x03f8 (irq = 4) is a 16550A
ttyS1 at 0x02f8 (irq = 3) is a 16550A
Real Time Clock Driver v1.10e
NET4: Frame Diverter 0.46
RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
SIS5513: IDE controller at PCI slot 00:02.5
SIS5513: chipset revision 0
SIS5513: not 100% native mode: will probe irqs later
SIS5513: SiS 962/963 MuTIOL IDE UDMA133 controller
ide0: BM-DMA at 0xff00-0xff07, BIOS settings: hdaMA, hdbMA
ide1: BM-DMA at 0xff08-0xff0f, BIOS settings: hdcMA, hddMA
hda: ST380011A, ATA DISK drive
hdb: Maxtor 6Y080L0, ATA DISK drive
blk: queue c040cfc0, I/O limit 4095Mb (mask 0xffffffff)
blk: queue c040d100, I/O limit 4095Mb (mask 0xffffffff)
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hda: attached ide-disk driver.
hda: host protected area => 1
hda: 156301488 sectors (80026 MB) w/2048KiB Cache, CHS=9729/255/63, UDMA(100)
hdb: attached ide-disk driver.
hdb: host protected area => 1
hdb: 160086528 sectors (81964 MB) w/2048KiB Cache, CHS=9964/255/63, UDMA(133)
Partition check:
hda: hda1 hda2 hda3 hda4 < hda5 hda6 >
hdb: hdb1 hdb2
ide: late registration of driver.
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
Initializing Cryptographic API
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 8192 buckets, 64Kbytes
TCP: Hash tables configured (established 262144 bind 65536)
Linux IP multicast router 0.06 plus PIM-SM
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
RAMDISK: Compressed image found at block 0
Freeing initrd memory: 160k freed
VFS: Mounted root (ext2 filesystem).
Journalled Block Device driver loaded
EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write access will be enabled during recovery.
kjournald starting. Commit interval 5 seconds
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
Freeing unused kernel memory: 136k freed
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
PCI: Found IRQ 5 for device 00:03.1
usb-ohci.c: USB OHCI at membase 0xf884c000, IRQ 5
usb-ohci.c: usb-00:03.1, Silicon Integrated Systems [SiS] USB 1.0 Controller (#2)
usb.c: new USB bus registered, assigned bus number 1
hub.c: USB hub found
hub.c: 3 ports detected
PCI: Found IRQ 5 for device 00:03.0
usb-ohci.c: USB OHCI at membase 0xf884e000, IRQ 5
usb-ohci.c: usb-00:03.0, Silicon Integrated Systems [SiS] USB 1.0 Controller
usb.c: new USB bus registered, assigned bus number 2
hub.c: USB hub found
hub.c: 3 ports detected
PCI: Found IRQ 10 for device 00:03.2
ehci_hcd 00:03.2: Silicon Integrated Systems [SiS] USB 2.0 Controller
ehci_hcd 00:03.2: irq 10, pci mem f8856000
usb.c: new USB bus registered, assigned bus number 3
PCI: cache line size of 128 is not supported by device 00:03.2
ehci_hcd 00:03.2: USB 2.0 enabled, EHCI 1.00, driver 2003-Jun-19/2.4
hub.c: USB hub found
hub.c: 6 ports detected
usb.c: registered new driver hiddev
usb.c: registered new driver hid
hid-core.c: v1.8.1 Andreas Gal, Vojtech Pavlik <vojtech@suse.cz>
hid-core.c: USB HID support drivers
mice: PS/2 mouse device common for all mice
hub.c: new USB device 00:03.2-1, assigned address 2
usb.c: USB device 2 (vend/prod 0x6e1/0xd804) is not claimed by any active driver.
EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,6), internal journal
Adding Swap: 2024148k swap-space (priority -1)
Adding Swap: 2024148k swap-space (priority -2)
SCSI subsystem driver Revision: 1.00
Initializing USB Mass Storage driver...
usb.c: registered new driver usb-storage
scsi0 : SCSI emulation for USB Mass Storage devices
Vendor: ST380011 Model: A Rev: 0 0
Type: Direct-Access ANSI SCSI revision: 02
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 2
USB Mass Storage support registered.
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
SCSI device sda: 156301488 512-byte hdwr sectors (80026 MB)
sda: sda1 sda2
inserting floppy driver for 2.4.22-1.2115.nptl
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
kjournald starting. Commit interval 5 seconds
EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,1), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,66), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,3), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,2), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
IA-32 Microcode Update Driver: v1.11 <tigran@veritas.com>
microcode: CPU0 no microcode found! (sig=f29, pflags=4)
parport0: PC-style at 0x378 (0x778) [PCSPP,TRISTATE,EPP]
parport0: irq 7 detected
sis900.c: v1.08.06 9/24/2002
PCI: Found IRQ 5 for device 00:04.0
divert: allocating divert_blk for eth0
eth0: Realtek RTL8201 PHY transceiver found at address 1.
eth0: Using transceiver found at address 1 as default
eth0: SiS 900 PCI Fast Ethernet at 0xdc00, IRQ 5, 00:0b:6a:2c:ac:c3.
divert: freeing divert_blk for eth0
ip_tables: (C) 2000-2002 Netfilter core team
sis900.c: v1.08.06 9/24/2002
PCI: Found IRQ 5 for device 00:04.0
divert: allocating divert_blk for eth0
eth0: Realtek RTL8201 PHY transceiver found at address 1.
eth0: Using transceiver found at address 1 as default
eth0: SiS 900 PCI Fast Ethernet at 0xdc00, IRQ 5, 00:0b:6a:2c:ac:c3.
ip_tables: (C) 2000-2002 Netfilter core team
eth0: Media Link On 10mbps half-duplex
parport0: PC-style at 0x378 (0x778) [PCSPP,TRISTATE,EPP]
parport0: irq 7 detected
lp0: using parport0 (polling).
lp0: console ready
hdb: dma_timer_expiry: dma status == 0x61
hdb: dma_timer_expiry: dma status == 0x61
hdb: error waiting for DMA
hdb: dma timeout retry: status=0xd0 { Busy }

hda: DMA disabled
hdb: DMA disabled
ide0: reset: success
hdb: dma_timer_expiry: dma status == 0x41
hdb: dma_timer_expiry: dma status == 0x41
hdb: dma_timer_expiry: dma status == 0x41
hdb: dma_timer_expiry: dma status == 0x41
hdb: dma_timer_expiry: dma status == 0x41
hdb: dma_timer_expiry: dma status == 0x41
hdb: set_drive_speed_status: status=0x58 { DriveReady SeekComplete DataRequest }
hdb: DMA disabled
hdb: dma_timer_expiry: dma status == 0x00
hdb: timeout waiting for DMA
hdb: timeout waiting for DMA
hdb: (__ide_dma_test_irq) called while not waiting
hdb: DMA disabled
hdb: dma_timer_expiry: dma status == 0x01
hdb: error waiting for DMA
hdb: dma timeout retry: status=0x50 { DriveReady SeekComplete }

hdb: dma_timer_expiry: dma status == 0x41

SHould have put down this infor for my hda (OS) drive. Its much fatser on disk reads..but I haven't been able to turn using_dma off via hdparm

[root@startbox sysconfig]# hdparm -tT /dev/hda

/dev/hda:
Timing buffer-cache reads: 1264 MB in 2.01 seconds = 628.86 MB/sec
Timing buffered disk reads: 4 MB in 3.22 seconds = 1.24 MB/sec

[root@startbox sysconfig]# hdparm /dev/hda

/dev/hda:
multcount = 16 (on)
IO_support = 0 (default 16-bit)
unmaskirq = 0 (off)
using_dma = 0 (off)
keepsettings = 0 (off)
readonly = 0 (off)
readahead = 8 (on)
geometry = 9729/255/63, sectors = 156301488, start = 0

"Well..is this considered a slow disk read?
[root@startbox log]# hdparm -tT /dev/hdb

/dev/hdb:
Timing buffer-cache reads: 1264 MB in 2.11 seconds = 599.05 MB/sec
Timing buffered disk reads: 2 MB in 10.28 seconds = 199.22 kB/sec"


I don't know. I suggest that you run a benchmark on a comparable server that is running well and compare the results.

"I'm seeing a really high server load being driven by a phpBB site which is hitting hdb hard. I'm not sure that hdb (where the MySQL tables are housed for virtual host) is keeping up?"

Is the phpBB site legit or is this a denial of service attack?


"SIS5513: SiS 962/963 MuTIOL IDE UDMA133 controller"

I use a SIS controller chip, although a different model, and as far as I know there is nothing wrong with Linux SIS IDE support.

I just noticed that you are having problems with /dev/hdb but DMA support is being turned off for /dev/hda. WTF?

"/dev/hda:
using_dma = 0 (off)"

"dev/hdb:
using_dma = 1 (on)"

"May 21 23:44:57 startbox kernel: hdb: dma_timer_expiry: dma status == 0x61"

"May 22 11:25:09 startbox kernel: hda: DMA disabled"

You could try using hdparm to turn DMA off for hdb and on for hda and see what happens. You could try turning DMA off for both and try turning DMA on for both.


-------------------------
Steve Stites

probably best if you review a different topic of mine about disk drive issues .. and where I stand today. Sorry to forum mods if it appears I'm multiple postign about the same, just frantic for someone to help but many learning curves to traverse.

http://www.linuxquestions.org/questi...&postid=949484

"probably best if you review a different topic of mine about disk drive issues .. and where I stand today. "

The other thread showing 99% iowait time establishes that your problem is disk I/O. You can find out how much swapping you are doing by using the free command. Just type in:
free

"Swap: 4048296k av, 0k used, 4048296k free 413740k cached"
This line says that you are not swapping.

Another possibility is that you may have swap turned off. Use:
swapon -s
which will both give you swap statistics and tell you if swap is turned off.

I am still at a loss as to why DMA is being turned off on /dev/hda instead of /dev/hdb.

I checked the kernel source code and the SIS5513 driver is the correct driver for the SIS 962/963.

From post #3 in the other thread I understand that since the problem began you have replaced hdb and the motherboard (thus replacing the IDE chipset) and the new configuration ran fine Wednesday through Friday.

Given the confusion about hda/hdb DMA being turned off I offer this admittedly weak possibility as a solution. If hda is still the original hard drive then try replacing hda and see what happens.

___________________________________
Be prepared. Create a LifeBoat CD.
http://users.rcn.com/srstites/LifeBo...home.page.html

Steve Stites

In my last post in the other thread I stated that as of my last bootup, both hda/hdb have the same hdparm settings going forward today.

[root@startbox /]# swapon -s
Filename Type Size Used Priority
/dev/hdb1 partition 2024148 0 -1
/dev/hda5 partition 2024148 0 -2

I have seen swap in use, however today maybe it hasn't been needed..just wait till tonight when people come back to their computers and tomorrow during work day when they avoid working.

Another idea:

The fact that I/O errors on hdb is handled by turning DMA off on hda still has me puzzled. There may be a bug in the way that SIS5513 handles I/O errors. So I suggest that you look in the kernel changelog for changes to SIS5513 that might fix your problem. This is not as arduous as it might first appear. Get your kernel version number with:
uname -r
Then go to www.kernel.org and start looking through the kernel changlogs for every kernel version after your kernel version. Simply scan the changelog for SIS5513 and read every entry that you find for SIS5513. If you find a fix for your problem in a kernel changelog then that kernel version and any higher version will fix the problem.

What do you think of the idea of replacing hda?

--------------------------
Steve Stites

I don't know what's giving the impression dma was turned off on hda to fix anything. I'll post the /var/log/messages entries since bringing my server up today.

hda seems ok, but what about the last hdb dma entry?

As this is a live production server I'm not up to doing anything unless its a clear and concise discussion.

May 23 13:06:49 startbox kernel: ide0: BM-DMA at 0xff00-0xff07, BIOS settings: hdaMA, hdbMA
May 23 13:06:49 startbox kernel: hdb: Maxtor 6Y080L0, ATA DISK drive
May 23 13:06:49 startbox kernel: hdb: attached ide-disk driver.
May 23 13:06:49 startbox kernel: hdb: host protected area => 1
May 23 13:06:49 startbox kernel: hdb: 160086528 sectors (81964 MB) w/2048KiB Cache, CHS=9964/255/63, UDMA(133)
May 23 13:06:49 startbox kernel: hdb: hdb1 hdb2
May 23 13:44:55 startbox kernel: hdb: dma_timer_expiry: dma status == 0x61

May 23 13:06:48 startbox smartd[3631]: Device: /dev/hda, opened
May 23 13:06:48 startbox smartd[3631]: Device: /dev/hda, not found in smartd database.
May 23 13:06:48 startbox smartd[3631]: Device: /dev/hda, is SMART capable. Adding to "monitor" list.
May 23 13:06:49 startbox kernel: ide0: BM-DMA at 0xff00-0xff07, BIOS settings: hdaMA, hdbMA
May 23 13:06:49 startbox kernel: hda: ST380011A, ATA DISK drive
May 23 13:06:49 startbox kernel: hda: attached ide-disk driver.
May 23 13:06:49 startbox kernel: hda: host protected area => 1
May 23 13:06:49 startbox kernel: hda: 156301488 sectors (80026 MB) w/2048KiB Cache, CHS=9729/255/63, UDMA(100)
May 23 13:06:49 startbox kernel: hda: hda1 hda2 hda3 hda4 < hda5 hda6 >


also, this is current from dmesg, isn't this the correct drivers?

SIS5513: IDE controller at PCI slot 00:02.5
SIS5513: chipset revision 0
SIS5513: not 100% native mode: will probe irqs later
SIS5513: SiS 962/963 MuTIOL IDE UDMA133 controller
ide0: BM-DMA at 0xff00-0xff07, BIOS settings: hdaMA, hdbMA
ide1: BM-DMA at 0xff08-0xff0f, BIOS settings: hdcMA, hddMA

"I don't know what's giving the impression dma was turned off on hda to fix
anything."

post #1
May 22 11:25:09 startbox kernel: hda: DMA disabled

post #3
hda: DMA disabled
hdb: DMA disabled
ide0: reset: success

post #4
/dev/hda:
multcount = 16 (on)
IO_support = 0 (default 16-bit)
unmaskirq = 0 (off)
using_dma = 0 (off)

"also, this is current from dmesg, isn't this the correct drivers?"

Yes, I checked the kernel source code and the SIS5513 driver is the correct
driver for the SIS 962/963 chipset.

___________________________________
Be prepared. Create a LifeBoat CD.
http://users.rcn.com/srstites/LifeBo...home.page.html

Steve Stites

Those posts are from the time when things were a skew and I tried to turn off dma through ssh but it would only do so on hda, but hdb kept being re-enabled. I wouldn't say that fixed anything.

i was using redhat 9 with stock kernel, everything was working fine..
recently installed a fresh fedora core 2 with stock kernel...
all the hard disk partitioning was done by a dos version of partition magic 8.0

but in fedora core 2, errors starting 2 appear...

the error messages i got:

dma_timer_expiry: dma status == 0x61
dma timeout error : status=0xd0

my harddisk emits weird sounds like clicking sounds, sounds like the harddisk head is reading beyond
it's C/H/S

i reinstall fedora core 2 and partitioning using disk druid....now everything works just fine... - -"

i think the problem was hard disk C/H/S mapping in kernel 2.6 is different from 2.4 as my previous installation work just fine...better partition the hard disk using linux disk druid or fdisk...

hi, could any1 help me out with this kernel error i am having? it has popped up recently on my master (/dev/hda) drive and it looks serious to me. thanks. :

Jun 6 23:30:16 linux kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jun 6 23:30:16 linux kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jun 6 23:30:16 linux kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jun 6 23:30:16 linux kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jun 6 23:30:16 linux kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jun 6 23:30:16 linux kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jun 6 23:30:16 linux kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jun 6 23:30:16 linux kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jun 6 23:30:16 linux kernel: blk: queue c03e66c0, I/O limit 4095Mb (mask 0xffffffff)
Jun 6 23:30:16 linux kernel: hdb: DMA disabled
Jun 6 23:30:16 linux kernel: ide0: reset: success
Jun 6 23:30:16 linux kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jun 6 23:30:16 linux kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jun 6 23:30:16 linux kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jun 6 23:30:16 linux kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jun 6 23:30:16 linux kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jun 6 23:30:16 linux kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jun 6 23:30:16 linux kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jun 6 23:30:16 linux kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jun 6 23:30:16 linux kernel: ide0: reset: success
Jun 6 23:30:16 linux kernel: PCI: Found IRQ 11 for device 00:10.0
Jun 6 23:30:16 linux kernel: PCI: Sharing IRQ 11 with 00:07.2
Jun 6 23:30:16 linux kernel: PCI: Sharing IRQ 11 with 00:07.3

it continues obviously but i wasnt sure where to cut if off. it looks more serious to me as disabling DMA didnt solve the problem did it? help!!

i AM temporarily using my old motherboard - could this be the problem? or is it more likely a disk fault?

also, if i copy EVERYTHING from one disk to another (ie cp -R *.* /second_disk/) will the other disk behave the same or will boot cylinders etc be incorrect? thanks

im adding this later coz i just moticed it disabled DMA on hdb not hda to aid the problem - what does this mean?

I too have some similar entries in /var/log/messages:

________________________________________________________________________
Oct 14 12:38:11 server kernel: hde: dma_timer_expiry: dma status == 0x61
Oct 14 12:38:21 server kernel: hde: error waiting for DMA
Oct 14 12:38:21 server kernel: hde: dma timeout retry: status=0x51 { DriveReady SeekComplete Error }
Oct 14 12:38:21 server kernel: hde: dma timeout retry: error=0x01 { AddrMarkNotFound }, LBAsect=328701639, high=19, low=993453
5, sector=324621072
Oct 14 12:38:21 server kernel: blk: queue c03c61e8, I/O limit 4095Mb (mask 0xffffffff)
________________________________________________________________________

These entries were chucked into the logs when the server was under a relatively
high workload and I was not able to ssh back into the machine as a result...

The server has the Promise Ultra 133 PCI Chipset...what can i do to get around this????