| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <CAObL_7FNa20Hsd0v-hs1vz=ejnkdaT+Yr=wwM681GbZJiuLkMQ@mail.gmail.com> Date: Wed, 3 Aug 2011 12:42:13 -0400 From: Andrew Lutomirski <luto@....edu> To: Len Brown <lenb@...nel.org> Cc: x86@...nel.org, linux-kernel@...r.kernel.org, Fenghua Yu <fenghua.yu@...el.com>, linux-acpi@...r.kernel.org Subject: Re: [PATCH 2/2] x86: Enable monitor/mwait on Intel if BIOS hasn't already On Wed, Aug 3, 2011 at 12:22 PM, Andrew Lutomirski <luto@....edu> wrote: > On Wed, Aug 3, 2011 at 12:15 PM, Len Brown <lenb@...nel.org> wrote: >> On Wed, 3 Aug 2011, Andy Lutomirski wrote: >> >>> I have a Sandy Bridge machine with an Intel BIOS that enables >>> monitor/mwait on all but the boot CPU. With this patch, intel_idle >>> works. >> >> 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? --Andy > > (Enabling monitor/mwait on some but not all CPUs is obnoxious, too. I > think it's just dumb luck that Linux notices at all and doesn't > crash.) > > --Andy > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists