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 S1751021AbdCPBGc (ORCPT <rfc822;w@1wt.eu>);
        Wed, 15 Mar 2017 21:06:32 -0400
Received: from mail.linuxfoundation.org ([140.211.169.12]:38338 "EHLO
        mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1750895AbdCPBGa (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Wed, 15 Mar 2017 21:06:30 -0400
Date: Thu, 16 Mar 2017 10:06:15 +0900
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Icenowy Zheng <icenowy@aosc.xyz>, Tejun Heo <tj@kernel.org>
Cc: 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: <20170316010615.GA23552@kroah.com>
References: <20170315161406.smd4na25two55jjh@angband.pl>
 <197431489595078@web8g.yandex.ru>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <197431489595078@web8g.yandex.ru>
User-Agent: Mutt/1.8.0 (2017-02-23)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Thu, Mar 16, 2017 at 12:24:38AM +0800, Icenowy Zheng wrote:
> 
> 
> 16.03.2017, 00:14, "Adam Borowski" <kilobyte@angband.pl>:
> > Hi!
> > On Pine64, since mid-February's -next, I get the following non-fatal warning:
> 
> I don't think this is from any bug in sun50i-a64-pinctrl driver, as the PC even
> didn't enter sun50i-a64-pinctrl driver...
> 
> Maybe you should send this email also to the maintainer of the basical driver
> framework.
> 
> He's "Greg Kroah-Hartman <gregkh@linuxfoundation.org> (supporter:DRIVER
> CORE, KOBJECTS, DEBUGFS, KERNFS AND SYSFS)"
> 
> I added him to the "To" list of this reply.

Well, Tejun added that line, way back in 2.6.21, it's not exactly "new
code".  It says something is wrong with the devres list for the device,
that the bus and driver control, probe of your driver hasn't happened
yet though, so I don't really know what this is trying to check for.

Tejun?

rest of the email left below for context for Tejun..

thanks,

greg k-h

> > [ 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
> >
> > (this log has drivers/base/dd.c:350 not :349 because of added "#define
> > DEBUG" at the start of that file)
> >
> > Full console output until that point attached.
> >
> > --
> > ⢀⣴⠾⠻⢶⣦⠀ Meow!
> > ⣾⠁⢠⠒⠀⣿⡁
> > ⢿⡄⠘⠷⠚⠋⠀ Collisions shmolisions, let's see them find a collision or second
> > ⠈⠳⣄⠀⠀⠀⠀ preimage for double rot13!