From owner-freebsd-stable@FreeBSD.ORG Fri Jan 20 17:26:05 2012 Return-Path: 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 00CF11065673; Fri, 20 Jan 2012 17:26:05 +0000 (UTC) (envelope-from mazhe@alkumuna.eu) Received: from smtp1-g21.free.fr (smtp1-g21.free.fr [IPv6:2a01:e0c:1:1599::10]) by mx1.freebsd.org (Postfix) with ESMTP id 945FE8FC16; Fri, 20 Jan 2012 17:26:01 +0000 (UTC) Received: from yggdrasil.alkumuna.eu (unknown [IPv6:2a01:e35:8a74:6e70:232:36ff:fe5c:3a87]) by smtp1-g21.free.fr (Postfix) with ESMTP id 7750F9403F0; Fri, 20 Jan 2012 18:25:56 +0100 (CET) Received: from localhost ([IPv6:2a01:e35:8a74:6e70:224:8cff:fe8a:73b2]) (authenticated bits=0) by yggdrasil.alkumuna.eu (8.14.4/8.14.4) with ESMTP id q0KHPs32036357 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 20 Jan 2012 18:25:55 +0100 (CET) (envelope-from mazhe@alkumuna.eu) Date: Fri, 20 Jan 2012 18:25:52 +0100 From: Matthieu Volat To: John Baldwin Message-Id: <20120120182552.683bba8b.mazhe@alkumuna.eu> In-Reply-To: <201201200928.55558.jhb@freebsd.org> References: <20120120142128.0c6ba578.mazhe@alkumuna.eu> <201201200928.55558.jhb@freebsd.org> X-Mailer: Sylpheed 3.1.2 (GTK+ 2.24.6; amd64-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: mazhe@alkumun, freebsd-stable@freebsd.org Subject: Re: 9.0-Release and Asus P5-NE motherboard 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: Fri, 20 Jan 2012 17:26:05 -0000 On Fri, 20 Jan 2012 09:28:55 -0500 John Baldwin wrote: > On Friday, January 20, 2012 8:21:28 am Matthieu Volat wrote: > > Hello, > > > > For a week, I have been trying to boot the FreeBSD 9 installation media > (usb, cdrom) on a computer with an Asus P5-NE motherboard (amd64, nvidia MCP51 > controller), but the kernel fails to initialize correctly. > > I think the problem is with the nvidia chipset and MSI support. There's not > an easy way to fix it via a tunable unfortunately. You can try hacking > sys/dev/pci/pci.c to disable this code: > > #if defined(__i386__) || defined(__amd64__) || defined(__powerpc__) > /* > * Enable the MSI mapping window for all HyperTransport > * slaves. PCI-PCI bridges have their windows enabled via > * PCIB_MAP_MSI(). > */ > if (cfg->ht.ht_slave != 0 && cfg->ht.ht_msimap != 0 && > !(cfg->ht.ht_msictrl & PCIM_HTCMD_MSI_ENABLE)) { > device_printf(pcib, > "Enabling MSI window for HyperTransport slave at pci%d:%d:%d:%d\n", > cfg->domain, cfg->bus, cfg->slot, cfg->func); > cfg->ht.ht_msictrl |= PCIM_HTCMD_MSI_ENABLE; > WREG(cfg->ht.ht_msimap + PCIR_HT_COMMAND, cfg->ht.ht_msictrl, > 2); > } > #endif > > -- > John Baldwin Thanks, you are absolutely right, I compiled a kernel disabling MSI-X support and it booted. I wonder how this worked previously and not now. From what I see, there is a blacklist to disable unsupported chipsets... Maybe this chipset should be added as a workaround (I wonder if I'm the only one with the problem)... The only references I found about MCP51 and MSI-X () seems to indicates that the chipset should work, but maybe with extra code... I'm willing to test patches & so if somebody wants to have a look. -- Matthieu Volat