super slow startup because of DKMS

lapubell · 2015-05-14 20:36:58

Hello. After the latest pacman -Syu I started to get some weird ACPI behavior, and have a super slow startup.

any idea why dkms would take 3.5 minutes?

Also the weird ACPI stuff is not something I know how to research. I can explain it, but I'm not sure what to run to give anyone a better idea of what is happening.
This is a laptop running plugged in most of the time. When I disconnect the power cord, I get a pop up from XFCE letting me know that I'm discharging. Then, when I replug it, I don't get another notification for up to 10 minutes that the AC power is back and I'm charging. Also, If I ever put the machine into suspend and swap the power status while it's sleeping, when I wake it up everything is hanging. So, for example, I close the lid when the machine is plugged in, take it to a coffee shop, open it back up without plugging it into the wall, it's frozen.

$ systemd-analyze blame
    3min 29.063s dkms.service
         19.066s man-db.service
         13.976s mysqld.service
          5.186s accounts-daemon.service
          4.050s dev-sdb2.device
          2.622s NetworkManager.service
          2.595s lightdm.service
          2.493s systemd-fsck@dev-disk-by\x2duuid-7D61\x2d3669.service
          2.028s systemd-fsck@dev-disk-by\x2duuid-30bd4eeb\x2d1e5b\x2d42c2\x2db305\x2d4d841fe0a9da.service
          1.806s upower.service
          1.555s wpa_supplicant.service
          1.447s alsa-restore.service
          1.446s systemd-user-sessions.service
          1.245s systemd-journald.service
          1.150s systemd-tmpfiles-setup-dev.service
           895ms user@620.service
           770ms systemd-sysctl.service
           752ms polkit.service
           740ms sys-kernel-debug.mount
           739ms sys-kernel-config.mount
           721ms dev-hugepages.mount
           627ms boot.mount
           614ms systemd-vconsole-setup.service
           614ms systemd-remount-fs.service
           613ms dev-mqueue.mount
           598ms tmp.mount
           529ms systemd-rfkill@rfkill0.service
           513ms systemd-udevd.service
           511ms systemd-rfkill@rfkill1.service
           447ms systemd-journal-flush.service
           393ms rtkit-daemon.service
           392ms home-swap.swap
           362ms logrotate.service
           303ms shadow.service
           296ms systemd-logind.service
           284ms systemd-udev-trigger.service
           247ms home.mount
           233ms systemd-backlight@backlight:intel_backlight.service
           215ms dropbox@lapubell.service
           205ms udisks2.service
           190ms systemd-random-seed.service
           183ms user@1000.service
           156ms systemd-rfkill@rfkill2.service
           101ms kmod-static-nodes.service
            93ms systemd-tmpfiles-clean.service
            66ms systemd-tmpfiles-setup.service

Any help at all would be appreciated. Thanks!

Head_on_a_Stick · 2015-05-14 20:44:59

What is the output of:

journalctl -x|grep -i dkms
ls -l /etc/systemd/system/multi-user.target.wants

For your ACPI issues, open a terminal window and run:

journalctl -xf

Then plug & unplug the power cable and see what error messages are written in the journal.

lapubell · 2015-05-14 20:51:43

