https://bugs.freedesktop.org/show_bug.cgi?id=105173

--- Comment #10 from Pierre Moreau <pierre.morrow-GANU6spQydw@public.gmane.org> ---
(In reply to Nick Lee from comment #8)
> Also tried:
> 
> Vanilla kernel 4.15.4-300.vanilla.knurd.1.fc27.x86_64
> mesa-17.3.5
> wayland session
> reproducible

What exactly is reproducible? The artefacts I would assume, but which error
exactly? The NULL pointer dereference, or the “trapped read at 0080000000 on
channel 1 [0fbb0000 DRM] engine 00 [PGRAPH] client 03 [DISPATCH] subclient 04
[M2M_IN] reason 00000006 [NULL_DMAOBJ]” one?
I did manage to reproduce the second one with Wayland, but still no luck with
the first one.

(In reply to Nick Lee from comment #8)
> Fedora-Workstation-Live-x86_64-Rawhide-20180220.n.0.iso
> wayland session
> mesa-18.0.0-0.1.rc4.fc28.x86_64
> Got artefacts with dmesg output:
> 
> [ 1035.437016] nouveau 0000:03:00.0: swiotlb buffer is full (sz: 2097152
> bytes)
> [ 1035.437020] nouveau 0000:03:00.0: swiotlb: coherent allocation failed,
> size=2097152
> [ 1035.437023] CPU: 0 PID: 1842 Comm: gnome-shell Not tainted
> 4.16.0-0.rc2.git0.1.fc28.x86_64 #1
> [ 1035.437024] Hardware name: NVIDIA MCP7A/MCP7A, BIOS 6.00 PG 04/22/2009
> [ 1035.437025] Call Trace:
> [ 1035.437036]  dump_stack+0x5c/0x85
> [ 1035.437040]  swiotlb_alloc_coherent+0x1c3/0x1e0
> [ 1035.437052]  ttm_dma_pool_get_pages+0x21a/0x620 [ttm]
> [ 1035.437057]  ttm_dma_populate+0xdd/0x390 [ttm]
> [ 1035.437062]  ttm_tt_bind+0x2e/0x60 [ttm]
> [ 1035.437067]  ttm_bo_handle_move_mem+0x4cf/0x550 [ttm]
> [ 1035.437073]  ttm_bo_validate+0x119/0x130 [ttm]
> [ 1035.437104]  ? drm_get_edid_switcheroo+0x16/0x40 [drm]
> [ 1035.437109]  ttm_bo_init_reserved+0x334/0x380 [ttm]
> [ 1035.437114]  ? ttm_bo_init+0x62/0xd0 [ttm]
> [ 1035.437190]  ? nouveau_bo_invalidate_caches+0x10/0x10 [nouveau]
> [ 1035.437226]  ? nouveau_bo_new+0x401/0x580 [nouveau]
> [ 1035.437262]  ? nouveau_bo_invalidate_caches+0x10/0x10 [nouveau]
> [ 1035.437298]  ? nouveau_gem_new+0x120/0x120 [nouveau]
> [ 1035.437334]  ? nouveau_gem_new+0x5d/0x120 [nouveau]
> [ 1035.437370]  ? nouveau_gem_ioctl_new+0x53/0xe0 [nouveau]
> [ 1035.437381]  ? drm_ioctl_kernel+0x5b/0xb0 [drm]
> [ 1035.437392]  ? drm_ioctl+0x1c4/0x380 [drm]
> [ 1035.437428]  ? nouveau_gem_new+0x120/0x120 [nouveau]
> [ 1035.437431]  ? eventfd_write+0x94/0x2a0
> [ 1035.437467]  ? nouveau_drm_ioctl+0x65/0xc0 [nouveau]
> [ 1035.437470]  ? do_vfs_ioctl+0xa4/0x610
> [ 1035.437471]  ? SyS_ioctl+0x74/0x80
> [ 1035.437475]  ? do_syscall_64+0x74/0x180
> [ 1035.437478]  ? entry_SYSCALL_64_after_hwframe+0x3d/0xa2

I’ll try the iso. Did you get this error with supertuxkart as well, or simply
by launching the session?


(In reply to Sérgio M. Basto from comment #9)
> Complete unresponsive my nvidia , with nouveau or nvidia drive when boot
> with kernel 4.15.x last kernel tested :  4.15.4 
> 
> 
> 01:00.0 VGA compatible controller: NVIDIA Corporation G98M [GeForce 9300M
> GS] (rev a1)
> 
> [   29.876760] nouveau 0000:01:00.0: DRM: EVO timeout

It might be a different issue (especially if you get a freeze even when using
the NVIDIA driver. Please open a separate bug report; it’s always easier to
merge two bug reports than to split one in two.

-- 
You are receiving this mail because:
You are the assignee for the bug.