stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Thorsten Leemhuis <regressions@leemhuis.info>
Cc: Andreas <andreas.thalhammer@linux.com>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	"regressions@lists.linux.dev" <regressions@lists.linux.dev>,
	Javier Martinez Canillas <javierm@redhat.com>,
	ML dri-devel <dri-devel@lists.freedesktop.org>,
	David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
	Sasha Levin <sashal@kernel.org>,
	Thomas Zimmermann <tzimmermann@suse.de>
Subject: Re: [Regression] CPU stalls and eventually causes a complete system freeze with 6.0.3 due to "video/aperture: Disable and unregister sysfb devices via aperture helpers"
Date: Mon, 24 Oct 2022 13:27:46 +0200	[thread overview]
Message-ID: <Y1Z2sq9RyEnIdixD@kroah.com> (raw)
In-Reply-To: <958fd763-01b6-0167-ba6b-97cbd3bddcb6@leemhuis.info>

On Mon, Oct 24, 2022 at 12:41:43PM +0200, Thorsten Leemhuis wrote:
> Hi! Thx for the reply.
> 
> On 24.10.22 12:26, Thomas Zimmermann wrote:
> > Am 23.10.22 um 10:04 schrieb Thorsten Leemhuis:
> >>
> >> I noticed a regression report in bugzilla.kernel.org. As many (most?)
> >> kernel developer don't keep an eye on it, I decided to forward it by
> >> mail. Quoting from https://bugzilla.kernel.org/show_bug.cgi?id=216616  :
> >>
> >>>   Andreas 2022-10-22 14:25:32 UTC
> >>>
> >>> Created attachment 303074 [details]
> >>> dmesg
> > 
> > I've looked at the kernel log and found that simpledrm has been loaded
> > *after* amdgpu, which should never happen. The problematic patch has
> > been taken from a long list of refactoring work on this code. No wonder
> > that it doesn't work as expected.
> > 
> > Please cherry-pick commit 9d69ef183815 ("fbdev/core: Remove
> > remove_conflicting_pci_framebuffers()") into the 6.0 stable branch and
> > report on the results. It should fix the problem.
> 
> Greg, is that enough for you to pick this up? Or do you want Andreas to
> test first if it really fixes the reported problem?

This should be good enough.  If this does NOT fix the issue, please let
me know.

thanks,

greg k-h

  reply	other threads:[~2022-10-24 11:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-23  8:04 [Regression] CPU stalls and eventually causes a complete system freeze with 6.0.3 due to "video/aperture: Disable and unregister sysfb devices via aperture helpers" Thorsten Leemhuis
2022-10-24 10:26 ` Thomas Zimmermann
2022-10-24 10:41   ` Thorsten Leemhuis
2022-10-24 11:27     ` Greg KH [this message]
2022-10-24 11:31       ` Thomas Zimmermann
2022-10-24 16:19         ` Andreas Thalhammer
2022-10-25  8:16           ` Thomas Zimmermann
2022-10-25  8:45             ` Andreas Thalhammer
2022-10-25  9:21               ` Thomas Zimmermann
2022-10-25 10:25                 ` Greg KH
2022-10-24 16:53         ` Andreas Thalhammer

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=Y1Z2sq9RyEnIdixD@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=airlied@gmail.com \
    --cc=andreas.thalhammer@linux.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=javierm@redhat.com \
    --cc=regressions@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).