------------[ cut here ]------------ WARNING: CPU: 2 PID: 0 at /work/autotest/nobackup/linux-test.git/drivers/gpu/drm/i915/intel_uncore.c:566 hsw_unclaimed_reg_debug.isra.10+0x6c/0x84() Unclaimed register detected before writing to register 0xc4040 Modules linked in: microcode r8169 CPU: 2 PID: 0 Comm: swapper/2 Not tainted 4.1.0-rc2-test+ #4 Hardware name: MSI MS-7823/CSM-H87M-G43 (MS-7823), BIOS V1.6 02/22/2014 0000000000000236 ffff880215203c68 ffffffff81ba8161 0000000000000000 ffff880215203cb8 ffff880215203ca8 ffffffff81080dbb 0000000000000000 ffffffff81626bc6 ffff88020de60068 00000000000c4040 0000000000000001 Call Trace: <IRQ> [<ffffffff81ba8161>] dump_stack+0x4c/0x65 [<ffffffff81080dbb>] warn_slowpath_common+0xa1/0xbb [<ffffffff81626bc6>] ? hsw_unclaimed_reg_debug.isra.10+0x6c/0x84 [<ffffffff81080e78>] warn_slowpath_fmt+0x46/0x48 [<ffffffff81626bc6>] hsw_unclaimed_reg_debug.isra.10+0x6c/0x84 [<ffffffff81629ac4>] hsw_write32+0x86/0xcf [<ffffffff81616246>] cpt_irq_handler+0x1e8/0x1f5 [<ffffffff81616347>] ivb_display_irq_handler+0xf4/0x11b [<ffffffff81619837>] ironlake_irq_handler+0x187/0x24d [<ffffffff810ceba8>] handle_irq_event_percpu+0xf7/0x2a3 [<ffffffff810ced95>] handle_irq_event+0x41/0x64 [<ffffffff810d17e3>] handle_edge_irq+0xa0/0xb9 [<ffffffff8103f961>] handle_irq+0x11d/0x128 [<ffffffff8109d5a0>] ? atomic_notifier_call_chain+0x14/0x16 [<ffffffff81bc2fde>] do_IRQ+0x4e/0xc4 [<ffffffff81bc11f0>] common_interrupt+0x70/0x70 <EOI> [<ffffffff819c9788>] ? cpuidle_enter_state+0xd8/0x135 [<ffffffff819c9784>] ? cpuidle_enter_state+0xd4/0x135 [<ffffffff819c9811>] cpuidle_enter+0x17/0x19 [<ffffffff810b545a>] cpuidle_idle_call+0xf2/0x180 [<ffffffff810b5613>] cpu_idle_loop+0x12b/0x164 [<ffffffff810b565f>] cpu_startup_entry+0x13/0x14 [<ffffffff81066a3a>] start_secondary+0x102/0x106 [<ffffffff81066938>] ? set_cpu_sibling_map+0x35e/0x35e ---[ end trace 77c6a96cf41e96d1 ]---
I'm still triggering warnings in the i915 code. :-(
config attached.
-- Steve
On Thu, May 7, 2015 at 9:40 PM, Steven Rostedt rostedt@goodmis.org wrote:
Please retry with snd-hda-intel blacklisted. At least last time I checked that was the only culprit left, i915 is just the messenger here. The other one was stupid things done by the bios, but we should correctly clear that up since a long time. -Daniel
On Fri, 8 May 2015 08:55:46 +0200 Daniel Vetter daniel@ffwll.ch wrote:
On Thu, May 7, 2015 at 9:40 PM, Steven Rostedt rostedt@goodmis.org wrote:
Maybe it's my bios still (it is an older box). I'll just block out compiling in SND_HDA_INTEL, so that it doesn't break my tests (they fail on a WARNING).
-- Steve
On Fri, 8 May 2015 12:08:31 -0400 Steven Rostedt rostedt@goodmis.org wrote:
Hmm, right after I posted this I triggered the Call Trace again with
# CONFIG_SND_HDA_INTEL is not set
:-/
Now to figure out how to keep this from triggering. I may just keep adding a patch to hide that warning.
-- Steve
On Fri, 8 May 2015 12:18:10 -0400 Steven Rostedt rostedt@goodmis.org wrote:
Oh, I forgot to mention, that before the Call Trace, I get theses:
[ 673.093330] [drm:intel_uncore_check_errors] *ERROR* Unclaimed register before interrupt [ 673.103206] [drm:intel_uncore_check_errors] *ERROR* Unclaimed register before interrupt [ 673.139252] [drm:intel_uncore_check_errors] *ERROR* Unclaimed register before interrupt [ 673.151323] [drm:ivybridge_set_fifo_underrun_reporting] *ERROR* uncleared fifo underrun on pipe A [ 673.160745] [drm:intel_cpu_fifo_underrun_irq_handler] *ERROR* CPU pipe A FIFO underrun
Mean anything?
-- Steve
On Fri, May 08, 2015 at 12:57:01PM -0400, Steven Rostedt wrote:
Ok, so it's really i915 to blame for this.
Display fifo underflow. It doesn happen very rarely when we change the configuration of cursors/overlays (because our code sucks, getting fixed). But in general I though we've curbed most of them ...
How easy is this to reproduce? It would be interesting to see what the driver is doing with drm.debug=0xe, but that's a veritable firehose. You can change that modparam in /sys/modules/drm/parameters/debug at runtime and it has immediate effect. But we don't keep a running log around.
Other things to check: - Is the fifo underrun always right next to to unclaimed register issue in dmesg? - i915.mmio_debug=10 or so for hopefully more information around the next splat. Has some gfx performance impact though.
Thanks, Daniel
dri-devel@lists.freedesktop.org
-
Daniel Vetter -
Steven Rostedt