NetBSD Problem Report #22869

Received: (qmail 12108 invoked by uid 605); 20 Sep 2003 09:51:13 -0000
Message-Id: <20030920095109.174F524B@sun.local>
Date: Sat, 20 Sep 2003 11:51:09 +0200 (CEST)
From: jmmv@menta.net
Sender: gnats-bugs-owner@NetBSD.org
Reply-To: jmmv@menta.net
To: gnats-bugs@gnats.netbsd.org
Subject: Slave IDE drive not detected
X-Send-Pr-Version: 3.95

>Number:         22869
>Category:       kern
>Synopsis:       Slave IDE drive not detected
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    kern-bug-people
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Sep 20 09:52:00 +0000 2003
>Closed-Date:    Wed Mar 24 21:46:15 +0000 2004
>Last-Modified:  Wed Mar 24 21:46:15 +0000 2004
>Originator:     Julio M. Merino Vidal
>Release:        NetBSD 1.6ZC
>Organization:
Julio M. Merino Vidal <jmmv@menta.net>
The NetBSD Project - http://www.NetBSD.org/
>Environment:


System: NetBSD dawn.local 1.6ZC NetBSD 1.6ZC (DAWN) #2: Wed Sep 17 12:06:13 CEST 2003 jmmv@dawn.local:/home/NetBSD/obj/home/NetBSD/src/sys/arch/i386/compile/DAWN i386
Architecture: i386
Machine: i386
>Description:
	After the last changes to the IDE code (those to speed up detection
	of drives when there is no slave present), drives set up as slave
	are not recognized any more.

	This is with a recent kernel:

ghost detected
wd0 at pciide0 channel 0 drive 0: <WDC WD800JB-00ETA0>
wd0: drive supports 16-sector PIO transfers, LBA48 addressing
wd0: 76319 MB, 155061 cyl, 16 head, 63 sec, 512 bytes/sect x 156301488 sectors
wd0: 32-bit data port
wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 5 (Ultra/100)
wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5 (Ultra/100) (using DMA data transfers)
ghost detected
atapibus0 at pciide0 channel 1: 2 targets
cd0 at atapibus0 drive 0: <TOSHIBA DVD-ROM SD-M1612, , 1004> cdrom removable
cd0: 32-bit data port
cd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 2 (Ultra/33)
cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2 (Ultra/33) (using DMA data transfers)

	And this with the old one:

wd0 at pciide0 channel 0 drive 0: <WDC WD800JB-00ETA0>
wd0: drive supports 16-sector PIO transfers, LBA48 addressing
wd0: 76319 MB, 155061 cyl, 16 head, 63 sec, 512 bytes/sect x 156301488 sectors
wd0: 32-bit data port
wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 5 (Ultra/100)
wd1 at pciide0 channel 0 drive 1: <FUJITSU MPG3204AT E>
wd1: drive supports 16-sector PIO transfers, LBA addressing
wd1: 19546 MB, 39714 cyl, 16 head, 63 sec, 512 bytes/sect x 40031712 sectors
wd1: 32-bit data port
wd1: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 5 (Ultra/100)
pciide0: primary channel interrupting at irq 14
wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5 (Ultra/100) (using DMA data transfers)
wd1(pciide0:0:1): using PIO mode 4, Ultra-DMA mode 5 (Ultra/100) (using DMA data transfers)
pciide0: secondary channel configured to compatibility mode
atapibus0 at pciide0 channel 1: 2 targets
cd0 at atapibus0 drive 0: <TOSHIBA DVD-ROM SD-M1612, , 1004> cdrom removable
cd0: 32-bit data port
cd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 2 (Ultra/33)
cd1 at atapibus0 drive 1: <PLEXTOR CD-R   PX-W1210A, , 1.10> cdrom removable
cd1: 32-bit data port
cd1: drive supports PIO mode 4, DMA mode 2
pciide0: secondary channel interrupting at irq 15
cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2 (Ultra/33) (using DMA data transfers)
cd1(pciide0:1:1): using PIO mode 4, DMA mode 2 (using DMA data transfers)

>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:

