Re: ide cd/dvd with 2.4.19-pre8

Andre Hedrick (andre@linux-ide.org)
Sat, 18 May 2002 02:43:59 -0700 (PDT)


The driver pulled your system back into safe data io ranges.
Either your cable routing is poor, your power supply is marginal, possible
but not likely (hardware combination does not like the odd or even cable
grounding setup), regardless it did the correct thing.

The problem is a feature to prevent the driver from dropping out of DMA
to PIO when it is better to down grade the transfer rate.

The next issue is whether your ATAPI is in DMA, and it should not be.
The driver core does not use split dma engines yet.

Cheers,

Andre Hedrick
LAD Storage Consulting Group

On 18 May 2002, Måns Rullgård wrote:

> Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
>
> > > I just noticed that reading from both my cdrom and dvd is a lot slower
> > > with 2.4.19-pre8 than 2.4.18. Now hdparm reports ~800 kbytes/s compared=
> > > to
> > > 1.7 MBytes/s for CD and >2 MBytes/s for DVD with 2.4.18. It is even imp=
> > > ossible
> > > to play DVDs. Any ideas?
> >
> > Did you include support for your controller. Are you in fact now in PIO
> > mode because you didnt ?
>
> I included support for PDC202xx and have a PDC20268 (Promise Ultra100
> TX2). Isn't that enough? hdparm claims the cd and dvd are using
> dma. The configuration is exactly the same with both kernels.
>
> However, I had to modify pdc202xx.c to make it use udma3 and higher
> for the disk. It failed to set hwif->udma_four so other parts of the
> ide driver refused to even try the fast modes. I pointed this out a couple
> of weeks ago but didn't get any response.
>
> There is also some trouble with udma4&5. Both the disk and the controller
> claim they support it and it looks like it is properly detected. However
> I get these messages when booting:
> PDC20268: IDE controller on PCI bus 00 dev 60
> PDC20268: chipset revision 2
> PDC20268: not 100% native mode: will probe irqs later
> PDC20268: ROM enabled at 0x09074000
> ide2: BM-DMA at 0x8090-0x8097, BIOS settings: hde:pio, hdf:pio
> ide3: BM-DMA at 0x8098-0x809f, BIOS settings: hdg:pio, hdh:pio
> hde: ST340810A, ATA DISK drive
> hdg: SAMSUNG COMBO SM-304B, ATAPI CD/DVD-ROM drive
> ide2 at 0x80a0-0x80a7,0x80b2 on irq 32
> ide3 at 0x80a8-0x80af,0x80b6 on irq 32
> hde: 78165360 sectors (40021 MB) w/2048KiB Cache, CHS=77545/16/63, UDMA(100)
> Partition check:
> /dev/ide/host2/bus0/target0/lun0:hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
> hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
> hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
> hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
> PDC202XX: Primary channel reset.
> ide2: reset: success
> hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
> hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
> hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
> hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
> PDC202XX: Primary channel reset.
> ide2: reset: success
>
> After this the disk is in udma3 mode and works fine, though it should be able
> to go faster. This problem has been present with all kernels from 2.4.10.
> I haven't tried earlier ones. I have an Alpha in case it matters.
>
> --
> Måns Rullgård
> mru@users.sf.net
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>

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