kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: getarunks@gmail.com (Arun KS)
To: kernelnewbies@lists.kernelnewbies.org
Subject: BUG: scheduling while atomic
Date: Wed, 18 Apr 2012 14:28:47 +0530	[thread overview]
Message-ID: <CABOM9Zp5g7oJpx7DYCuPNBZecA9Kdmyb-5=MFHBZ+cO8sT6V8g@mail.gmail.com> (raw)
In-Reply-To: <CABOM9ZoPLrhpGfqv-JUkPM76CqrAYKOukS4XyPP5NM4Y4=sR1w@mail.gmail.com>

On Wed, Apr 18, 2012 at 12:14 PM, Arun KS <getarunks@gmail.com> wrote:

>
> Hello Guys,
>
> System is working normal after this BUG.
> PC is at 0x400b4614, probably a mmaped address.
>
> Just wondering how can this BUG happen when a process is running in user
> space.
>
>
> Can it be something like this
> 1) enter to kernel from userspace through some system call.
> 2) kernel disables the interrupt and return to user space.
> 3) and now it can happen in user space?
>
> Any thoughts?
>
> shell at android: # ls
> device[   40.603515] BUG: scheduling while atomic: Binder Thread
> #/1355/0x00010003
> [   40.610290] Modules linked in:
> [   40.613342]
> [   40.614837] Pid: 1355, comm:      Binder Thread #
> [   40.619506] CPU: 0    Tainted: G        W    (3.0.15+ #174)
> [   40.625061] PC is at 0x400b4614
> [   40.628173] LR is at 0x408d83c9
> [   40.631317] pc : [<400b4614>]    lr : [<408d83c9>]    psr: 40000010
> [   40.631317] sp : 50551918  ip : 4092d1c0  fp : 505519a4
> [   40.642730] r10: 50551974  r9 : 5016de28  r8 : 1f600009
> [   40.647949] r7 : 00000000  r6 : 00000000  r5 : 5055194c  r4 : 00f09f90
> [   40.654418] r3 : 40931c58  r2 : 00000000  r1 : 00f09f90  r0 : 00000006
> [   40.660919] Flags: nZcv  IRQs on  FIQs on  Mode USER_32  ISA ARM
> Segment user
>

But if you look at the flags here,  it is showing that IRQs are on.

[   40.668121] Control: 10c53c7d  Table: 91184059  DAC: 00000015
>
> shell at android: #
> shell at android: #
> shell at android: #
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20120418/fa9e3272/attachment.html 

  parent reply	other threads:[~2012-04-18  8:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CABOM9ZqSazS-NkD980f6sUyy=hk1aLVY+Vjwcxs3mGybvbkgaQ@mail.gmail.com>
2012-04-18  6:44 ` BUG: scheduling while atomic 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 [this message]
2012-04-18 15:40     ` Dave Hylands
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
  -- strict thread matches above, loose matches on Subject: below --
2011-05-10  5:51 BUG: scheduling " sandeep kumar
2011-05-10  6:08 ` 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='CABOM9Zp5g7oJpx7DYCuPNBZecA9Kdmyb-5=MFHBZ+cO8sT6V8g@mail.gmail.com' \
    --to=getarunks@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).