Wireless: AP crashes with "Busy time statistics is not included into the driver"

hi there,

I have a weird problem, i've 4 notebooks and a couple of mobile phones everythings goes well untill a acer notebook with an N wireless adapter init connects to the AP30

The only thing that helps is to poweroff and poweron the accesspoint

When this happends the following situation begins in the logging

2010:11:13-11:36:24 192.168.0.100 kernel: [42470.970000] Rcv Wcid(4) AddBAReq
2010:11:13-11:36:24 192.168.0.100 kernel: [42470.970000] Start Seq = 00000000
2010:11:13-11:36:24 192.168.0.100 kernel: [42470.980000] AP SETKEYS DONE - WPA2, AuthMode(7)=WPA2PSK, WepStatus(6)=AES, GroupWepStatus(6)=AES
2010:11:13-11:36:24 192.168.0.100 kernel: [42470.980000]
2010:11:13-11:36:27 192.168.0.100 kernel: [42474.950000] Busy time statistics is not included into the driver!
2010:11:13-11:36:27 192.168.0.100 kernel: [42474.950000]
2010:11:13-11:36:28 192.168.0.100 kernel: [42475.950000] Busy time statistics is not included into the driver!
2010:11:13-11:36:28 192.168.0.100 kernel: [42475.950000]
2010:11:13-11:36:32 192.168.0.100 kernel: [42479.950000] Busy time statistics is not included into the driver!
2010:11:13-11:36:32 192.168.0.100 kernel: [42479.950000]
2010:11:13-11:36:34 192.168.0.100 kernel: [42481.040000] Qidx(0), not enough space in MgmtRing, MgmtRingFullCount=1!
2010:11:13-11:36:34 192.168.0.100 kernel: [42481.040000] Qidx(0), not enough space in MgmtRing, MgmtRingFullCount=2!
2010:11:13-11:36:34 192.168.0.100 kernel: [42481.040000] Qidx(0), not enough space in MgmtRing, MgmtRingFullCount=3!
2010:11:13-11:36:34 192.168.0.100 kernel: [42481.040000] Qidx(0), not enough space in MgmtRing, MgmtRingFullCount=4!
2010:11:13-11:36:34 192.168.0.100 kernel: [42481.040000] Qidx(0), not enough space in MgmtRing, MgmtRingFullCount=5!
2010:11:13-11:36:34 192.168.0.100 kernel: [42481.040000] Qidx(0), not enough space in MgmtRing, MgmtRingFullCount=6!
2010:11:13-11:36:34 192.168.0.100 kernel: [42481.040000] Qidx(0), not enough space in MgmtRing, MgmtRingFullCount=7!
2010:11:13-11:36:34 192.168.0.100 kernel: [42481.040000] Qidx(0), not enough space in MgmtRing, MgmtRingFullCount=8!
2010:11:13-11:36:34 192.168.0.100 kernel: [42481.540000] Qidx(0), not enough space in MgmtRing, MgmtRingFullCount=9!
2010:11:13-11:36:34 192.168.0.100 kernel: [42481.540000] Qidx(0), not enough space in MgmtRing, MgmtRingFullCount=10!
2010:11:13-11:36:34 192.168.0.100 kernel: [42481.540000] Qidx(0), not enough space in MgmtRing, MgmtRingFullCount=11!
2010:11:13-11:36:34 192.168.0.100 kernel: [42481.540000] Qidx(0), not enough space in MgmtRing, MgmtRingFullCount=12!
2010:11:13-11:36:34 192.168.0.100 kernel: [42481.540000] Qidx(0), not enough space in MgmtRing, MgmtRingFullCount=13!
2010:11:13-11:36:34 192.168.0.100 kernel: [42481.540000] Qidx(0), not enough space in MgmtRing, MgmtRingFullCount=14!
2010:11:13-11:36:34 192.168.0.100 kernel: [42481.540000] Qidx(0), not enough space in MgmtRing, MgmtRingFullCount=15!
2010:11:13-11:36:34 192.168.0.100 kernel: [42481.540000] Qidx(0), not enough space in MgmtRing, MgmtRingFullCount=16!
2010:11:13-11:36:34 192.168.0.100 kernel: [42481.540000] Qidx(0), not enough space in MgmtRing, MgmtRingFullCount=17!
2010:11:13-11:36:34 192.168.0.100 kernel: [42481.540000] Qidx(0), not enough space in MgmtRing, MgmtRingFullCount=18!
2010:11:13-11:36:34 192.168.0.100 kernel: [42481.540000] Qidx(0), not enough space in MgmtRing, MgmtRingFullCount=19!
2010:11:13-11:36:34 192.168.0.100 kernel: [42481.540000] Qidx(0), not enough space in MgmtRing, MgmtRingFullCount=20!
2010:11:13-11:36:34 192.168.0.100 kernel: [42481.540000] Qidx(0), not enough space in MgmtRing, MgmtRingFullCount=21!
2010:11:13-11:36:34 192.168.0.100 kernel: [42481.540000] Qidx(0), not enough space in MgmtRing, MgmtRingFullCount=22!
2010:11:13-11:36:34 192.168.0.100 kernel: [42481.540000] Qidx(0), not enough space in MgmtRing, MgmtRingFullCount=23!
2010:11:13-11:36:34 192.168.0.100 kernel: [42481.540000] Qidx(0), not enough space in MgmtRing, MgmtRingFullCount=24!
2010:11:13-11:36:34 192.168.0.100 kernel: [42481.540000] Qidx(0), not enough space in MgmtRing, MgmtRingFullCount=25!
2010:11:13-11:36:34 192.168.0.100 kernel: [42481.540000] Qidx(0), not enough space in MgmtRing, MgmtRingFullCount=26!
2010:11:13-11:36:34 192.168.0.100 kernel: [42481.540000] Qidx(0), not enough space in MgmtRing, MgmtRingFullCount=27!
2010

