https://bugzilla.novell.com/show_bug.cgi?id=776563 https://bugzilla.novell.com/show_bug.cgi?id=776563#c0 Summary: NetworkManager 80000+ms on boot Classification: openSUSE Product: openSUSE 12.2 Version: RC 2 Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: i@marguerite.su QAContact: qa-bugs@suse.de Found By: --- Blocker: --- Created an attachment (id=502816) --> (http://bugzilla.novell.com/attachment.cgi?id=502816) boot plot by systemd-analyze User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.1 (KHTML, like Gecko) Chrome/22.0.1190.0 Safari/537.1 SUSE/22.0.1190.0 Hi, I saw the post on lizards teaching us how to improve openSUSE boot performance to 2s, but when it was my case: marguerite@linux:~> systemd-analyze blame 88848ms NetworkManager.service 5578ms home.mount 4145ms systemd-modules-load.service 2684ms windows-C.mount 2089ms localnet.service 1903ms systemd-vconsole-setup.service 1492ms remount-rootfs.service 1341ms xdm.service 1300ms sys-kernel-security.mount 1287ms udev.service 1255ms systemd-remount-api-vfs.service 1138ms systemd-logind.service 931ms vboxdrv.service 860ms media.mount 851ms var-lock.mount 849ms dev-hugepages.mount 848ms var-run.mount 841ms dev-mqueue.mount 825ms sys-kernel-debug.mount 708ms syslog.service 231ms systemd-readahead-replay.service 218ms udev-trigger.service 210ms vboxweb-service.service 207ms systemd-readahead-collect.service 206ms systemd-tmpfiles-setup.service 203ms network.service 199ms vboxballoonctrl-service.service 192ms systemd-sysctl.service 181ms boot.mount 138ms upower.service 130ms bluez-coldplug.service 89ms console-kit-log-system-start.service 89ms fbset.service 48ms rtkit-daemon.service 42ms systemd-user-sessions.service 28ms console-kit-daemon.service 21ms acpid.service 15ms rc-local.service 2ms sys-fs-fuse-connections.mount and I had a few tests with help from Binli: * It's not an specific AP related bug. It's even slower without an AP. because then NM took 60000+ ms, but systemd-modules-load.service took another 30000+ ms. * Binli said it may be related to these lines: Aug 19 23:28:39 linux NetworkManager[709]: <warn> Trying to remove a non-existant call id. Aug 19 23:28:51 linux NetworkManager[709]: <info> Auto-activating connection 'NETGEAR'. Since I'm not a low-level hacker, and Binli is busy at the moment, so I attached my logs and plots to see if any other basesystem maintainer can offer some help. Marguerite Reproducible: Always Steps to Reproduce: boot Actual Results: after around 5 minutes I saw the KDE splash Expected Results: It should be below 1 minute NM version: 0.9.4.0-5.2.1 wpa_supplicant version: 1.0-2.1.2 Kernel version: 3.4.6-1.1-desktop systemd version: 44-10.1.1 (also happens to 44-9) by the way, systemd split systemd-analyze to a separate package. so you need to download and install systemd-analyze manually from https://build.opensuse.org/package/binaries?package=systemd&project=openSUSE%3A12.2&repository=standard -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.