From: "Jiří Prchal" <jiri.prchal-cKCO0sOKHLPtwjQa/ONI9g@public.gmane.org>
To: "Ferre, Nicolas" <Nicolas.FERRE-AIFe0yeh4nAAvxtiuMwx3w@public.gmane.org>
Cc: broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [BUG] atmel: spi: scheduling while atomic
Date: Tue, 8 Sep 2015 14:17:42 +0200 [thread overview]
Message-ID: <55EED1E6.7000902@aksignal.cz> (raw)
Hi,
again I discovered a problem when I access devices on SPI. It appears if I access one device pretty often (about once at
second) and the error message appears about 3 times a hour. Nevertheless it works correctly.
I thing it's in kernels 3.17 and 3.18 maybe even longer, now I have 3.18.21.
...
[10176.960000] BUG: scheduling while atomic: spi0/401/0x00000002
[10176.960000] Modules linked in:
[10176.960000] Preemption disabled at:[< (null)>] (null)
[10176.960000]
[10176.960000] CPU: 0 PID: 401 Comm: spi0 Tainted: G W 3.18.21_cpm9g25 #2
[10176.960000] [<c000eef4>] (unwind_backtrace) from [<c000c558>] (show_stack+0x20/0x24)
[10176.960000] [<c000c558>] (show_stack) from [<c04a214c>] (dump_stack+0x20/0x28)
[10176.960000] [<c04a214c>] (dump_stack) from [<c049fc74>] (__schedule_bug+0x88/0xac)
[10176.960000] [<c049fc74>] (__schedule_bug) from [<c04a3488>] (__schedule+0x68/0x508)
[10176.960000] [<c04a3488>] (__schedule) from [<c04a3ae0>] (schedule+0xa0/0xa4)
[10176.960000] [<c04a3ae0>] (schedule) from [<c04a3cac>] (schedule_preempt_disabled+0x20/0x2c)
[10176.960000] [<c04a3cac>] (schedule_preempt_disabled) from [<c04a5684>] (__mutex_lock_slowpath+0xe8/0x17c)
[10176.960000] [<c04a5684>] (__mutex_lock_slowpath) from [<c04a5758>] (mutex_lock+0x40/0x44)
[10176.960000] [<c04a5758>] (mutex_lock) from [<c039086c>] (clk_prepare_lock+0x58/0xf4)
[10176.960000] [<c039086c>] (clk_prepare_lock) from [<c0391808>] (clk_get_rate+0x1c/0x54)
[10176.960000] [<c0391808>] (clk_get_rate) from [<c0311c60>] (atmel_spi_transfer_one_message+0x264/0x9ec)
[10176.960000] [<c0311c60>] (atmel_spi_transfer_one_message) from [<c030f428>] (spi_pump_messages+0x5cc/0x5f0)
[10176.960000] [<c030f428>] (spi_pump_messages) from [<c003541c>] (kthread_worker_fn+0x140/0x1ac)
[10176.960000] [<c003541c>] (kthread_worker_fn) from [<c00355c4>] (kthread+0xd4/0xe8)
[10176.960000] [<c00355c4>] (kthread) from [<c0009798>] (ret_from_fork+0x14/0x20)
...
--
To unsubscribe from this list: send the line "unsubscribe linux-spi" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2015-09-08 12:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-08 12:17 Jiří Prchal [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-03-04 14:29 [BUG] atmel: spi: scheduling while atomic Jiří Prchal
2014-03-04 21:40 ` Alexandre Belloni
2014-03-05 6:56 ` Jiří Prchal
2014-03-07 22:58 ` Alexandre Belloni
2014-03-08 0:41 ` Rabin Vincent
2014-03-10 8:11 ` Jiří Prchal
2014-03-10 9:08 ` Yang, Wenyou
2014-03-11 9:45 ` Jiří Prchal
2014-03-11 9:54 ` Yang, Wenyou
2014-03-11 10:01 ` Jiří Prchal
2014-03-08 0:46 ` Stephen Boyd
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=55EED1E6.7000902@aksignal.cz \
--to=jiri.prchal-ckco0sokhlptwjqa/oni9g@public.gmane.org \
--cc=Nicolas.FERRE-AIFe0yeh4nAAvxtiuMwx3w@public.gmane.org \
--cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.