Bug 83421
Summary: | oom-killer invoked, machine hangs on 32-bit PAE kernel 3.12 to 3.17 but not 3.11 | ||
---|---|---|---|
Product: | Memory Management | Reporter: | Trevor Cordes (kernelbugs) |
Component: | Other | Assignee: | Andrew Morton (akpm) |
Status: | NEW --- | ||
Severity: | high | ||
Priority: | P1 | ||
Hardware: | i386 | ||
OS: | Linux | ||
URL: | https://bugzilla.redhat.com/show_bug.cgi?id=1075185 | ||
Kernel Version: | 3.14.17-100.fc19 | Subsystem: | |
Regression: | Yes | Bisected commit-id: | |
Attachments: | oom data from /v/l/messages |
Description
Trevor Cordes
2014-08-29 07:55:46 UTC
Bug still exists as of 3.14.22-100.fc19. Had it crash while using it at 5:25am during the nightly cron/find (I was awake). X oom'd first and I lost control of everything (black screen). Virt console switching wouldn't work. Numlock was frozen on. Floppy disk light was frozen on(!!). However, the alt-sysrq keys I tried got logged to disk! However, the alt-sysrq reboot attempt didn't work as the system seems to have gone dead right before that (no more logs after after 10 oom's in 30s). I still haven't had time to switch to 64-bit as I discovered all my "easy" (read: contrived and wacky) "upgrade" options were impossible with the recent Fedoras. If anyone wants to help debug this I can still do it... System still works 100% ok bug-free in 3.11. But still exists as of 3.17.7-200.fc20.i686+PAE. Just upgraded to F20 and its newest kernel hoping it has been fixed, but within 24 hours the bug hit (at 5:22am again). I also saw a precursor to the bug within an hour of booting F20 doing a simple find . -newer on my home dir (83k files). I could tell the whole system bogged down, and just switching windows I could see the frames draw slowly until the find was done. In fact, it seemed boggy even about 10-20s after the find was done. Weird. Created attachment 162391 [details]
oom data from /v/l/messages
|