On Sun, 16.01.11 11:11, Peter Robinson (pbrobinson@xxxxxxxxx) wrote: > > On Sun, Jan 16, 2011 at 7:32 AM, Jason D. Clinton <me@xxxxxxxxxxxxxxxx> wrote: > > There's a twenty second pause in my boot sequence, shown below, before GDM > > starts and I'm not certain if it's in NetworkManager waiting on org.bluez, > > bluez itself or the bluez systemd unit file. (Or maybe I'm completely off.) > > Later on, the bluetooth.service starts normally and Bluetooth is working > > normally. Any ideas how to debug this? > > Can you use bootchart [1] to map it, not sure if it works with systemd or not. > > Peter > > [1] http://meego.gitorious.org/meego-developer-tools/bootchart Yes it works fine with systemd, and this version even is packaged in Fedora as the "bootchart" package. Just add "init=/sbin/bootchartd initcall_debug printk.time=y" to the kernel cmdline to use it to profile systemd. Lennart -- Lennart Poettering - Red Hat, Inc. -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