From: Manuel Bouyer <bouyer@antioche.eu.org>
To: jmmv@menta.net
Cc: gnats-bugs@gnats.netbsd.org, netbsd-bugs@netbsd.org
Subject: Re: kern/22869: Slave IDE drive not detected
Date: Sat, 20 Sep 2003 20:18:10 +0200

 On Sat, Sep 20, 2003 at 11:51:09AM +0200, jmmv@menta.net wrote:
 > 
 > >Number:         22869
 > >Category:       kern
 > >Synopsis:       Slave IDE drive not detected
 > >Confidential:   no
 > >Severity:       serious
 > >Priority:       high
 > >Responsible:    kern-bug-people
 > >State:          open
 > >Class:          sw-bug
 > >Submitter-Id:   net
 > >Arrival-Date:   Sat Sep 20 09:52:00 UTC 2003
 > >Closed-Date:
 > >Last-Modified:
 > >Originator:     Julio M. Merino Vidal
 > >Release:        NetBSD 1.6ZC
 > >Organization:
 > Julio M. Merino Vidal <jmmv@menta.net>
 > The NetBSD Project - http://www.NetBSD.org/
 > >Environment:
 > 	
 > 	
 > System: NetBSD dawn.local 1.6ZC NetBSD 1.6ZC (DAWN) #2: Wed Sep 17 12:06:13 CEST 2003 jmmv@dawn.local:/home/NetBSD/obj/home/NetBSD/src/sys/arch/i386/compile/DAWN i386
 > Architecture: i386
 > Machine: i386
 > >Description:
 > 	After the last changes to the IDE code (those to speed up detection
 > 	of drives when there is no slave present), drives set up as slave
 > 	are not recognized any more.

 What IDE controller is it ?
 I have the same problem with a:
 pciide0 at pci1 dev 3 function 0: CMD Technology PCI0646 (rev. 0x03)
 pciide0: bus-master DMA support present
 pciide0: primary channel configured to native-PCI mode

 -- 
 Manuel Bouyer <bouyer@antioche.eu.org>
      NetBSD: 24 ans d'experience feront toujours la difference
 --

From: "Julio M. Merino Vidal" <jmmv@menta.net>
To: Manuel Bouyer <bouyer@antioche.eu.org>
Cc: gnats-bugs@gnats.netbsd.org, netbsd-bugs@netbsd.org
Subject: Re: kern/22869: Slave IDE drive not detected
Date: Sat, 20 Sep 2003 20:24:19 +0200

 On Sat, 20 Sep 2003 20:18:10 +0200
 Manuel Bouyer <bouyer@antioche.eu.org> wrote:

 > What IDE controller is it ?
 > I have the same problem with a:
 > pciide0 at pci1 dev 3 function 0: CMD Technology PCI0646 (rev. 0x03)
 > pciide0: bus-master DMA support present
 > pciide0: primary channel configured to native-PCI mode

 pciide0 at pci0 dev 17 function 1: VIA Technologies VT8235 ATA133 controller
 pciide0: bus-master DMA support present
 pciide0: primary channel configured to compatibility mode

 It seems a generic problem (introduced with the quick detection of slave
 drives when not present).

 Cheers

 -- 
 Julio M. Merino Vidal <jmmv@menta.net>
 The NetBSD Project - http://www.NetBSD.org/

From: Quentin Garnier <netbsd@quatriemek.com>
To: tech-kern@netbsd.org
Cc: gnats-bugs@gnats.netbsd.org
Subject: kern/22869 and ghost detection for IDE controllers
Date: Sat, 20 Sep 2003 20:26:48 +0200

 Some people reported issues with the new wdc.c code committed yesterday,
 with the kernel showing 'ghost detected' messages and preventing any slave
 device to be found (see PR kern/22869).

 I've been doing some digging today but I couldn't find any real IDE
 specification. Though I saw the following:

 > Mind: BOTH devices will get their registers WRITTEN. Any data or
 > register READ will come from the selected device. ONLY the
 > selected device will execute commands.

 in http://www.ent.ohiou.edu/~welker/ide.txt.

 I don't know what this is worth, but I can tell this is exactly what is
 happening on my hardware, on probably on other's.

 The ghost detection algorithm does the following:

 write 1 to <some data register> for drive 1
 write 2 to <some data register> for drive 0
 read <some data register> for drive 1
 if value read is 2 then disbale drive 1 and print message about a ghost
 detected.

 Of course, if the citation above is true, this code will always detect a
 ghost.

 Maybe someone more clueful with IDE can confirm or infirm this, in the
 meantime I suggest this piece of code should be at least commented out.

 -- 
 Quentin Garnier - cube@cubidou.net
 "Feels like I'm fiddling while Rome is burning down.
 Should I lay my fiddle down and take a rifle from the ground ?"
 Leigh Nash/Sixpence None The Richer, Paralyzed, Divine Discontents, 2002.

