From owner-freebsd-mobile@FreeBSD.ORG Mon May 3 07:25:26 2004 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 35D5E16A4CE; Mon, 3 May 2004 07:25:26 -0700 (PDT) Received: from smtp.newipnet.com (5.Red-80-32-157.pooles.rima-tde.net [80.32.157.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0882643D67; Mon, 3 May 2004 07:25:25 -0700 (PDT) (envelope-from freebsd@newipnet.com) Received: by smtp.newipnet.com (ESMTP Server, from userid 511) id C69882051B; Mon, 3 May 2004 16:25:22 +0200 (CEST) Received: from madre (madre.newipnet.com [192.168.128.4]) by smtp.newipnet.com (ESMTP Server) with ESMTP id 23961204DB; Mon, 3 May 2004 16:25:17 +0200 (CEST) Message-ID: <200405031623510114.17102862@192.168.128.16> In-Reply-To: <20040502.091407.20913778.imp@bsdimp.com> References: <200405021259230046.12648609@192.168.128.16> <20040502.091407.20913778.imp@bsdimp.com> X-Mailer: Courier 3.50.00.09.1097 (http://www.rosecitysoftware.com) (P) Date: Mon, 03 May 2004 16:23:51 +0200 From: "Carlos Velasco" To: "M. Warner Losh" Content-Type: text/plain; charset="us-ascii" X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on atlas.newipnet.com X-Spam-Level: X-Spam-Status: No, hits=-104.9 required=5.0 tests=BAYES_00,USER_IN_WHITELIST autolearn=ham version=2.63 cc: freebsd-current@freebsd.org cc: scott@uk.freebsd.org cc: freebsd-mobile@freebsd.org Subject: Re[2]: Modem + Network in Xircom cards, and maybe others X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 May 2004 14:25:26 -0000 On 02/05/2004 at 9:14 M. Warner Losh wrote: >: sio4: 118 more interrupt-level buffer overflows (total 118) >: sio4: 162 more interrupt-level buffer overflows (total 280) > >That may be due to the MFC interrupt issue that I talked about. But >it could be something else... I have beeen looking: ==== sio%d: silo overflow. Problem in the interrupt handler. sio%d: interrupt-level buffer overflow. Problem in the bottom half of the driver. sio%d: tty-level buffer overflow. Problem in the application. Input has arrived faster than the given module could process it and some has been lost. ==== Not sure about how to debug this, problem seems to be in the sio driver. It could not be 100% compatible with serial in Xircom :\ Regards, Carlos Velasco