2011/5/18 Kay Sievers <kay.siev...@vrfy.org>: > > Completely different! That's an Intel Core Duo 1.4 GHz laptop: > systemd-analyze blame | grep udev > 87ms udev-trigger.service > 13ms udev.service I updated systemd(to v26) and udev(to 168), still got ~1s startup time of udev.service plus udev-trigger.service.
May be some distribution added udev rules cause this? I'll do a bootchart to see the detail. > >>> Care to provide the full output of: >>> time udevadm test /class/block/sda1 >>> ? >> real 0m0.146s >> user 0m0.084s >> sys 0m0.048s >> See udevadm_sda2.txt in detail. > > It seems not slow. But it looks a bit weird. You are sure there is > nothing missing in the file? It was gathered by redirecting the output, shouldn't miss anything... What's wrong with the log? No scsi_id invocation message present? > We never call scsi_id, ata_id in your output, but get the links from it? > udev_rules_new: rules use 153420 bytes tokens (12785 * 12 bytes), > 29178 bytes buffer > ... > udev_rules_apply_to_event: LINK > 'disk/by-id/scsi-SATA_SAMSUNG_HM121HCS12SJD0S208504-part2' > /lib/udev/rules.d/60-persistent-storage.rules:99 _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
