Bug 1120864
| Summary: | [abrt] WARNING: CPU: 1 PID: 749 at drivers/gpu/drm/i915/intel_display.c:931 assert_pll+0x68/0x70 [i915]() | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Pete <pete> | ||||||
| Component: | xorg-x11-drv-intel | Assignee: | Adam Jackson <ajax> | ||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 20 | CC: | ajax, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, m.a.young, mchehab, xgl-maint | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Unspecified | ||||||||
| URL: | https://retrace.fedoraproject.org/faf/reports/bthash/344e2e48f4d703105cc1c49237fce0fac06c22c4 | ||||||||
| Whiteboard: | abrt_hash:02378d013acbf140dbcb614858d2d732f9c5d3d7 | ||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2014-11-19 15:50:57 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
Pete
2014-07-17 21:37:26 UTC
Created attachment 918834 [details]
File: dmesg
Created attachment 919194 [details]
gzipped output from /sys/class/drm/card0/error
I am seeing a similar crash. I noticed in the dmesg output a request for the contents of /sys/class/drm/card0/error and I have successfully managed to get it (not easy when you don't have a working screen and the contents don't survive a reboot). I have gzipped the file to save space. The unzipped file is 776860 bytes.
With 3.15.6-200.fc20.x86_64 I still get backtraces in /var/log/messages but the screen no longer blanks, so my computer is usable again. *** This bug has been marked as a duplicate of bug 1101633 *** |