Server reboots when silo overflows - FreeBSD 4.11
Mike Tancsa
mike at sentex.net
Fri Feb 11 04:34:48 PST 2005
At 12:37 AM 11/02/2005, Lefteris Tsintjelis wrote:
> > >sio5: 1 more silo overflow (total 7)
> > >puc0: <VScom PCI-200L> port
> > >0xb000-0xb007,0xb400-0xb407,0xb800-0xb807,0xd000-0xd007 mem
> > >0xea800000-0xea80003f irq 14 at device 12.0 on pci2
> > >sio4: configured irq 14 not in bitmap of probed irqs 0x8000
> > >sio4: type 16550A
> > >sio5: configured irq 14 not in bitmap of probed irqs 0x8000
> > >sio5: type 16550A
> >
> > How do you have device sio configured in your kernel ? Are you trying to
> > specify the ports for the puc attached serial ports ? All you need is
> >
> > device sio
> > device puc
>
>device sio0 at isa? port IO_COM1 flags 0x10 irq 4
>device sio1 at isa? port IO_COM2 irq 3
>device sio2 at isa? disable port IO_COM3 irq 5
>device sio3 at isa? disable port IO_COM4 irq 9
>
>device puc
>
>No other sio specific devices for puc other than the kernel's default.
>The sio0/1 never gave me any trouble though. Its the sio4/5 (puc)
>that fail me. BTW this bug is old and run to it again about a year ago.
>
> > Also, enable crash dumps and build a debug kernel.
>
>I enabled the debug symbols already and I have a few crash dumps.
>What can do I do next?
Take out the sio2 and sio3 definitions and just have
device sio
device puc
leave sio0 and sio1 as is.
---Mike
More information about the freebsd-stable
mailing list