On Wed, Aug 10, 2011 at 1:42 PM, Felipe Contreras
<felipe.contre...@gmail.com> wrote:
> Hi,
>
> I am trying to use a more recent version of the tidspbridge code in
> the Nokia N9, but I'm stuck with this warning that is caused by using
> the dm timer framework.
>
> [ 30.883636] BUG: sleeping function called from invalid context at
> kernel/mutex.c:287
> [ 30.885925] in_atomic(): 1, irqs_disabled(): 0, pid: 305, name: mboxd/0
> [ 30.892517] 3 locks held by mboxd/0/305:
> [ 30.896392] #0: (mboxd){+.+...}, at: [<b0081778>]
> worker_thread+0x154/0x2bc
> [ 30.903533] #1: (&mq->work){+.+...}, at: [<b0081778>]
> worker_thread+0x154/0x2bc
> [ 30.911041] #2: (pwr_lock){+.....}, at: [<af12f870>]
> handle_hibernation_from_dsp+0x1c/0x158 [bridgedriver]
> [ 30.920959] [<b003f75c>] (unwind_backtrace+0x0/0xd4) from
> [<b03a3ac4>] (mutex_lock_nested+0x30/0x32c)
> [ 30.930175] [<b03a3ac4>] (mutex_lock_nested+0x30/0x32c) from
> [<b00568f8>] (clk_set_parent+0x34/0xf8)
...
> From what I can see this could be triggered in upstream by enabling PM
> and debug mutex stuff right after loading the baseimage.
>
> Any ideas?
May I know which kernel version are you using? I can't seem to find
the mutex_lock inside clk_set_parent in arch/arm/plat-omap/clock.c.
Regards,
Omar
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
