From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from xkh0.infr.xiaoka.com ([85.11.67.240]:55826 "EHLO xkh0.infr.xiaoka.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756546Ab0JAVMD convert rfc822-to-8bit (ORCPT ); Fri, 1 Oct 2010 17:12:03 -0400 Subject: Re: [PATCH] [Streak] Add workaround for TTY kernel OOPS at the cost of performance. From: Tomasz Sterna In-Reply-To: <1285948046.22265.12.camel@m0nster> References: <1285886565.11486.26.camel@wing> <1285887854.14953.46.camel@c-dwalke-linux.qualcomm.com> <1285923176.16981.53.camel@ubuntu> <1285948046.22265.12.camel@m0nster> Content-Type: text/plain; charset="UTF-8" Date: Fri, 01 Oct 2010 23:11:49 +0200 Message-ID: <1285967509.25392.66.camel@wing> Mime-Version: 1.0 Content-Transfer-Encoding: 8BIT Sender: linux-arm-msm-owner@vger.kernel.org List-ID: To: Daniel Walker Cc: linux-arm-msm@vger.kernel.org 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: [] (unwind_backtrace+0x0/0xe4) from [] (schedule+0x68/0x330) [] (schedule+0x68/0x330) from [] (schedule_timeout+0x18/0x1ec) [] (schedule_timeout+0x18/0x1ec) from [] (wait_for_common+0xf4/0x1ac) [] (wait_for_common+0xf4/0x1ac) from [] (wait_for_completion_killable+0x18/0x24) [] (wait_for_completion_killable+0x18/0x24) from [] (notifier_call_chain+0x38/0x68) from [] (__blocking_notifier_callchain+0x48/0x5c) [] (__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/ ;-)