Bug 29152

Summary:	identify retries exceeded
Product:	Base System	Reporter:	Derek <coffee>
Component:	kern	Assignee:	freebsd-bugs (Nobody) <bugs>
Status:	Closed FIXED
Severity:	Affects Only Me
Priority:	Normal
Version:	Unspecified
Hardware:	Any
OS:	Any

Description Derek 2001-07-23 00:10:01 UTC

there have been several posts of this issue on the mailing lists, with no reports submitted, and no fix ever announced... some CD-ROMS (particularly those in dell laptops, but this is not limited to dells, nor even laptop cd-roms) get the following errors in your dmesg, and are not recognized (full output of dmes available upon request from coffee@fatburrito.com):

atapci0: <Intel ICH2 ATA100 controller> port 0xbfa0-0xbfaf at device 31.1 on pci0
...... snip ......
ata0-slave: identify retries exceeded
ata0-master: DMA limited to UDMA33, non-ATA66 compliant cable
ad0: 9590MB <HITACHI_DK23BA-10> [19485/16/63] at ata0-master UDMA33

Fix: 

Unknown.
How-To-Repeat: Not sure... is not a problem on all laptops with the identical configuration, nor is it a consistemnt problem on 2 or more of any identical machine.

Comment 1 Eric Anholt 2001-12-12 07:04:22 UTC

I am also seeing this on -current on a Dell Inspiron 8000 laptop with 
DVD drive.  The OS was originally 4.4-RELEASE, installed from bootable 
cd in that drive.  A verbose boot is posted at:
http://gladstone.uoregon.edu/~eanholt/neutrino-bootverbose

Comment 2 iedowse freebsd_committer

2002-12-01 03:43:49 UTC

State Changed
From-To: open->feedback


Does this still occur in more recent releases?

Comment 3 iedowse 2002-12-01 12:08:13 UTC

Adding to the audit trail:

In message <4849.206.163.219.46.1038718135.squirrel@mail.fatburrito.com>, coffe
e@fatburrito.com writes:
>I don't know. I took freebsd off of that laptop some time ago, as I really
>needed something that I could use my CD-ROM with.
>
>Thanks,
>Derek

Comment 4 iedowse freebsd_committer

2002-12-01 12:13:13 UTC

State Changed
From-To: feedback->closed


Thanks for the quick reply! There have been a lot of ATA changes 
since FreeBSD 4.4, so there is little point in keeping this open 
without information about how this hardware behaves in a more recent 
-STABLE. If you do get a chance to test it and the problem is still 
there then the PR can of course be re-opened.