Bug 14639
Summary: | BUG: unable to handle kernel paging request | ||
---|---|---|---|
Product: | Memory Management | Reporter: | Vadim Zeitlin (vadim) |
Component: | Other | Assignee: | Andrew Morton (akpm) |
Status: | CLOSED OBSOLETE | ||
Severity: | high | CC: | alan |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 2.6.30-2-amd64 | Subsystem: | |
Regression: | No | Bisected commit-id: |
Description
Vadim Zeitlin
2009-11-19 01:30:39 UTC
Gee. We have a million machines running that codepath a million times a minute. It's really well tested. I expect that your machine has hardware problems. FWIW I wasn't able to reproduce this problem. I do have another, perfectly reproducible, problem on this machine which I filed in Fedora bugzilla as I'm not 100% sure that it's a kernel problem (although considering that I see it under both Fedora and Debian it might be): https://bugzilla.redhat.com/show_bug.cgi?id=540199 In short, file system data seems to be corrupted after resuming from suspend and although the bug reported above was observed after a reboot, it might be possible that something bad happened to on disk data too because of this. If this is indeed the case there is probably still a bug somewhere in the kernel as ideally it shouldn't crash even if the file system was corrupted but I realize that this is going to be all but impossible to debug so I'd understand perfectly well if this bug was simply closed. As for hardware problems, I'd love this to be the case as it would mean that I still could hope to use Linux on this machine. Unfortunately several things are against this hypothesis: 1. Windows 7 (x64) doesn't show any problems even when redoing the equivalent of the "make -j8" I'm running under Linux a dozen times in a row (this is my primary test because this is I'd actually like to use this machine for building software, I just need to stop testing/crashing it first...) 2. I ran LinX under Windows and sys_basher under Fedora for several hours without any problems (this is before suspending and resuming under Linux -- after resuming things start crashing immediately, see the Fedora bug report above) 3. I ran memtest for the entire night (10+ hours) and it didn't find any problems. So if it is a hardware problem I really don't know what could it be... Anyhow, to summarize, this bug is probably an extremely rare consequence of file system corruption caused by the other bug so this report should probably be closed as I don't know how to reproduce it nor can I provide any more information about it. |