I'm also seeing this issue in a fresh install (not an upgrade) of Jaunty (xubuntu). The same laptop and wireless router didn't have this issue with hardy.
Post 21 https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/331103/comments/21 seems to be the most consistent with what I'm seeing as well. During times of heavy network traffic - **specifically over the internet** - the connection will stop working. Oddly enough I can still do things with other local machines (ssh, scp, etc) over wireless which is really strange and seems like a gateway routing issue (though my routing table is normal). The other machines have no trouble getting to the internet during that time.
The dmesg log will show:
iwlagn 0000:02:00.0: iwl_tx_agg_start on ra = 00:21:91:f7:5a:56 tid = 0
iwlagn 0000:02:00.0: HW queue is empty
If I wait a little while it will start working again. My NIC is an Intel PRO/Wireless 5100 AGN. I tried updating the kernel to 2.6.30 and while it runs great everywhere else, this issue still occurs. I feel like it's a nm-applet issue but not for certain.
I'm also seeing this issue in a fresh install (not an upgrade) of Jaunty (xubuntu). The same laptop and wireless router didn't have this issue with hardy.
Post 21 https:/ /bugs.launchpad .net/ubuntu/ +source/ network- manager/ +bug/331103/ comments/ 21 seems to be the most consistent with what I'm seeing as well. During times of heavy network traffic - **specifically over the internet** - the connection will stop working. Oddly enough I can still do things with other local machines (ssh, scp, etc) over wireless which is really strange and seems like a gateway routing issue (though my routing table is normal). The other machines have no trouble getting to the internet during that time.
The dmesg log will show:
iwlagn 0000:02:00.0: iwl_tx_agg_start on ra = 00:21:91:f7:5a:56 tid = 0
iwlagn 0000:02:00.0: HW queue is empty
If I wait a little while it will start working again. My NIC is an Intel PRO/Wireless 5100 AGN. I tried updating the kernel to 2.6.30 and while it runs great everywhere else, this issue still occurs. I feel like it's a nm-applet issue but not for certain.