DHCP IP lease fails (ipw3945)

Bug #83235 reported by merc
8
Affects Status Importance Assigned to Milestone
linux-source-2.6.20 (Ubuntu)
Invalid
Undecided
Kyle McMartin
network-manager (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Hi,

I am having a problem with Ubuntu Fiesty. It's a freshly installed HERD 3 with all the latest updates.
Here's my uname:

Linux merc-laptop 2.6.20-6-generic #2 SMP Wed Jan 31 20:53:39 UTC 2007 i686 GNU/Linux

The wireless network is detected. However, the DHCP seems to have a bit of a problem.
It will work for a while - the computer will get a DHCP lease without a problem. However, after a while after suspending/unsuspending the computer, the system will not be able to obtain a DHCP lease anymore.

As far as the lights are concerned, when I try to get Network Manager to lease an IP address, it actually looks like the system manages (the light blinks, it stays on for a tick, and then it goes away again).

Here is lspci:

00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS/940GML and 945GT Express Memory Controller Hub (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS/940GML Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/940GML Express Integrated Graphics Controller (rev 03)
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02)
00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #3 (rev 02)
00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #4 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02)
00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7 Family) Serial ATA Storage Controller IDE (rev 02)
00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 02)
04:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)
0a:01.0 FireWire (IEEE 1394): Ricoh Co Ltd Unknown device 0832
0a:01.1 Generic system peripheral [0805]: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 19)
0a:01.2 System peripheral: Ricoh Co Ltd Unknown device 0843 (rev 01)
0a:01.3 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 0a)
0a:01.4 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 05)
0a:07.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)

iwlist scanning returns:

lo Interface doesn't support scanning.
eth0 Interface doesn't support scanning.
eth1 Scan completed :
          Cell 01 - Address: 00:0F:B5:7F:7E:44
                    ESSID:"THENETWORK"
                    Protocol:IEEE 802.11bg
                    Mode:Master
                    Channel:11
                    Encryption key:off
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
                              11 Mb/s; 12 Mb/s; 18 Mb/s; 22 Mb/s; 24 Mb/s
                              36 Mb/s; 48 Mb/s; 54 Mb/s
                    Quality=90/100 Signal level=-41 dBm Noise level=-41 dBm
                    Extra: Last beacon: 184ms ago

root@merc-laptop:/var/log#

This is what happens in terms of DMESG:

[33091.932000] ADDRCONF(NETDEV_UP): eth1: link is not ready
[33091.964000] eth0: link up, 100Mbps, full-duplex, lpa 0x41E1

And this is the log (with EVERYTHING activated):

Feb 5 00:21:58 merc-laptop dhclient: No DHCPOFFERS received.
Feb 5 00:21:58 merc-laptop dhclient: No working leases in persistent database - sleeping.
Feb 5 00:22:06 merc-laptop syslogd 1.4.1#20ubuntu3: restart.
Feb 5 00:22:15 merc-laptop sudo: merc : TTY=unknown ; PWD=/media/sda3/home/merc ; USER=root ; COMMAND=/usr/bin/network-admin
Feb 5 00:22:45 merc-laptop NetworkManager: <information>^IGoing to sleep.
Feb 5 00:22:45 merc-laptop avahi-autoipd(eth1)[31942]: SIOCSIFFLAGS failed: Permission denied
Feb 5 00:22:45 merc-laptop avahi-autoipd(eth1)[31942]: Callout STOP, address 169.254.9.148 on interface eth1
Feb 5 00:22:45 merc-laptop avahi-daemon[5234]: Interface eth1.IPv4 no longer relevant for mDNS.
Feb 5 00:22:45 merc-laptop avahi-daemon[5234]: Leaving mDNS multicast group on interface eth1.IPv4 with address 169.254.9.148.
Feb 5 00:22:45 merc-laptop dhclient: There is already a pid file /var/run/dhclient.eth0.pid with pid 31811
Feb 5 00:22:45 merc-laptop dhclient: killed old client process, removed PID file
Feb 5 00:22:45 merc-laptop dhclient: receive_packet failed on eth1: Network is down
Feb 5 00:22:45 merc-laptop avahi-daemon[5234]: Withdrawing address record for 169.254.9.148 on eth1.
Feb 5 00:22:45 merc-laptop avahi-daemon[5234]: Interface eth0.IPv4 no longer relevant for mDNS.
Feb 5 00:22:45 merc-laptop avahi-daemon[5234]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.0.7.
Feb 5 00:22:45 merc-laptop avahi-daemon[5234]: Withdrawing address record for 192.168.0.7 on eth0.
Feb 5 00:22:45 merc-laptop NetworkManager: <information>^IWaking up from sleep.
Feb 5 00:22:45 merc-laptop NetworkManager: <information>^IDeactivating device eth1.
Feb 5 00:22:45 merc-laptop avahi-autoipd(eth1)[31943]: client: RTNETLINK answers: No such process
Feb 5 00:22:45 merc-laptop NetworkManager: <information>^IDeactivating device eth0.
Feb 5 00:22:45 merc-laptop kernel: [32970.760000] ADDRCONF(NETDEV_UP): eth1: link is not ready
Feb 5 00:22:45 merc-laptop NetworkManager: <information>^Ieth1: Device is fully-supported using driver 'ipw3945'.
Feb 5 00:22:45 merc-laptop NetworkManager: <information>^Inm_device_init(): waiting for device's worker thread to start
Feb 5 00:22:45 merc-laptop dhclient: DHCPRELEASE on eth0 to 192.168.0.1 port 67
Feb 5 00:22:45 merc-laptop dhclient: send_packet: Network is unreachable
Feb 5 00:22:45 merc-laptop dhclient: send_packet: please consult README file regarding broadcast address.
Feb 5 00:22:45 merc-laptop NetworkManager: <information>^Inm_device_init(): device's worker thread started, continuing.
Feb 5 00:22:45 merc-laptop NetworkManager: <information>^INow managing wireless (802.11) device 'eth1'.
Feb 5 00:22:45 merc-laptop NetworkManager: <information>^IDeactivating device eth1.
Feb 5 00:22:45 merc-laptop kernel: [32970.828000] eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
Feb 5 00:22:45 merc-laptop avahi-autoipd(eth0)[32178]: Found user 'avahi-autoipd' (UID 104) and group 'avahi-autoipd' (GID 108).
Feb 5 00:22:45 merc-laptop avahi-autoipd(eth0)[32178]: Successfully called chroot().
Feb 5 00:22:45 merc-laptop avahi-autoipd(eth0)[32178]: Successfully dropped root privileges.
Feb 5 00:22:45 merc-laptop avahi-autoipd(eth0)[32178]: fopen() failed: Permission denied
Feb 5 00:22:45 merc-laptop avahi-autoipd(eth0)[32178]: Starting with address 169.254.7.219
Feb 5 00:22:45 merc-laptop NetworkManager: <information>^Ieth0: Device is fully-supported using driver '8139too'.
Feb 5 00:22:45 merc-laptop NetworkManager: <information>^Inm_device_init(): waiting for device's worker thread to start
Feb 5 00:22:45 merc-laptop NetworkManager: <information>^Inm_device_init(): device's worker thread started, continuing.
Feb 5 00:22:45 merc-laptop NetworkManager: <information>^INow managing wired Ethernet (802.3) device 'eth0'.
Feb 5 00:22:45 merc-laptop NetworkManager: <information>^IDeactivating device eth0.
Feb 5 00:22:45 merc-laptop NetworkManager: <information>^IWill activate wired connection 'eth0' because it now has a link.
Feb 5 00:22:45 merc-laptop NetworkManager: <information>^ISWITCH: no current connection, found better connection 'eth0'.
Feb 5 00:22:45 merc-laptop NetworkManager: <information>^IWill activate connection 'eth0'.
Feb 5 00:22:45 merc-laptop NetworkManager: <information>^IDevice eth0 activation scheduled...
Feb 5 00:22:45 merc-laptop NetworkManager: <information>^IActivation (eth0) started...
Feb 5 00:22:45 merc-laptop NetworkManager: <information>^IActivation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
Feb 5 00:22:45 merc-laptop NetworkManager: <information>^IActivation (eth0) Stage 1 of 5 (Device Prepare) started...
Feb 5 00:22:45 merc-laptop NetworkManager: <information>^IActivation (eth0) Stage 2 of 5 (Device Configure) scheduled...
Feb 5 00:22:45 merc-laptop NetworkManager: <information>^IActivation (eth0) Stage 1 of 5 (Device Prepare) complete.
Feb 5 00:22:45 merc-laptop NetworkManager: <information>^IActivation (eth0) Stage 2 of 5 (Device Configure) starting...
Feb 5 00:22:45 merc-laptop NetworkManager: <information>^IActivation (eth0) Stage 2 of 5 (Device Configure) successful.
Feb 5 00:22:45 merc-laptop NetworkManager: <information>^IActivation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
Feb 5 00:22:45 merc-laptop NetworkManager: <information>^IActivation (eth0) Stage 2 of 5 (Device Configure) complete.
Feb 5 00:22:45 merc-laptop NetworkManager: <information>^IActivation (eth0) Stage 3 of 5 (IP Configure Start) started...
Feb 5 00:22:45 merc-laptop NetworkManager: <information>^IOld device 'eth0' activating, won't change.
Feb 5 00:22:47 merc-laptop NetworkManager: <information>^IActivation (eth0) Beginning DHCP transaction.
Feb 5 00:22:47 merc-laptop NetworkManager: <information>^ICouldn't send DHCP 'up' message because: name 'com.redhat.dhcp.OperationInProgress', message 'interface eth0 is being released. Please try again later.'.
Feb 5 00:22:47 merc-laptop NetworkManager: <information>^IActivation (eth0) failure scheduled...
Feb 5 00:22:47 merc-laptop NetworkManager: <information>^IActivation (eth0) Stage 3 of 5 (IP Configure Start) complete.
Feb 5 00:22:47 merc-laptop NetworkManager: <information>^IActivation (eth0) failed.
Feb 5 00:22:47 merc-laptop NetworkManager: <information>^IDeactivating device eth0.
Feb 5 00:22:48 merc-laptop NetworkManager: <information>^ISWITCH: no current connection, found better connection 'eth0'.
Feb 5 00:22:48 merc-laptop NetworkManager: <information>^IWill activate connection 'eth0'.
Feb 5 00:22:48 merc-laptop NetworkManager: <information>^IDevice eth0 activation scheduled...
Feb 5 00:22:48 merc-laptop NetworkManager: <information>^IActivation (eth0) started...
Feb 5 00:22:48 merc-laptop NetworkManager: <information>^IActivation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
Feb 5 00:22:48 merc-laptop NetworkManager: <information>^IActivation (eth0) Stage 1 of 5 (Device Prepare) started...
Feb 5 00:22:48 merc-laptop NetworkManager: <information>^IActivation (eth0) Stage 2 of 5 (Device Configure) scheduled...
Feb 5 00:22:48 merc-laptop NetworkManager: <information>^IActivation (eth0) Stage 1 of 5 (Device Prepare) complete.
Feb 5 00:22:48 merc-laptop NetworkManager: <information>^IActivation (eth0) Stage 2 of 5 (Device Configure) starting...
Feb 5 00:22:48 merc-laptop NetworkManager: <information>^IActivation (eth0) Stage 2 of 5 (Device Configure) successful.
Feb 5 00:22:48 merc-laptop NetworkManager: <information>^IActivation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
Feb 5 00:22:48 merc-laptop NetworkManager: <information>^IActivation (eth0) Stage 2 of 5 (Device Configure) complete.
Feb 5 00:22:48 merc-laptop NetworkManager: <information>^IActivation (eth0) Stage 3 of 5 (IP Configure Start) started...
Feb 5 00:22:50 merc-laptop NetworkManager: <information>^IActivation (eth0) Beginning DHCP transaction.
Feb 5 00:22:50 merc-laptop NetworkManager: <information>^ICouldn't send DHCP 'up' message because: name 'com.redhat.dhcp.OperationInProgress', message 'interface eth0 is being released. Please try again later.'.
Feb 5 00:22:50 merc-laptop NetworkManager: <information>^IActivation (eth0) failure scheduled...
Feb 5 00:22:50 merc-laptop NetworkManager: <information>^IActivation (eth0) Stage 3 of 5 (IP Configure Start) complete.
Feb 5 00:22:50 merc-laptop NetworkManager: <information>^IActivation (eth0) failed.
Feb 5 00:22:50 merc-laptop NetworkManager: <information>^IDeactivating device eth0.
Feb 5 00:22:51 merc-laptop NetworkManager: <information>^ISWITCH: no current connection, found better connection 'eth0'.
Feb 5 00:22:51 merc-laptop NetworkManager: <information>^IWill activate connection 'eth0'.
Feb 5 00:22:51 merc-laptop NetworkManager: <information>^IDevice eth0 activation scheduled...
Feb 5 00:22:51 merc-laptop NetworkManager: <information>^IActivation (eth0) started...
Feb 5 00:22:51 merc-laptop NetworkManager: <information>^IActivation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
Feb 5 00:22:51 merc-laptop NetworkManager: <information>^IActivation (eth0) Stage 1 of 5 (Device Prepare) started...
Feb 5 00:22:51 merc-laptop NetworkManager: <information>^IActivation (eth0) Stage 2 of 5 (Device Configure) scheduled...
Feb 5 00:22:51 merc-laptop NetworkManager: <information>^IActivation (eth0) Stage 1 of 5 (Device Prepare) complete.
Feb 5 00:22:51 merc-laptop NetworkManager: <information>^IActivation (eth0) Stage 2 of 5 (Device Configure) starting...
Feb 5 00:22:51 merc-laptop NetworkManager: <information>^IActivation (eth0) Stage 2 of 5 (Device Configure) successful.
Feb 5 00:22:51 merc-laptop NetworkManager: <information>^IActivation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
Feb 5 00:22:51 merc-laptop NetworkManager: <information>^IActivation (eth0) Stage 2 of 5 (Device Configure) complete.
Feb 5 00:22:51 merc-laptop NetworkManager: <information>^IActivation (eth0) Stage 3 of 5 (IP Configure Start) started...
Feb 5 00:22:52 merc-laptop avahi-autoipd(eth0)[32178]: Callout BIND, address 169.254.7.219 on interface eth0
Feb 5 00:22:52 merc-laptop avahi-daemon[5234]: New relevant interface eth0.IPv4 for mDNS.
Feb 5 00:22:52 merc-laptop avahi-daemon[5234]: Joining mDNS multicast group on interface eth0.IPv4 with address 169.254.7.219.
Feb 5 00:22:52 merc-laptop avahi-daemon[5234]: Registering new address record for 169.254.7.219 on eth0.
Feb 5 00:22:53 merc-laptop NetworkManager: <information>^IActivation (eth0) Beginning DHCP transaction.
Feb 5 00:22:53 merc-laptop NetworkManager: <information>^ICouldn't send DHCP 'up' message because: name 'com.redhat.dhcp.OperationInProgress', message 'interface eth0 is being released. Please try again later.'.
Feb 5 00:22:53 merc-laptop NetworkManager: <information>^IActivation (eth0) failure scheduled...
Feb 5 00:22:53 merc-laptop NetworkManager: <information>^IActivation (eth0) Stage 3 of 5 (IP Configure Start) complete.
Feb 5 00:22:53 merc-laptop NetworkManager: <information>^IActivation (eth0) failed.
Feb 5 00:22:53 merc-laptop NetworkManager: <information>^IDeactivating device eth0.
Feb 5 00:22:54 merc-laptop avahi-daemon[5234]: Withdrawing address record for 169.254.7.219 on eth0.
Feb 5 00:22:54 merc-laptop avahi-daemon[5234]: Leaving mDNS multicast group on interface eth0.IPv4 with address 169.254.7.219.
Feb 5 00:22:54 merc-laptop avahi-daemon[5234]: iface.c: interface_mdns_mcast_join() called but no local address available.
Feb 5 00:22:54 merc-laptop avahi-daemon[5234]: Interface eth0.IPv4 no longer relevant for mDNS.
Feb 5 00:22:54 merc-laptop NetworkManager: <information>^ISWITCH: no current connection, found better connection 'eth0'.
Feb 5 00:22:54 merc-laptop NetworkManager: <information>^IWill activate connection 'eth0'.
Feb 5 00:22:54 merc-laptop NetworkManager: <information>^IDevice eth0 activation scheduled...
Feb 5 00:22:54 merc-laptop NetworkManager: <information>^IActivation (eth0) started...
Feb 5 00:22:54 merc-laptop NetworkManager: <information>^IActivation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
Feb 5 00:22:54 merc-laptop NetworkManager: <information>^IActivation (eth0) Stage 1 of 5 (Device Prepare) started...
Feb 5 00:22:54 merc-laptop NetworkManager: <information>^IActivation (eth0) Stage 2 of 5 (Device Configure) scheduled...
Feb 5 00:22:54 merc-laptop NetworkManager: <information>^IActivation (eth0) Stage 1 of 5 (Device Prepare) complete.
Feb 5 00:22:54 merc-laptop NetworkManager: <information>^IActivation (eth0) Stage 2 of 5 (Device Configure) starting...
Feb 5 00:22:54 merc-laptop NetworkManager: <information>^IActivation (eth0) Stage 2 of 5 (Device Configure) successful.
Feb 5 00:22:54 merc-laptop NetworkManager: <information>^IActivation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
Feb 5 00:22:54 merc-laptop NetworkManager: <information>^IActivation (eth0) Stage 2 of 5 (Device Configure) complete.
Feb 5 00:22:54 merc-laptop NetworkManager: <information>^IActivation (eth0) Stage 3 of 5 (IP Configure Start) started...
Feb 5 00:22:56 merc-laptop avahi-autoipd(eth0)[32178]: Successfully claimed IP address 169.254.7.219
Feb 5 00:22:56 merc-laptop avahi-autoipd(eth0)[32178]: fopen() failed: Permission denied
Feb 5 00:22:56 merc-laptop NetworkManager: <information>^IDHCP daemon state is now 11 (unknown) for interface eth0
Feb 5 00:22:56 merc-laptop NetworkManager: <information>^IDHCP daemon state is now 14 (normal exit) for interface eth0
Feb 5 00:22:56 merc-laptop NetworkManager: <information>^IActivation (eth0) Beginning DHCP transaction.
Feb 5 00:22:56 merc-laptop dhclient: There is already a pid file /var/run/dhclient.eth0.pid with pid 134993440
Feb 5 00:22:56 merc-laptop NetworkManager: <information>^IActivation (eth0) Stage 3 of 5 (IP Configure Start) complete.
Feb 5 00:22:56 merc-laptop NetworkManager: <information>^IDHCP daemon state is now 12 (successfully started) for interface eth0
Feb 5 00:22:56 merc-laptop avahi-autoipd(eth0)[32178]: Got SIGTERM, quitting.
Feb 5 00:22:56 merc-laptop avahi-autoipd(eth0)[32178]: Callout STOP, address 169.254.7.219 on interface eth0
Feb 5 00:22:56 merc-laptop avahi-autoipd(eth0)[32179]: client: RTNETLINK answers: No such device
Feb 5 00:22:56 merc-laptop avahi-autoipd(eth0)[32179]: Script execution failed with return value 2
Feb 5 00:22:57 merc-laptop NetworkManager: <information>^IDHCP daemon state is now 1 (starting) for interface eth0
Feb 5 00:23:01 merc-laptop dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
Feb 5 00:23:01 merc-laptop dhclient: DHCPOFFER from 192.168.0.1
Feb 5 00:23:01 merc-laptop dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Feb 5 00:23:01 merc-laptop dhclient: DHCPACK from 192.168.0.1
Feb 5 00:23:01 merc-laptop avahi-daemon[5234]: New relevant interface eth0.IPv4 for mDNS.
Feb 5 00:23:01 merc-laptop avahi-daemon[5234]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.0.7.
Feb 5 00:23:01 merc-laptop avahi-daemon[5234]: Registering new address record for 192.168.0.7 on eth0.
Feb 5 00:23:01 merc-laptop dhclient: bound to 192.168.0.7 -- renewal in 39451 seconds.
Feb 5 00:23:01 merc-laptop NetworkManager: <information>^IDHCP daemon state is now 2 (bound) for interface eth0
Feb 5 00:23:01 merc-laptop NetworkManager: <information>^IActivation (eth0) Stage 4 of 5 (IP Configure Get) scheduled...
Feb 5 00:23:01 merc-laptop NetworkManager: <information>^IActivation (eth0) Stage 4 of 5 (IP Configure Get) started...
Feb 5 00:23:01 merc-laptop dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.host_name
Feb 5 00:23:01 merc-laptop dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.domain_name
Feb 5 00:23:01 merc-laptop dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_domain
Feb 5 00:23:01 merc-laptop dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_servers
Feb 5 00:23:01 merc-laptop NetworkManager: <information>^IRetrieved the following IP4 configuration from the DHCP daemon:
Feb 5 00:23:01 merc-laptop NetworkManager: <information>^I address 192.168.0.7
Feb 5 00:23:01 merc-laptop NetworkManager: <information>^I netmask 255.255.255.0
Feb 5 00:23:01 merc-laptop NetworkManager: <information>^I broadcast 192.168.0.255
Feb 5 00:23:01 merc-laptop NetworkManager: <information>^I gateway 192.168.0.1
Feb 5 00:23:01 merc-laptop NetworkManager: <information>^I nameserver 192.168.0.1
Feb 5 00:23:01 merc-laptop NetworkManager: <information>^IActivation (eth0) Stage 5 of 5 (IP Configure Commit) scheduled...
Feb 5 00:23:01 merc-laptop NetworkManager: <information>^IActivation (eth0) Stage 4 of 5 (IP Configure Get) complete.
Feb 5 00:23:01 merc-laptop NetworkManager: <information>^IActivation (eth0) Stage 5 of 5 (IP Configure Commit) started...
Feb 5 00:23:01 merc-laptop avahi-daemon[5234]: Withdrawing address record for 192.168.0.7 on eth0.
Feb 5 00:23:01 merc-laptop avahi-daemon[5234]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.0.7.
Feb 5 00:23:01 merc-laptop avahi-daemon[5234]: iface.c: interface_mdns_mcast_join() called but no local address available.
Feb 5 00:23:01 merc-laptop avahi-daemon[5234]: Interface eth0.IPv4 no longer relevant for mDNS.
Feb 5 00:23:01 merc-laptop avahi-daemon[5234]: New relevant interface eth0.IPv4 for mDNS.
Feb 5 00:23:01 merc-laptop avahi-daemon[5234]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.0.7.
Feb 5 00:23:01 merc-laptop avahi-daemon[5234]: Registering new address record for 192.168.0.7 on eth0.
Feb 5 00:23:02 merc-laptop NetworkManager: <information>^IClearing nscd hosts cache.
Feb 5 00:23:02 merc-laptop NetworkManager: <WARNING>^I nm_spawn_process (): nm_spawn_process('/usr/sbin/nscd -i hosts'): could not spawn process. (Failed to execute child process "/usr/sbin/nscd" (No such file or directory))
Feb 5 00:23:02 merc-laptop NetworkManager: <information>^IActivation (eth0) Finish handler scheduled.
Feb 5 00:23:02 merc-laptop NetworkManager: <information>^IActivation (eth0) Stage 5 of 5 (IP Configure Commit) complete.
Feb 5 00:23:02 merc-laptop NetworkManager: <information>^IActivation (eth0) successful, device activated.
Feb 5 00:23:08 merc-laptop ntpdate[32374]: adjust time server 82.211.81.145 offset 0.001070 sec
Feb 5 00:23:12 merc-laptop kernel: [32998.316000] eth0: no IPv6 routers present

This is another example - a little different, for whichever reason:

Feb 5 00:13:55 merc-laptop syslogd 1.4.1#20ubuntu3: restart.
Feb 5 00:13:59 merc-laptop NetworkManager: <debug info>^I[1170602039.106976] nm_device_802_11_wireless_get_activation_ap (): Forcing AP 'THENETWORK'
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^IUser Switch: /org/freedesktop/NetworkManager/Devices/eth1 / THENETWORK
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^IDeactivating device eth1.
Feb 5 00:13:59 merc-laptop avahi-daemon[5234]: Withdrawing address record for 169.254.9.148 on eth1.
Feb 5 00:13:59 merc-laptop avahi-daemon[5234]: Leaving mDNS multicast group on interface eth1.IPv4 with address 169.254.9.148.
Feb 5 00:13:59 merc-laptop avahi-daemon[5234]: iface.c: interface_mdns_mcast_join() called but no local address available.
Feb 5 00:13:59 merc-laptop avahi-daemon[5234]: Interface eth1.IPv4 no longer relevant for mDNS.
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^IDevice eth1 activation scheduled...
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^IActivation (eth1) started...
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^IActivation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^IActivation (eth1) Stage 1 of 5 (Device Prepare) started...
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^IActivation (eth1) Stage 2 of 5 (Device Configure) scheduled...
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^IActivation (eth1) Stage 1 of 5 (Device Prepare) complete.
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^IActivation (eth1) Stage 2 of 5 (Device Configure) starting...
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^IActivation (eth1/wireless): access point 'THENETWORK' is unencrypted, no key needed.
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^ISUP: sending command 'INTERFACE_ADD eth1^I^Iwext^I/var/run/wpa_supplicant^I'
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^ISUP: response was 'OK'
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^ISUP: sending command 'AP_SCAN 1'
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^ISUP: response was 'OK'
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^ISUP: sending command 'ADD_NETWORK'
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^ISUP: response was '0'
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^ISUP: sending command 'SET_NETWORK 0 ssid 504f52434f4444494f'
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^ISUP: response was 'OK'
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^ISUP: sending command 'SET_NETWORK 0 key_mgmt NONE'
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^ISUP: response was 'OK'
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^ISUP: sending command 'ENABLE_NETWORK 0'
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^ISUP: response was 'OK'
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^IActivation (eth1) Stage 2 of 5 (Device Configure) complete.
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): Global control interface '/var/run/wpa_supplicant-global'
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): RX global ctrl_iface - hexdump_ascii(len=49):
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): 49 4e 54 45 52 46 41 43 45 5f 41 44 44 20 65 74 INTERFACE_ADD et
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): 68 31 09 09 77 65 78 74 09 2f 76 61 72 2f 72 75 h1__wext_/var/ru
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): 6e 2f 77 70 61 5f 73 75 70 70 6c 69 63 61 6e 74 n/wpa_supplicant
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): 09 _
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): CTRL_IFACE GLOBAL INTERFACE_ADD 'eth1^I^Iwext^I/var/run/wpa_supplicant^I'
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): Initializing interface 'eth1' conf 'N/A' driver 'wext' ctrl_interface '/var/run/wpa_supplicant' bridge 'N/A'
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): Initializing interface (2) 'eth1'
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): EAPOL: SUPP_PAE entering state DISCONNECTED
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): EAPOL: KEY_RX entering state NO_KEY_RECEIVE
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): EAPOL: SUPP_BE entering state INITIALIZE
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): EAP: EAP entering state DISABLED
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): EAPOL: External notification - portEnabled=0
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): EAPOL: External notification - portValid=0
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): SIOCGIWRANGE: WE(compiled)=21 WE(source)=16 enc_capa=0xf
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): capabilities: key_mgmt 0xf enc 0xf
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): WEXT: Operstate: linkmode=1, operstate=5
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): c
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): wpa_driver_wext_set_wpa
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): wpa_driver_wext_set_countermeasures
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): wpa_driver_wext_set_drop_unencrypted
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): Setting scan request: 0 sec 100000 usec
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): Added interface eth1
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): Wireless event: cmd=0x8b06 len=8
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): RX ctrl_iface - hexdump_ascii(len=9):
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): 41 50 5f 53 43 41 4e 20 31 AP_SCAN 1
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): RX ctrl_iface - hexdump_ascii(len=11):
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): 41 44 44 5f 4e 45 54 57 4f 52 4b ADD_NETWORK
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): CTRL_IFACE: ADD_NETWORK
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): RX ctrl_iface - hexdump_ascii(len=37): [REMOVED]
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): CTRL_IFACE: SET_NETWORK id=0 name='ssid'
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): CTRL_IFACE: value - hexdump_ascii(len=18): [REMOVED]
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): ssid - hexdump_ascii(len=9):
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): 50 4f 52 43 4f 44 44 49 4f THENETWORK
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): e - hexdump_ascii(len=27): [REMOVED]
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): CTRL_IFACE: SET_NETWORK id=0 name='key_mgmt'
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): CTRL_IFACE: value - hexdump_ascii(len=4): [REMOVED]
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): key_mgmt: 0x4
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): RX ctrl_iface - hexdump_ascii(len=16):
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): 45 4e 41 42 4c 45 5f 4e 45 54 57 4f 52 4b 20 30 ENABLE_NETWORK 0
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): CTRL_IFACE: ENABLE_NETWORK id=0
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): Setting scan request: 0 sec 0 usec
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): State: DISCONNECTED -> SCANNING
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): Starting AP scan (broadcast SSID)
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): Trying to get current scan results first without requesting a new scan to speed up initial association
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): Received 231 bytes of scan results (1 BSSes)
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): Scan results: 1
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): Selecting BSS from priority group 0
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): 0: 00:0f:b5:7f:7e:44 ssid='THENETWORK' wpa_ie_len=0 rsn_ie_len=0 caps=0x1
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): skip - no WPA/RSN IE
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): selected non-WPA AP 00:0f:b5:7f:7e:44 ssid='THENETWORK'
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): Trying to associate with 00:0f:b5:7f:7e:44 (SSID='THENETWORK' freq=0 MHz)
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): Cancelling scan request
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): WPA: clearing own WPA/RSN IE
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): Automatic auth_alg selection: 0x1
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): WPA: clearing AP WPA IE
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): WPA: clearing AP RSN IE
Feb 5 00:13:59 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): WPA: clearing own WPA/RSN IE
Feb 5 00:14:09 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): earing
Feb 5 00:14:09 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): wpa_driver_wext_set_drop_unencrypted
Feb 5 00:14:09 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): State: SCANNING -> ASSOCIATING
Feb 5 00:14:09 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
Feb 5 00:14:09 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): WEXT: Operstate: linkmode=-1, operstate=5
Feb 5 00:14:09 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): wpa_driver_wext_associate
Feb 5 00:14:09 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): Setting authentication timeout: 10 sec 0 usec
Feb 5 00:14:09 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): EAPOL: External notification - portControl=ForceAuthorized
Feb 5 00:14:09 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): CTRL_IFACE monitor attached - hexdump(len=41): 2f 76 61 72 2f 72 75 6e 2f 4e 65 74 77 6f 72 6b 4d 61 6e 61 67 65 72 2f 77 70 61 5f 63 74 72 6c 5f 35 32 31 33 2d 32 32 00
Feb 5 00:14:09 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Feb 5 00:14:09 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): Wireless event: cmd=0x8b06 len=8
Feb 5 00:14:09 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Feb 5 00:14:09 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): Wireless event: cmd=0x8b1a len=17
Feb 5 00:14:09 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): Authentication with 00:00:00:00:00:00 timed out.
Feb 5 00:14:09 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): CTRL_IFACE monitor send - hexdump(len=41): 2f 76 61 72 2f 72 75 6e 2f 4e 65 74 77 6f 72 6b 4d 61 6e 61 67 65 72 2f 77 70 61 5f 63 74 72 6c 5f 35 32 31 33 2d 32 32 00
Feb 5 00:14:09 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): Added BSSID 00:0f:b5:7f:7e:44 into blacklist
Feb 5 00:14:09 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): State: ASSOCIATING -> DISCONNECTED
Feb 5 00:14:09 merc-laptop NetworkManager: <information>^Iwpa_supplicant(31002): wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
Feb 5 00:14:10 merc-laptop kernel: [32457.600000] ipw3945: association process canceled
Feb 5 00:14:10 merc-laptop kernel: [32457.600000] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
Feb 5 00:14:10 merc-laptop NetworkManager: <information>^IActivation (eth1/wireless) Stage 2 of 5 (Device Configure) successful. Connected to access point 'THENETWORK'.
Feb 5 00:14:10 merc-laptop NetworkManager: <information>^IActivation (eth1) Stage 3 of 5 (IP Configure Start) scheduled.
Feb 5 00:14:10 merc-laptop NetworkManager: <information>^IActivation (eth1) Stage 3 of 5 (IP Configure Start) started...
Feb 5 00:14:11 merc-laptop NetworkManager: <information>^IActivation (eth1) Beginning DHCP transaction.
Feb 5 00:14:11 merc-laptop NetworkManager: <information>^ICouldn't send DHCP 'up' message because: name 'com.redhat.dhcp.OperationInProgress', message 'interface eth1 is being released. Please try again later.'.
Feb 5 00:14:11 merc-laptop NetworkManager: <information>^IActivation (eth1) failure scheduled...
Feb 5 00:14:11 merc-laptop NetworkManager: <information>^IActivation (eth1) Stage 3 of 5 (IP Configure Start) complete.
Feb 5 00:14:11 merc-laptop NetworkManager: <information>^IActivation (eth1) failed for access point (THENETWORK)
Feb 5 00:14:11 merc-laptop NetworkManager: <information>^IActivation (eth1) failed.
Feb 5 00:14:11 merc-laptop NetworkManager: <information>^IDeactivating device eth1.
Feb 5 00:14:11 merc-laptop NetworkManager: <information>^Iwpa_supplicant(-1): rstate=5
Feb 5 00:14:11 merc-laptop NetworkManager: <information>^Iwpa_supplicant(-1): No keys have been configured - skip key clearing
Feb 5 00:14:11 merc-laptop NetworkManager: <information>^Iwpa_supplicant(-1): EAPOL: External notification - portEnabled=0
Feb 5 00:14:11 merc-laptop NetworkManager: <information>^Iwpa_supplicant(-1): EAPOL: External notification - portValid=0
Feb 5 00:14:11 merc-laptop NetworkManager: <information>^Iwpa_supplicant(-1): Setting scan request: 0 sec 0 usec
Feb 5 00:14:12 merc-laptop NetworkManager: <information>^Iwpa_supplicant(-1): State: DISCONNECTED -> SCANNING
Feb 5 00:14:12 merc-laptop NetworkManager: <information>^Iwpa_supplicant(-1): Starting AP scan (broadcast SSID)
Feb 5 00:14:12 merc-laptop NetworkManager: <information>^Iwpa_supplicant(-1): RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
Feb 5 00:14:12 merc-laptop NetworkManager: <information>^Iwpa_supplicant(-1): RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
Feb 5 00:14:12 merc-laptop NetworkManager: <information>^Iwpa_supplicant(-1): RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
Feb 5 00:14:12 merc-laptop NetworkManager: <information>^Iwpa_supplicant(-1): Wireless event: cmd=0x8b15 len=20
Feb 5 00:14:12 merc-laptop NetworkManager: <information>^Iwpa_supplicant(-1): Wireless event: new AP: 00:0f:b5:7f:7e:44
Feb 5 00:14:12 merc-laptop NetworkManager: <information>^Iwpa_supplicant(-1): State: SCANNING -> ASSOCIATED
Feb 5 00:14:12 merc-laptop NetworkManager: <information>^Iwpa_supplicant(-1): wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
Feb 5 00:14:12 merc-laptop NetworkManager: <information>^Iwpa_supplicant(-1): WEXT: Operstate: linkmode=-1, operstate=5
Feb 5 00:14:12 merc-laptop NetworkManager: <information>^Iwpa_supplicant(-1): Associated to a new BSS: BSSID=00:0f:b5:7f:7e:44
Feb 5 00:14:12 merc-laptop avahi-autoipd(eth1)[29484]: SIOCSIFFLAGS failed: Permission denied
Feb 5 00:14:12 merc-laptop dhclient: receive_packet failed on eth1: Network is down
Feb 5 00:14:12 merc-laptop NetworkManager: <information>^Iwpa_supplicant(-1): Network configuration found for the current AP
Feb 5 00:14:12 merc-laptop avahi-autoipd(eth1)[29484]: Callout STOP, address 169.254.9.148 on interface eth1
Feb 5 00:14:12 merc-laptop NetworkManager: <information>^Iwpa_supplicant(-1): WPA: clearing AP WPA IE
Feb 5 00:14:12 merc-laptop avahi-autoipd(eth1)[29485]: client: RTNETLINK answers: No such device
Feb 5 00:14:12 merc-laptop NetworkManager: <information>^Iwpa_supplicant(-1): WPA: clearing AP RSN IE
Feb 5 00:14:12 merc-laptop avahi-autoipd(eth1)[29485]: Script execution failed with return value 2
Feb 5 00:14:12 merc-laptop NetworkManager: <information>^Iwpa_supplicant(-1): WPA: clearing own WPA/RSN IE
Feb 5 00:14:12 merc-laptop NetworkManager: <information>^Iwpa_supplicant(-1): EAPOL: External notification - portControl=ForceAuthorized
Feb 5 00:14:12 merc-laptop NetworkManager: <information>^Iwpa_supplicant(-1): Associated with 00:0f:b5:7f:7e:44
Feb 5 00:14:26 merc-laptop dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 3
Feb 5 00:14:26 merc-laptop dhclient: send_packet: Network is down
Feb 5 00:14:29 merc-laptop dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 5
Feb 5 00:14:29 merc-laptop dhclient: send_packet: Network is down
Feb 5 00:14:34 merc-laptop dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7
Feb 5 00:14:34 merc-laptop dhclient: send_packet: Network is down

