Bug 903492
| Summary: | [abrt]: BUG: unable to handle kernel NULL pointer dereference at 0000000000000060 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jan Synacek <jsynacek> |
| Component: | xorg-x11-drv-intel | Assignee: | Adam Jackson <ajax> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 18 | CC: | ajax, balay, beland, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, xgl-maint |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Unspecified | ||
| Whiteboard: | abrt_hash:17d6a1b73d880aba048fc5595c676fc3181b88fa | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-02-05 18:25: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: | |||
|
Description
Jan Synacek
2013-01-24 07:19:58 UTC
*** Bug 895123 has been marked as a duplicate of this bug. *** Experiencing exactly the same problem if I close the lid even for a few seconds. The system reports: Not tainted 3.7.9-201.fc18.x86_64 #1 Dell Inc. Latitude E6320/0GJF11 I marked Bug 895123 as a duplicate; it was filed against xorg-x11-drv-intel. I think the reporter there is saying that this is fixed in Rawhide kernel-3.8.0-0.rc3.git1.2.fc19.x86_64, so this might be relatively easy to backport. ABRT did not report the problem, I assume because I had to reboot to recover from it. But obviously it is a serious problem to have a laptop you can't suspend, even if it is hardware-specific. (In reply to comment #2) > Experiencing exactly the same problem if I close the lid even for a few > seconds. The system reports: > Not tainted 3.7.9-201.fc18.x86_64 #1 Dell Inc. Latitude E6320/0GJF11 > > I marked Bug 895123 as a duplicate; it was filed against xorg-x11-drv-intel. We file DRM bugs against the relative xorg driver on purpose. > I think the reporter there is saying that this is fixed in Rawhide > kernel-3.8.0-0.rc3.git1.2.fc19.x86_64, so this might be relatively easy to > backport. This is neither "EasyFix" nor "Triaged". Pointing to a newer -rcX kernel is great, but that doesn't mean it's easy to pick out the specific commit that fixed it and since there's no root cause and only a single report that it's working, it isn't triaged either. We appreciate the effort. F18 should be getting a 3.8 kernel soon. In the meantime, you can test 3.8.0-1.fc19 from rawhide/koji and let us know if that fixes things for you. > > I think the reporter there is saying that this is fixed in Rawhide > > kernel-3.8.0-0.rc3.git1.2.fc19.x86_64, so this might be relatively easy to > > backport. > > This is neither "EasyFix" nor "Triaged". Pointing to a newer -rcX kernel is > great, but that doesn't mean it's easy to pick out the specific commit that > fixed it and since there's no root cause and only a single report that it's > working, it isn't triaged either. > > We appreciate the effort. F18 should be getting a 3.8 kernel soon. In the > meantime, you can test 3.8.0-1.fc19 from rawhide/koji and let us know if > that fixes things for you. A few comment as the submitter of Bug 895123 The stack trace I submitted for this problem was with kernel-3.8.0-0.rc3.git1.2.fc19.x86_64. [triggered with the listed additional i915 driver options] I claimed a different problem might be fixed by kernel-3.8.0-0.rc3.git1.2.fc19.x86_64 [well that problem comes up but much less frequently than with 3.7 kernel] I had this issue only once. I've been using various 3.8 rc kernels since then without problems. [and I haven't used the additional i915 driver options again] I can now close the lid with kernel-3.8.3-201.fc18.x86_64 and I do not see this problem. This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |