http://bugzilla.kernel.org/show_bug.cgi?id=11541
------- Comment #69 from [email protected] 2009-03-03 03:25 ------- I suggest to change the Linux code to ignore RdMem/WrMem of fixed MTRR registers and not to sync them between CPUs. I've found this old thread http://lkml.org/lkml/2007/4/3/110 as a rationale of introducing the code which is causing the problems described here. From this thread it seems that the problematic system had the SYSCFG[MtrrFixDramModEn] bit set on CPU0 but not on CPU1. Thus the RdMem/WrMem bits were only reported on CPU0. My assumption is that if SYSCFG[MtrrFixDramModEn] is cleared the fixed MTRR contents will not differ on the CPUs. Linux won't try to change the settings on CPU1 and the system boots normally -- hopefully ;-) -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ acpi-bugzilla mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