In both cases, I am trying to get the wireless to connect using the Network Manager. It's NOT the AP - it's worked fine for months, and there are three more people here using it (with different machines).

Bye!

Merc.

Revision history for this message
merc (merc) wrote :

Hi,

Is anybody onto this?
The latest updates didn't fix it...

Sorry to be a pain :-D

Merc.

Revision history for this message
Kyle McMartin (kyle) wrote :

Do you have linux-restricted-modules-2.6.20 installed? You'll need the ipw3945d daemon from that package running to be able to use your wireless.

Changed in linux-source-2.6.20:
status: Confirmed → Needs Info
assignee: nobody → kyle
Revision history for this message
merc (merc) wrote :

I do have linux-restricted-modules-2.6.20 installed.
Please note that the card worked fine before upgrading to herd 3.

Also:

merc@merc-laptop:~$ ps ax | grep ipw
 3697 ? S< 0:00 [ipw3945/0]
 3698 ? S< 0:00 [ipw3945/1]
 3699 ? S< 0:00 [ipw3945/0]
 3700 ? S< 0:00 [ipw3945/1]
 3768 ? S< 0:01 /sbin/ipw3945d-2.6.20-6-generic --quiet
 6726 pts/0 S+ 0:00 grep ipw
merc@merc-laptop:~$

