Bug 731588
Summary: | NMI Crash tracing back to ext4 code on IBM t60p | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | George B. Magklaras <georgios> |
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 15 | CC: | dzickus, esandeen, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, prd-fedora |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-05-14 18:06:31 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 781749 |
Description
George B. Magklaras
2011-08-17 22:32:20 UTC
Hi George, You have a lot going on there. Multiple warnings and an unknown NMI. What happens if you repeat the same set of tests but don't have skype running? That should make a bunch of the warnings go away it seems. I also don't know what is making you machine crash. Those stack traces are just warnings. Is it possible to take a picture of the screen when it crashes and attach it. You also mentioned that it can take 10-20 minutes after resume before it dies. Can you save the output of dmesg into a file and attach it after you resume. I want to be able to determine which problems are the result of a resume and which are something else. You can do this with 'dmesg > /tmp/dmesg.log'. Thanks, Don Eric, do those ext4 errors seem like something that could just be fallout from the NMI problem, or something else ? If the disk went out to lunch, it might cause the NMI problems and I assume the ext4 problems. Though I assumed the block I/O layer would have balked first. Cheers, Don This might have been related to the i915 memory corruption bug that was fixed in 2.6.43 recently. The NMI could feasibly have been generated if that corrupter had scribbled to a non-ram address. George, can you retry with that update, and see if the problem is solved ? |