Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754313AbXL0Scy (ORCPT ); Thu, 27 Dec 2007 13:32:54 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752250AbXL0Scr (ORCPT ); Thu, 27 Dec 2007 13:32:47 -0500 Received: from cg-p07-fb.rzone.de ([81.169.146.215]:39470 "EHLO cg-p07-fb.rzone.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752105AbXL0Scq (ORCPT ); Thu, 27 Dec 2007 13:32:46 -0500 X-RZG-CLASS-ID: mo07 X-RZG-AUTH: iaL9KxG65sFyH/NRHEm13ZpWIsASIz2sPdozvvFFdQCNetlf Message-ID: <4773EF5C.8090502@tragetaschen.dyndns.org> Date: Thu, 27 Dec 2007 19:30:52 +0100 From: Kai Ruhnau User-Agent: Thunderbird 2.0.0.9 (X11/20071122) MIME-Version: 1.0 To: Robert Hancock CC: Linus Torvalds , Jeff Garzik , Arjan van de Ven , linux-kernel@vger.kernel.org, gregkh@suse.de, linux-pci , Benjamin Herrenschmidt , Martin Mares , Matthew Wilcox Subject: Re: [Patch v2] Make PCI extended config space (MMCONFIG) a driver opt-in References: <4773EBB4.2020805@shaw.ca> In-Reply-To: <4773EBB4.2020805@shaw.ca> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 5831 Lines: 126 Robert Hancock wrote: > Linus Torvalds wrote: >> >> On Thu, 27 Dec 2007, Jeff Garzik wrote: >>> 2) [non-minor] hmmmm. >>> >>> [jgarzik@core ~]$ lspci -n | wc -l >>> 23 >>> >>> So I would have to perform 23 sysfs twiddles, before I could obtain >>> a full and >>> unabridged 'lspci -vvvxxx'? >> >> Or you force it on with "pci=mmconfig" or something at boot-time. >> >> But yes. The *fact* is that MMCONFIG has not just been globally >> broken, but broken on a per-device basis. I don't know why (and quite >> frankly, I doubt anybody does), but the PCI device ID corruption >> happened only for a specific set of devices. >> >> Whether it was a timing issue with particular devices or whether it >> was a timing issue with some particular bridge (and could affect any >> devices behind that bridge), who knows... It almost certainly was >> brought on by a borderline (or broken) northbridge, but it apparently >> only affected specific devices - which makes me suspect that it >> wasn't *entirely* due to just the northbridge, and it was a >> combination of things. > > Pointer to such a report? The only single-device problems I'm aware of > are with some devices within the K8 integrated northbridge, which we > already handle. Other than that, the only non-global problems I'm aware > of are devices behind host bridges which can't receive/handle MMCONFIG > requests, in which case the problem would be bus-wide. That is my computer here. The moment I do not switch off mmconfig my graphics and my network card show up with vendor ID 0001 lspci without mmconfig: 00:00.0 Host bridge: ATI Technologies Inc Unknown device 7930 00:02.0 PCI bridge: ATI Technologies Inc Unknown device 7933 00:06.0 PCI bridge: ATI Technologies Inc Unknown device 7936 00:12.0 SATA controller: ATI Technologies Inc SB600 Non-Raid-5 SATA 00:13.0 USB Controller: ATI Technologies Inc SB600 USB (OHCI0) 00:13.1 USB Controller: ATI Technologies Inc SB600 USB (OHCI1) 00:13.2 USB Controller: ATI Technologies Inc SB600 USB (OHCI2) 00:13.3 USB Controller: ATI Technologies Inc SB600 USB (OHCI3) 00:13.4 USB Controller: ATI Technologies Inc SB600 USB (OHCI4) 00:13.5 USB Controller: ATI Technologies Inc SB600 USB Controller (EHCI) 00:14.0 SMBus: ATI Technologies Inc SB600 SMBus (rev 13) 00:14.1 IDE interface: ATI Technologies Inc SB600 IDE 00:14.2 Audio device: ATI Technologies Inc SB600 Azalia 00:14.3 ISA bridge: ATI Technologies Inc SB600 PCI to LPC Bridge 00:14.4 PCI bridge: ATI Technologies Inc SB600 PCI to PCI Bridge 01:00.0 VGA compatible controller: nVidia Corporation G80 [GeForce 8800 GTS] (rev a2) 02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8056 PCI-E Gigabit Ethernet Controller (rev 12) 03:02.0 FireWire (IEEE 1394): Texas Instruments TSB43AB23 IEEE-1394a-2000 Controller (PHY/Link) My network card with enabled mmconfig: 02:00.0 Ethernet controller: Unknown device 0001:4364 (rev 12) Subsystem: Micro-Star International Co., Ltd. Unknown device 326c Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR-