Peter Osterlund wrote: > Michael Buesch <[EMAIL PROTECTED]> writes: > >> On Monday 04 September 2006 05:09, Larry Finger wrote: >>> This sounds as if there may be a deadlock when a restart occurs. Do you >>> have the lock debugging >>> options set in your configuration? I used to get the NETDEV WATCHDOG >>> timeouts, but the recent >>> wireless-2.6 changes appear to have fixed them. >> Yes, Emanuele. Please try with: >> * Latest wireless-2.6 >> * and most Kernel Hacking options enabled >> * and most important, with bcm43xx debugging enabled. > > Unfortunately, it doesn't help on my computer. With current > wireless-2.6 tree, I see the same behavior as I reported before, ie > "transmit timed out", followed by "controller RESET" and ksoftirqd > using 100% CPU. >
Peter - does the interface work for a while, or does this transmit timeout happen immediately? Are you able to capture anything in the logs, or are they always lost? If you can recover any bcm43xx info from the logs, please send it. In addition, please send the firmware version as indicated by the firmware cutter. Thanks, Larry _______________________________________________ Bcm43xx-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
