Public bug reported:
Kernel oops occurs randomly every now and then, seemingly when running
memory-intensive processes (so far, it happened to me when using bowtie2
or STAR).
Running Ubuntu 14.04 LTS on AWS EC2 instances (m4.* and c4.* family
classes). After the error occurs, the server stays accessible through
SSH, but the commands w, htop, ps (and maybe others) seem to hang, while
commands like ls, cd, top and others keep working. Whatever process was
running and (probably) caused the crash seems to go into a sleeping
mode.
Rebooting (sudo reboot) makes the instance refuse all connections (more
than an hour after initiating the reboot). Stopping the (AWS EC2)
instance and starting again makes the instance function normally again.
Restarting the task that was running when the instance crashed on the
newly (re)started instance usually works with no more problems.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: kernel-oops
** Attachment added: "Dmseg, lspci, uname and version info"
https://bugs.launchpad.net/bugs/1813018/+attachment/5231741/+files/ubuntu_kernel_oops.zip
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1813018
Title:
Kernel Oops - unable to handle kernel paging request; RIP is at
wait_migrate_huge_page+0x51/0x70
Status in linux package in Ubuntu:
New
Bug description:
Kernel oops occurs randomly every now and then, seemingly when running
memory-intensive processes (so far, it happened to me when using
bowtie2 or STAR).
Running Ubuntu 14.04 LTS on AWS EC2 instances (m4.* and c4.* family
classes). After the error occurs, the server stays accessible through
SSH, but the commands w, htop, ps (and maybe others) seem to hang,
while commands like ls, cd, top and others keep working. Whatever
process was running and (probably) caused the crash seems to go into a
sleeping mode.
Rebooting (sudo reboot) makes the instance refuse all connections
(more than an hour after initiating the reboot). Stopping the (AWS
EC2) instance and starting again makes the instance function normally
again.
Restarting the task that was running when the instance crashed on the
newly (re)started instance usually works with no more problems.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813018/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
