From: "François Valenduc" <francoisvalenduc@gmail.com>
To: "Saarinen, Jani" <jani.saarinen@intel.com>,
Jani Nikula <jani.nikula@linux.intel.com>,
"Lisovskiy, Stanislav" <stanislav.lisovskiy@intel.com>
Cc: "intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: [Intel-gfx] commit 15512021eb3975a8c2366e3883337e252bb0eee5 causes white spots in console screens
Date: Thu, 14 Apr 2022 15:25:01 +0200 [thread overview]
Message-ID: <cb017f97-bf6a-191b-d12b-14bcf91c84dd@gmail.com> (raw)
In-Reply-To: <DM8PR11MB56557E53CB85DD86A4F21A21E0EF9@DM8PR11MB5655.namprd11.prod.outlook.com>
Le 14/04/22 à 11:51, Saarinen, Jani a écrit :
>
>> -----Original Message-----
>> From: Intel-gfx <intel-gfx-bounces@lists.freedesktop.org> On Behalf Of Jani
>> Nikula
>> Sent: torstai 14. huhtikuuta 2022 11.32
>> To: François Valenduc <francoisvalenduc@gmail.com>; Lisovskiy, Stanislav
>> <stanislav.lisovskiy@intel.com>
>> Cc: intel-gfx@lists.freedesktop.org; dri-devel@lists.freedesktop.org
>> Subject: Re: [Intel-gfx] commit 15512021eb3975a8c2366e3883337e252bb0eee5
>> causes white spots in console screens
>>
>> On Thu, 14 Apr 2022, François Valenduc <francoisvalenduc@gmail.com> wrote:
>>> Le 14/04/22 à 10:03, Lisovskiy, Stanislav a écrit :
>>>> On Thu, Apr 14, 2022 at 08:33:35AM +0200, François Valenduc wrote:
>>>>> Le 14/04/22 à 08:31, Lisovskiy, Stanislav a écrit :
>>>>>> On Wed, Apr 13, 2022 at 08:12:20PM +0300, Jani Nikula wrote:
>>>>>>> On Wed, 13 Apr 2022, François Valenduc <francoisvalenduc@gmail.com>
>> wrote:
>>>>>>>> Commit 15512021eb3975a8c2366e3883337e252bb0eee5
>>>>>>>> (15512021eb3975a8c2366e3883337e252bb0eee5) causes a lof of white
>>>>>>>> spots to appears on the right upper corner of all console screens
>>>>>>>> (see
>> https://drive.google.com/file/d/13GabEvOIKSAj5yox6ybAZEDu3Ixncw5Q/view).
>>>>>>>> git-bisect shows that this is the offending commit and if I
>>>>>>>> revert it, the problem goes away. The problem still occurs with
>>>>>>>> kernel 5.18-rc2 and to all stable trees where it was applied.
>>>>>>>> Can somebody explains what happens ?
>>>>>>>>
>>>>>>>> The video card is the following: VGA compatible controller: Intel
>>>>>>>> Corporation WhiskeyLake-U GT2 [UHD Graphics 620] (rev 02)
>>>>>>>> (prog-if 00 [VGA controller])
>>>>>>>>
>>>>>>>> Please tell me if you need more info.
>>>>>>> That's commit 15512021eb39 ("drm/i915: Workaround broken BIOS DBUF
>>>>>>> configuration on TGL/RKL"), adding Cc's.
>>>>>>>
>>>>>>> Please file a report at fdo gitlab [1] and attach dmesg etc. there.
>>>>>> That commit looks like it is just disabling all the planes, if
>>>>>> wrong dbuf/wm configuration is detected.
>>>>>> However it should do that only once during boot as I understand.
>>>>>>
>>>>>> Are you sure that is exactly this commit which is causing this?
>>>>>> Does the issue appear always?
>>>>>>
>>>>>> Ville Syrjälä, thoughts?
>>>>>>
>>>>>> Stan
>>>>>>
>>>>>>> Thanks,
>>>>>>> Jani.
>>>>>>>
>>>>>>>
>>>>>>> [1]
>>>>>>> https://gitlab.freedesktop.org/drm/intel/wikis/How-to-file-i915-bu
>>>>>>> gs
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Jani Nikula, Intel Open Source Graphics Center
>>>>> As I said, git-bisect shows it's the offending commit and if I
>>>>> revert it, the problem doesn't happens. Otherwise, it always occurs.
>>>>>
>>>>> François
>>>>>
>>>> Does it just happen all the time or some steps/certain circumstances
>>>> needed for it to happen?
>>>>
>>>> Only suspicion after looking briefly is that once suspend/resume is
>>>> done it might be messing something up. Just a quick guess..
>>>>
>>>> Stan
>>> It occurs permantently as soon as I boot my computer.
>> I'd appreciate that bug being filed, and the discussion moved there, so all the
>> details and history are in one place.
> Agree.
>
>> Thanks,
>> Jani.
>>
>>
>> --
>> Jani Nikula, Intel Open Source Graphics Center
As requested, I filled a bug on freedesktop
(https://gitlab.freedesktop.org/drm/intel/-/issues/5711)
prev parent reply other threads:[~2022-04-14 13:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-13 10:15 commit 15512021eb3975a8c2366e3883337e252bb0eee5 causes white spots in console screens François Valenduc
2022-04-13 17:12 ` [Intel-gfx] " Jani Nikula
2022-04-13 17:12 ` Jani Nikula
2022-04-14 6:31 ` [Intel-gfx] " Lisovskiy, Stanislav
2022-04-14 6:31 ` Lisovskiy, Stanislav
2022-04-14 6:33 ` François Valenduc
2022-04-14 8:03 ` [Intel-gfx] " Lisovskiy, Stanislav
2022-04-14 8:03 ` Lisovskiy, Stanislav
2022-04-14 8:04 ` François Valenduc
2022-04-14 8:31 ` [Intel-gfx] " Jani Nikula
2022-04-14 8:31 ` Jani Nikula
2022-04-14 9:51 ` [Intel-gfx] " Saarinen, Jani
2022-04-14 9:51 ` Saarinen, Jani
2022-04-14 13:25 ` François Valenduc [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=cb017f97-bf6a-191b-d12b-14bcf91c84dd@gmail.com \
--to=francoisvalenduc@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=jani.saarinen@intel.com \
--cc=stanislav.lisovskiy@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.