Created attachment 356681 [details] boot-duration file for "fast boot" Description of problem: For several consequent boots I've experienced the plymouth progress bar (text one, no kms) was already up to 100% while real boot procedure was just about to get IP address for eth0 devices (found by pressing Esc), which is far from being 100% ready. Version-Release number of selected component (if applicable): plymouth-0.7.0-0.2009.05.15.1.fc11.x86_64 How reproducible: Do not know. You can use the attached boot-duration file. Additional info: In my opinion this gets worse and worse with every boot, but this is just my feeling.
Created attachment 356683 [details] boot-duration file for normal boot Attached is the boot duration file created by the first boot after I deleted the one that was stored and showing incorrect progress.
It is here again. If I can provide any other information to debug this, please let me know: 0.044:RCkernelparam 0.044:RChostname 0.899:RCmountfs 0.902:RCswap 0.903:microcode_ctl 0.905:sysstat 0.905:akmods 0.906:cpuspeed 0.907:ip6tables 0.909:iptables 0.909:nvidia 0.941:network 0.947:auditd 0.949:portreserve 0.951:restorecond 0.953:rsyslog 0.954:irqbalance 0.954:rpcbind 0.955:nfslock 0.956:rpcidmapd 0.957:rpcgssd 0.957:messagebus 0.959:cups 0.963:netfs 0.963:acpid 0.964:lm_sensors 0.964:pcscd 0.965:udev-post 0.965:autofs 0.974:bluetooth 0.974:sshd 0.977:ntpd 0.978:sendmail 0.979:crond 0.980:munin-node 0.986:smolt 0.987:atd 0.987:avahi-daemon 0.988:haldaemon 1.000:wine 1.000:local
I can't solve the issue of your system booting slowly, all I can do is stop the progress bar from progressing all the way to the end before it mounts / and checks the progress times file. I'll put a limit of 25% of how far it can progress without any data from a progress file. Somewhere between RChostname and RCmountfs you have something very slow happening (fsck?). It may be in your /var/log/messages.
This is missunderstanding. My system is not booting slow or fast, just the progress bar does not correspond to boot process. In the case of "fast" boot progress bar rockets to its end just after it starts, but under the hood the boot process is still the same one. Please compare the files for so called "fast boot" and "normal boot". You can see that timestamps in "normal boot" file are let's say equaly spread over the boot time, but in the "fast boot" those are pushed towards 1.0. The boot process (services starting) under plymouth is still the same, there is no difference (no fsck), just the timestamp stored in plymouth boot-duration file are somehow tending to be closer to 1.0 for most of the timestamps with every boot. IMHO there is some calculation problem in the mechanism that is correcting the values with every boot.
This message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '11'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 11's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 11 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.