<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - WARN_ON(!in_irq()) warnings from intel_check_page_flip beginning with 3.19-rc1, kernel flag `threadirqs`"
href="https://bugs.freedesktop.org/show_bug.cgi?id=89321">89321</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>WARN_ON(!in_irq()) warnings from intel_check_page_flip beginning with 3.19-rc1, kernel flag `threadirqs`
</td>
</tr>
<tr>
<th>Product</th>
<td>DRI
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Hardware</th>
<td>x86-64 (AMD64)
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux (All)
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>minor
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>DRM/Intel
</td>
</tr>
<tr>
<th>Assignee</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>sakari.m.kapanen@gmail.com
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>CC</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr></table>
<p>
<div>
<pre>Created <span class=""><a href="attachment.cgi?id=113816" name="attach_113816" title="dmesg.log which shows the warnings">attachment 113816</a> <a href="attachment.cgi?id=113816&action=edit" title="dmesg.log which shows the warnings">[details]</a></span>
dmesg.log which shows the warnings
This has been discussed in
<a href="http://lists.freedesktop.org/archives/intel-gfx/2015-February/059291.html">http://lists.freedesktop.org/archives/intel-gfx/2015-February/059291.html</a> ,
filing it here so it can be better tracked.
Beginning with kernel 3.19-rc1, there are warnings generated by the i915 from
the function intel_check_page_flip. A dmesg log from boot to the problem with
`drm.debug=13` is attached. This only happens when booting with threaded IRQs
enabled by the `threadirqs` kernel flag.
As pointed out on the mailing lists, this is probably caused because in_irq()
only tests for real hardware interrupts, not threaded ones. Further information
here: <a href="http://lists.freedesktop.org/archives/intel-gfx/2015-February/059623.html">http://lists.freedesktop.org/archives/intel-gfx/2015-February/059623.html</a>
Kernel: 3.19-rc1
Distro: Arch Linux
Machine: Asus Zenbook UX32VD (Intel HD4000 graphics)</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are on the CC list for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>