Skip to contentSkip to conversation

ServerWorks CSB5 in recent -ac

DISCUSSION Tomas Szepe 1 participant 2 messages Sep 20, 2002

lore
Share & tools
lore
#0 lore raw

Hi Alan/Andre,

it seems (U)DMA on CSB5 has only been possible to switch on w/ (a) recent -ac kernel(s). Of 2.4.17, 2.4.19-pre2, 2.4.19, 2.4.20-pre7, and 2.4.20- -pre7-ac3, only the last one is capable of running the disks/cdroms in our HP tc3100 netserver in DMA.

While it won't let us use anything above UDMA2 unless we pass ideX=ata66, the driver still seems to work just fine when forced into, say, UDMA5.

A bit rough around the edges but perfectly usable, thanks!

Relevant boot messages follow:

Kernel command line: root=/dev/md0 ide1=ata66 rw vga=4
ide_setup: ide1=ata66
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx SvrWks CSB5: IDE controller at PCI slot 00:0f.1
SvrWks CSB5: chipset revision 147
SvrWks CSB5: not 100% native mode: will probe irqs later
SvrWks CSB5: simplex device: DMA forced

    ide0: BM-DMA at 0x1840-0x1847, BIOS settings: hda:pio, hdb:pio
SvrWks CSB5: simplex device: DMA forced
    ide1: BM-DMA at 0x1848-0x184f, BIOS settings: hdc:DMA, hdd:DMA

hdc: WDC WD800AB-00CBA0, ATA DISK drive
hdd: LTN486S, ATAPI CD/DVD-ROM drive
blk: queue c033256c, I/O limit 4095Mb (mask 0xffffffff)
ide1 at 0x170-0x177,0x376 on irq 15
hdc: host protected area => 1
hdc: 156301488 sectors (80026 MB) w/2048KiB Cache, CHS=155061/16/63, UDMA(100)
hdd: ATAPI 48X CD-ROM drive, 120kB Cache, UDMA(33)

The CDROM gets autotuned to:
/dev/hdd:

 IO_support   =  0 (default 16-bit)
 unmaskirq    =  0 (off)
 using_dma    =  0 (off)
 keepsettings =  0 (off)
 readonly     =  1 (on)
 readahead    =  8 (on)

... and makes the driver spit the following upon initial read attempts:

hdd: DMA interrupt recovery
hdd: lost interrupt
hdd: status timeout: status=0xd0 { Busy }
hdd: status timeout: error=0x00
hdd: DMA disabled
hdd: drive not ready for command
hdd: ATAPI reset complete

... after which everything works ook. Contrary to what the driver reports, DMA doesn't get disabled.

So how's integration into vanilla going? :)

T.

#1 lore raw
Quoted 10 lines

... and makes the driver spit the following upon initial read attempts:

hdd: DMA interrupt recovery
hdd: lost interrupt
hdd: status timeout: status=0xd0 { Busy }
hdd: status timeout: error=0x00
hdd: DMA disabled
hdd: drive not ready for command
hdd: ATAPI reset complete

Quoted 2 lines

... after which everything works ook. Contrary to what the driver reports, DMA doesn't get disabled.

Okay, I lied, it does get disabled. So at least you've got something left to fix. :)

T.