<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - DC6 already programmed to be enabled while screen saver"
href="https://bugs.freedesktop.org/show_bug.cgi?id=103766">103766</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>DC6 already programmed to be enabled while screen saver
</td>
</tr>
<tr>
<th>Product</th>
<td>DRI
</td>
</tr>
<tr>
<th>Version</th>
<td>XOrg git
</td>
</tr>
<tr>
<th>Hardware</th>
<td>x86-64 (AMD64)
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux (All)
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>DRM/Intel
</td>
</tr>
<tr>
<th>Assignee</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>sp31415s_bugreport@gmx.com
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>CC</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr></table>
<p>
<div>
<pre>Created <span class=""><a href="attachment.cgi?id=135497" name="attach_135497" title="dmesg while funtional">attachment 135497</a> <a href="attachment.cgi?id=135497&action=edit" title="dmesg while funtional">[details]</a></span>
dmesg while funtional
Hi,
I'm using Debian Stretch (stable) with kernel from backport (4.12.13) on Kaby
Lake chip (i5-7600).
I got crash during screen saver.
extract from syslog :
Nov 15 16:33:36 lemon kernel: [10269.665458] DC6 already programmed to be
enabled.
Nov 15 16:33:36 lemon kernel: [10269.665480] ------------[ cut here
]------------
Nov 15 16:33:36 lemon kernel: [10269.665493] WARNING: CPU: 0 PID: 11235 at
/build/linux-RdeW6Z/linux-4.12.13/drivers/gpu/drm/i915/intel_runtime_pm.c:676
skl_enable_dc6+0x9e/0xb0 [i915]
Nov 15 16:33:36 lemon kernel: [10269.665493] Modules linked in: tun nls_ascii
nls_cp437 vfat fat intel_rapl x86_pkg_temp_thermal intel_powerclamp kvm_intel
kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmu
lni_intel intel_cstate mxm_wmi snd_hda_codec_hdmi intel_uncore
snd_hda_codec_realtek snd_hda_codec_generic intel_lpss_acpi snd_hda_intel
snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_timer intel_rapl_perf i9
15 intel_lpss mfd_core drm_kms_helper battery efi_pstore evdev snd efivars
serio_raw pcspkr iTCO_wdt iTCO_vendor_support wmi soundcore hci_uart sg btbcm
btqca btintel bluetooth ecdh_generic rfkill video acpi_pa
d button mei_me mei drm shpchp acpi_als kfifo_buf industrialio coretemp
parport_pc ppdev lp parport efivarfs ip_tables x_tables autofs4 ext4 crc16 jbd2
crc32c_generic fscrypto ecb mbcache sr_mod cdrom sd_mod hi
d_generic
Nov 15 16:33:36 lemon kernel: [10269.665513] usbhid crc32c_intel aesni_intel
aes_x86_64 crypto_simd cryptd glue_helper ahci e1000e libahci i2c_i801 igb
i2c_algo_bit dca xhci_pci ptp pps_core libata xhci_hcd us
bcore scsi_mod usb_common fan thermal i2c_hid hid
Nov 15 16:33:36 lemon kernel: [10269.665520] CPU: 0 PID: 11235 Comm:
kworker/0:1 Not tainted 4.12.0-0.bpo.2-amd64 #1 Debian 4.12.13-1~bpo9+1
Nov 15 16:33:36 lemon kernel: [10269.665521] Hardware name: Gigabyte Technology
Co., Ltd. Z270X-UD5/Z270X-UD5-CF, BIOS F5 07/07/2017
Nov 15 16:33:36 lemon kernel: [10269.665532] Workqueue: events
i915_hotplug_work_func [i915]
Nov 15 16:33:36 lemon kernel: [10269.665532] task: ffff8c8c42881080 task.stack:
ffffb4f247cb8000
Nov 15 16:33:36 lemon kernel: [10269.665540] RIP: 0010:skl_enable_dc6+0x9e/0xb0
[i915]
Nov 15 16:33:36 lemon kernel: [10269.665541] RSP: 0018:ffffb4f247cbbd20 EFLAGS:
00010282
Nov 15 16:33:36 lemon kernel: [10269.665542] RAX: 0000000000000025 RBX:
ffff8c8ce9940000 RCX: 0000000000000000
Nov 15 16:33:36 lemon kernel: [10269.665542] RDX: 0000000000000000 RSI:
ffff8c8d0ec0dee8 RDI: ffff8c8d0ec0dee8
Nov 15 16:33:36 lemon kernel: [10269.665542] RBP: ffff8c8ce9944b58 R08:
0000000000000001 R09: 00000000000003d9
Nov 15 16:33:36 lemon kernel: [10269.665543] R10: 0000000000000040 R11:
00000000000003d9 R12: ffffffffc0916e68
Nov 15 16:33:36 lemon kernel: [10269.665543] R13: ffff8c8ce9940000 R14:
0000000080000000 R15: ffff8c8ce4b56000
Nov 15 16:33:36 lemon kernel: [10269.665544] FS: 0000000000000000(0000)
GS:ffff8c8d0ec00000(0000) knlGS:0000000000000000
Nov 15 16:33:36 lemon kernel: [10269.665544] CS: 0010 DS: 0000 ES: 0000 CR0:
0000000080050033
Nov 15 16:33:36 lemon kernel: [10269.665545] CR2: 00007fdfb2515000 CR3:
00000007c2ecf000 CR4: 00000000003406f0
Nov 15 16:33:36 lemon kernel: [10269.665545] DR0: 0000000000000000 DR1:
0000000000000000 DR2: 0000000000000000
Nov 15 16:33:36 lemon kernel: [10269.665545] DR3: 0000000000000000 DR6:
00000000fffe0ff0 DR7: 0000000000000400
Nov 15 16:33:36 lemon kernel: [10269.665546] Call Trace:
Nov 15 16:33:36 lemon kernel: [10269.665554] ?
intel_display_power_put+0xb6/0x110 [i915]
Nov 15 16:33:36 lemon kernel: [10269.665564] ? intel_dp_detect+0x1be/0x6d0
[i915]
Nov 15 16:33:36 lemon kernel: [10269.665567] ?
drm_helper_probe_detect_ctx+0x41/0xd0 [drm_kms_helper]
Nov 15 16:33:36 lemon kernel: [10269.665576] ?
i915_hotplug_work_func+0x1e1/0x2a0 [i915]
Nov 15 16:33:36 lemon kernel: [10269.665578] ? process_one_work+0x181/0x370
Nov 15 16:33:36 lemon kernel: [10269.665579] ? worker_thread+0x4d/0x3a0
Nov 15 16:33:36 lemon kernel: [10269.665580] ? kthread+0xfc/0x130
Nov 15 16:33:36 lemon kernel: [10269.665580] ? process_one_work+0x370/0x370
Nov 15 16:33:36 lemon kernel: [10269.665581] ?
kthread_create_on_node+0x70/0x70
Nov 15 16:33:36 lemon kernel: [10269.665582] ? ret_from_fork+0x25/0x30
Nov 15 16:33:36 lemon kernel: [10269.665583] Code: 05 1b 99 0e 00 01 e8 b8 53
73 cb 0f ff eb 9b 80 3d 0a 99 0e 00 00 75 a9 48 c7 c7 d0 6b 91 c0 c6 05 fa 98
0e 00 01 e8 98 53 73 cb <0f> ff eb 92 0f 1f 40 00 66 2
e 0f 1f 84 00 00 00 00 00 0f 1f 44
Nov 15 16:33:36 lemon kernel: [10269.665595] ---[ end trace 8778ee3d58864911
]---
Nov 15 16:33:36 lemon kernel: [10269.665607] [drm:gen9_set_dc_state [i915]]
*ERROR* DC state mismatch (0x0 -> 0x2)
I also attached the dmesg from the next reboot.
I found some bug report with the same error message but not tthe same call
trace
Regards,
Serge</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are on the CC list for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>