Arch Linux

doupod

Member

Registered: 2012-09-06

Posts: 76

[SOLVED] Kernel error in early boot

Hi,

I have this output in journalctl during early boot:

févr. 09 15:58:46 Phyks-laptop kernel: resource sanity check: requesting [mem 0xfed10000-0xfed15fff], which spans more than pnp 00:01 [mem 0xfed10000-0xfed13fff]
févr. 09 15:58:46 Phyks-laptop kernel: ------------[ cut here ]------------
févr. 09 15:58:46 Phyks-laptop kernel: WARNING: CPU: 2 PID: 1 at arch/x86/mm/ioremap.c:198 __ioremap_caller+0x234/0x390()
févr. 09 15:58:46 Phyks-laptop kernel: Info: mapping multiple BARs. Your kernel is fine.
févr. 09 15:58:46 Phyks-laptop kernel: Modules linked in:
févr. 09 15:58:46 Phyks-laptop kernel:
févr. 09 15:58:46 Phyks-laptop kernel: CPU: 2 PID: 1 Comm: swapper/0 Not tainted 4.4.1-2-ARCH #1
févr. 09 15:58:46 Phyks-laptop kernel: Hardware name: LENOVO 20B6CTO1WW/20B6CTO1WW, BIOS GJET79WW (2.29 ) 09/03/2014
févr. 09 15:58:46 Phyks-laptop kernel:  0000000000000000 00000000ffacdb04 ffff88011a767b38 ffffffff812c7f39
févr. 09 15:58:46 Phyks-laptop kernel:  ffff88011a767b80 ffff88011a767b70 ffffffff810765b2 00000000fed10000
févr. 09 15:58:46 Phyks-laptop kernel:  ffffc90000778000 0000000000006000 0000000000000000 ffff88011a1d1180
févr. 09 15:58:46 Phyks-laptop kernel: Call Trace:
févr. 09 15:58:46 Phyks-laptop kernel:  [<ffffffff812c7f39>] dump_stack+0x4b/0x72
févr. 09 15:58:46 Phyks-laptop kernel:  [<ffffffff810765b2>] warn_slowpath_common+0x82/0xc0
févr. 09 15:58:46 Phyks-laptop kernel:  [<ffffffff8107664c>] warn_slowpath_fmt+0x5c/0x80
févr. 09 15:58:46 Phyks-laptop kernel:  [<ffffffff8107cc27>] ? iomem_map_sanity_check+0x97/0xd0
févr. 09 15:58:46 Phyks-laptop kernel:  [<ffffffff81064a84>] __ioremap_caller+0x234/0x390
févr. 09 15:58:46 Phyks-laptop kernel:  [<ffffffff81064bf7>] ioremap_nocache+0x17/0x20
févr. 09 15:58:46 Phyks-laptop kernel:  [<ffffffff8103b4d9>] snb_uncore_imc_init_box+0x79/0xb0
févr. 09 15:58:46 Phyks-laptop kernel:  [<ffffffff8103a1bb>] uncore_pci_probe+0xcb/0x200
févr. 09 15:58:46 Phyks-laptop kernel:  [<ffffffff8130d685>] local_pci_probe+0x45/0xa0
févr. 09 15:58:46 Phyks-laptop kernel:  [<ffffffff8130d5d0>] ? pci_match_device+0xe0/0x110
févr. 09 15:58:46 Phyks-laptop kernel:  [<ffffffff8130e823>] pci_device_probe+0x103/0x150
févr. 09 15:58:46 Phyks-laptop kernel:  [<ffffffff813eb652>] driver_probe_device+0x222/0x4a0
févr. 09 15:58:46 Phyks-laptop kernel:  [<ffffffff813eb954>] __driver_attach+0x84/0x90
févr. 09 15:58:46 Phyks-laptop kernel:  [<ffffffff813eb8d0>] ? driver_probe_device+0x4a0/0x4a0
févr. 09 15:58:46 Phyks-laptop kernel:  [<ffffffff813e928c>] bus_for_each_dev+0x6c/0xc0
févr. 09 15:58:46 Phyks-laptop kernel:  [<ffffffff813eae0e>] driver_attach+0x1e/0x20
févr. 09 15:58:46 Phyks-laptop kernel:  [<ffffffff813ea95b>] bus_add_driver+0x1eb/0x280
févr. 09 15:58:46 Phyks-laptop kernel:  [<ffffffff819164ea>] ? uncore_types_exit+0x26/0x26
févr. 09 15:58:46 Phyks-laptop kernel:  [<ffffffff813ec260>] driver_register+0x60/0xe0
févr. 09 15:58:46 Phyks-laptop kernel:  [<ffffffff8130ce5c>] __pci_register_driver+0x4c/0x50
févr. 09 15:58:46 Phyks-laptop kernel:  [<ffffffff819165cc>] intel_uncore_init+0xe2/0x2df
févr. 09 15:58:46 Phyks-laptop kernel:  [<ffffffff819164ea>] ? uncore_types_exit+0x26/0x26
févr. 09 15:58:46 Phyks-laptop kernel:  [<ffffffff81002123>] do_one_initcall+0xb3/0x200
févr. 09 15:58:46 Phyks-laptop kernel:  [<ffffffff81093645>] ? parse_args+0x295/0x4b0
févr. 09 15:58:46 Phyks-laptop kernel:  [<ffffffff819061a5>] kernel_init_freeable+0x171/0x210
févr. 09 15:58:46 Phyks-laptop kernel:  [<ffffffff815858d0>] ? rest_init+0x90/0x90
févr. 09 15:58:46 Phyks-laptop kernel:  [<ffffffff815858de>] kernel_init+0xe/0xe0
févr. 09 15:58:46 Phyks-laptop kernel:  [<ffffffff81591e8f>] ret_from_fork+0x3f/0x70
févr. 09 15:58:46 Phyks-laptop kernel:  [<ffffffff815858d0>] ? rest_init+0x90/0x90
févr. 09 15:58:46 Phyks-laptop kernel: ---[ end trace 77093d056d231a59 ]---

Everything is working fine, and the INFO message tends to make me think it can be safely ignored. However, is there something special that could be done about it? Should I report it upstream?

Thanks

Last edited by doupod (2016-02-09 16:16:51)

ewaller

Administrator

From: Pasadena, CA

Registered: 2009-07-13

Posts: 20,654

Re: [SOLVED] Kernel error in early boot

You could try dropping a note to Lenovo and tell them that their BIOS is buggy and they need to fix it.  Good luck with that.
You might check to see if they have updated firmware for your laptop.

This looks like yet another workaround that the kernel folk have had to implement to get around hopelessly buggy hardware that is "Good Enough" because it is able to boot a toy operating system from one particular company.

---

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way

doupod

Member

Registered: 2012-09-06

Posts: 76

Re: [SOLVED] Kernel error in early boot

Ok. I have indeed some BIOS updates to do, I will see if it solves it. Else, I will just forget about it.

Thanks