linux-kernel - /ioremap.c:191 __ioremap_caller... Info: mapping multiple BARs. Your kernel is fine.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <5637C395.1040803@gmx.de>
Date:	Mon, 2 Nov 2015 21:12:05 +0100
From:	Toralf Förster <toralf.foerster@....de>
To:	X86 ML <x86@...nel.org>
Cc:	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: /ioremap.c:191 __ioremap_caller... Info: mapping multiple BARs. Your
 kernel is fine.

Starting with 4.1 and still in 4.3-rc7 I get this in dmesg during boot phase at a 64 bit Gentoo Linux at a Lenovo T440s:


------------[ cut here ]------------
WARNING: CPU: 1 PID: 1 at arch/x86/mm/ioremap.c:191 __ioremap_caller+0x233/0x380()
Info: mapping multiple BARs. Your kernel is fine.
Modules linked in:

CPU: 1 PID: 1 Comm: swapper/0 Not tainted 4.1.7-hardened-r1 #1
Hardware name: LENOVO 20AQCTO1WW/20AQCTO1WW, BIOS GJET83WW (2.33 ) 03/09/2015
 ffffffff810e9f76 0000000000000000 ffffffff817d2f95 ffffc9000001baf8
 ffffffff815cb8b5 0000000000002b2b ffffc9000001bb48 ffffc9000001bb38
 ffffffff8106265a ffffc9000001bb78 ffffffff817d2f95 00000000000000bf
Call Trace:
 [<ffffffff810e9f76>] ? print_modules+0x76/0xe0
 [<ffffffff815cb8b5>] dump_stack+0x45/0x5d
 [<ffffffff8106265a>] warn_slowpath_common+0x8a/0xd0
 [<ffffffff810626fa>] warn_slowpath_fmt+0x5a/0x70
 [<ffffffff8104e633>] __ioremap_caller+0x233/0x380
 [<ffffffff8102b51d>] ? snb_uncore_imc_init_box+0x6d/0xa0
 [<ffffffff8104e7a6>] ioremap_nocache+0x26/0x40
 [<ffffffff8102b51d>] snb_uncore_imc_init_box+0x6d/0xa0
 [<ffffffff810296ad>] uncore_pci_probe+0xdd/0x200
 [<ffffffff8139d8c8>] pci_device_probe+0xa8/0x110
 [<ffffffff81434406>] driver_probe_device+0x176/0x340
 [<ffffffff814346db>] __driver_attach+0xab/0xb0
 [<ffffffff81434630>] ? __device_attach+0x60/0x60
 [<ffffffff81431e63>] bus_for_each_dev+0x83/0xd0
 [<ffffffff81433d96>] driver_attach+0x26/0x40
 [<ffffffff814339d0>] bus_add_driver+0x170/0x220
 [<ffffffff81434f44>] driver_register+0x64/0xf0
 [<ffffffff8139bcce>] __pci_register_driver+0x6e/0x80
 [<ffffffff81c2326b>] ? uncore_cpu_setup+0x33/0x33
 [<ffffffff81c233ae>] intel_uncore_init+0x143/0x473
 [<ffffffff81c2326b>] ? uncore_cpu_setup+0x33/0x33
 [<ffffffff810003a4>] do_one_initcall+0x94/0x1b0
 [<ffffffff81c15af6>] kernel_init_freeable+0x1ba/0x2b2
 [<ffffffff815c6440>] ? rest_init+0x80/0x80
 [<ffffffff815c644e>] kernel_init+0xe/0x100
 [<ffffffff815d2a3e>] ret_from_fork+0x3e/0x70
 [<ffffffff815c6440>] ? rest_init+0x80/0x80
---[ end trace 61b2adc0dcfc0e9b ]---


Should I worry about that ?
-- 
Toralf, pgp key: C4EACDDE 0076E94E
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/