It looks like the stack is junk, the chain of fns listed just isn't correct for what would happen within the apparmor hook. It is likely that parts of that sequence happened at some point, but tracing down what actually caused the oops from the attached screenshot isn't possible.
Is this a reproducible oops? If so can you try booting with apparmor=0 as a parameter to the kernel command line, that completely remove apparmor from being used and help to decide whether its potentially causing the oops. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/805714 Title: possible apparmor related panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/805714/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
