when startup delays become bugs

[Chris Murphy]

On May 16, 2013, at 1:51 PM, Chris Murphy <lists at colorremedies.com> wrote:
> 
> I wonder if wireless connectivity is related? When I reboot with and without a wired connection attached, I get the same result. But maybe wireless is causing delays just by being configured, even if a wired connection is available?

OK well this isn't right. On every reboot, wireless is activated and connected to. But the wired connection is disabled. I just removed the b43 wireless firmware files to prevent it from being involved, and on every wired reboot, Gnome has the wired connection set to off. I turn it on, I connect, I reboot, and it's off again. That's not how Live media works (it's on on every boot), and isn't how F18 works either. So I don't know what's going on…

journalctl | grep p5p1
May 16 14:13:50 F19.localdomain systemd-udevd[187]: renamed network interface eth0 to p5p1
May 16 14:14:06 F19.localdomain NetworkManager[403]: <info> (p5p1): carrier is OFF
May 16 14:14:06 F19.localdomain NetworkManager[403]: <info> (p5p1): new Ethernet device (driver: 'sky2' ifindex: 2)
May 16 14:14:06 F19.localdomain NetworkManager[403]: <info> (p5p1): exported as /org/freedesktop/NetworkManager/Devices/0
May 16 14:14:06 F19.localdomain NetworkManager[403]: <info> (p5p1): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
May 16 14:14:06 F19.localdomain NetworkManager[403]: <info> (p5p1): bringing up device.
May 16 14:14:06 F19.localdomain kernel: sky2 0000:0c:00.0 p5p1: enabling interface
May 16 14:14:06 F19.localdomain kernel: IPv6: ADDRCONF(NETDEV_UP): p5p1: link is not ready
May 16 14:14:06 F19.localdomain NetworkManager[403]: <info> (p5p1): preparing device.
May 16 14:14:06 F19.localdomain NetworkManager[403]: <info> (p5p1): deactivating device (reason 'managed') [2]
May 16 14:14:08 F19.localdomain kernel: sky2 0000:0c:00.0 p5p1: Link is up at 100 Mbps, full duplex, flow control both
May 16 14:14:08 F19.localdomain kernel: IPv6: ADDRCONF(NETDEV_CHANGE): p5p1: link becomes ready
May 16 14:14:08 F19.localdomain NetworkManager[403]: <info> (p5p1): carrier now ON (device state 20)
May 16 14:14:08 F19.localdomain NetworkManager[403]: <info> (p5p1): device state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40]
May 16 14:14:10 F19.localdomain avahi-daemon[308]: Registering new address record for fe80::21e:c2ff:fe1d:507e on p5p1.*.


This is where I manually slide the Wired setting from Off to On in Gnome:


May 16 14:14:36 F19.localdomain NetworkManager[403]: <info> Activation (p5p1) starting connection 'ens5'
May 16 14:14:36 F19.localdomain NetworkManager[403]: <info> (p5p1): device state change: disconnected -> prepare (reason 'none') [30 40 0]
May 16 14:14:36 F19.localdomain NetworkManager[403]: <info> Activation (p5p1) Stage 1 of 5 (Device Prepare) scheduled...
May 16 14:14:36 F19.localdomain NetworkManager[403]: <info> Activation (p5p1) Stage 1 of 5 (Device Prepare) started...
May 16 14:14:36 F19.localdomain NetworkManager[403]: <info> Activation (p5p1) Stage 2 of 5 (Device Configure) scheduled...
May 16 14:14:36 F19.localdomain NetworkManager[403]: <info> Activation (p5p1) Stage 1 of 5 (Device Prepare) complete.
May 16 14:14:36 F19.localdomain NetworkManager[403]: <info> Activation (p5p1) Stage 2 of 5 (Device Configure) starting...
May 16 14:14:36 F19.localdomain NetworkManager[403]: <info> (p5p1): device state change: prepare -> config (reason 'none') [40 50 0]
May 16 14:14:36 F19.localdomain NetworkManager[403]: <info> Activation (p5p1) Stage 2 of 5 (Device Configure) successful.
May 16 14:14:36 F19.localdomain NetworkManager[403]: <info> Activation (p5p1) Stage 2 of 5 (Device Configure) complete.
May 16 14:14:36 F19.localdomain NetworkManager[403]: <info> Activation (p5p1) Stage 3 of 5 (IP Configure Start) scheduled.
May 16 14:14:36 F19.localdomain NetworkManager[403]: <info> Activation (p5p1) Stage 3 of 5 (IP Configure Start) started...
May 16 14:14:36 F19.localdomain NetworkManager[403]: <info> (p5p1): device state change: config -> ip-config (reason 'none') [50 70 0]
May 16 14:14:36 F19.localdomain NetworkManager[403]: <info> Activation (p5p1) Beginning DHCPv4 transaction (timeout in 45 seconds)
May 16 14:14:36 F19.localdomain NetworkManager[403]: <info> Activation (p5p1) Beginning IP6 addrconf.
May 16 14:14:36 F19.localdomain avahi-daemon[308]: Withdrawing address record for fe80::21e:c2ff:fe1d:507e on p5p1.
May 16 14:14:36 F19.localdomain NetworkManager[403]: <info> Activation (p5p1) Stage 3 of 5 (IP Configure Start) complete.
May 16 14:14:36 F19.localdomain NetworkManager[403]: <info> (p5p1): DHCPv4 state changed nbi -> preinit
May 16 14:14:36 F19.localdomain dhclient[1526]: Listening on LPF/p5p1/00:1e:c2:1d:50:7e
May 16 14:14:36 F19.localdomain dhclient[1526]: Sending on   LPF/p5p1/00:1e:c2:1d:50:7e
May 16 14:14:36 F19.localdomain dhclient[1526]: DHCPREQUEST on p5p1 to 255.255.255.255 port 67 (xid=0x5cc85c0c)
May 16 14:14:36 F19.localdomain NetworkManager[403]: <info> (p5p1): DHCPv4 state changed preinit -> reboot
May 16 14:14:36 F19.localdomain NetworkManager[403]: <info> Activation (p5p1) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
May 16 14:14:36 F19.localdomain NetworkManager[403]: <info> Activation (p5p1) Stage 5 of 5 (IPv4 Commit) started...
May 16 14:14:36 F19.localdomain avahi-daemon[308]: Joining mDNS multicast group on interface p5p1.IPv4 with address 192.168.1.144.
May 16 14:14:36 F19.localdomain avahi-daemon[308]: New relevant interface p5p1.IPv4 for mDNS.
May 16 14:14:36 F19.localdomain avahi-daemon[308]: Registering new address record for 192.168.1.144 on p5p1.IPv4.
May 16 14:14:37 F19.localdomain NetworkManager[403]: <info> (p5p1): device state change: ip-config -> secondaries (reason 'none') [70 90 0]
May 16 14:14:37 F19.localdomain NetworkManager[403]: <info> Activation (p5p1) Stage 5 of 5 (IPv4 Commit) complete.
May 16 14:14:37 F19.localdomain NetworkManager[403]: <info> (p5p1): device state change: secondaries -> activated (reason 'none') [90 100 0]
May 16 14:14:37 F19.localdomain NetworkManager[403]: <info> Policy set 'ens5' (p5p1) as default for IPv4 routing and DNS.
May 16 14:14:37 F19.localdomain NetworkManager[403]: <info> Activation (p5p1) successful, device activated.
May 16 14:14:38 F19.localdomain avahi-daemon[308]: Registering new address record for fe80::21e:c2ff:fe1d:507e on p5p1.*.
May 16 14:14:57 F19.localdomain NetworkManager[403]: <info> (p5p1): IP6 addrconf timed out or failed.
May 16 14:14:57 F19.localdomain NetworkManager[403]: <info> Activation (p5p1) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
May 16 14:14:57 F19.localdomain NetworkManager[403]: <info> Activation (p5p1) Stage 4 of 5 (IPv6 Configure Timeout) started...
May 16 14:14:57 F19.localdomain NetworkManager[403]: <info> Activation (p5p1) Stage 4 of 5 (IPv6 Configure Timeout) complete.
[root at F19 ~]# 


Chris Murphy