From: James K. <jke...@li...> - 2006-01-31 07:35:55
|
Joerg Mayer wrote: >On Tue, Jan 24, 2006 at 09:38:16PM -0600, James Ketrenos wrote: > > >>I haven't experienced the cpu load or packet missing with the 2.3 >>firmware and 1.0.10. If you look at your kernel log, are you getting >>the frequent restarts in monitor mode after switching to the 2.3 >>firmware, or is something else consuming all the system resources? >> >> > >As far as the cpu load problems are concerned: Have you understood why >they occur? If Stefan has written a patch for it, maybe he has >understood what is going wrong here. > > In monitor mode there is never an association and so netif_start_queue is never called. If the firmware is in a seemingly continuous restart cycle (which happens if you use the 2.4 firmware image in monitor mode), your system will grind to a halt as the microcode loader takes more and more of the processing time. This problem typically goes away when switching back to the 2.3 firmware files (not just the sniffer files but also the ipw-2.4-boot.fw needs to be copied from ipw-2.3-boot.fw--which means you need to take *all* of the firmware files from 2.3) Stefan's patch addresses an issue dealing with the qdisc layer rescheduling packets to be transmitted if the current transmit priority queue is full while in managed or ad-hoc mode and packet transmit queues are enabled. James |