From: Tejun Heo <tj@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Icenowy Zheng <icenowy@aosc.xyz>,
Adam Borowski <kilobyte@angband.pl>,
Andre Przywara <andre.przywara@arm.com>,
linux-kernel@vger.kernel.org
Subject: Re: sun50i-a64-pinctrl WARN_ON drivers/base/dd.c:349
Date: Fri, 17 Mar 2017 10:08:12 -0400 [thread overview]
Message-ID: <20170317140812.GB5078@htj.duckdns.org> (raw)
In-Reply-To: <20170316010615.GA23552@kroah.com>
Hello,
On Thu, Mar 16, 2017 at 10:06:15AM +0900, Greg Kroah-Hartman wrote:
> > > [ 2.895375] platform 1c20800.pinctrl: Retrying from deferred list
> > > [ 2.901945] bus: 'platform': driver_probe_device: matched device 1c20800.pinctrl with driver sun50i-a64-pinctrl
> > > [ 2.912660] bus: 'platform': really_probe: probing driver sun50i-a64-pinctrl with device 1c20800.pinctrl
> > > [ 2.922826] ------------[ cut here ]------------
> > > [ 2.927751] WARNING: CPU: 2 PID: 65 at drivers/base/dd.c:350 driver_probe_device.part.1+0x37c/0x390
> > > [ 2.937339] Modules linked in:
> > > [ 2.940578]
> > > [ 2.942165] CPU: 2 PID: 65 Comm: kworker/2:1 Not tainted 4.11.0-rc1-00037-g4ca6f786aed9 #2
> > > [ 2.950913] Hardware name: Pine64+ (DT)
> > > [ 2.954989] Workqueue: events deferred_probe_work_func
> > > [ 2.960449] task: ffff80007c690c80 task.stack: ffff80007c698000
> > > [ 2.966741] PC is at driver_probe_device.part.1+0x37c/0x390
> > > [ 2.972658] LR is at driver_probe_device.part.1+0x140/0x390
> > > ...
> > > [ 3.173581] [<ffff000008555794>] driver_probe_device.part.1+0x37c/0x390
> > > [ 3.180602] [<ffff00000855595c>] __device_attach_driver+0xac/0x150
> > > [ 3.187162] [<ffff000008553610>] bus_for_each_drv+0x58/0x98
> > > [ 3.193081] [<ffff000008555374>] __device_attach+0xc4/0x150
> > > [ 3.198991] [<ffff000008555b40>] device_initial_probe+0x10/0x18
> > > [ 3.205265] [<ffff0000085547f4>] bus_probe_device+0x94/0xa0
It's warning that the device has resources associated with it on
probe. There gotta be something fishy going on with the probing
sequence. How reproducible is the problem?
Thanks.
--
tejun
next prev parent reply other threads:[~2017-03-17 14:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170315161406.smd4na25two55jjh@angband.pl>
[not found] ` <197431489595078@web8g.yandex.ru>
2017-03-16 1:06 ` Greg Kroah-Hartman
2017-03-17 14:08 ` Tejun Heo [this message]
[not found] ` <785901489760914@web50g.yandex.ru>
2017-03-17 14:44 ` Tejun Heo
2017-03-17 16:32 ` Adam Borowski
2017-04-02 23:48 ` André Przywara
2017-04-18 7:25 ` Tejun Heo
2017-04-18 9:12 ` Andre Przywara
2017-04-28 22:03 ` Tejun Heo
2017-04-29 21:28 ` Adam Borowski
2017-04-29 23:34 ` André Przywara
2017-05-01 19:22 ` Tejun Heo
2017-04-18 10:51 ` Icenowy Zheng
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=20170317140812.GB5078@htj.duckdns.org \
--to=tj@kernel.org \
--cc=andre.przywara@arm.com \
--cc=gregkh@linuxfoundation.org \
--cc=icenowy@aosc.xyz \
--cc=kilobyte@angband.pl \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®