The thing is: now I don't have the issue that I reported in the first message of this thread anymore. Libertas works as expected without the patch. I'm on wireless-testing v2.6.26-rc3-8056-gc2c4044 and have the following patches applied: libertas-fix-lock.patch libertas-fix-printk.patch libertas-if-cs-speed-firmware.patch libertas-if-cs-int.patch Compared to friday, I also turned on the following kernel debug options: +CONFIG_DEBUG_KERNEL=y +CONFIG_DETECT_SOFTLOCKUP=y +CONFIG_DEBUG_PREEMPT=y +CONFIG_DEBUG_RT_MUTEXES=y +CONFIG_DEBUG_PI_LIST=y +CONFIG_DEBUG_SPINLOCK=y +CONFIG_DEBUG_MUTEXES=y +CONFIG_DEBUG_LOCK_ALLOC=y +CONFIG_PROVE_LOCKING=y +CONFIG_LOCKDEP=y +CONFIG_LOCK_STAT=y +CONFIG_TRACE_IRQFLAGS=y +CONFIG_DEBUG_SPINLOCK_SLEEP=y Yet associating and executing of commands works fine. I did run "while true; do iwconfig eth1; sleep 0.2; done" quite long (up to sequence number 8804) and did not have any hickup. On friday, I even saw the hickup on the first commands/response ... -- 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
