Bug 61661 - WARNING in ironlake_crtc_disable: pipe_off wait timed out
Summary: WARNING in ironlake_crtc_disable: pipe_off wait timed out
Status: RESOLVED MOVED
Alias: None
Product: Drivers
Classification: Unclassified
Component: Video(DRI - Intel) (show other bugs)
Hardware: x86-64 Linux
: P1 low
Assignee: intel-gfx-bugs@lists.freedesktop.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-09-19 09:44 UTC by Meelis Roos
Modified: 2014-01-23 08:46 UTC (History)
2 users (show)

See Also:
Kernel Version: 3.11
Subsystem:
Regression: No
Bisected commit-id:


Attachments
dmesg from 3.12-rc1 with drm debug (57.27 KB, application/octet-stream)
2013-09-19 09:44 UTC, Meelis Roos
Details

Description Meelis Roos 2013-09-19 09:44:43 UTC
Created attachment 108891 [details]
dmesg from 3.12-rc1 with drm debug

There is a seemingly harmless WARNING on every bootup on my PC with DP monitor. It appeared between 3.6 and 3.7, first reported on LKML https://lkml.org/lkml/2012/11/12/343 in Nov 2012. Later it was added to a bugzilla bug https://bugzilla.kernel.org/show_bug.cgi?id=52061 where the old dmesgs from 3.6 and 3.7 are still present. This bug came out to be something different so I am resubmitting it as a separate bug on Ironlake.

I retested it with 3.11 and 3.12-rc1, it is still there, dmesg with drm debug from 3.12-rc1-00101-ged24fee is attached.
Comment 1 Daniel Vetter 2013-09-19 12:31:35 UTC
Already tracked in the fdo bz at: https://bugs.freedesktop.org/show_bug.cgi?id=54687

I guess we can keep this one here around anyway. For the actual bug we've unfortunately not grown any clue, but it really shouldn't happen. Hence why we're keeping the WARN in there as a remainder.
Comment 2 Jani Nikula 2014-01-23 08:46:28 UTC
(In reply to Daniel Vetter from comment #1)
> Already tracked in the fdo bz at:
> https://bugs.freedesktop.org/show_bug.cgi?id=54687
> 
> I guess we can keep this one here around anyway. For the actual bug we've
> unfortunately not grown any clue, but it really shouldn't happen. Hence why
> we're keeping the WARN in there as a remainder.

IMO no reason to keep this open. Let's track this at fdo. Please reopen if this turns out to be a different bug after all.

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