Date: Mon, 30 Nov 1998 15:14:30 -0800 From: Mike Smith <mike@smith.net.au> To: geoffb@demon.net Cc: bde@zeta.org.au (Bruce Evans), ortmann@sparc.isl.net, andyf@speednet.com.au, freebsd-current@FreeBSD.ORG, johan@granlund.nu Subject: Re: sio breakage Message-ID: <199811302314.PAA06193@dingo.cdrom.com> In-Reply-To: Your message of "Mon, 30 Nov 1998 16:27:33 GMT." <199811301627.QAA00766@gti.noc.demon.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> > >> > I see these types of messages (when running XF86 3.3.2): > > >> > > > >> > Nov 25 23:10:11 zippy /kernel: sio0: 9 more tty-level buffer overflows (total 1260) > > >> > Nov 25 23:10:12 zippy /kernel: sio0: 4 more tty-level buffer overflows (total 1264) > > >> > Nov 25 23:10:15 zippy /kernel: sio0: 20 more tty-level buffer overflows (total 1284) > > >> > Nov 26 13:36:55 zippy /kernel: sio0: 1 more silo overflow (total 4) > > > > This seems to be caused by some video cards and/or X drivers. > > > > >I am curious to know whats going on here, I have been seeing numerous > > >silo overflows while using my laptop (2.2.6+PAO) as a console for a > > >DEC multia/UDB, I had dismissed them as an annoyance probably caused > > >by a slight misconfiguration in /etc/remote. > > > I was assuming the serial interface which is a fixed one breaking out of > the back of the Laptop had nothing to do with the PCMCIA, You're quite correct; it doesn't. There's *something* holding up both your interrupt handlers and the tty soft interrupt; maybe even possibly the same thing that causes the "calcru: negative time for ..." messages. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199811302314.PAA06193>