From: Len Brown <lenb@kernel.org>
To: Andrew Lutomirski <luto@mit.edu>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
Fenghua Yu <fenghua.yu@intel.com>,
linux-acpi@vger.kernel.org
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) [thread overview]
Message-ID: <alpine.LFD.2.02.1108031514550.22067@x980> (raw)
In-Reply-To: <CAObL_7FNa20Hsd0v-hs1vz=ejnkdaT+Yr=wwM681GbZJiuLkMQ@mail.gmail.com>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 785 bytes --]
> >> 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
next prev parent reply other threads:[~2011-08-03 19:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1312386029.git.luto@mit.edu>
[not found] ` <5bec80947da3fb72f2f18fbe6d924a69f83fbed9.1312386029.git.luto@mit.edu>
2011-08-03 16:15 ` [PATCH 2/2] x86: Enable monitor/mwait on Intel if BIOS hasn't already Len Brown
2011-08-03 16:22 ` Andrew Lutomirski
2011-08-03 16:42 ` Andrew Lutomirski
2011-08-03 19:17 ` Len Brown [this message]
2011-08-04 3:18 ` Andrew Lutomirski
2011-08-04 19:41 ` Matthew Garrett
2011-08-04 21:54 ` Len Brown
2011-08-04 21:56 ` Matthew Garrett
2011-08-05 9:43 ` Ingo Molnar
2011-08-06 11:42 ` Andrew Lutomirski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LFD.2.02.1108031514550.22067@x980 \
--to=lenb@kernel.org \
--cc=fenghua.yu@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@mit.edu \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox