From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Valdis.Kletnieks@vt.edu, linux-kernel@vger.kernel.org
Subject: Re: mmotm 2010-05-19 BUG weirdness...
Date: Thu, 20 May 2010 09:45:24 -0700 [thread overview]
Message-ID: <201005200945.24901.dmitry.torokhov@gmail.com> (raw)
In-Reply-To: <20100520085520.5176d13c.akpm@linux-foundation.org>
On Thursday 20 May 2010 05:55:20 am Andrew Morton wrote:
> On Thu, 20 May 2010 11:47:50 -0400 Valdis.Kletnieks@vt.edu wrote:
> > On Wed, 19 May 2010 16:13:09 PDT, akpm@linux-foundation.org said:
> > > The mm-of-the-moment snapshot 2010-05-19-16-12 has been uploaded to
> > >
> > > http://userweb.kernel.org/~akpm/mmotm/
> >
> > So I'm looking closer at the BUG I just posted
>
> I can't see that BUG report on lkml or in inbox.
>
> > - I had deleted two further
> > BUGs because they were obviously follow-ons to the original. But then...
> >
> > Note the following 2 lines:
> >
> > [ 35.357018] note: keymap[2481] exited with preempt_count 1
> > [ 35.360503] BUG: scheduling while atomic: keymap/2481/0x10000002
> >
> > The kernel reports the instigating process exited - and then reports it
> > as the offender for a "scheduling while atomic". Insufficient attempted
> > cleanup after the first BUG? Do we care because this is a sign of a
> > scheduler bug that could trip on a non-BUG as well, or is it "all bets
> > are off" because of the first BUG?
>
> Yes, the oops code will end up calling do_exit() to get rid of this
> process and to try to keep the machine limping along. So if you hit an
> oops with (say) a spinlock held, the task will end up calling do_exit()
> with a non-zero preempt_count.
>
> So the only problem I'm seeing here is .... Dmitry's ;)
Hmm, any chance you could stick a printk in input_set_keycode and print
the id/name of the input device?
--
Dmitry
next prev parent reply other threads:[~2010-05-20 16:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-19 23:13 mmotm 2010-05-19-16-12 uploaded akpm
2010-05-20 15:21 ` mmotm 2010-05-19 - Kconfig dependency list from hell Valdis.Kletnieks
2010-05-20 15:47 ` mmotm 2010-05-19 BUG weirdness Valdis.Kletnieks
2010-05-20 12:55 ` Andrew Morton
2010-05-20 16:45 ` Dmitry Torokhov [this message]
2010-05-20 17:52 ` Valdis.Kletnieks
2010-05-20 18:17 ` [2.6.34 PATCH] kernel: fix exit message for dead process Valdis.Kletnieks
2010-05-20 18:36 ` Andrew Morton
2010-05-20 21:08 ` [PATCH -mmotm] media: ak881x needs slab.h Randy Dunlap
2010-06-01 6:04 ` Ingo Molnar
2010-05-20 21:08 ` [PATCH -mmotm] backlight: fix s6e63m0 kconfig Randy Dunlap
2010-05-20 21:08 ` [PATCH -mmotm] backlight: fix s6e63m0 device attr function return types Randy Dunlap
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=201005200945.24901.dmitry.torokhov@gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@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 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.