From owner-freebsd-hackers Wed Sep 9 05:56:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA07267 for freebsd-hackers-outgoing; Wed, 9 Sep 1998 05:56:03 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alpha.netvision.net.il (alpha.netvision.net.il [194.90.1.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA07197 for ; Wed, 9 Sep 1998 05:55:55 -0700 (PDT) (envelope-from ycs@netvision.net.il) Received: from netvision.net.il (RAS2-p18.hfa.netvision.net.il [62.0.145.146]) by alpha.netvision.net.il (8.8.6/8.8.6) with ESMTP id OAA04994 for ; Wed, 9 Sep 1998 14:54:39 +0300 (IDT) Message-ID: <35F66CE1.347AAE45@netvision.net.il> Date: Wed, 09 Sep 1998 14:56:17 +0300 From: Yoav Cohen-Sivan X-Mailer: Mozilla 4.5b1 [en] (X11; I; FreeBSD 2.2.7-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG Subject: sio FIFO overflow? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think I am seeig FIFO overflows during 115200 bps transfers on a serial port. Especially with heavy disk activity. Is there a way to flag FIFO overflows, and is there a way to check interrupt latency? I've been seeing randomly-timed link lockups during almost every PPP session I initiate (both kernel and user). The lockups clear after hanging up and redialling. I finally lowered my bps from 115200 to 57600, and voila! lockups have disappeared. I've spent the better part of the past 3 days banging on the link (and my phone bill) like there's no tomorrow. The lockups were usually during heavy link and system use, and I'm thinking the serial FIFO was overflowing, but the sio driver latency was too great to respond in time. Could this have caused some corrupted packets to be sent to my ISP (using Cisco 5200 equipment), causing it to ignore me for the duration of the session? Yoav To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message