Bug 81101 - [byt] drm:vlv_force_gfx_clock *ERROR* timeout waiting for GFX clock force-off (00000008)
Summary: [byt] drm:vlv_force_gfx_clock *ERROR* timeout waiting for GFX clock force-off...
Status: CLOSED DUPLICATE of bug 75244
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: Other All
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-07-09 12:22 UTC by Chris Wilson
Modified: 2017-07-24 22:53 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
dmesg (79.67 KB, text/plain)
2014-07-09 12:22 UTC, Chris Wilson
no flags Details

Description Chris Wilson 2014-07-09 12:22:09 UTC
Created attachment 102483 [details]
dmesg

[  449.303068] ------------[ cut here ]------------
[  449.303082] WARNING: CPU: 2 PID: 1380 at drivers/gpu/drm/i915/i915_drv.c:1189 vlv_force_gfx_clock+0x244/0x250()
[  449.303085] Modules linked in: ctr(E) ccm(E) arc4(E) iTCO_wdt(E) asus_nb_wmi(E) hid_multitouch(E) iTCO_vendor_support(E) asus_wmi(E) sparse_keymap(E) intel_powerclamp(E) coretemp(E) kvm_intel(E) kvm(E) crc32_pclmul(E) ghash_clmulni_intel(E) aesni_intel(E) aes_x86_64(E) lrw(E) gf128mul(E) glue_helper(E) ablk_helper(E) cryptd(E) rt2800usb(E) rt2x00usb(E) rt2800lib(E) rt2x00lib(E) microcode(E) mac80211(E) crc_ccitt(E) joydev(E) brcmfmac(E) brcmutil(E) cfg80211(E) pcspkr(E) wmi(E) ak8975(E) mac_hid(E) industrialio(E) dw_dmac(E) dw_dmac_core(E) acpi_pad(E) iosf_mbi(E) lpc_ich(E) spi_pxa2xx_platform(E) i2c_designware_platform(E) 8250_dw(E) i2c_designware_core(E) autofs4(E) ext2(E) usbkbd(E) hid_generic(E) usb_storage(E) usbhid(E) mmc_block(E) i2c_hid(E) hid(E) sdhci_acpi(E) sdhci(E)
[  449.303156] CPU: 2 PID: 1380 Comm: kworker/u8:1 Tainted: G        W   E 3.16.0-rc4+ #297
[  449.303159] Hardware name: ASUSTeK COMPUTER INC. T100TA/T100TA, BIOS T100TA.304 03/14/2014
[  449.303166] Workqueue: i915 i915_gem_idle_work_handler
[  449.303169]  0000000000000009 ffff88007201fd20 ffffffff817e8f2b 0000000000000000
[  449.303174]  ffff88007201fd58 ffffffff81067ffd ffff880036c20000 0000000000000000
[  449.303179]  0000000100009172 ffff880036c20000 0000000000000100 ffff88007201fd68
[  449.303184] Call Trace:
[  449.303194]  [<ffffffff817e8f2b>] dump_stack+0x45/0x56
[  449.303201]  [<ffffffff81067ffd>] warn_slowpath_common+0x7d/0xa0
[  449.303206]  [<ffffffff810680da>] warn_slowpath_null+0x1a/0x20
[  449.303211]  [<ffffffff814be774>] vlv_force_gfx_clock+0x244/0x250
[  449.303217]  [<ffffffff814c9120>] gen6_rps_idle+0x170/0x1f0
[  449.303223]  [<ffffffff81516b65>] intel_mark_idle+0x1a5/0x200
[  449.303229]  [<ffffffff810978c8>] ? finish_task_switch+0x128/0x180
[  449.303234]  [<ffffffff814df625>] i915_gem_idle_work_handler+0x15/0x20
[  449.303240]  [<ffffffff81083a62>] process_one_work+0x182/0x450
[  449.303245]  [<ffffffff810841d3>] worker_thread+0x123/0x5a0
[  449.303251]  [<ffffffff810840b0>] ? rescuer_thread+0x380/0x380
[  449.303256]  [<ffffffff8108add9>] kthread+0xc9/0xe0
[  449.303261]  [<ffffffff8108ad10>] ? kthread_create_on_node+0x180/0x180
[  449.303267]  [<ffffffff817f267c>] ret_from_fork+0x7c/0xb0
[  449.303272]  [<ffffffff8108ad10>] ? kthread_create_on_node+0x180/0x180
[  449.303275] ---[ end trace f24328456c1916e6 ]---

repeats.
Comment 1 Yi Sun 2014-07-10 07:35:53 UTC
Just curious, is it the same issue which QA encounter in following bug?
https://bugs.freedesktop.org/show_bug.cgi?id=75244#c18
Comment 2 Chris Wilson 2014-07-10 07:40:02 UTC
(In reply to comment #1)
> Just curious, is it the same issue which QA encounter in following bug?
> https://bugs.freedesktop.org/show_bug.cgi?id=75244#c18

Looks to be the same warning indeed. Always helps to keep the bug summary up-to-date.
Comment 3 Rodrigo Vivi 2014-10-08 21:21:26 UTC
Feel free to reopen if you are still able to reproduce it on latest drm-intel-nightly.

*** This bug has been marked as a duplicate of bug 75244 ***


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.