From: Archit Taneja <a0393947@ti.com>
To: Ilya Yanok <yanok@emcraft.com>
Cc: linux-omap@vger.kernel.org, "paul@pwsan.com" <paul@pwsan.com>
Subject: Re: Interesting L3 driver panic on v3.2-rc5 on 3530
Date: Tue, 20 Dec 2011 17:53:06 +0530 [thread overview]
Message-ID: <4EF07E2A.7030201@ti.com> (raw)
In-Reply-To: <loom.20111220T013434-130@post.gmane.org>
Hi Ilya,
On Tuesday 20 December 2011 06:09 AM, Ilya Yanok wrote:
> Hi Paul,
>
> Paul Walmsley<paul<at> pwsan.com> writes:
>> [ 0.238494] Kernel BUG at c0033e34 [verbose debug info unavailable]
>> [ 0.245025] Internal error: Oops - undefined instruction: 0 [#1] SMP
>> [ 0.262390] PC is at omap3_l3_app_irq+0x108/0x12c
>
> I'm getting the same error on one of my AM3517 boards.
> L3_SI_FLAG_STATUS_0 register has bit 15 set that means Display SS IA burst
> timeout according to the RM.
>
> Regards, Ilya.
Do the bootloaders on these boards enable display?
There was a patch which got into the kernel in 3.2-rc4:
b923d40dd4211c4ef7d4efa2bd81b7ca1d8744c1
ARM: OMAP2PLUS: DSS: Ensure DSS works correctly if display is enabled in
bootloader
This tries to disable any display outputs if enabled in bootloader. If
this issue didn't happen before, we might want to look into this code.
Could you share what debug prints you get from the function
omap_dss_reset() (its in arch/arm/mach-omap2/display.c)
Thanks,
Archit
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2011-12-20 12:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-17 2:02 Interesting L3 driver panic on v3.2-rc5 on 3530 Paul Walmsley
2011-12-17 5:14 ` Shilimkar, Santosh
2011-12-20 0:39 ` Ilya Yanok
2011-12-20 12:23 ` Archit Taneja [this message]
2011-12-20 19:15 ` Ilya Yanok
2011-12-22 1:05 ` Ilya Yanok
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=4EF07E2A.7030201@ti.com \
--to=a0393947@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=yanok@emcraft.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).