I'm seeing an "Unclaimed write to register 0x1e0100" WARN_ON trigger with 5.4-rc3 on an Asus T100HA (after a suspend/resume cycle): [ 247.738558] ------------[ cut here ]------------ [ 247.739115] Unclaimed write to register 0x1e0100 [ 247.739349] WARNING: CPU: 0 PID: 2778 at drivers/gpu/drm/i915/intel_uncore.c:1098 skl_pcode_request+0xae1/0x74a0 [i915] [ 247.739363] Modules linked in: fuse bnep sunrpc vfat fat snd_soc_sst_cht_bsw_rt5645 mei_hdcp intel_rapl_msr intel_powerclamp gpio_keys coretemp kvm_intel kvm irqbypass intel_cstate asus_nb_wmi wdat_wdt pcspkr btsdio brcmfmac brcmutil joydev cfg80211 snd_sof_acpi snd_sof_intel_byt snd_sof_intel_bdw snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_intel_sst_acpi snd_intel_sst_core hid_sensor_gyro_3d hid_sensor_magn_3d hid_sensor_rotation hid_sensor_incl_3d hid_sensor_accel_3d snd_soc_sst_atom_hifi2_platform hid_sensor_trigger hid_sensor_iio_common snd_soc_rt5645 industrialio_triggered_buffer snd_soc_acpi_intel_match kfifo_buf snd_soc_acpi industrialio snd_soc_rl6231 snd_soc_core mei_txe intel_xhci_usb_role_switch roles cros_ec_ishtp cros_ec processor_thermal_device hci_uart intel_rapl_common lpc_ich mei snd_hdmi_lpe_audio intel_soc_dts_iosf intel_atomisp2_pm snd_compress ac97_bus snd_pcm_dmaengine btqca btrtl btbcm snd_seq btintel bluetooth snd_seq_device snd_pcm intel_hid snd_timer snd [ 247.739687] ecdh_generic ecc soundcore spi_pxa2xx_platform dw_dmac int3406_thermal int3403_thermal int340x_thermal_zone int3400_thermal soc_button_array acpi_thermal_rel intel_int0002_vgpio acpi_pad dm_crypt hid_sensor_hub intel_ishtp_loader mmc_block intel_ishtp_hid hid_multitouch crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel i915(E) i2c_algo_bit drm_kms_helper drm hid_asus asus_wmi sparse_keymap uas rfkill usb_storage intel_ish_ipc intel_ishtp wmi video i2c_hid(E) sdhci_acpi sdhci mmc_core pwm_lpss_platform pwm_lpss i2c_dev [ 247.739914] CPU: 0 PID: 2778 Comm: kworker/u8:15 Tainted: G E 5.4.0-rc3+ #188 [ 247.739928] Hardware name: ASUSTeK COMPUTER INC. T100HAN/T100HAN, BIOS T100HAN.221 05/18/2016 [ 247.739954] Workqueue: events_unbound async_run_entry_fn [ 247.740027] RIP: 0010:skl_pcode_request+0xae1/0x74a0 [i915] [ 247.740045] Code: 5d 41 5c 41 5d c3 45 84 ed 48 c7 c0 78 e0 58 c0 44 89 e2 48 c7 c6 6e e0 58 c0 48 0f 44 f0 48 c7 c7 81 e0 58 c0 e8 07 85 cc f9 <0f> 0b 83 2d 06 0b 20 00 01 5b 5d 41 5c 41 5d c3 66 66 2e 0f 1f 84 [ 247.740060] RSP: 0018:ffffb58d81dafce8 EFLAGS: 00010082 [ 247.740078] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000006 [ 247.740091] RDX: 0000000000000007 RSI: 0000000000000000 RDI: ffff9b87b4bd7d80 [ 247.740106] RBP: ffff9b87b4290f40 R08: 00000039ae670dd0 R09: 0000000000000000 [ 247.740119] R10: 0000000000000000 R11: ffff9b87ab428900 R12: 00000000001e0100 [ 247.740132] R13: 0000000000000000 R14: ffff9b87b4290f58 R15: ffffffffbb38da17 [ 247.740148] FS: 0000000000000000(0000) GS:ffff9b87b4a00000(0000) knlGS:0000000000000000 [ 247.740162] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 247.740175] CR2: 00007fd12f6f988a CR3: 000000003d612000 CR4: 00000000001006f0 [ 247.740190] Call Trace: [ 247.740287] skl_pcode_request+0x66f9/0x74a0 [i915] [ 247.740395] intel_power_domains_init_hw+0x4ec/0x620 [i915] [ 247.740469] ? vlv_force_gfx_clock+0x840/0x4430 [i915] [ 247.740550] intel_power_domains_resume+0x3e/0x60 [i915] [ 247.740615] vlv_force_gfx_clock+0x7f9/0x4430 [i915] [ 247.740651] dpm_run_callback+0x66/0x240 [ 247.740693] device_resume_early+0x9d/0x180 [ 247.740736] async_resume_early+0x1c/0x30 [ 247.740757] async_run_entry_fn+0x39/0x160 [ 247.740792] process_one_work+0x247/0x580 [ 247.740863] worker_thread+0x50/0x3b0 [ 247.740919] kthread+0x10a/0x140 [ 247.740936] ? process_one_work+0x580/0x580 [ 247.740952] ? kthread_park+0x90/0x90 [ 247.740990] ret_from_fork+0x3a/0x50 [ 247.741085] irq event stamp: 2162 [ 247.741104] hardirqs last enabled at (2161): [<ffffffffbab3bbdb>] _raw_spin_unlock_irqrestore+0x4b/0x60 [ 247.741121] hardirqs last disabled at (2162): [<ffffffffbab3c383>] _raw_spin_lock_irqsave+0x23/0x83 [ 247.741141] softirqs last enabled at (2138): [<ffffffffbae0035d>] __do_softirq+0x35d/0x45d [ 247.741159] softirqs last disabled at (2131): [<ffffffffba0f20e4>] irq_exit+0xf4/0x100 [ 247.741173] ---[ end trace d10e680a24fba687 ]---
Can you verify the issue with drmtip? (https://cgit.freedesktop.org/drm-tip) with kernel parameters drm.debug=0x1e log_buf_len=4M. If the problem persists attach the full dmesg from boot. Is there any other impact other than the warning?
The CI Bug Log issue associated to this bug has been updated. ### New filters associated * BSW: igt@gem_exec_suspend@basic-s0 - dmesg-warn - Unclaimed write to register 0x1e0100 - https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15009/fi-bsw-n3050/igt@gem_exec_suspend@basic-s0.html - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7213/fi-bsw-n3050/igt@gem_exec_suspend@basic-s0.html
(In reply to CI Bug Log from comment #2) > The CI Bug Log issue associated to this bug has been updated. > > ### New filters associated > > * BSW: igt@gem_exec_suspend@basic-s0 - dmesg-warn - Unclaimed write to > register 0x1e0100 > - > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15009/fi-bsw-n3050/ > igt@gem_exec_suspend@basic-s0.html > - > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7213/fi-bsw-n3050/ > igt@gem_exec_suspend@basic-s0.html @Chris, correct me if these failures are not part of this bug.
I have tried to reproduce this with drm-tip to gather the requested logs and with "normal" 5.4-rc7 I cannot reproduce it with either atm. It seems that this bug triggering might be timing dependent or some such :| So sorry, no logs.
(In reply to Hans de Goede from comment #4) > I have tried to reproduce this with drm-tip to gather the requested logs and > with "normal" 5.4-rc7 I cannot reproduce it with either atm. It seems that > this bug triggering might be timing dependent or some such :| > > So sorry, no logs. Thanks for verifying the issue with drmtip. I will close this issue as WORKSFORME. Please reopen this issue if it appears again.
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.