You are not logged in.
Anyone any clues why this is so - it *would* have to be Linux for Workgroups .
Downgrading to 3.10.10-1 makes the device work again:
Device is:
01:00.0 Network controller: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe
dmesg output:
[ 4.949297] wlp1s0f0: authenticate with 5c:7d:5e:de:b6:04
[ 4.961762] wlp1s0f0: send auth to 5c:7d:5e:de:b6:04 (try 1/3)
[ 4.963279] wlp1s0f0: authenticated
[ 4.964933] wlp1s0f0: associate with 5c:7d:5e:de:b6:04 (try 1/3)
[ 4.970465] wlp1s0f0: RX AssocResp from 5c:7d:5e:de:b6:04 (capab=0x431 status=0 aid=1)
[ 4.970563] wlp1s0f0: associated
[ 28.285869] fuse init (API version 7.22)
[ 29.967936] EXT4-fs (sda3): re-mounted. Opts: data=ordered,commit=0
[ 29.983555] EXT4-fs (sda1): re-mounted. Opts: data=ordered,commit=0
[ 30.020684] EXT4-fs (sda4): re-mounted. Opts: data=ordered,commit=0
[ 31.468349] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
[ 32.031587] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
[ 32.058518] cfg80211: Calling CRDA for country: GB
[ 32.264907] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
[ 32.398225] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
[ 33.482380] wlp1s0f0: authenticate with 5c:7d:5e:de:b6:04
[ 33.621406] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
[ 33.628168] wlp1s0f0: send auth to 5c:7d:5e:de:b6:04 (try 1/3)
[ 34.324623] wlp1s0f0: send auth to 5c:7d:5e:de:b6:04 (try 2/3)
[ 35.324464] wlp1s0f0: send auth to 5c:7d:5e:de:b6:04 (try 3/3)
[ 36.334424] wlp1s0f0: authentication with 5c:7d:5e:de:b6:04 timed out
[ 36.504382] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
[ 37.137655] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
[ 37.270932] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
The patch that fixes this issue http://marc.info/?l=linux-wireless&m=13 … 815360&w=2 has been applied to the 3.12 kernel which has hit the core package repo.
Last edited by prawn (2013-11-19 06:59:05)
Offline
It looks like every network adaptor will have some off-time sooner or later.
Offline
Same problem here. Downgrading did not solve the problem though.
The device I use is Network controller: Ralink corp. RT2500 Wireless 802.11bg (rev 01)
Using Linux archlinux 3.10.7-1 I met this error over and over :
Sep 18 15:46:59 localhost wicd[13607]: dhcpcd[21484]: dhcpcd not running
Sep 18 15:46:59 localhost dhcpcd[21484]: dhcpcd not running
Sep 18 15:47:00 localhost kernel: [ 7009.185486] forcedeth 0000:00:07.0: irq 44 for MSI/MSI-X
Sep 18 15:47:00 localhost kernel: [ 7009.185521] forcedeth 0000:00:07.0 eth0: MSI enabled
Sep 18 15:47:00 localhost kernel: [ 7009.185737] forcedeth 0000:00:07.0 eth0: no link during initialization
Sep 18 15:47:00 localhost kernel: [ 7009.187162] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep 18 15:47:00 localhost wicd[13607]: Failed to connect to non-global ctrl_ifname: eth0 error: No such file or directory
Sep 18 15:47:02 localhost ntpd[339]: Deleting interface #10 wlan0, fe80::212:17ff:fe83:3baa#123, interface stats: received=0, sent=0, dropped=0, active_time=131 secs
Sep 18 15:47:02 localhost ntpd[339]: Deleting interface #9 wlan0, 192.168.0.5#123, interface stats: received=5, sent=6, dropped=0, active_time=131 secs
Sep 18 15:47:02 localhost ntpd[339]: 212.83.133.52 interface 192.168.0.5 -> (none)
Sep 18 15:47:02 localhost ntpd[339]: 91.121.92.90 interface 192.168.0.5 -> (none)
Sep 18 15:47:02 localhost ntpd[339]: 5.9.67.110 interface 192.168.0.5 -> (none)
Sep 18 15:47:02 localhost ntpd[339]: peers refreshed
Sep 18 15:47:04 localhost kernel: [ 7014.049852] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
And from time to time this
Sep 18 15:56:26 localhost kernel: [ 7575.585972] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
I'm gonna try to "upgrade" to 3.10.10-1 as prawn suggested in order to check if the issue is still there for me. Thus, this is extremely annoying. I believe it could also be wicd related, or initscript/initsysv/systemd related, according to what I've found looking on google.
Last edited by Fl0w3D (2013-09-18 13:59:22)
Offline
Exactly the same issue here guys, I'm on a 3.11.1 kernel as well (debian and wicd though, not arch). It's either something with the kernel or wicd, yet I don't believe wicd was upgraded for me lately...
*EDIT*: kernel bug tracker: https://bugzilla.kernel.org/show_bug.cgi?id=61621
Last edited by Aktau (2013-09-18 14:59:38)
Github: http://github.com/aktau
Offline
For what it's worth, I'm using NetworkManager and not wicd nor netctl - it may make for an unusual case in the Arch realm, or not be germaine.
Offline
For what it's worth, I'm using NetworkManager and not wicd nor netctl - it may make for an unusual case in the Arch realm, or not be germaine.
Since I use debian wheezy (7), and wicd, I think we've narrowed it down to a new kernel release then. (I use wicd, but you don't, and we both have the error with 3.11.1)
Github: http://github.com/aktau
Offline
prawn wrote:For what it's worth, I'm using NetworkManager and not wicd nor netctl - it may make for an unusual case in the Arch realm, or not be germaine.
Since I use debian wheezy (7), and wicd, I think we've narrowed it down to a new kernel release then. (I use wicd, but you don't, and we both have the error with 3.11.1)
OK. I would agree with that sentiment. Just getting the facts out there
Offline
By the way, I would like to request everyone that has this problem to please add yourself to the cc list on the kernel bug tracker, that should illustrate better that this is a common issue for everyone with the chipset and might make it a higher priority.
You can do it here: https://bugzilla.kernel.org/show_bug.cgi?id=61621
Github: http://github.com/aktau
Offline
Note that in my case, downgrading to an older kernel (I tried 3.10.10-1, 3.10.9-1, 3.10.7-1) does not fix the problem. The issue is kinda the same than the one who appeared in the kernel 2 years ago (with rt2500/rt2x00 drivers). Back in these days, the result of the bug was a kernel panic, though.
Offline
For those not following the thread here: https://bugzilla.kernel.org/show_bug.cgi?id=61621
The following patch to the 3.11.n source code fixes the issue:
diff --git a/drivers/net/wireless/rt2x00/rt2x00pci.c b/drivers/net/wireless/rt2x00/rt2x00pci.c
index 76d95de..dc49e52 100644
--- a/drivers/net/wireless/rt2x00/rt2x00pci.c
+++ b/drivers/net/wireless/rt2x00/rt2x00pci.c
@@ -105,13 +105,11 @@ int rt2x00pci_probe(struct pci_dev *pci_dev, const struct rt2x00_ops *ops)
goto exit_release_regions;
}
- pci_enable_msi(pci_dev);
-
hw = ieee80211_alloc_hw(sizeof(struct rt2x00_dev), ops->hw);
if (!hw) {
rt2x00_probe_err("Failed to allocate hardware\n");
retval = -ENOMEM;
- goto exit_disable_msi;
+ goto exit_release_regions;
}
pci_set_drvdata(pci_dev, hw);
@@ -152,9 +150,6 @@ exit_free_reg:
exit_free_device:
ieee80211_free_hw(hw);
-exit_disable_msi:
- pci_disable_msi(pci_dev);
-
exit_release_regions:
pci_release_regions(pci_dev);
@@ -179,8 +174,6 @@ void rt2x00pci_remove(struct pci_dev *pci_dev)
rt2x00pci_free_reg(rt2x00dev);
ieee80211_free_hw(hw);
- pci_disable_msi(pci_dev);
-
/*
* Free the PCI device data.
*/
This patch has been sent to the 3.12 kernel for inclusion: http://marc.info/?l=linux-wireless&m=13 … 815360&w=2
Offline
Thank you, prawn.
I have rebuilt 3.11.5 with the patch that you referenced. Wi-Fi appears to work now.
I used to be unable to connect to any network on this new laptop. Now I can \o/
Offline