Bug 4199 - 2_a3: initrd time changed from 24s to 5min 30s
Summary: 2_a3: initrd time changed from 24s to 5min 30s
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 2120 4198
  Show dependency tree / graph
 
Reported: 2012-01-20 05:07 CET by Bit Twister
Modified: 2012-02-26 12:15 CET (History)
1 user (show)

See Also:
Source RPM: systemd-43-1.mga2.src.rpm
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Bit Twister 2012-01-20 05:07:13 CET 
Description of problem:

System boot completion has changed from 
Startup finished in 2s 243ms 257us (kernel) + 19s 697ms 628us (initrd) + 24s 132ms 212us (userspace) = 46s 73ms 97us.

to 
Startup finished in 621ms 638us (kernel) + 5s 15ms 898us (initrd) + 5min 30s 819ms 940us (userspace) = 5min 36s 457ms 476us.


Version-Release number of selected component (if applicable):


How reproducible: Always


Steps to Reproduce:
1. install latest updates, reboot
2. grep finish /var/log/messages until it shows up.

$ systemd-analyze blame
 12390ms fedora-loadmodules.service
 12349ms systemd-vconsole-setup.service
  8636ms fedora-readonly.service
  7270ms media.mount
  7269ms sys-kernel-debug.mount
  7269ms sys-kernel-security.mount
  7268ms dev-hugepages.mount
  7256ms udev-trigger.service
  7255ms dev-mqueue.mount
  7235ms fedora-storage-init.service
  6920ms systemd-remount-api-vfs.service
  6919ms remount-rootfs.service
  6914ms hwclock-load.service
  5609ms systemd-sysctl.service
  5592ms systemd-modules-load.service
  3325ms network-up.service
  2803ms mysqld.service
  2191ms shorewall.service
  1608ms postfix.service
  1357ms udev-settle.service
  1334ms udev.service
  1146ms privoxy.service
   905ms vboxdrv.service
   652ms resolvconf.service
   587ms network.service
   546ms nfs-server.service
   488ms numlock.service
   406ms portreserve.service
   365ms netfs.service
   335ms named.service
   325ms iptables.service
   303ms msec.service
   263ms nfs-common.service
   240ms udev-post.service
   225ms local.mount
   223ms rpcbind.service
   204ms systemd-readahead-collect.service
   200ms xinetd.service
   200ms systemd-readahead-replay.service
   185ms avahi-daemon.service
   161ms systemd-logind.service
   120ms stunnel.service
    94ms rsyslog.service
    94ms vmguest.mount
    82ms video.mount
    80ms accounts.mount
    79ms console-kit-daemon.service
    46ms acpid.service
    39ms vboxballoonctrl-service.service
    39ms dbus.service
    36ms fedora-storage-init-late.service
    28ms console-kit-log-system-start.service
    28ms fedora-wait-storage.service
    16ms rtkit-daemon.service
     7ms systemd-tmpfiles-setup.service
     3ms systemd-user-sessions.service
Manuel Hiebel 2012-01-20 12:27:35 CET

Blocks: (none) => 2120

Manuel Hiebel 2012-01-20 12:28:23 CET

Blocks: (none) => 4198

Comment 1 Bit Twister 2012-01-27 08:16:05 CET 
Resolution, clean Alpha3 install, apply updates, reboot.

Jan 27 00:48:23 wb2 systemd[1]: Startup finished in 600ms 279us (kernel) + 4s 764ms 465us (initrd) + 24s 756ms 206us (userspace) = 30s 120ms 950us.
Comment 2 Bit Twister 2012-01-27 08:16:52 CET 
Oops, forgot to mark it resolved.

Status: NEW => RESOLVED
Resolution: (none) => FIXED

Comment 3 Bit Twister 2012-02-26 06:21:45 CET 
Feb 25 23:12:38 wb2 systemd[1]: Startup finished in 634ms 909us (kernel) + 9s 17ms 825us (initrd) + 5min 45s 274ms 959us (userspace) = 5min 54s 927ms 693us.

bug 3823 creates the failure condition.

Source RPM: systemd-38-8.mga2.src.rpm => systemd-43-1.mga2.src.rpm
Status: RESOLVED => REOPENED
Resolution: FIXED => (none)

Comment 4 Colin Guthrie 2012-02-26 12:15:38 CET 
There are likely many different cases that cause boot time elongation like in bug 3823. They all need to be fixed, but I'm not sure having this generic tracker bug for them is useful.

As the above bug is now fixed, I'll close this one too. Feel free to reopen if needed however.

Resolution: (none) => FIXED
Status: REOPENED => RESOLVED
CC: (none) => mageia
Note You need to log in before you can comment on or make changes to this bug.