Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751156AbdCQOo6 (ORCPT ); Fri, 17 Mar 2017 10:44:58 -0400 Received: from mail-yw0-f177.google.com ([209.85.161.177]:33886 "EHLO mail-yw0-f177.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751017AbdCQOo4 (ORCPT ); Fri, 17 Mar 2017 10:44:56 -0400 Date: Fri, 17 Mar 2017 10:44:22 -0400 From: Tejun Heo To: Icenowy Zheng Cc: Greg Kroah-Hartman , Adam Borowski , Andre Przywara , "linux-kernel@vger.kernel.org" Subject: Re: sun50i-a64-pinctrl WARN_ON drivers/base/dd.c:349 Message-ID: <20170317144422.GD5078@htj.duckdns.org> References: <20170315161406.smd4na25two55jjh@angband.pl> <197431489595078@web8g.yandex.ru> <20170316010615.GA23552@kroah.com> <20170317140812.GB5078@htj.duckdns.org> <785901489760914@web50g.yandex.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <785901489760914@web50g.yandex.ru> User-Agent: Mutt/1.7.1 (2016-10-04) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 735 Lines: 21 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