From: Manuel Bouyer <bouyer@antioche.eu.org>
To: "Julio M. Merino Vidal" <jmmv@menta.net>
Cc: gnats-bugs@gnats.netbsd.org, netbsd-bugs@netbsd.org
Subject: Re: kern/22869: Slave IDE drive not detected
Date: Sat, 20 Sep 2003 21:32:46 +0200

 On Sat, Sep 20, 2003 at 08:24:19PM +0200, Julio M. Merino Vidal wrote:
 > > What IDE controller is it ?
 > > I have the same problem with a:
 > > pciide0 at pci1 dev 3 function 0: CMD Technology PCI0646 (rev. 0x03)
 > > pciide0: bus-master DMA support present
 > > pciide0: primary channel configured to native-PCI mode
 > 
 > pciide0 at pci0 dev 17 function 1: VIA Technologies VT8235 ATA133 controller
 > pciide0: bus-master DMA support present
 > pciide0: primary channel configured to compatibility mode
 > 
 > It seems a generic problem (introduced with the quick detection of slave
 > drives when not present).

 I wouldn't call it generic, but I suspect it's happening with most pciide
 controllers. My theory is that these controllers have shadows registers of
 the drives registers, and don't always bother reading the real value.
 I tried using the sector_hi register instead of the sector register, with
 no better results.

 I'm going to run more tests (waiting for a i386 release build
 to complete ...) with different controllers.

 -- 
 Manuel Bouyer <bouyer@antioche.eu.org>
      NetBSD: 24 ans d'experience feront toujours la difference
 --

From: Manuel Bouyer <bouyer@antioche.eu.org>
To: Quentin Garnier <netbsd@quatriemek.com>
Cc: tech-kern@NetBSD.org, gnats-bugs@gnats.netbsd.org
Subject: Re: kern/22869 and ghost detection for IDE controllers
Date: Sat, 20 Sep 2003 23:29:32 +0200

 On Sat, Sep 20, 2003 at 08:26:48PM +0200, Quentin Garnier wrote:
 > Some people reported issues with the new wdc.c code committed yesterday,
 > with the kernel showing 'ghost detected' messages and preventing any slave
 > device to be found (see PR kern/22869).
 > 
 > I've been doing some digging today but I couldn't find any real IDE
 > specification. Though I saw the following:

 http://www.t13.org/

 > 
 > > Mind: BOTH devices will get their registers WRITTEN. Any data or
 > > register READ will come from the selected device. ONLY the
 > > selected device will execute commands.
 > 
 > in http://www.ent.ohiou.edu/~welker/ide.txt.
 > 
 > I don't know what this is worth, but I can tell this is exactly what is
 > happening on my hardware, on probably on other's.

 Yes, of course you're right ! I forgot this. This is there since ata-2
 at last.

 > [...]
 > Maybe someone more clueful with IDE can confirm or infirm this, in the
 > meantime I suggest this piece of code should be at least commented out.

 I'm going to remove it, I've another change pending too.

 -- 
 Manuel Bouyer <bouyer@antioche.eu.org>
      NetBSD: 24 ans d'experience feront toujours la difference
 --

From: Manuel Bouyer <bouyer@netbsd.org>
To: gnats-bugs@gnats.NetBSD.org
Cc:  
Subject: pr/22869 CVS commit: src/sys/dev/ic
Date: Sat, 20 Sep 2003 21:42:49 +0000 (UTC)

 Module Name:	src
 Committed By:	bouyer
 Date:		Sat Sep 20 21:42:48 UTC 2003

 Modified Files:
 	src/sys/dev/ic: wdc.c

 Log Message:
 Remove the "Register ghost test". It won't work, because on ATA register
 of both devices are written, and device 0 will respond for device 1 if
 device 1 isn't present. Pointed out by Quentin Garnier.
 So the only way to know if device 1 is there or not is to send a command, which
 is done later.
 Detecting the second device here isn't important and won't speed up the probe.
 We just need to know if there is at last one device on the bus.

 Fix PR kern/22869 from Julio M. Merino Vidal.


 To generate a diff of this commit:
 cvs rdiff -r1.127 -r1.128 src/sys/dev/ic/wdc.c

 Please note that diffs are not public domain; they are subject to the
 copyright notices on the relevant files.

State-Changed-From-To: open->closed 
State-Changed-By: bouyer 
State-Changed-When: Sat Sep 20 17:44:37 EDT 2003 
State-Changed-Why:  
Fixed in wdc.c 1.128. Thanks ! 

From: "Charles M. Hannum" <abuse@spamalicious.com>
To: Manuel Bouyer <bouyer@antioche.eu.org>
Cc: "Julio M. Merino Vidal" <jmmv@menta.net>
Subject: Re: kern/22869: Slave IDE drive not detected
Date: Mon, 22 Sep 2003 04:56:47 +0000 (UTC)

 > I wouldn't call it generic, but I suspect it's happening with most pciide
 > controllers. My theory is that these controllers have shadows registers of
 > the drives registers, and don't always bother reading the real value.

 That might be what you'd think if you only read the ATA-5 spec, and
 not ATA-2 and earlier.  The reality is much dumber.

 Traditionally, if the master does not detect a slave device (by
 probing DIAGP during reset), it fakes the slave register access by
 exposing its own register file -- so it smells a bit like there is
 another device there -- but any attempt to actually execute a command
 fails.

 Why it's done this way, WTF knows?  It comes up every year or two on
 the ATA mailing list, and nobody who's around any more seems to know
 why.  It's a historical oddity.

 At any rate, proper detection of drives without 15- or 30-second
 stalls is very important, and it *will* be fixed.  It's not even
 vaguely correct to say that detecting the ghosting "won't speed up the
 probe" -- it has a huge and extremely obvious impact on many machines.


