From owner-freebsd-current@FreeBSD.ORG Thu Nov 24 01:57:11 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4C96B16A422 for ; Thu, 24 Nov 2005 01:57:11 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id EE00443D95 for ; Thu, 24 Nov 2005 01:56:16 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id jAO1uEfl040352; Wed, 23 Nov 2005 18:56:14 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <43851DBF.9060702@samsco.org> Date: Wed, 23 Nov 2005 18:56:15 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050615 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Darren Pilgrim References: <000401c5f099$f1ae1f30$642a15ac@smiley> In-Reply-To: <000401c5f099$f1ae1f30$642a15ac@smiley> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: freebsd-current@freebsd.org Subject: Re: em interrupt storm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Nov 2005 01:57:11 -0000 Darren Pilgrim wrote: > From: Scott Long [mailto:scottl@samsco.org] > >>Darren Pilgrim wrote: >> >>>Until this gets "fixed" in FreeBSD, what should those of us who are >>>effectively stuck with this hardware do to avoid the problem? >> >>What I've done is vacated the use of irq16 on my machines by disabling >>things like usb and if_em. > > > Do the devices have to be really turned off (meaning disabled in the BIOS) > or do I just not load the corresponding driver? I think that either works. > > If nothing is using irq16, does the aliasing not occur or does it just > become transparent to FreeBSD? > > If no drivers request a particular interrupt vector, then it gets masked. The chipset probably still tries to deliver the interrupt, but it never makes it to the CPU and thus is transparent. Scott