From: Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt>
To: Ben Skeggs <skeggsb@gmail.com>
Cc: regressions@lists.linux.dev, kherbst@redhat.com,
kwizart@gmail.com, nouveau@lists.freedesktop.org,
dri-devel@lists.freedesktop.org, bskeggs@redhat.com,
David Airlie <airlied@redhat.com>
Subject: Re: [REGRESSION] GM20B probe fails after commit 2541626cfb79
Date: Fri, 20 Jan 2023 11:34:43 +0000 [thread overview]
Message-ID: <20230120113443.wgwhwp7tm6rnc6je@wslaptop> (raw)
In-Reply-To: <CACAvsv48vH6hbacQCN+yKP8ZcDjFMWciBt6U_Xv-LEYJHZ1q9g@mail.gmail.com>
On Wed, Jan 18, 2023 at 11:28:49AM +1000, Ben Skeggs wrote:
> On Mon, 16 Jan 2023 at 22:27, Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt> wrote:
> > On Mon, Jan 16, 2023 at 07:45:05AM +1000, David Airlie wrote:
> > > As a quick check can you try changing
> > >
> > > drivers/gpu/drm/nouveau/nvkm/core/firmware.c:nvkm_firmware_mem_target
> > > from NVKM_MEM_TARGET_HOST to NVKM_MEM_TARGET_NCOH ?
> In addition to Dave's change, can you try changing the
> nvkm_falcon_load_dmem() call in gm20b_pmu_init() to:
>
> nvkm_falcon_pio_wr(falcon, (u8 *)&args, 0, 0, DMEM, addr_args,
> sizeof(args), 0, false);
Hello!
Chiming in just to say that with this change I see the same as Nicolas
except that the init message size is 255 instead of 0:
[ 2.196934] nouveau 57000000.gpu: pmu: unexpected init message size 255 vs 42
next prev parent reply other threads:[~2023-01-20 11:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-28 14:49 [REGRESSION] GM20B probe fails after commit 2541626cfb79 Diogo Ivo
2023-01-05 12:28 ` Thorsten Leemhuis
2023-01-13 13:19 ` Linux kernel regression tracking (Thorsten Leemhuis)
2023-01-14 3:27 ` Karol Herbst
2023-01-14 16:03 ` Diogo Ivo
2023-01-14 18:56 ` Karol Herbst
2023-01-14 15:58 ` Diogo Ivo
2023-02-03 9:13 ` Linux kernel regression tracking (#update)
2023-01-15 21:45 ` David Airlie
2023-01-16 12:24 ` Diogo Ivo
2023-01-18 1:28 ` Ben Skeggs
2023-01-18 8:42 ` [Nouveau] " Nicolas Chauvet
2023-01-20 11:34 ` Diogo Ivo [this message]
2023-01-27 6:00 ` Ben Skeggs
2023-01-27 9:03 ` Nicolas Chauvet
2023-01-27 10:48 ` Diogo Ivo
2023-01-27 10:39 ` Diogo Ivo
2023-01-29 22:36 ` Ben Skeggs
2023-01-30 13:54 ` Diogo Ivo
2023-01-30 16:05 ` Nicolas Chauvet
2023-01-17 15:55 ` [Nouveau] " Nicolas Chauvet
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=20230120113443.wgwhwp7tm6rnc6je@wslaptop \
--to=diogo.ivo@tecnico.ulisboa.pt \
--cc=airlied@redhat.com \
--cc=bskeggs@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kherbst@redhat.com \
--cc=kwizart@gmail.com \
--cc=nouveau@lists.freedesktop.org \
--cc=regressions@lists.linux.dev \
--cc=skeggsb@gmail.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).