Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 27 Feb 2006 15:50:07 GMT
From:      Eugene Grosbein <eugen@grosbein.pp.ru>
To:        freebsd-usb@FreeBSD.org
Subject:   Re: usb/81524 : panic: usb_cold_explore: busses to explore when !cold
Message-ID:  <200602271550.k1RFo7U8077630@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help
The following reply was made to PR usb/81524; it has been noted by GNATS.

From: Eugene Grosbein <eugen@grosbein.pp.ru>
To: bug-followup@freebsd.org
Cc: iedowse@freebsd.org
Subject: Re: usb/81524 : panic: usb_cold_explore: busses to explore when !cold
Date: Mon, 27 Feb 2006 22:47:54 +0700

 >>I've upgraded my system to RELENG_4 today.
 >>The kernel still panices the same way when compiled
 >>with INVARIANS and INVARIANT_SUPPORT but without
 >>these options it detects devices only once.
  
 >Could you try the patch below to see if it helps? I forget all the
 >details of the USB backports that caused this, so I'm probably
 >missing something obvious.
 
 > Index: usb.c
 > ===================================================================
 > RCS file: /home/iedowse/CVS/src/sys/dev/usb/usb.c,v
 > retrieving revision 1.26.2.13
 > diff -u -r1.26.2.13 usb.c
 
 I've applied your patch to 1.26.2.14 (that's the latest revision
 in RELENG_4 for now) and it broke my USB. The kernel prints at the boot time:
 
 usb_new_device: set address 2 failed - trying a port reset
 usb_new_device: set address 2 failed - trying a port reset
 usb_new_device: set address 2 failed - trying a port reset
 usb_new_device: set address 2 failed
 uhub_explore: usb_new_device failed, error=SET_ADDR_FAILED
 uhub0: device problem (SET_ADDR_FAILED), disabling port 1
 usb_new_device: set address 2 failed - trying a port reset
 usb_new_device: set address 2 failed - trying a port reset
 usb_new_device: set address 2 failed - trying a port reset
 usb_new_device: set address 2 failed
 uhub_explore: usb_new_device failed, error=SET_ADDR_FAILED
 uhub0: device problem (SET_ADDR_FAILED), disabling port 2
  
 >>Also, my APC UPS now is detected as ugen and not as uhid device
 >>due to recent USB blacklist MFC.
  
 >Is that a good or a bad thing?
 
 That's good thing, now apcupsd from ports works with BackUPS CS USB
 using /dev/ugen0. It couldn't use /dev/uhid0 and that's why
 USB blacklist came to be.
 
 Eugene Grosbein



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200602271550.k1RFo7U8077630>