From owner-freebsd-stable@FreeBSD.ORG  Wed Apr 22 20:32:36 2009
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id D0E411065673
	for <freebsd-stable@freebsd.org>; Wed, 22 Apr 2009 20:32:36 +0000 (UTC)
	(envelope-from marius@alchemy.franken.de)
Received: from alchemy.franken.de (alchemy.franken.de [194.94.249.214])
	by mx1.freebsd.org (Postfix) with ESMTP id 5FD0E8FC0A
	for <freebsd-stable@freebsd.org>; Wed, 22 Apr 2009 20:32:36 +0000 (UTC)
	(envelope-from marius@alchemy.franken.de)
Received: from alchemy.franken.de (localhost [127.0.0.1])
	by alchemy.franken.de (8.14.3/8.14.3/ALCHEMY.FRANKEN.DE) with ESMTP id
	n3MKWXar052808; Wed, 22 Apr 2009 22:32:33 +0200 (CEST)
	(envelope-from marius@alchemy.franken.de)
Received: (from marius@localhost)
	by alchemy.franken.de (8.14.3/8.14.3/Submit) id n3MKWWN3052807;
	Wed, 22 Apr 2009 22:32:32 +0200 (CEST) (envelope-from marius)
Date: Wed, 22 Apr 2009 22:32:32 +0200
From: Marius Strobl <marius@alchemy.franken.de>
To: David Christensen <davidch@broadcom.com>
Message-ID: <20090422203232.GC50221@alchemy.franken.de>
References: <20090420204637.GA1236@mr-happy.com>
	<20090421184924.GA36542@alchemy.franken.de>
	<20090421193129.GA4869@mr-happy.com>
	<20090421195510.GC33994@alchemy.franken.de>
	<20090422150612.GA1231@mr-happy.com>
	<20090422192644.GA52151@alchemy.franken.de>
	<5D267A3F22FD854F8F48B3D2B523819339D9F5A64D@IRVEXCHCCR01.corp.ad.broadcom.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5D267A3F22FD854F8F48B3D2B523819339D9F5A64D@IRVEXCHCCR01.corp.ad.broadcom.com>
User-Agent: Mutt/1.4.2.3i
Cc: Jeff Blank <jb000003@mr-happy.com>,
	"freebsd-stable@freebsd.org" <freebsd-stable@freebsd.org>
Subject: Re: bge problems under 7.2-PRERELEASE
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Apr 2009 20:32:37 -0000

On Wed, Apr 22, 2009 at 01:21:58PM -0700, David Christensen wrote:
> > > > Then update if_bge.c to rev
> > > > 1.198.2.14 and check whether things still work,
> > > 
> > > this causes the problem to resurface.
> > > 
> > 
> > David,
> > 
> > this is the second report that using MSI with a BCM5754/
> > chip=0x167a14e4 results in no interrupts, is there any errata 
> > about this?
> 
> Nope, no errata for MSI on the 5754, nor can I recall any
> MSI problems on any of the PCIe based devices.  Do the 
> systems share a common root complex that might be the source
> of the issue?
> 

This one useses a:
none0@pci0:0:0:0:       class=0x050000 card=0x02f010de chip=0x02f010de rev=0xa2 hdr=0x00
    vendor     = 'Nvidia Corp'
    device     = 'C51 Host Bridge'
    class      = memory
    subclass   = RAM

At least Linux doesn't seem to avoid using MSI with these.
I didn't get any further regarding the other report so far.

Marius