From owner-freebsd-hackers@FreeBSD.ORG Sat Dec 3 21:35:46 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D85E416A420; Sat, 3 Dec 2005 21:35:46 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id F2AAD43D5E; Sat, 3 Dec 2005 21:35:45 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 3086643 for multiple; Sat, 03 Dec 2005 16:33:47 -0500 Received: from zion.baldwin.cx (zion.baldwin.cx [192.168.0.7]) (authenticated bits=0) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jB3LZemW020949; Sat, 3 Dec 2005 16:35:40 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: Craig Boston Date: Sat, 3 Dec 2005 16:29:19 -0500 User-Agent: KMail/1.8.3 References: <20051130020734.GA6577@nowhere> <200512020817.55769.jhb@freebsd.org> <20051203014356.GC22567@nowhere> In-Reply-To: <20051203014356.GC22567@nowhere> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200512031629.20992.jhb@freebsd.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: freebsd-hackers@freebsd.org, imp@freebsd.org Subject: Re: Weird PCI interrupt delivery 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: Sat, 03 Dec 2005 21:35:47 -0000 On Friday 02 December 2005 08:43 pm, Craig Boston wrote: > On Fri, Dec 02, 2005 at 08:17:53AM -0500, John Baldwin wrote: > > > Argh, this is driving me up the wall. I had a hunch that it was > > > somehow connected to level-triggered interrupts. That seems to not be > > > the case, as upon closer inspection the SCI interrupt (9) gets > > > reprogrammed to level/low. I can read the ACPI status all day long a= nd > > > the count for IRQ 9 goes up and up without freezing... > > > > Interesting. How about IRQ 11 in non-APIC mode, is it programmed to > > level/low? I've seen BIOSes that do very stupid things like have the > > link devices set to level/hi or edge/lo or even edge/hi. A verbose boot > > should tell you if any settings are changed though, and in the APIC case > > you should see the initial defaults as well. > > Added some printfs to i386/isa/atpic.c. At bootup, everything is > programmed by the BIOS to edge/high, except IRQ 11 which is set to > level/low. FreeBSD doesn't seem to be changing that as far as I can > tell. (this is -APIC -ACPI) Ok. =2D-=20 John Baldwin =A0<>< =A0http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" =A0=3D =A0http://www.FreeBSD.org