From: Tony Lindgren <tony@atomide.com>
To: Komal Shah <komal_shah802003@yahoo.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: clk_get kernel dump
Date: Mon, 20 Feb 2006 16:05:38 -0800 [thread overview]
Message-ID: <20060221000538.GJ30248@atomide.com> (raw)
In-Reply-To: <20060215143716.48574.qmail@web32901.mail.mud.yahoo.com>
* Komal Shah <komal_shah802003@yahoo.com> [060215 06:37]:
> --- Tony Lindgren <tony@atomide.com> wrote:
>
> >
> > Might be the common DSP code trying to set NULL clocks on omap2. I've
> > patched the clock framework to check that:
> >
> >
> http://source.mvista.com/git/gitweb.cgi?p=linux-omap-2.6.git;a=commitdiff;h=8fc55a5be4a212efc51a335ddcd5ba066f46de6c
> >
> > So updating to current git tree should help.
>
> My tree is having this patch and clock fwk is latest as per the git
> tree. But the dump seems to coming from debug_mutex_waiter_free(...)
> function.
In case you still have this problem, my h4 boots just fine here, BTW.
Tony
prev parent reply other threads:[~2006-02-21 0:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-14 17:01 clk_get kernel dump Komal Shah
2006-02-14 17:56 ` Tony Lindgren
2006-02-15 14:37 ` Komal Shah
2006-02-21 0:05 ` Tony Lindgren [this message]
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=20060221000538.GJ30248@atomide.com \
--to=tony@atomide.com \
--cc=komal_shah802003@yahoo.com \
--cc=linux-omap-open-source@linux.omap.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox