From: Tomi Valkeinen <tomi.valkeinen@nokia.com>
To: ext Robert Nelson <robertcnelson@gmail.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: dss2 for-next BUG at drivers/video/omap2/dss/core.c:323!
Date: Tue, 18 May 2010 10:55:34 +0300 [thread overview]
Message-ID: <1274169334.2307.74.camel@tubuntu.research.nokia.com> (raw)
In-Reply-To: <AANLkTinS0irEdEzttaHd0n_w5Cs3h6Q44e9sXgcbDmNH@mail.gmail.com>
On Mon, 2010-05-17 at 16:30 +0200, ext Robert Nelson wrote:
> Hi Tomi,
>
> I've been using your dss2 branch with much success.
>
> http://gitorious.org/linux-omap-dss2/linux/commits/for-next
>
> I've just ran into a weird BUG that occurs on reboot on my headless
> beagles and wondering if you've ran into it too...
>
> The kernel I'm currently testing is 2.6.34-rc7 plus the 2.6.35 dss2
> for-next commits..
>
> I was assuming http://gitorious.org/linux-omap-dss2/linux/commit/89627989c6b4408c4578a41bcd5f9d04545797ad
> would fix it, but it hasn't fixed the Opps'ing...
>
> log on attempt to reboot:
>
> http://pastebin.com/iqAHMVD4
It looks like there's a mismatch with clock enables and disables
somewhere... I haven't seen that.
Can you tell me more details of your beagle? Does "headless" mean that
it's standard beagle board, but no display is connected to it?
Tomi
Ps. Added linux-omap to cc, somebody there may have encountered this.
next parent reply other threads:[~2010-05-18 7:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTinS0irEdEzttaHd0n_w5Cs3h6Q44e9sXgcbDmNH@mail.gmail.com>
2010-05-18 7:55 ` Tomi Valkeinen [this message]
2010-05-18 12:34 ` dss2 for-next BUG at drivers/video/omap2/dss/core.c:323! Robert Nelson
2010-05-18 17:12 ` Felipe Contreras
2010-05-24 17:02 ` Robert Nelson
2010-05-25 12:49 ` Tomi Valkeinen
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=1274169334.2307.74.camel@tubuntu.research.nokia.com \
--to=tomi.valkeinen@nokia.com \
--cc=linux-omap@vger.kernel.org \
--cc=robertcnelson@gmail.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;
as well as URLs for NNTP newsgroup(s).