No ethernet after cold boot; works after warm boot

Bug #160436 reported by Werner Karl
2
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

After the dist-upgrade from feisty to gutsy, ethernet does not work after a cold boot. The NIC is a Broadcom NetXtreme BCM 5171 using the tg3 driver. /etc/init.d/networking restart does not bring network up. Instead it issues a:
SIOCSIFADDR: no such device
error for eth0

After the cold boot, lshw and lspci do not show up the NIC hardware. After a warm boot without any changes to the system, the NIC comes up and network is OK.

Please find attached the output from dmesg, lshw, lspci, ifconfig and syslog, each in a version after cold boot and after warm boot.

I am not sure, if this is a kernel issue. Maybe this is an upstart issue?

Revision history for this message
Werner Karl (wkarl-bfe) wrote :
Revision history for this message
Werner Karl (wkarl-bfe) wrote : only applies to realtime kernel

Meanwhile I found out, that this applies *only* to the realtime kernel 2.6.22-14-rt. When I use kernel 2.6.22.14-generic, everything works.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

[This is an automated message. Apologies if it has reached you inappropriately.]

This bug was reported against the linux-meta package when it likely should have been reported against the linux package instead. We are automatically transitioning this to the linux kernel package so that the appropriate teams are notified and made aware of this issue. Thanks.

affects: linux-meta (Ubuntu) → linux (Ubuntu)
Revision history for this message
Werner Karl (wkarl-bfe) wrote :

This did also occur in Intrepid.

However, this does *not* occur in Jaunty anymore. At least for my system. If there aren't any objections, I would close this bug next week.

Revision history for this message
Werner Karl (wkarl-bfe) wrote :

Please close this bug. It doesn't occur in Jaunty anymore.

Changed in linux (Ubuntu):
status: New → 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.