search for: 000001f9

Displaying 3 results from an estimated 3 matches for "000001f9".

Did you mean: 000001f6
2018 Apr 04
2
nouveau TRAP_M2MF still there on G98
...95] nouveau 0000:01:00.0: fifo: DMA_PUSHER - ch 2 [Xorg[2667]] get 0000037d90 put 000003a2cc ib_get 000001dc ib_put 000001dd state 80004861 (err: INVALID_CMD) push 00704031 [29982.027959] nouveau 0000:01:00.0: fifo: DMA_PUSHER - ch 2 [Xorg[2667]] get 000003a2cc put 000003a2cc ib_get 000001dc ib_put 000001f9 state 80000000 (err: INVALID_CMD) push 00406040 [29982.044136] nouveau 0000:01:00.0: gr: DATA_ERROR 00000004 [INVALID_VALUE] [29982.050934] nouveau 0000:01:00.0: gr: 00100000 [] ch 2 [001fa31000 Xorg[2667]] subc 2 class 502d mthd 0218 data ff000000 [29982.061866] nouveau 0000:01:00.0: gr: DATA_ERRO...
2018 Apr 04
0
nouveau TRAP_M2MF still there on G98
...00.0: fifo: DMA_PUSHER - ch 2 [Xorg[2667]] get > 0000037d90 put 000003a2cc ib_get 000001dc ib_put 000001dd state 80004861 (err: > INVALID_CMD) push 00704031 > [29982.027959] nouveau 0000:01:00.0: fifo: DMA_PUSHER - ch 2 [Xorg[2667]] get > 000003a2cc put 000003a2cc ib_get 000001dc ib_put 000001f9 state 80000000 (err: > INVALID_CMD) push 00406040 These, as I call them, 406040 errors, have been around on Tesla for ages. We have no idea what leads to them, but generally some kind of fifo desync appears to follow. -ilia
2018 Apr 03
2
nouveau TRAP_M2MF still there on G98
Hi! In commit da5e45e619b3f101420c38b3006a9ae4f3ad19b0: > drm/nouveau/mmu: ALIGN_DOWN correct variable > > Commit 7110c89bb8852ff8b0f88ce05b332b3fe22bd11e ("mmu: swap out round > for ALIGN") replaced two calls to round/rounddown with ALIGN/ALIGN_DOWN, > but erroneously applied ALIGN_DOWN to a different variable (addr) and left > intended variable (tail) not