[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1739928
T
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1739928
Title:
Ke
As far as I can see, nothing is wrong, except you put too much memory
pressure on your machine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1739928
Title:
Kernel segfault playing EVERSPACE
To man
What would be the problem?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1739928
Title:
Kernel segfault playing EVERSPACE
To manage notifications about this bug go to:
https://bugs.launchpad.net/ub
Well, not 6 seconds. It is 21 seconds.
I overlooked that timestamp in syslog and uptime are not in sync.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1739928
Title:
Kernel segfault playing EVERSPAC
It seems to me that this is not a kernel problem.
I guess that there was a NULL pointer dereference in RSG-Linux-Shipping when
the system started entering severe memory pressure. Then, due to severe memory
pressure, many memory allocation requests started stalling. But there is no
kernel oops mess
