WiFi data corruption?

[shoragan]

While investigating why the WiFi connection to my plug became flakey very suddenly, i discovered this:

Code:

$ ping -n 192.168.128.3
PING 192.168.128.3 (192.168.128.3) 56(84) bytes of data.
64 bytes from 192.168.128.3: icmp_seq=1 ttl=64 time=10.1 ms
wrong data byte #50 should be 0x32 but was 0x40
#16 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f
#48 30 31 40 38 89 db 0 0
64 bytes from 192.168.128.3: icmp_seq=2 ttl=64 time=5.13 ms
64 bytes from 192.168.128.3: icmp_seq=3 ttl=64 time=4.52 ms
wrong data byte #50 should be 0x32 but was 0x40
#16 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f
#48 30 31 40 38 89 db 0 0
64 bytes from 192.168.128.3: icmp_seq=4 ttl=64 time=4.69 ms
64 bytes from 192.168.128.3: icmp_seq=5 ttl=64 time=4.80 ms
wrong data byte #50 should be 0x32 but was 0x40
#16 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f
#48 30 31 40 38 89 db 0 0
64 bytes from 192.168.128.3: icmp_seq=6 ttl=64 time=3.05 ms

Some packet sizes are ok, others fail at the same offest. The plug operates as a client to my AVM FritzBox AP. I verified the problem using a different PC, where i got the same errors. After starting some programs on the plug, the error went away.

Did anyone else see errors like this?

[demus]

I see the same behaviour on my guruplug plus. Every second ping returns "wrong data byte #50 should be 0x32 but was 0x00".

Either the driver is garbage, or the wifi becomes unstable when the plug heats up.

A good part of the kernel OOPS' I get also relate to libertas.ko.

[stefba]

Same issues here for me. Which kernel do you use?