On Wed, 2010-02-03 at 12:24 -0500, Iordan Iordanov wrote: > This is a very strange issue indeed. I had 2GB of RAM on the laptop at > that moment (now they are 1.5GB) and was running nothing else. Hence, > a memory leak seems more than likely in this situation. I didn't think > to check the amount of free memory during the problems, but I'll > certainly give it a shot. I am not experiencing this problem with b43 > or with the proprietary Broadcom driver and my bcm based adapter. The > only time I've seen it is with ath9k, both the karmic koala one and > the cutting edge one. > > Can you please give me some hints as to tests I can do for you, or > debugging I can enable so I can give you more useful information? The > stall during large transfers is 100% reproducible. It would be > wonderful if I can show you more debug info and shed some light on the > situation. Here's what you can try, in order of intrusiveness. Use slabtop to see the kernel memory in use. You should be able to spot who is hogging memory. Try MadWifi trunk with your card. It's easy to compile and should support AR5418 just fine. That will show if ath9k is to blame. Try compat-wireless. That's a bigger package that would replace all your wireless drivers, but you won't need to replace your kernel. That would help if the memory leak was fixed in the current wireless branch of the kernel. Recompile the kernel with CONFIG_DEBUG_KMEMLEAK and follow the instructions in the kernel sources (Documentation/kmemleak.txt) how to discover the leaks. Ask in LKML (linux-kernel@xxxxxxxxxxxxxxx), they may know better. -- Regards, Pavel Roskin -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
