From: dhylands@gmail.com (Dave Hylands)
To: kernelnewbies@lists.kernelnewbies.org
Subject: BUG: scheduling while atomic
Date: Mon, 9 May 2011 23:08:17 -0700 [thread overview]
Message-ID: <BANLkTinaPdGvf9za4paw808jkmhrgY7DYw@mail.gmail.com> (raw)
In-Reply-To: <BANLkTik=+18=ZKgP+1DbcFkjmc-DNxue2g@mail.gmail.com>
Hi Sandeep,
Sending to the list this time...
On Mon, May 9, 2011 at 10:51 PM, sandeep kumar
<coolsandyforyou@gmail.com> wrote:
> Here is the following logs i got when i collected ramdump from my
> development mobile after going to kernel panic
> Kernel version is 2.6.35.7, Android version GingerBread.
>
> BUG: scheduling while atomic: pppd/675/0x00000203
> <4>[?? 85.745849] Modules linked in: dhd hotspot_event_monitoring bthid
> cmc7xx_sdio
> <4>[?? 85.746032] [<c003f7dc>] (unwind_backtrace+0x0/0x168) from
> [<c05aa808>] (dump_stack+0x18/0x1c)
> <4>[?? 85.746154] [<c05aa808>] (dump_stack+0x18/0x1c) from [<c00d86a4>]
> (__schedule_bug+0x54/0x68)
> <4>[?? 85.746246] [<c00d86a4>] (__schedule_bug+0x54/0x68) from [<c05aab3c>]
> (schedule+0x78/0x48c)
> <4>[?? 85.746337] [<c05aab3c>] (schedule+0x78/0x48c) from [<c05ab604>]
> (schedule_timeout+0x24/0x23c)
> <4>[?? 85.746429] [<c05ab604>] (schedule_timeout+0x24/0x23c) from
> [<c05aced0>] (__down+0x88/0xc4)
> <4>[?? 85.746520] [<c05aced0>] (__down+0x88/0xc4) from [<c00fd654>]
> (down+0x44/0x84)
> <4>[?? 85.746643] [<c00fd654>] (down+0x44/0x84) from [<c0440bac>]
> (dpram_write+0x64/0x884)
> <4>[?? 85.746734] [<c0440bac>] (dpram_write+0x64/0x884) from [<c04414f0>]
> (vs_write+0x104/0x154)
> <4>[?? 85.746826] [<c04414f0>] (vs_write+0x104/0x154) from [<c034328c>]
> (ppp_async_push+0x110/0x584)
> <4>[?? 85.746917] [<c034328c>] (ppp_async_push+0x110/0x584) from
> [<c0343750>] (ppp_async_send+0x50/0x58)
> <4>[?? 85.747009] [<c0343750>] (ppp_async_send+0x50/0x58) from [<c0341360>]
> (ppp_channel_push+0x60/0x100)
> <4>[?? 85.747100] [<c0341360>] (ppp_channel_push+0x60/0x100) from
> [<c0341500>] (ppp_write+0x100/0x108)
Looking at the source, ppp_channel_push calls spin_lock_bh which
enters the atomic context.
dpram_write tries to call down from within this context, which isn't legal.
--
Dave Hylands
Shuswap, BC, Canada
http://www.davehylands.com
next prev parent reply other threads:[~2011-05-10 6:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-10 5:51 BUG: scheduling while atomic sandeep kumar
2011-05-10 6:08 ` Dave Hylands [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-12-05 9:12 Bug:scheduling " sandeep kumar
2011-12-05 19:03 ` Jonathan Neuschäfer
2011-12-05 19:16 ` Jonathan Neuschäfer
[not found] <CABOM9ZqSazS-NkD980f6sUyy=hk1aLVY+Vjwcxs3mGybvbkgaQ@mail.gmail.com>
2012-04-18 6:44 ` BUG: scheduling " Arun KS
2012-04-18 7:31 ` Dave Hylands
2012-04-18 8:08 ` Arun KS
2012-04-18 8:14 ` Dave Hylands
2012-04-18 8:27 ` Srivatsa S. Bhat
2012-04-18 8:40 ` Arun KS
2012-04-18 8:58 ` Arun KS
2012-04-18 15:40 ` Dave Hylands
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=BANLkTinaPdGvf9za4paw808jkmhrgY7DYw@mail.gmail.com \
--to=dhylands@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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).