I don't know, the cause is apparently that IRQs are disabled, but I don't know whether that's considered an error. The aesni_intel module is needed to trigger the bug, but that doesn't imply that it contains the bug. It's possible that ecryptfs is using it wrong, or that the fallback code (which is used when aesni_intel is not available) happens to contain something that avoids the bug. Since ecryptfs is the module that binds all these other modules together, I thought that was the right place to ask.
The ecryptfs mailing list doesn't seem very active though, is it normal that this takes so long? Should I send it directly to one of the maintainers? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1265841 Title: kernel BUG at /build/buildd/linux-3.11.0/fs/buffer.c:1268!; RIP: 0010:[<ffffffff816e3efd>] [<ffffffff816e3efd>] check_irqs_on.part.11+0x4/0x6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1265841/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
