Larry Finger <[EMAIL PROTECTED]> writes: > 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?
It works perfectly for a few hours, then it stops working. Stressing the network doesn't seem to make a difference. The only workaround I've found so far is to increase BADNESS_LIMIT to 20 in bcm43xx_main.c. With that change I have never seen this problem. > 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. When I start the kernel, it reports this: Sep 4 20:55:47 r3000 kernel: bcm43xx driver Sep 4 20:55:47 r3000 kernel: bcm43xx: Chip ID 0x4306, rev 0x3 Sep 4 20:55:47 r3000 kernel: bcm43xx: Number of cores: 5 Sep 4 20:55:47 r3000 kernel: bcm43xx: Core 0: ID 0x800, rev 0x4, vendor 0x4243, enabled Sep 4 20:55:47 r3000 kernel: bcm43xx: Core 1: ID 0x812, rev 0x5, vendor 0x4243, disabled Sep 4 20:55:47 r3000 kernel: bcm43xx: Core 2: ID 0x80d, rev 0x2, vendor 0x4243, enabled Sep 4 20:55:47 r3000 kernel: bcm43xx: Core 3: ID 0x807, rev 0x2, vendor 0x4243, disabled Sep 4 20:55:47 r3000 kernel: bcm43xx: Core 4: ID 0x804, rev 0x9, vendor 0x4243, enabled Sep 4 20:55:47 r3000 kernel: bcm43xx: PHY connected Sep 4 20:55:47 r3000 kernel: bcm43xx: Detected PHY: Version: 2, Type 2, Revision 2 Sep 4 20:55:47 r3000 kernel: bcm43xx: Detected Radio: ID: 2205017f (Manuf: 17f Ver: 2050 Rev: 2) Sep 4 20:55:47 r3000 kernel: bcm43xx: Radio turned off Sep 4 20:55:47 r3000 kernel: bcm43xx: Radio turned off Sep 4 20:55:48 r3000 kernel: bcm43xx: PHY connected Sep 4 20:55:48 r3000 kernel: bcm43xx: Radio turned on Sep 4 20:55:48 r3000 kernel: bcm43xx: Chip initialized Sep 4 20:55:48 r3000 kernel: bcm43xx: 32-bit DMA initialized Sep 4 20:55:48 r3000 kernel: bcm43xx: Keys cleared Sep 4 20:55:48 r3000 kernel: bcm43xx: Selected 802.11 core (phytype 2) Sep 4 20:55:48 r3000 kernel: bcm43xx: set security called, .level = 0, .enabled = 0, .encrypt = 0 Sep 4 20:55:48 r3000 kernel: bcm43xx: set security called, .level = 0, .enabled = 0, .encrypt = 0 Sep 4 20:55:48 r3000 kernel: bcm43xx: set security called, .active_key = 0, .level = 2, .enabled = 1, .encrypt = 1 Sep 4 20:55:48 r3000 kernel: bcm43xx: set security called, .enabled = 1, .encrypt = 1 Sep 4 20:55:48 r3000 kernel: bcm43xx: set security called, .enabled = 1, .encrypt = 1 When it stops working, it reports this: Sep 4 21:50:12 r3000 kernel: bcm43xx: set security called, .enabled = 1, .encrypt = 1 Sep 4 21:50:12 r3000 kernel: bcm43xx: set security called, .enabled = 1, .encrypt = 1 Sep 4 21:50:12 r3000 kernel: bcm43xx: Controller RESET (TX timeout) ... Sep 4 21:50:12 r3000 kernel: bcm43xx: select_wireless_core: cleanup Sep 4 21:50:12 r3000 kernel: bcm43xx: Radio turned off Sep 4 21:50:12 r3000 kernel: bcm43xx: DMA-32 0x0200 (RX) max used slots: 4/64 Sep 4 21:50:12 r3000 kernel: bcm43xx: DMA-32 0x02A0 (TX) max used slots: 0/512 Sep 4 21:50:12 r3000 kernel: bcm43xx: DMA-32 0x0280 (TX) max used slots: 0/512 Sep 4 21:50:12 r3000 kernel: bcm43xx: DMA-32 0x0260 (TX) max used slots: 0/512 Sep 4 21:50:12 r3000 kernel: bcm43xx: DMA-32 0x0240 (TX) max used slots: 0/512 Sep 4 21:50:12 r3000 kernel: bcm43xx: DMA-32 0x0220 (TX) max used slots: 87/512 Sep 4 21:50:12 r3000 kernel: bcm43xx: DMA-32 0x0200 (TX) max used slots: 0/512 Sep 4 21:50:12 r3000 kernel: bcm43xx: Radio turned on Sep 4 21:50:12 r3000 kernel: bcm43xx: Chip initialized Sep 4 21:50:12 r3000 kernel: bcm43xx: 32-bit DMA initialized Sep 4 21:50:12 r3000 kernel: bcm43xx: Keys cleared Sep 4 21:50:12 r3000 kernel: bcm43xx: Selected 802.11 core (phytype 2) Sep 4 21:50:12 r3000 kernel: bcm43xx: Controller restarted > In addition, please send the firmware version as indicated by the > firmware cutter. bcm43xx-fwcutter can cut the firmware out of bcmwl5.sys filename : bcmwl5.sys version : 3.40.73.0 MD5 : 52d67c5465c01913b03b7daca0cc4077 It also reports this: *****: Sorry, it's not posible to extract "bcm43xx_microcode11.fw". *****: Extracting firmware from an old driver is bad. Choose a more recent one. *****: Luckily bcm43xx driver doesn't include microcode11 uploads at the moment. *****: But this can be added in the future... The reason I use that firmware is because it came with the windows driver that was pre-installed on the computer when I bought it. I did try some newer firmware once (sorry don't remember which version), but it made the computer lock up immediately. Since I didn't have the Tx timeout problems until the BADNESS_LIMIT logic got added, I never bothered to experiment with different firmware versions. -- Peter Osterlund - [EMAIL PROTECTED] http://web.telia.com/~u89404340 _______________________________________________ Bcm43xx-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
