Re: Frequent USB mouse disconnections under load with RELENG_7

On Fri, 2008-02-01 at 07:17 -0800, Jeremy Chadwick wrote:
On Fri, Feb 01, 2008 at 10:00:11PM +1030, Wayne Sierke wrote:
- I've also just noticed that I'm getting these messages on startup
under 7.x:

kernel: Starting devd.
kernel: Starting ums0 moused:
kernel: Starting default moused:
moused: unable to open /dev/ums0: Device busy

but I can't now recall whether I was seeing those under 6.x. Has devd
changed with 7.x? I've got a feeling that I'd tried to get devd in 6.x
to handle the USB mouse on startup, but that I'd found it necessary to
configure moused explicitly (i.e. with moused_port) in rc.conf as listed
below. However my memory of it now is hazy at best. In any case,
disconnections aside, I've not noticed any change in mouse behaviour
since moving to 7.x either in console or xorg.

moused_enable="YES"
moused_port="/dev/ums0"

I think this is what's happening here:

* kernel starts
* usb stack loads, finds a USB mouse, attaches it to ums0
* attachment tells devd "hey, theres a /dev/ums0 device that
just attached"
* /etc/devd.conf automatically spawns moused, which attaches to
the /dev/ums0 device
* rc scripts begin
* moused_enable="yes" is detected, thus moused is run manually
against /dev/ums0
* moused is already running from when devd spawned it, which is
why /dev/ums0 is "Device busy"

I would recommend removing the moused_* stuff in your rc.conf and
let devd take care of it, or, consider editing /etc/devd.conf and
removing the /dev/umsX detection which runs moused.

Yes, well that's what I figured, but over the years getting the USB
mouse to work with X has required manual configuration and I don't
recall ever having any kind of automatic devd-style detection work
previously. The handbook only appears to deal with setting up a mouse
via sysinstall and it isn't apparent to me from the text what
configuration settings would be made when installing a USB mouse.

However this current behaviour looks encouraging so I shall "give it a
whirl" and we'll see whether removing the manual moused config from
rc.conf eliminates these disconnections.


Wayne

_______________________________________________
freebsd-stable@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: HAL/freebsd architecture
    ... :> think that these would be useful for many more applications than just hald. ... This is so that we could preserve current devd functionality ... :> either already done in kernel as well or it better be done in kernel. ... asked developers include extending the ldev driver (luigi's Linux device ...
    (freebsd-arch)
  • Re: HAL/freebsd architecture
    ... :> think that these would be useful for many more applications than just hald. ... This is so that we could preserve current devd functionality ... :> either already done in kernel as well or it better be done in kernel. ...
    (freebsd-arch)
  • devd panic on i386 7.2 Release with CARP
    ... I am having a problem with one of my freebsd 7.2R boxes panicing on start of devd after upgrading to 7.2R. ... custom kernel does not panic with devd_enable="NO" set in rc.conf, ... My kernel config is pretty simple, I am building a test i386 box with a carp kernel to try and repro this on another box, but that box is really slow. ... page fault while in kernel mode ...
    (freebsd-stable)
  • Re: Frequent USB mouse disconnections under load with RELENG_7
    ... kernel: Starting devd. ... to handle the USB mouse on startup, but that I'd found it necessary to ... I would recommend removing the moused_* stuff in your rc.conf and ...
    (freebsd-stable)
  • Re: cvs commit: src/sys/modules/iwi Makefile src/sys/dev/iwi if_iwi.c if_iwireg.h if_iwivar.h
    ... > scottl> can ask for a module via a particular key, devd maps the key to a file ... > scottl> via its config file and loads it into kernel space as a KLD, ... Why is driver firmware any different? ...
    (freebsd-arch)