Bug 89321 - WARN_ON(!in_irq()) warnings from intel_check_page_flip beginning with 3.19-rc1, kernel flag `threadirqs`
Summary: WARN_ON(!in_irq()) warnings from intel_check_page_flip beginning with 3.19-rc...
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium minor
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-02-25 14:06 UTC by Sakari Kapanen
Modified: 2017-07-24 22:48 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments
dmesg.log which shows the warnings (164.44 KB, text/plain)
2015-02-25 14:06 UTC, Sakari Kapanen 		no flags Details
View All

Description Sakari Kapanen 2015-02-25 14:06:57 UTC 
Created attachment 113816 [details]
dmesg.log which shows the warnings

This has been discussed in http://lists.freedesktop.org/archives/intel-gfx/2015-February/059291.html , 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: http://lists.freedesktop.org/archives/intel-gfx/2015-February/059623.html

Kernel: 3.19-rc1
Distro: Arch Linux
Machine: Asus Zenbook UX32VD (Intel HD4000 graphics)
Comment 1 Jani Nikula 2015-03-10 17:04:36 UTC 
Fixed by

commit 6c51d46f135b00c00373fcd029786ccef2b02b5b
Author: Dave Gordon <david.s.gordon@intel.com>
Date:   Fri Mar 6 15:34:26 2015 +0000

    drm/i915: use in_interrupt() not in_irq() to check context

in drm-intel-fixes. Thanks for the report.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.