All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Lothian <mike@fireburn.co.uk>
To: Arunpravin Paneer Selvam <arunpravin.paneerselvam@amd.com>
Cc: intel-gfx@lists.freedesktop.org, amd-gfx@lists.freedesktop.org,
	dri-devel@lists.freedesktop.org, alexander.deucher@amd.com,
	"Christian König" <christian.koenig@amd.com>,
	matthew.auld@intel.com
Subject: Re: [PATCH v12] drm/amdgpu: add drm buddy support to amdgpu
Date: Mon, 2 May 2022 17:31:36 +0100	[thread overview]
Message-ID: <CAHbf0-EzPP5gAyZQmxeAo3Ep0g-rO4XbDgEB_SdsR84xY+at9A@mail.gmail.com> (raw)
In-Reply-To: <8b99ca20-f711-ec32-0cd2-16fc52846ce0@amd.com>

On Mon, 2 May 2022 at 16:54, Arunpravin Paneer Selvam
<arunpravin.paneerselvam@amd.com> wrote:
>
>
>
> On 5/2/2022 8:41 PM, Mike Lothian wrote:
> > On Wed, 27 Apr 2022 at 12:55, Mike Lothian <mike@fireburn.co.uk> wrote:
> >> On Tue, 26 Apr 2022 at 17:36, Christian König <christian.koenig@amd.com> wrote:
> >>> Hi Mike,
> >>>
> >>> sounds like somehow stitching together the SG table for PRIME doesn't
> >>> work any more with this patch.
> >>>
> >>> Can you try with P2P DMA disabled?
> >> -CONFIG_PCI_P2PDMA=y
> >> +# CONFIG_PCI_P2PDMA is not set
> >>
> >> If that's what you're meaning, then there's no difference, I'll upload
> >> my dmesg to the gitlab issue
> >>
> >>> Apart from that can you take a look Arun?
> >>>
> >>> Thanks,
> >>> Christian.
> > Hi
> >
> > Have you had any success in replicating this?
> Hi Mike,
> I couldn't replicate on my Raven APU machine. I see you have 2 cards
> initialized, one is Renoir
> and the other is Navy Flounder. Could you give some more details, are
> you running Gravity Mark
> on Renoir and what is your system RAM configuration?
> >
> > Cheers
> >
> > Mike
>
Hi

It's a PRIME laptop, it failed on the RENOIR too, it caused a lockup,
but systemd managed to capture it, I'll attach it to the issue

I've got 64GB RAM, the 6800M has 12GB VRAM

Cheers

Mike

WARNING: multiple messages have this Message-ID (diff)
From: Mike Lothian <mike@fireburn.co.uk>
To: Arunpravin Paneer Selvam <arunpravin.paneerselvam@amd.com>
Cc: intel-gfx@lists.freedesktop.org, amd-gfx@lists.freedesktop.org,
	dri-devel@lists.freedesktop.org, alexander.deucher@amd.com,
	"Christian König" <christian.koenig@amd.com>,
	matthew.auld@intel.com
Subject: Re: [Intel-gfx] [PATCH v12] drm/amdgpu: add drm buddy support to amdgpu
Date: Mon, 2 May 2022 17:31:36 +0100	[thread overview]
Message-ID: <CAHbf0-EzPP5gAyZQmxeAo3Ep0g-rO4XbDgEB_SdsR84xY+at9A@mail.gmail.com> (raw)
In-Reply-To: <8b99ca20-f711-ec32-0cd2-16fc52846ce0@amd.com>

