ralphy wrote: > There is also a 'kernel patch to fix the Wireless Event too big > messages' > (https://github.com/ralph-irving/squeezeos/commit/edf339db574b10c9375972029e4c8fd91942aff0) > but I still get the occasional one in /var/log/messages.
The only Wireless Event too big message that I can recall seeing is -eth1 (WE) : Wireless Event too big (33)-. '33' being the length of the offending message. Have you ever seen any others with different lengths ? I found a commented patch, otherwise identical to yours, here: https://www.spinics.net/lists/linux-wireless/msg21543.html. The relevant maximum permitted message length is -IW_CUSTOM_MAX-, which is defined to be 256. So the "Wireless Event too big" messages that I see are outside the scope of this patch. The kernel message is being sourced from here, in - wireless_send_event- (I think): https://github.com/Logitech/squeezeos/blob/585fb6501704f0ca93e2bde662ccf4f8c4c9af10/src/s3c2412/linux-2.6.22/net/wireless/wext.c#L1225 We might get a little more information by printing out the command as well, i.e. by replacing: Code: -------------------- printk(KERN_ERR "%s (WE) : Wireless Event too big (%d)\n", dev->name, wrqu->data.length); -------------------- with Code: -------------------- printk(KERN_ERR "%s (WE) : Wireless Event (cmd=0x%04X) too big (%d)\n", dev->name, cmd, wrqu->data.length); -------------------- The replacement being motivate by this patch taken up within the current kernel code: https://github.com/torvalds/linux/commit/e5f5b2fb07353de00ffde49221cffad71e2fecfe Perhaps something to slip in on a next test build. It might help track it down, even though it may not actually matter. ------------------------------------------------------------------------ mrw's Profile: http://forums.slimdevices.com/member.php?userid=38299 View this thread: http://forums.slimdevices.com/showthread.php?t=111663 _______________________________________________ Radio mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/radio
