no ethernet after suspend with forcedeth driver
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linux |
Fix Released
|
High
|
|||
linux (Ubuntu) |
Fix Released
|
Medium
|
Andy Whitcroft | ||
Intrepid |
Fix Released
|
Medium
|
Andy Whitcroft |
Bug Description
Binary package hint: network-manager
Network-manager can't connect eth0 after suspend on Ubuntu 8.10 frozen (64 bit).
version: 0.7~~svn2008101
I am not shure its a network-manager problem because i can't connect mannually either.
I have tried this in console:
koen@ubuntu64:~$ sudo /etc/init.
* Reconfiguring network interfaces...
Ignoring unknown interface eth0=eth0.
info about hardware:
ifconfig
eth0 Link encap:Ethernet HWaddr 00:1a:4d:70:ac:df
inet6 addr: fe80::21a:
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:11476 errors:0 dropped:0 overruns:0 frame:0
TX packets:8469 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:14170701 (14.1 MB) TX bytes:1230020 (1.2 MB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1912 errors:0 dropped:0 overruns:0 frame:0
TX packets:1912 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:157810 (157.8 KB) TX bytes:157810 (157.8 KB)
hwinfo --network
24: None 00.0: 10701 Ethernet
[Created at net.124]
Unique ID: usDW.ndpeucax6V1
Parent ID: rBUF.Co2JF_zcRV2
SysFS ID: /class/net/eth0
SysFS Device Link: /devices/
Hardware Class: network interface
Model: "Ethernet network interface"
Driver: "forcedeth"
Driver Modules: "forcedeth"
Device File: eth0
HW Address: 00:1a:4d:70:ac:df
Link detected: yes
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #9 (Ethernet controller)
===
SRU Justification
Justification: NVIDIA nForce wireless cards are lost after a suspend/resume cycle
Impact: wireless networking is lost after a suspend/resume cycle requiring a reboot
Fix Description: fixes to the reset processing following resume
Risks: this is a device specific change which is only applied on resume, where these devices already do not work. The change has also already been accepted upstream into the net-next tree.
TEST CASE: see bug
Related branches
Changed in linux: | |
status: | Unknown → Confirmed |
Changed in linux: | |
assignee: | nobody → apw |
status: | Triaged → In Progress |
Changed in linux: | |
status: | Confirmed → Fix Released |
Changed in linux: | |
status: | Confirmed → In Progress |
Changed in linux: | |
assignee: | nobody → apw |
importance: | Undecided → Medium |
status: | New → In Progress |
Changed in linux: | |
status: | Incomplete → In Progress |
description: | updated |
Changed in linux: | |
status: | In Progress → Fix Committed |
Changed in linux: | |
status: | Fix Released → Confirmed |
Changed in linux: | |
status: | Confirmed → Fix Released |
tags: | added: hw-specific |
Changed in linux: | |
importance: | Unknown → High |
I have the same problem (Intrepid Ibex, all updates, 32-bit). d/network restart" gives "OK" as response. network/ ifstate" it finds only lo=lo
Only difference is, that "/etc/init.
I don't know if it should be there, but :
"cat /var/run/
When working there is also "eth0=eth0" -line
"ifup eth0" gives "unknown interface error eth0=eth0"