registry team mailing list archive

[jim_charlton <charltn@xxxxxxxxx>]

Ah .... rats...  It always pays to double check everything many times
before writing a report.

Ureadahead puts its parameter file "pack" into /var/lib/ureadahead.  I
confirmed that the pack files were gone after I removed ureadahead.conf
and ureadahead-other.conf from /etc/init.

The I did the obvious further test test.  I put ureadahead.conf and
ureadahead-other.conf back into /etc/init (but left plymouth.conf out)
and rebooted.  It booted fast.  It also recreated the
/var/lib/ureadahead/pack file.  So I rebooted again.  It boots even
faster!!! (about 23 seconds).  Dang.  Ureadahead was not the problem.  I
booted a couple of times to confirm.

So.... I put plymouth.conf, plymouth-log.conf, plymouth-splash.conf and
plymouth-stop.conf back into /etc/init and rebooted.  No problem.  The
boot time remains at 23 seconds.  Note that I have only "ro" on the
kernel command line.  The original ubuntu distribution has also got
"quiet splash" there.  But I don't want those anyway.

I rebooted several times.  If I reboot from a terminal shell issuing the
command "reboot" (as root), the boot time is consistently 23 seconds.
If I reboot from the gdm desktop using the "restart" menu entry, the
boot time is about 48 seconds.  I don't know why there is a difference
here but I am not so worried about that difference.

Note that I have bootchart running during boot (bootchart.conf in
/etc/init).

I am now not sure I want to say what caused the slow boot problem.  But
removing ureadahead and plymouth and rebooting several times... and then
putting them back... appears to have solved the problem.  It could be
that simply removing any pack files in /var/lib/ureadahead and then
rebooting would have also solved the problem.  Perhaps someone could
test this.

Resume from suspend (lid closed/opened) still takes almost exactly 5
minutes (tested 2 times).  So that problem remains.

-- 
wakeup from sleep fails on toshiba nb305
https://bugs.launchpad.net/bugs/508516
You received this bug notification because you are a member of Registry
Administrators, which is the registrant for Fedora.