Date: Tue, 18 May 2004 09:57:06 -0400 From: Mike Tancsa <mike@sentex.net> To: Bruce Evans <bde@zeta.org.au> Cc: freebsd-current@freebsd.org Subject: Re: sio / puc wedging on both -current and -stable Message-ID: <6.0.3.0.0.20040518095146.069184a0@64.7.153.2> In-Reply-To: <6.0.3.0.0.20040518094139.059b0cb0@64.7.153.2> References: <6.0.3.0.0.20040517154946.06d23d60@64.7.153.2> <20040518132157.B8772@gamplex.bde.org> <6.0.3.0.0.20040518094139.059b0cb0@64.7.153.2>
next in thread | previous in thread | raw e-mail | index | archive | help
At 09:49 AM 18/05/2004, Mike Tancsa wrote:
>today. One quick note that I am not sure if its a fluke yet or something
>important, the problem *seems* to go away, if on the STABLE box, I remove
>the defs for sio2 and sio3
>device sio2 at isa? disable port IO_COM3 irq 5
>device sio3 at isa? disable port IO_COM4 irq 9
>to
>#device sio2 at isa? disable port IO_COM3 irq 5
>#device sio3 at isa? disable port IO_COM4 irq 9
>
>But it has not yet locked up in 12hrs and it usually takes 15-40min.
Spoke too soon. It seems if the box is quite and doing nothing (i.e. not
even me typing across an ssh session) than it does sit work through the
night. To alert myself of a lockup, I had been doing ping -A
192.168.43.51 to tell me when it froze. It seems my monitoring trick has
something to do with triggering / encouraging the problem.
---Mike
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6.0.3.0.0.20040518095146.069184a0>