From owner-freebsd-stable@FreeBSD.ORG Wed Sep 8 09:41:05 2010 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7D5AB10656CC for ; Wed, 8 Sep 2010 09:41:05 +0000 (UTC) (envelope-from bsd@lordcow.org) Received: from lordcow.org (lordcow.org [41.203.5.188]) by mx1.freebsd.org (Postfix) with ESMTP id A482D8FC18 for ; Wed, 8 Sep 2010 09:41:04 +0000 (UTC) Received: from lordcow.org (localhost [127.0.0.1]) by lordcow.org (8.14.4/8.14.4) with ESMTP id o889eute075636 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO) for ; Wed, 8 Sep 2010 11:40:56 +0200 (SAST) (envelope-from lordcow@lordcow.org) Received: (from lordcow@localhost) by lordcow.org (8.14.4/8.14.4/Submit) id o889epRG075635 for stable@freebsd.org; Wed, 8 Sep 2010 11:40:51 +0200 (SAST) (envelope-from lordcow) Date: Wed, 8 Sep 2010 11:40:50 +0200 From: Gareth de Vaux To: stable@freebsd.org Message-ID: <20100908094050.GA73841@lordcow.org> References: <20100906155350.GA50151@lordcow.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED autolearn=unavailable version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on lordcow.org Cc: Subject: Re: MSIX failure X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Sep 2010 09:41:05 -0000 On Tue 2010-09-07 (13:25), Jack Vogel wrote: > I've looked at the code, this message was misleading, what really happens > is that the driver fails to be able to setup either MSIX OR MSI, when this > happens it will fall back and use a Legacy interrupt, so its non-fatal and > the device should work anyway. > > The only real reason you should see this is a) you used sysctl and turned > msi and msix off, or b) a real hardware problem in the chipset has caused > the failure. All devices em drives (as opposed to lem) are PCI Express and > so by definition they have MSI and MSIX available. Ok I think I got my cards mixed up - in my original mail em1 is the PCI card and em0 is the onboard, sorry. I guessed the numbering may not have been as expected while trying to fix the issue, but I might not have fully tested this at the time. So here's the situation after looking through older kernel logs: I installed 8.0-RELEASE, the onboard card didn't work - the kernel didn't even pick it up, and ifconfig only showed the lo0 device. I added the PCI Intel(R) PRO/1000 GT card (Gigabit Ethernet Controller (Copper) rev 5 (82541PI)) - this worked and came up as em0. Last week I moved to -STABLE, GENERIC kernel. The kernel now detects both cards, with the kernel messages in my original mail. Whether either works I'm not completely sure, I'll need to get to the machine physically and switch cables/cards/configurations first. I didn't turn off msi/msix with sysctl (except when debugging in my original mail).