All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: наб <nabijaczleweli@nabijaczleweli.xyz>
Cc: intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	dri-devel@lists.freedesktop.org, 971068@bugs.debian.org,
	Daniel Vetter <daniel@ffwll.ch>, David Airlie <airlied@gmail.com>,
	Salvatore Bonaccorso <carnil@debian.org>
Subject: Re: [Intel-gfx] Assertion failure in i915 intel_display.c#assert_plane() after resume from hibernation
Date: Thu, 26 Jan 2023 15:43:53 +0200	[thread overview]
Message-ID: <878rhp5s2u.fsf@intel.com> (raw)
In-Reply-To: <20230124173127.os3rwxnt6m6nloce@nabtop.nabijaczleweli.xyz>

On Tue, 24 Jan 2023, наб <nabijaczleweli@nabijaczleweli.xyz> wrote:
> Booted with both, hibernated, resumed; full dmesg below.

Unfortunately, this is probably hitting a regression with drm debug
logging, and we don't get proper debug logging for i915. :(

Please use DRM_USE_DYNAMIC_DEBUG=n with v6.1. I don't know if the proper
fixes have been backported to v6.1 stable kernels.

BR,
Jani.


-- 
Jani Nikula, Intel Open Source Graphics Center

WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@linux.intel.com>
To: наб <nabijaczleweli@nabijaczleweli.xyz>
Cc: intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	dri-devel@lists.freedesktop.org, 971068@bugs.debian.org,
	Salvatore Bonaccorso <carnil@debian.org>
Subject: Re: Assertion failure in i915 intel_display.c#assert_plane() after resume from hibernation
Date: Thu, 26 Jan 2023 15:43:53 +0200	[thread overview]
Message-ID: <878rhp5s2u.fsf@intel.com> (raw)
In-Reply-To: <20230124173127.os3rwxnt6m6nloce@nabtop.nabijaczleweli.xyz>

On Tue, 24 Jan 2023, наб <nabijaczleweli@nabijaczleweli.xyz> wrote:
> Booted with both, hibernated, resumed; full dmesg below.

Unfortunately, this is probably hitting a regression with drm debug
logging, and we don't get proper debug logging for i915. :(

Please use DRM_USE_DYNAMIC_DEBUG=n with v6.1. I don't know if the proper
fixes have been backported to v6.1 stable kernels.

BR,
Jani.


-- 
Jani Nikula, Intel Open Source Graphics Center

WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@linux.intel.com>
To: наб <nabijaczleweli@nabijaczleweli.xyz>
Cc: Salvatore Bonaccorso <carnil@debian.org>,
	David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
	intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	dri-devel@lists.freedesktop.org, 971068@bugs.debian.org
Subject: Re: Assertion failure in i915 intel_display.c#assert_plane() after resume from hibernation
Date: Thu, 26 Jan 2023 15:43:53 +0200	[thread overview]
Message-ID: <878rhp5s2u.fsf@intel.com> (raw)
In-Reply-To: <20230124173127.os3rwxnt6m6nloce@nabtop.nabijaczleweli.xyz>

On Tue, 24 Jan 2023, наб <nabijaczleweli@nabijaczleweli.xyz> wrote:
> Booted with both, hibernated, resumed; full dmesg below.

Unfortunately, this is probably hitting a regression with drm debug
logging, and we don't get proper debug logging for i915. :(

Please use DRM_USE_DYNAMIC_DEBUG=n with v6.1. I don't know if the proper
fixes have been backported to v6.1 stable kernels.

BR,
Jani.


-- 
Jani Nikula, Intel Open Source Graphics Center

  reply	other threads:[~2023-01-26 13:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-24  5:49 [Intel-gfx] Assertion failure in i915 intel_display.c#assert_plane() after resume from hibernation Salvatore Bonaccorso
2023-01-24  5:49 ` Salvatore Bonaccorso
2023-01-24  5:49 ` Salvatore Bonaccorso
2023-01-24 15:40 ` [Intel-gfx] " Jani Nikula
2023-01-24 15:40   ` Jani Nikula
2023-01-24 17:31   ` наб
2023-01-24 17:31     ` наб
2023-01-26 13:43     ` Jani Nikula [this message]
2023-01-26 13:43       ` Jani Nikula
2023-01-26 13:43       ` Jani Nikula
2023-01-26 15:42       ` наб
2023-01-26 15:42         ` наб

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=878rhp5s2u.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=971068@bugs.debian.org \
    --cc=airlied@gmail.com \
    --cc=carnil@debian.org \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nabijaczleweli@nabijaczleweli.xyz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.