[Hardy] tg3 network driver doesn't come up via NetworkManger consistently
Bug #194547 reported by
Mario Limonciello
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| network-manager (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
Several machines in the Dell platform use tg3 as an ethernet driver. This driver itself functions properly, but NetworkManager won't always bring it up on the first try.
It seems there needs to be an extra delay with this driver from when NetworkManager starts to look for an address with it. This behavior can be seen either when the link is active (cable being plugged in), or when resuming from a suspend.
The problem is typically resolved by selecting nm-applet and re-requesting a network address the second time or by running dhclient manually on the command line.
Revision history for this message
| Mario Limonciello (superm1) wrote | #1 |
| Changed in dell: | |
| status: | New → Invalid |
Revision history for this message
| Mario Limonciello (superm1) wrote | #2 |
| Changed in network-manager: | |
| status: | New → Invalid |
| Changed in somerville: | |
| status: | New → Invalid |
| no longer affects: | dell |
Revision history for this message
| Timothy R. Chavez (timrchavez) wrote | #3 |
| no longer affects: | somerville |
To post a comment you must log in.
This appears to be happening on both the corporate network as well as a network with dnsmasq running.