From mboxrd@z Thu Jan 1 00:00:00 1970 From: Len Brown Subject: Re: [PATCH 2/2] x86: Enable monitor/mwait on Intel if BIOS hasn't already Date: Wed, 03 Aug 2011 15:17:59 -0400 (EDT) Message-ID: References: <5bec80947da3fb72f2f18fbe6d924a69f83fbed9.1312386029.git.luto@mit.edu> Mime-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="8323328-18042863-1312399079=:22067" Return-path: Received: from vms173011pub.verizon.net ([206.46.173.11]:63076 "EHLO vms173011pub.verizon.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754948Ab1HCTSN (ORCPT ); Wed, 3 Aug 2011 15:18:13 -0400 In-reply-to: Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: Andrew Lutomirski Cc: x86@kernel.org, linux-kernel@vger.kernel.org, Fenghua Yu , linux-acpi@vger.kernel.org This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --8323328-18042863-1312399079=:22067 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT > >> What machine has this BIOS bug, and are you running > >> the latest version of the BIOS? > > > > Intel DQ67SW, version SWQ6710H.86A.0051.2011.0413.1154.  This is not > > quite up-to-date -- I'll test a newer BIOS. > > SWQ6710H.86A.0053.2011.0615.1535 has the same problem. It fixed ASPM, though :) > > Should I redo the patch with a printk to warn about the firmware bug? I would hope that a patch that _only_ prints [Firmware bug] should be enough. This isn't the kind of workaround that we should really have to carry in the kernel. This is still a very new platform, and my guess is that they are actively updating the BIOS as we speak. I'll see if I can figure out who to talk to in order to make sure of that:-) thanks, Len Brown, Intel Open Source Technology Center --8323328-18042863-1312399079=:22067--