dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Stein <himbeere@meine-oma.de>
To: Oleksandr Natalenko <oleksandr@natalenko.name>
Cc: David Airlie <airlied@linux.ie>,
	Lucas De Marchi <lucas.demarchi@intel.com>,
	linux-kernel@vger.kernel.org,
	Manasi Navare <manasi.d.navare@intel.com>,
	Kai-Heng Feng <kai.heng.feng@canonical.com>,
	Sean Paul <seanpaul@chromium.org>,
	dri-devel@lists.freedesktop.org,
	Rodrigo Vivi <rodrigo.vivi@intel.com>,
	Ankit Nautiyal <ankit.k.nautiyal@intel.com>,
	intel-gfx@lists.freedesktop.org
Subject: Re: thinkpad x1 carbon display flickering after update to 5.12. good on 5.11.x (i915)
Date: Fri, 14 May 2021 15:44:51 +0200	[thread overview]
Message-ID: <e41eba8500f731c979340fd810da203f@meine-oma.de> (raw)
In-Reply-To: <20210514123431.fqvaa437zlw7rq7j@spock.localdomain>


Yes, it does indeed! No flicker anymore. Thanks and cheers!

On 2021-05-14 14:34, Oleksandr Natalenko wrote:
> Hello.
> 
> On Fri, May 14, 2021 at 10:24:26AM +0200, Thomas Stein wrote:
>> After upgrading to linux 5.12 the display on my X1 Carbon Gen 2 starts 
>> to
>> flicker. Well actually it seems to turn off and on again and again. 
>> Here a
>> link to a video a person posted who has the same issue as me 
>> obviousely. 
>> https://linuxove.com/thinkpad-x1-carbon-gen-3-display-flickering-on-linux-kernel-5-12/
>> 
>> This happens without having Xorg running too. So it can't be related 
>> to
>> Xorg. The kernel boots and after a few seconds, the kernel messages 
>> scoll
>> through, the flickering starts. Nothing special in dmesg.
>> 
>> dmesg:
>> 
>> himbeere@rather ~ $ dmesg | grep i915
>> [    0.713595] i915 0000:00:02.0: vgaarb: deactivate vga console
>> [    0.720280] i915 0000:00:02.0: vgaarb: changed VGA decodes:
>> olddecodes=io+mem,decodes=io+mem:owns=io+mem
>> [    0.741494] i915 0000:00:02.0: [drm] Panel advertises DPCD 
>> backlight
>> support, but VBT disagrees. If your backlight controls don't work try
>> booting with i915.enable_dpcd_backlight=1. If your machine needs this,
>> please file a _new_ bug report on drm/i915, see
>> https://gitlab.freedesktop.org/drm/intel/-/wikis/How-to-file-i915-bugs 
>> for
>> details.
>> [    1.864837] [drm] Initialized i915 1.6.0 20201103 for 0000:00:02.0 
>> on
>> minor 0
>> [    1.875907] fbcon: i915drmfb (fb0) is primary device
>> [    3.158255] i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer 
>> device
>> himbeere@rather ~ $
>> 
>> Downgrading to 5.11 solves the issue for me. Any ideas?
> 
> Does [1] fix your issue?
> 
> [1] 
> https://cgit.freedesktop.org/drm-tip/patch/?id=acca7762eb71bc05a8f28d29320d193150051f79

      reply	other threads:[~2021-05-15 13:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1a6cf0a3dc8a2c6364265ad7249b76b1@meine-oma.de>
2021-05-14 12:34 ` thinkpad x1 carbon display flickering after update to 5.12. good on 5.11.x (i915) Oleksandr Natalenko
2021-05-14 13:44   ` Thomas Stein [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e41eba8500f731c979340fd810da203f@meine-oma.de \
    --to=himbeere@meine-oma.de \
    --cc=airlied@linux.ie \
    --cc=ankit.k.nautiyal@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=kai.heng.feng@canonical.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lucas.demarchi@intel.com \
    --cc=manasi.d.navare@intel.com \
    --cc=oleksandr@natalenko.name \
    --cc=rodrigo.vivi@intel.com \
    --cc=seanpaul@chromium.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).