From: "Charles M. Hannum" <abuse@spamalicious.com>
To: Manuel Bouyer <bouyer@antioche.eu.org>
Cc: "Julio M. Merino Vidal" <jmmv@menta.net>
Subject: Re: kern/22869: Slave IDE drive not detected
Date: Mon, 22 Sep 2003 14:26:33 +0000 (UTC)

 > detecting the ghosting *before the reset* should't speed up the reset.
 > If we have only one master, it will also handle registers read for the
 > slave and both drives will appear ready at the same time.

 I'm not sure what difference you think that makes.  Since we're
 (typically) reading a status of all-0s at that point, the reset does
 complete quickly, but we still try sending a command to the bogus
 drive 1 and time out.


From: Manuel Bouyer <bouyer@antioche.lip6.fr>
To: "Charles M. Hannum" <abuse@spamalicious.com>
Cc: "Julio M. Merino Vidal" <jmmv@menta.net>, gnats-bugs@gnats.netbsd.org,
  netbsd-bugs@netbsd.org
Subject: Re: kern/22869: Slave IDE drive not detected
Date: Mon, 22 Sep 2003 17:41:16 +0200

 On Mon, Sep 22, 2003 at 02:26:33PM +0000, Charles M. Hannum wrote:
 > 
 > > detecting the ghosting *before the reset* should't speed up the reset.
 > > If we have only one master, it will also handle registers read for the
 > > slave and both drives will appear ready at the same time.
 > 
 > I'm not sure what difference you think that makes.  Since we're
 > (typically) reading a status of all-0s at that point, the reset does

 We should get the contents of the drive 0 registers, not all 0.

 > complete quickly, but we still try sending a command to the bogus
 > drive 1 and time out.

 I can't see how we can differentiate a real drive from a bogus one
 exept by sending a command, as we will read the same values from registers,
 whatever drive is selected, when there is only one drive.

 Now, a command send to drive 1, when there's only one master, shoud not time
 out, it should be aborted immediatly by the drive. If it times out maybe
 we have a problem with the code sending the command.

 --
 Manuel Bouyer, LIP6, Universite Paris VI.           Manuel.Bouyer@lip6.fr
      NetBSD: 24 ans d'experience feront toujours la difference
 --

