Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 23 Dec 2003 08:07:41 -0800
From:      "Kevin Oberman" <oberman@es.net>
To:        jesse@wingnet.net
Cc:        freebsd-current@freebsd.org
Subject:   Re: usb problem with 5.2-RC1 
Message-ID:  <20031223160741.6613F5D08@ptavv.es.net>
In-Reply-To: Message from Jesse Guardiani <jesse@wingnet.net>  of "Tue, 23 Dec 2003 10:07:52 EST." <bs9lo8$ufk$1@sea.gmane.org> 

next in thread | previous in thread | raw e-mail | index | archive | help
> From: Jesse Guardiani <jesse@wingnet.net>
> Date: Tue, 23 Dec 2003 10:07:52 -0500
> Sender: owner-freebsd-current@freebsd.org
> 
> Howdy list,
> 
> Upon resuming from an APM induced suspended state as
> described here:
> 
>     http://article.gmane.org/gmane.os.freebsd.current/36652/match=tracking+down+ata0+problem
> 
> I experience USB problems. Specifically, my mouse
> doesn't work and I get these messages from the kernel:
> 
> Dec 23 09:35:50 trevarthan kernel: ums0: at uhub1 port 2 (addr 2) disconnected
> Dec 23 09:35:50 trevarthan kernel: ums0: detached
> Dec 23 09:35:58 trevarthan moused: unable to open /dev/ums0: No such file or directory
> Dec 23 09:37:09 trevarthan kernel: uhub1: device problem, disabling port 2
> Dec 23 09:38:30 trevarthan kernel: uhub1: device problem, disabling port 2
> Dec 23 09:39:52 trevarthan kernel: uhub1: device problem, disabling port 1
> Dec 23 09:39:52 trevarthan kernel: uhub1: port error, restarting port 2
> Dec 23 09:52:50 trevarthan kernel: uhub1: device problem, disabling port 2
> Dec 23 09:55:10 trevarthan kernel: uhub1: device problem, disabling port 2

Yes, this is a well known problem with USB. Some fixes for several of the
USB drivers were committed last week, but the primary issues with the
USB and resume remain unresolved. Nate has posted a request for help in
finding this long-standing bug.

The normal work-around is to build without USB and only load USB when
needed, but a USB mouse requires it all the time, so...

USB also blocks the best power-saving mode (C3) on my system, so I
really hope that some of this can be tracked down soon. But, with the
latest commits to ACPI code I have finally switched to running with ACPI
most of the time. Things do continue to get better.
-- 
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: oberman@es.net			Phone: +1 510 486-8634



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