Created attachment 138909 [details] dmesg with drm.debug=0x1e log_buf_len=4M Screen goes black in 50% case on normal boot, always when boot with "drm.debug=0x1e log_buf_len=1M". Also in case of successful boot it goes black after changing resolution or waking up from suspend. I've tried to remove i915 from initrd (just in case), same result. Maybe this could be the reason: [ +0.000084] [drm:i915_gem_object_create_stolen_for_preallocated [i915]] failed to allocate stolen space Architecture: x86_64 Kernel: 4.17.0-1e1fbca48 (drm-tip 04.19.18) Linux distribution: Arch Linux Machine or mother board model: Toshiba Satellite Click 10 (LX0W-C64 model) Cherry trail cpu, X5-Z8300 Dispay connector: DSI-1
Jani, can you have a look as dsi? Joonas for gem.
Please test these two patches https://patchwork.freedesktop.org/series/41953/ Please attach /sys/kernel/debug/dri/0/i915_vbt
Created attachment 138923 [details] dmesg with https://patchwork.freedesktop.org/series/41953/
Created attachment 138924 [details] i915_vbt
(In reply to Denis from comment #3) > Created attachment 138923 [details] > dmesg with https://patchwork.freedesktop.org/series/41953/ But... does it help?
(In reply to Jani Nikula from comment #2) > Please test these two patches https://patchwork.freedesktop.org/series/41953/ > > Please attach /sys/kernel/debug/dri/0/i915_vbt Still black screen. I've attached i915_vbt and dmesg with patches
(In reply to Jani Nikula from comment #5) > (In reply to Denis from comment #3) > > Created attachment 138923 [details] > > dmesg with https://patchwork.freedesktop.org/series/41953/ > > But... does it help? Sorry, I'm not at home, bad internet con
When you have a moment, can you please run intel_reg from igt-gpu-toos [1] and provide the output of the following sequence: # intel_reg write 0x180000:0xb080 0xffffffff # intel_reg write 0x180000:0xb880 0xffffffff # intel_reg read 0x180000:0xb080 0x180000:0xb880 [1] https://cgit.freedesktop.org/drm/igt-gpu-tools/
(In reply to Jani Nikula from comment #8) > When you have a moment, can you please run intel_reg from igt-gpu-toos [1] > and provide the output of the following sequence: > > # intel_reg write 0x180000:0xb080 0xffffffff > # intel_reg write 0x180000:0xb880 0xffffffff > # intel_reg read 0x180000:0xb080 0x180000:0xb880 > > [1] https://cgit.freedesktop.org/drm/igt-gpu-tools/ # intel_reg write 0x180000:0xb080 0xffffffff Warning: stat '/usr/local/share/intel-gpu-tools/registers' failed: No such file or directory. Using builtin register spec. # intel_reg write 0x180000:0xb880 0xffffffff Warning: stat '/usr/local/share/intel-gpu-tools/registers' failed: No such file or directory. Using builtin register spec. # intel_reg read 0x180000:0xb080 0x180000:0xb880 Warning: stat '/usr/local/share/intel-gpu-tools/registers' failed: No such file or directory. Using builtin register spec. (0x00180000:0x0000b080): 0x3f1fff3f (0x00180000:0x0000b880): 0x3f1fff3f
(In reply to Denis from comment #9) > (0x00180000:0x0000b080): 0x3f1fff3f > (0x00180000:0x0000b880): 0x3f1fff3f Thanks, that confirms one detail, and patch 2 should be irrelevant here. Please apply only patch 1 of the series, i.e. https://patchwork.freedesktop.org/patch/217857/ and attach dmesg. It should provide us with some more clues.
Created attachment 138925 [details] dmesg with first patch from https://patchwork.freedesktop.org/series/41953/
Jani, did the new log provide any info?
Couple of things out of bounds that we limit. Not too much though. It may be a clue something else is bonkers with our calculations. [ 5.967819] [drm:intel_dsi_vbt_init [i915]] exit zero count too high 68 [ 5.967915] [drm:intel_dsi_vbt_init [i915]] trail count too high 32 Or it might be something completely different...
Hi Jani, What are the next steps for this issue?
No real clues I'm afraid, but please do try current drm-tip, and report back. There are a few changes that might impact this, but not sure.
Denis, have you tried to verify this issue with latest drm-tip?
(In reply to Lakshmi from comment #16) > Denis, have you tried to verify this issue with latest drm-tip? I'll try it in free time
Well, it's been a while. The bug is still present on drm tip
Denis, Can you give a try with latest drmtip? Sorry to ask you again, dmesg from latest drmtip will be useful to investigate the issue further.
@Denis, need logs from drmtip to investigate this further. Can you please attach dmesg from latest drmtip?
(In reply to Lakshmi from comment #19) > Denis, Can you give a try with latest drmtip? Sorry to ask you again, dmesg > from latest drmtip will be useful to investigate the issue further. (In reply to Lakshmi from comment #20) > @Denis, need logs from drmtip to investigate this further. Can you please > attach dmesg from latest drmtip? No feedback from more than a few months closing this issue as WORKSFORME. Please reopen the issue if the issue is reproducible with latest drmtip (https://cgit.freedesktop.org/drm-tip). Remember to attach dmesg from boot with kernel parameters drm.debug=0x1e log_buf_len=4M when this issue is reopened.
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.