| Summary: | Intel 8550U with 620UHD GPU screen flashing | ||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | DRI | Reporter: | Joe <R34skyline> | ||||||||||||||||||||||||||||||
| Component: | DRM/Intel | Assignee: | Jani Saarinen <jani.saarinen> | ||||||||||||||||||||||||||||||
| Status: | RESOLVED MOVED | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||||||||||||||||||||||||||
| Severity: | normal | ||||||||||||||||||||||||||||||||
| Priority: | high | CC: | bugs, intel-gfx-bugs, james.ausmus, kai.heng.feng, mazinalhaddad05, midskavid, R34skyline, stanislav.lisovskiy, yuglooc | ||||||||||||||||||||||||||||||
| Version: | XOrg git | ||||||||||||||||||||||||||||||||
| Hardware: | x86-64 (AMD64) | ||||||||||||||||||||||||||||||||
| OS: | Linux (All) | ||||||||||||||||||||||||||||||||
| Whiteboard: | Triaged, ReadyForDev | ||||||||||||||||||||||||||||||||
| i915 platform: | KBL | i915 features: | display/DP | ||||||||||||||||||||||||||||||
| Attachments: |
|
||||||||||||||||||||||||||||||||
|
Description
Joe
2018-10-02 15:43:17 UTC
Joe, Can you please try to reproduce the issue using drm-tip (https://cgit.freedesktop.org/drm-tip) and kernel parameters drm.debug=0x1e log_buf_len=4M, and if the problem persists attach the full dmesg from boot. Joe, In order to debug the issue, following information will be useful cat /sys/kernel/debug/dri/0/i915_edp_psr_status Can you send this output? *** Bug 108138 has been marked as a duplicate of this bug. *** For starters, full dmesg with drm.debug=14 on whichever kernel you're running will be helpful, but be prepared to try drm-tip too. And do *attach* the logs, don't add them in comments! Jani & Lakshmi, Thank you for your continued support and my apologies for creating a duplicate on this. I received and email saying this ticket was canceled due to size so I created a new one with the dmesg attached. I will try the drm-tip when I get back to my laptop this evening and report. Will also include the full dmesg from boot and the cat /sys/kernel/debug/dri/0/i915_edp_psr_status. Can I get some guidance on the following to help debug? Where do I change drm.debug=0x1e & log_buf_len=4M? Also should I add the drm.debug=14 to these as well and produce the log? Thanks, Joe Ok apparently I'm a noob, I can't get drm-tip to install and I have no clue where to add the config statements. Any help would be appreciated. Joe Created attachment 141867 [details]
cat /sys/kernel/debug/dri/0/i915_edp_psr_status
Created attachment 141868 [details]
dmesg after drm changes
Ok so the only thing I couldn't figure out is install drm-tip. So unfortunately I was not able to get the dmesg after drm-tip. (In reply to Joe from comment #6) > Ok apparently I'm a noob, I can't get drm-tip to install and I have no clue > where to add the config statements. Any help would be appreciated. > > Joe Joe, go to grub file under /etc/default and edit like below Grub-cmdline-linux-default = “quiet splash drm.debug=0x1e log_buf_len=4M” This is also happening on the 8250U version of the ideapad 720s. I can attach logs if you would find them helpful. Mazin,Can you also elaborate the issue, to ensure its the same bug. Have you verified with latest drm-tip? You can attach the dmesg with kernel parameters drm.debug=0x1e log_buf_len=4M from boot. The above information will help us in debugging. (In reply to Lakshmi from comment #10) > (In reply to Joe from comment #6) > > Ok apparently I'm a noob, I can't get drm-tip to install and I have no clue > > where to add the config statements. Any help would be appreciated. > > > > Joe > > Joe, go to grub file under /etc/default and edit like below > Grub-cmdline-linux-default = “quiet splash drm.debug=0x1e log_buf_len=4M” Lakshmi, I was able to make the changes to grub and attached the dmesg. Please look at dmesg2.txt. Thanks, joe Created attachment 141902 [details]
dmesg2.txt
Team, I was able to perform the following tasks: git clone git://anongit.freedesktop.org/drm-tip make defconfig make sudo make modules_install sudo make install However, I must be missing a step because dim and or drm-tip are not known programs. Thoughts on getting drm-tip to run? Thanks, Joe Looks like my changes did not take I reviewed the dmesg and noticed it loaded the i915. I attached dmesg3.txt with the changes. Also note that I change the grub and still the changed didn't take. I have attached the grub file as well so you can see my changes. Joe Created attachment 141905 [details]
dmesg3.txt
Created attachment 141906 [details]
grub
Any Luck Team? Joe, if not with latest drm-tip, can you try with latest mainline kernel. (In reply to Lakshmi from comment #20) > Joe, if not with latest drm-tip, can you try with latest mainline kernel. What would you like me to try?
> What would you like me to try?
Try to reproduce the issue with latest kernel with kernel parameters drm.debug=0x1e log_buf_len=4M, and if the problem persists attach the full dmesg from boot.
Created attachment 141943 [details] Kernel 4.19 before flickering stops There is still artifact issues that sometimes go away with time, this is with kernel 4.19. I don't know how to install a kernel from source and got a out of data error when I tried your provided link. This is from the .deb files http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-nightly/2018-10-08/ I found here. Thank you for your time and hope my contribution is useful Created attachment 141944 [details]
flickering stopped
(In reply to Lakshmi from comment #22) > > > What would you like me to try? > Try to reproduce the issue with latest kernel with kernel parameters > drm.debug=0x1e log_buf_len=4M, and if the problem persists attach the full > dmesg from boot. Lakshmi, You are a godsend!!! Finally no more glitching.. Thought I was going to have a seizure watching the screen glitch like that... In any case, I did want to tell you the splash screen glitched out but once I logged in, no more glitching or artifacts. I did install the latest kernel, the latest headers, and the latest modules. Attached is dmesg4.txt which is my latest dmesg in case you need if for the splash screen. I removed something from kernel parameters but will have to go back to see what it was. Wish I could help you folks on a regular basis but I'm no programmer just a network admin. Joe Created attachment 141947 [details]
dmesg4.txt
Lakshmi, If you don’t mind can you explain what the fix was/how you fixed it? Team is making changes on regular basis to improve the quality. You had a bit old kernel, so asked you to check with latest kernel. That solved the major problem. You had the glitch only once? Were able to reproduce it again? (In reply to Lakshmi from comment #28) > Team is making changes on regular basis to improve the quality. You had a > bit old kernel, so asked you to check with latest kernel. That solved the > major problem. > > You had the glitch only once? Were able to reproduce it again? I can reproduce the glitch on kernel 4.18 and the following systems. Ubuntu 18.04 and 18.10 daily, Fedora 28 and 29 Beta, and Deepin Linux. I don't recall all of their kernel versions but 4.19 only worked on yesterday's daily update. Basically anything older then yesterday's kernel update won't work and the splash screen still glitches. Here is where I got the main kernel from for Ubuntu. http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-nightly/2018-10-08/ Joe (In reply to Mazin from comment #23) > Created attachment 141943 [details] > Kernel 4.19 before flickering stops > > There is still artifact issues that sometimes go away with time, this is > with kernel 4.19. I don't know how to install a kernel from source and got a > out of data error when I tried your provided link. This is from the .deb > files > http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-nightly/2018-10-08/ > I found here. Thank you for your time and hope my contribution is useful Mazin, Just read this, wish I had this last night would have made my google searching less time consuming. Thanks for posting!! Joe (In reply to Lakshmi from comment #28) > Team is making changes on regular basis to improve the quality. You had a > bit old kernel, so asked you to check with latest kernel. That solved the > major problem. > > You had the glitch only once? Were able to reproduce it again? Sorry, for second response. I had the glitch continuously until I went to last night's build. That's why I was asking what change you made to fix it. Also what do you consider to be an old kernel because I tried 4.19 and 4.19 until last night. Joe (In reply to Joe from comment #31) > (In reply to Lakshmi from comment #28) > > Team is making changes on regular basis to improve the quality. You had a > > bit old kernel, so asked you to check with latest kernel. That solved the > > major problem. > > > > You had the glitch only once? Were able to reproduce it again? > > Sorry, for second response. I had the glitch continuously until I went to > last night's build. If you don't see any problems with available latest kernel, I would like to close this bug. That's why I was asking what change you made to fix it. If kernel is build from drm-tip branch, git log might help to see all the recent changes done. In your case, I believe the file CHANGES (in the same link you posted) will help to see the changes. > Also what do you consider to be an old kernel because I tried 4.19 and 4.19 > until last night. Latest drm-tip is considered as the latest kernel where you will get all the recent changes (up-to date). Recommended to try latest kernel if not the latest kernel. (In reply to Lakshmi from comment #32) > (In reply to Joe from comment #31) > > (In reply to Lakshmi from comment #28) > > > Team is making changes on regular basis to improve the quality. You had a > > > bit old kernel, so asked you to check with latest kernel. That solved the > > > major problem. > > > > > > You had the glitch only once? Were able to reproduce it again? > > > > Sorry, for second response. I had the glitch continuously until I went to > > last night's build. > > If you don't see any problems with available latest kernel, I would like to > close this bug. > > > That's why I was asking what change you made to fix it. > > If kernel is build from drm-tip branch, git log might help to see all the > recent changes done. In your case, I believe the file CHANGES (in the same > link you posted) will help to see the changes. > > > Also what do you consider to be an old kernel because I tried 4.19 and 4.19 > > until last night. > > Latest drm-tip is considered as the latest kernel where you will get all the > recent changes (up-to date). Recommended to try latest kernel if not the > latest kernel. The issue still happens but most of the time it goes away after a few minutes of usage on the latest kernel. When it doesn't, rebooting and waiting for around 5 minutes usually fixes it. (In reply to Mazin from comment #34) > The issue still happens but most of the time it goes away after a few > minutes of usage on the latest kernel. When it doesn't, rebooting and > waiting for around 5 minutes usually fixes it. Mazin, Can you please elaborate the issue from this scenario? Is there any particular pattern where you see this issue? How often you see this issue? Can you attach the dmesg log? Created attachment 142004 [details]
kernel 4.19 2018-10-12
On the latest kernel built on 2018-10-12 the screen displays those artifacts the whole time. The artifacts do not appear until the kernel is loaded by grub, at which point it starts to "flicker".The issue is always present and the screen flickers 24/7 and doesn't require any steps to be reproduced. With the latest kernel the display also turns off for around a second and comes back on in addition to always flickering. The artifacts are always present during the boot process and when using any desktop environment regardless if it was running on X11 or wayland. I have attached a dmesg log hopefully I was clear, but you will have to forgive me if I was not as english is not my native language.
Wanted to see when the did for the splash screen would occur? I still have glitching on the splash screen, also how long does it take for these kernel updates be used in Ubuntu LTS? Joe the issue still happens on the newer daily kernels that were released yesterday, I think the fix may have been "coincidental" so it hasn't been fixed yet which is why you see the artifacts at splash screen Do you guys need anything else or is this good for now? For now, we don't need anything more. If needed our team will contact you. (In reply to Mazin from comment #39) > Do you guys need anything else or is this good for now? I was afraid that was the case. However, even with the splash screen still broken the desktop not glitching is much easier to troubleshoot. I was also hoping to install a kernel that loads smoothly. (In reply to Lakshmi from comment #40) > For now, we don't need anything more. If needed our team will contact you. Lakshmi, Happen to have an estimated time when we can see a true fix? Not rushing just looking forward to a solid boot and OS load. Joe Idk if some of the devs here are even payed to fix this, which is why we shouldn't ask for an ETA. Just want to report that the issue is still present when rolling back to the kernel built on 2018-10-08. It used to stop flickering after 20 minutes of usage everytime I boot up/ wake the laptop from sleep. But now the issue is present 24/7 on every kernel I try. Lakshmi, sorry for asking but does this have anything to do with link training for eDP? Just curious to know whats going on. Setting nomodeset and i915.modeset=0 stops the flickering on today's kernel! Mazin - from a look at your most recent attached log, it doesn't appear to be link training related - I'm only seeing 2 link training failures (one at ~67 seconds, one at ~77 seconds), so these wouldn't account for the continual flashing that you're describing. Have you been able to try drm-tip on your system yet? Created attachment 142392 [details]
form drm-tip built on 2018-11-02
The one from oct 12 was from drm-tip, but I have been updating to the latest kernel from drm-tip daily to see if the issue has been fixed and the lateset one I have installed is from 2018-11-02. I couldn't install kernel 4.20rc as it returns Error 2. I think the issue is from the hotplug events towards the end of the dmesg. I will attach one from 2018-11-02 just in case.
I just tried building the latest kernel from drm-tip with the old makeconfig settings and it still has the same problem. If I try to say yes to any of the new changes during make oldconfig it spits out an error message when I try to build it (error 2), so I just said no to everything. The config was taken from ubuntu 18.04. Created attachment 142399 [details]
Forgot to add required boot parameters, here is the fixed one
Ah forgot to add drm.debug=0x1e and log_buf_len=4M, added them in this one.
James, any suggestion here? *** Bug 108702 has been marked as a duplicate of this bug. *** I am also having the same issue! Is there anyway in which I can help ? My kernel is 4.15.0-38-generic and flickering vanishes much more quickly on battery (under 1 minute) than when plugged in only to resurface next after computer wakes up from sleep or boots or locked screen (and screen turns black). In short, anytime the pixels are painted afresh, flickering begins. Mirdul, how did you get it to stop flickering. When I was on kernel 4.15, it used to go away just like how you described. But ever since I upgraded the kernel, even downgrading won't fix it. It's always present for me whether i'm on battery or not. I also noticed that it does only flicker when there is a redraw. Enabling Panel self refresh and having the laptop display a static image causes the flickering to vanish as long as I don't do anything. If I move the cursor for example it would start flickering again. Mazen, now that I think about it, initially, the flicker was horrible. I saw some posts asking me to set 'intel_idle.max_cstate=1'. However this had no effect on the flicker. I then uninstalled intel drivers completely and reinstalled by adding this ppa https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers. These are the drivers I have currently. Maybe you can check if this helps in reducing the flicker a little. Tried updating with that ppa added, but nothing changed. Also the i915 driver is included in the kernel I don't understand what you mean by reinstalled the drivers. I really hope this bug gets fixed soon. Any change in behavior with i915.enable_psr=0 added to the kernel command line? No changes with psr disabled as it was the default state, the artifacts are present 24/7. However, when psr is enabled and the refreshes happen from the panels memory the flickering stops. Whenever something changes on the screen and stuff have to be rendered the screen displays those artifacts. what about booting with i915.enable_dc=0 ? I added `i915.enable_dc=0' to GRUB_CMDLINE_LINUX_DEFAULT; updated grub and rebooted, but still nothing. It is still flickering. I experienced the same thing as Mirdul. Hi, just idea, could this series from Ville helping on symptoms? https://patchwork.freedesktop.org/series/51878/ I don't know how to apply the patch, I keep getting errors with git am. Hopefully someone else can try it. Hi guys! I'm having the same problem on my new laptop - Razer Blade Stealth 13". System: Kubuntu 18.04 CPU: i7-8550U Video: Intel UHD Graphics 620 (rev 07) (prog-if 00 [VGA controller]) Kernel: 4.15.0-39-generic There are some updates I haven't yet applied since system install, so I'm going to update and then write back. Same issue here, Ideapad 720S, i5 version with the 620UHD chip. Tried running drm-tip and also Ville's patch but still have the constant flickering. Good news! I activated fastboot (add kernel param i915.fastboot=1) and that caused the flickering to stop! Yugge, It looks good and there is almost no glitching(just a slight flicker) when booting and thereafter. However, once the system wakes from sleep or a locked screen, flickering returns! Are you not facing this? Just tried adding i915.fastboot=1, it stops the flickering. But I'm experiencing the same thing as Mirdul, where after having the laptop suspend the flickering is back. I had not tried suspending when I wrote before, but yes, I also experience it returning. But at least it turned my new laptop from totally useless to with some annoyances. :) It hope it might also give some puzzle pieces to what is wrong with the driver. Yes, indeed! Hi. Same issue on a new Lenovo Ideapad 530s, having the same Intel graphics card. However, if I connect a second display over HDMI, the laptop display flickers while this other display is functioning just fine (doing this in mirror mode). P.S.: This flickering issue was encountered on Ubuntu 18.04LTS and Debian 9.6, but not on Windows 10, so it doesn't seem to be a hardware problem, or at least not entirely. :)) Just started flickering on Windows as well. It might just be a hardware bug, after all. @Yugge, Your fix was a life saver! I think this bug is on a lower priority with them and chances of it being fixed anytime soon are bleak. You saved our lives!! I was contemplating going back to Windows; the flickering was so bad.. Imagine! Thanks again! Could you also create a debug log with drm.debug=0x1e and fastboot=1 ? Looking at dump_pipe_config, I don't see big differences. setup_hw_state: [drm:intel_dump_pipe_config [i915]] dp m_n: lanes: 4; gmch_m: 6213395, gmch_n: 8388608, link_m: 517782, link_n: 524288, tu: 64 Only thing in link is: modeset: [drm:intel_dump_pipe_config [i915]] dp m_n: lanes: 4; gmch_m: 6213395, gmch_n: 8388608, link_m: 1035565, link_n: 1048576, tu: 64 Doubt that causes it.. But could always try a lower m/n value.. In i915/intel_dp.c: bool constant_n = drm_dp_has_quirk(&intel_dp->desc, DP_DPCD_QUIRK_CONSTANT_N); Change to bool constant_n = true; Fixed it (on Ubuntu 18.04) with this: sudo gedit /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT=”quiet splash nomodeset" then exit the gedit sudo update-grub reboot More details here: https://askubuntu.com/questions/1068022/screen-tearing-flickering-on-lenovo-ideapad-720s-131ikb?fbclid=IwAR37_dYF_Q4mqLZ20KMPeNvb4yZYH7_X299pXdYs214hLGhaiYI2p78kE88 Pay attention at the wrong quote sign, please! So: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset" @Dromichet adding nomodeset make my setup not boot, both on my primary arch and on liveusbs of buntulikes @Maarten Lankhorst - Will try it out when I get the chance! @Maarten Lankhorst - Verified, forcing constant_n to true does solve the issue and let me restore from suspend without flickering! This is a display DP bug then, probably needs some quirk to work correctly. :) (In reply to Yugge from comment #78) > @Maarten Lankhorst - Verified, forcing constant_n to true does solve the > issue and let me restore from suspend without flickering! Will I have to build the drivers from source? Is this documented somewhere (how to build it from source)? Also, is this the final fix? forcing it to true? Lenovo 720s-13IKS 81A8000SRK. Update to latest BIOS (5SSCN34WW to 5SCN38WW) fix the problem for me. Ubuntu 18.10. (In reply to Mridul from comment #80) > (In reply to Yugge from comment #78) > > @Maarten Lankhorst - Verified, forcing constant_n to true does solve the > > issue and let me restore from suspend without flickering! > > Will I have to build the drivers from source? Is this documented somewhere > (how to build it from source)? > > Also, is this the final fix? forcing it to true? It very much depends on the distribution on how to do it properly, Arch has it documented https://wiki.archlinux.org/index.php/Kernel/Traditional_compilation . I wouldn't call the fix final, While it did stop some flickering (short suspension, closing the lid) it caused other issues, flickering returning after a long suspension (laptop picked up after being in my bag for a while) and sometimes caused the screen not to turn on after lid open. So it might indicate something about the issue, but is by no means the final fix. (In reply to Dmitry from comment #81) > Lenovo 720s-13IKS 81A8000SRK. Update to latest BIOS (5SSCN34WW to 5SCN38WW) > fix the problem for me. Ubuntu 18.10. Was interested to see if it was indeed a bios issue for my Lenovo 720s-13IKB 81BV so I updated the bios to 6MCN28WW. The issue still remained, unfortunately. Just to confirmed, that model is the UHD version right? (In reply to Yugge from comment #83) > (In reply to Dmitry from comment #81) > > Lenovo 720s-13IKS 81A8000SRK. Update to latest BIOS (5SSCN34WW to 5SCN38WW) > > fix the problem for me. Ubuntu 18.10. > > Was interested to see if it was indeed a bios issue for my Lenovo 720s-13IKB > 81BV so I updated the bios to 6MCN28WW. The issue still remained, > unfortunately. Just to confirmed, that model is the UHD version right? Yes, UHD versoin. dm@720S-13IKB:~$ sudo systool -vm i915 [sudo] пароль для dm: Module = "i915" Attributes: coresize = "1740800" initsize = "0" initstate = "live" refcnt = "20" srcversion = "8F2ABA1EAAB491BBB0801EE" taint = "" uevent = <store method only> Parameters: alpha_support = "N" disable_display = "N" disable_power_well = "1" dmc_firmware_path = "(null)" edp_vswing = "0" enable_cmd_parser = "Y" enable_dc = "-1" enable_dp_mst = "Y" enable_dpcd_backlight= "N" enable_fbc = "1" enable_guc = "0" enable_gvt = "N" enable_hangcheck = "Y" enable_ips = "1" enable_ppgtt = "3" enable_psr = "0" error_capture = "Y" fastboot = "N" force_reset_modeset_test= "N" guc_firmware_path = "(null)" guc_log_level = "0" huc_firmware_path = "(null)" invert_brightness = "0" load_detect_test = "N" lvds_channel_mode = "0" mmio_debug = "0" modeset = "-1" nuclear_pageflip = "N" panel_ignore_lid = "1" panel_use_ssc = "-1" prefault_disable = "N" reset = "2" vbt_firmware = "(null)" vbt_sdvo_panel_type = "-1" verbose_state_checks= "Y" dm@720S-13IKB:~$ uname -a Linux 720S-13IKB 4.18.0-12-generic #13-Ubuntu SMP Wed Nov 14 15:17:05 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux dm@720S-13IKB:~$ tlp-stat -s --- TLP 1.1 -------------------------------------------- +++ System Info System = LENOVO Lenovo ideapad 720S-13IKB 81A8 BIOS = 5SCN38WW Release = Ubuntu 18.10 Kernel = 4.18.0-12-generic #13-Ubuntu SMP Wed Nov 14 15:17:05 UTC 2018 x86_64 /proc/cmdline = BOOT_IMAGE=/vmlinuz-4.18.0-12-generic root=/dev/nvme0n1p3 ro quiet splash vt.handoff=1 Init system = systemd v239 Boot mode = UEFI Boot kubuntu 18.10 from legacy mode (MBR) - screen flicker, boot from EFI - no screen fliker. Hello again. Although I've got rid of the flickering/screen-tearing by booting with the "nomodeset" GRUB parameter (or i915.modeset=0), I wasn't fully satisfied with this solution as some options were no longer available (the missing brightness control and disabled suspend mode were the most annoying). After much digging around for a solution, and even updating the kernel to 4.19.0-041900.201810221809, the actual solution came from BIOS. The problem was SOLVED when I changed the Boot Mode from "Legacy support" (or something) to (only) UEFI. Dromichet I've been running UEFI only the whole time. I don't think this is related since turning on legacy support also breaks windows for me and linux doesn't get fixed on either UEFI/Legacy. Plus even the symptoms you were having are different. Yup! me too. I have been running UEFI too and therefore do not think it is related to this! Hello All! I got a bios update today when I was working on Windows.. When I logged back in, there was no flickering even after waking from a suspend. Could you folks please confirm if this was indeed an issue with the Lennovo BIOS. Regards, Sorry! False alarm... It is still flickering despite BIOS update... Hi, Was this issue resolved for anyone. I moved to kernel `Linux 4.20.6-042006-generic` and use `i915.fastboot=1` in my grub options but ubuntu 18.04 still flickers when it wakes up after lock or sleep. The above options do prevent it from flickering from the start but only after it has once gone to sleep (display turned off). Any help with this would be greatly appreciated. Thanks, Siddharth No, this is still an ongoing issue. Some people had luck with upgrading their BIOS, but me and many more still have the issue unfortunately. @Maintainers Is there anything additional Information I can supply to help with this issue? @Maarten, any further help here? Did anyone check with the new kernel(5) in ubuntu 19.04? Nothing changed, I assume that work will be done here before the fix is pushed. @Marteen I also tried to build the kernel with "constant_n = true;" and the flickering is still there. I do know that a laptop with the same display panel (Dell xps 9370) works perfectly fine under Linux. The panel is manufactured by AUO and is the B133ZAN01.1. (In reply to Mazin from comment #96) > Nothing changed, I assume that work will be done here before the fix is > pushed. > > @Marteen I also tried to build the kernel with "constant_n = true;" and the > flickering is still there. I do know that a laptop with the same display > panel (Dell xps 9370) works perfectly fine under Linux. The panel is > manufactured by AUO and is the B133ZAN01.1. Maarten, any further comments here? Ignore what I said earlier, the xps 13 model that uses the same panel is the xps 13 9380, and it seems to exhibit the same sort of flicker issue according to Bug 110511. Sorry! Created attachment 144358 [details]
dmesg from 5.1.4-arch1-1-ARCH with drm.debug=14
Adding a dmesg of my current kernel with fastboot enabled, 0-70s is the correct behaviour, after that its me closing the lid, waiting a bit and then opening it to a flickery display. Seems like the later part gets a lot of hotplug events etc, maybe a hint?
@Stan/Maarten, can you help here? Any further suggestions? Working (fastset at boot): [ 3.494890] [drm:intel_dump_pipe_config [i915]] dp m_n: lanes: 4; gmch_m: 6213395, gmch_n: 8388608, link_m: 517782, link_n: 524288, tu: 64 Broken (modeset): [ 192.531640] [drm:intel_dump_pipe_config [i915]] dp m_n: lanes: 4; gmch_m: 6213395, gmch_n: 8388608, link_m: 1035565, link_n: 1048576, tu: 64 in intel_dp.c: bool constant_n = drm_dp_has_quirk(&intel_dp->desc, DP_DPCD_QUIRK_CONSTANT_N); Replace with bool constant_n = true; And rebuild. Could you test if it works then? Created attachment 144365 [details]
dmesg with constant_n forced true
Unfortunately not. Attached dmesg from using the newly compiled kernel with the forced constant_n
Same thing happens to me, drops to the exact same wrong modeset after changing the bool value. (wrong modeset) dp m_n: lanes: 4; gmch_m: 24271, gmch_n: 32768, link_m: 32361, link_n: 32768, tu: 64 Oh well, worth a shot. Maarten, what are the next steps? I am having the same flickering problem with my Asus.Kernel is Kernel Linux 5.0.0-29-generic x86_64. I have a dual boot with windows where the problem is occurring as well. The flickering in windows lowers down (but does not stop) from insane levels if I disable the Intel graphics in display adapters option in Device manager. Any comments? (In reply to Ashish Maknikar from comment #106) > I am having the same flickering problem with my Asus.Kernel is Kernel Linux > 5.0.0-29-generic x86_64. I have a dual boot with windows where the problem > is occurring as well. The flickering in windows lowers down (but does not > stop) from insane levels if I disable the Intel graphics in display adapters > option in Device manager. Any comments? Can you verify the issue with drmtip (https://cgit.freedesktop.org/drm-tip) and attach the dmesg from boot with kernel parameters drm.debug=0x1e log_buf_len=4M? (In reply to Lakshmi from comment #107) > (In reply to Ashish Maknikar from comment #106) > > I am having the same flickering problem with my Asus.Kernel is Kernel Linux > > 5.0.0-29-generic x86_64. I have a dual boot with windows where the problem > > is occurring as well. The flickering in windows lowers down (but does not > > stop) from insane levels if I disable the Intel graphics in display adapters > > option in Device manager. Any comments? > > Can you verify the issue with drmtip (https://cgit.freedesktop.org/drm-tip) > and attach the dmesg from boot with kernel parameters drm.debug=0x1e > log_buf_len=4M? I dont have enough memory(dual boot partition) and it is my only system which is flickering but stops after a while.. I observed the following on dmesg : [drm] HPD interrupt storm detected on connector eDP-1: switching from hotplug detection to polling when the screen blacks out and flickering stops if it helps. can someone explain the terms. commit f0521558a2a8 ("drm/i915: Don't clobber M/N values during fastset check") may have helped here.
Looks like that one should be in 5.1.15+ or 5.2+. What's the most recent kernel people have tried here?
I tried kernel 5.3.7, screen still exhibits the same issue with flickering on lenovo ideapad 720s 13ikb. Same issue with Ideapad 720s tested with the latest Ubuntu 19.10. I don't get flashing on boot, but when the computer wakes up from sleep mode it starts flashing and after 1 min or 2 the computer hangs. -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/intel/issues/166. |
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.