Leap 42.1 installation: [Firmware Warn]: MTRR: CPU 0: not cleared by BIOS, - logfile-analysis

dilbertone · March 20, 2016, 2:33pm

hello dear OpenSuse-Experts,

running a Notebook with OpenSuse Leap 42.1 - - just installed it yesterday - it runs very well - and i am glad that i have installed opensuse LEAP 42.1

to sume up: the installation went okay - i had no troubles during the installation. But while i start the computer i notice interesting logs
so i wanted to know what do they say …

so i runned journalctl - see below:

**the notebook:
**

Akoya P 6512 15" AMD Athlon X2 P320
CPU: AMD Athlon X2 P320 (Champlain, 2,1 GHz)
Memory: Level-1-/Level-2-/Level-3-Cache / 2 x 128 Kilobyte/2 x 512 Kilobyte/–
Memory: Hyundai SO-DIMM DDR3 (1.066 MHz, CL 7, 2 Dual Channel) 4.096 Megabyte/8.192 Megabyte/3.071 Megabyte (bei 32 Bit)
Chipsatz/BIOS (Version)    AMD 785G/AMI (A16GKAM7.106)
USB, eSATA, Netzwerkbuchse (LAN)


Akoya P 6512 15" OpenSuse Leap 42.1: AMD Athlon X2 P320

the BIOS


    dmidecode -t bios -q
    linux-0f5x:/home/martin #  dmidecode -t bios -q
    BIOS Information
            Vendor: American Megatrends Inc.
            Version: A16GKAM7.106
            Release Date: 07/09/2010
            Address: 0xF0000
            Runtime Size: 64 kB
            ROM Size: 1024 kB
            Characteristics:
                    ISA is supported
                    PCI is supported
                    PNP is supported
                    BIOS is upgradeable
                    BIOS shadowing is allowed
                    ESCD support is available
                    Boot from CD is supported
                    Selectable boot is supported
                    BIOS ROM is socketed
                    EDD is supported
                    5.25"/1.2 MB floppy services are supported (int 13h)
                    3.5"/720 kB floppy services are supported (int 13h)
                    3.5"/2.88 MB floppy services are supported (int 13h)
                    Print screen service is supported (int 5h)
                    8042 keyboard services are supported (int 9h)
                    Serial services are supported (int 14h)
                    Printer services are supported (int 17h)
                    CGA/mono video services are supported (int 10h)
                    ACPI is supported                                                                                                                                                               
                    USB legacy is supported                                                                                                                                                         
                    LS-120 boot is supported                                                                                                                                                        
                    ATAPI Zip drive boot is supported                                                                                                                                               
                    BIOS boot specification is supported                                                                                                                                            
                    Targeted content distribution is supported                                                                                                                                      
            BIOS Revision: 8.15                                                                                                                                                                     
                                                                                                                                                                                                    
    BIOS Language Information                                                                                                                                                                       
            Language Description Format: Long                                                                                                                                                       
            Installable Languages: 1                                                                                                                                                                
                    en|US|iso8859-1                                                                                                                                                                 
            Currently Installed Language: en|US|iso8859-1

The installation went fine - no problem at all.
But i guess that the BIOS is quite very very old:
conclusion - well i guess that i have to update the BIOS -

i run journalctl - to see the full logfiles

see them here: http://pastebin.com/xSGceRwK

see some lines of the logfiles:


