Boot time is slow when RTC not set as in the factory

Bug #1420473 reported by Pat McGowan on 2015-02-10
This bug affects 6 people
Affects Status Importance Assigned to Milestone
Canonical System Image
Ricardo Salveti
initramfs-tools (Ubuntu)
initramfs-tools (Ubuntu RTM)

Bug Description

When the RTC is not set, the apparmor cache is rebuilt on first boot resulting in a very long boot time.

Pat McGowan (pat-mcgowan) wrote :

Script that sets date and hwclock to which ever is latest from buildstamps of custom or rootfs, if device clock is older than that.

Ricardo Salveti (rsalveti) wrote :

There is a functionality already available in the initrd to help fixing such issues, but to know if that would work I need the following information:
1 - Remove any available SIM card from the device;
2 - Flash the with MTK's flasher (factory flash);
3 - Boot and skip the wifi network settings (once you connect ntp will set the clock to the right time);
4 - Enable developer mode and run the following: sudo dumpe2fs -h /dev/mmcblk0p6

Please paste the output of that command.

John McAleely (john.mcaleely) wrote :

As discussed in IRC, the machine was shutdown hard (power+volup) and booted again, because adb refused to come up on first boot (there's another bug about that).

phablet@ubuntu-phablet:~$ sudo dumpe2fs -h /dev/mmcblk0p6
dumpe2fs 1.42.10 (18-May-2014)
Filesystem volume name: system
Last mounted on: /home/jhm/Documents/barajas/krillin/system.tmpdir
Filesystem UUID: bbd9c800-5e7e-4b35-9184-9de6741443c8
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr resize_inode filetype extent sparse_super large_file uninit_bg
Filesystem flags: signed_directory_hash
Default mount options: user_xattr acl
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 131920
Block count: 527360
Reserved block count: 26368
Free blocks: 121055
Free inodes: 83607
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 128
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 7760
Inode blocks per group: 485
Filesystem created: Mon Feb 9 17:59:53 2015
Last mount time: Wed Jan 1 00:05:30 2014
Last write time: Wed Jan 1 00:05:30 2014
Mount count: 3
Maximum mount count: -1
Last checked: Mon Feb 9 17:59:53 2015
Check interval: 0 (<none>)
Lifetime writes: 65 MB
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Required extra isize: 28
Desired extra isize: 28
Journal inode: 8
Default directory hash: half_md4
Directory Hash Seed: 544ec946-29cf-492e-839d-d1e3786f7cfa
Journal backup: inode blocks
Journal features: (none)
Journal size: 64M
Journal length: 16384
Journal sequence: 0x0000000d
Journal start: 0

Launchpad Janitor (janitor) wrote :

This bug was fixed in the package initramfs-tools - 0.103ubuntu11

initramfs-tools (0.103ubuntu11) vivid; urgency=medium

  * scripts/local-premount/fixrtc:
    - Make it work with busybox (different date syntax)
    - Add support to retrieve the last mount time from the ubuntu touch system
    - Make it able to extract the filesystem created timestamp (useful when
      last mounted is older) LP: #1420473
 -- Ricardo Salveti de Araujo <email address hidden> Thu, 12 Feb 2015 04:34:46 -0200

Changed in initramfs-tools (Ubuntu):
status: New → Fix Released
Changed in canonical-devices-system-image:
status: Confirmed → In Progress
milestone: ww07-2015 → ww09-2015
Changed in canonical-devices-system-image:
status: In Progress → Fix Released
Changed in initramfs-tools (Ubuntu RTM):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers