2.2.14 dma trouble with shuttle av61 (apollo pro 133)

From: Scott V. McGuire (svmcguir@syr.edu)
Date: Thu Jan 20 2000 - 03:18:21 EST

Next message: Tigran Aivazian: "[patch-2.3.40-pre6] kzalloc() (ala kmem_zalloc() of SVR4)"
Previous message: Tigran Aivazian: "Re: [patch-2.3.40-pre6] nfds limit for poll() raised to 131 million (is that enough?)"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

What is this telling me?

Jan 20 00:47:53 homebox kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 20 00:47:53 homebox kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 20 00:57:15 homebox kernel: hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 20 00:57:15 homebox kernel: hdd: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 20 00:57:15 homebox kernel: hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 20 00:57:15 homebox kernel: hdd: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 20 00:57:15 homebox kernel: hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 20 00:57:15 homebox kernel: hdd: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 20 00:57:15 homebox kernel: hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 20 00:57:15 homebox kernel: hdd: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 20 00:57:15 homebox kernel: hdd: DMA disabled
Jan 20 00:57:15 homebox kernel: ide1: reset: success
Jan 20 01:54:41 homebox kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 20 01:54:41 homebox kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 20 02:00:13 homebox kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 20 02:00:13 homebox kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 20 02:58:21 homebox kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 20 02:58:21 homebox kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC }

hda is IBM-DTTA-351680, a 16.8Gb UDMA33 drive
hdb is IBM-DJNA-352030, a 20.3Gb UDMA66 drive
hdc is UTI V4.6a, a cheap cdrom drive
hdd is WDC AC25100L, a 5.xGb UDMA33 drive (leaving soon)

UDMA is set to auto in bios and it correctly recognizes each drive.

At startup I do:
hdparm -A1 -a8 -c1 -d1 -m16 -u1 -W1 -X66 /dev/hda
hdparm -A1 -a8 -c1 -d1 -m16 -u1 -W1 -X66 /dev/hdb
hdparm -A1 -a8 -c1 -d1 -m16 -u1 -W1 -X66 /dev/hdd

It started when I got the motherboard (shuttle av61 apollo pro 133).
It lessens but still happens if I turn of UDMA in bios and remove -X66
from the above lines. Aside from the messages, everything seems to
work fine. Any other info I should send?

Thanks,

-- Scott V. McGuire <svmcguir@syr.edu> GnuPG key available at http://physics.syr.edu/~svmcguir GnuPG key fingerprint: 21EA 4999 3620 3E1D 71EC 98A9 5B9B EF52 1258 6D53 GnuPG is at http://www.gnupg.org/

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/

Next message: Tigran Aivazian: "[patch-2.3.40-pre6] kzalloc() (ala kmem_zalloc() of SVR4)"
Previous message: Tigran Aivazian: "Re: [patch-2.3.40-pre6] nfds limit for poll() raised to 131 million (is that enough?)"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Sun Jan 23 2000 - 21:00:22 EST