$ journalctl -x|grep -i dkms
-- Subject: Unit dkms.service has begun shutting down
-- Unit dkms.service has begun shutting down.
-- Subject: Unit dkms.service has begun start-up
-- Unit dkms.service has begun starting up.
May 13 15:23:08 klaptop dkms[353]: Kernel preparation unnecessary for this kernel.  Skipping...
May 13 15:23:22 klaptop dkms[353]: Building module:
May 13 15:23:38 klaptop dkms[353]: cleaning build area........
May 13 15:24:53 klaptop dkms[353]: make KERNELRELEASE=4.0.2-1-ARCH -C /usr/lib/modules/4.0.2-1-ARCH/build M=/var/lib/dkms/vboxhost/4.3.26/build............................
May 13 15:24:56 klaptop dkms[353]: cleaning build area....
May 13 15:24:56 klaptop dkms[353]: Kernel cleanup unnecessary for this kernel.  Skipping...
May 13 15:24:56 klaptop dkms[353]: DKMS: build completed.
May 13 15:24:56 klaptop dkms[353]: vboxdrv.ko:
May 13 15:24:56 klaptop dkms[353]: Running module version sanity check.
May 13 15:25:15 klaptop dkms[353]: - Original module
May 13 15:25:15 klaptop dkms[353]: - No original module exists within this kernel
May 13 15:25:15 klaptop dkms[353]: - Installation
May 13 15:25:15 klaptop dkms[353]: - Installing to /usr/lib/modules/4.0.2-1-ARCH/kernel/misc/
May 13 15:25:15 klaptop dkms[353]: vboxnetflt.ko:
May 13 15:25:15 klaptop dkms[353]: Running module version sanity check.
May 13 15:25:15 klaptop dkms[353]: - Original module
May 13 15:25:15 klaptop dkms[353]: - No original module exists within this kernel
May 13 15:25:15 klaptop dkms[353]: - Installation
May 13 15:25:15 klaptop dkms[353]: - Installing to /usr/lib/modules/4.0.2-1-ARCH/kernel/misc/
May 13 15:25:15 klaptop dkms[353]: vboxnetadp.ko:
May 13 15:25:15 klaptop dkms[353]: Running module version sanity check.
May 13 15:25:15 klaptop dkms[353]: - Original module
May 13 15:25:15 klaptop dkms[353]: - No original module exists within this kernel
May 13 15:25:15 klaptop dkms[353]: - Installation
May 13 15:25:15 klaptop dkms[353]: - Installing to /usr/lib/modules/4.0.2-1-ARCH/kernel/misc/
May 13 15:25:15 klaptop dkms[353]: vboxpci.ko:
May 13 15:25:15 klaptop dkms[353]: Running module version sanity check.
May 13 15:25:15 klaptop dkms[353]: - Original module
May 13 15:25:15 klaptop dkms[353]: - No original module exists within this kernel
May 13 15:25:15 klaptop dkms[353]: - Installation
May 13 15:25:15 klaptop dkms[353]: - Installing to /usr/lib/modules/4.0.2-1-ARCH/kernel/misc/
May 13 15:26:36 klaptop dkms[353]: depmod..............................
May 13 15:26:36 klaptop dkms[353]: DKMS: install completed.
-- Subject: Unit dkms.service has finished start-up
-- Unit dkms.service has finished starting up.

$ ls -l /etc/systemd/system/multi-user.target.wants
total 0
lrwxrwxrwx 1 root root 36 Dec  3 13:10 dkms.service -> /usr/lib/systemd/system/dkms.service
lrwxrwxrwx 1 root root 38 Dec 19 14:01 docker.service -> /usr/lib/systemd/system/docker.service
lrwxrwxrwx 1 root root 36 Dec 15 16:53 dropbox@user.service -> /etc/systemd/system/dropbox@.service
lrwxrwxrwx 1 root root 38 Dec  3 13:50 mysqld.service -> /usr/lib/systemd/system/mysqld.service
lrwxrwxrwx 1 root root 46 Dec  3 02:14 NetworkManager.service -> /usr/lib/systemd/system/NetworkManager.service
lrwxrwxrwx 1 root root 40 Apr 20 14:55 remote-fs.target -> /usr/lib/systemd/system/remote-fs.target
lrwxrwxrwx 1 root root 36 Dec  3 22:16 sshd.service -> /usr/lib/systemd/system/sshd.service

lapubell · 2015-05-14 20:53:45

no new messages showed up in the journal log, but I also got a response super fast from my notification system for both unplug and plug in. So, I don't know if I ran into the same issue this time.

Thanks for the speedy reply!

Head_on_a_Stick · 2015-05-14 21:00:15

lapubell wrote:

lrwxrwxrwx 1 root root 36 Dec  3 13:10 dkms.service -> /usr/lib/systemd/system/dkms.service

Your system is rebuilding your VBox modules every time you boot up.

Unless you need it to do this, you can stop it with:

# systemctl disable dkms.service

Then rebuild the modules manually when necessary.

lapubell · 2015-05-14 21:02:32

Yeah that makes sense.

Thanks for the insight!

Head_on_a_Stick · 2015-05-14 21:06:06

You're welcome

Arch Linux

#1 2015-05-14 20:36:58

super slow startup because of DKMS

#2 2015-05-14 20:44:59

Re: super slow startup because of DKMS

#3 2015-05-14 20:51:43

Re: super slow startup because of DKMS

#4 2015-05-14 20:53:45

Re: super slow startup because of DKMS

#5 2015-05-14 21:00:15

Re: super slow startup because of DKMS

#6 2015-05-14 21:02:32

Re: super slow startup because of DKMS

#7 2015-05-14 21:06:06

Re: super slow startup because of DKMS

Board footer