dri-devel.lists.freedesktop.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 12:26:56 +0100	[thread overview]
Message-ID: <c9bae016-413f-0db9-c9ee-d6f39d24a6ab@suse.de> (raw)
In-Reply-To: <c01d2d95f1e64be984cff71e7bdf1c84@AcuMS.aculab.com>


[-- Attachment #1.1.1.1: Type: text/plain, Size: 2481 bytes --]

Hi

Am 20.11.20 um 11:51 schrieb David Laight:
> From: Thomas Zimmermann
>> Sent: 20 November 2020 10:14
> ...
>>> Is there any way to bisect through the parts of the
>>> drm merge patch into v5.10-rc1 ?
>>>
>>> That ought to be quicker (and less error prone) than
>>> the bisect builds I was doing.
>>>
>>> Note that the stack 'splat' is due to a later change.
>>> It is separate from the broken pixel alignment.
>>>
>>> I actually saw the vga text go 'funny' while the boot
>>> was outputting all the [OK] messages (from systemd?)
>>> before the graphic login stole tty1 (bloody stupid
>>> to use tty1).
>>>
>>> I don't need to use the failing system today, I'll
>>> have another go at isolating the failure.
>>
>> 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.

Best regards
Thomas

> 
>> I have two systems with AST chips and neither shows any of the symptoms
>> you describe; nor do we have such reports about drivers that use a
>> similar stack (hibmc, bochs). Could you provide the output of
>>
>>     dmesg | grep drm
> 
> [    2.112303] fb0: switching to astdrmfb from EFI VGA
> [    2.120222] ast 0000:02:00.0: [drm] Using P2A bridge for configuration
> [    2.120233] ast 0000:02:00.0: [drm] AST 2400 detected
> [    2.120247] ast 0000:02:00.0: [drm] Analog VGA only
> [    2.120257] ast 0000:02:00.0: [drm] dram MCLK=408 Mhz type=1 bus_width=16
> [    2.121121] [drm] Initialized ast 0.1.0 20120228 for 0000:02:00.0 on minor 0
> [    2.125838] fbcon: astdrmfb (fb0) is primary device
> [    2.152179] ast 0000:02:00.0: [drm] fb0: astdrmfb frame buffer device
> [    6.061034] systemd[1]: Condition check resulted in Load Kernel Module drm being skipped.
> 
> The output is the same for both good and bad kernels.
> 
> 	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.1.2: OpenPGP_0x680DC11D530B7A23.asc --]
[-- Type: application/pgp-keys, Size: 7535 bytes --]

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

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2020-11-20 11:27 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 [this message]
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
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=c9bae016-413f-0db9-c9ee-d6f39d24a6ab@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).