From owner-freebsd-hackers@FreeBSD.ORG Mon Feb 19 17:22:42 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9502E16A870 for ; Mon, 19 Feb 2007 17:22:42 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 48F5D13C461 for ; Mon, 19 Feb 2007 17:22:42 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.13.4/8.13.4) with ESMTP id l1JHJh8N066733; Mon, 19 Feb 2007 10:19:43 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Mon, 19 Feb 2007 10:20:31 -0700 (MST) Message-Id: <20070219.102031.87764872.imp@bsdimp.com> To: dr2867@pacbell.net From: "M. Warner Losh" In-Reply-To: <45D57B29.2050408@pacbell.net> References: <45D2C7F8.9050302@pacbell.net> <20070215081426.GH862@turion.vk2pj.dyndns.org> <45D57B29.2050408@pacbell.net> X-Mailer: Mew version 4.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Mon, 19 Feb 2007 10:19:44 -0700 (MST) Cc: freebsd-hackers@freebsd.org Subject: Re: PING: Someone on the core team. (Modem Problem) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Feb 2007 17:22:42 -0000 In message: <45D57B29.2050408@pacbell.net> Daniel Rudy writes: : At about the time of 2/15/2007 12:14 AM, Peter Jeremy stated the following: : > On 2007-Feb-14 00:27:36 -0800, Daniel Rudy wrote: : >> Changing the slot did help. I moved it from slot 3 to slot 1. But, now : >> it's dropping characters with a port speed of 57600, and I am also : >> getting irq overrun errors from the kernel too now. : > : > This is not good. Interrupt latency is a bit of a sore point but the : > FIFO trigger level is 8 bytes so getting SILO overflows implies a : > latency of >1.38msec. Does sio4 report as [FAST] in the dmesg? : : No, it does not report as fast. I changed the /boot/device.hints file : and commented out all the sio devices, since all the serial ports on the : system are disabled anyways. This is the only one that is up and running. : : Here is the verbose dmesg from a reboot that I did just now: : : sio0: Reserved 0x100 bytes for rid 0x14 type 4 at 0xd400 : sio0: configured irq 17 not in bitmap of probed irqs 0 : sio0: port may not be enabled : sio0: irq maps: 0xcb9 0xcb9 0xcb9 0xcb9 : sio0: port : 0xd400-0xd4ff,0xd800-0xd8ff,0xdc00-0xdc07 mem 0xeb105000-0xeb1050ff : irq 17 at device 9.0 on pci0 : sio0: type 16550A : : What I don't understand is why it keeps saying that "configured irq 17 : not in bitmap of probed irqs 0"... What exactly does that mean? IRQ 17 was configured for the sio device. The sio probe provokes an interrupt and then reads the interrupt mask. When it read it, the mask was '0' meaning nothing was interrupting... Warner