On Mon, 2 May 2022 at 16:54, Arunpravin Paneer Selvam
<arunpravin.paneerselvam@amd.com> wrote:
>
>
>
> On 5/2/2022 8:41 PM, Mike Lothian wrote:
> > On Wed, 27 Apr 2022 at 12:55, Mike Lothian <mike@fireburn.co.uk> wrote:
> >> On Tue, 26 Apr 2022 at 17:36, Christian König <christian.koenig@amd.com> wrote:
> >>> Hi Mike,
> >>>
> >>> sounds like somehow stitching together the SG table for PRIME doesn't
> >>> work any more with this patch.
> >>>
> >>> Can you try with P2P DMA disabled?
> >> -CONFIG_PCI_P2PDMA=y
> >> +# CONFIG_PCI_P2PDMA is not set
> >>
> >> If that's what you're meaning, then there's no difference, I'll upload
> >> my dmesg to the gitlab issue
> >>
> >>> Apart from that can you take a look Arun?
> >>>
> >>> Thanks,
> >>> Christian.
> > Hi
> >
> > Have you had any success in replicating this?
> Hi Mike,
> I couldn't replicate on my Raven APU machine. I see you have 2 cards
> initialized, one is Renoir
> and the other is Navy Flounder. Could you give some more details, are
> you running Gravity Mark
> on Renoir and what is your system RAM configuration?
> >
> > Cheers
> >
> > Mike
>
Hi

It's a PRIME laptop, it failed on the RENOIR too, it caused a lockup,
but systemd managed to capture it, I'll attach it to the issue

I've got 64GB RAM, the 6800M has 12GB VRAM

Cheers

Mike

  reply	other threads:[~2022-05-02 16:31 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-07  5:46 [PATCH v12] drm/amdgpu: add drm buddy support to amdgpu Arunpravin Paneer Selvam
2022-04-07  5:46 ` Arunpravin Paneer Selvam
2022-04-07  5:46 ` [Intel-gfx] " Arunpravin Paneer Selvam
2022-04-07  6:10 ` Christian König
2022-04-07  6:10   ` Christian König
2022-04-07  6:10   ` [Intel-gfx] " Christian König
2022-04-07  6:22 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for drm/amdgpu: add drm buddy support to amdgpu (rev3) Patchwork
2022-04-07 13:47 ` [PATCH v12] drm/amdgpu: add drm buddy support to amdgpu Paul Menzel
2022-04-07 13:47   ` Paul Menzel
2022-04-07 13:47   ` [Intel-gfx] " Paul Menzel
2022-04-26 15:29 ` Mike Lothian
2022-04-26 15:29   ` [Intel-gfx] " Mike Lothian
2022-04-26 16:36   ` Christian König
2022-04-26 16:36     ` [Intel-gfx] " Christian König
2022-04-27  5:26     ` Paneer Selvam, Arunpravin
2022-04-27  5:26       ` [Intel-gfx] " Paneer Selvam, Arunpravin
2022-04-27 11:55     ` Mike Lothian
2022-04-27 11:55       ` [Intel-gfx] " Mike Lothian
2022-05-02 15:11       ` Mike Lothian
2022-05-02 15:11         ` [Intel-gfx] " Mike Lothian
2022-05-02 15:54         ` Arunpravin Paneer Selvam
2022-05-02 15:54           ` [Intel-gfx] " Arunpravin Paneer Selvam
2022-05-02 16:31           ` Mike Lothian [this message]
2022-05-02 16:31             ` Mike Lothian
2022-05-16 12:40             ` Mike Lothian
2022-05-16 12:40               ` [Intel-gfx] " Mike Lothian
2022-05-16 15:05               ` Alex Deucher
2022-05-16 15:05                 ` [Intel-gfx] " Alex Deucher
2022-05-28  7:43                 ` Paneer Selvam, Arunpravin
2022-05-28  7:43                   ` [Intel-gfx] " Paneer Selvam, Arunpravin
2022-05-28 23:52                   ` Mike Lothian
2022-05-28 23:52                     ` Mike Lothian
2022-05-28 23:52                     ` [Intel-gfx] " Mike Lothian
2022-05-30  6:02                     ` Christian König
2022-05-30  6:02                       ` Christian König
2022-06-23 11:15                     ` Mike Lothian
2022-06-23 11:15                       ` Mike Lothian
2022-06-23 11:15                       ` [Intel-gfx] " Mike Lothian

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=CAHbf0-EzPP5gAyZQmxeAo3Ep0g-rO4XbDgEB_SdsR84xY+at9A@mail.gmail.com \
    --to=mike@fireburn.co.uk \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=arunpravin.paneerselvam@amd.com \
    --cc=christian.koenig@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=matthew.auld@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 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.