From: Peter Schneider <pschneider1968@googlemail.com>
To: Thomas Zimmermann <tzimmermann@suse.de>,
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: Wed, 22 Oct 2025 13:23:25 +0200 [thread overview]
Message-ID: <3ca10b2e-fb9c-4495-9219-5e8537314751@googlemail.com> (raw)
In-Reply-To: <e2462c92-4049-486b-92d7-e78aaec4b05d@suse.de>
Am 22.10.2025 um 12:20 schrieb Thomas Zimmermann:
> Hi
>
> Am 22.10.25 um 11:16 schrieb Peter Schneider:
>> Am 22.10.2025 um 11:11 schrieb Thomas Zimmermann:
>>> Hi
>>>
>>> Am 22.10.25 um 10:08 schrieb Peter Schneider:
>>>>
>>>> Your patch applied cleanly against 6.18-rc2 and the kernel built fine, but unfortunately it did not solve the issue:
>>>> my console screen stays blank after booting. This is regardless whether I do a soft reboot, press the reset button
>>>> or power cycle and do a cold boot. They are all the same.
>>>
>>> Just to be sure: you do see output at the early boot stages (BIOS, boot loader). It's at some later point during
>>> boot, the driver loads and the display blanks out?
>>
>> Yes, that's correct.
>>
>>> There's another patch attached. does this make a difference?
>>
>> Do I have to apply that against base 6.18-rc2 or against 6.18-rc2 + your previous patch?
>
> Base 6.18-rc2. All the patches are against this.
So with this new patch against 6.18-rc2, I first got this build error:
CC [M] drivers/gpu/drm/ast/ast_mode.o
drivers/gpu/drm/ast/ast_mode.c: In function ‘ast_crtc_helper_atomic_disable’:
drivers/gpu/drm/ast/ast_mode.c:857:12: error: unused variable ‘vgacr17’ [-Werror=unused-variable]
857 | u8 vgacr17 = 0xff;
| ^~~~~~~
cc1: all warnings being treated as errors
because I always do my kernel builds with CONFIG_WERROR=y. So then I commented out the now superfluous declaration in
line 857 and the build succeeded. However, unfortunately the issue still persists. The screen still gets blanked on
reboot (as clarified before, after BIOS/POST messages, Grub boot menu, initial boot messages).
Beste Grüße,
Peter Schneider
--
Climb the mountain not to plant your flag, but to embrace the challenge,
enjoy the air and behold the view. Climb it so you can see the world,
not so the world can see you. -- David McCullough Jr.
OpenPGP: 0xA3828BD796CCE11A8CADE8866E3A92C92C3FF244
Download: https://www.peters-netzplatz.de/download/pschneider1968_pub.asc
https://keys.mailvelope.com/pks/lookup?op=get&search=pschneider1968@googlemail.com
https://keys.mailvelope.com/pks/lookup?op=get&search=pschneider1968@gmail.com
next prev parent reply other threads:[~2025-10-22 11:23 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 [this message]
2025-10-23 12:46 ` Thomas Zimmermann
2025-10-23 12:50 ` Thomas Zimmermann
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=3ca10b2e-fb9c-4495-9219-5e8537314751@googlemail.com \
--to=pschneider1968@googlemail.com \
--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=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=tzimmermann@suse.de \
/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