I observe periodic kernel warning on a VTC1010 device, which has a BayTrail-I Intel SoC. It is not fatal, but quite annoying as it spams the logs. The kernel is stock 3.12. I can enable drm debugging and provide more data, if needed. Thanks! [ 8175.790554] [drm:intel_pipe_config_compare] *ERROR* mismatch in clock (expected 108000, found 0) [ 8175.790557] ------------[ cut here ]------------ [ 8175.790571] WARNING: CPU: 0 PID: 283 at drivers/gpu/drm/i915/intel_display.c:8806 check_crtc_state+0x8c1/0x906() [ 8175.790573] pipe state doesn't match! [ 8175.790652] Modules linked in: af_packet bnep iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_filter ip_tables cn iwlmvm mac80211 snd_hda_codec_realtek snd_hda_intel snd_hda_codec igb_avb(O) snd_hwdep snd_pcm igb ptp iwlwifi snd_page_alloc snd_timer snd pps_core hid_sensor_hub fan mfd_core thermal cfg80211 soundcore btusb dca bluetooth rfkill acpi_cpufreq rtc_cmos processor ipv6 autofs4 [ 8175.790661] CPU: 0 PID: 283 Comm: kworker/0:2 Tainted: G W O 3.12.0-2.1-x86-ivi #1 [ 8175.790665] Hardware name: NEXCOM VTC1010/Aptio CRB, BIOS 5.6.5 09/05/2013 [ 8175.790675] Workqueue: events console_callback [ 8175.790694] 00000000 00000000 f2641aac c13be3fb f2641aec f2641adc c102d45f c1559556 [ 8175.790713] f2641b08 0000011b c15584b7 00002266 c1266fd5 c1266fd5 f24e0000 f24ba000 [ 8175.790759] 00000000 f2641af4 c102d4a4 00000009 f2641aec c1559556 f2641b08 f2641d5c [ 8175.790763] Call Trace: [ 8175.790779] [<c13be3fb>] dump_stack+0x4b/0x79 [ 8175.790790] [<c102d45f>] warn_slowpath_common+0x79/0x90 [ 8175.790804] [<c1266fd5>] ? check_crtc_state+0x8c1/0x906 [ 8175.790816] [<c1266fd5>] ? check_crtc_state+0x8c1/0x906 [ 8175.790827] [<c102d4a4>] warn_slowpath_fmt+0x2e/0x30 [ 8175.790840] [<c1266fd5>] check_crtc_state+0x8c1/0x906 [ 8175.790871] [<c1270f01>] intel_modeset_check_state+0x388/0x62b [ 8175.790885] [<c12711e9>] intel_connector_dpms+0x45/0x48 [ 8175.790896] [<c122dcdf>] drm_fb_helper_dpms.isra.4+0x73/0xb2 [ 8175.790909] [<c122dd51>] drm_fb_helper_blank+0x33/0x3a [ 8175.790920] [<c11cc50a>] fb_blank+0x45/0x74 [ 8175.790931] [<c11d51df>] fbcon_blank+0x112/0x20f [ 8175.790944] [<c1051ae3>] ? update_cfs_rq_blocked_load+0x100/0x10b [ 8175.790958] [<c1035cc1>] ? internal_add_timer+0xe/0x26 [ 8175.790970] [<c13c25d2>] ? _raw_spin_unlock_irqrestore+0x1e/0x29 [ 8175.790981] [<c1036795>] ? __mod_timer+0xd0/0xdb [ 8175.790993] [<c1036819>] ? mod_timer+0x62/0x6f [ 8175.791005] [<c121a271>] do_unblank_screen+0xc7/0x12e [ 8175.791016] [<c13c25d2>] ? _raw_spin_unlock_irqrestore+0x1e/0x29 [ 8175.791027] [<c121a2e2>] unblank_screen+0xa/0xc [ 8175.791038] [<c121ab01>] poke_blanked_console+0x5a/0x9f [ 8175.791049] [<c121abad>] console_callback+0x67/0xda [ 8175.791062] [<c103f95b>] process_one_work+0x137/0x245 [ 8175.791073] [<c103df6b>] ? destroy_worker+0x76/0x7a [ 8175.791085] [<c103eddc>] ? manage_workers.isra.28+0x183/0x18d [ 8175.791098] [<c103fdb6>] worker_thread+0x127/0x1c4 [ 8175.791110] [<c103fc8f>] ? rescuer_thread+0x205/0x205 [ 8175.791121] [<c1043c12>] kthread+0x6e/0x73 [ 8175.791136] [<c13c33f7>] ret_from_kernel_thread+0x1b/0x28 [ 8175.791147] [<c1043ba4>] ? __kthread_parkme+0x54/0x54 [ 8175.791155] ---[ end trace fb9bcca9480b3c8f ]---
Does this happen with drm-intel-nightly? I'm hoping this one is fixed already (I know I've fixed it at least once!).
Yes, no warning in drm-intel-nightly. Any hint which patch I should cherry-pick to 3.12?
According to 67345: commit 662c6ecbcdca1fe8a5402f6c83d98d242917a043 Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Wed Sep 25 14:24:01 2013 -0700 commit acbec814a27f233b5ddb88a1bcaa2ac20daf64e0 Author: Jesse Barnes <jbarnes@virtuousgeek.org> Date: Fri Sep 20 11:29:32 2013 -0700 drm/i915/vlv: add VLV specific clock_get function v3 are two relevant ones, but you'll also want: commit f60711666bcab6df2c6c91d851e07ed54088453c Author: Jesse Barnes <jbarnes@virtuousgeek.org> Date: Tue Oct 1 10:41:38 2013 -0700 i915/vlv: untangle integrated clock source handling v4
OK, it looks like it is impossible to cherry-pick them due to too many conflicts. So it looks like 3.12.x releases are not going to have these fixed.
I see this happening in 'drm-intel-testing', commit commit 013133c43b2595ad72d1c66c7afa31dca82132d4 Author: Daniel Vetter <daniel.vetter@ffwll.ch> Date: Fri Nov 29 15:52:10 2013 +0100 drm-intel-nightly: 2013y-11m-29d-15h-52m-00s integration manifest [ 2.144406] [drm:check_encoder_state], [ENCODER:17:TMDS-17] [ 2.144409] [drm:check_crtc_state], [CRTC:3] [ 2.144420] [drm:i9xx_crtc_clock_get], Unknown DPLL mode 00000000 in programmed mode [ 2.144424] [drm:intel_pipe_config_compare] *ERROR* mismatch in clock (expected 108000, found 0) [ 2.144425] ------------[ cut here ]------------ [ 2.144434] WARNING: CPU: 0 PID: 1 at /mnt/bigssd/dedekind/work/tizen/git/kernel-x86-ivi/drivers/gpu/drm/i915/intel_display.c:8810 check_crtc_state+0x8f7/0x93c() [ 2.144435] pipe state doesn't match! [ 2.144437] Modules linked in: [ 2.144441] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.12.3-custom+ #50 [ 2.144443] Hardware name: Intel Corp. VALLEYVIEW B0 PLATFORM/NOTEBOOK, BIOS BYTICRB1.86C.0066.R41.1311081812 11/08/2013 [ 2.144451] 00000000 00000000 f446f61c c13c72c4 f446f65c f446f64c c102dbc1 c1568da5 [ 2.144457] f446f678 00000001 c1567d41 0000226a c126ce5c c126ce5c f4568000 00000000 [ 2.144463] f45d328c f446f664 c102dc54 00000009 f446f65c c1568da5 f446f678 f446f8e0 [ 2.144464] Call Trace: [ 2.144471] [<c13c72c4>] dump_stack+0x4b/0x72 [ 2.144477] [<c102dbc1>] warn_slowpath_common+0x79/0x90 [ 2.144482] [<c126ce5c>] ? check_crtc_state+0x8f7/0x93c [ 2.144486] [<c126ce5c>] ? check_crtc_state+0x8f7/0x93c [ 2.144490] [<c102dc54>] warn_slowpath_fmt+0x2e/0x30 [ 2.144494] [<c126ce5c>] check_crtc_state+0x8f7/0x93c [ 2.144505] [<c1277183>] intel_modeset_check_state+0x390/0x66c [ 2.144510] [<c127748a>] intel_set_mode+0x2b/0x33 [ 2.144514] [<c1277a7f>] intel_crtc_set_config+0x5ed/0x7da [ 2.144521] [<c1242415>] drm_mode_set_config_internal+0x39/0x90 [ 2.144526] [<c12346ee>] drm_fb_helper_set_par+0x51/0x8f [ 2.144532] [<c11da3d3>] fbcon_init+0x2d1/0x3b9 [ 2.144538] [<c121dd8f>] visual_init+0x9a/0xed [ 2.144542] [<c121f44e>] do_bind_con_driver+0x142/0x248 [ 2.144548] [<c11274d8>] ? sysfs_create_file+0x1a/0x24 [ 2.144552] [<c12a1e86>] ? device_create_file+0x34/0x89 [ 2.144556] [<c121f680>] do_take_over_console+0x12c/0x153 [ 2.144561] [<c11d6f99>] do_fbcon_takeover+0x4f/0x8f [ 2.144566] [<c11dab20>] fbcon_event_notify+0x371/0x651 [ 2.144570] [<c1127449>] ? sysfs_add_file_mode+0x6a/0x86 [ 2.144575] [<c1048940>] notifier_call_chain+0x25/0x46 [ 2.144580] [<c1048a54>] __blocking_notifier_call_chain+0x39/0x4f [ 2.144585] [<c1048a84>] blocking_notifier_call_chain+0x1a/0x1c [ 2.144589] [<c11d0e89>] fb_notifier_call_chain+0x11/0x13 [ 2.144593] [<c11d24c7>] register_framebuffer+0x1f9/0x259 [ 2.144598] [<c1234552>] drm_fb_helper_initial_config+0x33f/0x3e5 [ 2.144601] [<c1233c03>] ? drm_fb_helper_init+0xb1/0x118 [ 2.144606] [<c12338f1>] ? kzalloc.constprop.11+0xd/0xf [ 2.144611] [<c13cb4ba>] ? _raw_spin_unlock_irqrestore+0x17/0x22 [ 2.144616] [<c129c043>] ? spin_unlock_irqrestore+0x8/0xa [ 2.144620] [<c129cd3c>] ? i915_write32+0xb9/0xc1 [ 2.144625] [<c1293709>] intel_fbdev_initial_config+0x19/0x1b [ 2.144630] [<c124e723>] i915_driver_load+0xafe/0xce1 [ 2.144634] [<c124c916>] ? intel_teardown_mchbar+0x9f/0x9f [ 2.144640] [<c1342e7f>] ? pcibios_allocate_bus_resources+0x98/0x98 [ 2.144646] [<c123f1a9>] drm_get_pci_dev+0x177/0x284 [ 2.144651] [<c11c54bf>] ? pci_match_id+0x18/0x38 [ 2.144655] [<c124bcab>] i915_pci_probe+0x4c/0x56 [ 2.144659] [<c11c5d82>] pci_device_probe+0x56/0x8e [ 2.144664] [<c12a4c3f>] driver_probe_device+0x8f/0x195 [ 2.144668] [<c12a4d8c>] __driver_attach+0x47/0x63 [ 2.144672] [<c12a377b>] bus_for_each_dev+0x3c/0x66 [ 2.144676] [<c12a47fa>] driver_attach+0x17/0x19 [ 2.144680] [<c12a4d45>] ? driver_probe_device+0x195/0x195 [ 2.144684] [<c12a44f7>] bus_add_driver+0xc7/0x20c [ 2.144688] [<c12a5277>] driver_register+0x79/0xaa [ 2.144692] [<c11c5449>] __pci_register_driver+0x2e/0x31 [ 2.144698] [<c1658e52>] ? ftrace_define_fields_drm_vblank_event+0x71/0x71 [ 2.144701] [<c123f329>] drm_pci_init+0x73/0xcf [ 2.144706] [<c1658e52>] ? ftrace_define_fields_drm_vblank_event+0x71/0x71 [ 2.144710] [<c1658eb0>] i915_init+0x5e/0x60 [ 2.144714] [<c10003db>] do_one_initcall+0x8a/0x11b [ 2.144720] [<c1628400>] ? do_early_param+0x3b/0x7a [ 2.144724] [<c162843f>] ? do_early_param+0x7a/0x7a [ 2.144729] [<c104355f>] ? parse_args+0x166/0x225 [ 2.144733] [<c13cb4ba>] ? _raw_spin_unlock_irqrestore+0x17/0x22 [ 2.144738] [<c1628af3>] kernel_init_freeable+0x119/0x1bd [ 2.144743] [<c162843f>] ? do_early_param+0x7a/0x7a [ 2.144748] [<c13c193b>] kernel_init+0xb/0xc3 [ 2.144752] [<c13cc177>] ret_from_kernel_thread+0x1b/0x28 [ 2.144755] [<c13c1930>] ? rest_init+0x70/0x70 [ 2.144768] ---[ end trace 0897b95cdc50c52b ]--- [ 2.144772] [drm:intel_dump_pipe_config], [CRTC:3][hw state] config for pipe A [ 2.144774] [drm:intel_dump_pipe_config], cpu_transcoder: A [ 2.144776] [drm:intel_dump_pipe_config], pipe bpp: 24, dithering: 0 [ 2.144780] [drm:intel_dump_pipe_config], fdi/pch: 0, lanes: 0, gmch_m: 0, gmch_n: 0, link_m: 0, link_n: 0, tu: 0
My apologies, this was a mistake, I actually looked at wrong kernel.
Apologies for bugging with this, but this is a regression - 3.11 did not see this scary warning, while 3.12 does see it. And I've tried to back-port those 3 patches to 3.12 - does not help. There were many conflicts, and I could make a resolution mistake. Let me re-open this, thanks!
Created attachment 90560 [details] The patches Jesse specified back-ported to 3.12 which did not help
(In reply to comment #8) > Created attachment 90560 [details] > The patches Jesse specified back-ported to 3.12 which did not help Thos aren't quite right. Please try these: git://gitorious.org/vsyrjala/linux.git vlv_get_clock_backport
Many thanks Ville, confirmed, those indeed fix the issue. Closing the bug then.
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.