t
Mär 19 23:05:49 linux-0f5x kernel: Linux version 4.1.15-8-default (geeko@buildhost) (gcc
Mär 19 23:05:49 linux-0f5x kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-4.1.15-8-defau
Mär 19 23:05:49 linux-0f5x kernel: tseg: 0000000000
Mär 19 23:05:49 linux-0f5x kernel: e820: BIOS-provided physical RAM map:
Mär 19 23:05:49 linux-0f5x kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009e3ff
Mär 19 23:05:49 linux-0f5x kernel: BIOS-e820: [mem 0x000000000009e400-0x000000000009ffff
Mär 19 23:05:49 linux-0f5x kernel: BIOS-e820: [mem 0x00000000000e2000-0x00000000000fffff
Mär 19 23:05:49 linux-0f5x kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000bff9ffff
Mär 19 23:05:49 linux-0f5x kernel: BIOS-e820: [mem 0x00000000bffa0000-0x00000000bffadfff
Mär 19 23:05:49 linux-0f5x kernel: BIOS-e820: [mem 0x00000000bffae000-0x00000000bffdffff
Mär 19 23:05:49 linux-0f5x kernel: BIOS-e820: [mem 0x00000000bffe0000-0x00000000bfffffff
Mär 19 23:05:49 linux-0f5x kernel: BIOS-e820: [mem 0x0000000100000000-0x000000012fffffff
Mär 19 23:05:49 linux-0f5x kernel: NX (Execute Disable) protection: active
Mär 19 23:05:49 linux-0f5x kernel: SMBIOS 2.6 present.
Mär 19 23:05:49 linux-0f5x kernel: DMI: MEDION P651x series/P6512, BIOS A16GKAM7.106 07/
Mär 19 23:05:49 linux-0f5x kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> r
Mär 19 23:05:49 linux-0f5x kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
Mär 19 23:05:49 linux-0f5x kernel: AGP: No AGP bridge found
Mär 19 23:05:49 linux-0f5x kernel: e820: last_pfn = 0x130000 max_arch_pfn = 0x400000000
Mär 19 23:05:49 linux-0f5x kernel: [Firmware Warn]: MTRR: CPU 0: SYSCFG[MtrrFixDramModEn
Mär 19 23:05:49 linux-0f5x kernel: MTRR default type: uncachable
Mär 19 23:05:49 linux-0f5x kernel: MTRR fixed ranges enabled:
Mär 19 23:05:49 linux-0f5x kernel:   00000-9FFFF write-back
Mär 19 23:05:49 linux-0f5x kernel:   A0000-EFFFF uncachable
Mär 19 23:05:49 linux-0f5x kernel:   F0000-FFFFF write-protect
Mär 19 23:05:49 linux-0f5x kernel: MTRR variable ranges enabled:
Mär 19 23:05:49 linux-0f5x kernel:   0 base 000000000000 mask FFFF80000000 write-back
Mär 19 23:05:49 linux-0f5x kernel:   1 base 000080000000 mask FFFFC0000000 write-back
lines 1-34...skipping...
-- Logs begin at Sa 2016-03-19 23:05:49 CET, end at So 2016-03-20 13:58:02 CET. --                                                                                                              
Mär 19 23:05:49 linux-0f5x systemd-journal[117]: Runtime journal is using 8.0M (max allowed 185.0M, trying to leave 277.5M free of 1.7G available → current limit 185.0M).                      
Mär 19 23:05:49 linux-0f5x systemd-journal[117]: Runtime journal is using 8.0M (max allowed 185.0M, trying to leave 277.5M free of 1.7G available → current limit 185.0M).                      
Mär 19 23:05:49 linux-0f5x kernel: Initializing cgroup subsys cpuset                                                                                                                            
Mär 19 23:05:49 linux-0f5x kernel: Initializing cgroup subsys cpu                                                                                                                               
Mär 19 23:05:49 linux-0f5x kernel: Initializing cgroup subsys cpuacct                                                                                                                           
Mär 19 23:05:49 linux-0f5x kernel: Linux version 4.1.15-8-default (geeko@buildhost) (gcc version 4.8.5 (SUSE Linux) ) #1 SMP PREEMPT Wed Jan 20 16:41:00 UTC 2016 (0e3b3ab)                     
Mär 19 23:05:49 linux-0f5x kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-4.1.15-8-default root=UUID=358d55e7-f95d-4dae-8df8-ed362fba114b resume=/dev/disk/by-uuid/d8167a64-d4cd-45d3-9392-752cd
Mär 19 23:05:49 linux-0f5x kernel: tseg: 0000000000                                                                                                                                             
Mär 19 23:05:49 linux-0f5x kernel: e820: BIOS-provided physical RAM map:                                                                                                                        
Mär 19 23:05:49 linux-0f5x kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009e3ff] usable                                                                                                
Mär 19 23:05:49 linux-0f5x kernel: BIOS-e820: [mem 0x000000000009e400-0x000000000009ffff] reserved                                                                                              
Mär 19 23:05:49 linux-0f5x kernel: BIOS-e820: [mem 0x00000000000e2000-0x00000000000fffff] reserved                                                                                              
Mär 19 23:05:49 linux-0f5x kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000bff9ffff] usable                                                                                                
Mär 19 23:05:49 linux-0f5x kernel: BIOS-e820: [mem 0x00000000bffa0000-0x00000000bffadfff] ACPI data                                                                                             
Mär 19 23:05:49 linux-0f5x kernel: BIOS-e820: [mem 0x00000000bffae000-0x00000000bffdffff] ACPI NVS                                                                                              
Mär 19 23:05:49 linux-0f5x kernel: BIOS-e820: [mem 0x00000000bffe0000-0x00000000bfffffff] reserved                                                                                              
Mär 19 23:05:49 linux-0f5x kernel: BIOS-e820: [mem 0x0000000100000000-0x000000012fffffff] usable                                                                                                
Mär 19 23:05:49 linux-0f5x kernel: NX (Execute Disable) protection: active
Mär 19 23:05:49 linux-0f5x kernel: SMBIOS 2.6 present.
Mär 19 23:05:49 linux-0f5x kernel: DMI: MEDION P651x series/P6512, BIOS A16GKAM7.106 07/09/2010
Mär 19 23:05:49 linux-0f5x kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Mär 19 23:05:49 linux-0f5x kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
Mär 19 23:05:49 linux-0f5x kernel: AGP: No AGP bridge found
Mär 19 23:05:49 linux-0f5x kernel: e820: last_pfn = 0x130000 max_arch_pfn = 0x400000000
Mär 19 23:05:49 linux-0f5x kernel: [Firmware Warn]: MTRR: CPU 0: SYSCFG[MtrrFixDramModEn] not cleared by BIOS, clearing this bit
Mär 19 23:05:49 linux-0f5x kernel: MTRR default type: uncachable
Mär 19 23:05:49 linux-0f5x kernel: MTRR fixed ranges enabled:
Mär 19 23:05:49 linux-0f5x kernel:   00000-9FFFF write-back
Mär 19 23:05:49 linux-0f5x kernel:   A0000-EFFFF uncachable
Mär 19 23:05:49 linux-0f5x kernel:   F0000-FFFFF write-protect
Mär 19 23:05:49 linux-0f5x kernel: MTRR variable ranges enabled:
Mär 19 23:05:49 linux-0f5x kernel:   0 base 000000000000 mask FFFF80000000 write-back
Mär 19 23:05:49 linux-0f5x kernel:   1 base 000080000000 mask FFFFC0000000 write-back
Mär 19 23:05:49 linux-0f5x kernel:   2 base 0000C0000000 mask FFFFF0000000 write-back
Mär 19 23:05:49 linux-0f5x kernel:   3 disabled
Mär 19 23:05:49 linux-0f5x kernel:   4 disabled
Mär 19 23:05:49 linux-0f5x kernel:   5 disabled
Mär 19 23:05:49 linux-0f5x kernel:   6 base 0000FFFA0000 mask FFFFFFFE0000 uncachable
Mär 19 23:05:49 linux-0f5x kernel:   7 disabled
Mär 19 23:05:49 linux-0f5x kernel: TOM2: 0000000130000000 aka 4864M
Mär 19 23:05:49 linux-0f5x kernel: PAT configuration [0-7]: WB  WC  UC- UC  WB  WC  UC- UC  
Mär 19 23:05:49 linux-0f5x kernel: e820: update [mem 0xd0000000-0xffffffff] usable ==> reserved
Mär 19 23:05:49 linux-0f5x kernel: e820: last_pfn = 0xbffa0 max_arch_pfn = 0x400000000
Mär 19 23:05:49 linux-0f5x kernel: found SMP MP-table at [mem 0x000ff780-0x000ff78f] mapped at [ffff8800000ff780]
Mär 19 23:05:49 linux-0f5x kernel: Scanning 1 areas for low memory corruption
Mär 19 23:05:49 linux-0f5x kernel: Base memory trampoline at [ffff880000098000] 98000 size 24576
Mär 19 23:05:49 linux-0f5x kernel: Using GB pages for direct mapping
Mär 19 23:05:49 linux-0f5x kernel: init_memory_mapping: [mem 0x00000000-0x000fffff]
Mär 19 23:05:49 linux-0f5x kernel:  [mem 0x00000000-0x000fffff] page 4k
Mär 19 23:05:49 linux-0f5x kernel: BRK [0x0221a000, 0x0221afff] PGTABLE
Mär 19 23:05:49 linux-0f5x kernel: BRK [0x0221b000, 0x0221bfff] PGTABLE

look forward to hear from you

what to do.?

What does this mean -. [Firmware Warn]: MTRR: CPU 0: not cleared by BIOS, - logfile-analysis

greetings

nrickert · March 20, 2016, 3:22pm

I usually ignore all of those messages unless something is going wrong. If everything is working, then ignore them.

It looks as if the kernel is reporting a BIOS flaw – that it failed to clear a bit. On two of my computers, I see notices about BIOS issues on every boot. But everything is working so I don’t worry about it.

When I first acquired one of those computers, the kernel was not reporting problems. And I ran into difficulties. I had to add something to the kernel boot line (I think it was “nolapic”) before it would run properly. Now that the kernel recognized the BIOS issue, it takes care of it and I no longer have to fudge the kernel boot command.

If everything is working as expected, then I suggest that you pay less attention to the bootup messages.

dilbertone · March 20, 2016, 7:35pm

hello dear nrickert

many many thanks for the reply. Thanks for clearing up this issues. I agree.

Thanks for helping me solving this “thread” - issues.

greetings