Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755167AbXL1AVZ (ORCPT ); Thu, 27 Dec 2007 19:21:25 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755641AbXL1ASp (ORCPT ); Thu, 27 Dec 2007 19:18:45 -0500 Received: from idcmail-mo1so.shaw.ca ([24.71.223.10]:52439 "EHLO pd3mo3so.prod.shaw.ca" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755895AbXL1ASo (ORCPT ); Thu, 27 Dec 2007 19:18:44 -0500 Date: Thu, 27 Dec 2007 18:18:23 -0600 From: Robert Hancock Subject: Re: [Patch v2] Make PCI extended config space (MMCONFIG) a driver opt-in In-reply-to: To: Linus Torvalds Cc: Jeff Garzik , Arjan van de Ven , linux-kernel@vger.kernel.org, gregkh@suse.de, linux-pci , Benjamin Herrenschmidt , Martin Mares , Matthew Wilcox Message-id: <477440CF.1090807@shaw.ca> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7bit References: <4773EBB4.2020805@shaw.ca> User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1397 Lines: 38 Linus Torvalds wrote: > But as mentioned, there were other reports too of the exact same bug (with > different PCI devices, but the same "vendor == 0001" bogosity). > > Googling for > > lspci "Unknown device 0001:" mmconfig > > shows reports like these: > > http://lkml.org/lkml/2007/10/29/500 > http://madwifi.org/ticket/1587 > http://www.nvnews.net/vbulletin/showthread.php?t=103271 > http://naoya.g.hatena.ne.jp/naoya/20070529/1180436756 > http://bbs.archlinux.org/viewtopic.php?id=34321 > ... > > which all seem to be due to this same bug with different cards (but the > common theme seems to be an ATI northbridge). This isn't an example of a per-device breakage, though. It only shows up on some devices, but the cause is apparently the chipset. Those devices work fine on other boards. As mentioned later, it appears that CRS stuff might be related to this problem, but if it couldn't be fixed, I think the only sane solution would be to blacklist MMCONFIG support on that chipset. -- Robert Hancock Saskatoon, SK, Canada To email, remove "nospam" from hancockr@nospamshaw.ca Home Page: http://www.roberthancock.com/ -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/