mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Zimmermann <tzimmermann@suse.de>
To: Nick Bowler <nbowler@draconx.ca>,
	linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
	regressions@lists.linux.dev
Cc: Douglas Anderson <dianders@chromium.org>
Subject: Re: PROBLEM: AST2500 BMC video output disabled by reboot (regression)
Date: Wed, 17 Sep 2025 11:22:22 +0200	[thread overview]
Message-ID: <b0cbc791-a209-4756-acf0-e869888294ac@suse.de> (raw)
In-Reply-To: <wpwd7rit6t4mnu6kdqbtsnk5bhftgslio6e2jgkz6kgw6cuvvr@xbfswsczfqsi>

Hi

Am 21.04.25 um 06:26 schrieb Nick Bowler:
> Hi,
>
> I recently noticed that on current kernels I lose video output from
> my Blackbird's AST2500 BMC after a reboot, which makes it difficult to
> boot the system again (the video output will come on only after Linux
> is booted again).
>
> With Linux 6.6 and earlier, there is no problem rebooting, everything
> is fine.
>
> I bisected to this commit:
>
>    ce3d99c8349584bc0fbe1e21918a3ea1155343aa is the first bad commit
>    commit ce3d99c8349584bc0fbe1e21918a3ea1155343aa
>    Author: Douglas Anderson <dianders@chromium.org>
>    Date:   Fri Sep 1 16:39:53 2023 -0700
>
>        drm: Call drm_atomic_helper_shutdown() at shutdown time for misc drivers
>
> This commit does not revert cleanly on 6.14, but I can easily undo
> the changes this commit made to the ast driver, and this is enough
> to restore working behaviour.
>
> Let me know if you need any more info!

Would you be able to test a patch?

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)



      parent reply	other threads:[~2025-09-17  9:22 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
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 [this message]

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=b0cbc791-a209-4756-acf0-e869888294ac@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®