Bug 86431 - [ivb] WARNING at drivers/gpu/drm/i915/intel_pm.c:5997 intel_display_power_put
Summary: [ivb] WARNING at drivers/gpu/drm/i915/intel_pm.c:5997 intel_display_power_put
Status: RESOLVED CODE_FIX
Alias: None
Product: Drivers
Classification: Unclassified
Component: Video(DRI - Intel) (show other bugs)
Hardware: All Linux
: P1 blocking
Assignee: intel-gfx-bugs@lists.freedesktop.org
URL:
Keywords:
Depends on:
Blocks: 84221
  Show dependency tree
 
Reported: 2014-10-16 21:42 UTC by brent s.
Modified: 2015-01-28 15:42 UTC (History)
3 users (show)

See Also:
Kernel Version: >= 3.16.0
Subsystem:
Regression: Yes
Bisected commit-id:


Attachments
dmesg output on 3.16.4-1 (166.55 KB, text/plain)
2014-10-16 22:36 UTC, brent s.
Details

Description brent s. 2014-10-16 21:42:58 UTC
In kernels >= 3.17, my AMD GPU does not seem to initialize.

For full background (including lspci output, dmesg, symptoms, acpidump, bisection, and other pertinent info), please see bug #84221
Specifically, in addition to the attachments and description, see comment 23, 24, 25.
Comment 1 Alex Deucher 2014-10-16 22:28:09 UTC
Please attach your full dmesg output (I couldn't find it on the other bug report).  Note that the AMD card is not connected to the laptop panel.  The AMD card is purely for offload rendering (e.g., AMD card renders a game and then the frame is sent to the Intel card for display).
Comment 2 brent s. 2014-10-16 22:36:12 UTC
Created attachment 154051 [details]
dmesg output on 3.16.4-1
Comment 3 brent s. 2014-10-16 22:39:23 UTC
Dmesg output attached.

The panel isn't attached to the AMD card? The ACPI issues in the other bug seem related to AMD, and it affects the display, even in TTY, so I had thought otherwise.

Let me know if you need any other output
Comment 4 Alex Deucher 2014-10-16 22:48:01 UTC
The radeon driver has initialized fine.  There are no displays wired to the radeon card at all.  It's purely for rendering offload.  If you are not getting a display it's an issue with the intel driver.
Comment 5 Alan 2014-10-23 13:46:31 UTC
(moved to Intel side)
Comment 6 Jani Nikula 2015-01-28 15:08:51 UTC
We seem to have neglected this bug a bit, apologies. Is this still an issue with recent kernels? Please attach dmesg with drm.debug=14 module parameter set. Thanks.
Comment 7 brent s. 2015-01-28 15:35:06 UTC
Actually, my apologies- I think this can be closed.

it seemed to be related to bug #84221 (which was then tracked in bug #84561). that's been fixed and incorporated into commit 7d0b93499f4879ddbc75d594f4ea216ba964f78e

that hasn't hit mainline as of 3.18.2 but it does seem to be in mainline stable: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=7d0b93499f4879ddbc75d594f4ea216ba964f78e (unfortunately i'm on a low-bandwidth connection so i can't clone the repo and see which tag it's under, and i'm not sure how to do that with cgit...)

BUT the display is working properly with that commit. I think it's solving this bug as well, but can't check at the moment. I'll test later tonight and let you know!
Comment 8 Jani Nikula 2015-01-28 15:42:18 UTC
Thanks, I'll close the bug - please reopen if the bug is still present.

Note You need to log in before you can comment on or make changes to this bug.