From owner-freebsd-current Mon Aug 23 20:29: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id 36DCE14CB9 for ; Mon, 23 Aug 1999 20:29:04 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id VAA06661; Mon, 23 Aug 1999 21:26:03 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id VAA04652; Mon, 23 Aug 1999 21:26:02 -0600 Date: Mon, 23 Aug 1999 21:26:02 -0600 Message-Id: <199908240326.VAA04652@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: George Michaelson Cc: freebsd-current@FreeBSD.ORG Subject: Re: SIO "lost interrupt" status in current? In-Reply-To: <199908240135.LAA15228@azure.dstc.edu.au> References: <199908240135.LAA15228@azure.dstc.edu.au> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@mt.sri.com (Nate Williams) 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 me! > changing the modem serial speed down from 57600 through 33600 to 19200 made > 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. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message