From: Felipe Balbi <balbi@ti•com>
To: Nishanth Menon <nm@ti•com>
Cc: Mark Brown <broonie@kernel•org>,
Russell King - ARM Linux <linux@arm•linux.org.uk>,
Linux OMAP Mailing List <linux-omap@vger•kernel.org>,
linux-next@vger•kernel.org, linux-arm-kernel@lists•infradead.org
Subject: Re: LDP: next-20150402: twl4030 regression?
Date: Mon, 6 Apr 2015 10:27:50 -0500 [thread overview]
Message-ID: <20150406152750.GE11160@saruman.tx.rr.com> (raw)
In-Reply-To: <5522A391.6080503@ti.com>
[-- Attachment #1: Type: text/plain, Size: 1806 bytes --]
Hi,
On Mon, Apr 06, 2015 at 10:17:37AM -0500, Nishanth Menon wrote:
> On 04/06/2015 10:01 AM, Mark Brown wrote:
> > On Mon, Apr 06, 2015 at 02:58:29PM +0100, Russell King - ARM Linux wrote:
> >> On Mon, Apr 06, 2015 at 08:53:36AM -0500, Nishanth Menon wrote:
> >
> >>>> at least a description of the problem you're seeing and some attempt at
> >
> >>> Test was a simple boot test. There seems to be a lockdep reported at the
> >>> very least in the log provided (see
> >>> https://github.com/nmenon/kernel-test-logs/blob/next-20150402/omap2plus_defconfig/ldp.txt#L488
> >>> ).
> >
> >> I think what Mark is trying to say is to include a fuller description of
> >> the problem, and don't expect people to fire up their web browser to get
> >> a basic overview of what the problem is.
> >
> > Yes, indeed. I hadn't actually opened the links, I might've got round
> > to it later on.
> >
> >> My guess is that the problem _appears_ to be that someone's added a call
> >> to debug_check_no_locks_held() into schedule_hrtimeout_range_clock()
> >> without considering what this means.
> >
> >> What it means is that you can't now use usleep_range() from within any
> >> driver probe function - which is absolutely absurd.
> >
> > I can't think of any regulator side changes which might be relevant in
> > that period. It's possible that there might be something in the MFD I
> > guess.
> >
>
> Ran a few tests since my original email..
>
> 6261b06de565baafa590e58a531a1a5522cea0b6 ("regulator: Defer lookup of
> supply to regulator_get") was the only patch that was introduced in
> the interval. there seems nothing in mfd either.
>
> I still have the following in my log.. trying to further down.
I noticed a similar warning with AM437x SK
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-04-06 15:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-06 13:21 LDP: next-20150402: twl4030 regression? Nishanth Menon
2015-04-06 13:45 ` Mark Brown
2015-04-06 13:53 ` Nishanth Menon
2015-04-06 13:58 ` Russell King - ARM Linux
2015-04-06 15:01 ` Mark Brown
2015-04-06 15:17 ` Nishanth Menon
2015-04-06 15:27 ` Felipe Balbi [this message]
2015-04-06 18:45 ` Nishanth Menon
2015-04-08 16:35 ` Felipe Balbi
2015-04-08 21:46 ` Stephen Rothwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150406152750.GE11160@saruman.tx.rr.com \
--to=balbi@ti$(echo .)com \
--cc=broonie@kernel$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux-omap@vger$(echo .)kernel.org \
--cc=linux@arm$(echo .)linux.org.uk \
--cc=nm@ti$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox