From: Hans de Bruin <jmdebruin@xmsnet.nl>
To: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: 4.2.0+ warning in dmesg drm_atomic.c:491 drm_atomic_check_only+0x19e/0x401()
Date: Sun, 6 Sep 2015 15:37:42 +0200 [thread overview]
Message-ID: <55EC41A6.90909@xmsnet.nl> (raw)
Hi
Since this morning this warning is in my kernel log:
[ 10.588770] ------------[ cut here ]------------
[ 10.593120] WARNING: CPU: 0 PID: 1477 at
/usr/src/linux.git/drivers/gpu/drm/drm_atomic.c:491
drm_atomic_check_only+0x19e/0x401()
[ 10.597589] Modules linked in:
[ 10.601962] CPU: 0 PID: 1477 Comm: kworker/0:5 Tainted: G W
4.2.0+ #822
[ 10.606363] Hardware name: Dell Inc. Latitude D430
/0XW455, BIOS A02 10/11/2007
[ 10.610827] Workqueue: events output_poll_execute
[ 10.615241] 000002ba 00000000 f5941c70 c14eeecb f5941c88 c105b158
c12740a2 f5ab0000
[ 10.619761] f62c0000 c17092f8 f5941c98 c105b1d3 00000009 00000000
f5941cb8 c12740a2
[ 10.624296] 00000001 f6222000 00000002 f5ab0000 f6222000 f6222000
f5941cc8 c1274313
[ 10.628817] Call Trace:
[ 10.633175] [<c14eeecb>] dump_stack+0x16/0x18
[ 10.637525] [<c105b158>] warn_slowpath_common+0x72/0x89
[ 10.641866] [<c12740a2>] ? drm_atomic_check_only+0x19e/0x401
[ 10.646134] [<c105b1d3>] warn_slowpath_null+0xf/0x13
[ 10.650324] [<c12740a2>] drm_atomic_check_only+0x19e/0x401
[ 10.654473] [<c1274313>] drm_atomic_commit+0xe/0x44
[ 10.658668] [<c12c81cf>] intel_get_load_detect_pipe+0x40e/0x48b
[ 10.662791] [<c12f0d1a>] intel_tv_detect+0x10b/0x43a
[ 10.666900] [<c12558f3>]
drm_helper_probe_single_connector_modes_merge_bits+0xaf/0x34a
[ 10.671061] [<c1255b98>] drm_helper_probe_single_connector_modes+0xa/0xc
[ 10.675163] [<c125bf73>] drm_fb_helper_probe_connector_modes+0x3b/0x49
[ 10.679269] [<c125d744>] drm_fb_helper_hotplug_event+0x61/0x94
[ 10.683298] [<c12d49df>] intel_fbdev_output_poll_changed+0x15/0x17
[ 10.687373] [<c125562c>] drm_kms_helper_hotplug_event+0x1c/0x1f
[ 10.691502] [<c1255759>] output_poll_execute+0x108/0x145
[ 10.695629] [<c106801a>] process_one_work+0x152/0x248
[ 10.699777] [<c1068796>] worker_thread+0x236/0x327
[ 10.703872] [<c1068560>] ? cancel_delayed_work_sync+0xf/0xf
[ 10.707982] [<c106b8b6>] kthread+0xa3/0xa8
[ 10.712016] [<c14f3380>] ret_from_kernel_thread+0x20/0x30
[ 10.716035] [<c106b813>] ? kthread_worker_fn+0x100/0x100
[ 10.720696] ---[ end trace b2652b27bfce9d22 ]---
--
Hans
In case I need to bisect: good..bad : 51e771c..6c0f568
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
reply other threads:[~2015-09-06 13:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=55EC41A6.90909@xmsnet.nl \
--to=jmdebruin@xmsnet.nl \
--cc=intel-gfx@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.