On Tue, May 10, 2011 at 20:37, Koen Kooi <k...@dominion.thruhere.net> wrote:
>>> root@beagleboard-systemd:~# time ( udevadm trigger ; udevadm settle ) >>> >>> real 0m10.475s >> >> Ok, at least the timeout issue seems gone. >> >> How many device do you have? >> find /sys -name uevent | wc -l > > root@beagleboard-systemd:/usr/bin# find /sys -name uevent | wc -l > 462 > >> How many devices have a modalias: >> find /sys -name modalias | wc -l > > root@beagleboard-systemd:/usr/bin# find /sys -name modalias | wc -l > 84 That looks all fine. > parse_file: reading '/etc/udev/rules.d/50-udev-default.rules' as rules file > parse_file: reading '/etc/udev/rules.d/95-udev-late.rules' as rules file > parse_file: reading '/etc/udev/rules.d/local.rules' as rules file > parse_file: reading '/etc/udev/rules.d/permissions.rules' as rules file > parse_file: reading '/etc/udev/rules.d/run.rules' as rules file > parse_file: reading '/etc/udev/rules.d/udev.rules' as rules file What are these files? There is no default udev rules file in /etc. 'late' is years old, and the ones without number prefix look like they come from something else, and they shouldn't be there. > real 0m0.065s >> If you run it only for certain subsystems, what does it give you: >> time ( udevadm trigger -s block; udevadm settle ) > > That triggers a preempt bug and oopses the kernel. Great! :) >> time ( udevadm trigger -s tty; udevadm settle ) > > root@beagleboard-systemd:~# time ( udevadm trigger -s tty; udevadm settle ) > > real 0m1.203s > user 0m0.000s > sys 0m0.031s That's seems very long compared to the above run for a single tty. >> I'll be around Fri+Sat. Maybe we'll walk into each other ... > > I'll attend the systemd talk :) Good. See you there. Kay _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
