7.3-P r203700: what can I do about "psm0: the aux device is
gone!"
jhell
jhell at DataIX.net
Thu Feb 11 17:06:59 UTC 2010
On Tue, 9 Feb 2010 17:41, david@ wrote:
> I normally run X11 (via xdm) on my laptop.
>
> Today, running FreeBSD 7.3-PRERELEASE as of r203700, the mouse stopped
> moving.
>
> Logging in from a pty & checking the last bit of /var/log/messages
> showed:
>
> Feb 9 14:30:27 localhost kernel: kbdc: TEST_AUX_PORT status:0000
> Feb 9 14:30:27 localhost kernel: kbdc: RESET_AUX return code:00fa
> Feb 9 14:30:27 localhost kernel: kbdc: RESET_AUX status:ffffffff
> Feb 9 14:30:27 localhost kernel: kbdc: DIAGNOSE status:0055
> Feb 9 14:30:27 localhost kernel: kbdc: TEST_KBD_PORT status:0000
> Feb 9 14:30:27 localhost kernel: psm0: failed to reset the aux device.
> Feb 9 14:30:27 localhost kernel: psm0: the aux device has gone! (reinitialize).
>
>
> uname output:
>
> FreeBSD localhost 7.3-PRERELEASE FreeBSD 7.3-PRERELEASE #56 r203700: Tue Feb 9 05:31:36 PST 2010 root at g1-136.catwhisker.org:/common/S2/obj/usr/src/sys/CANARY i386
>
> So far, the least disruptive form of evasive action I've found is a
> reboot, which is quite a bit more disruptive than I'd prefer.
>
> Help?
>
> Thanks!
>
> Peace,
> david
>
High David,
I'm assuming that you've checked to make sure that moused is running after
psm has disappeared ?.
As a somewhat workaround until the cause of this problem can be determined
you could setup a cronjob as root to check for moused and if not found
restart it.
Add moused_port="/dev/ums?" to /etc/rc.conf and replace ? with
corresponding device number.
Add the following to /etc/crontab
pgrep moused ||service moused restart
Of course this does not detect which moused is running and for what device
so some adjustment might be needed there if you have more then one moused
running at a time usually.
Good Luck.
--
jhell
More information about the freebsd-stable
mailing list