Re: ATAng problem: drive gets no longer detected

It seems Stefan Ehmann wrote:
> After tonight's cvsup and kernel build my primary slave hard disk gets
> no longer detected.
> 
> This is due to the latest update to src/sys/dev/ata/ata-lowlevel.c. When
> i revert from version 1.10 to 1.9 everything is fine again.
> 
> So much about the "Hopefully this doesn't loose any real ATA disks..."

yeah yeah, you win some you loose some....

> Relevant part of dmesg with ata-lowlevel.c 1.10:
> 
> GEOM: create disk ad0 dp=0xc413d470
> ad0: 58644MB <IC35L060AVER07-0> [119150/16/63] at ata0-master UDMA66
> acd0: CDRW <CR-4804TE> at ata1-master PIO3
> acd1: DVDROM <LITEON DVD-ROM LTD122> at ata1-slave PIO4
> 
> Relevant part of dmesg with ata-lovel.c 1.9
> 
> GEOM: create disk ad0 dp=0xc413d470
> ad0: 58644MB <IC35L060AVER07-0> [119150/16/63] at ata0-master UDMA66
> GEOM: create disk ad1 dp=0xc413d270
> ad1: 38166MB <ST340823A> [77545/16/63] at ata0-slave UDMA66
> acd0: CDRW <CR-4804TE> at ata1-master PIO3
> acd1: DVDROM <LITEON DVD-ROM LTD122> at ata1-slave PIO4

Could I have the dmesg from a verbose boot from both please ? the above
doesn't tell anything about why it fails...

You could also change the #if 0 to #if 1 in ata-lowlevel.c::ata_reset()
as that should bring your drive back (and alot of phantom drives on
other systems)...

-Søren