From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 6 12:28:21 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 17E9016A401 for ; Fri, 6 Apr 2007 12:28:21 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id D763313C45A for ; Fri, 6 Apr 2007 12:28:20 +0000 (UTC) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smarthost1.sentex.ca (8.13.8/8.13.8) with ESMTP id l36CSKRb087246; Fri, 6 Apr 2007 08:28:20 -0400 (EDT) (envelope-from mike@sentex.net) Received: from mdt-xp.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.13.8/8.13.3) with ESMTP id l36CSJ8Z064543 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 6 Apr 2007 08:28:19 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <200704061228.l36CSJ8Z064543@lava.sentex.ca> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Fri, 06 Apr 2007 08:28:23 -0400 To: Volker From: Mike Tancsa In-Reply-To: <46163987.4010409@vwsoft.com> References: <7.1.0.9.0.20070405163059.16b8a220@sentex.net> <200704061130.l36BUtjW064328@lava.sentex.ca> <46163987.4010409@vwsoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Cc: freebsd-hackers@freebsd.org Subject: Re: Re: fixing IRQ storms 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: Fri, 06 Apr 2007 12:28:21 -0000 At 08:13 AM 4/6/2007, Volker wrote: >Mike, > >have a look at GNAT: http://www.freebsd.org/cgi/query-pr.cgi?pr=51982 > >You need to patch your kernel sources a bit (all info in the PR) and >your silo overflows will be gone. I've done that to get a Merlin >U630 working (w/o patching sio.c the card was almost unusable). Hi, Thanks for the note. Actually, I have done this in the past (I am even in the above PR :)), but I had found using the UART driver instead of sio was better for working around such issues on the whole. The overflow rate is so high in the case, even increasing the ticks by 10 doesnt seem to fix the issue. It seems to reduce the overflows a bit, but nowhere nearly enough sio2: 108 more interrupt-level buffer overflows (total 108) sio2: 81 more interrupt-level buffer overflows (total 189) sio2: 108 more interrupt-level buffer overflows (total 297) sio2: 81 more interrupt-level buffer overflows (total 378) sio2: 33 more interrupt-level buffer overflows (total 411) sio2: 76 more interrupt-level buffer overflows (total 487) With the uart driver, I am able to talk to the modem OK, but the cpu is really high dealing with all those interrupts. I was hoping I could just tell the card to use a different interrupt like 5 which is available, but I dont know how to do that, or if its even possible. ---Mike