Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!news.sprintlink.net!in2.uu.net!newsfeed.pitt.edu!toads.pgh.pa.us!usenet From: Jim Durham <durham> Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Help !! interrupt-level overflows Date: 22 Sep 1995 00:38:40 GMT Organization: The Toads Lines: 34 Message-ID: <43t0ih$2fm@toads.pgh.pa.us> References: <431281$511@sparky.servicom.es> NNTP-Posting-Host: w2xo.pgh.pa.us Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 1.1N (X11; I; BSD/386 uname failed) X-URL: news:431281$511@sparky.servicom.es Antonio Navarro Navarro <bemar@servicom.es> wrote: >I am trying to connect a modem (28.800 bps Hayes compatible) to my FreeBSD machine in order to gain >access to it via modem. When I connect using the modem, the machine shows the login and password >prompt, but when I key in the login and password the terminal emulator I use shows me a lot of >garbage ( I key in my login for example 'antonio', and the terminal shows 'antosdfsogsrwwe' ). The >console of the FreeBSD Machine show the next message : > > bemar/kernel : sio0 : xxx more interrupt-level overflows (total yyy) > >being xxx and yyy different numbers each time. Please, help me !!, (The same message appears when I >try to connect a mouse and use them under X-Windows) > This means that the tty buffers are overflowing without being serviced. Too many characters have come in and the buffers have not been emptied, probably because something is not servicing interrupts quickly enough. This can be caused by a hung process. I sometimes get this when a process that has the serial ports open tries to do a kill() on a child process and gets caught in a wait condition. Since it seems to do it in all cases, it sounds like a hardware problem to do with interrupts on your serial card. Perhaps you have them configured improperly. sio0 (com1:) should be be set to IRQ 4 on the card. sio1 (com2:) should be set to IRQ 3. Another possibility is that you are trying to use a card with 8250 Uarts at 28.8 K. You should have the newer 16550AN Uarts which buffer 7 bytes in hardware. Regards, Jim Durham