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/ ;-) -- To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
