From owner-freebsd-hackers@FreeBSD.ORG  Fri Jan 20 15:27:37 2006
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 D66C716A41F
	for <freebsd-hackers@freebsd.org>; Fri, 20 Jan 2006 15:27:37 +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 A349143D45
	for <freebsd-hackers@freebsd.org>; Fri, 20 Jan 2006 15:27:37 +0000 (GMT)
	(envelope-from craig@tobuj.gank.org)
Received: by ion.gank.org (mail, from userid 1001)
	id F38E72AB1B; Fri, 20 Jan 2006 09:27:36 -0600 (CST)
Date: Fri, 20 Jan 2006 09:27:31 -0600
From: Craig Boston <craig@tobuj.gank.org>
To: Scott Long <scottl@samsco.org>
Message-ID: <20060120152731.GA5660@nowhere>
Mail-Followup-To: Craig Boston <craig@tobuj.gank.org>,
	Scott Long <scottl@samsco.org>, freebsd-hackers@freebsd.org
References: <20060120014307.GA3118@nowhere> <43D07273.6030804@samsco.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <43D07273.6030804@samsco.org>
User-Agent: Mutt/1.4.2.1i
Cc: freebsd-hackers@freebsd.org
Subject: Re: Weird PCI interrupt delivery problem (resolution, sort of)
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: Fri, 20 Jan 2006 15:27:38 -0000

On Thu, Jan 19, 2006 at 10:17:39PM -0700, Scott Long wrote:
> This points to a bus coherency problem.  I wonder if your BIOS is
> incorrectly setting the memory region of the apics as cachable.  You'll
> want to bug Baldwin about this.

I CC-ed him on my post since he was working with me on the problem
before.  For some reason the Cc: header got wiped out when it went to
the list (but I checked my server logs and it did deliver a copy of the
message to him).

Craig