From: Tomasz Sterna <tomek@xiaoka.com>
To: Daniel Walker <dwalker@codeaurora.org>
Cc: linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH] [Streak] Add workaround for TTY kernel OOPS at the cost of performance.
Date: Fri, 01 Oct 2010 23:11:49 +0200 [thread overview]
Message-ID: <1285967509.25392.66.camel@wing> (raw)
In-Reply-To: <1285948046.22265.12.camel@m0nster>
Dnia 2010-10-01, pią o godzinie 08:47 -0700, Daniel Walker pisze:
> But if you give us the OOPS message we can try to figure out
> what's going on..
[...]
Console: switching to colour frame buffer device 60x50
BUG: scheduling while atomic swapper/1/0x00000002
Modules linked in:
[<c0032740>] (unwind_backtrace+0x0/0xe4) from [<c04104e8>] (schedule+0x68/0x330)
[<c04104e8>] (schedule+0x68/0x330) from [<c0410d98>] (schedule_timeout+0x18/0x1ec)
[<c0410d98>] (schedule_timeout+0x18/0x1ec) from [<c0410bc8>] (wait_for_common+0xf4/0x1ac)
[<c0410bc8>] (wait_for_common+0xf4/0x1ac) from [<c0410cd0>] (wait_for_completion_killable+0x18/0x24)
[<c0410cd0>] (wait_for_completion_killable+0x18/0x24) from
[<c0081650>] (notifier_call_chain+0x38/0x68) from [<c0081850>] (__blocking_notifier_callchain+0x48/0x5c)
[<c0081850>] (__blocking_notifier_callchain+0x48/0x5c) from ...
then it gets "scrambled", but I see the following functions:
device_attach
bus_probe_device
driver_probe_device
bus_for_each_drv
platform_drv_probe
schedule
fbcon_takeover
device_attach
I guess the 'scheduling while atomic swapper' happens in fbcon_takeover()
Right?
P.S. source of oops msg is here: http://www.flickr.com/photos/smoku/5042198623/ ;-)
next prev parent reply other threads:[~2010-10-01 21:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-30 22:42 [PATCH] [Streak] Add workaround for TTY kernel OOPS at the cost of performance Tomasz Sterna
2010-09-30 23:04 ` Daniel Walker
2010-10-01 8:52 ` Tomasz Sterna
2010-10-01 15:47 ` Daniel Walker
2010-10-01 20:07 ` Tomasz Sterna
2010-10-02 0:26 ` Daniel Walker
2010-10-01 21:11 ` Tomasz Sterna [this message]
[not found] ` <AANLkTimVpsmWLpXwuLyFgC3sOSMVCbF38DNRL13_5bgk@mail.gmail.com>
2010-10-02 10:14 ` Bradley Smith
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=1285967509.25392.66.camel@wing \
--to=tomek@xiaoka.com \
--cc=dwalker@codeaurora.org \
--cc=linux-arm-msm@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.