[gutsy]network-manager drops connection when transfering large files

Bug #146586 reported by Matthew Specker
16
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Invalid
Low
Unassigned

Bug Description

After recent gutsy update network-manager started dropping connection. Only occurs when streaming music or movies from another computer via NFS. System is Dell 1420n (intel wireless).

Revision history for this message
Daniel Karlsson (dannioni) wrote :

I belive I have the same problem, when trying to update with adept the connection was dropped. My wireless card is AR5007EG which i use with ndiswrapper 1.48. Do you use ndiswrapper too?

Revision history for this message
Matthew Specker (matthew-specker) wrote :

Anytime I do a large file transfer everything locks up. The last syslog lines are as follows:
Sep 29 12:18:12 notebook NetworkManager: <WARN> nm_device_802_11_wireless_get_essid(): error getting ESSID for device eth1: Resource temporarily unavailable
Sep 29 12:18:12 notebook kernel: [ 1155.324000] ipw3945: Error sending LEDS_CMD: time out after 500ms.
Sep 29 12:18:13 notebook kernel: [ 1155.824000] ipw3945: Error sending LEDS_CMD: time out after 500ms.
Sep 29 12:18:14 notebook NetworkManager: <WARN> nm_device_802_11_wireless_get_essid(): error getting ESSID for device eth1: Resource temporarily unavailable

Revision history for this message
Matthew Specker (matthew-specker) wrote :

Fixed by switching to iwl3945 and blacklisting ipw3945.

Revision history for this message
Thom Pischke (thom-pischke) wrote :

Can confirm this, as well as note that it not only consistently crashes during large NFS transfers, but can also drop the connection with ANY heavy network activity. Using stock 1420n from Dell upgraded to gutsy.

issue157293 is probably a duplicate of this one.

Revision history for this message
Thom Pischke (thom-pischke) wrote :

more info here: bug158045

Revision history for this message
Thom Pischke (thom-pischke) wrote :
Revision history for this message
Thom Pischke (thom-pischke) wrote :

not quite the same, but possibly related, and contains some info about how to switch to iwl3945: bug 121439

Revision history for this message
Thom Pischke (thom-pischke) wrote :

And here a link to a how-to. Looks like it's written by Matthew Specker, who originated this bug report ;)

http://ubuntuforums.org/showthread.php?t=595060

Revision history for this message
Thom Pischke (thom-pischke) wrote :

Sweet, that how-to worked fine for me. I'm up on running on iwl3945. Time will tell if it proves more stable than ipw3945. Thanks Matt!

Revision history for this message
Thom Pischke (thom-pischke) wrote :

Ok, tested the iwl3945 driver for the day. Seems to work great! No problems yet. Speed is good, about 1.2 MB/s at peak, maybe a bit better.

Revision history for this message
Matthew Specker (matthew-specker) wrote :

iwl3945 has been working flawlessly for me. The ipw3945 was causing so many issues it was worthless for anything more then simple web browsing.

Revision history for this message
Daniel Karlsson (dannioni) wrote :

I might mention that i was running ndiswrapper earlier and have now switched to madwifi, and that made all my problems disappear, what drivers where you guys using?

Revision history for this message
Basilio Kublik (sourcercito) wrote :

Hi there
do you still experience this issue with the current version of the application?, could you please try to reproduce this using the live environment of the Desktop CD of the development release - Hardy Heron.

Thanks in advance

Changed in network-manager:
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!.

Changed in network-manager:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.