From: "Toralf Förster" <toralf.foerster@gmx.de>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: new dmesg warning in 4.1.3: WARNING: CPU: 1 PID: 1 at arch/x86/mm/ioremap.c:202 __ioremap_caller+0x26f/0x3b0()
Date: Mon, 27 Jul 2015 14:09:54 +0200 [thread overview]
Message-ID: <55B61F92.4030500@gmx.de> (raw)
At a Gentoo Linux hardened amd64 desktop I got this trace after upgrading from 4.0.8 :
Jul 27 14:01:13 t44 kernel: [ 0.344444] ------------[ cut here ]------------
Jul 27 14:01:13 t44 kernel: [ 0.344453] WARNING: CPU: 1 PID: 1 at arch/x86/mm/ioremap.c:202 __ioremap_caller+0x26f/0x3b0()
Jul 27 14:01:13 t44 kernel: [ 0.344459] Info: mapping multiple BARs. Your kernel is fine.
Jul 27 14:01:13 t44 kernel: [ 0.344462] Modules linked in:
Jul 27 14:01:13 t44 kernel: [ 0.344470] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 4.1.3-hardened #1
Jul 27 14:01:13 t44 kernel: [ 0.344475] Hardware name: LENOVO 20AQCTO1WW/20AQCTO1WW, BIOS GJET83WW (2.33 ) 03/09/2015
Jul 27 14:01:13 t44 kernel: [ 0.344481] ffffffff810e2c33 0000000000000000 ffffffff817b4418 ffffc9000001bae8
Jul 27 14:01:13 t44 kernel: [ 0.344490] ffffffff815b239d 0000000000002b2b ffffc9000001bb38 ffffc9000001bb28
Jul 27 14:01:13 t44 kernel: [ 0.344498] ffffffff8105e097 ffffc9000001bb68 ffffffff817b4418 00000000000000ca
Jul 27 14:01:13 t44 kernel: [ 0.344506] Call Trace:
Jul 27 14:01:13 t44 kernel: [ 0.344515] [<ffffffff810e2c33>] ? print_modules+0x73/0xd0
Jul 27 14:01:13 t44 kernel: [ 0.344523] [<ffffffff815b239d>] dump_stack+0x45/0x5d
Jul 27 14:01:13 t44 kernel: [ 0.344530] [<ffffffff8105e097>] warn_slowpath_common+0x87/0xd0
Jul 27 14:01:13 t44 kernel: [ 0.344536] [<ffffffff8105e13a>] warn_slowpath_fmt+0x5a/0x70
Jul 27 14:01:13 t44 kernel: [ 0.344543] [<ffffffff8104a3ef>] __ioremap_caller+0x26f/0x3b0
Jul 27 14:01:13 t44 kernel: [ 0.344550] [<ffffffff8102ae46>] ? snb_uncore_imc_init_box+0x66/0xa0
Jul 27 14:01:13 t44 kernel: [ 0.344556] [<ffffffff8104a556>] ioremap_nocache+0x26/0x40
Jul 27 14:01:13 t44 kernel: [ 0.344562] [<ffffffff8102ae46>] snb_uncore_imc_init_box+0x66/0xa0
Jul 27 14:01:13 t44 kernel: [ 0.344568] [<ffffffff8102903c>] uncore_pci_probe+0xdc/0x1f0
Jul 27 14:01:13 t44 kernel: [ 0.344576] [<ffffffff81386ce8>] pci_device_probe+0xa8/0x110
Jul 27 14:01:13 t44 kernel: [ 0.344582] [<ffffffff8141bd36>] driver_probe_device+0x176/0x2f0
Jul 27 14:01:13 t44 kernel: [ 0.344587] [<ffffffff8141bf10>] ? __device_attach+0x60/0x60
Jul 27 14:01:13 t44 kernel: [ 0.344592] [<ffffffff8141bfbb>] __driver_attach+0xab/0xb0
Jul 27 14:01:13 t44 kernel: [ 0.344597] [<ffffffff8141bf10>] ? __device_attach+0x60/0x60
Jul 27 14:01:13 t44 kernel: [ 0.344602] [<ffffffff8141bf10>] ? __device_attach+0x60/0x60
Jul 27 14:01:13 t44 kernel: [ 0.344609] [<ffffffff8141999b>] bus_for_each_dev+0x7b/0xc0
Jul 27 14:01:13 t44 kernel: [ 0.344614] [<ffffffff8141b6c6>] driver_attach+0x26/0x40
Jul 27 14:01:13 t44 kernel: [ 0.344619] [<ffffffff8141b308>] bus_add_driver+0x178/0x220
Jul 27 14:01:13 t44 kernel: [ 0.344632] [<ffffffff8141c830>] driver_register+0x60/0xe0
Jul 27 14:01:13 t44 kernel: [ 0.344641] [<ffffffff813852ee>] __pci_register_driver+0x6e/0x80
Jul 27 14:01:13 t44 kernel: [ 0.344647] [<ffffffff81c2355e>] ? uncore_cpu_setup+0x33/0x33
Jul 27 14:01:13 t44 kernel: [ 0.344652] [<ffffffff81c236a1>] intel_uncore_init+0x143/0x4b4
Jul 27 14:01:13 t44 kernel: [ 0.344657] [<ffffffff81c2355e>] ? uncore_cpu_setup+0x33/0x33
Jul 27 14:01:13 t44 kernel: [ 0.344664] [<ffffffff810003a4>] do_one_initcall+0x94/0x1a0
Jul 27 14:01:13 t44 kernel: [ 0.344671] [<ffffffff81c15c7d>] kernel_init_freeable+0x1c6/0x2be
Jul 27 14:01:13 t44 kernel: [ 0.344676] [<ffffffff81c14eb2>] ? initcall_blacklist+0x148/0x148
Jul 27 14:01:13 t44 kernel: [ 0.344683] [<ffffffff815a8940>] ? rest_init+0x80/0x80
Jul 27 14:01:13 t44 kernel: [ 0.344689] [<ffffffff815a894e>] kernel_init+0xe/0x100
Jul 27 14:01:13 t44 kernel: [ 0.344696] [<ffffffff815b9cbe>] ret_from_fork+0x3e/0x70
Jul 27 14:01:13 t44 kernel: [ 0.344701] [<ffffffff815a8940>] ? rest_init+0x80/0x80
Jul 27 14:01:13 t44 kernel: [ 0.344709] ---[ end trace 59720842ea32ef0e ]---
Anything to worry about ?
--
Toralf, pgp key: 872AE508 0076E94E
reply other threads:[~2015-07-27 12:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55B61F92.4030500@gmx.de \
--to=toralf.foerster@gmx.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.