From: Stanislav Meduna <stano@meduna.org>
To: zbr@ioremap.net,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>
Subject: w1-gpio: sleeping function called from invalid context
Date: Wed, 16 Apr 2014 16:46:32 +0200 [thread overview]
Message-ID: <534E97C8.5090407@meduna.org> (raw)
Hi,
trying 1-wire with rt-patched Linux 3.12.15-rt25+ and lock debugging:
[ 12.055550] BUG: sleeping function called from invalid context at /home/stano/Kernels/linux-3.12-rt/kernel/rtmutex.c:673
[ 12.055573] in_atomic(): 0, irqs_disabled(): 128, pid: 92, name: w1_bus_master1
[ 12.055588] 2 locks held by w1_bus_master1/92:
[ 12.055675] #0: (&dev->mutex){+.+...}, at: [<c0233560>] w1_process+0xbc/0xe0
[ 12.055729] #1: (&dev->bus_mutex){+.+...}, at: [<c0232a50>] w1_search+0x78/0x1e8
[ 12.055741] irq event stamp: 374
[ 12.055787] hardirqs last enabled at (373): [<c02e04cc>] _raw_spin_unlock_irqrestore+0x6c/0x74
[ 12.055815] hardirqs last disabled at (374): [<c0234598>] w1_touch_bit+0x50/0xc4
[ 12.055860] softirqs last enabled at (0): [<c001bacc>] copy_process+0x37c/0x1178
[ 12.055876] softirqs last disabled at (0): [< (null)>] (null)
[ 12.055899] CPU: 0 PID: 92 Comm: w1_bus_master1 Not tainted 3.12.15-rt25+ #66
[ 12.055973] [<c00151bc>] (unwind_backtrace+0x0/0xf4) from [<c0012c00>] (show_stack+0x10/0x14)
[ 12.056020] [<c0012c00>] (show_stack+0x10/0x14) from [<c02df920>] (rt_spin_lock+0x20/0x60)
[ 12.056080] [<c02df920>] (rt_spin_lock+0x20/0x60) from [<c01bc98c>] (gpiod_direction_output+0x50/0x2fc)
[ 12.056122] [<c01bc98c>] (gpiod_direction_output+0x50/0x2fc) from [<c02345ac>] (w1_touch_bit+0x64/0xc4)
[ 12.056156] [<c02345ac>] (w1_touch_bit+0x64/0xc4) from [<c0234794>] (w1_write_8+0x54/0x7c)
[ 12.056196] [<c0234794>] (w1_write_8+0x54/0x7c) from [<c0232a78>] (w1_search+0xa0/0x1e8)
[ 12.056239] [<c0232a78>] (w1_search+0xa0/0x1e8) from [<c0233414>] (w1_search_process_cb+0x50/0xe0)
[ 12.056280] [<c0233414>] (w1_search_process_cb+0x50/0xe0) from [<c0233570>] (w1_process+0xcc/0xe0)
[ 12.056334] [<c0233570>] (w1_process+0xcc/0xe0) from [<c003cf24>] (kthread+0xa0/0xa8)
[ 12.056379] [<c003cf24>] (kthread+0xa0/0xa8) from [<c000f3e0>] (ret_from_fork+0x14/0x34)
This happens reproducibly on any access.
Please Cc: me when replying
Thanks
--
Stano
next reply other threads:[~2014-04-16 14:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-16 14:46 Stanislav Meduna [this message]
2014-04-16 19:21 ` w1-gpio: sleeping function called from invalid context Paul Gortmaker
2014-04-16 19:58 ` Stanislav Meduna
2014-04-17 14:18 ` Stanislav Meduna
2015-02-16 13:29 ` Sebastian Andrzej Siewior
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=534E97C8.5090407@meduna.org \
--to=stano@meduna.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--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