Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.mel.connect.com.au!munnari.OZ.AU!spool.mu.edu!howland.reston.ans.net!newsfeed.internetmci.com!in1.uu.net!newshost.elvis.ru!newsmaster From: st@sw.ru (Stanislav Protasov) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Interrupt-level buffer overflow Date: Thu, 14 Dec 1995 16:08:12 GMT Organization: Westcom Ltd. Lines: 27 Message-ID: <4api59$4j0@ss10.elvis.ru> NNTP-Posting-Host: zombie.sw.ru X-Newsreader: Forte Free Agent 1.0.82 Hi, All I've got a problem. When I start X (it doesn't matter via startx or xdm) I have the following message after each mouse movement: /kernel: sio0: 240 more interrupt-level buffer overflows (total 498177) I looked at sio.c and saw there something like: if (com->iptr >= com->ibufend) CE_RECORD(com, CE_INTERRUPT_OVERFLOW) So, as far as I understand, com interrupt handler doesn't catch all events from mouse. The machine is 486DX4-100 with 8M RAM, MIO card - Tekram DC-290, Microsoft compatible mouse, running FreeBSD 2.1.0-Release. The most interesting thing is that on another machine (DX4-100 with the same MIO) I never get such a message. The only differences between these 2 PCs is the BIOS (on the first - AWARD, on the second - AMI). So, could anyone tell me, what causes messages to appear: falty MIO (it works absolutely correct under Windows) or incompatible (?) BIOS? Best regards, St.