Bug 746482
Summary: | general protection fault (address: 00aaaaaa00aaaaaa) | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | badseed <badseedtux> |
Component: | kernel | Assignee: | Eric Sandeen <esandeen> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 15 | CC: | gansalmon, icj, itamar, jonathan, kernel-maint, madhu.chinakonda |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Unspecified | ||
Whiteboard: | abrt_hash:ed21079a753c3302f1443dac4d9fae99de394502 | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-04-11 14:11:42 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: |
Description
badseed
2011-10-16 13:58:13 UTC
*** Bug 747096 has been marked as a duplicate of this bug. *** *** Bug 747099 has been marked as a duplicate of this bug. *** > kernel_tainted: 128
> kernel_tainted_long: Kernel has oopsed before.
We'll probably need the first oops... the dup'd bugs also are secondary.
If you could look in your logs for some oops prior to this, I'd appreciate it.
-Eric
Ok, maybe abrt was confused, thanks Josh...
> :Pid: 7683, comm: chrome-sandbox Not tainted 2.6.40.6-0.fc15.x86_64 #1 LENOVO
44014PG/44014PG
Is this reproducible? I wonder if it'd be worth stracing chromium (or chrome-sandbox?) before you click the death button, and see what it is accessing in /proc strace -f will follow any child processes ... -Eric if you could run the kernel-debug build at http://koji.fedoraproject.org/koji/buildinfo?buildID=304798 that might turn up a different trace that might be helpful to us to track this down. (it's going to be considerably slower than the regular build, due to the extra checking). Keith Packard pointed out that the value this is faulting on (00aaaaaa00aaaaaa) is likely a strip of grey pixels in ARGB format. (That it looks like a repeating pattern is another hint). It's likely the i915 driver is causing memory corruption in some circumstances. We know this happens after hibernation. *** Bug 802223 has been marked as a duplicate of this bug. *** |