From: Kevin Hilman <khilman@deeprootsystems.com>
To: "Gupta, Ramesh" <grgupta@ti.com>
Cc: "Menon, Nishanth" <nm@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: Bridge issue #3! dma_alloc_coherent causing crash - pm branch
Date: Fri, 13 Mar 2009 08:59:46 -0700 [thread overview]
Message-ID: <87sklh1ki5.fsf@deeprootsystems.com> (raw)
In-Reply-To: <EAF47CD23C76F840A9E7FCE10091EFAB02A8FD10D6@dbde02.ent.ti.com> (Ramesh Gupta's message of "Fri\, 13 Mar 2009 15\:18\:12 +0530")
"Gupta, Ramesh" <grgupta@ti.com> writes:
[...]
>> > Sounds like a memory leak in the bridge driver to me. I
>> suggest you
>> > enable memory leak debugging. In Kconfig
>> >
>> > Kernel Hacking --> Kernel debugging
>> >
>> > Enable 'Debug slab memory allocations' and its child 'Memory leak
>> > debugging'.
>> >
>> > Or, you could switch to the SLUB allocator which has some more
>> > flexible debug options which can be controlled at boot-time
>> from the cmdline.
>> >
>> > While you are in the Kernel debugging menu, make sure you enable
>> > 'Verbose BUG()' and 'Verbose kernel errors'. This will ensure that
>> > any memory leaks will be dumped with some extra debug output.
>
> I enabled all the above options, do I need to add some boot options to enable
> Debug messages? I am not seeing any debug information displayed in the cosole by default.
> Looks like I am mising some thing :( . Any comments?
>
You'll only see extra messages when the kerel hits a BUG() or a WARN(). If
you don't see anything more verbose with all these options enabled, then
the kernel is not detecting any problems.
Kevin
next prev parent reply other threads:[~2009-03-13 15:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-13 0:23 Bridge issue #3! dma_alloc_coherent causing crash - pm branch Menon, Nishanth
2009-03-13 0:34 ` Kevin Hilman
2009-03-13 8:04 ` Menon, Nishanth
2009-03-13 9:48 ` Gupta, Ramesh
2009-03-13 15:59 ` Kevin Hilman [this message]
2009-03-14 4:26 ` Gupta, Ramesh
2009-03-16 9:54 ` dma_alloc_coherent bug? Menon, Nishanth
2009-03-16 17:29 ` Ameya Palande
2009-03-16 19:09 ` Menon, Nishanth
2009-03-17 6:16 ` dma_alloc_coherent fragmentation Menon, Nishanth
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=87sklh1ki5.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=grgupta@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=nm@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox