Re: Odd network locking
On Saturday 04 August 2007 07:12:46 Brennan Ashton wrote: > When the bcm43xx_mac80211 driver stops communicating, and needs to be > reset (this seems to happens when coming from strong to week to strong > signal area quickly) i have been rmmod and then modprobing it. this Can you test if you still have that "stop communication" problem, if you pull latest wireless-dev and apply these patches on top of it? http://bu3sch.de/patches/wireless-dev/LATEST/patches/ > works most of the time, but some times (~20%), it will lock up the > network with this error that repeats. > > Message from [EMAIL PROTECTED] at Fri Aug 3 00:55:41 2007 ... > localhost kernel: [19316.256549] unregister_netdevice: waiting for eth1 to > becom > e free. Usage count = 5 Most likely a bug in mac80211. But it _could_ be related to the ieee80211_stop_queues() call we do when stopping the wireless core. I think it's still not race free. But I don't know if that can cause something like this. -- Greetings Michael. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: Odd network locking
On Sat, 2007-08-04 at 00:56 -0700, Brennan Ashton wrote: > the trace overflows dmesg buffer, but here is what is left in the log: > > [...] Not very understandable unfortunately. Somewhere there must be a missing dev_put but I can't pinpoint it. johannes signature.asc Description: This is a digitally signed message part ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: Odd network locking
On Saturday 04 August 2007 17:23:57 you wrote: > > I've seen this while testing the 4301 driver (also mac80211). > > I do not get it when booting into recovery mode, but is 100% reproducible > > when booting into X. A guess is that networkmanager is involved in it. I > > am also pretty sure that "Usage count" equals the number of times the > > driver has been reloaded. I can shut down fine when I've not reloaded the > > module. > > > > My specs: 2.6.23-rc1+bcm4301 driver, 4311 hardware, kubuntu feisty. > > I will do some tests to see if killing NM first will resolve this. > This is not the first NM bug with this driver that i have noticed. The > nice thing about this bug is that it is easy to reproduce. Also i have > notice that failure rate has risen to ~50% > > PS > Sorry for the top post on that last message I have tested a lot more now, but can't isolate what program causes this. I was wrong about the "Usage count" being the number of times the driver has been reloaded, at least for my setup. After rmmod when modprobe'ing the module I get this message when in console (init 3): net eth1: device_rename: sysfs_create_symlink failed (-17) I will see if it goes away with Larrys new bcm43xx-mac80211 patch for my kernel, if not I will continue hunting. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: Odd network locking
> I've seen this while testing the 4301 driver (also mac80211). > I do not get it when booting into recovery mode, but is 100% reproducible when > booting into X. A guess is that networkmanager is involved in it. I am also > pretty sure that "Usage count" equals the number of times the driver has been > reloaded. I can shut down fine when I've not reloaded the module. > > My specs: 2.6.23-rc1+bcm4301 driver, 4311 hardware, kubuntu feisty. I will do some tests to see if killing NM first will resolve this. This is not the first NM bug with this driver that i have noticed. The nice thing about this bug is that it is easy to reproduce. Also i have notice that failure rate has risen to ~50% PS Sorry for the top post on that last message -- Brennan Ashton Bellingham, Washington "The box said, 'Requires Windows 98 or better'. So I installed Linux" ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: Odd network locking
On Saturday 04 August 2007 07:12:46 Brennan Ashton wrote: > When the bcm43xx_mac80211 driver stops communicating, and needs to be > reset (this seems to happens when coming from strong to week to strong > signal area quickly) i have been rmmod and then modprobing it. this > works most of the time, but some times (~20%), it will lock up the > network with this error that repeats. > > Message from [EMAIL PROTECTED] at Fri Aug 3 00:55:41 2007 ... > localhost kernel: [19316.256549] unregister_netdevice: waiting for eth1 to > becom e free. Usage count = 5 > > usage count varies, but renders the system unusable (extremely slow, > like when localhost is not defined) until the laptop is turned off, > the system will hang during shutdown requiring a power interrupt. > This did not happen with the bcm43xx driver in 2.6.22-rc7. > I've seen this while testing the 4301 driver (also mac80211). I do not get it when booting into recovery mode, but is 100% reproducible when booting into X. A guess is that networkmanager is involved in it. I am also pretty sure that "Usage count" equals the number of times the driver has been reloaded. I can shut down fine when I've not reloaded the module. My specs: 2.6.23-rc1+bcm4301 driver, 4311 hardware, kubuntu feisty. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: Odd network locking
On Fri, 2007-08-03 at 22:12 -0700, Brennan Ashton wrote: > When the bcm43xx_mac80211 driver stops communicating, and needs to be > reset (this seems to happens when coming from strong to week to strong > signal area quickly) i have been rmmod and then modprobing it. this > works most of the time, but some times (~20%), it will lock up the > network with this error that repeats. > > Message from [EMAIL PROTECTED] at Fri Aug 3 00:55:41 2007 ... > localhost kernel: [19316.256549] unregister_netdevice: waiting for eth1 to > becom > e free. Usage count = 5 > > usage count varies, but renders the system unusable (extremely slow, > like when localhost is not defined) until the laptop is turned off, > the system will hang during shutdown requiring a power interrupt. > This did not happen with the bcm43xx driver in 2.6.22-rc7. I was about to suggest it could be caused by the deadlock Michael just found and fixed, but that happens under rtnl so it can't be. Can you get a process dump? echo t > /proc/sysrq-trigger or just pressing sysrq-t johannes signature.asc Description: This is a digitally signed message part ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Odd network locking
When the bcm43xx_mac80211 driver stops communicating, and needs to be reset (this seems to happens when coming from strong to week to strong signal area quickly) i have been rmmod and then modprobing it. this works most of the time, but some times (~20%), it will lock up the network with this error that repeats. Message from [EMAIL PROTECTED] at Fri Aug 3 00:55:41 2007 ... localhost kernel: [19316.256549] unregister_netdevice: waiting for eth1 to becom e free. Usage count = 5 usage count varies, but renders the system unusable (extremely slow, like when localhost is not defined) until the laptop is turned off, the system will hang during shutdown requiring a power interrupt. This did not happen with the bcm43xx driver in 2.6.22-rc7. Current Data [EMAIL PROTECTED] ~]# uname -r 2.6.23-rc1 [EMAIL PROTECTED] ~]# lspci | grep Broadcom 03:00.0 Network controller: Broadcom Corporation Dell Wireless 1390 WLAN Mini-PCI Card (rev 01) dmesg is over filled with TKIP decrypt info, so little info is there [EMAIL PROTECTED] ~]# iwlist eth1 scanning Warning: Driver for device eth1 has been compiled with version 22 of Wireless Extension, while this program supports up to version 20. Some things may be broken... eth1 Scan completed : Cell 01 - Address: 00:12:17:AA:84:67 ESSID:"thishome" Mode:Master Channel:6 Frequency:2.437 GHz (Channel 6) Quality=41/100 Signal level=-61 dBm Noise level=-68 dBm Encryption key:on IE: WPA Version 1 Group Cipher : TKIP Pairwise Ciphers (1) : TKIP Authentication Suites (1) : PSK Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s 24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s 12 Mb/s; 48 Mb/s Extra:tsf=0298702da2c8 Cell 02 - Address: 00:18:3F:64:47:D9 ESSID:"2WIRE199" Mode:Master Channel:6 Frequency:2.437 GHz (Channel 6) Quality=31/100 Signal level=-77 dBm Noise level=-68 dBm Encryption key:on Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s 48 Mb/s; 54 Mb/s Extra:tsf=00401364c181 Cell 03 - Address: 00:03:52:C7:E3:B0 ESSID:"bbx" Mode:Master Channel:11 Frequency:2.462 GHz (Channel 11) Quality=27/100 Signal level=-83 dBm Noise level=-68 dBm Encryption key:off Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s Extra:tsf=02711d4b -- Brennan Ashton Bellingham, Washington "The box said, 'Requires Windows 98 or better'. So I installed Linux" ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
