Comment # 31 on bug 902779 from Dr. Werner Fink

(In reply to Sebastian Kuhne from comment #28)

For me this looks like a network problem

(1 of 7) A start job is running for Modem Manager (11s / 1min 36s)
(1 of 7) A start job is running for Modem Manager (11s / 1min 36s)
(1 of 7) A start job is running for Modem Manager (12s / 1min 36s)
(2 of 7) A start job is running for WPA Supplicant daemon (12s / 1min 36s)
(2 of 7) A start job is running for WPA Supplicant daemon (13s / 1min 36s)
(2 of 7) A start job is running for WPA Supplicant daemon (13s / 1min 36s)
(3 of 7) A start job is running for SuSEfirewall2 phase 1 (14s / no limit)

that is e.g. a static WLAN connection which is not ready and therefore will
hold the boot process at the point where e.g. the firewall is waiting on the
network target.