From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1751180AbdCQOIV (ORCPT <rfc822;w@1wt.eu>);
        Fri, 17 Mar 2017 10:08:21 -0400
Received: from mail-yw0-f180.google.com ([209.85.161.180]:33846 "EHLO
        mail-yw0-f180.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1751092AbdCQOIU (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Fri, 17 Mar 2017 10:08:20 -0400
Date: Fri, 17 Mar 2017 10:08:12 -0400
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
Message-ID: <20170317140812.GB5078@htj.duckdns.org>
References: <20170315161406.smd4na25two55jjh@angband.pl>
 <197431489595078@web8g.yandex.ru>
 <20170316010615.GA23552@kroah.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170316010615.GA23552@kroah.com>
User-Agent: Mutt/1.7.1 (2016-10-04)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

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