Bug 1139021
| Summary: | [abrt] WARNING: CPU: 0 PID: 1363 at drivers/gpu/drm/i915/intel_display.c:931 assert_pll+0x68/0x70 [i915]() | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Stan King <stanley.king> | ||||||
| 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, mchehab, xgl-maint | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Unspecified | ||||||||
| URL: | https://retrace.fedoraproject.org/faf/reports/bthash/b53019595614269b60473bd8b6c9d1f891b38d31 | ||||||||
| Whiteboard: | abrt_hash:02378d013acbf140dbcb614858d2d732f9c5d3d7 | ||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2014-11-19 15:51:08 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
Stan King
2014-09-07 14:14:50 UTC
Created attachment 935152 [details]
File: dmesg
Created attachment 937240 [details]
error info from /sys/class/drm/card0/error
Hello, everybody. I was able to reliably reproduce this issue with the kernel in use above, 3.15.10-201.fc20.x86_64.
Then, after the upgrade to kernel 3.16.2-200.fc20.x86_64, the error is less severe, at least for the one time I've tried it. X and the Chrome web browser remain running, and the following messages appear in the dmesg output:
[ 163.704211] [drm] stuck on render ring
[ 163.705282] [drm] GPU HANG: ecode 0:0x9f47f9fd, in chrome [1613], reason: Ring hung, action: reset
[ 163.705287] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[ 163.705289] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[ 163.705291] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[ 163.705301] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[ 163.705303] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 163.707997] [drm:i915_reset] *ERROR* Failed to reset chip: -19
[ 164.039708] chrome[1720]: segfault at 280 ip 00007f2440249c98 sp 00007fff7f66e540 error 4 in i965_dri.so[7f243ff1d000+500000]
I'll attach the data that I copied out of /sys/class/drm/card0/error.
Let me know if I can provide more information.
*** This bug has been marked as a duplicate of bug 1101633 *** |