Hi Oleksij, When the chipset goes into sleep mode and cannot come back due to errors like "Chip reset failed", we do not get any traffic inflow or outflow on that interface.
Is it safe to assume that when no traffic is visible on that interface, we can restart that interface. Is there any way to check that the device is in that particular failed state? ip link, ip addr, ifconfig all show that the link is UP, but tcpdump does not show any traffic. Regards, On 03/31/2014 02:40 PM, Harshal Vora wrote: > Hi Oleksij, > > I compared the initial few commits from wireless-testing repo with > 3.13.y branch of raspberry linux git repo. Seems like all of those > have been merged. > > I also specifically checked commits only for > /drivers/net/wireless/ath/ath9k folder and seems like they are also > present in the raspberry linux repo. > > So I assume all the changes should be there. > > If issues persist, then I will test with the wireless-testing repo as > well. > > Thanks, > Regards, > > On 03/31/2014 01:52 PM, Oleksij Rempel wrote: >> Am 31.03.2014 10:06, schrieb Harshal Vora: >>> Hi Oleksij, >>> >>> We will test with kernel version 3.13.7 and also the latest firmware. >> I assume we misunderstand each other. FW will work with older kernel >> versions and some bugs are fixed in 3.13. But only wireless-testing.git >> can detect some FW oopses, and has changes which may affect AdHock >> mode. >> I recommend you to use wireless-testing.git or at least try to >> cherry-peak this changes. >> > _______________________________________________ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
