linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Zimmermann <tzimmermann@suse.de>
To: David Laight <David.Laight@ACULAB.COM>,
	Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Daniel Vetter" <daniel.vetter@ffwll.ch>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	"Huang, Ray" <ray.huang@amd.com>,
	"Dave Airlie" <airlied@redhat.com>,
	"Christian König" <christian.koenig@amd.com>
Subject: Re: Linux 5.10-rc4; graphics alignment
Date: Fri, 20 Nov 2020 14:41:42 +0100	[thread overview]
Message-ID: <7d42ee6b-d72b-9f4d-21fe-4f5981eb425e@suse.de> (raw)
In-Reply-To: <ec3130c3d22a4d4dafe020d30fd224cd@AcuMS.aculab.com>


[-- Attachment #1.1.1: Type: text/plain, Size: 2468 bytes --]

Hi

Am 20.11.20 um 13:53 schrieb David Laight:
> From: Thomas Zimmermann
>> Sent: 20 November 2020 12:30
>>
>> Am 20.11.20 um 12:45 schrieb David Laight:
>>> From: Thomas Zimmermann
>>>> Sent: 20 November 2020 11:27
>>> ...
>>>>>> You can use drm-tip for testing, where many of the DRM patches go through.
>>>>>>
>>>>>>       https://cgit.freedesktop.org/drm/drm-tip/
>>>>>>
>>>>>> It's fairly up-to-date.
>>>>>
>>>>> Any idea of tags either side of the 5.10 merge?
>>>>
>>>> The final commit before v5.9 appears to be
>>>>
>>>>      Fixes: 33c8256b3bcc ("drm/amd/display: Change ABM config init interface")
>>>>
>>>> I'd try this as a good commit. For the bad commit, just try HEAD.
>>>
>>> HEAD off that tree works.
>>> Colours ok and no stack backtrace.
>>>
>>> Ideas??
>>
>> The good news is that it's been fixed. All you have to do is wait for
>> the fix to hit upstream.
>>
>> Did you try the patch that Dave linked?
> 
> That patch makes no difference to my system.
> The condition is false so it doesn't corrupt the flags.
> (I printed the values to see.)

I see, so it's probably something else that has been fixed in drm-tip. 
It's likely that at least one commit in drm-tip is also broken. I'd try 
to find one of these. One idea is to go through the commits that went 
into the related files. Maybe go back to the HEAD of drm-tip and try 
something like

   git log --oneline -- drivers/gpu/drm/ast/ 
drivers/gpu/drm/drm_gem_vram_helper.c drivers/gpu/drm/ttm/

That lists recent ast and memory-management commits. One of them might 
be broken and can serve an a starting point for a bisect.

I did a diff from v5.10-rc4 to drm-tip to look for suspicious changes. 
Some candidates are

   8e3784dfef8a ("drm/ast: Reload gamma LUT after changing primary 
plane's color format")
   2b8283ff1a60 ("drm/vram_helper: implement a ttm move callback.")
   6a6e5988a265 ("drm/ttm: replace last move_notify with delete_mem_notify")

I'd test them against their parent commits to see if anything changes.

Thanks for all your efforts!

Best regards
Thomas

> 
> 	David
> 
> -
> Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
> Registration No: 1397386 (Wales)
> 

-- 
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5, 90409 Nürnberg, Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Felix Imendörffer

[-- Attachment #1.1.2: OpenPGP_0x680DC11D530B7A23.asc --]
[-- Type: application/pgp-keys, Size: 7535 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

  reply	other threads:[~2020-11-20 13:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-20  9:52 Linux 5.10-rc4; graphics alignment David Laight
2020-11-20 10:13 ` Thomas Zimmermann
2020-11-20 10:51   ` David Laight
2020-11-20 11:26     ` Thomas Zimmermann
2020-11-20 11:45       ` David Laight
2020-11-20 12:30         ` Thomas Zimmermann
2020-11-20 12:53           ` David Laight
2020-11-20 13:41             ` Thomas Zimmermann [this message]
2020-11-20 15:39               ` David Laight
2020-11-24 16:27                 ` David Laight
2020-11-25  7:53                   ` Thomas Zimmermann
2020-11-25  8:25                   ` Thomas Zimmermann

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=7d42ee6b-d72b-9f4d-21fe-4f5981eb425e@suse.de \
    --to=tzimmermann@suse.de \
    --cc=David.Laight@ACULAB.COM \
    --cc=airlied@redhat.com \
    --cc=christian.koenig@amd.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ray.huang@amd.com \
    --cc=torvalds@linux-foundation.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).