Still present in 3.13.2-gentoo. I found that -EBUSY returns from nv50_fbcon_imageblit.
> what is wrong in nouveau's way of setting up pgraph.
Does it mean that the bug somewhere in nv50_grctx_generate? Just to be sure that bug in this function, is it possible to replace it using data from mmiotrace of nvidia driver? For me it is not obvious how to modificate nv50_grctx_fill in that case, what nv50_grctx_init should write to *size and, after all, may it help somehow?
Still present in 3.13.2-gentoo. I found that -EBUSY returns from nv50_fbcon_ imageblit.
> what is wrong in nouveau's way of setting up pgraph. generate? Just to be sure that bug in this function, is it possible to replace it using data from mmiotrace of nvidia driver? For me it is not obvious how to modificate nv50_grctx_fill in that case, what nv50_grctx_init should write to *size and, after all, may it help somehow?
Does it mean that the bug somewhere in nv50_grctx_