On Thu, Apr 24, 2014 at 09:45:37AM -0700, John Tobias wrote: > How did you know that by downgrading the firmware the problem has > been solved?. Did you see a scenario or flow in the driver that both > occurred when using the two different firmware but able to work on > the p80?. I knew it had been solved because the problem stopped happening, whereas before it would always happen. No, there was nothing in the driver changed, and nothing I could see in the driver had any effect on the problem. > The reason why I am asking is because sometimes the bug/s did not > occur often. We are probably facing different problems. For the problem I am working, it always happens, all I have to do is boot 14 or more laptops. The sequence is: - the automatic starting or joining of an ad-hoc network, by the Sugar learning software, - a stream of 13 adhoc station connect events from the card, one for each station in the network, - at about the point that the 14th beacon is seen on RF, the card firmware hangs, - a command is sent by the host (e.g. to get RSSI to update the display), - no interrupt occurs, and so the mwifiex driver reports a command timeout. http://dev.laptop.org/ticket/12763 has some of the details. I have an instrumented kernel that reports the adhoc station connect and disconnect events, and counts the number of stations that the card knows about. There's some sort of timer used by the card to issue the adhoc station disconnect event; when no beacons from the station have been heard for a few seconds. So increasing the beacon interval to 10000 TU also avoided the problem. I doubt your problem is caused by firmware, but you could test for it. -- James Cameron http://quozl.linux.org.au/ -- 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
