Bug 64570 - [HSW Regression]I-G-T testdisplay causes call trace
Summary: [HSW Regression]I-G-T testdisplay causes call trace
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: All Linux (All)
: high major
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-05-14 06:05 UTC by lu hua
Modified: 2017-01-12 07:03 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:

Attachments
dmesg (78.39 KB, text/plain)
2013-05-14 06:05 UTC, lu hua 		no flags Details
View All

Description lu hua 2013-05-14 06:05:19 UTC 
Created attachment 79282 [details]
dmesg

Environment:
--------------------------
Kernel: (drm-intel-next-queued) 0a790cdbfc526890af7dc41515a563f09e427129
Author: Paulo Zanoni <paulo.r.zanoni@intel.com>
Date:   Wed Apr 17 18:15:49 2013 -0300

    drm/i915: implement WADPOClockGatingDisable for LPT

    This should prevent mode set failures on LPT.

Description:
--------------------------
run ./testdisplay causes Call trace. It happens on rm-intel-next-queued kernel, works well on drm-intel-fixes kernel.

The latest known bad commit: 0a790cdbfc526890af7dc41515a563f09e427129
The latest known good commit:a1520318a51d6c21b1d9229a9c35b4fcb890b175

Following cases also cause call trace:
igt/gem_flink/bad-flink
igt/kms_flip/absolute-wf_vblank
igt/kms_flip/delayed-wf_vblank-vs-modeset
igt/kms_flip/flip-vs-blocking-wf-vblank
igt/kms_flip/flip-vs-expired-vblank
igt/kms_flip/flip-vs-modeset
igt/kms_flip/flip-vs-panning
igt/kms_flip/plain-flip-ts-check
igt/kms_flip/wf_vblank

output:
CRTS(3):[0]  1920x1080 60 1920 2008 2052 2200 1080 1084 1089 1125 0x5 0x48 148500
CRTS(3):[1]  1920x1080 50 1920 2448 2492 2640 1080 1084 1089 1125 0x5 0x40 148500
CRTS(3):[2]  1600x1200 60 1600 1664 1856 2160 1200 1201 1204 1250 0x5 0x40 162000
CRTS(3):[3]  1680x1050 60 1680 1728 1760 1840 1050 1053 1059 1080 0x9 0x40 119000
CRTS(3):[4]  1280x1024 60 1280 1328 1440 1688 1024 1025 1028 1066 0x5 0x40 108000
CRTS(3):[5]  1440x900 60 1440 1488 1520 1600 900 903 909 926 0x9 0x40 88750
CRTS(3):[6]  1280x960 60 1280 1376 1488 1800 960 961 964 1000 0x5 0x40 108000
CRTS(3):[7]  1280x720 50 1280 1720 1760 1980 720 725 730 750 0x5 0x40 74250
CRTS(3):[8]  1280x720 60 1280 1390 1430 1650 720 725 730 750 0x5 0x40 74250
CRTS(3):[9]  1024x768 60 1024 1048 1184 1344 768 771 777 806 0xa 0x40 65000
CRTS(3):[10]  800x600 60 800 840 968 1056 600 601 605 628 0x5 0x40 40000
CRTS(3):[11]  720x576 50 720 732 796 864 576 581 586 625 0xa 0x40 27000
CRTS(3):[12]  720x480 60 720 736 798 858 480 489 495 525 0xa 0x40 27000
CRTS(3):[13]  640x480 60 640 656 752 800 480 490 492 525 0xa 0x40 25200
CRTS(3):[14]  640x480 60 640 656 752 800 480 490 492 525 0xa 0x40 25175
CRTS(3):[15]  720x400 70 720 738 846 900 400 412 414 449 0x6 0x40 28320


Calltrace:
[16065.787350] WARNING: at drivers/gpu/drm/i915/intel_display.c:8142 intel_modeset_check_state+0x83f/0x856 [i915]()
[16065.787351] Hardware name: Shark Bay Client platform
[16065.787352] pipe state doesn't match!
[16065.787353] Modules linked in: bnep bluetooth rfkill ipv6 dm_mod iTCO_wdt iTCO_vendor_support snd_hda_codec_realtek acpi_cpufreq coretemp kvm_intel kvm microcode pcspkr i2c_i801 snd_hda_codec_hdmi lpc_ich mfd_core snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_page_alloc snd_timer snd soundcore battery ac i915 video button drm_kms_helper drm mperf freq_table
[16065.787366] Pid: 31085, comm: testdisplay Tainted: G        W    3.9.0-rc6_nightlytop_fa643c_20130513_+ #2199
[16065.787367] Call Trace:
[16065.787373]  [<ffffffffa0088900>] ? intel_modeset_check_state+0x7cb/0x856 [i915]
[16065.787377]  [<ffffffff8102b610>] ? warn_slowpath_common+0x76/0x8c
[16065.787379]  [<ffffffff8102b6be>] ? warn_slowpath_fmt+0x45/0x4a
[16065.787385]  [<ffffffffa007ef7b>] ? haswell_get_pipe_config+0xbc/0xc7 [i915]
[16065.787390]  [<ffffffffa0088974>] ? intel_modeset_check_state+0x83f/0x856 [i915]
[16065.787396]  [<ffffffffa00889fb>] ? intel_set_mode+0x1d/0x27 [i915]
[16065.787401]  [<ffffffffa0088fc4>] ? intel_crtc_set_config+0x5bf/0x777 [i915]
[16065.787407]  [<ffffffffa0012a2b>] ? drm_mode_set_config_internal+0x19/0x40 [drm]
[16065.787409]  [<ffffffffa0049b85>] ? drm_fb_helper_restore_fbdev_mode+0x2d/0x48 [drm_kms_helper]
[16065.787414]  [<ffffffffa00a2bc5>] ? intel_fb_restore_mode+0x29/0x94 [i915]
[16065.787418]  [<ffffffffa000967a>] ? drm_lastclose+0x40/0x22a [drm]
[16065.787421]  [<ffffffffa0009f58>] ? drm_release+0x4fb/0x52c [drm]
[16065.787425]  [<ffffffff810cca44>] ? __fput+0xe5/0x1d6
[16065.787427]  [<ffffffff8104004a>] ? task_work_run+0x73/0x89
[16065.787429]  [<ffffffff8102f70c>] ? do_exit+0x3a4/0x8cd
[16065.787431]  [<ffffffff810492e2>] ? __cond_resched+0x1d/0x26
[16065.787434]  [<ffffffff816cd980>] ? _cond_resched+0x27/0x2f
[16065.787436]  [<ffffffff8102fd8a>] ? do_group_exit+0x66/0x98
[16065.787437]  [<ffffffff8102fdcb>] ? sys_exit_group+0xf/0xf
[16065.787439]  [<ffffffff816d3a52>] ? system_call_fastpath+0x16/0x1b
[16065.787441] ---[ end trace 134322919ae2cf62 ]---

Reproduce steps:
----------------
1. ./testdisplay
Comment 1 Paulo Zanoni 2013-05-14 14:52:18 UTC 
The bad commit was removed last Friday. Current trees should not have this error message. Can you please confirm?
Comment 2 lu hua 2013-05-15 05:51:58 UTC 
Fixed on commit 328d8e829b9a05814af4722c1091d62c5533c4f8.
Comment 3 lu hua 2013-05-15 05:52:14 UTC 
Verified.Fixed.
Comment 4 Jari Tahvanainen 2017-01-12 07:03:58 UTC 
Closing verified+fixed.

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.