From owner-freebsd-hackers@FreeBSD.ORG  Tue Dec  6 03:52:32 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 9992D16A41F;
	Tue,  6 Dec 2005 03:52:32 +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 5781043D55;
	Tue,  6 Dec 2005 03:52:32 +0000 (GMT)
	(envelope-from craig@tobuj.gank.org)
Received: by ion.gank.org (mail, from userid 1001)
	id E2F7F2D405; Mon,  5 Dec 2005 21:52:31 -0600 (CST)
Date: Mon, 5 Dec 2005 21:52:28 -0600
From: Craig Boston <craig@tobuj.gank.org>
To: freebsd-hackers@freebsd.org
Message-ID: <20051206035228.GA34979@nowhere>
Mail-Followup-To: Craig Boston <craig@tobuj.gank.org>,
	freebsd-hackers@freebsd.org, John Baldwin <jhb@freebsd.org>
References: <20051130020734.GA6577@nowhere>
	<200512020817.55769.jhb@freebsd.org>
	<20051203005104.GA22567@nowhere>
	<200512031630.59476.jhb@freebsd.org>
	<20051204004131.GA7596@nowhere> <20051206015129.GA34415@nowhere>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20051206015129.GA34415@nowhere>
User-Agent: Mutt/1.4.2.1i
Cc: 
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: Tue, 06 Dec 2005 03:52:32 -0000

On Mon, Dec 05, 2005 at 07:51:29PM -0600, Craig Boston wrote:
> With the ACPI timer disabled (debug.acpi.disabled=timer), the ACPI+APIC
> case now behaves the same as the plain APIC case.  Each IRQ gets
> anywhere from 10,000-500,000 interrupts before it simply stops working.

And to follow up to myself yet again, the i8254 timecounter is also bad
news for APIC.  Switching to it, with or without ACPI, causes things to
stop working really fast.

Just a stab in the dark, but it sounds like there may be something
screwy going on in the interconnect between the I/O APIC and the 8259s.
I'm pretty familiar with old-style (ISA) design, but somewhat fuzzy on
exactly how those two normally coexist, especially when everything is
integrated together on a bridge chip somewhere.

IIRC there used to be some mixed-mode hacks that have been cleaned up in
6.0.  Might Windows still be doing something similar and that's why it
works?

Craig