Bug 106130 - [CHV] Toshiba LX0W-C64, 50/50% black screen on boot, always at debug and resume
Summary: [CHV] Toshiba LX0W-C64, 50/50% black screen on boot, always at debug and resume
Status: NEEDINFO
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: x86-64 (AMD64) Linux (All)
: high major
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard: Triaged, ReadyForDev
Keywords:
Depends on:
Blocks:
 
Reported: 2018-04-18 21:28 UTC by Denis
Modified: 2019-07-13 18:37 UTC (History)
2 users (show)

See Also:
i915 platform: BSW/CHT
i915 features: display/DSI


Attachments
dmesg with drm.debug=0x1e log_buf_len=4M (112.48 KB, text/x-log)
2018-04-18 21:28 UTC, Denis
no flags Details
dmesg with https://patchwork.freedesktop.org/series/41953/ (113.91 KB, text/x-log)
2018-04-19 10:30 UTC, Denis
no flags Details
i915_vbt (7.00 KB, application/octet-stream)
2018-04-19 10:32 UTC, Denis
no flags Details
dmesg with first patch from https://patchwork.freedesktop.org/series/41953/ (114.07 KB, text/x-log)
2018-04-19 14:18 UTC, Denis
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Denis 2018-04-18 21:28:00 UTC
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
Comment 1 Jani Saarinen 2018-04-19 06:41:57 UTC
Jani, can you have a look as dsi? Joonas for gem.
Comment 2 Jani Nikula 2018-04-19 09:01:58 UTC
Please test these two patches https://patchwork.freedesktop.org/series/41953/

Please attach /sys/kernel/debug/dri/0/i915_vbt
Comment 4 Denis 2018-04-19 10:32:59 UTC
Created attachment 138924 [details]
i915_vbt
Comment 5 Jani Nikula 2018-04-19 10:46:58 UTC
(In reply to Denis from comment #3)
> Created attachment 138923 [details]
> dmesg with https://patchwork.freedesktop.org/series/41953/

But... does it help?
Comment 6 Denis 2018-04-19 10:52:04 UTC
(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
Comment 7 Denis 2018-04-19 10:52:34 UTC
(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
Comment 8 Jani Nikula 2018-04-19 12:20:35 UTC
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/
Comment 9 Denis 2018-04-19 13:03:11 UTC
(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
Comment 10 Jani Nikula 2018-04-19 13:51:23 UTC
(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.
Comment 11 Denis 2018-04-19 14:18:24 UTC
Created attachment 138925 [details]
dmesg with first patch from https://patchwork.freedesktop.org/series/41953/
Comment 12 Francesco Balestrieri 2018-05-07 13:39:15 UTC
Jani, did the new log provide any info?
Comment 13 Jani Nikula 2018-05-08 09:47:18 UTC
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...
Comment 14 Simon Lee 2018-07-17 14:27:36 UTC
Hi Jani,

What are the next steps for this issue?
Comment 15 Jani Nikula 2018-10-23 11:40:20 UTC
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.
Comment 16 Lakshmi 2018-11-05 09:14:45 UTC
Denis, have you tried to verify this issue with latest drm-tip?
Comment 17 Denis 2018-11-06 18:11:26 UTC
(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
Comment 18 Denis 2019-01-17 18:00:00 UTC
Well, it's been a while. The bug is still present on drm tip
Comment 19 Lakshmi 2019-06-04 09:43:58 UTC
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.
Comment 20 Lakshmi 2019-07-13 18:37:01 UTC
@Denis, need logs from drmtip to investigate this further. Can you please attach dmesg from latest drmtip?


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.