On Tue, 2011-10-04 at 16:55 -0800, Jef Spaleta wrote: > On Tue, Oct 4, 2011 at 3:32 PM, JB <jb.1234abcd@xxxxxxxxx> wrote: > > 13837ms udev-settle.service > > 11392ms plymouth-start.service > > > if you use the plot option instead of blame option and produce the svg > of the service timing you get a better feel for what Lennart was > talking about with regard to the udev settle being problematic. > > I'll try to break it down for you. Keep the following in mind when you > look over the svgs produced in susequent testing. > > udev-settle.service essentially calls udevadm settle and that's all it does. > udevadm settle takes FOREVER (15 seconds) to return during boot up on > my live media run But its returns more quickly on on F15 install (3 > seconds). I'll check a full F16 beta install soonish. And remember that all udevadm settle does is wait for the udev event queue to empty. So essentially all that's going on here is 'wait for udev to be done', which is a fairly sensible prerequisite for all manner of other bits of boot. The reasons why udev takes a while to be 'done' are more interesting and Lennart went into some of them. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
