[Bug 267063] Re: iwl4965 - wireless event too big (366) and 2.6.27-2 regression

mvdberg112 sp1471 at zonnet.nl
Sat Apr 25 15:04:45 UTC 2009


This Linux system has also the "event too big message"

[344969.732039] wlan0: No ProbeResp from current AP 00:0c:e6:fe:02:02 - assume out of range
[344972.965475] wlan0: authenticate with AP 00:0c:e6:fe:02:02
[344973.146432] wlan0: authenticate with AP 00:0c:e6:fe:02:02
[344973.344028] wlan0: authenticate with AP 00:0c:e6:fe:02:02
[344973.490484] wlan0: authenticated
[344973.490497] wlan0: associate with AP 00:0c:e6:fe:02:02
[344973.496606] wlan0: deauthenticated
[344974.496030] wlan0: authenticate with AP 00:0c:e6:fe:02:02
[344974.619355] wlan0: authenticated
[344974.619369] wlan0: associate with AP 00:0c:e6:fe:02:02
[344974.622374] wlan0: RX ReassocResp from 00:0c:e6:fe:02:02 (capab=0x1 status=0 aid=2)
[344974.622383] wlan0: associated
[344974.622429] wlan0 (WE) : Wireless Event too big (294)
[345889.764040] wlan0: No ProbeResp from current AP 00:0c:e6:fe:02:02 - assume out of range
[345893.005372] wlan0: authenticate with AP 00:0c:e6:fe:02:02
[345893.189332] wlan0: authenticate with AP 00:0c:e6:fe:02:02
[345893.190724] wlan0: authenticated
[345893.190734] wlan0: associate with AP 00:0c:e6:fe:02:02
[345893.193084] wlan0: RX ReassocResp from 00:0c:e6:fe:02:02 (capab=0x1 status=0 aid=2)
[345893.193092] wlan0: associated
[345893.193141] wlan0 (WE) : Wireless Event too big (314)

(1) Ubuntu Intrepid 8.10
(2) wireless USB: Netgear WG111v2
(3) driver rtl8187 (automatically included in the upgrade Intrepid and loaded automatically)

What I understand from the whole thread that it is possible to make the
message go away under particular conditions, but nobody explains what
the message really means. In which case would the kernel say "event too
big"? Does any developer know that? Is there  a way that we can see the
"too big" message? For example, with a test kernel.

-- 
iwl4965 - wireless event too big (366) and 2.6.27-2 regression
https://bugs.launchpad.net/bugs/267063
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.




More information about the kernel-bugs mailing list