On (06/19/19 02:07), Ilia Mirkin wrote:
> If all else fails, just remove nouveau_dri.so and/or boot with
> nouveau.noaccel=1 -- should be perfect.
nouveau.noaccel=1 did the trick. Is there any other, let's say
less CPU-intensive, way to fix nouveau?
-ss
___
On (06/19/19 15:27), Sergey Senozhatsky wrote:
> [..]
>
> > If all else fails, just remove nouveau_dri.so and/or boot with
> > nouveau.noaccel=1 -- should be perfect.
>
> Can give it a try.
That has some impact on system responsiveness:
CPU% COMM
339.7
On (06/19/19 02:07), Ilia Mirkin wrote:
> On Wed, Jun 19, 2019 at 1:48 AM Sergey Senozhatsky
> wrote:
> >
> > On (06/19/19 01:20), Ilia Mirkin wrote:
> > > On Wed, Jun 19, 2019 at 1:08 AM Sergey Senozhatsky
> > > wrote:
> > > >
>
On (06/19/19 01:20), Ilia Mirkin wrote:
> On Wed, Jun 19, 2019 at 1:08 AM Sergey Senozhatsky
> wrote:
> >
> > On (06/14/19 11:50), Sergey Senozhatsky wrote:
> > > dmesg
> > >
> > > nouveau :01:00.0: DRM: GPU lockup - switching to software fbcon
&
On (06/14/19 11:50), Sergey Senozhatsky wrote:
> dmesg
>
> nouveau :01:00.0: DRM: GPU lockup - switching to software fbcon
> nouveau :01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT]
> nouveau :01:00.0: fifo: runlist 0: scheduled for recovery
> nouveau :01:00.
5.2.0-rc4-next-20190613
dmesg
nouveau :01:00.0: DRM: GPU lockup - switching to software fbcon
nouveau :01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT]
nouveau :01:00.0: fifo: runlist 0: scheduled for recovery
nouveau :01:00.0: fifo: channel 5: killed
nouveau :01:00.0: fifo:
On (05/17/19 16:27), Sergey Senozhatsky wrote:
> > ... but most likely it's utterly wrong.
> >
>
> JFI, I removed kmemleak annotation
meeehhh
kmemleak: 2046 new suspected memory leaks (see /sys/kernel/debug/kmemleak)
unreferenced object 0x95cbea4e6060 (size 1
On (05/17/19 15:13), Sergey Senozhatsky wrote:
> ... but most likely it's utterly wrong.
>
JFI, I removed kmemleak annotation and added the following
thing:
@@ -360,6 +360,7 @@ gp100_vmm_valid(struct nvkm_vmm *vmm, void *argv, u32 argc,
ret
On (05/17/19 15:31), Sergey Senozhatsky wrote:
> > backtrace:
> > [<81f2894f>] nvkm_memory_tags_get+0x8e/0x130
> > [<7cd7c0bc>] gf100_vmm_valid+0x196/0x2f0
> > [<70cc6d67>] nvkm_vmm_map+0xa8/0x360
>
On (05/17/19 15:13), Sergey Senozhatsky wrote:
> 5.1.0-next-20190517
>
> I'm looking at quite a lot of kmemleak reports coming from
> drm/nouveau/core/memory, all of which are:
>
> unreferenced object 0x8deec27c4ac0 (size 16):
> comm "Web Content"
Hello,
5.1.0-next-20190517
I'm looking at quite a lot of kmemleak reports coming from
drm/nouveau/core/memory, all of which are:
unreferenced object 0x8deec27c4ac0 (size 16):
comm "Web Content", pid 5309, jiffies 4309675011 (age 68.076s)
hex dump (first 16 bytes):
00
On (09/06/18 12:46), Ben Skeggs wrote:
> On Thu, Sep 6, 2018 at 12:42 PM Sergey Senozhatsky
> wrote:
> >
> > On (08/02/18 11:46), Sergey Senozhatsky wrote:
> > > Hi,
> > >
> > > My dmesg is filled up with these errors
> > >
> > > nou
On (08/02/18 11:46), Sergey Senozhatsky wrote:
> Hi,
>
> My dmesg is filled up with these errors
>
> nouveau :01:00.0: DRM: DDC responded, but no EDID for HDMI-A-1
> nouveau :01:00.0: DRM: DDC responded, but no EDID for VGA-1
> nouveau :01:00.0: DRM: DDC respo
Hi,
My dmesg is filled up with these errors
nouveau :01:00.0: DRM: DDC responded, but no EDID for HDMI-A-1
nouveau :01:00.0: DRM: DDC responded, but no EDID for VGA-1
nouveau :01:00.0: DRM: DDC responded, but no EDID for HDMI-A-1
nouveau :01:00.0: DRM: DDC responded, but no ED
14 matches
Mail list logo
