>The fact remains, however -- If moused_enable is set to YES, and the
>mouse is not present, the kernel crashes when trying to start moused,
>and it crashes VERY hard. It is a total freeze.
>This crash is the issue. I'm pursuing the fact that if this is
>reproducible elsewhere that it is unacceptable.
>
>I've now done a completely clean cvs and world build, and the same
>for the kernel. The problem is still occuring.
Would you carry out the following test?
1. Boot the system, but don't run moused yet.
2. Run moused as follows:
moused -d -f -p /dev/cuaa0 -i all
You should see something like the following (if everything is Ok :-)
zeus# moused -d -f -p /dev/cuaa0 -i all
moused: PnP COM device rev 1.0 probe...
moused: modem status 03
moused: alternate probe...
moused: cannot determine mouse type on /dev/cuaa0
/dev/cuaa0 unknown unknown generic
zeus#
I would like to know at which point your system hangs.
(BTW, the above output is obtained from my -CURRENT box cvsupped
and compiled on 8 February.)
Kazu
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
