Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1603370
| From | Tejun Heo <tj@kernel.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: sun50i-a64-pinctrl WARN_ON drivers/base/dd.c:349 |
| Date | 2017-03-17 15:50 +0100 |
| Message-ID | <tm1my-7VB-25@gated-at.bofh.it> (permalink) |
| References | <tls5r-7wD-9@gated-at.bofh.it> <tls5r-7wD-11@gated-at.bofh.it> <tls5r-7wD-7@gated-at.bofh.it> <tm0Tv-7D7-11@gated-at.bofh.it> <tm1my-7VB-27@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
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
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: sun50i-a64-pinctrl WARN_ON drivers/base/dd.c:349 Greg Kroah-Hartman <gregkh@linuxfoundation.org> - 2017-03-16 02:10 +0100
Re: sun50i-a64-pinctrl WARN_ON drivers/base/dd.c:349 Tejun Heo <tj@kernel.org> - 2017-03-17 15:20 +0100
Re: sun50i-a64-pinctrl WARN_ON drivers/base/dd.c:349 Tejun Heo <tj@kernel.org> - 2017-03-17 15:50 +0100
Re: sun50i-a64-pinctrl WARN_ON drivers/base/dd.c:349 Adam Borowski <kilobyte@angband.pl> - 2017-03-17 17:40 +0100
csiph-web