JFWIW, this sounds like something that I "fixed" in the old wd driver,
where a device 'echoed' on the bus after it was deselected. Increasing
the timeout between deselecting the device and trying to talk again to
the bus was, AFAIR, the workaround then.
> It seems Alex wrote:
> >
> > OK - here's the part relevant to ata:
> >
> >
> > ata-pci0: <Intel PIIX4 ATA-33 controller> port 0xfcf0-0xfcff at device
> > 1.1 on pci0
> > ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xfcf0
> > ata0: mask=03 status0=50 status1=00
> > ata0: mask=03 status0=50 status1=00
> > ata0: devices = 0x1
> > ata0 at 0x01f0 irq 14 on ata-pci0
> > ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0xfcf8
> > ata1: mask=03 status0=00 status1=00
> > ata1: mask=03 status0=00 status1=00
> > ata1: devices = 0xc
>
> Here it sees two devices, apparently you cdrom is reacting both on
> master AND slave addresses :(
>
> > ata1-slave: ata_command: timeout waiting for intr
> > ata1-slave: identify failed
>
> But when we try to talk to it it fails...
>
> > ata0-master: success setting up UDMA2 mode on PIIX4 chip
>
> But when we try to talk to it it fails...
>
> > Any ideas?
>
> I'll try to come up with a patch that solves this...
>
> -Søren
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
>
--
\\ Give a man a fish, and you feed him for a day. \\ Mike Smith
\\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED]
\\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
