F20 Boot Delay

David L. Crow crow at OrangeBlood.org
Mon Jan 6 19:20:25 UTC 2014


After upgrading to F20 (fedup from F19), I am seeing a significant delay 
early in the boot process.  Interesting lines from dmesg at the relevant 
time are

[    0.000000] Linux version 3.12.6-300.fc20.x86_64 
(mockbuild at bkernel02) (gcc version 4.8.2 20131212 (Red Hat 4.8.2-7) 
(GCC) ) #1 SMP Mon Dec 23 16:44:31 UTC 2013
[    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.12.6-300.fc20.x86_64 
root=/dev/mapper/vg_waterloo-lv_root ro rd.lvm.lv=vg_waterloo/lv_root 
rd.md=0 rd.dm=0 SYSFONT=latarcyrheb-sun16 KEYTABLE=us rd.luks=0 
LANG=en_US.UTF-8 rd.lvm.lv=vg_waterloo/lv_swap quiet

....

[    3.999696] PM: Starting manual resume from disk
[    3.999700] PM: Hibernation image partition 253:0 present
[    3.999701] PM: Looking for hibernation image.
[    4.000088] PM: Image not found (code -22)
[    4.000091] PM: Hibernation image not present or could not be loaded.
[    4.078212] EXT4-fs (dm-1): mounted filesystem with ordered data 
mode. Opts: (null)
[    4.300374] systemd-journald[102]: Received SIGTERM
[    5.581305] SELinux:  Disabled at runtime.
[    5.581319] SELinux:  Unregistering netfilter hooks
[    5.610748] type=1404 audit(1389022514.307:2): selinux=0 
auid=4294967295 ses=4294967295
[   69.403203] systemd[1]: Found dependency on arp-ethers.service/start
[  129.409054] systemd[1]: Found dependency on basic.target/start
[  189.414943] systemd[1]: Breaking ordering cycle by deleting job 
timers.target/start
[  249.420808] systemd[1]: Job timers.target/start deleted to break 
ordering cycle starting with basic.target/start
[  249.423268] systemd[1]: Stopped Switch Root.
[  249.423314] systemd[1]: Stopping Switch Root.
[  249.424008] systemd[1]: Stopped target Switch Root.
[  249.424025] systemd[1]: Stopping Initrd File Systems.
[  249.424092] systemd[1]: Stopped target Initrd File Systems.
[  249.424099] systemd[1]: Stopping Initrd Root File System.
[  249.424133] systemd[1]: Stopped target Initrd Root File System.
[  249.424146] systemd[1]: Starting Collect Read-Ahead Data...
[  249.432398] systemd[1]: Starting Replay Read-Ahead Data...
[  249.432700] systemd[1]: Starting system-getty.slice.
[  249.433319] systemd[1]: Created slice system-getty.slice.
[  249.433352] systemd[1]: Starting Login Prompts.
[  249.433412] systemd[1]: Reached target Login Prompts.
[  249.433423] systemd[1]: Starting User and Session Slice.
[  249.434210] systemd[1]: Created slice User and Session Slice.

I booted without the "quiet" kernel parameter and did not see any 
additional logging at this delay point.

I have selinux disabled via the following /etc/sysconfig/selinux lines

SELINUX=disabled
SELINUXTYPE=targeted

Any thoughts as to what might be causing this or next steps in problem 
determination?
-- 
  David L. Crow                     Texas!  It's like a
  crow at OrangeBlood.org              whole other country.


More information about the users mailing list