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>
Subject: Re: [REGRESSION][BISECTED] Screen goes blank with ASpeed AST2300 in 6.18-rc2
Date: Wed, 22 Oct 2025 08:51:30 +0200 [thread overview]
Message-ID: <43992c88-3a3a-4855-9f46-27a7e5fdec2e@suse.de> (raw)
In-Reply-To: <a40caf8e-58ad-4f9c-af7f-54f6f69c29bb@googlemail.com>
[-- Attachment #1: Type: text/plain, Size: 2618 bytes --]
Hi
Am 22.10.25 um 05:27 schrieb Peter Schneider:
> #regzbot introduced: 6f719373b943a955fee6fc2012aed207b65e2854
>
> Hi all,
>
> I have encountered a serious (for me) regression with 6.18-rc2 on my
> 2-socket Ivy Bridge Xeon E5-2697 v2 server. After booting, my console
> screen goes blank and stays blank. 6.18-rc1 was still fine.
>
> The machine has an Asus Z9PE-D16 server mainboard with an onboard
> ASpeed AST2300 VGA chip with 16MB VRAM. I have attached an older HP
> Monitor to it via old VGA jack/cable. It also has a second graphics
> card in a PCI-E slot; an older NVidia GTX 560. It is not connected to
> a monitor, but I have configured it via kernel command line for
> PCI-pass-through to VMs running on this server (I use Proxmox VE, i.e.
> QEMU/KVM virtual machines). Currently, no VMs use this yet, and also
> no VMs are autostarting with machine boot. So when this regression
> occurs, the server is idle. Pressing a key on the keyboard does not
> make the screen come alive. The server is running fine though, and I
> can access it via SSH. It just has no graphic output anymore. In case
> this is important, the machine also has a ASMB6 BMC (can be used via
> http).
>
> I have attached dmesg output from both 6.18-rc1 which is fine, and
> 6.18-rc2 which exhibits this bug. I have bisected the issue, please
> see attached git bisect.log.
Thanks for the detailed bug report.
Attached is a patch that partially reverts the broken commit. Could you
please apply it on top of the broken kernel and report on the results?
Best regards
Thomas
>
> The bad commit is
>
> commit 6f719373b943a955fee6fc2012aed207b65e2854
> Author: Thomas Zimmermann <tzimmermann@suse.de>
> Date: Tue Oct 14 10:46:34 2025 +0200
>
> drm/ast: Blank with VGACR17 sync enable, always clear VGACRB6 sync
> off
>
> Blank the display by disabling sync pulses with VGACR17<7>. Unblank
> by reenabling them. This VGA setting should be supported by all
> Aspeed
> hardware.
>
> When I revert this from 6.18-rc2, the issue goes away and my console
> screen works again.
>
> I just saw that Greg just yesterday evening included the offending
> patch already in stable RCs 6.12.55-rc1 and 6.17.5-rc1, so I'll test
> these seperately and send a mail to the stable mailing list, too, if
> affected (which I anticipate).
>
> 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)
[-- Attachment #2: 0001-ast-Set-clear-screen-disable-bit.patch --]
[-- Type: text/x-patch, Size: 1714 bytes --]
From 5fdea2e9936a49905902e339e627a27b0ab0a884 Mon Sep 17 00:00:00 2001
From: Thomas Zimmermann <tzimmermann@suse.de>
Date: Wed, 22 Oct 2025 08:48:49 +0200
Subject: [PATCH] ast: Set/clear screen-disable bit
---
drivers/gpu/drm/ast/ast_mode.c | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/drivers/gpu/drm/ast/ast_mode.c b/drivers/gpu/drm/ast/ast_mode.c
index 9ce874dba69c..b73437083dbf 100644
--- a/drivers/gpu/drm/ast/ast_mode.c
+++ b/drivers/gpu/drm/ast/ast_mode.c
@@ -820,6 +820,7 @@ ast_crtc_helper_atomic_flush(struct drm_crtc *crtc,
static void ast_crtc_helper_atomic_enable(struct drm_crtc *crtc, struct drm_atomic_state *state)
{
struct ast_device *ast = to_ast_device(crtc->dev);
+ u8 vgasr1 = 0xff;
u8 vgacr17 = 0x00;
u8 vgacrb6 = 0xff;
@@ -828,6 +829,9 @@ static void ast_crtc_helper_atomic_enable(struct drm_crtc *crtc, struct drm_atom
ast_set_index_reg_mask(ast, AST_IO_VGACRI, 0x17, 0x7f, vgacr17);
ast_set_index_reg_mask(ast, AST_IO_VGACRI, 0xb6, 0xfc, vgacrb6);
+
+ vgasr1 &= ~AST_IO_VGASR1_SD;
+ ast_set_index_reg_mask(ast, AST_IO_VGASRI, 0x01, 0xdf, vgasr1);
}
static void ast_crtc_helper_atomic_disable(struct drm_crtc *crtc, struct drm_atomic_state *state)
@@ -835,6 +839,10 @@ static void ast_crtc_helper_atomic_disable(struct drm_crtc *crtc, struct drm_ato
struct drm_crtc_state *old_crtc_state = drm_atomic_get_old_crtc_state(state, crtc);
struct ast_device *ast = to_ast_device(crtc->dev);
u8 vgacr17 = 0xff;
+ u8 vgasr1 = 0x00;
+
+ vgasr1 |= AST_IO_VGASR1_SD;
+ ast_set_index_reg_mask(ast, AST_IO_VGASRI, 0x01, 0xdf, vgasr1);
vgacr17 &= ~AST_IO_VGACR17_SYNC_ENABLE;
ast_set_index_reg_mask(ast, AST_IO_VGACRI, 0x17, 0x7f, vgacr17);
--
2.51.0
next prev parent reply other threads:[~2025-10-22 6:51 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 ` Thomas Zimmermann [this message]
2025-10-22 8:08 ` [REGRESSION][BISECTED] Screen goes blank with ASpeed AST2300 in 6.18-rc2 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
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=43992c88-3a3a-4855-9f46-27a7e5fdec2e@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@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®