It would be good to know if when using the threadirqs parameter is a regression. If that is the case, we can bisect to identify the commit that introduced this.
Can you test the following kernels with the threadirqs parameter enabled and post back if any do not exhibit the bug: v3.2 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2-precise/ v3.4 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-quantal/ v3.8 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8-raring v3.12 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-trusty/ You don't have to test every kernel, just up until the kernel that first has this bug. If 3.2 has the bug, no need to test the rest. Thanks in advance! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1275116 Title: lowlatency-flavour crashes and locks up alot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1275116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs