Still happening with drm-tip as of today. I appear to be special...

Just me.

I'm having the same issue with Linux 4.11 on an Skylake-based ASUS UX305, with Archlinux.

kernel: WARNING: CPU: 2 PID: 104 at drivers/gpu/drm/i915/intel_pm.c:3749 skl_compute_wm+0xbf7/0x1560 [i915]
kernel: WARN_ON(!intel_pstate->base.fb)
...

The computer boots and the screen becomes black when starting the DRM.

For now, I've downgraded to Linux 4.10 which is not affected by this issue.

(In reply to joel.porquet from comment #3)
> I'm having the same issue with Linux 4.11 on an Skylake-based ASUS UX305,
> with Archlinux.
> 
> kernel: WARNING: CPU: 2 PID: 104 at drivers/gpu/drm/i915/intel_pm.c:3749
> skl_compute_wm+0xbf7/0x1560 [i915]
> kernel: WARN_ON(!intel_pstate->base.fb)
> ...
> 
> The computer boots and the screen becomes black when starting the DRM.
> 
> For now, I've downgraded to Linux 4.10 which is not affected by this issue.

Hello Joel,
This bug had been already mark as CLOSED, if you can replicate the problem, could you please share a clean kern.log that includes the bug and change the status to REOPEN. Thank you.

Created attachment 132505 [details]
tar file containing most important logs

Hi all, 

I have a similar problem to Joel.

The system boots normally, the only problem is the screen remains black (the backlight seems to be turned on). I have remote control of the machine via ssh: I managed to start the sshd after logging in tty4 without having any visual control of what I was doing.

The most important tracelogs can be found in dmesg and syslog and look similar to this:
[    2.146215] ------------[ cut here ]------------
[    2.146253] WARNING: CPU: 2 PID: 254 at drivers/gpu/drm/i915/intel_pm.c:3749 skl_compute_wm+0xbf5/0x1550 [i915]
[    2.146253] WARN_ON(!intel_pstate->base.fb)
[    2.146254] Modules linked in: sparse_keymap mac80211 snd_soc_skl snd_soc_skl_ipc snd_soc_sst_ipc iwlwifi snd_soc_sst_dsp snd_hda_ext_core snd_soc_sst_mat
ch nls_iso8859_1 intel_rapl snd_soc_core x86_pkg_temp_thermal nls_cp437 intel_powerclamp coretemp snd_compress kvm_intel snd_pcm_dmaengine vfat cfg80211 fat 
kvm irqbypass ac97_bus crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel i915 pcbc aesni_intel snd_hda_intel idma64 snd_hda_codec uvcvideo aes_x
86_64 crypto_simd glue_helper cryptd videobuf2_vmalloc drm_kms_helper intel_cstate videobuf2_memops videobuf2_v4l2 snd_hda_core intel_rapl_perf videobuf2_cor
e snd_hwdep drm videodev snd_pcm media evdev snd_timer intel_gtt syscopyarea snd mei_me sysfillrect input_leds sysimgblt mac_hid pcspkr fb_sys_fops processor
_thermal_device soundcore
[    2.146275]  i2c_i801 mei i2c_algo_bit shpchp intel_pch_thermal intel_soc_dts_iosf intel_lpss_pci i2c_hid thermal elan_i2c hid wmi int3403_thermal hci_uar
t intel_lpss_acpi battery int3406_thermal int3402_thermal intel_lpss btqca video int340x_thermal_zone ac tpm_crb int3400_thermal asus_wireless acpi_thermal_r
el acpi_als led_class kfifo_buf button industrialio acpi_pad tpm_tis tpm_tis_core tpm btusb btrtl btbcm btintel bluetooth rfkill sch_fq_codel sg ip_tables x_
tables ext4 crc16 jbd2 fscrypto mbcache sd_mod serio_raw atkbd libps2 ahci libahci xhci_pci libata xhci_hcd scsi_mod usbcore usb_common i8042 serio
[    2.146300] CPU: 2 PID: 254 Comm: kworker/u8:4 Not tainted 4.11.7-1-ARCH #1
[    2.146301] Hardware name: ASUSTeK COMPUTER INC. UX305UA/UX305UA, BIOS UX305UA.201 10/12/2015
[    2.146305] Workqueue: events_unbound async_run_entry_fn
[    2.146306] Call Trace:
[    2.146310]  dump_stack+0x63/0x81
[    2.146312]  __warn+0xcb/0xf0
[    2.146314]  warn_slowpath_fmt+0x5a/0x80
[    2.146345]  skl_compute_wm+0xbf5/0x1550 [i915]
[    2.146379]  intel_atomic_check+0x5ac/0x11a0 [i915]
[    2.146386]  ? drm_mode_object_unreference+0x15/0x20 [drm]
[    2.146392]  drm_atomic_check_only+0x39e/0x580 [drm]
[    2.146397]  drm_atomic_commit+0x18/0x50 [drm]
[    2.146400]  restore_fbdev_mode+0x222/0x280 [drm_kms_helper]
[    2.146402]  drm_fb_helper_restore_fbdev_mode_unlocked+0x2e/0x80 [drm_kms_helper]
[    2.146405]  drm_fb_helper_set_par+0x2d/0x60 [drm_kms_helper]
[    2.146435]  intel_fbdev_set_par+0x18/0x70 [i915]
[    2.146437]  fbcon_init+0x484/0x650
[    2.146440]  visual_init+0xd6/0x130
[    2.146441]  do_bind_con_driver+0x1fc/0x420
[    2.146443]  do_take_over_console+0x82/0x1b0
[    2.146445]  do_fbcon_takeover+0x5c/0xb0
[    2.146446]  fbcon_event_notify+0x587/0x780
[    2.146448]  notifier_call_chain+0x4a/0x70
[    2.146450]  blocking_notifier_call_chain+0x43/0x60
[    2.146452]  fb_notifier_call_chain+0x1b/0x20
[    2.146453]  register_framebuffer+0x24d/0x360
[    2.146455]  ? vga_switcheroo_client_fb_set+0x5b/0x70
[    2.146458]  drm_fb_helper_initial_config+0x230/0x3e0 [drm_kms_helper]
[    2.146487]  intel_fbdev_initial_config+0x18/0x30 [i915]
[    2.146489]  async_run_entry_fn+0x37/0x150
[    2.146491]  process_one_work+0x1e0/0x490
[    2.146493]  worker_thread+0x48/0x4e0
[    2.146494]  kthread+0x125/0x140
[    2.146495]  ? process_one_work+0x490/0x490
[    2.146497]  ? kthread_create_on_node+0x70/0x70
[    2.146499]  ret_from_fork+0x2c/0x40
[    2.146500] ---[ end trace b45da8c5dcb81a7f ]---
[    2.146501] ------------[ cut here ]------------

(In reply to Martin from comment #5)
> Created attachment 132505 [details]
> tar file containing most important logs

Thanks for the update Martin,
Could you please attach another dmesg but with drm.debug=0xe parameter on grub and change to REOPEN?
Thank you.

(In reply to joel.porquet from comment #3)
> I'm having the same issue with Linux 4.11 on an Skylake-based ASUS UX305,
> with Archlinux.
> 
> kernel: WARNING: CPU: 2 PID: 104 at drivers/gpu/drm/i915/intel_pm.c:3749
> skl_compute_wm+0xbf7/0x1560 [i915]
> kernel: WARN_ON(!intel_pstate->base.fb)
> ...
> 
> The computer boots and the screen becomes black when starting the DRM.
> 
> For now, I've downgraded to Linux 4.10 which is not affected by this issue.

Want to contribute that I have this same issue, also on an ASUS UX305; all kernels after 4.11.3.

Hello everybody, still reproducible with latest tip/mainline? Thanks.

https://cgit.freedesktop.org/drm-tip
https://www.kernel.org

First of all. Sorry about spam.
This is mass update for our bugs. 

Sorry if you feel this annoying but with this trying to understand if bug still valid or not.
If bug investigation still in progress, please ignore this and I apologize!

If you think this is not anymore valid, please comment to the bug that can be closed.
If you haven't tested with our latest pre-upstream tree(drm-tip), can you do that also to see if issue is valid there still and if you cannot see issue there, please comment to the bug.

Chris, is this still valid?

Closing, please re-open is issue still exists.