On Thu, May 9, 2024 at 8:31 PM Linux regression tracking (Thorsten
Leemhuis) wrote:
>
> On 06.05.24 20:23, Dan Moulding wrote:
> > After upgrading to rc7 from rc6 on a system with NVIDIA GP104 using
> > the nouveau driver, I get no display output from the kernel (only the
> > output from GRUB
> V2:
> * Fixup explanation as the prior one was bogus
For v2 of both patches,
Reviewed-by: Dave Airlie
Please apply to drm-misc-fixes
Dave.
On Fri, Apr 19, 2024 at 6:27 AM Lyude Paul wrote:
>
> So - first some context here for Ben and anyone else who hasn't been
> following. A little while ago I got a Slimbook Executive 16 with a
> Nvidia RTX 4060 in it, and I've unfortunately been running into a kind
> of annoying issue. Currently
Reviewed-by: Dave Airlie
On Sat, Mar 16, 2024 at 7:21 AM Lyude Paul wrote:
>
> I've recently been seeing some unexplained GSP errors on my RTX 6000 from
> failed aux transactions:
>
> [ 132.915867] nouveau :1f:00.0: gsp: cli:0xc1d2 obj:0x0073
> ctrl cmd:0x00731341 failed:
On Tue, Feb 6, 2024 at 1:55 PM Timur Tabi wrote:
>
> On Tue, 2024-02-06 at 10:35 +1000, David Airlie wrote:
> > >
> > > An end-user can capture the logs using the following commands:
> > >
> > > cp /sys/kernel/debug/nouveau/loginit loginit
> >
On Tue, Feb 6, 2024 at 7:45 AM Timur Tabi wrote:
>
> The LOGINIT, LOGINTR, LOGRM, and LOGPMU buffers are circular buffers
> that have printf-like logs from GSP-RM and PMU encoded in them.
>
> LOGINIT, LOGINTR, and LOGRM are allocated by Nouveau and their DMA
> addresses are passed to GSP-RM
NAK for backporting this to anything, it is just a fix for 6.7
On Mon, Jan 8, 2024 at 10:28 PM Sasha Levin wrote:
>
> From: Dave Airlie
>
> [ Upstream commit 7854ea0e408d7f2e8faaada1773f3ddf9cb538f5 ]
>
> This func ptr here is normally static allocation, but gsp r535
> uses a dynamic pointer,
On Wed, Nov 22, 2023 at 9:53 AM Timur Tabi wrote:
>
> Document a few aspects of communication with GSP-RM. These comments
> are derived from notes made during early development of GSP-RM
> support in Nouveau, but were not included in the initial patch set.
>
> Signed-off-by: Timur Tabi
> ---
>
On Sat, Jan 28, 2023 at 1:17 AM Christian König
wrote:
>
> Am 27.01.23 um 15:44 schrieb Danilo Krummrich:
> > [SNIP]
>
> What you want is one component for tracking the VA allocations
> (drm_mm based) and a different component/interface for tracking the
> VA mappings (probably
On Thu, Dec 29, 2022 at 12:58 AM Diogo Ivo wrote:
>
> Hello,
>
> Commit 2541626cfb79 breaks GM20B probe with
> the following kernel log:
>
> [2.153892] [ cut here ]
> [2.153897] WARNING: CPU: 1 PID: 36 at
> drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmmgf100.c:273
>
Hi Mike,
Thanks for the report,
Does the attached patch help?
Dave.
On Thu, Dec 17, 2020 at 11:30 PM Mike Galbraith wrote:
>
> On Wed, 2020-12-16 at 14:31 +0100, Mike Galbraith wrote:
> > When the below new to 5.11 cycle badness happens, it's time to reboot.
> >
> > ...
> > [ 27.467260]
On Thu, Mar 20, 2014 at 1:28 AM, Ilia Mirkin imir...@alum.mit.edu wrote:
There was a proliferation of duplicated checks for runpm == -1
optimus. Instead of continuing that tradition, get rid of all of them,
only doing the optimus computation once on load.
This should hopefully fix
- Original Message -
From: Ilia Mirkin imir...@alum.mit.edu
To: David Airlie airl...@redhat.com
Cc: Ben Skeggs skeg...@gmail.com, Ben Skeggs bske...@redhat.com,
nouveau@lists.freedesktop.org
Sent: Thursday, 20 March, 2014 9:49:47 AM
Subject: Re: [Nouveau] [PATCH] drm: compute
13 matches
Mail list logo
