From: Ronald Warsow <rwarsow@gmx.de>
To: Greg KH <greg@kroah.com>
Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5.11 000/306] 5.11.7-rc1 review
Date: Tue, 16 Mar 2021 15:38:39 +0100 [thread overview]
Message-ID: <7874700a-694e-d85f-71c6-731e89832da9@gmx.de> (raw)
In-Reply-To: <YFCrUP3TPqVK57E9@kroah.com>
On 16.03.21 13:57, Greg KH wrote:
> On Tue, Mar 16, 2021 at 01:34:31PM +0100, Ronald Warsow wrote:
...
>>
>> bug/error (since 5.11.1 or 2):
>>
>> i915 0000:00:02.0: [drm] *ERROR* mismatch in DDB state pipe A plane 1
>> (expected (0,0), found (0,446))
>
> What is the commit id here for the fix that you are looking for?
>
> thanks,
>
> greg k-h
>
sorry, I do not have an commit id.
*An* error report is here:
https://gitlab.freedesktop.org/drm/intel/-/issues/2708
and the fix:
sh*t, I searched and found it yesterday somewhere here:
https://cgit.freedesktop.org/drm-intel/
but can't find it anymore now.
Aaarrggghhh !
IIRC, it seemed to me that a fix regarding the error in(?)
./drivers/gpu/drm/i915/display/intel_display.c:
was ~queued~ in one of the *next* or *fixes*
I've no idea which *next* or *fixes* will when go into stable or maybe
5.12...
sorry, I can't help here much
--
regards
Ronald
next prev parent reply other threads:[~2021-03-16 14:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-16 12:34 [PATCH 5.11 000/306] 5.11.7-rc1 review Ronald Warsow
2021-03-16 12:57 ` Greg KH
2021-03-16 14:38 ` Ronald Warsow [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-03-15 13:51 gregkh
2021-03-15 17:07 ` Jon Hunter
2021-03-15 22:57 ` Jason Self
2021-03-16 5:15 ` Naresh Kamboju
2021-03-19 9:50 ` Greg Kroah-Hartman
2021-03-16 21:14 ` Guenter Roeck
2021-03-19 9:42 ` Greg KH
2021-03-17 3:03 ` Ross Schmidt
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=7874700a-694e-d85f-71c6-731e89832da9@gmx.de \
--to=rwarsow@gmx.de \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.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).