From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: LDP: next-20150402: twl4030 regression?
Date: Mon, 6 Apr 2015 16:01:27 +0100 [thread overview]
Message-ID: <20150406150127.GF6023@sirena.org.uk> (raw)
In-Reply-To: <20150406135829.GH4027@n2100.arm.linux.org.uk>
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.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150406/12c26bd7/attachment.sig>
next prev parent reply other threads:[~2015-04-06 15:01 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 [this message]
2015-04-06 15:17 ` Nishanth Menon
2015-04-06 15:27 ` Felipe Balbi
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=20150406150127.GF6023@sirena.org.uk \
--to=broonie@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).