linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alex Deucher <alexdeucher@gmail.com>
To: Phillip Susi <phill@thesusis.net>
Cc: "Luben Tuikov" <ltuikov89@gmail.com>,
	"Linux regressions mailing list" <regressions@lists.linux.dev>,
	"Christian König" <ckoenig.leichtzumerken@gmail.com>,
	linux-kernel@vger.kernel.org,
	"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>,
	dri-devel@lists.freedesktop.org,
	"Alex Deucher" <alexander.deucher@amd.com>,
	"Christian König" <christian.koenig@amd.com>,
	"Danilo Krummrich" <dakr@redhat.com>
Subject: Re: Radeon regression in 6.6 kernel
Date: Tue, 12 Dec 2023 09:55:21 -0500	[thread overview]
Message-ID: <CADnq5_MYSCd32p2doPMN1_vcrUZvHMDPn83LU-0oVBS6fuRVuA@mail.gmail.com> (raw)
In-Reply-To: <87r0jsw9g3.fsf@vps.thesusis.net>

On Mon, Dec 11, 2023 at 7:28 PM Phillip Susi <phill@thesusis.net> wrote:
>
> Phillip Susi <phill@thesusis.net> writes:
>
> > And it works, but 6.7-rc5 does not, even though it includes that patch.
> > Here's the syslog from the attempt.  I'll start bisecting again.
>
> I checked out the patch that got merged upstream and it also fails.  I
> looked at the two commits, and I see what happened.  Your original patch
> MOVED the call to amdgpu_ttm_set_buffer_funcs_status().  The one that
> got merged into Linus' tree instead DUPLICATES the call.  Oops?
>

Yeah, I messed up the patch somehow when I applied it.  Fix up already
queued up to add the missing chunk.

Alex

  reply	other threads:[~2023-12-12 14:55 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-12  0:46 Radeon regression in 6.6 kernel Phillip Susi
2023-11-12 11:12 ` Bagas Sanjaya
2023-11-12 18:42   ` Phillip Susi
2023-11-19  6:32 ` Linux regression tracking (Thorsten Leemhuis)
2023-11-19  6:47   ` Dave Airlie
2023-11-19 13:24     ` Bagas Sanjaya
2023-11-19 13:48       ` Linux regression tracking (Thorsten Leemhuis)
2023-11-19 13:53         ` Bagas Sanjaya
2023-11-20 15:57     ` Christian König
2023-11-20 16:08       ` Alex Deucher
2023-11-20 16:24         ` Christian König
2023-11-20 17:31           ` Alex Deucher
2023-11-20 22:40             ` Phillip Susi
2023-11-21 14:05               ` Alex Deucher
2023-11-21 22:05                 ` Phillip Susi
2023-11-23  1:34                   ` Luben Tuikov
2023-11-27 23:24             ` Phillip Susi
2023-11-28 22:13               ` Alex Deucher
2023-11-29  4:44                 ` Luben Tuikov
2023-11-29 13:50                   ` Alex Deucher
2023-11-29 15:22                     ` Alex Deucher
2023-11-29 16:41                       ` Luben Tuikov
2023-11-29 18:52                         ` Alex Deucher
2023-11-29 20:10                           ` Alex Deucher
2023-11-29 20:49                             ` Alex Deucher
2023-11-30  3:36                               ` Luben Tuikov
2023-11-30  3:47                                 ` Luben Tuikov
2023-11-30 23:28                                   ` Alex Deucher
2023-11-30 21:29                                 ` Alex Deucher
2023-12-01 16:55                               ` Alex Deucher
2023-12-03 20:40                                 ` Phillip Susi
2023-12-04 14:14                                   ` Alex Deucher
2023-12-11 23:50                                     ` Phillip Susi
2023-12-12  0:28                                       ` Phillip Susi
2023-12-12 14:55                                         ` Alex Deucher [this message]
2023-11-29 16:20                     ` Luben Tuikov
2023-11-29 18:45                       ` Alex Deucher
2023-11-29 20:24                       ` Phillip Susi
2023-11-20 22:08       ` Phillip Susi

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=CADnq5_MYSCd32p2doPMN1_vcrUZvHMDPn83LU-0oVBS6fuRVuA@mail.gmail.com \
    --to=alexdeucher@gmail.com \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=christian.koenig@amd.com \
    --cc=ckoenig.leichtzumerken@gmail.com \
    --cc=dakr@redhat.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ltuikov89@gmail.com \
    --cc=phill@thesusis.net \
    --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;
as well as URLs for NNTP newsgroup(s).