I am seeing the same thing in different circumstances: while developing
Launchpad, running "utilities/start-dev-soyuz.sh" and then "make
run_all", I've seen the similar OOPS like in comment #23 twice now (i.e.
exception in decrypt_scatterlist, vs. the OOPS from bug 836513 which
happens in encrypt_scatterlist).
The worst thing is that system seems to remain usable (except that
gnome-screensaver locks you out of the system until you kill it from a
virtual console or ssh), but after you reboot, your changes/new files
created after the panic are lost.
FWIW, my dmesg has following lines (more of them, but just at different
times) on boot, but those could be the old "empty files start appearing"
bug in ecryptfs or something different:
[ 68.145110] Valid eCryptfs headers not found in file header region or xattr
region
[ 68.145113] Either the lower file is not in a valid eCryptfs format, or the
key could not be retrieved. Plaintext passthrough mode is not enabled;
returning -EIO
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/813146
Title:
kernel panic when running Python test suite on ecryptfs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ecryptfs/+bug/813146/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
