"Gupta, Ramesh" <grgu...@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 -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
