Re: Has anyone seen the ATA driver timeout issue again?

[Matthew Dillon <dillon@xxxxxxxxxxxxxxxxxxxx>]

    Jonathon, I looked at our mail archives but I couldn't find the dmesg
    output from a DFly attempted boot to compare the FreeBSD dmesg output
    with.  I realize that this might not have been possible due to the
    system not booting to a state where you could copy the output, but
    if possible I would like you to try to boot DFly and write down
    any lines starting with 'ata' or 'ad' or 'ad0'.

    Your FreeBSD dmesg output had this:

    atapci0: <Intel PIIX4 ATA33 controller> port 0xfe60-0xfe6f at device 7.1 on pci0
    ata0: at 0x1f0 irq 14 on atapci0
    ata1: at 0x170 irq 15 on atapci0
    ...
    ata1-slave: ATAPI identify retries exceeded
    ...
    ad0: 6194MB <IBM-DADA-26480> [13424/15/63] at ata0-master UDMA33
    acd0: CDROM <CD-220EA> at ata1-master PIO4

    If we can get similar information for the DFly boot we might see something
    interesting.  The identify retries exceeded that FBsd gets is already
    interesting.  I'm hoping it is as simple as the DMA/PIO mode being
    different (but I may be hoping for too much).

					-Matt
					Matthew Dillon 
					<dillon@xxxxxxxxxxxxx>