lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 10 Nov 2009 07:54:57 +0100 From: Daniel Mack <daniel@...aq.de> To: Dan Williams <dcbw@...hat.com> Cc: netdev@...r.kernel.org, libertas-dev@...ts.infradead.org, Michael Hirsch <m.hirsch@...mfeld.com>, linux-kernel@...r.kernel.org Subject: Re: Libertas related kernel crash On Mon, Nov 09, 2009 at 10:51:33PM -0800, Dan Williams wrote: > On Mon, 2009-11-09 at 16:53 +0100, Daniel Mack wrote: > > On Thu, Nov 05, 2009 at 01:05:49PM +0100, Daniel Mack wrote: > > > On an ARM (PXA300) embdedded platform with a libertas chip connected via > > > SDIO, we happen to see the kernel Ooops below once in a while. > > > > > > Any pointer on where to dig? > > > > Some more input on this. Oopses similar to the one below are likely > > triggered when switching from Ad-hoc to managed mode multiple times in a > > row, and something seems corrupt the memory badly. I've searched for the > > obvious (double frees, out-of-bound writes etc), but I couldn't find > > anything yet. It is, however, related to the wireless core and/or the > > libertas driver. > > Probably just libertas. Any chance you can enable debugging options > (either in libertas, or in the kernel allocator) to help narrow down the > issue? Sure. I already enabled DEBUG_VM, but that didn't spit out anything before it crashes. Which other debug flags would you recommend to set? Daniel -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists