Bug 14073
Summary: | mouse pointer begins to drift left under high wifi load (IRQ problem?) | ||
---|---|---|---|
Product: | Drivers | Reporter: | Rolf Leggewie (bugzilla.kernel.org) |
Component: | network-wireless | Assignee: | drivers_network-wireless (drivers_network-wireless) |
Status: | CLOSED INSUFFICIENT_DATA | ||
Severity: | normal | CC: | linville, nhorman |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://bugs.launchpad.net/ubuntu/+source/linux/+bug/334957 | ||
Kernel Version: | 2.6.31 | Subsystem: | |
Regression: | No | Bisected commit-id: |
Description
Rolf Leggewie
2009-08-27 14:05:09 UTC
my wifi connection is wlan2, but there is also a wifi0 interface. The latter does not have an IP associated with it. And frankly, I'm not sure where it comes from and what it's supposed to do. Both wifi0 and wlan2 do disappear when I pull the CF card out of its socket. dmesg has a lot of lines of the form [ 5918.062172] Virtual device wifi0 asks to queue packet! Out of curiousity, can you revert 5ae4efbcd2611562a8b93596be034e63495706a5 and see if that changes anything? John, thank you for your comment. I'll compile a kernel later today and see how that goes. FWIW, March does coincide with the time I first experienced this. But I believe, I've also seen this with hardy which would make that commit an unlikely candidate in case this is a regression. I'll let you know about the results. Another observation I made. It seems that both high throughput and low signal strength exacerbate the issue. IOW, it's more likely and will have a stronger effect when the wifi bandwidth to the AP is saturated or close to it. My compilations weren't so successful, most of the time the compilation would just fail. And if it didn't, there was some other problem with the kernel like it not driving the Zonet Wifi card at all for some reason. Eventually, I gave up compiling but resorted to another solution. Ubuntu mainline kernel go back to February, the commit was made in March. I verified that the effect exists in vmlinuz-2.6.28-02062808-generic and vmlinuz-2.6.27-02062714-generic as well. Both were compiled before 5ae4efbcd2611562a8b93596be034e63495706a5 was committed. If that commit has anything to do with it, there'd have to be at least one other piece to the puzzle. I downloaded the kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline. It did feel like the effect was not as strong with the two old kernels. But that could be highly subjective and the speed of the drift depends on a lot of factors, it seems. Hmmm...this is an old one. Does the problem persist with current (i.e. 2.6.33 or later) kernels? Closing due to lack of response... |