From: Reinoud Zandijk <reinoud@netbsd.org>
To: Martin Husemann <martin@duskware.de>
Cc: gnats@gnats.netbsd.org
Subject: Re: kern/22869
Date: Mon, 29 Dec 2003 15:19:14 +0100

 Hi Martin,

 On Mon, Dec 29, 2003 at 01:22:11AM +0100, Martin Husemann wrote:
 > To debug this you need to follow this advice I got from Manuel.
 > Please add results to the PR.

 Here it follows!
 Reinoud


 consinit: not using prom console
 Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003
     The NetBSD Foundation, Inc.  All rights reserved.
 Copyright (c) 1982, 1986, 1989, 1991, 1993
     The Regents of the University of California.  All rights reserved.

 NetBSD 1.6ZG (GENERIC) #1: Mon Dec 29 14:50:14 CET 2003
 	imago@starbuck:/usr/sources/cvs.netbsd.org/src/sys/arch/alpha/compile/GENERIC
 Digital Personal WorkStation 500au, 500MHz, s/n 
 8192 byte page size, 1 processor.
 total memory = 768 MB
 (1896 KB reserved for PROM, 766 MB used by NetBSD)
 avail memory = 705 MB
 using 4916 buffers containing 39328 KB of memory
 mainbus0 (root)
 cpu0 at mainbus0: ID 0 (primary), 21164A-0
 cpu0: Architecture extensions: 1<BWX>
 cia0 at mainbus0: DECchip 2117x Core Logic Chipset (Pyxis), pass 1
 cia0: extended capabilities: 1<BWEN>
 cia0: using BWX for PCI config access
 pci0 at cia0 bus 0
 pci0: i/o space, memory space enabled, rd/line, rd/mult, wr/inv ok
 tlp0 at pci0 dev 3 function 0: DECchip 21143 Ethernet, pass 3.0
 tlp0: interrupting at dec 550 irq 0
 tlp0: DEC , Ethernet address 00:00:f8:76:43:f5
 nsphy0 at tlp0 phy 5: DP83840 10/100 media interface, rev. 1
 nsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
 tlp0: 10baseT, 10baseT-FDX, 10base2, 10base5
 sio0 at pci0 dev 7 function 0: Contaq Microsystems 82C693 PCI-ISA Bridge (rev. 0x00)
 cypide0 at pci0 dev 7 function 1
 cypide0: Cypress 82C693 IDE Controller (rev. 0x00)
 cypide0: bus-master DMA support present
 cypide0: primary channel wired to compatibility mode
 cypide0: primary channel interrupting at isa irq 14
 atabus0 at cypide0 channel 0
 cypide1 at pci0 dev 7 function 2
 cypide1: Cypress 82C693 IDE Controller (rev. 0x00)
 cypide1: hardware does not support DMA
 cypide1: primary channel wired to compatibility mode
 cypide1: secondary channel interrupting at isa irq 15
 atabus1 at cypide1 channel 0
 Contaq Microsystems 82C693 PCI-ISA Bridge (USB serial bus, interface 0x10) at pci0 dev 7 function 3 not configured
 ppb0 at pci0 dev 20 function 0: Digital Equipment DECchip 21152 PCI-PCI Bridge (rev. 0x02)
 pci1 at ppb0 bus 1
 pci1: i/o space, memory space enabled, rd/line, wr/inv ok
 isp0 at pci1 dev 4 function 0: QLogic 1020 Fast Wide SCSI HBA
 isp0: interrupting at dec 550 irq 3
 scsibus0 at isp0: 16 targets, 8 luns per target
 rtk0 at pci1 dev 8 function 0: RealTek 8139 10/100BaseTX
 rtk0: interrupting at dec 550 irq 12
 rtk0: Ethernet address 00:10:a7:0a:de:e7
 ukphy0 at rtk0 phy 7: Generic IEEE 802.3u media interface
 ukphy0: OUI 0x000000, model 0x0000, rev. 0
 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
 vga0 at pci1 dev 10 function 0: Texas Instruments TVP4020 Permedia 2 (rev. 0x01)
 wsdisplay0 at vga0 kbdmux 1: console (80x25, vt100 emulation)
 wsmux1: connecting to wsdisplay0
 isa0 at sio0
 com0 at isa0 port 0x3f8-0x3ff irq 4: ns16550a, working fifo
 com1 at isa0 port 0x2f8-0x2ff irq 3: ns16550a, working fifo
 pckbc0 at isa0 port 0x60-0x64
 pckbd0 at pckbc0 (kbd slot)
 pckbc0: using irq 1 for kbd slot
 wskbd0 at pckbd0: console keyboard, using wsdisplay0
 pms0 at pckbc0 (aux slot)
 pckbc0: using irq 12 for aux slot
 wsmouse0 at pms0 mux 0
 lpt0 at isa0 port 0x3bc-0x3bf irq 7
 sb0 at isa0 port 0x220-0x237 irq 5 drq 1: dsp v3.01
 audio0 at sb0: half duplex, mmap, independent
 midi at sb0 not configured
 opl at sb0 not configured
 pcppi0 at isa0 port 0x61
 midi0 at pcppi0: PC speaker
 spkr0 at pcppi0
 isabeep0 at pcppi0
 fdc0 at isa0 port 0x3f0-0x3f7 irq 6 drq 2
 mcclock0 at isa0 port 0x70-0x71: mc146818 or compatible
 stray isa irq 14
 Kernelized RAIDframe activated
 stray isa irq 14
 cypide0:0: before reset, st0=0x50, st1=0x0
 stray isa irq 14
 cypide1:0: before reset, st0=0x0, st1=0x90
 scsibus0: waiting 2 seconds for devices to settle...
 cypide1:0:0: after reset, sc=0x1 sn=0x1 cl=0x14 ch=0xeb
 cypide1:0:1: after reset, sc=0x1 sn=0x1 cl=0x14 ch=0xeb
 cypide1:0: wdcwait_reset() end, st0=0x0 st1=0x10
 cypide1:0: after reset, ret_value=0x1
 cypide1:0:0: after reset, sc=0x1 sn=0x1 cl=0x14 ch=0xeb
 cypide1:0: wait DRDY st0 0x0 st1 0x10
 __wdcwait: timeout (time=11), status d0 error d0 (mask 0x0 bits 0x0)
 atabusattach: ch_drive_flags 0x2 0x0
 stray isa irq 14
 cypide0:0:0: after reset, sc=0x1 sn=0x1 cl=0x0 ch=0x0
 cypide0:0:1: after reset, sc=0x1 sn=0x1 cl=0x0 ch=0x0
 cypide0:0: wdcwait_reset() end, st0=0x50 st1=0x0
 cypide0:0: after reset, ret_value=0x3
 cypide0:0:0: after reset, sc=0x1 sn=0x1 cl=0x0 ch=0x0
 stray isa irq 14; stopped logging
 cypide0:0:1: after reset, sc=0x1 sn=0x1 cl=0x0 ch=0x0
 cypide0:0: wait DRDY st0 0x50 st1 0x0
 __wdcwait: timeout (time=11), status d0 error d0 (mask 0x0 bits 0x0)
 atabusattach: ch_drive_flags 0x1 0x0
 wd0 at atabus0 drive 0: <ST340810A>
 wd0: drive supports 16-sector PIO transfers, LBA addressing
 wd0: 38166 MB, 77545 cyl, 16 head, 63 sec, 512 bytes/sect x 78165360 sectors
 wd0: 32-bit data port
 wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 5 (Ultra/100)
 wd0(cypide0:0:0): using PIO mode 4, DMA mode 2 (using DMA data transfers)
 atapibus0 at atabus1: 2 targets
 cd0 at atapibus0 drive 0: <_NEC DVD+RW ND-1100A, , 1.A0> cdrom removable
 cd0: 32-bit data port
 cd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 2 (Ultra/33)
 wdc_atapi_get_params: drive 1 not present
 cd0(cypide1:0:0): using PIO mode 4
 __wdcwait: timeout (time=11), status d0 error d0 (mask 0x40 bits 0x40)
 __wdcwait: timeout (time=11), status d0 error d0 (mask 0x40 bits 0x40)
 root on wd0a dumps on wd0b
 __wdcwait: timeout (time=11), status d0 error d0 (mask 0x40 bits 0x40)
 __wdcwait: timeout (time=11), status d0 error d0 (mask 0x40 bits 0x40)
 __wdcwait: timeout (time=11), status d0 error d0 (mask 0x40 bits 0x40)
 __wdcwait: timeout (time=11), status d0 error d0 (mask 0x40 bits 0x40)
 __wdcwait: timeout (time=11), status d0 error d0 (mask 0x40 bits 0x40)
 __wdcwait: timeout (time=11), status d0 error d0 (mask 0x40 bits 0x40)
 __wdcwait: timeout (time=11), status d0 error d0 (mask 0x40 bits 0x40)
 __wdcwait: timeout (time=11), status d0 error d0 (mask 0x40 bits 0x40)
 __wdcwait: timeout (time=11), status d0 error d0 (mask 0x40 bits 0x40)
 __wdcwait: timeout (time=11), status d0 error d0 (mask 0x40 bits 0x40)
 __wdcwait: timeout (time=11), status d0 error d0 (mask 0x40 bits 0x40)
 __wdcwait: timeout (time=11), status d0 error d0 (mask 0x40 bits 0x40)
 __wdcwait: timeout (time=11), status d0 error d0 (mask 0x40 bits 0x40)
 __wdcwait: timeout (time=11), status d0 error d0 (mask 0x40 bits 0x40)
 __wdcwait: timeout (time=11), status d0 error d0 (mask 0x40 bits 0x40)
 __wdcwait: timeout (time=11), status d0 error d0 (mask 0x40 bits 0x40)
 __wdcwait: timeout (time=11), status d0 error d0 (mask 0x40 bits 0x40)
 __wdcwait: timeout (time=11), status d0 error d0 (mask 0x40 bits 0x40)
 root file system type: ffs


