[Nouveau] [Bug 87819] [NVAC] EQ overflowing

[bugzilla-daemon at freedesktop.org]

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

--- Comment #2 from Ilia Mirkin <imirkin at alum.mit.edu> ---
EQ overflowing == driver is stuck (in this case, at least). That "show state"
shows:

[ 1014.288718] Xorg            R  running task        0  1638   1589 0x00400004
[ 1014.288720]  ffff8800bc98fb48 ffffffff82f158c0 ffff8800bc98ffd8
0000000000014200
[ 1014.288722]  ffff880138e7fb80 ffffffff82c1c500 ffff8800be2f8000
0000000000000000
[ 1014.288724]  ffff8800bc98fb80 000000010002d6d7 ffffffff82f158c0
ffffffff82f158c0
[ 1014.288727] Call Trace:
[ 1014.288729]  [<ffffffff827cd549>] schedule+0x29/0x70
[ 1014.288731]  [<ffffffff827d023c>] schedule_timeout+0x11c/0x210
[ 1014.288734]  [<ffffffff820deea0>] ? call_timer_fn+0x160/0x160
[ 1014.288736]  [<ffffffff827d11ae>] ? _raw_spin_unlock_irqrestore+0x1e/0x50
[ 1014.288739]  [<ffffffff8252f2c5>] fence_default_wait.part.10+0xe5/0x220
[ 1014.288741]  [<ffffffff8252e0e0>] ? fence_remove_callback+0x70/0x70
[ 1014.288744]  [<ffffffff8252f42c>] fence_default_wait+0x2c/0x30
[ 1014.288746]  [<ffffffff8252e13f>] fence_wait_timeout+0x3f/0x100
[ 1014.288748]  [<ffffffff8252fcf0>]
reservation_object_wait_timeout_rcu+0xa0/0x2c0
[ 1014.288799]  [<ffffffffc03a15af>] nouveau_gem_ioctl_cpu_prep+0x6f/0x120
[nouveau]
[ 1014.288816]  [<ffffffffc022ce76>] drm_ioctl+0x2e6/0x590 [drm]
[ 1014.288843]  [<ffffffffc03a1540>] ? nouveau_gem_ioctl_pushbuf+0x9a0/0x9a0
[nouveau]
[ 1014.288846]  [<ffffffff82020ac6>] ? init_fpu+0x56/0xc0
[ 1014.288848]  [<ffffffff82021b49>] ? __restore_xstate_sig+0x99/0x6b0
[ 1014.288874]  [<ffffffffc0396c98>] nouveau_drm_ioctl+0x68/0xf0 [nouveau]
[ 1014.288877]  [<ffffffff820839c7>] ? __set_task_blocked+0x37/0x80
[ 1014.288879]  [<ffffffff82208b25>] do_vfs_ioctl+0x75/0x320
[ 1014.288881]  [<ffffffff82087408>] ? restore_altstack+0x18/0x30
[ 1014.288884]  [<ffffffff82015238>] ? sys_rt_sigreturn+0xb8/0xd0
[ 1014.288886]  [<ffffffff82208e61>] SyS_ioctl+0x91/0xb0
[ 1014.288889]  [<ffffffff827d176d>] system_call_fastpath+0x16/0x1b


Which basically just means that it's waiting for a fence to be reached, which
in turn means that the GPU hung. GPU hang recovery is... lacking in nouveau.

Were you doing anything in particular in firefox? (Like running a WebGL
testsuite or something)

Does booting with 'nouveau.config=NvMSI=0' help things? I would assume not, but
it's an easy one to knock out.

Lastly, there are some patches eventually destined for 3.19 related to
nvaa/nvac but which haven't made it to Linus's tree yet:

http://cgit.freedesktop.org/nouveau/linux-2.6/log/?h=linux-3.19

(specifically the 3 prefixed with drm/nouveau/fb/ram/mcp77.) Would be great if
you could give those a shot.

Also it'd be nice to verify that 256MB is the correct quantity of stolen memory
to be used as VRAM. This is often configurable from the bios, and you can
probably get that information from the nvidia blob too.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/nouveau/attachments/20141229/23d874f4/attachment-0001.html>