On Thu, 2017-01-05 at 22:36 +0000, Alin M Elena wrote:
Thanks Martin, here it is. http://sprunge.us/gfHW
Is this a regression with the 4.10-rc2 kernel? As a workaround, you could try to blacklist the aesni_intel module which is apparently causing trouble: echo blacklist aesni_intel >>/etc/modrobe.d/aesni.conf Background: I can see a BUG() in your logs related to loading the aesni_intel module. It's probably caused by recent changes in the crypto layer of the kernel. The boot delay is related to the following messages: Jan 05 18:32:01 circassia systemd-udevd[805]: seq 2404 '/devices/system/cpu/cpu0' is taking a long time Jan 05 18:32:01 circassia systemd-udevd[805]: seq 2407 '/devices/system/cpu/cpu3' is taking a long time ... Jan 05 18:34:01 circassia.dl.ac.uk systemd-udevd[805]: seq 2404 '/devices/system/cpu/cpu0' killed Jan 05 18:34:01 circassia.dl.ac.uk systemd-udevd[805]: seq 2407 '/devices/system/cpu/cpu3' killed ... Jan 05 18:34:01 circassia.dl.ac.uk systemd-udevd[805]: worker [994] terminated by signal 9 (Killed) Jan 05 18:34:01 circassia.dl.ac.uk systemd-udevd[805]: worker [994] failed while handling '/devices/system/cpu/cpu0' Jan 05 18:34:01 circassia.dl.ac.uk systemd-udevd[805]: worker [995] terminated by signal 9 (Killed) Jan 05 18:34:01 circassia.dl.ac.uk systemd-udevd[805]: worker [995] failed while handling '/devices/system/cpu/cpu1' Udev worker hanging on a CPU "add" or "change" event - I've never seen this before. Udev has hardly anything to do for cpu devices... but it's probably a side-effect of the BUG above.
I suspect something goes wrong at shutdown. since i see running jobs runnig related to the lvm attached bellow. http://sprunge.us/efbg
Not sure what you mean. I can see problems with your encrypted disk,
which is again probably related to the BUG().
Martin
--
Dr. Martin Wilck