All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Hanno Böck" <hanno@hboeck.de>
To: linux-kernel@vger.kernel.org
Subject: call trace warn_slowpath_common / warn_slowpath_fmt / ioremap_caller ... on every boot
Date: Wed, 9 Sep 2015 21:48:27 +0200	[thread overview]
Message-ID: <20150909214827.2bc644df@pc1> (raw)

[-- Attachment #1: Type: text/plain, Size: 3472 bytes --]

Hi,

On my system the kernel prints a stack trace and some error messages on
every boot, see below.

This is currently not causing any notable malfunction, but I wonder
what this is about. I tried bisecting the issue and endet up with this
commit as the first bad commit:
15c1247953e8a45232ed5a5540f291d2d0a77665

Interestingly that's itself a revert of a previous commit.

Any ideas what's wrong here? I'd gladly provide more info if needed.


The device is a Thinkpad X1 Carbon 2014 edition (20A7). Here is the full
dmesg output:
https://files.hboeck.de/dmesg-calltrace.txt.xz

Here's some more info about the hw, like lspci, dmidecode, lsusb output:
http://int21.de/x1carbon/data/


[    0.129335] resource sanity check: requesting [mem 0xfed10000-0xfed15fff], which spans more than pnp 00:01 [mem 0xfed10000-0xfed13fff]
[    0.129478] ------------[ cut here ]------------
[    0.129569] WARNING: CPU: 0 PID: 1 at arch/x86/mm/ioremap.c:198 __ioremap_caller+0x200/0x350()
[    0.129705] Info: mapping multiple BARs. Your kernel is fine.
[    0.129757] Modules linked in:

[    0.129973] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.2.0 #1
[    0.130064] Hardware name: LENOVO 20A7CTO1WW/20A7CTO1WW, BIOS GRET43WW (1.20 ) 01/08/2015
[    0.130198]  ffffffff819914f1 ffff880214d1bb18 ffffffff817e0a3a 0000000000000001
[    0.130487]  ffff880214d1bb68 ffff880214d1bb58 ffffffff810b38a0 0000000080000200
[    0.130776]  ffffc90000e88000 ffffc90000e88000 00000000fed10000 0000000000000000
[    0.131076] Call Trace:
[    0.131163]  [<ffffffff817e0a3a>] dump_stack+0x45/0x57
[    0.131256]  [<ffffffff810b38a0>] warn_slowpath_common+0x80/0xc0
[    0.131350]  [<ffffffff810b3921>] warn_slowpath_fmt+0x41/0x50
[    0.131441]  [<ffffffff8107baf0>] __ioremap_caller+0x200/0x350
[    0.131533]  [<ffffffff8107bc52>] ioremap_nocache+0x12/0x20
[    0.131625]  [<ffffffff81061448>] snb_uncore_imc_init_box+0x68/0x90
[    0.131717]  [<ffffffff8105f961>] uncore_pci_probe+0xd1/0x1b0
[    0.131809]  [<ffffffff812f3050>] local_pci_probe+0x40/0xa0
[    0.131913]  [<ffffffff811fc288>] ? sysfs_do_create_link_sd.isra.2+0x68/0xb0
[    0.132009]  [<ffffffff812f3172>] pci_device_probe+0xc2/0x110
[    0.132101]  [<ffffffff81481471>] driver_probe_device+0x131/0x2d0
[    0.132193]  [<ffffffff8148169b>] __driver_attach+0x8b/0x90
[    0.132283]  [<ffffffff81481610>] ? driver_probe_device+0x2d0/0x2d0
[    0.132377]  [<ffffffff8147f6ef>] bus_for_each_dev+0x5f/0x90
[    0.132467]  [<ffffffff81480ff9>] driver_attach+0x19/0x20
[    0.132558]  [<ffffffff81480c4b>] bus_add_driver+0x1ab/0x220
[    0.132650]  [<ffffffff81b42ab9>] ? uncore_types_exit+0x26/0x26
[    0.132741]  [<ffffffff81481eab>] driver_register+0x5b/0xe0
[    0.132832]  [<ffffffff812f2847>] __pci_register_driver+0x47/0x50
[    0.132934]  [<ffffffff81b42b8b>] intel_uncore_init+0xd2/0x2aa
[    0.133025]  [<ffffffff81b42ab9>] ? uncore_types_exit+0x26/0x26
[    0.133117]  [<ffffffff810002c3>] do_one_initcall+0x83/0x1a0
[    0.133209]  [<ffffffff81b38fc6>] kernel_init_freeable+0x14b/0x1d8
[    0.133303]  [<ffffffff817dd800>] ? rest_init+0x80/0x80
[    0.133393]  [<ffffffff817dd809>] kernel_init+0x9/0xe0
[    0.133483]  [<ffffffff817e7c9f>] ret_from_fork+0x3f/0x70
[    0.133574]  [<ffffffff817dd800>] ? rest_init+0x80/0x80
[    0.133665] ---[ end trace 60c3f2999044d108 ]---

-- 
Hanno Böck
http://hboeck.de/

mail/jabber: hanno@hboeck.de
GPG: BBB51E42

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

                 reply	other threads:[~2015-09-09 19:53 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=20150909214827.2bc644df@pc1 \
    --to=hanno@hboeck.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.