<div class="gmail_quote">On Mon, Jan 17, 2011 at 15:09, Lennart Poettering <span dir="ltr"><<a href="mailto:mzerqung@0pointer.de">mzerqung@0pointer.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div></div><div class="h5">> getting default adapter: Activation of org.bluez timed out<br>
<br>
</div></div>Smells like a bluez problem. Note sure what is going on there.<br>
<br>
It might be a good idea to pass systemd.log_level=debug and<br>
systemd.log_target=kmsg on the kernel cmdline and then inspect "dmesg"<br>
after boot to figure out what is going on.<br></blockquote><div><br>I tried this here is some interesting output during boot:<br><br>Jan 17 20:56:22 jclinton-laptop kernel: [ 19.475805] systemd[1]: sys-devices-pci0000:00-0000:00:1a.1-usb4-4\x2d2-4\x2d2:1.0-bluetooth-hci0.device changed dead -> plugged<br>
Jan 17 20:56:22 jclinton-laptop kernel: [ 19.475823] systemd[1]: Trying to enqueue job bluetooth.target/start/fail<br>Jan 17 20:56:22 jclinton-laptop kernel: [ 19.475840] systemd[1]: Installed new job bluetooth.target/start as 146<br>
Jan 17 20:56:22 jclinton-laptop kernel: [ 19.475853] systemd[1]: Enqueued job bluetooth.target/start as 146<br>Jan 17 20:56:22 jclinton-laptop kernel: [ 19.475863] systemd[1]: bluetooth.target changed dead -> active<br>
Jan 17 20:56:22 jclinton-laptop kernel: [ 19.475871] systemd[1]: Job bluetooth.target/start finished, success=yes<br><br>So the bluetooth.target is now satisfied. Later on after 20s pause:<br><br>Jan 17 20:56:47 jclinton-laptop NetworkManager[1214]: <warn> bluez error getting default adapter: Activation of org.bluez timed out<br>
<br>And then 4 seconds later when pulseaudio is starting, it triggers the D-Bus Activation and then everything is fine.<br><br>Jan 17 20:56:51 jclinton-laptop pulseaudio[1721]: module-alsa-card.c: Failed to find a working profile.<br>
Jan 17 20:56:51 jclinton-laptop pulseaudio[1721]: module.c: Failed to load module "module-alsa-card" (argument: "device_id="29" name="platform-thinkpad_acpi" card_name="alsa_c<br>ard.platform-thinkpad_acpi" tsched=yes ignore_dB=no card_properties="module-udev-detect.discovered=1""): initialization failed.<br>
Jan 17 20:56:51 jclinton-laptop kernel: [ 60.825082] systemd[1]: Got D-Bus request: org.freedesktop.DBus.NameOwnerChanged() on /org/freedesktop/DBus<br>Jan 17 20:56:51 jclinton-laptop kernel: [ 60.826717] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Activator.ActivationRequest() on /org/freedesktop/DBus<br>
Jan 17 20:56:51 jclinton-laptop kernel: [ 60.826726] systemd[1]: Got D-Bus activation request for bluetooth.service<br>Jan 17 20:56:51 jclinton-laptop kernel: [ 60.827703] systemd[1]: Trying to enqueue job bluetooth.service/start/replace<br>
Jan 17 20:56:51 jclinton-laptop kernel: [ 60.827929] systemd[1]: Installed new job bluetooth.service/start as 658<br>Jan 17 20:56:51 jclinton-laptop kernel: [ 60.827936] systemd[1]: Enqueued job bluetooth.service/start as 658<br>
Jan 17 20:56:51 jclinton-laptop kernel: [ 60.827980] systemd[1]: About to execute: /usr/sbin/bluetoothd -n<br>Jan 17 20:56:51 jclinton-laptop kernel: [ 60.838118] systemd[1]: Forked /usr/sbin/bluetoothd as 1727<br>Jan 17 20:56:51 jclinton-laptop kernel: [ 60.838223] systemd[1]: bluetooth.service changed dead -> start<br>
Jan 17 20:56:51 jclinton-laptop kernel: [ 60.838255] systemd[1]: Incoming traffic on systemd-logger.socket<br>Jan 17 20:56:51 jclinton-laptop kernel: [ 60.838290] systemd[1]: Trying to enqueue job systemd-logger.service/start/replace<br>
Jan 17 20:56:51 jclinton-laptop kernel: [ 60.838315] systemd[1]: Installed new job systemd-logger.service/start as 759<br>Jan 17 20:56:51 jclinton-laptop kernel: [ 60.838325] systemd[1]: Enqueued job systemd-logger.service/start as 759<br>
Jan 17 20:56:51 jclinton-laptop kernel: [ 60.838350] systemd[1]: systemd-logger.socket changed listening -> running<br>Jan 17 20:56:51 jclinton-laptop kernel: [ 60.838398] systemd[1]: About to execute: /lib/systemd/systemd-logger<br>
Jan 17 20:56:51 jclinton-laptop kernel: [ 60.850099] systemd[1]: Forked /lib/systemd/systemd-logger as 1728<br>Jan 17 20:56:51 jclinton-laptop kernel: [ 60.850302] systemd[1]: systemd-logger.service changed dead -> running<br>
Jan 17 20:56:51 jclinton-laptop kernel: [ 60.850323] systemd[1]: Job systemd-logger.service/start finished, success=yes<br>Jan 17 20:56:51 jclinton-laptop bluetoothd[1727]: Bluetooth deamon 4.85<br><br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
My uneducated guess is that for some reason bluez is ordered after NM<br>
but NM wants to use bluez and hence we have a deadlock which is resolved<br>
via the timeout you see. On my own machine I do not see that behaviour<br>
however, which makes this very suspicious.<br></blockquote><div><br>I did an rpm -Va and I have no unit files which are not verified so it appears that I am starting Networkmanager before pulseaudio instead of with/after it. Perhaps my system has a unit file which requires network.target but comes before pulseaudio?<br>
<br>I tried to generate a dot file of the dep. graph but dot in rawhide infinite loops on the output.<br><br>This interesting though:<br>$ ls -l /etc/systemd/system/dbus-org.freedesktop.NetworkManager.service <br>lrwxrwxrwx. 1 root root 42 Oct 22 13:33 /etc/systemd/system/dbus-org.freedesktop.NetworkManager.service -> /lib/systemd/system/NetworkManager.service<br>
<br></div></div>