On Thu, Jan 5, 2012 at 9:19 AM, Denis 'GNUtoo' Carikli GNUtoo@no-log.org wrote:
Hi, is it normal that TOM2 is 0 on the M4A785T-M mainboard?
Here are the logs from coreboot:
Sysmem TOM = 0_80000000 Sysmem TOM2 = 0_0 [...] Setting fixed MTRRs(0-88) type: UC Setting fixed MTRRs(0-16) Type: WB, RdMEM, WrMEM Setting fixed MTRRs(24-88) Type: WB, RdMEM, WrMEM DONE fixed MTRRs Setting variable MTRR 0, base: 0MB, range: 2048MB, type WB ADDRESS_MASK_HIGH=0xffff Setting variable MTRR 1, base: 1792MB, range: 256MB, type UC ADDRESS_MASK_HIGH=0xffff DONE variable MTRRs Clear out the extra MTRR's call enable_var_mtrr() Leave x86_setup_var_mtrrs
MTRR check Fixed MTRRs : Enabled Variable MTRRs: Enabled
And from the linux kernel:
[ 0.312294] mtrr: your CPUs had inconsistent variable MTRR settings [ 0.312295] mtrr: probably your BIOS does not setup all CPUs. [ 0.312296] mtrr: corrected configuration. [...] [ 0.317404] ACPI: Executed 2 blocks of module-level executable AML code [ 0.383560] ACPI: Interpreter enabled [ 0.384025] ACPI: (supports S0 S1 S2 S3 S4 S5) [ 0.392816] ACPI: BIOS offers _BFS [ 0.396026] ACPI: If "acpi.bfs=1" improves resume, please notify linux- acpi@vger.kernel.org [ 0.400025] ACPI: Using IOAPIC for interrupt routing [ 0.432761] ACPI: Power Resource [PFN0] (on) [ 0.444081] ACPI: No dock devices found. [ 0.448028] HEST: Table not found. [ 0.451490] PCI: Ignoring host bridge windows from ACPI; if necessary, use "pci=use_crs" and report a bug [ 0.452071] ACPI Error: [TOM2] Namespace lookup failure, AE_NOT_FOUND (20110112/psargs-359) [ 0.460029] ACPI Error: Method parse/execution failed [_SB_.PCI0._CRS] (Node f4426e70), AE_NOT_FOUND (20110112/psparse-536) [ 0.472033] [Firmware Bug]: ACPI: no secondary bus range in _CRS [ 0.476035] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff]) [ 0.480086] ACPI Error: [TOM2] Namespace lookup failure, AE_NOT_FOUND (20110112/psargs-359) [ 0.492031] ACPI Error: Method parse/execution failed [_SB_.PCI0._CRS] (Node f4426e70), AE_NOT_FOUND (20110112/psparse-536)
Denis.
Hi Denis,
This is probably a failure in the mainboard ssdt. The dsdt has the variable for TOM and TOM2 that are in an ssdt. You probably want to add some debug code to acpi_tables.c to see what is getting loaded. It looks like the method used in this mainboard is to copy a compile time ssdt in. A better way is to generate the ssdt. The amd/mahogany or the amd/persimmon acpi_tables.c have examples that generate the ssdt table. You may want to start there.
Marc