So, the demon is running. Are you saying that it looked like it had died before, when it didn't get the IP address?

Merc.

Revision history for this message
Kyle McMartin (kyle) wrote :

Hmm. I'm inclined to think this is a network-manager bug. Can you please attach a full dmesg after a suspend, ps aux | grep ipw3945d after the suspend, and the output of ifconfig eth1? That should help track down whether network-manager isn't handling the wakeup properly, or the kernel isn't suspending/resuming properly.

Thanks!
  Kyle

Revision history for this message
merc (merc) wrote :

Hi,

I haven't been able to replicate the problem in 3 days.
I will report back as soon as it does it away. If you don't hear from me in 7 days, feel free to close the bug!

Bye,

Merc.

Revision history for this message
merc (merc) wrote :
Download full text (114.0 KiB)

Hi,

I am afraid it's doing it again.
As requested, this is the FULL dmesg:

DMESG:
------
[ 0.000000] Linux version 2.6.20-6-generic (root@palmer) (gcc version 4.1.2 20070106 (prerelease) (Ubuntu 4.1.1-21ubuntu7)) #2 SMP Wed Jan 31 20:53:39 UTC 2007 (Ubuntu 2.6.20-6.11-generic)
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] sanitize start
[ 0.000000] sanitize end
[ 0.000000] copy_e820_map() start: 0000000000000000 size: 000000000009f800 end: 000000000009f800 type: 1
[ 0.000000] copy_e820_map() type is E820_RAM
[ 0.000000] copy_e820_map() start: 000000000009f800 size: 0000000000000800 end: 00000000000a0000 type: 2
[ 0.000000] copy_e820_map() start: 00000000000dc000 size: 0000000000008000 end: 00000000000e4000 type: 2
[ 0.000000] copy_e820_map() start: 00000000000e8000 size: 0000000000018000 end: 0000000000100000 type: 2
[ 0.000000] copy_e820_map() start: 0000000000100000 size: 000000002f590000 end: 000000002f690000 type: 1
[ 0.000000] copy_e820_map() type is E820_RAM
[ 0.000000] copy_e820_map() start: 000000002f690000 size: 0000000000010000 end: 000000002f6a0000 type: 3
[ 0.000000] copy_e820_map() start: 000000002f6a0000 size: 0000000000060000 end: 000000002f700000 type: 4
[ 0.000000] copy_e820_map() start: 000000002f700000 size: 0000000000900000 end: 0000000030000000 type: 2
[ 0.000000] copy_e820_map() start: 00000000e0000000 size: 0000000010000000 end: 00000000f0000000 type: 2
[ 0.000000] copy_e820_map() start: 00000000fec00000 size: 0000000000010000 end: 00000000fec10000 type: 2
[ 0.000000] copy_e820_map() start: 00000000fed00000 size: 0000000000000400 end: 00000000fed00400 type: 2
[ 0.000000] copy_e820_map() start: 00000000fed14000 size: 0000000000006000 end: 00000000fed1a000 type: 2
[ 0.000000] copy_e820_map() start: 00000000fed1c000 size: 0000000000074000 end: 00000000fed90000 type: 2
[ 0.000000] copy_e820_map() start: 00000000fee00000 size: 0000000000001000 end: 00000000fee01000 type: 2
[ 0.000000] copy_e820_map() start: 00000000ff000000 size: 0000000001000000 end: 0000000100000000 type: 2
[ 0.000000] BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
[ 0.000000] BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
[ 0.000000] BIOS-e820: 00000000000dc000 - 00000000000e4000 (reserved)
[ 0.000000] BIOS-e820: 00000000000e8000 - 0000000000100000 (reserved)
[ 0.000000] BIOS-e820: 0000000000100000 - 000000002f690000 (usable)
[ 0.000000] BIOS-e820: 000000002f690000 - 000000002f6a0000 (ACPI data)
[ 0.000000] BIOS-e820: 000000002f6a0000 - 000000002f700000 (ACPI NVS)
[ 0.000000] BIOS-e820: 000000002f700000 - 0000000030000000 (reserved)
[ 0.000000] BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
[ 0.000000] BIOS-e820: 00000000fec00000 - 00000000fec10000 (reserved)
[ 0.000000] BIOS-e820: 00000000fed00000 - 00000000fed00400 (reserved)
[ 0.000000] BIOS-e820: 00000000fed14000 - 00000000fed1a000 (reserved)
[ 0.000000] BIOS-e820: 00000000fed1c000 - 00000000fed90000 (reserved)
[ 0.000000] BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
[ 0.000000] BIOS-e820: 00000000ff000000 - 0000000100000000 ...

