>Number:         22787
>Category:       kern
>Synopsis:       IDE led stays lighted forever
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Sep 14 16:39:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     
>Release:        NetBSD 1.6ZB
>Organization:
Julio M. Merino Vidal <jmmv@menta.net>
The NetBSD Project - http://www.NetBSD.org/
>Environment:
	
	
System: NetBSD dawn.local 1.6ZB NetBSD 1.6ZB (DAWN) #0: Sun Sep 14 17:32:28 CEST 2003 jmmv@dawn.local:/home/NetBSD/obj/home/NetBSD/src/sys/arch/i386/compile/DAWN i386
Architecture: i386
Machine: i386
>Description:
	I have an Asus A7V8X-X motherboard; it comes with a VIA KT400 north
	bridge and a VIA VT8235 south bridge.  Attached to the IDE controller
	are two ATA 100 disks in the first channel, a Toshiba 16x DVD-ROM
	drive as secondary master and a Plextor 12/10/32A CDRW as secondary
	slave.

	After the kernel probes for disks, the IDE led stays lighted forever.
	This is umm... annoying.

	gendalia@ pointed me a way to turn off the led and make it work.  It
	is simple, from userland: 'mount /dev/cd1d /mnt'; this works even if
	there is no disk in the drive.  But, as you could imagine, this is
	weird.
>How-To-Repeat:
	As described below, connect a "buggy?" ATAPI drive to the secondary
	slave channel and boot a kernel.
>Fix:
	Googling a bit, I found this URL:
		http://www.stanford.edu/~csapuntz/blackmagic.html
	The following text has been extracted from it, which contains
	indications on how to fix this issue:

----------
    ATAPI slave causes drive light to stay on

   The drive light is directly connected to the DASP-/PDIAG- signal on the
   IDE bus. The PDIAG- signal is used by the slave to indicate its presence
   on the bus to the master upon Hardware RESET, SRST, and Execute Device
   Diagnostic.

   Most ATAPI device will de-assert PDIAG- upon receiving an ATA command
   after reset. However, some devices seem to require a PACKET COMMAND before
   they deassert PDIAG-. Others seem to require a DEVICE RESET.
----------

	For someone who knows the code, I guess this should be easy to fix...

	Thanks.
>Release-Note:
>Audit-Trail:
>Unformatted: