I'm guessing there is an implicit or explicit wake-up somewhere that I managed to miss. If it is implicit it could be hard to catch.
Mike Galbraith <bitbuc...@online.de> wrote: >On Thu, 2013-12-12 at 06:57 +0100, Mike Galbraith wrote: >> On Wed, 2013-12-11 at 21:45 -0800, H. Peter Anvin wrote: >> > As in it hangs at that point? >> >> Nope, it's still going. >> >> [1567.578340] pcc-cpufreq: (v1.10.00) driver loaded with frequency >limits: 1064 MHz, 2266 MHz >> >> Funny, continents move faster :) Maybe missing a write or two. > >When I get back it may be done booting. I'm gonna let it try for grins >while I'm away, then take a peek, see if I can spot it. > >[ 1567.578340] pcc-cpufreq: (v1.10.00) driver loaded with frequency >limits: 1064 MHz, 2266 MHz > done >Starting HAL daemon >done > > >Setting up (localfs) network interfaces: > lo > lo IP address: 127.0.0.1/8 > IP address: 127.0.0.2/8 done > eth0 device: Broadcom Corporation NetXtreme II BCM5709 Gig > No configuration found for eth0 unused > eth1 device: Broadcom Corporation NetXtreme II BCM5709 Gig > No configuration found for eth1 unused > eth2 device: NetXen Incorporated NX3031 Multifunction 1/10 >[ 2457.114007] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready >[ 2457.114455] netxen_nic: eth2 NIC Link is up >[ 2457.223582] IPv6: ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready > eth2 IP address: 0.0.0.0/32 -- Sent from my mobile phone. Please pardon brevity and lack of formatting. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