Revision history for this message
Kyle McMartin (kyle) wrote :

Can't see how this is a kernel bug, reassigning to network-manager.

Changed in linux-source-2.6.20:
status: Needs Info → Rejected
Revision history for this message
Ben (ben-joldersma) wrote :

I'm also having this problem. Feisty, Thinkpad T60. I can give dmesg output, syslog. ipwd is running:

ben@dawntreader:~$ ps ax | grep ipw
 3655 ? S< 0:00 [ipw3945/0]
 3656 ? S< 0:00 [ipw3945/1]
 3657 ? S< 0:00 [ipw3945/0]
 3658 ? S< 0:00 [ipw3945/1]
 3953 ? S< 0:01 /sbin/ipw3945d-2.6.20-13-generic --quiet
 7572 pts/0 S+ 0:00 grep ipw

seems like the problem kicked in in a recent kernel upgrade. maybe 2.6.20.12?

Changed in network-manager:
importance: Undecided → Medium
status: Unconfirmed → Confirmed
Revision history for this message
Ketil Malde (ketil-ii) wrote :

I notice this line from iwlist above:

                    Quality=90/100 Signal level=-41 dBm Noise level=-41 dBm

Note that signal and noise show up as equal, this may be the same problem as mentioned here:

http://sourceforge.net/mailarchive/message.php?msg_id=20061106011420.GB14990%40gamma.logic.tuwien.ac.at
http://sourceforge.net/mailarchive/message.php?msg_id=45A23520.7080405%40gmx.net
http://sourceforge.net/mailarchive/message.php?msg_id=20061106011420.GB14990%40gamma.logic.tuwien.ac.at
http://groups.google.no/group/linux.kernel/browse_thread/thread/ad26d28b6c02971/f8711a5ed9875d72?lnk=st&q=intel+dBm+noise+signal+level&rnum=8&hl=no#f8711a5ed9875d72

