boottime increased again

[Phillip Susi]

Your dmesg is cut off and only shows what happened after 40+ seconds 
into the boot.  Try looking in your /var/log/kern.log and see if you can 
get back to where the timestamps roll back through 0.

MadMan2k wrote:
> the only error that is displayed is that /selinux is not found.
> But I added my full dmesg log as attachment.
> 
> My system is only a athlon XP2800+ with 768MB CL2.5 166Mhz Ram and
> a Maxtor 80GB 7200rpm hdd. (+200GB Maxtor 7200rpm data partition)
> 
> M2k
> 
> Phillip Susi wrote:
>> WOW!  1:25 bootchart?  Mine's 0:24.  It looks like you're spending an 
>> insane amount of time just doing hardware detection in the initrd ( 
>> ~44 seconds before the real init runs ).  Are you getting any kind of 
>> odd dmesg errors during this time?
>>
>> Then once the main system starts coming up, I see several fscks in 
>> there and evms stuff.  I assume you are using evms?  Seems like that 
>> is doing a lot of work it shouldn't need to.
>>
>> For reference I'm running an athlon 64 3200+ ( 2 years old now, socket 
>> 774 I think it was, before 939 ), 1 gig of corsair low latency pc3200 
>> sdram, and booting from a hardware fakeraid raid0 of 2 x 10,000 rpm 36 
>> gig WD raptor drives partitioned as:
>>
>> 1 - 40 gigs NTFS winder's partition ( never use anymore )
>> 2 - (extended partition)
>> 3 - 10 gig experimental partition ( alternate OSes and such )
>> 5 - 50 MB /boot  ext2
>> 6 - 1 gig swap   swap
>> 7 - 22 gig /     reiserfs
>>
>> MadMan2k wrote:
>>> I'm sorry I forgot, who was responsible for the boot-time 
>>> optimizations, so I am sending it to the devel.
>>>
>>> after the first work on that, my bootime used to be at ~70s and 
>>> increased now again.
>>> I am not sure with which update it started, but I think it was 
>>> sometime after linux went final.
>>>
>>> here is my bootchart
>>> http://www.madman2k.net/files/dapper-20060125-1.png
>>>
>>> M2k
>>>
>>
>>
>