Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759095AbXLLVNc (ORCPT ); Wed, 12 Dec 2007 16:13:32 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754059AbXLLVNJ (ORCPT ); Wed, 12 Dec 2007 16:13:09 -0500 Received: from terminus.zytor.com ([198.137.202.10]:48865 "EHLO terminus.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752248AbXLLVNG (ORCPT ); Wed, 12 Dec 2007 16:13:06 -0500 Message-ID: <47604EA4.50504@zytor.com> Date: Wed, 12 Dec 2007 13:12:04 -0800 From: "H. Peter Anvin" User-Agent: Thunderbird 2.0.0.9 (X11/20071115) MIME-Version: 1.0 To: Alan Cox CC: Rene Herman , "David P. Reed" , Pavel Machek , Andi Kleen , "linux-os (Dick Johnson)" , David Newall , Paul Rolland , Krzysztof Halasa , linux-kernel@vger.kernel.org, Thomas Gleixner , Ingo Molnar , rol@witbe.net Subject: Re: More info on port 80 symptoms on MCP51 machine. References: <475DE6F4.80702@zytor.com> <475DEB23.1000304@davidnewall.com> <20071211084059.3d03e11d@tux.DEF.witbe.net> <475E5D4B.8020101@keyaccess.nl> <475E7DC2.4060509@davidnewall.com> <475E8D91.20201@keyaccess.nl> <475E95A3.3070801@davidnewall.com> <20071211163017.GD16750@one.firstfloor.org> <475EBFBA.6090301@keyaccess.nl> <20071211191649.GB3437@elf.ucw.cz> <475EEC75.80609@keyaccess.nl> <47603F66.3070108@reed.com> <476043DA.5000602@keyaccess.nl> <47604B71.7090902@keyaccess.nl> <20071212210143.48721a41@the-village.bc.nu> In-Reply-To: <20071212210143.48721a41@the-village.bc.nu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1176 Lines: 28 Alan Cox wrote: > On Wed, 12 Dec 2007 21:58:25 +0100 > Rene Herman wrote: > >> On 12-12-07 21:26, Rene Herman wrote: >> >>> On 12-12-07 21:07, David P. Reed wrote: >>>> Someone might have an in to nVidia to clarify this, since I don't. In >>>> any case, the udelay(2) approach seems to be a safe fix for this machine. >> By the way, _does_ anyone have a contact at nVidia who could clarify? Alan >> maybe? I'm quite curious what they did... > > I don't. Nvidia are not the most open bunch of people on the planet. This > doesn't appear to be a chipset bug anyway but a firmware one (other > systems with the same chipset work just fine). > > The laptop maker might therefore be a better starting point. One wonders if it does some SMM trick to capture port 0x80 writes and attempt to haul them off for debugging; it almost sounds like some kind of debugging code got let out into the field. -hpa -- 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/