linux-kernel - Re: sun50i-a64-pinctrl WARN

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20170317140812.GB5078@htj.duckdns.org>
Date:   Fri, 17 Mar 2017 10:08:12 -0400
From:   Tejun Heo <tj@...nel.org>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:     Icenowy Zheng <icenowy@...c.xyz>,
        Adam Borowski <kilobyte@...band.pl>,
        Andre Przywara <andre.przywara@....com>,
        linux-kernel@...r.kernel.org
Subject: Re: sun50i-a64-pinctrl WARN_ON drivers/base/dd.c:349

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