From: Genes Lists <lists@sapience.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: regressions@lists.linux.dev, linux-kernel@vger.kernel.org,
lucas.demarchi@intel.com, thomas.hellstrom@linux.intel.com,
rodrigo.vivi@intel.com, airlied@gmail.com, tzimmermann@suse.de,
dri-devel@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: 6.13-rc1 graphics fail
Date: Fri, 13 Dec 2024 07:14:07 -0500 [thread overview]
Message-ID: <dd13efc9b3fe3e3acd599ca91b714fa92f6cb9a8.camel@sapience.com> (raw)
In-Reply-To: <7db24095f935d874fae466853b0984103f97b40f.camel@sapience.com>
[-- Attachment #1: Type: text/plain, Size: 790 bytes --]
On Tue, 2024-12-03 at 06:34 -0500, Genes Lists wrote:
> On Tue, 2024-12-03 at 11:16 +0200, Ville Syrjälä wrote:
> > > ...
>
> > Probably https://gitlab.freedesktop.org/drm/i915/kernel/-
> > /issues/13057
> >
> Very helpful.
>
> I tested your patch set on Linus' tree commit
> cdd30ebb1b9f36159d66f088b61aee264e649d7a :
>
> https://patchwork.freedesktop.org/series/141911/
>
> and confirm that this fixes the problem
>
> Thank you.
>
>
Just a CC to regressions list for tracking.
First report here:
https://lore.kernel.org/lkml/3b097dddd7095bccabe6791b90899c689f271a35.c
amel@sapience.com/
Fixed by patch set as noted above, but not yet in mainline or linux-
next.
Thank you again Ville for quickly coming up with a fix.
--
Gene
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-12-13 12:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 18:40 6.13-rc1 graphics fail Genes Lists
2024-12-02 19:22 ` Thomas Hellström
2024-12-02 19:45 ` Genes Lists
2024-12-03 9:16 ` Ville Syrjälä
2024-12-03 11:34 ` Genes Lists
2024-12-13 12:14 ` Genes Lists [this message]
2025-01-04 11:06 ` [REGRESSION] " Genes Lists
2025-01-13 16:48 ` [REGRESSION] Re: 6.13-rc1 graphics fail -> resolved Genes Lists
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=dd13efc9b3fe3e3acd599ca91b714fa92f6cb9a8.camel@sapience.com \
--to=lists@sapience.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lucas.demarchi@intel.com \
--cc=regressions@lists.linux.dev \
--cc=rodrigo.vivi@intel.com \
--cc=thomas.hellstrom@linux.intel.com \
--cc=tzimmermann@suse.de \
--cc=ville.syrjala@linux.intel.com \
/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).