56282 – [snb dp] WARNING: at drivers/gpu/drm/i915/intel_dp.c:2081 -- disabling a disabled output

Bug 56282 - [snb dp] WARNING: at drivers/gpu/drm/i915/intel_dp.c:2081 -- disabling a disabled output

Summary: [snb dp] WARNING: at drivers/gpu/drm/i915/intel_dp.c:2081 -- disabling a dis...

Status:	CLOSED WORKSFORME

Alias:	None

Product:	DRI
Classification:	Unclassified
Component:	DRM/Intel (show other bugs)
Version:	unspecified
Hardware:	Other All

Importance:	medium normal
Assignee:	Daniel Vetter
QA Contact:	Intel GFX Bugs mailing list

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2012-10-22 14:43 UTC by Chris Wilson
Modified:	2017-07-24 22:59 UTC (History)
CC List:	5 users (show)

See Also:
i915 platform:
i915 features:

Attachments

Description Chris Wilson 2012-10-22 14:43:15 UTC

intel_dp.c:2081 -- intel_dp_link_down():

        if (WARN_ON((I915_READ(intel_dp->output_reg) & DP_PORT_EN) == 0))
                return;

[  114.080576] WARNING: at drivers/gpu/drm/i915/intel_dp.c:2081 intel_dp_link_down+0x19d/0x1b0()
[  114.080581] Hardware name: HP ProBook 6360b
[  114.080584] Modules linked in: fuse bnep bluetooth arc4 iwldvm snd_hda_codec_hdmi mac80211 snd_hda_codec_idt snd_hda_intel snd_hda_codec snd_hwdep iwlwifi snd_seq snd_seq_device snd_pcm iTCO_wdt coretemp cfg80211 snd_page_alloc crc32c_intel iTCO_vendor_support lpc_ich hp_accel e1000e mei snd_timer snd hp_wmi sparse_keymap rfkill wmi mfd_core lis3lv02d microcode serio_raw input_polldev soundcore uinput sdhci_pci sdhci mmc_core
[  114.080671] Pid: 540, comm: Xorg Not tainted 3.7.0-rc2+ #5
[  114.080675] Call Trace:
[  114.080691]  [<c1037a82>] warn_slowpath_common+0x72/0xa0
[  114.080701]  [<c1364aed>] ? intel_dp_link_down+0x19d/0x1b0
[  114.080710]  [<c1364aed>] ? intel_dp_link_down+0x19d/0x1b0
[  114.080720]  [<c1037ad2>] warn_slowpath_null+0x22/0x30
[  114.080729]  [<c1364aed>] intel_dp_link_down+0x19d/0x1b0
[  114.080738]  [<c1366cd7>] ? intel_dp_sink_dpms+0x47/0xa0
[  114.080748]  [<c1366d70>] intel_disable_dp+0x40/0x170
[  114.080760]  [<c10ebddd>] ? generic_file_buffered_write+0x17d/0x220
[  114.080773]  [<c13569d0>] ironlake_crtc_disable+0x650/0x860
[  114.080785]  [<c135a8de>] intel_crtc_update_dpms+0x5e/0x90
[  114.080795]  [<c135a9a8>] intel_encoder_dpms+0x18/0x30
[  114.080804]  [<c135be95>] intel_connector_dpms+0x35/0x60
[  114.080815]  [<c132a0cd>] drm_mode_obj_set_property_ioctl+0x36d/0x390
[  114.080830]  [<c1561cd8>] ? mutex_lock+0x18/0x40
[  114.080841]  [<c132a127>] drm_mode_connector_property_set_ioctl+0x37/0x50
[  114.080851]  [<c132a0f0>] ? drm_mode_obj_set_property_ioctl+0x390/0x390
[  114.080861]  [<c131a93a>] drm_ioctl+0x3ea/0x460
[  114.080871]  [<c132a0f0>] ? drm_mode_obj_set_property_ioctl+0x390/0x390
[  114.080884]  [<c116f360>] ? fsnotify_put_event+0x50/0x90
[  114.080892]  [<c116f360>] ? fsnotify_put_event+0x50/0x90
[  114.080901]  [<c116f360>] ? fsnotify_put_event+0x50/0x90
[  114.080910]  [<c131a550>] ? drm_copy_field+0x80/0x80
[  114.080923]  [<c114713a>] do_vfs_ioctl+0x7a/0x590
[  114.080936]  [<c120ec6a>] ? inode_has_perm.isra.30.constprop.61+0x3a/0x50
[  114.080947]  [<c1210030>] ? file_has_perm+0xa0/0xb0
[  114.080958]  [<c1138238>] ? vfs_write+0xe8/0x160
[  114.080967]  [<c1210448>] ? selinux_file_ioctl+0x48/0xe0
[  114.080977]  [<c11476bb>] sys_ioctl+0x6b/0x80
[  114.080987]  [<c156ab7a>] sysenter_do_call+0x12/0x22
[  114.080999]  [<c1560000>] ? i915_gem_object_pin_pages.isra.7.part.8+0x2/0x5

Comment 1 Chris Wilson 2012-10-22 14:50:10 UTC

Hmm, not easy to reproduce. But I did get a

[  114.710837] [drm:intel_disable_transcoder] *ERROR* failed to disable transcoder 1

instead.

Comment 2 Jesse Barnes 2012-12-12 18:41:49 UTC

Daniel just changed the order of PCH vs CPU disable, maybe that fixes this?

Comment 3 Chris Wilson 2013-01-07 17:40:29 UTC

I was playing around with the suspect device yesterday, and whilst I haven't seen this warning again, the DP output on that machine does occassionally go haywire (bad signal to monitor and it loses sync).

Comment 4 Ben Widawsky 2013-04-17 18:34:02 UTC

Still present?

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.