On Sat, 12 Feb 2000, Kazutaka YOKOTA wrote:
> Both changes have effect only when we fail to attach a serial port,
> which is not the case with your machine...
>
> Hmm. Any idea, Bruce?
The usual (non-AST4) of COM_MULTIPORT is currently broken. This causes
non-working interrupts on all except t
> You have a multiport serial card in your system, right? What is it
> and how do you configure it in your kernel configuration file?
Here's the relevant bits (note: sio0 has been tried without 0x10):
# generic multi-I/O card with 16550 type UARTS
device sio0at isa? port IO_COM1 fl
>The following is, as indicated, a kernel built from Jan 24 cvs snap.
>Everything with this kernel is fine.
>
>ttyp1:--ROOT--@portley (2)# uname -a
>FreeBSD portley.mrynet.com 4.0-CURRENT FreeBSD 4.0-CURRENT #24: Mon Jan 24
> 17:36:27 PST 2000
>[EMAIL PROTECTED]:/usr/src/sys/compile/PO
>
> >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
>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 unacc
>> >moused_enable="NO" # Run the mouse daemon.
>> >moused_type="mousesystems" # See man page for rc.conf(5) for available
> se
>> >ttings.
>> >moused_port="/dev/cuaa0" # Set to your mouse port.
>> >moused_flags="" # Any additional flags to moused.
>>
>> Your configuration refer
>Last cvs was a few hours ago and world was installed.
>A kernel built from this cvs hangs dead-hard when moused runs from
>rc.i386 and no mouse is plugged into the psm0 port
>
> device psm0at atkbdc? irq 12
>
>The moused config is:
>
>moused_enable="NO" # Run the mouse
