#2434 BLOC Untriag: One of my B4s can't get on the mesh today
Zarro Boogs per Child
bugtracker at laptop.org
Tue Jul 24 14:39:03 EDT 2007
#2434: One of my B4s can't get on the mesh today
-----------------------------+----------------------------------------------
Reporter: Zack | Owner: dcbw
Type: defect | Status: new
Priority: blocker | Milestone: Untriaged
Component: network manager | Version:
Keywords: | Verified: 0
-----------------------------+----------------------------------------------
I have two B4s sitting next to each other with 530. The first one to boot
won't get on the mesh; the icon blinks for 10ish seconds, and then stops
blinking. It never gets an autoip address. Here's some info from
/var/log/messages:
Jul 24 18:34:21 localhost NetworkManager: <info> User Switch:
/org/freedesktop/NetworkManager/Devices/msh0
Jul 24 18:34:21 localhost NetworkManager: <info> Deactivating device
msh0.
Jul 24 18:34:21 localhost avahi-daemon[1211]: Withdrawing address record
for fe80::217:c4ff:fe03:56da on msh0.
Jul 24 18:34:21 localhost NetworkManager: <info> aipd_cleanup(): called
Jul 24 18:34:21 localhost NetworkManager: <info> Device msh0 activation
scheduled...
Jul 24 18:34:21 localhost NetworkManager: <info> Activation (msh0)
started...
Jul 24 18:34:21 localhost NetworkManager: <info> Activation (msh0) Stage
1 of 5 (Device Prepare) scheduled...
Jul 24 18:34:21 localhost NetworkManager: <info> Activation (msh0) Stage
1 of 5 (Device Prepare) started...
Jul 24 18:34:21 localhost NetworkManager: <info> Activation (msh0) Stage
2 of 5 (Device Configure) scheduled...
Jul 24 18:34:21 localhost NetworkManager: <info> Activation (msh0) Stage
1 of 5 (Device Prepare) complete.
Jul 24 18:34:21 localhost NetworkManager: <info> Activation (msh0) Stage
2 of 5 (Device Configure) starting...
Jul 24 18:34:21 localhost NetworkManager: <info> Activation (msh0/mesh)
level 4: Peer-to-Peer Mesh.
Jul 24 18:34:21 localhost NetworkManager: <info> Activation (msh0/mesh)
Stage 2 of 6 (Device Configure) looking for a mesh on channel 1.
Jul 24 18:34:21 localhost NetworkManager: <info> Activation (msh0) Stage
2 of 5 (Device Configure) complete.
Jul 24 18:34:22 localhost kernel: [ 4067.447790] ADDRCONF(NETDEV_CHANGE):
msh0: link becomes ready
Jul 24 18:34:22 localhost NetworkManager: <info> Old device 'msh0'
activating, won't change.
Jul 24 18:34:23 localhost NetworkManager: <info> msh0: Got association;
scheduling association handler
Jul 24 18:34:23 localhost NetworkManager: <info> msh0: got association
event from driver.
Jul 24 18:34:23 localhost NetworkManager: <info> Activation (msh0) Stage
3 of 5 (IP Configure Start) scheduled.
Jul 24 18:34:23 localhost NetworkManager: <info> Activation (msh0) Stage
3 of 5 (IP Configure Start) started...
Jul 24 18:34:23 localhost NetworkManager: <info> aipd_exec(): returning
success pid 1721
Jul 24 18:34:23 localhost NetworkManager: <info> Activation (msh0) Stage
3 of 5 (IP Configure Start) complete.
Jul 24 18:34:24 localhost avahi-daemon[1211]: Registering new address
record for fe80::217:c4ff:fe03:56da on msh0.*.
Jul 24 18:34:43 localhost NetworkManager: <info> msh0: avahi-autoipd
timed out.
Jul 24 18:34:43 localhost NetworkManager: <info> channel_failure_handler:
step 4, channel 1, next channel -1
Jul 24 18:34:43 localhost NetworkManager: <info> will fail
Jul 24 18:34:43 localhost NetworkManager: <info> channel_failure_handler:
failing activation
Jul 24 18:34:43 localhost NetworkManager: <info> Activation (msh0)
failure scheduled...
Jul 24 18:34:43 localhost NetworkManager: <info> Activation (msh0)
failed.
Jul 24 18:34:43 localhost NetworkManager: <info> Deactivating device
msh0.
Jul 24 18:34:43 localhost avahi-daemon[1211]: Withdrawing address record
for fe80::217:c4ff:fe03:56da on msh0.
Jul 24 18:34:43 localhost NetworkManager: <info> aipd_cleanup(): called
Jul 24 18:34:43 localhost NetworkManager: <info> aipd_cleanup(): Will
kill avahi-autoipd pid 1721
--
Ticket URL: <http://dev.laptop.org/ticket/2434>
One Laptop Per Child <http://laptop.org/>
More information about the Bugs
mailing list