Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Lukas Wunner <lukas@wunner.de>
To: Johannes Stezenbach <js@sig21.net>,
	Thomas Zimmermann <tzimmermann@suse.de>
Cc: "Saarinen, Jani" <jani.saarinen@intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>
Subject: Re: i915 IVB hangup after resume from s2mem since v6.6.x
Date: Mon, 6 May 2024 21:42:18 +0200	[thread overview]
Message-ID: <ZjkymnMC40-Le7vG@wunner.de> (raw)
In-Reply-To: <Zjkk3y906HKdzScK@sig21.net>

[cc += Thomas]

On Mon, May 06, 2024 at 08:43:43PM +0200, Johannes Stezenbach wrote:
> so, git bisect pointed to:
> 
>  commit 701d2054fa317188cd4039c84e72c73254013b23
>  Author: Thomas Zimmermann <tzimmermann@suse.de>
>  Date:   Tue Jun 13 13:07:13 2023 +0200
> 
>     fbdev: Make support for userspace interfaces configurable
> 
>     Add Kconfig option CONFIG_FB_DEVICE and make the virtual fbdev
>     ...
> 
> I think nothing on my system uses /dev/fb*, thus I had disabled
> CONFIG_FB_DEVICE. Everything worked, only suspend/resume broke.
> I can confirm v6.8.9 with CONFIG_FB_DEVICE=y works fine.
> 
> Maybe setting CONFIG_FB_DEVICE=n would allow you to reproduce
> it in your CI tests?
> Let me know if you still want me to file at bug report about this.

A user-visible regression like this is always sufficient to ask for a
revert of the offending commit.  It's the commit author's duty to find
a fix ASAP. If you could file a bug report that would be helpful but
you've already done more than could be asked from any user.

Thanks,

Lukas

  reply	other threads:[~2024-05-06 19:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-29 19:34 i915 IVB hangup after resume from s2mem since v6.6.x Johannes Stezenbach
2024-04-30  6:57 ` Saarinen, Jani
2024-04-30  8:23   ` Johannes Stezenbach
2024-05-06 18:43     ` Johannes Stezenbach
2024-05-06 19:42       ` Lukas Wunner [this message]
2024-05-07  7:47         ` Johannes Stezenbach

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=ZjkymnMC40-Le7vG@wunner.de \
    --to=lukas@wunner.de \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.saarinen@intel.com \
    --cc=js@sig21.net \
    --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