what can i do

Parents

0 tom_01 over 14 years ago

This looks like a problem we already saw with one other client. We have an alternative firmware which supposedly fixes this problem. We'll provide more information on Monday.

In the meantime, can you find out which wireless N-Chipset (i.e. which manufacturer) is used in the Acer?

thanks,

/tom
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Rudie over 14 years ago in reply to tom_01

Hereby the information about the notebook and the adapter thats inside

Notebook: AcerAspire: 5735Z
type wireless adaptor: atheros AR5B91
Driver version Vista 7.6.0.172

Hardware-ids
PCI\VEN_168C&DEV_002A&SUBSYS_E006105B&REV_01
PCI\VEN_168C&DEV_002A&SUBSYS_E006105B
PCI\VEN_168C&DEV_002A&CC_028000
PCI\VEN_168C&DEV_002A&CC_0280

I hope that this is enough information, if not please contact me

rudie,
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 snowcrash_01 over 14 years ago in reply to Rudie

I almost get the same error:

2010:11:14-18:40:05 ap30-wz kernel: [69989.890000] Busy time statistics is not included into the driver!

Asus EeePC 1201HA
Atheros AR9285 Wireless Network Adapter
PCI\VEN_168&DEV_002B&SUBSYS_10891A3B&REV_01
PCI\VEN_168&DEV_002B&SUBSYS_10891A3B
PCI\VEN_168&DEV_002B&CC_028000
PCI\VEN_168&DEV_002B&CC_0280
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 hschaa over 14 years ago in reply to snowcrash_01
Attached is a new AP firmware that is likely to fix some of these issues. However, we're unsure if we identified the root cause correctly.

Rudie, would it be possible to install the attached test firmware and try if the behavior improves (you'll have to wait a few minutes for the firmware update to proceed)?

rpm -Uhv ep-wireless-firmware-35-0.55257942.g0ebeed4_HT40test.i686.rpm
/var/mdw/scripts/awed restart

JFI: The firmware is meant for 8.100 and wasn't tested on 7.508. Still, the firmware is experimental and should automatically get replaced with a new firmware during the next Up2Date.

Thanks,
Helmut
ep-wireless-firmware-35-0.55257942.g0ebeed4_HT40test.i686.rpm
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Rudie over 14 years ago in reply to hschaa

Hi i will test this as soon as possible,

I will get that laptop at my place this week to test this

I will let you know
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Rudie over 14 years ago in reply to Rudie

Hereby the log after the patch. It solved the problem the first rules where without the notebook ON (19:10:18) from the moment that the notebook was turned on (19:10:42)
It goes wrong

The patch was applied at (19:11:10)

At (19:18:11) i rebooted the notebooks wich has the troubles and no problems anymore. So the patch is succesfull

Attached : wireless.zip with the shortend log file

wireless.zip
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 Rudie over 14 years ago in reply to Rudie

Hereby the log after the patch. It solved the problem the first rules where without the notebook ON (19:10:18) from the moment that the notebook was turned on (19:10:42)
It goes wrong

The patch was applied at (19:11:10)

At (19:18:11) i rebooted the notebooks wich has the troubles and no problems anymore. So the patch is succesfull

Attached : wireless.zip with the shortend log file

wireless.zip
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

0 hschaa over 14 years ago in reply to Rudie

Thanks for testing Rudie. If you encounter the same issue with the patched firmware again please report back.

Thanks,
Helmut
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel