From owner-freebsd-hackers@FreeBSD.ORG Wed Feb 14 08:23:26 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 E8FA416A400 for ; Wed, 14 Feb 2007 08:23:26 +0000 (UTC) (envelope-from dr2867@pacbell.net) Received: from smtp106.sbc.mail.re2.yahoo.com (smtp106.sbc.mail.re2.yahoo.com [68.142.229.99]) by mx1.freebsd.org (Postfix) with SMTP id 9F31A13C441 for ; Wed, 14 Feb 2007 08:23:26 +0000 (UTC) (envelope-from dr2867@pacbell.net) Received: (qmail 58786 invoked from network); 14 Feb 2007 08:23:22 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=pacbell.net; h=Received:X-YMail-OSG:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=aLZYpK/lsAzDv9H+1Qtnbb7PyGWcdXL2qUZUPj2QXBGqDaMutKGEYUbYFIDudrWZpo7mciLaiWgT6Jldds/URBHv1ITM/SaSf3VtkXFzMgRV8ecuOP9UEwoeUvzlc93bqinn3iBjFDedugO6yAeMKeN1feuFkfKdxjiyT+YwNxg= ; Received: from unknown (HELO ?192.168.0.190?) (dr2867.business@pacbell.net@71.146.10.137 with plain) by smtp106.sbc.mail.re2.yahoo.com with SMTP; 14 Feb 2007 08:23:22 -0000 X-YMail-OSG: qzv4fLcVM1nMiN8rEfBq2MtxbQPDaF6ZnMffQRs8UVdI3h1cvjvXF7vK2zTWa2y6Rc6bC8ganh603qpuIIAVeIe4F_06Ln._C3CKHDxWThwNRdDxKfo2zJgLLsSzet4jazAE4GcA9I8WpdA- Message-ID: <45D2C7F8.9050302@pacbell.net> Date: Wed, 14 Feb 2007 00:27:36 -0800 From: Daniel Rudy User-Agent: Mozilla/5.0 (X11R6; UNIX; FreeBSD/i386 6.1-RELEASE-p7; en-US; ja-JP; rv:1.8.0.7) Gecko/20060910 SeaMonkey/1.0.5 MIME-Version: 1.0 To: "M. Warner Losh" References: <45CC2DDF.6040600@pacbell.net> <20070212.234959.-432837120.imp@bsdimp.com> <45D2A48F.1010104@pacbell.net> <20070213.232425.-1929114897.imp@bsdimp.com> In-Reply-To: <20070213.232425.-1929114897.imp@bsdimp.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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: Wed, 14 Feb 2007 08:23:27 -0000 At about the time of 2/13/2007 10:24 PM, M. Warner Losh stated the following: > In message: <45D2A48F.1010104@pacbell.net> > Daniel Rudy writes: > : At about the time of 2/12/2007 10:49 PM, M. Warner Losh stated the > : following: > : > : sio0: configured irq 19 not in bitmap of probed irqs 0 > : > : sio0: port may not be enabled > : > > : > This may be your problem. sio isn't detecting the interrupts > : > happening on this card, it seems, from this dmesg. You may need to > : > use John Baldwin's hacks to force sio to not use fast interrupts. > : > This makes it possible to share it with non-fast interrupt sources. > : > Please let me know if you need these patches. > : > : I'm working on changing the hardware around and moving the modem to a > : different PCI slot to see if that makes a difference. The system is > : reinstalling right now on the machine (I tried to install Linux but it > : failed...miserably). > > OK. Please let me know if you need any additional help. Are the sis > cards add-in cards, or on the motherboard? > > Warner > 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 actually much better than I had before. With a port speed of 2400, I do not drop characters. Here's the message that I got: sio4: 2374 more interrupt-level buffer overflows (total 2374) test# vmstat -i interrupt total rate irq1: atkbd0 6 0 irq6: fdc0 10 0 irq14: ata0 1120 1 irq15: ata1 47 0 irq17: sio4 415 0 irq19: sis0 sis2 970 1 cpu0: timer 1764263 1998 Total 1766831 2000 test# >From what I can tell, PCI slot 3 and sis0 on the mainboard are both tied to irq 19, which probably was the whole problem. But now I'm having an irq latency problem. This is progressing well though. -- Daniel Rudy