Question, and I appologise if this is not the right way to address this!
Bug 356807 says that it is a duplicate for this one (373680), however, I do not experience any latency in my network, but my log is spammed with rt_ioctl_giwscan messages every 2 minutes
I got rid of those by removing -DDBG parameter in the make file.
I can see that there is a relation to the network scanning every 2 minutes and the entry of the rt_ioctl_.... message in the log. But when reading the comments here, it seems that the messages in the log are dependent on how the chipset reacts to the root cause (every 2 minutes network scan)
Wouldn't it make sense to uncouple the two bug numbers?
I'm on kernel 2.6.32-24-generic
using ralink rt3572sta chipset (this happens with drivers v2.3.0.0 and the latest v2.4.0.1)
Question, and I appologise if this is not the right way to address this!
Bug 356807 says that it is a duplicate for this one (373680), however, I do not experience any latency in my network, but my log is spammed with rt_ioctl_giwscan messages every 2 minutes
I got rid of those by removing -DDBG parameter in the make file.
I can see that there is a relation to the network scanning every 2 minutes and the entry of the rt_ioctl_.... message in the log. But when reading the comments here, it seems that the messages in the log are dependent on how the chipset reacts to the root cause (every 2 minutes network scan)
Wouldn't it make sense to uncouple the two bug numbers?
I'm on kernel 2.6.32-24-generic
using ralink rt3572sta chipset (this happens with drivers v2.3.0.0 and the latest v2.4.0.1)