northbridge/intel/nehalem: don't set FERR_CAPABILITY on BSP
This capability means: FERR messages are sent out on system detected an unmasked floating point x87 FPU error. Even though this capability is supported on nehalem it doesn't make sense to set it in early stage. This MSR has a core scope which results in an unsync MSR because it's not set on other cores than the BSP. Found-by: BITS Tested-on: lenovo thinkpad x201t Change-Id: Ief3c04f57ac69e7289fbd37dbc3fd239f9098155 Signed-off-by: Alexander Couzens <lynxis@fe80.eu> Reviewed-on: http://review.coreboot.org/8659 Tested-by: build bot (Jenkins) Reviewed-by: Paul Menzel <paulepanter@users.sourceforge.net> Reviewed-by: Patrick Georgi <pgeorgi@google.com>
This commit is contained in:
parent
ed48dfdc4e
commit
b7b83719bf
|
@ -131,11 +131,6 @@ static void early_cpu_init (void)
|
|||
m = rdmsr(MSR_IA32_MISC_ENABLES);
|
||||
m.lo |= 0x10000;
|
||||
wrmsr(MSR_IA32_MISC_ENABLES, m);
|
||||
|
||||
m = rdmsr(0x1f1);
|
||||
m.lo |= 1;
|
||||
wrmsr(0x1f1, m);
|
||||
|
||||
}
|
||||
|
||||
void nehalem_early_initialization(int chipset_type)
|
||||
|
|
Loading…
Reference in New Issue