From: David Fries <David@Fries.net>
To: Belisko Marek <marek.belisko@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
zbr@ioremap.net, "Dr. H. Nikolaus Schaller" <hns@goldelico.com>
Subject: Re: w1: 3.14-rc7 - possible recursive locking detected
Date: Sun, 23 Mar 2014 16:50:41 -0500 [thread overview]
Message-ID: <20140323215041.GB5096@spacedout.fries.net> (raw)
In-Reply-To: <CAAfyv37OPxJkcyYi0ZZe9MSQZ3TMeCuxa8rmWh8ahNF6Bs01Mg@mail.gmail.com>
On Mon, Mar 17, 2014 at 10:38:13PM +0100, Belisko Marek wrote:
> Hi,
>
> booting latest 3.14-rc7 on gta04 board gives following warning:
>
> [ 3.101409] Driver for 1-wire Dallas network protocol.
> [ 3.109649] omap_hdq omap_hdq: OMAP HDQ Hardware Rev 0.5. Driver in
> [ 3.400146] CPU0
> [ 3.402709] ----
> [ 3.405273] lock(&(&priv->bus_notifier)->rwsem);
> [ 3.410308] lock(&(&priv->bus_notifier)->rwsem);
> [ 3.415374]
> [ 3.415374] *** DEADLOCK ***
>
> AFAIK we didn't see that on (at least 3/14-rc2).
The last drivers/w1 change went in before v3.14-rc1, so if it is
something in the w1 code, it has either been there or something else
in the rest of the kernel changed to expose it. I'm using the ds2490
USB w1 dongle, I didn't see that problem when enabling lock debugging
on 3.14.0-rc5+ which includes some changes I'm working on.
https://github.com/dfries/linux.git w1_rework
--
David Fries <david@fries.net> PGP pub CB1EE8F0
http://fries.net/~david/
next prev parent reply other threads:[~2014-03-23 21:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-17 21:38 Belisko Marek
2014-03-23 21:50 ` David Fries [this message]
2014-03-24 5:55 ` Dr. H. Nikolaus Schaller
[not found] ` <698551395662480@web15j.yandex.ru>
2014-04-08 19:47 ` Belisko Marek
2014-04-13 22:24 ` David Fries
2014-04-14 13:10 ` Dr. H. Nikolaus Schaller
2014-04-14 15:04 ` Greg Kroah-Hartman
2014-04-16 6:21 ` [PATCH] w1: avoid recursive device_add David Fries
2014-04-16 20:46 ` Dr. H. Nikolaus Schaller
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=20140323215041.GB5096@spacedout.fries.net \
--to=david@fries.net \
--cc=hns@goldelico.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marek.belisko@gmail.com \
--cc=zbr@ioremap.net \
/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
all inboxes | Powered by JetHome®