mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Zimmermann <tzimmermann@suse.de>
To: Nick Bowler <nbowler@draconx.ca>
Cc: Doug Anderson <dianders@chromium.org>,
	linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
	regressions@lists.linux.dev
Subject: Re: PROBLEM: AST2500 BMC video output disabled by reboot (regression)
Date: Thu, 18 Sep 2025 12:46:04 +0200	[thread overview]
Message-ID: <2d62f7a1-712f-4868-8e21-e2d5b616c43a@suse.de> (raw)
In-Reply-To: <cox6kpackepnunrlhpsssvgdmjd24477cc7mide52xptmmoxyr@ijjotb3xju3v>

Hi

Am 18.09.25 um 04:04 schrieb Nick Bowler:
> On Wed, Sep 17, 2025 at 11:14:45AM -0400, Nick Bowler wrote:
>> On Fri, Aug 29, 2025 at 03:07:14PM +0200, Thomas Zimmermann wrote:
>>> The ast driver doesn't do much during shutdown. Could you please out-comment
>>> the lines at either [2] xor [3] and report on either effect? These calls
>>> turn of the video chip's memory access and sync pulses. Not doing that might
>>> resolve the problem.
>>>
>>> [2] https://elixir.bootlin.com/linux/v6.16.3/source/drivers/gpu/drm/ast/ast_mode.c#L835
>>> [3] https://elixir.bootlin.com/linux/v6.16.3/source/drivers/gpu/drm/ast/ast_mode.c#L839
>> I can try this.
> OK, I tested 6.17-rc6 and reproduced the problem on this version.  Then:
>
>    - Deleting [2] (only) appears to make no difference whatsoever. That
>      is, deleting the following line in ast_mode.c:
>
>        ast_set_index_reg_mask(ast, AST_IO_VGASRI, 0x01, 0xdf, AST_IO_VGASR1_SD);
>
>    - Deleting [3] (only) appears sufficient to make things work again,
>      that is, deleting the following line in ast_mode.c:
>
>        ast_set_index_reg_mask(ast, AST_IO_VGACRI, 0xb6, 0xfc, vgacrb6);

Great, thanks for testing! I'll see if i can make a workaround for your 
system.

Could you please provide me with 'lspci -nvv' of the device?

Best regards
Thomas

>
> Thanks,
>    Nick

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



  reply	other threads:[~2025-09-18 10:46 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-21  4:26 Nick Bowler
2025-04-28 20:40 ` Doug Anderson
2025-04-30 13:28   ` Nick Bowler
2025-04-30 17:05     ` Doug Anderson
2025-04-30 17:52       ` Nick Bowler
2025-04-30 23:31         ` Doug Anderson
2025-08-29 13:07     ` Thomas Zimmermann
2025-09-17 15:14       ` Nick Bowler
2025-09-18  2:04         ` Nick Bowler
2025-09-18 10:46           ` Thomas Zimmermann [this message]
2025-09-18 11:17           ` Thomas Zimmermann
2025-10-01  7:26             ` Thomas Zimmermann
2025-10-04  0:31               ` Nick Bowler
2025-10-07  8:51                 ` Thomas Zimmermann
2025-10-09 23:56                   ` Nick Bowler
2025-10-10  7:10                     ` Thomas Zimmermann
2025-09-17  9:22 ` 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=2d62f7a1-712f-4868-8e21-e2d5b616c43a@suse.de \
    --to=tzimmermann@suse.de \
    --cc=dianders@chromium.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nbowler@draconx.ca \
    --cc=regressions@lists.linux.dev \
    /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®