Unfortunately this not only happens on boot, but every time I remove and 
reinstall the module, with the cable unplugged.
relevant part of /var/log/messages

Jul 10 10:20:24 yelo3-laptop kernel: [ 1232.272000] tg3: eth0: Link is down.
Jul 10 10:20:29 yelo3-laptop kernel: [ 1237.048000] ACPI: PCI interrupt for 
device 0000:02:00.0 disabled
Jul 10 10:20:36 yelo3-laptop kernel: [ 1244.604000] tg3.c:v3.77 (May 31, 2007)
Jul 10 10:20:36 yelo3-laptop kernel: [ 1244.604000] ACPI: PCI Interrupt 
0000:02:00.0[A] -> Link [LNKB] -> GSI 4 (level, low) -> IRQ 4
Jul 10 10:20:37 yelo3-laptop kernel: [ 1244.652000] eth0: Tigon3 
[partno(BCM95788A50) rev 3003 PHY(5705)] (PCI:33MHz:32-bit) 10/100/1000Base-T 
Ethernet 00:11:2f:b5:41:dd
Jul 10 10:20:37 yelo3-laptop kernel: [ 1244.652000] eth0: RXcsums[1] 
LinkChgREG[0] MIirq[0] ASF[0] WireSpeed[0] TSOcap[1]
Jul 10 10:20:37 yelo3-laptop kernel: [ 1244.652000] eth0: dma_rwctrl[763f0000] 
dma_mask[32-bit]

-----

when I replug the cable
Jul 10 10:24:13 yelo3-laptop kernel: [ 1460.812000] tg3: eth0: Link is up at 
100 Mbps, full duplex.
Jul 10 10:24:13 yelo3-laptop kernel: [ 1460.812000] tg3: eth0: Flow control is 
off for TX and off for RX.
Jul 10 10:24:13 yelo3-laptop kernel: [ 1460.816000] ADDRCONF(NETDEV_CHANGE): 
eth0: link becomes ready
Jul 10 10:24:14 yelo3-laptop avahi-daemon[7003]: Registering new address record 
for fe80::211:2fff:feb5:41dd on eth0.*.

And the interface eth0:avah will remain, so that eth0 is not reconfigured with 
dhcp
------
if I remove the cable again, the eth0:avah is removed
Jul 10 10:25:39 yelo3-laptop NetworkManager: <info>  SWITCH: terminating 
current connection 'eth0' because it's no longer valid. 
Jul 10 10:25:39 yelo3-laptop NetworkManager: <info>  Deactivating device eth0. 
Jul 10 10:25:39 yelo3-laptop NetworkManager: nm_device_is_802_3_ethernet: 
assertion `dev != NULL' failed
Jul 10 10:25:39 yelo3-laptop NetworkManager: nm_device_is_802_11_wireless: 
assertion `dev != NULL' failed
Jul 10 10:25:39 yelo3-laptop avahi-daemon[7003]: Withdrawing address record for 
169.254.7.228 on eth0.
Jul 10 10:25:39 yelo3-laptop avahi-daemon[7003]: Leaving mDNS multicast group 
on interface eth0.IPv4 with address 169.254.7.228.
Jul 10 10:25:39 yelo3-laptop avahi-daemon[7003]: Interface eth0.IPv4 no longer 
relevant for mDNS.
Jul 10 10:25:39 yelo3-laptop avahi-daemon[7003]: Withdrawing address record for 
fe80::211:2fff:feb5:41dd on eth0.
------
now if I replug the cable, it gives me the correct address!

So this problem might be a kernel module problem, since it thinks that it has a 
link only when the module is loading even if there is no cable...
What do you think? Can someone in gutsy test if the things that are happening 
to me, happens to him, too?
Thanks

-- 
[feisty] nm gives me an ip even if there is no cable
https://bugs.launchpad.net/bugs/78078
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to