> -----Original Message----- > From: Kevin Hilman [mailto:[email protected]] > Sent: Friday, March 13, 2009 2:35 AM
> 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. Thanks. Yep, it does sound like a mem leak... will keep the list posted as we progress. Regards, Nishanth Menon -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
