Small comment: We might be dealing with 2 different situations/bugs for the two different stack traces we got (possible race condition / deadlock for the ext4 page flush for high memory pressure AND kmem_cache_alloc trying to access wrong addresses)...
As I said, investigating both and checking if they can be correlated. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1389787 Title: 3.11 memory consumption leads to HANG (not sure if 3.13 suffers from this). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1389787/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
