linux-kernel - Re: [REGRESSION][BISECTED] Screen goes blank with ASpeed AST2300 in 6.18-rc2

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <329a9f97-dd66-49c2-bc42-470566d01539@suse.de>
Date: Thu, 23 Oct 2025 14:46:50 +0200
From: Thomas Zimmermann <tzimmermann@...e.de>
To: Peter Schneider <pschneider1968@...glemail.com>,
 regressions@...ts.linux.dev, LKML <linux-kernel@...r.kernel.org>
Cc: dri-devel@...ts.freedesktop.org, stable@...r.kernel.org,
 jfalempe@...hat.com, airlied@...hat.com, dianders@...omium.org,
 nbowler@...conx.ca, Linus Torvalds <torvalds@...ux-foundation.org>,
 Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
 Thorsten Leemhuis <regressions@...mhuis.info>
Subject: Re: [REGRESSION][BISECTED] Screen goes blank with ASpeed AST2300 in
 6.18-rc2

Hi

Am 22.10.25 um 13:23 schrieb Peter Schneider:
> 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).

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?

Best regards
Thomas


>
> Beste Grüße,
> Peter Schneider
>

-- 
--
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)


View attachment "0001-ast-clear-preserved-bits-from-output-value.patch" of type "text/x-patch" (1198 bytes)