unregister_netdevice: waiting for eth0 to become free

Bug #89840 reported by Fernando Miguel
8
Affects Status Importance Assigned to Milestone
linux-source-2.6.20 (Ubuntu)
Fix Released
Undecided
Kyle McMartin

Bug Description

Binary package hint: linux-source-2.6.20

Most of the times that I try to shutdown my computer, after being connected to a network (may it be cable or WiFi) I get this kind of errors:

hcid[5199]: Can't connect to system message bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
hcid[5199]: Can't connect to system message bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
kernel: [37774.908000] unregister_netdevice: waiting for eth0 to become free. Usage count = 1

Revision history for this message
Fernando Miguel (fernandomiguel) wrote :

also, every time that I connect to any network, I cant hibernate.

Revision history for this message
Cristian Aravena Romero (caravena) wrote :

Thanks for taking the time to report this bug. Unfortunately we can't fix it, because your description didn't include enough information.

Please include the information requested from https://wiki.ubuntu.com/DebuggingACPI as separate attachments.

Changed in linux-source-2.6.20:
assignee: nobody → caravena
status: Unconfirmed → Needs Info
Revision history for this message
Fernando Miguel (fernandomiguel) wrote :

here are the files needed

Revision history for this message
Fernando Miguel (fernandomiguel) wrote :
Revision history for this message
Fernando Miguel (fernandomiguel) wrote :
  • vv Edit (10.9 KiB, text/plain)
Revision history for this message
Fernando Miguel (fernandomiguel) wrote :
Revision history for this message
Kyle McMartin (kyle) wrote :

Which device is "eth0" in this case? Is it the r8139 or the ipw2200 device? You can run "ethtool -i eth0" and paste the output here to tell me definitively.

Cheers, Kyle

Changed in linux-source-2.6.20:
assignee: caravena → kyle
Revision history for this message
Fernando Miguel (fernandomiguel) wrote :

both interfaces cause this problem.
When I can, I'll dump that command.

Revision history for this message
Fernando Miguel (fernandomiguel) wrote :

here it is:
$ ethtool -i eth0
driver: 8139too
version: 0.9.28
firmware-version:
bus-info: 0000:01:0c.0

$ ethtool -i eth1
driver: ipw2200
version: 1.2.0kmprq
firmware-version: ABG:9.0.2.6 (Mar 22 2005)
bus-info: 0000:01:07.0

Revision history for this message
Marco Monteiro (nok) wrote :

i have the same problem.

my output is:
$ ethtool -i eth0
driver: via-rhine
version: 1.4.2
firmware-version:
bus-info: 0000:00:12.0

Revision history for this message
Fernando Miguel (fernandomiguel) wrote :

with kernel 2.6.20-12-generic it seems to hibernate fine.
I'll be doing some more tests and report back.

Revision history for this message
Fernando Miguel (fernandomiguel) wrote :

From all the test I've made, the current kernel fixes this problem.
I can hibernate just fine, and resume my last session without any trouble.

Now I've found a different problem:
after I resume none of my network connections work, even after trying and updown, and /etc/init.d/networking restart.

thanks.

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

We are closing this bug report due to your last comment, regarding this being fixed with an update. Feel free to file a new bug report if the other issue still exists.

Thank you again for taking the time to report this bug and helping to make Ubuntu better. Feel free to submit any future bugs you may find.

Changed in linux-source-2.6.20:
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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