Bug 58107

Summary: -CURRENT fails to detect ATA devices
Product: Base System Reporter: Christian Ullrich <chris>
Component: kernAssignee: Søren Schmidt <sos>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: 5.1-CURRENT   
Hardware: Any   
OS: Any   

Description Christian Ullrich 2003-10-16 07:40:11 UTC
	-CURRENT repeatably fails to detect the ad1 device.
	atacontrol simply tells me "no device present".
	There are no error messages in dmesg, the system acts
	as if the disk was either missing or dead, which is isn't.

	Downdating sys/dev/ata/ata-lowlevel.c to rev 1.11 (I found
	someone doing that on freebsd-current) fixes the problem.
	I haven't yet tested if this is the last revision to work.

	I consider this a showstopper bug for 5.2-RELEASE.
Comment 1 Kris Kennaway freebsd_committer freebsd_triage 2003-10-17 07:22:02 UTC
Responsible Changed
From-To: freebsd-bugs->sos

Assign to ata maintainer
Comment 2 Søren Schmidt freebsd_committer freebsd_triage 2003-10-25 20:28:39 UTC
State Changed
From-To: open->feedback

Is this stil a problem on am updated current ie oct25 or newer ?
Comment 3 Christian Ullrich 2003-10-26 19:25:49 UTC
Yes, the problem still exists with a freshly built kernel
from a source tree last updated between 14:33 and 14:37 UTC
today. I can only build the kernel as buildworld is broken in
lib/libypclnt, but the disk isn't seen at all during the
boot process.

I don't think this is relevant, but -- I'm running -CURRENT
with all debugging disabled. If you'd like me to produce 
any kind of debugging output, I'll happily rebuild my kernel.
Just ask.

-- 
Christian Ullrich
Comment 4 Søren Schmidt freebsd_committer freebsd_triage 2004-01-12 19:20:29 UTC
State Changed
From-To: feedback->closed

THis issue has be solved int -current