From: Mushtaq Khan <mushtaqk921@gmail.com>
To: linux-rt-users@vger.kernel.org
Subject: BUG: scheduling while atomic
Date: Wed, 17 Sep 2014 14:42:30 +0530 [thread overview]
Message-ID: <CAP6rfc-1i2LkwVJory31cj8XzaYfXrBcpmKLPE2GP709LEw=Jg@mail.gmail.com> (raw)
Hi,
I see error message "BUG: scheduling while atomic"intermittently. As
per other post on similar issue, this happens when schedule is called
from either interrupt
context or some other atomic operation (Might be after acquiring
spinlock). But from the call trace am not getting any clue, please
help me guide on this issue.
Using Linux 3.4rt.
BUG: scheduling while atomic: dslmgmt/538/0x00000201
Modules linked in: iptable_mangle init_addr( (null) - (null)),
core_addr(c036
9000 - c0369210)
iptable_filter init_addr( (null) - (null)), core_addr(c0362000 - c03620b0)
ip_tables init_addr( (null) - (null)), core_addr(c0359000 - c035b618)
xt_multiport init_addr( (null) - (null)), core_addr(c034f000 - c034f2d8)
xt_mark init_addr( (null) - (null)), core_addr(c0348000 - c0348098)
xt_mac init_addr( (null) - (null)), core_addr(c0342000 - c03420b4)
xt_DSCP init_addr( (null) - (null)), core_addr(c033c000 - c033c388)
xt_dscp init_addr( (null) - (null)), core_addr(c0335000 - c0335128)
pwrmngtd(P) init_addr( (null) - (null)), core_addr(c032e000 - c032f54c)
bcmvlan(P) init_addr( (null) - (null)), core_addr(c030a000 - c031a598)
p8021ag(P) init_addr( (null) - (null)), core_addr(c02e0000 - c02e1120)
bcmarl(P) init_addr( (null) - (null)), core_addr(c02d7000 - c02d7e74)
nciTMSkmod(P) init_addr( (null) - (null)), core_addr(c0280000 - c029ffc8)
bcm_enet init_addr( (null) - (null)), core_addr(c01e4000 - c02078f4)
adsldd(P) init_addr( (null) - (null)), core_addr(c011b000 - c0150c78)
bcmxtmcfg(P) init_addr( (null) - (null)), core_addr(c009a000 - c00a5e28)
pktflow(P) init_addr( (null) - (null)), core_addr(c0067000 - c0074800)
bcm_bpm(P) init_addr( (null) - (null)), core_addr(c0045000 - c0046470)
bcm_ingqos(P) init_addr( (null) - (null)), core_addr(c003a000 - c003b070)
chipinfo(P) init_addr( (null) - (null)), core_addr(c0031000 - c0031198)
Call Trace:
[<802a0d6c>] printk+0x24/0x30
[<80074714>] print_modules+0x88/0x144
[<802a43c8>] __schedule+0x54c/0x58c
[<802a12d0>] __schedule_bug+0x38/0x54
[<802a0b30>] dump_stack+0x8/0x34
[<802a43c8>] __schedule+0x54c/0x58c
[<8017d0f0>] do_output_char+0x1b4/0x220
[<801876ec>] uart_write+0xd8/0x15c
[<8017d19c>] process_output+0x40/0x6c
[<802a4580>] schedule+0x58/0xb4
[<800f1dc0>] fsnotify+0x1b0/0x2dc
[<802a3514>] do_nanosleep+0xf8/0x13c
[<80055c98>] hrtimer_nanosleep+0xb4/0x158
[<80054dd8>] hrtimer_wakeup+0x0/0x2c
[<80044f00>] sys_rt_sigaction+0x78/0xd4
[<80055da8>] sys_nanosleep+0x6c/0x94
[<8001b95c>] stack_done+0x20/0x40
Call Trace:
[<802a0b30>] dump_stack+0x8/0x34
[<802a43c8>] __schedule+0x54c/0x58c
[<802a4580>] schedule+0x58/0xb4
[<802a3514>] do_nanosleep+0xf8/0x13c
[<80055c98>] hrtimer_nanosleep+0xb4/0x158
[<80055da8>] sys_nanosleep+0x6c/0x94
[<8001b95c>] stack_done+0x20/0x40
Regards,
Mushtaq Khan
next reply other threads:[~2014-09-17 9:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-17 9:12 Mushtaq Khan [this message]
2015-02-17 10:18 ` BUG: scheduling while atomic 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='CAP6rfc-1i2LkwVJory31cj8XzaYfXrBcpmKLPE2GP709LEw=Jg@mail.gmail.com' \
--to=mushtaqk921@gmail.com \
--cc=linux-rt-users@vger.kernel.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).