On Sun, Jan 27, 2013 at 10:49 PM, Maciek Zarzycki <zarzych@xxxxxxxxx> wrote: > On Sunday 27 of January 2013 22:25:16 Sedat Dilek wrote: > >> I can't say much to the call-traces, but in general you should add >> your kernel-config and dmesg at least. >> An 'lspci -nnvv' (or lsusb) wouldn't hurt, too. >> >> Check <wireless.kernel.org> on how to debug iwlwifi driver >> (documentation websites). >> >> If you are fit in kernel-building you can try the pending patches in >> Greg's linux-stable GIT [2]. >> Before that I would try the pending patch from iwlwifi-fixes GIT [1], >> it's for 3.7-stable as well. >> >> Can you try and report? >> >> Regards, >> - Sedat - >> >> P.S.: IIRC iwlwifi folks have an own mailing-list? > > Thanks for your answer. The iwlwifi page mentions this mailing list for bug reports. > > I'm using arch kernel. I'll compile a vanilla kernel tomorrow and also check it with the two sets of patches that you mentioned and report back. I've also just stumbled upon docs on how to report wireless related bugs. Sorry for not following them with my first email. > For quick testing of patches I would suggest you to do a localmodconfig-ed kernel-setup. Here on a Intel sandybridge CPU it's approx. 10-12min with 'make -j4'. - Sedat - [1] http://www.h-online.com/open/features/Good-and-quick-kernel-configuration-creation-1403046.html > -- > Maciek Zarzycki -- 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
