From: Steven Rostedt <rostedt@goodmis.org>
To: LKML <linux-kernel@vger.kernel.org>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Jani Nikula <jani.nikula@linux.intel.com>
Subject: [WARNING - 3.14-rc2] i915: pipe_off wait timed out
Date: Fri, 14 Feb 2014 17:41:01 -0500 [thread overview]
Message-ID: <20140214174101.7892a945@gandalf.local.home> (raw)
[-- Attachment #1: Type: text/plain, Size: 3142 bytes --]
I get the following splat in my tests running 3.14-rc2:
[ 3.955123] WARNING: CPU: 0 PID: 1 at /work/autotest/nobackup/linux-test.git/drivers/gpu/drm/i915/intel_display.c:857 intel_wait_for_pipe_off+0x17a/0x2d0()
[ 3.955124] pipe_off wait timed out
[ 3.955127] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.14.0-rc2-test+ #10
[ 3.955128] Hardware name: /DG965MQ, BIOS MQ96510J.86A.0372.2006.0605.1717 06/05/2006
[ 3.955133] 0000000000000359 ffff88007d075868 ffffffff828dff7d 0000000000000006
[ 3.955136] ffff88007d0758b8 ffff88007d0758a8 ffffffff8106c015 0000000000001000^M
[ 3.955139] ffff880078d58000 0000000000071008 00000000fffb7b90 0000000000001000
[ 3.955140] Call Trace:
[ 3.955144] [<ffffffff828dff7d>] dump_stack+0x77/0x9e
[ 3.955147] [<ffffffff8106c015>] warn_slowpath_common+0xa5/0xf0
[ 3.955150] [<ffffffff8106c0f1>] warn_slowpath_fmt+0x51/0x60
[ 3.955153] [<ffffffff81b74e02>] ? gen4_read32+0x52/0x70
[ 3.955156] [<ffffffff81b1cd0a>] intel_wait_for_pipe_off+0x17a/0x2d0
[ 3.955158] [<ffffffff81b1cf64>] intel_disable_pipe+0x104/0x110^M
[ 3.955161] [<ffffffff81b1e1ae>] i9xx_crtc_disable+0x11e/0x4a0
[ 3.955163] [<ffffffff81b28034>] intel_crtc_update_dpms+0x94/0xe0
[ 3.955166] [<ffffffff81b31c38>] intel_modeset_setup_hw_state+0x9f8/0x1020
[ 3.955168] [<ffffffff81b743c0>] ? gen4_write64+0x80/0x80
[ 3.955170] [<ffffffff81b322c2>] intel_modeset_gem_init+0x62/0x80
[ 3.955173] [<ffffffff81ae4f90>] i915_driver_load+0x15e0/0x1760
[ 3.955176] [<ffffffff81cafafb>] ? device_add+0x31b/0xa20
[ 3.955180] [<ffffffff8197c8a4>] drm_dev_register+0xb4/0x260
[ 3.955182] [<ffffffff8197fb5e>] drm_get_pci_dev+0x15e/0x320
[ 3.955186] [<ffffffff810d369d>] ? trace_hardirqs_on+0x1d/0x30
[ 3.955188] [<ffffffff81adf36e>] i915_pci_probe+0x4e/0x80
[ 3.955191] [<ffffffff8175524d>] pci_device_probe+0xdd/0x190
[ 3.955194] [<ffffffff81cb5928>] driver_probe_device+0xc8/0x550
[ 3.955196] [<ffffffff81cb5eab>] __driver_attach+0xfb/0x110
[ 3.955198] [<ffffffff81cb5db0>] ? driver_probe_device+0x550/0x550
[ 3.955200] [<ffffffff81cb2bce>] bus_for_each_dev+0x9e/0xf0
[ 3.955202] [<ffffffff81cb5481>] driver_attach+0x21/0x30
[ 3.955204] [<ffffffff81cb3aef>] bus_add_driver+0x16f/0x340
[ 3.955207] [<ffffffff81cb68a7>] driver_register+0xa7/0x190
[ 3.955209] [<ffffffff81754e7f>] __pci_register_driver+0x6f/0x80
[ 3.955211] [<ffffffff8197fe79>] drm_pci_init+0x159/0x170
[ 3.955214] [<ffffffff8356b260>] ? radeon_init+0xfb/0xfb^M
[ 3.955217] [<ffffffff8356b305>] i915_init+0xa5/0xae
[ 3.955220] [<ffffffff8351a5c5>] do_one_initcall+0xe1/0x1b2
[ 3.955223] [<ffffffff8351a832>] kernel_init_freeable+0x19c/0x29d
[ 3.955225] [<ffffffff8351996d>] ? loglevel+0x46/0x46
[ 3.955228] [<ffffffff828d2c50>] ? rest_init+0x120/0x120
[ 3.955230] [<ffffffff828d2c61>] kernel_init+0x11/0x1a0
[ 3.955233] [<ffffffff82900a3c>] ret_from_fork+0x7c/0xb0
[ 3.955235] [<ffffffff828d2c50>] ? rest_init+0x120/0x120^M
[ 3.955256] ---[ end trace 708152452bf03fad ]---
Config attached.
-- Steve
[-- Attachment #2: config.gz --]
[-- Type: application/x-gzip, Size: 26732 bytes --]
next reply other threads:[~2014-02-14 22:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-14 22:41 Steven Rostedt [this message]
2014-03-03 20:52 ` Daniel Vetter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140214174101.7892a945@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®