Subject: Still ehci+umass trouble...
To: None <current-users@netbsd.org>
From: Martin S. Weber <Ephaeton@gmx.net>
List: current-users
Date: 01/23/2006 10:26:56
On Sun, Jan 22, 2006 at 04:15:02PM +0100, Martin S. Weber wrote:
> (...)
> 1. I have these (exact same) problems with an Intel EHCI too:
> 
> NetBSD rfhinf038 3.99.11 NetBSD 3.99.11 (GENERIC) 
>  #0: Sat Nov 19 17:13:02 CET 2005  
>  root@rfhinf038:/usr/home/netbsd/obj/sys/arch/i386/compile/GENERIC i386
> (...)

Updated.

NetBSD rfhinf038 3.99.15 NetBSD 3.99.15 (GENERIC.MP_USBDEBUG) 
 #0: Sun Jan 22 17:52:54 CET 2006  
 root@circe.entropie.net:/src/obj/sys/arch/i386/compile/GENERIC.MP_USBDEBUG i386

ehci0 at pci0 dev 29 function 7: Intel 82801EB/ER USB EHCI Controller (rev. 0x02)
ehci0: interrupting at ioapic0 pin 23 (irq 5)
ehci0: BIOS has given up ownership
ehci0: EHCI version 1.0
ehci0: companion controllers, 2 ports each: uhci0 uhci1 uhci2 uhci3
usb4 at ehci0: USB revision 2.0

umass0 at uhub5 port 3 configuration 1 interface 0
umass0: Genesys Logic USB TO IDE, rev 2.00/0.33, addr 3
umass0: using SCSI over Bulk-Only
scsibus0 at umass0: 2 targets, 1 lun per target
sd0 at scsibus0 target 0 lun 0: <IC25N080, ATMR04-0, 0811> disk fixed
sd0: fabricating a geometry
sd0: 76319 MB, 76319 cyl, 64 head, 32 sec, 512 bytes/sect x 156301488 sectors
sd0: fabricating a geometry
umass0: BBB reset failed, TIMEOUT
umass0: BBB bulk-in clear stall failed, TIMEOUT
umass0: BBB bulk-out clear stall failed, TIMEOUT
umass0: BBB reset failed, TIMEOUT
umass0: BBB bulk-in clear stall failed, TIMEOUT
umass0: BBB bulk-out clear stall failed, TIMEOUT
umass0: BBB reset failed, TIMEOUT
umass0: BBB bulk-in clear stall failed, TIMEOUT
umass0: BBB bulk-out clear stall failed, TIMEOUT
umass0: BBB reset failed, TIMEOUT
umass0: BBB bulk-in clear stall failed, TIMEOUT
umass0: BBB bulk-out clear stall failed, TIMEOUT
....

All triggered by a harmless rsync running on the umass. I still have the machine
sitting here, coughing if I should do anything to find out more. 

Hrmpf. While I had EHCI_DEBUG and UMASS_DEBUG in the config file, config -x doesn't
find it. ...And I was wondering where all the debug messages Matthias warned me about
were going :)

--- GENERIC.MP  2005-12-28 02:53:25.000000000 +0100
+++ GENERIC.MP_USBDEBUG 2006-01-23 10:22:18.000000000 +0100
@@ -5,6 +5,9 @@
 
 include "arch/i386/conf/GENERIC"
 
+options EHCI_DEBUG
+options UMASS_DEBUG
+
 options        MULTIPROCESSOR
 
 options        APM_NO_IDLE

Hmm. As I have the machine sitting here coughing, any abuse wished for at a
ddb prompt or the like while I attempt to get a "real debugging" kernel baked? 
(and thus am able to gather enough info to (re)open the/a pr) :)

Regards,

-Martin