Bug 1236423
| Summary: | [abrt] BUG: unable to handle kernel NULL pointer dereference at 0000000000000010 [radeon] | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Andreas Tunek <andreas.tunek> | ||||
| Component: | xorg-x11-drv-ati | Assignee: | X/OpenGL Maintenance List <xgl-maint> | ||||
| Status: | CLOSED NEXTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 22 | CC: | gansalmon, itamar, jonathan, kernel-maint, kparal, labbott, madhu.chinakonda, mchehab, nicku, sebastien, xgl-maint | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Unspecified | ||||||
| URL: | https://retrace.fedoraproject.org/faf/reports/bthash/10a0e3035f02b141c42cd65cc9cd49f65f1c640f | ||||||
| Whiteboard: | abrt_hash:184a727d80efc463c1fac3d07f9d973bc61ec49c | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2015-08-04 19:05:17 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: | |||||||
| Attachments: |
|
||||||
|
Description
Andreas Tunek
2015-06-28 22:20:44 UTC
Created attachment 1044124 [details]
File: dmesg
4.0.4 works without a problem. Can't boot 4.0.6 either. Also happens on 4.0.7 in updates-testing. I can't reproduce this on Radeon R9 270 with a DisplayPort (nor DVI) monitor. It probably affects only certain cards (or maybe just Macs?). I'm not a maintainer of this component, but if you want to increase your chances of seeing this fixed, I suggest to report this to the upstream freedesktop bugzilla. See bug 1224579 (similar, but probably unrelated) for instructions how to do that. Added bugs here: https://bugzilla.kernel.org/show_bug.cgi?id=101131 https://bugs.freedesktop.org/show_bug.cgi?id=91253 Maybe it would be better if I tested the rawhide kernel? Can you do that in F22_ Yes, you can see them here: http://koji.fedoraproject.org/koji/packageinfo?packageID=8 You should be able to install F23 kernel on F22 just fine. (Some of them might have debugging options enabled, and be therefore considerably slower.) Tested rawhide kernel, bug report is here: https://bugzilla.redhat.com/show_bug.cgi?id=1240566 So now I should test F23 kernels as well? I see that you received feedback in the upstream freedesktop bug, but you haven't replied since then. If you want to see this fixed, your best chance is to study how to build your own kernel and then bisect the versions until you find the wrong commit. It requires quite some technical skills. If you don't feel up to it, you'll need to wait until someone else is able to reproduce the issue on their hardware and will do the bisecting. Or you can try to find someone technical in your surroundings, lend him your hardware and ask him/her to do it for you. If you need help with bisect, you can experiment with some scripts I wrote for making bisection on fedora easier https://pagure.io/fedbisect (In reply to Kamil Páral from comment #11) > I see that you received feedback in the upstream freedesktop bug, but you > haven't replied since then. If you want to see this fixed, your best chance > is to study how to build your own kernel and then bisect the versions until > you find the wrong commit. It requires quite some technical skills. If you > don't feel up to it, you'll need to wait until someone else is able to > reproduce the issue on their hardware and will do the bisecting. Or you can > try to find someone technical in your surroundings, lend him your hardware > and ask him/her to do it for you. I would like to see if the patch in https://bugzilla.redhat.com/show_bug.cgi?id=1224579 works, but that does not seem to be applied upstream. 4.1.2-200.fc22 does not work either. Fixed in 4.2 rc5 *** Bug 1240463 has been marked as a duplicate of this bug. *** |