On 06/23/2012 07:50 PM, Jonathan Nieder wrote: > Hi again, > > Camaleón wrote[1]: >> 2012/6/19 Jonathan Nieder <jrnieder@xxxxxxxxx>: >>> Camaleón wrote: > >>>> Update: I've been running kernel 3.2.2-1 over 4 days (since last >>>> Saturday until today) and still haven't experienced any disconnection. >>> >>> Interesting. I wonder if the workaround in f96b08a7e6f6 (brcmsmac: >>> fix tx queue flush infinite loop, 2012-01-17) has too short a timeout >>> and is backfiring. >> >> Mmm... >> >>> How about this patch, for 3.2.y kernels? I suggest the following >>> steps for testing: >> >> (...) >> >> Thanks for the detailed steps. >> >> I've planned to start debugging over the weekend because I have more >> spare time for this but the last (yesterday?) set of updates for >> wheezy have left the system in a very bad shape. Is not only that N-M >> is reconnecting very often (!) but gnome-shell and mail-notification >> are segfaulting as crazy horses. >> >> I'm attaching the syslog. >> >> There is also a "new" segfault coming from "net/wireless/mlme.c" (I >> say "new" because I don't recall this file was involved in the past >> :-?) so given the current state of the system I'm a bit reluctant of >> running more test at least for now. Let's see if an upcoming update >> restores the sanity to the system. I'll keep you informed. > > Just realized upstream was not in the cc. Moving to there. > > If I understand correctly, these symptoms are similar to those you > experienced with 3.2.9-1. So there is no reason to believe > f96b08a7e6f6 is the source of the trouble after all. The problem must > originate somewhere else. Right? > > Syslog at [1]. > > Thanks, > Jonathan > > [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=230;bug=664767 > > [...] >> Jun 23 12:43:28 stt300 kernel: [ 0.000000] Linux version 3.2.0-1-686-pae (Debian 3.2.2-1) (ben@xxxxxxxxxxxxxxx) (gcc version 4.6.2 (Debian 4.6.2-12) ) #1 SMP Wed Feb 1 09:39:41 UTC 2012 > [...] >> Jun 23 12:44:37 stt300 NetworkManager[1478]: <info> Activation (wlan0/wireless): connection 'WLAN_B5' has security, and secrets exist. No new secrets needed. > [...] >> Jun 23 12:44:38 stt300 kernel: [ 88.476883] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready > [...] >> Jun 23 12:44:40 stt300 dhclient: bound to 192.168.0.150 -- renewal in 123164 seconds. > [...] >> Jun 23 12:59:05 stt300 wpa_supplicant[1514]: wlan0: WPA: Group rekeying completed with 00:23:f8:9d:ad:11 [GTK=TKIP] > [...] >> Jun 23 13:14:41 stt300 wpa_supplicant[1514]: wlan0: WPA: Key negotiation completed with 00:23:f8:9d:ad:11 [PTK=TKIP GTK=TKIP] > [...] >> Jun 23 13:29:05 stt300 wpa_supplicant[1514]: wlan0: WPA: Group rekeying completed with 00:23:f8:9d:ad:11 [GTK=TKIP] > [...] >> Jun 23 13:41:44 stt300 kernel: [ 3513.868441] ieee80211 phy0: brcms_ops_bss_info_changed: qos enabled: false (implement) >> Jun 23 13:41:44 stt300 kernel: [ 3513.868462] ieee80211 phy0: brcmsmac: brcms_ops_bss_info_changed: disassociated >> Jun 23 13:41:44 stt300 kernel: [ 3513.868478] ieee80211 phy0: brcms_ops_bss_info_changed: arp filtering: enabled false, count 1 (implement) >> Jun 23 13:41:45 stt300 wpa_supplicant[1514]: wlan0: CTRL-EVENT-DISCONNECTED bssid=00:23:f8:9d:ad:11 reason=4 This means AP is not receiving anything from this machine. >> Jun 23 13:41:45 stt300 kernel: [ 3514.806036] cfg80211: Calling CRDA to update world regulatory domain > [...] >> Jun 23 13:41:45 stt300 kernel: [ 3514.825799] cfg80211: Calling CRDA for country: ES >> Jun 23 13:41:45 stt300 kernel: [ 3514.840865] cfg80211: Regulatory domain changed to country: ES > [...] I am curious how the system would behave if you select US instead ES country. Gr. AvS -- 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
