From: Tejun Heo <tj@kernel.org>
To: Icenowy Zheng <icenowy@aosc.xyz>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Adam Borowski <kilobyte@angband.pl>,
Andre Przywara <andre.przywara@arm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: sun50i-a64-pinctrl WARN_ON drivers/base/dd.c:349
Date: Fri, 17 Mar 2017 10:44:22 -0400 [thread overview]
Message-ID: <20170317144422.GD5078@htj.duckdns.org> (raw)
In-Reply-To: <785901489760914@web50g.yandex.ru>
On Fri, Mar 17, 2017 at 10:28:34PM +0800, Icenowy Zheng wrote:
> > 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?
>
> Do you mean in the first probing trial the driver didn't clean up well?
Possibly but devres should have released all resources after the
previous probe failure or driver disassociation, so I have no idea how
there can be resources left on that list.
> With the same driver I didn't see this problem in 4.11-rc{1,2}.
devres hasn't changed, so I have no idea what changed that. Which
kernels are affected? Can you bisect if the problem is easily
reproducible?
Thanks.
--
tejun
next prev parent reply other threads:[~2017-03-17 14:44 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 ` sun50i-a64-pinctrl WARN_ON drivers/base/dd.c:349 Greg Kroah-Hartman
2017-03-17 14:08 ` Tejun Heo
[not found] ` <785901489760914@web50g.yandex.ru>
2017-03-17 14:44 ` Tejun Heo [this message]
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=20170317144422.GD5078@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;
as well as URLs for NNTP newsgroup(s).