[TLDR: This mail in primarily relevant for Linux kernel regression
tracking. See link in footer if these mails annoy you.]
On 05.01.23 13:28, Thorsten Leemhuis wrote:
> On 28.12.22 15:49, Diogo Ivo wrote:
>> Hello,
>>
>> Commit 2541626cfb79 breaks GM20B probe with
>> the following kernel log:
> Ju
Le dim. 29 janv. 2023 à 23:36, Ben Skeggs a écrit :
>
> On Fri, 27 Jan 2023 at 20:42, Diogo Ivo wrote:
> >
> > On Fri, Jan 27, 2023 at 04:00:59PM +1000, Ben Skeggs wrote:
> > > On Fri, 20 Jan 2023 at 21:37, Diogo Ivo
> > > wrote:
> > > >
> > > > On Wed, Jan 18, 2023 at 11:28:49AM +1000, Ben Ske
On Mon, Jan 30, 2023 at 08:36:06AM +1000, Ben Skeggs wrote:
> On Fri, 27 Jan 2023 at 20:42, Diogo Ivo wrote:
> >
> > On Fri, Jan 27, 2023 at 04:00:59PM +1000, Ben Skeggs wrote:
> > > On Fri, 20 Jan 2023 at 21:37, Diogo Ivo
> > > wrote:
> > > >
> > > > On Wed, Jan 18, 2023 at 11:28:49AM +1000, Be
On Fri, 27 Jan 2023 at 20:42, Diogo Ivo wrote:
>
> On Fri, Jan 27, 2023 at 04:00:59PM +1000, Ben Skeggs wrote:
> > On Fri, 20 Jan 2023 at 21:37, Diogo Ivo
> > wrote:
> > >
> > > On Wed, Jan 18, 2023 at 11:28:49AM +1000, Ben Skeggs wrote:
> > > > On Mon, 16 Jan 2023 at 22:27, Diogo Ivo
> > > >
On Fri, Jan 27, 2023 at 10:03:17AM +0100, Nicolas Chauvet wrote:
> I've tried to run glmark2-wayland under weston with DRI_PRIME=1, it
> seems to work at the beginning, but then I have the following error:
>
> [ 1510.861730] nouveau 5700.gpu: gr: DATA_ERROR 0003
> [INVALID_OPERATION] ch 3
On Fri, Jan 27, 2023 at 04:00:59PM +1000, Ben Skeggs wrote:
> On Fri, 20 Jan 2023 at 21:37, Diogo Ivo wrote:
> >
> > On Wed, Jan 18, 2023 at 11:28:49AM +1000, Ben Skeggs wrote:
> > > On Mon, 16 Jan 2023 at 22:27, Diogo Ivo
> > > wrote:
> > > > On Mon, Jan 16, 2023 at 07:45:05AM +1000, David Airl
Le ven. 27 janv. 2023 à 07:01, Ben Skeggs a écrit :
>
> On Fri, 20 Jan 2023 at 21:37, Diogo Ivo wrote:
> >
> > On Wed, Jan 18, 2023 at 11:28:49AM +1000, Ben Skeggs wrote:
> > > On Mon, 16 Jan 2023 at 22:27, Diogo Ivo
> > > wrote:
> > > > On Mon, Jan 16, 2023 at 07:45:05AM +1000, David Airlie wr
On Fri, 20 Jan 2023 at 21:37, Diogo Ivo wrote:
>
> On Wed, Jan 18, 2023 at 11:28:49AM +1000, Ben Skeggs wrote:
> > On Mon, 16 Jan 2023 at 22:27, Diogo Ivo
> > wrote:
> > > On Mon, Jan 16, 2023 at 07:45:05AM +1000, David Airlie wrote:
> > > > As a quick check can you try changing
> > > >
> > > >
On Wed, Jan 18, 2023 at 11:28:49AM +1000, Ben Skeggs wrote:
> On Mon, 16 Jan 2023 at 22:27, Diogo Ivo 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_targ
On Mon, 16 Jan 2023 at 22:27, Diogo Ivo wrote:
>
> On Mon, Jan 16, 2023 at 07:45:05AM +1000, David Airlie wrote:
> > On Thu, Dec 29, 2022 at 12:58 AM Diogo Ivo
> > wrote:
> > As a quick check can you try changing
> >
> > drivers/gpu/drm/nouveau/nvkm/core/firmware.c:nvkm_firmware_mem_target
> > f
On Mon, Jan 16, 2023 at 07:45:05AM +1000, David Airlie wrote:
> On Thu, Dec 29, 2022 at 12:58 AM Diogo Ivo
> 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 ?
Hello!
App
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
>
On Sat, Jan 14, 2023 at 5:07 PM Diogo Ivo wrote:
>
> On Sat, Jan 14, 2023 at 04:27:38AM +0100, Karol Herbst wrote:
> > I tried to look into it, but my jetson nano, just constantly behaves
> > in very strange ways. I tried to compile and install a 6.1 kernel onto
> > it, but any kernel just refuses
On Sat, Jan 14, 2023 at 04:27:38AM +0100, Karol Herbst wrote:
> I tried to look into it, but my jetson nano, just constantly behaves
> in very strange ways. I tried to compile and install a 6.1 kernel onto
> it, but any kernel just refuses to boot and I have no idea what's up
> with that device. Th
On Fri, Jan 13, 2023 at 02:19:06PM +0100, Linux kernel regression tracking
(Thorsten Leemhuis) wrote:
> Diogo, for that it would be really helpful to known: is the issue still
> happening with latest mainline? Is it possible to revert 2541626cfb79
> easily? And if so: do things work afterwards aga
On Fri, Jan 13, 2023 at 2:19 PM Linux kernel regression tracking
(Thorsten Leemhuis) wrote:
>
> [CCing Daniel]
>
> On 05.01.23 13:28, Thorsten Leemhuis wrote:
> > [adding Karol and Lyude to the list of recipients]
> >
> > On 28.12.22 15:49, Diogo Ivo wrote:
> >> Hello,
> >>
> >> Commit 2541626cfb7
[CCing Daniel]
On 05.01.23 13:28, Thorsten Leemhuis wrote:
> [adding Karol and Lyude to the list of recipients]
>
> On 28.12.22 15:49, Diogo Ivo wrote:
>> Hello,
>>
>> Commit 2541626cfb79 breaks GM20B probe with
>> the following kernel log:
> Just wondering: is anyone looking on this? The report
[adding Karol and Lyude to the list of recipients]
Hi, this is your Linux kernel regression tracker. Top-posting for once,
to make this easily accessible to everyone.
On 28.12.22 15:49, Diogo Ivo wrote:
> Hello,
>
> Commit 2541626cfb79 breaks GM20B probe with
> the following kernel log:
Just won
18 matches
Mail list logo