From: Felipe Contreras <felipe.contreras@gmail.com>
To: "Guzman Lugo, Fernando" <fernando.lugo@ti.com>
Cc: linux-omap <linux-omap@vger.kernel.org>,
"Ramirez Luna, Omar" <omar.ramirez@ti.com>,
Hiroshi Doyu <hiroshi.doyu@nokia.com>
Subject: Re: [PATCH 1/2] dspbridge: deh: fix corruption on MMU fault
Date: Fri, 14 May 2010 01:42:47 +0300 [thread overview]
Message-ID: <AANLkTimJ0La59QijKT07GCZocapSZMmMg-OFT3m7sG0F@mail.gmail.com> (raw)
In-Reply-To: <496565EC904933469F292DDA3F1663E602CB6CABC3@dlee06.ent.ti.com>
On Fri, May 14, 2010 at 12:21 AM, Guzman Lugo, Fernando
<fernando.lugo@ti.com> wrote:
> dump_dsp_stack is waiting DSP for dumping the stack, I don't think that you
> are getting the complete dump with this patch.
I'm not getting it anyway. Besides, that feature should be
configurable so we can disable it on production systems. If this patch
indeed prevents that feature from working, then all that code should
be somehow configurable. Probably all the GPT8 code is not really
needed either and can be enabled only when
CONFIG_OMAP_BRIDGE_BACKTRACE.
In the meantime, getting rid of memory corruption > having dump stack
functionality.
Are you using the public L23.i3.3 baseimage?
--
Felipe Contreras
next prev parent reply other threads:[~2010-05-13 22:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-13 20:46 [PATCH 0/2] dspbridge: deh: fix memory corruption on faults Felipe Contreras
2010-05-13 20:46 ` [PATCH 1/2] dspbridge: deh: fix corruption on MMU fault Felipe Contreras
2010-05-13 21:21 ` Guzman Lugo, Fernando
2010-05-13 22:42 ` Felipe Contreras [this message]
2010-05-13 20:46 ` [PATCH 2/2] dspbridge: deh: remove unused code Felipe Contreras
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=AANLkTimJ0La59QijKT07GCZocapSZMmMg-OFT3m7sG0F@mail.gmail.com \
--to=felipe.contreras@gmail.com \
--cc=fernando.lugo@ti.com \
--cc=hiroshi.doyu@nokia.com \
--cc=linux-omap@vger.kernel.org \
--cc=omar.ramirez@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.