Needless to say, I get the same problem, both from the Feisty beta live CD, and from Fedora Core 6.

I'm unable to connect to any network, I see DHCP packets arrive on the server, but the responses are never received on the laptop.

Revision history for this message
merc (merc) wrote :

Hi,

I still get the problem... is there *anything* I can do to help fixing it?

THANKS!

Merc.

Revision history for this message
Brian Murray (brian-murray) wrote :

Please add the full output of 'sudo aptitude search generic$'. Thanks again.

Revision history for this message
Steve Romanow (slestak989) wrote :

I have same issue with Dell e1505 with ipw3945. worked fine with edgy, upgrade to feisty beta. Can no longer get dhcp address.

Here is my search you requested above.

steve@e1505:/$ sudo aptitude search generic$
p linux-backports-modules-2.6.20-12-generic - Backported modules package
p linux-backports-modules-2.6.20-13-generic - Backported modules package
p linux-backports-modules-generic - Backported drivers for generic kernel image
p linux-generic - Complete Generic Linux kernel
p linux-headers-2.6.20-12-generic - Linux kernel headers for version 2.6.20 on x86/x86_64
i linux-headers-2.6.20-13-generic - Linux kernel headers for version 2.6.20 on x86/x86_64
i linux-headers-generic - Generic Linux kernel headers
i linux-image-2.6.17-10-generic - Linux kernel image for version 2.6.17 on x86/x86_64
i linux-image-2.6.17-11-generic - Linux kernel image for version 2.6.17 on x86/x86_64
p linux-image-2.6.20-12-generic - Linux kernel image for version 2.6.20 on x86/x86_64
i linux-image-2.6.20-13-generic - Linux kernel image for version 2.6.20 on x86/x86_64
p linux-image-debug-2.6.20-12-generic - Linux kernel debug image for version 2.6.20 on x86/x86_64
p linux-image-debug-2.6.20-13-generic - Linux kernel debug image for version 2.6.20 on x86/x86_64
i linux-image-generic - Generic Linux kernel image
i linux-restricted-modules-2.6.17-10-generic - Non-free Linux 2.6.17 modules on x86_64 generic
i linux-restricted-modules-2.6.17-11-generic - Non-free Linux 2.6.17 modules on x86_64 generic
p linux-restricted-modules-2.6.20-12-generic - Non-free Linux 2.6.20 modules on x86/x86_64
i linux-restricted-modules-2.6.20-13-generic - Non-free Linux 2.6.20 modules on x86/x86_64
i linux-restricted-modules-generic - Restricted Linux modules for generic kernels
p xen-headers-2.6.19-4-generic - Common header files for Linux 2.6.19
p xen-image-2.6.19-4-generic - Linux 2.6.19 image on PPro/Celeron/PII/PIII/P4

