From: Bjorn Helgaas <helgaas@kernel.org>
To: Valdis Kletnieks <Valdis.Kletnieks@vt.edu>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Lukas Wunner <lukas@wunner.de>
Subject: Re: next-20160517 - lockdep splat in pcie code
Date: Tue, 17 May 2016 14:37:42 -0500 [thread overview]
Message-ID: <20160517193742.GA10755@localhost> (raw)
In-Reply-To: <4249.1463510162@turing-police.cc.vt.edu>
[+cc Lukas, Mika]
On Tue, May 17, 2016 at 02:36:02PM -0400, Valdis Kletnieks wrote:
> Seen during boot on next-20160517. This apparently sneaked into the tree
> sometime after -0502 (probably after -0512 but I can't prove it at the moment)
>
> [ 1.806765] INFO: trying to register non-static key.
> [ 1.806772] the code is fine but needs lockdep annotation.
> [ 1.806777] turning off the locking correctness validator.
> [ 1.806786] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 4.6.0-next-20160517-00001-gede618fce89c-dirty #276
> [ 1.806794] Hardware name: Dell Inc. Latitude E6530/07Y85M, BIOS A17 08/19/2015
> [ 1.806802] 0000000000000086 000000009200d6c8 ffff88022ca23a90 ffffffffa83f99f3
> [ 1.806815] 0000000000000000 ffff880223727d40 ffff88022ca23b00 ffffffffa80c1de1
> [ 1.806826] 0000000000000246 0000000000000000 ffffffffffffffff ffff88022ca23ad8
> [ 1.806834] Call Trace:
> [ 1.806845] [<ffffffffa83f99f3>] dump_stack+0x68/0x95
> [ 1.806855] [<ffffffffa80c1de1>] register_lock_class+0x541/0x550
> [ 1.806861] [<ffffffffa8404b6c>] ? widen_string+0x3c/0xf0
> [ 1.806870] [<ffffffffa80c4108>] __lock_acquire+0x88/0x1260
> [ 1.806876] [<ffffffffa840751a>] ? vsnprintf+0x36a/0x520
> [ 1.806886] [<ffffffffa81bdfc1>] ? kfree_const+0x21/0x30
> [ 1.806893] [<ffffffffa80c56d1>] lock_acquire+0xb1/0x200
> [ 1.806904] [<ffffffffa852874e>] ? pm_runtime_no_callbacks+0x1e/0x40
> [ 1.806915] [<ffffffffa8a07831>] _raw_spin_lock_irq+0x41/0x50
> [ 1.806923] [<ffffffffa852874e>] ? pm_runtime_no_callbacks+0x1e/0x40
> [ 1.806932] [<ffffffffa852874e>] pm_runtime_no_callbacks+0x1e/0x40
> [ 1.806942] [<ffffffffa844fe36>] pcie_port_device_register+0x226/0x560
> [ 1.806950] [<ffffffffa8450542>] pcie_portdrv_probe+0x32/0xa0
Probably introduced by this:
http://git.kernel.org/cgit/linux/kernel/git/helgaas/pci.git/commit/?id=0195d2813547
I dropped the pci/pm branch for now.
next prev parent reply other threads:[~2016-05-17 19:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-17 18:36 next-20160517 - lockdep splat in pcie code Valdis Kletnieks
2016-05-17 19:37 ` Bjorn Helgaas [this message]
2016-05-17 22:12 ` Lukas Wunner
2016-05-18 8:54 ` Mika Westerberg
2016-05-19 21:19 ` Valdis.Kletnieks
2016-05-23 8:11 ` [PATCH] PCI: pcie: Call pm_runtime_no_callbacks() after device is registered Mika Westerberg
2016-05-23 19:55 ` Bjorn Helgaas
2016-05-24 7:58 ` Mika Westerberg
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=20160517193742.GA10755@localhost \
--to=helgaas@kernel.org \
--cc=Valdis.Kletnieks@vt.edu \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=mika.westerberg@linux.intel.com \
--cc=rafael.j.wysocki@intel.com \
/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.