From owner-freebsd-hackers@FreeBSD.ORG  Sat Dec  3 01:43:57 2005
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
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 D16F716A41F;
	Sat,  3 Dec 2005 01:43:57 +0000 (GMT)
	(envelope-from craig@tobuj.gank.org)
Received: from ion.gank.org (ion.gank.org [69.55.238.164])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 62DE443D5E;
	Sat,  3 Dec 2005 01:43:57 +0000 (GMT)
	(envelope-from craig@tobuj.gank.org)
Received: by ion.gank.org (mail, from userid 1001)
	id 21C262BF5B; Fri,  2 Dec 2005 19:43:57 -0600 (CST)
Date: Fri, 2 Dec 2005 19:43:56 -0600
From: Craig Boston <craig@tobuj.gank.org>
To: John Baldwin <jhb@freebsd.org>
Message-ID: <20051203014356.GC22567@nowhere>
References: <20051130020734.GA6577@nowhere>
	<200512011342.19417.jhb@freebsd.org>
	<20051202013146.GA15424@nowhere>
	<200512020817.55769.jhb@freebsd.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200512020817.55769.jhb@freebsd.org>
User-Agent: Mutt/1.4.2.1i
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
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Dec 2005 01:43:58 -0000

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 and 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)

Craig