From: Reinoud Zandijk <reinoud@netbsd.org>(by way of Erik E. Fair)
To: NetBSD GNATS Problem Report Tracking System <gnats-bugs@gnats.netbsd.org>
Cc:  
Subject: Re: kern/22869
Date: Wed, 24 Mar 2004 12:20:02 -0800

 Hi Martin,

 On Mon, Dec 29, 2003 at 01:22:11AM +0100, Martin Husemann wrote:
 >  To debug this you need to follow this advice I got from Manuel.
 >  Please add results to the PR.

 Here it follows!
 Reinoud


 consinit: not using prom console
 Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003
      The NetBSD Foundation, Inc.  All rights reserved.
 Copyright (c) 1982, 1986, 1989, 1991, 1993
      The Regents of the University of California.  All rights reserved.

 NetBSD 1.6ZG (GENERIC) #1: Mon Dec 29 14:50:14 CET 2003
 	imago@starbuck:/usr/sources/cvs.netbsd.org/src/sys/arch/alpha/compile/GENERIC
 Digital Personal WorkStation 500au, 500MHz, s/n
 8192 byte page size, 1 processor.
 total memory = 768 MB
 (1896 KB reserved for PROM, 766 MB used by NetBSD)
 avail memory = 705 MB
 using 4916 buffers containing 39328 KB of memory
 mainbus0 (root)
 cpu0 at mainbus0: ID 0 (primary), 21164A-0
 cpu0: Architecture extensions: 1<BWX>
 cia0 at mainbus0: DECchip 2117x Core Logic Chipset (Pyxis), pass 1
 cia0: extended capabilities: 1<BWEN>
 cia0: using BWX for PCI config access
 pci0 at cia0 bus 0
 pci0: i/o space, memory space enabled, rd/line, rd/mult, wr/inv ok
 tlp0 at pci0 dev 3 function 0: DECchip 21143 Ethernet, pass 3.0
 tlp0: interrupting at dec 550 irq 0
 tlp0: DEC , Ethernet address 00:00:f8:76:43:f5
 nsphy0 at tlp0 phy 5: DP83840 10/100 media interface, rev. 1
 nsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
 tlp0: 10baseT, 10baseT-FDX, 10base2, 10base5
 sio0 at pci0 dev 7 function 0: Contaq Microsystems 82C693 PCI-ISA 
 Bridge (rev. 0x00)
 cypide0 at pci0 dev 7 function 1
 cypide0: Cypress 82C693 IDE Controller (rev. 0x00)
 cypide0: bus-master DMA support present
 cypide0: primary channel wired to compatibility mode
 cypide0: primary channel interrupting at isa irq 14
 atabus0 at cypide0 channel 0
 cypide1 at pci0 dev 7 function 2
 cypide1: Cypress 82C693 IDE Controller (rev. 0x00)
 cypide1: hardware does not support DMA
 cypide1: primary channel wired to compatibility mode
 cypide1: secondary channel interrupting at isa irq 15
 atabus1 at cypide1 channel 0
 Contaq Microsystems 82C693 PCI-ISA Bridge (USB serial bus, interface 
 0x10) at pci0 dev 7 function 3 not configured
 ppb0 at pci0 dev 20 function 0: Digital Equipment DECchip 21152 
 PCI-PCI Bridge (rev. 0x02)
 pci1 at ppb0 bus 1
 pci1: i/o space, memory space enabled, rd/line, wr/inv ok
 isp0 at pci1 dev 4 function 0: QLogic 1020 Fast Wide SCSI HBA
 isp0: interrupting at dec 550 irq 3
 scsibus0 at isp0: 16 targets, 8 luns per target
 rtk0 at pci1 dev 8 function 0: RealTek 8139 10/100BaseTX
 rtk0: interrupting at dec 550 irq 12
 rtk0: Ethernet address 00:10:a7:0a:de:e7
 ukphy0 at rtk0 phy 7: Generic IEEE 802.3u media interface
 ukphy0: OUI 0x000000, model 0x0000, rev. 0
 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
 vga0 at pci1 dev 10 function 0: Texas Instruments TVP4020 Permedia 2 
 (rev. 0x01)
 wsdisplay0 at vga0 kbdmux 1: console (80x25, vt100 emulation)
 wsmux1: connecting to wsdisplay0
 isa0 at sio0
 com0 at isa0 port 0x3f8-0x3ff irq 4: ns16550a, working fifo
 com1 at isa0 port 0x2f8-0x2ff irq 3: ns16550a, working fifo
 pckbc0 at isa0 port 0x60-0x64
 pckbd0 at pckbc0 (kbd slot)
 pckbc0: using irq 1 for kbd slot
 wskbd0 at pckbd0: console keyboard, using wsdisplay0
 pms0 at pckbc0 (aux slot)
 pckbc0: using irq 12 for aux slot
 wsmouse0 at pms0 mux 0
 lpt0 at isa0 port 0x3bc-0x3bf irq 7
 sb0 at isa0 port 0x220-0x237 irq 5 drq 1: dsp v3.01
 audio0 at sb0: half duplex, mmap, independent
 midi at sb0 not configured
 opl at sb0 not configured
 pcppi0 at isa0 port 0x61
 midi0 at pcppi0: PC speaker
 spkr0 at pcppi0
 isabeep0 at pcppi0
 fdc0 at isa0 port 0x3f0-0x3f7 irq 6 drq 2
 mcclock0 at isa0 port 0x70-0x71: mc146818 or compatible
 stray isa irq 14
 Kernelized RAIDframe activated
 stray isa irq 14
 cypide0:0: before reset, st0=0x50, st1=0x0
 stray isa irq 14
 cypide1:0: before reset, st0=0x0, st1=0x90
 scsibus0: waiting 2 seconds for devices to settle...
 cypide1:0:0: after reset, sc=0x1 sn=0x1 cl=0x14 ch=0xeb
 cypide1:0:1: after reset, sc=0x1 sn=0x1 cl=0x14 ch=0xeb
 cypide1:0: wdcwait_reset() end, st0=0x0 st1=0x10
 cypide1:0: after reset, ret_value=0x1
 cypide1:0:0: after reset, sc=0x1 sn=0x1 cl=0x14 ch=0xeb
 cypide1:0: wait DRDY st0 0x0 st1 0x10
 __wdcwait: timeout (time=11), status d0 error d0 (mask 0x0 bits 0x0)
 atabusattach: ch_drive_flags 0x2 0x0
 stray isa irq 14
 cypide0:0:0: after reset, sc=0x1 sn=0x1 cl=0x0 ch=0x0
 cypide0:0:1: after reset, sc=0x1 sn=0x1 cl=0x0 ch=0x0
 cypide0:0: wdcwait_reset() end, st0=0x50 st1=0x0
 cypide0:0: after reset, ret_value=0x3
 cypide0:0:0: after reset, sc=0x1 sn=0x1 cl=0x0 ch=0x0
 stray isa irq 14; stopped logging
 cypide0:0:1: after reset, sc=0x1 sn=0x1 cl=0x0 ch=0x0
 cypide0:0: wait DRDY st0 0x50 st1 0x0
 __wdcwait: timeout (time=11), status d0 error d0 (mask 0x0 bits 0x0)
 atabusattach: ch_drive_flags 0x1 0x0
 wd0 at atabus0 drive 0: <ST340810A>
 wd0: drive supports 16-sector PIO transfers, LBA addressing
 wd0: 38166 MB, 77545 cyl, 16 head, 63 sec, 512 bytes/sect x 78165360 sectors
 wd0: 32-bit data port
 wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 5 (Ultra/100)
 wd0(cypide0:0:0): using PIO mode 4, DMA mode 2 (using DMA data transfers)
 atapibus0 at atabus1: 2 targets
 cd0 at atapibus0 drive 0: <_NEC DVD+RW ND-1100A, , 1.A0> cdrom removable
 cd0: 32-bit data port
 cd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 2 (Ultra/33)
 wdc_atapi_get_params: drive 1 not present
 cd0(cypide1:0:0): using PIO mode 4
 __wdcwait: timeout (time=11), status d0 error d0 (mask 0x40 bits 0x40)
 __wdcwait: timeout (time=11), status d0 error d0 (mask 0x40 bits 0x40)
 root on wd0a dumps on wd0b
 __wdcwait: timeout (time=11), status d0 error d0 (mask 0x40 bits 0x40)
 __wdcwait: timeout (time=11), status d0 error d0 (mask 0x40 bits 0x40)
 __wdcwait: timeout (time=11), status d0 error d0 (mask 0x40 bits 0x40)
 __wdcwait: timeout (time=11), status d0 error d0 (mask 0x40 bits 0x40)
 __wdcwait: timeout (time=11), status d0 error d0 (mask 0x40 bits 0x40)
 __wdcwait: timeout (time=11), status d0 error d0 (mask 0x40 bits 0x40)
 __wdcwait: timeout (time=11), status d0 error d0 (mask 0x40 bits 0x40)
 __wdcwait: timeout (time=11), status d0 error d0 (mask 0x40 bits 0x40)
 __wdcwait: timeout (time=11), status d0 error d0 (mask 0x40 bits 0x40)
 __wdcwait: timeout (time=11), status d0 error d0 (mask 0x40 bits 0x40)
 __wdcwait: timeout (time=11), status d0 error d0 (mask 0x40 bits 0x40)
 __wdcwait: timeout (time=11), status d0 error d0 (mask 0x40 bits 0x40)
 __wdcwait: timeout (time=11), status d0 error d0 (mask 0x40 bits 0x40)
 __wdcwait: timeout (time=11), status d0 error d0 (mask 0x40 bits 0x40)
 __wdcwait: timeout (time=11), status d0 error d0 (mask 0x40 bits 0x40)
 __wdcwait: timeout (time=11), status d0 error d0 (mask 0x40 bits 0x40)
 __wdcwait: timeout (time=11), status d0 error d0 (mask 0x40 bits 0x40)
 __wdcwait: timeout (time=11), status d0 error d0 (mask 0x40 bits 0x40)
 root file system type: ffs

From: Reinoud Zandijk <reinoud@netbsd.org>(by way of Erik E. Fair)
To: NetBSD GNATS Problem Report Tracking System <gnats-bugs@gnats.netbsd.org>
Cc:  
Subject: Re: kern/22869
Date: Wed, 24 Mar 2004 12:19:44 -0800

 Just checked with the NT bios and yes they are connected. There is indeed
 the CD-RW on ATAPI#1

 Cheers,
 Reinoud
State-Changed-From-To: open->closed 
State-Changed-By: fair 
State-Changed-When: Wed Mar 24 21:44:13 UTC 2004 
State-Changed-Why:  

The audit trail shows this PR closed, but not reopened. 
I wonder why. 
>Unformatted:

NetBSD Home
NetBSD PR Database Search

(Contact us) $NetBSD: query-full-pr,v 1.51 2026/08/10 02:28:17 riastradh Exp $
$NetBSD: gnats_config.sh,v 1.10 2026/05/13 22:00:09 riastradh Exp $
Copyright © 1994-2026 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.