From owner-freebsd-current Mon Aug 23 23:49: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from piglet.dstc.edu.au (piglet.dstc.edu.au [130.102.176.1]) by hub.freebsd.org (Postfix) with ESMTP id D261215810 for ; Mon, 23 Aug 1999 23:49:00 -0700 (PDT) (envelope-from ggm@dstc.edu.au) Received: from dstc.edu.au (asuncion.dstc.edu.au [130.102.176.155]) by piglet.dstc.edu.au (8.9.3/8.9.3) with ESMTP id QAA18879; Tue, 24 Aug 1999 16:48:27 +1000 (EST) X-Mailer: exmh version 2.0.2 2/24/98 To: nate@mt.sri.com (Nate Williams) Cc: freebsd-current@FreeBSD.ORG Subject: Re: SIO "lost interrupt" status in current? In-reply-to: Your message of "Mon, 23 Aug 1999 21:26:02 CST." <199908240326.VAA04652@mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 24 Aug 1999 16:48:19 +1000 Message-ID: <16540.935477299@dstc.edu.au> From: George Michaelson Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm actually pretty sure it happens even without X11 live. This worries m e! > changing the modem serial speed down from 57600 through 33600 to 19200 ma de > no difference. This also worries me. If the speed isn't being set down, then somehow interrupts are being turned off for a very long time, possibly by another device driver, or possibly you have bad hardware. If interrupts were off, wouldn't I see other things like mice freezes or X-repaint problems? I'd go with either of these actually. Any suggestions for debug methods? (for instance, would swapping the sio used for mouse and modem make sense? or do they use common paths in the motherboard such that a fault in serial is going to kill both of them..) I would *love* this to turn out to be hardware! cheers -George -- George Michaelson | DSTC Pty Ltd Email: ggm@dstc.edu.au | University of Qld 4072 Phone: +61 7 3365 4310 | Australia Fax: +61 7 3365 4311 | http://www.dstc.edu.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message