From: Thomas Zimmermann <tzimmermann@suse.de>
To: Peter Schneider <pschneider1968@googlemail.com>,
regressions@lists.linux.dev, LKML <linux-kernel@vger.kernel.org>
Cc: dri-devel@lists.freedesktop.org, stable@vger.kernel.org,
jfalempe@redhat.com, airlied@redhat.com, dianders@chromium.org,
nbowler@draconx.ca,
Linus Torvalds <torvalds@linux-foundation.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Thorsten Leemhuis <regressions@leemhuis.info>
Subject: Re: [REGRESSION][BISECTED] Screen goes blank with ASpeed AST2300 in 6.18-rc2
Date: Thu, 23 Oct 2025 14:50:05 +0200 [thread overview]
Message-ID: <83945039-afb4-4cd3-b29c-e4fd5c757a95@suse.de> (raw)
In-Reply-To: <329a9f97-dd66-49c2-bc42-470566d01539@suse.de>
>
> I've been able to reproduce the problem with an AST2300 test system.
> The attached patch fixes the problem for me. Can you please test and
> report on the results?
On pure -rc2 without previous patches applied.
--
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Frankenstrasse 146, 90461 Nuernberg, Germany
GF: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman
HRB 36809 (AG Nuernberg)
next prev parent reply other threads:[~2025-10-23 12:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251014084743.18242-1-tzimmermann@suse.de>
2025-10-22 3:27 ` [REGRESSION][BISECTED] Screen goes blank with ASpeed AST2300 in 6.18-rc2 (was: Re: [PATCH v2] drm/ast: Blank with VGACR17 sync enable, always clear VGACRB6 sync off) Peter Schneider
2025-10-22 6:51 ` [REGRESSION][BISECTED] Screen goes blank with ASpeed AST2300 in 6.18-rc2 Thomas Zimmermann
2025-10-22 8:08 ` Peter Schneider
2025-10-22 9:11 ` Thomas Zimmermann
2025-10-22 9:16 ` Peter Schneider
2025-10-22 10:20 ` Thomas Zimmermann
2025-10-22 11:23 ` Peter Schneider
2025-10-23 12:46 ` Thomas Zimmermann
2025-10-23 12:50 ` Thomas Zimmermann [this message]
2025-10-23 19:11 ` Peter Schneider
2025-10-24 5:34 ` Peter Schneider
2025-10-24 6:15 ` 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=83945039-afb4-4cd3-b29c-e4fd5c757a95@suse.de \
--to=tzimmermann@suse.de \
--cc=airlied@redhat.com \
--cc=dianders@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=jfalempe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nbowler@draconx.ca \
--cc=pschneider1968@googlemail.com \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.kernel.org \
--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
all inboxes | Powered by JetHome®