Bug 86228 - [PNV]igt/kms_flip causes *ERROR* mismatch in adjusted_mode.crtc_clock (expected 65000, found -3840)
Summary: [PNV]igt/kms_flip causes *ERROR* mismatch in adjusted_mode.crtc_clock (expect...
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: All Linux (All)
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-11-13 03:31 UTC by lu hua
Modified: 2017-08-14 08:32 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
dmesg (55.28 KB, text/plain)
2014-11-13 03:31 UTC, lu hua
no flags Details

Description lu hua 2014-11-13 03:31:45 UTC
Created attachment 109375 [details]
dmesg

==System Environment==
--------------------------
Regression: not sure

Non-working platforms:  PNV

==kernel==
--------------------------
drm-intel-nightly/de6d6ca380bba4f962f942089b0a212d9b3977c1

==Bug detailed description==
kms_flip causes *ERROR* mismatch in adjusted_mode.crtc_clock (expected 65000, found -3840) with -nightly kernel. -queued kernel boot fail(bug 85835), So I don't test -queued kernel. 
Test -nightly kernel commit 2ea23cd593ba60ead60e2f796fae675aa4475b1a and -queued kernel commit fff95501f2095fa8a9dbd7e177bbf642d241b2fe, they work well.

run  ./kms_flip --run-subtest absolute-wf_vblank
output:
IGT-Version: 1.8-g50d539e (i686) (Linux: 3.18.0-rc3_drm-intel-nightly_de6d6c_20141111+ i686)
Using monotonic timestamps
Beginning absolute-wf_vblank on crtc 10, connector 11
  1024x600 60 1024 1072 1104 1200 600 603 609 625 0xa 0x48 45000
.............................................................................................................................
absolute-wf_vblank on crtc 10, connector 11: PASSED

Beginning absolute-wf_vblank on crtc 7, connector 17
  1024x768 60 1024 1048 1184 1344 768 771 777 806 0xa 0x40 65000
............................................................................................................................
absolute-wf_vblank on crtc 7, connector 17: PASSED

Beginning absolute-wf_vblank on crtc 10, connector 17
  1024x768 60 1024 1048 1184 1344 768 771 777 806 0xa 0x40 65000
.........................................................................................................................
absolute-wf_vblank on crtc 10, connector 17: PASSED

Subtest absolute-wf_vblank: SUCCESS (30.877s)


[  164.687447] [drm:check_crtc_state [i915]] *ERROR* mismatch in adjusted_mode.crtc_clock (expected 65000, found -3840)
[  164.687458] ------------[ cut here ]------------
[  164.687520] WARNING: CPU: 1 PID: 3606 at drivers/gpu/drm/i915/intel_display.c:10625 check_crtc_state+0xa07/0xa35 [i915]()
[  164.687527] pipe state doesn't match!
[  164.687532] Modules linked in: dm_mod iTCO_wdt iTCO_vendor_support msi_laptop sparse_keymap rfkill pcspkr i2c_i801 snd_hda_codec_realtek lpc_ich mfd_core snd_hda_codec_generi
c snd_hda_intel snd_hda_controller snd_hda_codec r8169 snd_hwdep snd_pcm snd_timer snd soundcore wmi ac battery acpi_cpufreq joydev i915 button video drm_kms_helper drm cfbfillr
ect cfbimgblt cfbcopyarea
[  164.687608] CPU: 1 PID: 3606 Comm: kms_flip Tainted: G        W      3.18.0-rc3_drm-intel-nightly_de6d6c_20141111+ #1386
[  164.687615] Hardware name: MICRO-STAR INTERNATIONAL CO., LTD MS-N014/MS-N014, BIOS EN014IMS.10B 11/30/2009
[  164.687622]  00000000 c16fd68c c002bac0 c102dbcc f8359f9f f5886000 0000fde8 fffff100
[  164.687639]  f5886670 c102dc47 00000009 c002bac0 f83a8524 c002bad8 f8359f9f f83a6c2b
[  164.687656]  00002981 f83a8524 00000000 f58e93c4 c12dd66c c002bafc 03000000 f5a70800
[  164.687674] Call Trace:
[  164.687694]  [<c16fd68c>] ? dump_stack+0x3e/0x4e
[  164.687708]  [<c102dbcc>] ? warn_slowpath_common+0x65/0x78
[  164.687776]  [<f8359f9f>] ? check_crtc_state+0xa07/0xa35 [i915]
[  164.687789]  [<c102dc47>] ? warn_slowpath_fmt+0x29/0x2d
[  164.687858]  [<f8359f9f>] ? check_crtc_state+0xa07/0xa35 [i915]
[  164.687874]  [<c12dd66c>] ? number.isra.2+0x155/0x249
[  164.687945]  [<f8364dae>] ? intel_modeset_check_state+0x401/0x6d3 [i915]
[  164.687960]  [<c16fac60>] ? printk+0x16/0x1a
[  164.688023]  [<f83650a0>] ? intel_set_mode+0x20/0x25 [i915]
[  164.688134]  [<f8365b48>] ? intel_crtc_set_config+0x67c/0x976 [i915]
[  164.688157]  [<c16fac60>] ? printk+0x16/0x1a
[  164.688199]  [<f804c2e1>] ? drm_mode_set_config_internal+0x39/0x97 [drm]
[  164.688238]  [<f804f578>] ? drm_mode_setcrtc+0x373/0x405 [drm]
[  164.688278]  [<f804f205>] ? drm_mode_setplane+0x188/0x188 [drm]
[  164.688314]  [<f8045c7c>] ? drm_ioctl+0x233/0x35c [drm]
[  164.688351]  [<f804f205>] ? drm_mode_setplane+0x188/0x188 [drm]
[  164.688373]  [<c104e216>] ? pick_next_task_fair+0xd1/0x3ee
[  164.688385]  [<c1088d0b>] ? __audit_syscall_exit+0x1cd/0x1e3
[  164.688410]  [<f8045a49>] ? drm_copy_field+0x47/0x47 [drm]
[  164.688423]  [<c10ee7ed>] ? do_vfs_ioctl+0x3fa/0x444
[  164.688436]  [<c16ffc8a>] ? __schedule+0x56a/0x6d5
[  164.688449]  [<c10e21e0>] ? vfs_write+0x106/0x165
[  164.688461]  [<c10ee879>] ? SyS_ioctl+0x42/0x6d
[  164.688473]  [<c1088b20>] ? __audit_syscall_entry+0x9f/0xbd
[  164.688486]  [<c1702208>] ? sysenter_do_call+0x12/0x12
[  164.688495] ---[ end trace c7161e1fd715f86a ]---


==Reproduce steps==
---------------------------- 
1. ./kms_flip --run-subtest absolute-wf_vblank
Comment 1 lu hua 2014-11-13 06:56:49 UTC
gem_evict_everything_forked-mempressure-normal also has this error.
Comment 2 lu hua 2014-11-13 07:14:00 UTC
kms_setmode_invalid-clone-exclusive-crtc also has this error.
Comment 3 lu hua 2014-11-13 07:16:21 UTC
 ./testdisplay also has this error.
Comment 4 Jesse Barnes 2014-11-13 19:09:31 UTC
commit ceb7ee9ff7b5245d46e716eeb33d769846395dae
Author: Bob Paauwe <bob.j.paauwe@intel.com>
Date:   Tue Nov 11 09:29:18 2014 -0800

    drm/i915: Use correct pipe config to update pll dividers. V2
Comment 5 lu hua 2014-11-14 06:59:44 UTC
Verified.Fixed.
Comment 6 Jari Tahvanainen 2017-08-14 08:32:25 UTC
Moving old bug from Verified to Closed.


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.