Additional info: once the system is running, I can remove the "exit 1"
from /etc/init.d/ulatencyd and then start ulatencyd process so this
seems to be some kind of race condition in the kernel. Some crashes have
kernel watchdog messages saying "Watchdog detected hard LOCKUP on cpu 1"
(sometimes the LOCKUP was on cpu 0).

Is it possible that the ulatencyd gets started before the system is
running on both cores (this system has dual core processor) and kernel
crashes with some feature that ulatencyd uses if all CPUs are not yet
up? Perhaps this really is a kernel bug that is triggered by ulatencyd?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1091986

Title:
  ulatencyd causes random kernel crashes during boot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ulatencyd/+bug/1091986/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to