Revision history for this message
merc (merc) wrote :

Here's mine...

p linux-backports-modules-2.6.20- - Backported modules package
p linux-backports-modules-2.6.20- - Backported modules package
p linux-backports-modules-generic - Backported drivers for generic kernel imag
i linux-generic - Complete Generic Linux kernel
i linux-headers-2.6.20-12-generic - Linux kernel headers for version 2.6.20 on
p linux-headers-2.6.20-13-generic - Linux kernel headers for version 2.6.20 on
i linux-headers-2.6.20-6-generic - Linux kernel headers for version 2.6.20 on
i linux-headers-2.6.20-9-generic - Linux kernel headers for version 2.6.20 on
i linux-headers-generic - Generic Linux kernel headers
i linux-image-2.6.20-12-generic - Linux kernel image for version 2.6.20 on x
p linux-image-2.6.20-13-generic - Linux kernel image for version 2.6.20 on x
i linux-image-2.6.20-6-generic - Linux kernel image for version 2.6.20 on x
i linux-image-2.6.20-9-generic - Linux kernel image for version 2.6.20 on x
p linux-image-debug-2.6.20-12-gen - Linux kernel debug image for version 2.6.2
p linux-image-debug-2.6.20-13-gen - Linux kernel debug image for version 2.6.2
i linux-image-generic - Generic Linux kernel image
p linux-restricted-modules-2.6.17 - Non-free Linux 2.6.17 modules on x86_64 ge
i linux-restricted-modules-2.6.20 - Non-free Linux 2.6.20 modules on x86/x86_6
p linux-restricted-modules-2.6.20 - Non-free Linux 2.6.20 modules on x86/x86_6
i linux-restricted-modules-2.6.20 - Non-free Linux 2.6.20 modules on x86/x86_6
i linux-restricted-modules-2.6.20 - Non-free Linux 2.6.20 modules on x86/x86_6
i linux-restricted-modules-generi - Restricted Linux modules for generic kerne
p xen-headers-2.6.19-4-generic - Common header files for Linux 2.6.19
p xen-image-2.6.19-4-generic - Linux 2.6.19 image on PPro/Celeron/PII/PII
merc@merc-laptop:~$

Revision history for this message
Steve Romanow (slestak989) wrote :

my issue appears to be resolved by one of the two following actions:
1) a new dhcp client was installed via adept
2) when entering my wep key, i changed the key type in the drop down list to "wep 40/104 bit hex". I did not see that dialog before, so it may have worked with the older dhcp client.

I am able to connect with my 3945 + wep.

Revision history for this message
merc (merc) wrote :

I live in Australia, and there is nobody with a computer in my wireless range. Therefore, I do not use WEP. I am happy to use it if it makes a difference though...
Which version of the dhcp client are you using?

Merc.

Revision history for this message
Steve Romanow (slestak989) wrote : Re: [Bug 83235] Re: DHCP IP lease fails (ipw3945)

On Monday 02 April 2007 22:37:37 merc wrote:
> I live in Australia, and there is nobody with a computer in my wireless
> range. Therefore, I do not use WEP. I am happy to use it if it makes a
> difference though... Which version of the dhcp client are you using?
>
> Merc.

dhcp3-client 3.0.4-12ubuntu4 was installed this afternoon.

I dont think the problem is KNetworkManager, because i tried executing the
dhcp request in the console, and my dhcp server saw the laptop andf
DHCPOFFERed but the laptop never took it.

Man, i upgraded with adept. Iwish adept logged to /var/log like dpkg and
aptitude. may file a bug.

Cheers,
Slestak

Revision history for this message
merc (merc) wrote :

Hi,

I have dhcp3-client 3.0.4-12ubuntu3 - where did you get dhcp3-client 3.0.4-12ubuntu4 from?

Merc.

Revision history for this message
Steve Romanow (slestak989) wrote :

On Monday 02 April 2007 23:17:55 merc wrote:
> Hi,
>
> I have dhcp3-client 3.0.4-12ubuntu3 - where did you get dhcp3-client
> 3.0.4-12ubuntu4 from?
>
> Merc.

It was offered up by the repos I check. Using ftp.gtlib.gatech.edu repos for
my feisty upgrades. Looked in adept, couldnt tell what section, probably
security, maybe.

Revision history for this message
Ketil Malde (ketil-ii) wrote : Re: my comment on signal/noise ratios and links

Well, I ditched Fedora (spiting my IT department) and installed Ubuntu (Feisty beta), over the quite superfluous Windows partition. No surprise, WiFi now works, as well as several other annoyances from Fedora being eradicated.

I guess displaying similar values for signal and noise is just a quirk.

Revision history for this message
merc (merc) wrote :

Ketil: this is not a forum to bitch about Fedora or praise ubuntu. This is a specific place to file bug reports - which is what we did.

About the bug: upgraded to dhcp3-client 3.0.4-12ubuntu4, it SEEMS to be working. However... well, since the problem is intermittent, I will keep an eye on it and will let you know if everything is finally OK!

Thanks everybody,

Merc.

Revision history for this message
merc (merc) wrote :

Hi,

I am happy to confirm that yes, with the latest feisty release the DHCP leasing has indeed stopped failing.
I waited a little while before writing here, because I wanted to make sure it wasn't just a temporary thing. I has now consistently reassociated for 3 days or so.

I *think* this bug can be considered closed - at least for feisty.

Can anybody/everybody confirm this?

Merc.

Revision history for this message
Martin Pitt (pitti) wrote :

Confirmed fixed by the original reporter, thanks merc! Closing.

Changed in network-manager:
status: Confirmed → Fix Released
Revision history for this message
merc (merc) wrote :

Hi,

No worries at all - in fact, thanks you! :-D

Merc.

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.