Hello (to myself, it seems) I continue with the warning message from both the messages log and the kern.log.0:
vmap allocation failed: use vmalloc=<size> to increase size The fact the time when it turns up is the same I encounter problems with modprobe is not a mere coincidence. With a little bit of search, I found that some folks suggest adding a boot parameter "vmalloc=some_sizeM", which I might try and report the results in the nearest future. However, it appears to me that the kernel is not the "bad guy" here. Something is related to the X. Since killing the X will fix it. ** Description changed: ** Summary changed: - system memory leakage due to suspend + system memory leakage due to suspend;vmap allocation failed: use vmalloc=<size> to increase size -- system memory leakage due to suspend;vmap allocation failed: use vmalloc=<size> to increase size https://bugs.launchpad.net/bugs/436665 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
