Bug 97296 - WARNING: CPU: 3 PID: 233 at drivers/gpu/drm/i915/intel_display.c:690 chv_calc_dpll_params+0x97/0xb0 [i915]
Summary: WARNING: CPU: 3 PID: 233 at drivers/gpu/drm/i915/intel_display.c:690 chv_calc...
Status: CLOSED INVALID
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: high major
Assignee: Jonathan Woodward
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-08-11 11:25 UTC by Jonathan Woodward
Modified: 2017-07-07 18:29 UTC (History)
3 users (show)

See Also:
i915 platform: BSW/CHT
i915 features: display/DP


Attachments

Description Jonathan Woodward 2016-08-11 11:25:55 UTC
Description: WARNING: CPU: 3 PID: 233 at drivers/gpu/drm/i915/intel_display.c:690 chv_calc_dpll_params+0x97/0xb0 [i915]

Product: PiPo X9S
Processor: Intel(R) Atom(TM) x5-Z8300 CPU @ 1.44GHz

Linux: 4.6.4-1-ARCH #1 SMP PREEMPT Mon Jul 11 19:12:32 CEST 2016 x86_64 GNU/Linux

Intel i915 fault:

[ 3.172649] ------------[ cut here ]------------
[ 3.172773] WARNING: CPU: 3 PID: 233 at drivers/gpu/drm/i915/intel_display.c:690 chv_calc_dpll_params+0x97/0xb0 [i915]
[ 3.172778] WARN_ON(clock->n == 0 || clock->p == 0)
[ 3.172781] Modules linked in:
[ 3.172785] fdp_i2c pcspkr fdp kxcjk_1013 nci industrialio_triggered_buffer kfifo_buf nfc goodix snd_soc_rt5645 industrialio battery snd_soc_rt5640 snd_so
c_rl6231 nls_iso8859_1 nls_cp437 vfat fat i915(+) drm_kms_helper drm dm9601 cdc_ether usbnet mii intel_gtt syscopyarea sysfillrect sysimgblt fb_sys_fops mei_t
xe i2c_algo_bit lpc_ich mei processor_thermal_device intel_soc_dts_iosf thermal snd_intel_sst_acpi snd_intel_sst_core snd_soc_sst_mfld_platform snd_soc_sst_ma
tch hci_uart snd_soc_core btbcm btqca btintel snd_compress snd_pcm_dmaengine bluetooth ac97_bus video fjes snd_pcm intel_hid sparse_keymap rfkill_gpio snd_tim
er rfkill snd i2c_designware_platform soundcore i2c_designware_core tpm_crb 8250_dw int3403_thermal int3400_thermal int340x_thermal_zone acpi_thermal_rel spi_
pxa2xx_platform tpm_tis
[ 3.172870] tpm pinctrl_cherryview acpi_pad ac processor button sch_fq_codel ip_tables x_tables ext4 crc16 jbd2 mbcache mmc_block crc32c_intel xhci_pci xh
ci_hcd usbcore usb_common sdhci_acpi sdhci led_class mmc_core dm_mod
[ 3.172904] CPU: 3 PID: 233 Comm: systemd-udevd Tainted: G W 4.6.4-1-ARCH #1
[ 3.172908] Hardware name: Default string Default string/Cherry Trail CR, BIOS 5.11 04/22/2016
[ 3.172912] 0000000000000286 0000000007c25e5f ffff88007851f5d0 ffffffff812e54c2
[ 3.172919] ffff88007851f620 0000000000000000 ffff88007851f610 ffffffff8107a6bb
[ 3.172924] 000002b27851f5f0 ffff88017911e800 ffff88017a380000 0000000000000000
[ 3.172930] Call Trace:
[ 3.172946] [<ffffffff812e54c2>] dump_stack+0x63/0x81
[ 3.172953] [<ffffffff8107a6bb>] __warn+0xcb/0xf0
[ 3.172958] [<ffffffff8107a73f>] warn_slowpath_fmt+0x5f/0x80
[ 3.173037] [<ffffffffa0568627>] chv_calc_dpll_params+0x97/0xb0 [i915]
[ 3.173103] [<ffffffffa0568db7>] i9xx_get_pipe_config+0x587/0x660 [i915]
[ 3.173126] [<ffffffffa04350c9>] ? drm_mode_object_get_reg+0x69/0x80 [drm]
[ 3.173191] [<ffffffffa0575ff5>] intel_modeset_setup_hw_state+0xa5/0xf50 [i915]
[ 3.173204] [<ffffffffa0446e94>] ? drm_modeset_lock_all_ctx+0xa4/0xb0 [drm]
[ 3.173269] [<ffffffffa0578d7d>] intel_modeset_init+0xc0d/0x1cb0 [i915]
[ 3.173334] [<ffffffffa05a7646>] ? intel_i2c_reset+0x46/0x50 [i915]
[ 3.173398] [<ffffffffa05a78f4>] ? intel_setup_gmbus+0x234/0x310 [i915]
[ 3.173463] [<ffffffffa05b340b>] i915_driver_load+0xe2b/0x1760 [i915]
[ 3.173469] [<ffffffff810bce54>] ? __wake_up+0x44/0x50
[ 3.173477] [<ffffffff814eebc9>] ? netlink_broadcast_filtered+0x139/0x3c0
[ 3.173482] [<ffffffff812e8aa0>] ? kobj_ns_drop+0x50/0x50
[ 3.173487] [<ffffffff812e8da7>] ? kobject_uevent_env+0x167/0x4f0
[ 3.173493] [<ffffffff8140d377>] ? get_device+0x17/0x20
[ 3.173498] [<ffffffff814137e5>] ? klist_class_dev_get+0x15/0x20
[ 3.173505] [<ffffffff815b8d97>] ? klist_node_init+0x37/0x50
[ 3.173511] [<ffffffff8140efa2>] ? device_add+0x232/0x670
[ 3.173525] [<ffffffffa0430847>] drm_dev_register+0xa7/0xb0 [drm]
[ 3.173541] [<ffffffffa0432c02>] drm_get_pci_dev+0xd2/0x1e0 [drm]
[ 3.173598] [<ffffffffa04f0316>] i915_pci_probe+0x66/0x90 [i915]
[ 3.173605] [<ffffffff8132e245>] local_pci_probe+0x45/0xa0
[ 3.173610] [<ffffffff8132e190>] ? pci_match_device+0xe0/0x110
[ 3.173614] [<ffffffff8132f449>] pci_device_probe+0x109/0x160
[ 3.173620] [<ffffffff8141280c>] driver_probe_device+0x22c/0x440
[ 3.173625] [<ffffffff81412af1>] __driver_attach+0xd1/0xf0
[ 3.173630] [<ffffffff81412a20>] ? driver_probe_device+0x440/0x440
[ 3.173635] [<ffffffff8141029c>] bus_for_each_dev+0x6c/0xc0
[ 3.173640] [<ffffffff81411efe>] driver_attach+0x1e/0x20
[ 3.173645] [<ffffffff81411943>] bus_add_driver+0x1c3/0x280
[ 3.173650] [<ffffffff81413500>] driver_register+0x60/0xe0
[ 3.173654] [<ffffffff8132da2c>] __pci_register_driver+0x4c/0x50
[ 3.173669] [<ffffffffa0432df0>] drm_pci_init+0xe0/0x110 [drm]
[ 3.173673] [<ffffffffa0617000>] ? 0xffffffffa0617000
[ 3.173728] [<ffffffffa0617093>] i915_init+0x93/0x9a [i915]
[ 3.173735] [<ffffffff81002123>] do_one_initcall+0xb3/0x1f0
[ 3.173741] [<ffffffff8116dc47>] do_init_module+0x5f/0x1d8
[ 3.173748] [<ffffffff81103e26>] load_module+0x2186/0x29b0
[ 3.173753] [<ffffffff81100f20>] ? symbol_put_addr+0x50/0x50
[ 3.173759] [<ffffffff811047a3>] SyS_init_module+0x153/0x1a0
[ 3.173768] [<ffffffff815c7232>] entry_SYSCALL_64_fastpath+0x1a/0xa4
[ 3.173773] ---[ end trace 0bc11f839e8dfb26 ]---

# cat /sys/class/drm/card0/error
no error state collected
Comment 1 Jari Tahvanainen 2017-03-27 14:25:40 UTC
Hello Jonathan - I'm really sorry about this loooooong delay until getting back to you. Is this problem still valid for you with the latest kernel (preferable from drm-tip)? What kind of user scenario you are/were doing while getting this on dmesg? Did you see any symptoms on GUI when this happened? And please attach full dmesg as attachment while doing the update on this.
Comment 2 Manasi 2017-04-27 23:41:47 UTC
Hi Jonathan,

When you get a chance to test this on the latest kernel (https://cgit.freedesktop.org/drm-tip), please provide me the entire dmesg log with drm.debug set to 0xe. This will help me look at all the debugs prints and I would be glad to help you fixing this issue.

Manasi
Comment 3 Ricardo 2017-05-09 17:53:15 UTC
Assigning the bug to the submitter for further information
Comment 4 Ricardo 2017-07-07 18:28:58 UTC
Closing bug as invalid due to inactivity, please if the problem appears again with latest configuration please open a new bug


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.