When using fedora nouveau code, it's usually advised to use fedora bug report.
People following this bug tracker might expect you to run latest git of all nouveau components : http://nouveau.freedesktop.org/wiki/InstallNouveau
(two main reasons for that : 1) git is usually better and has more fixes 2) we do not know what code exactly nouveau is shipping)
However, according to mwk, the data error is unlikely to be related to the hangs. Also he believes he might have the same problem using recent nouveau code. To confirm that, he would like to know the value of the 400700 register next time the machine hangs :
$ wget http://0x04.net/~mwk/pgtest/{peek.c,libio.{c,h}}
$ gcc peek.c libio.c -lpciaccess -o peek
# ./peek 0x400700
This seems related to two existing fedora bugs : /bugzilla. redhat. com/show_ bug.cgi? id=567412 /bugzilla. redhat. com/show_ bug.cgi? id=566987
https:/
https:/
When using fedora nouveau code, it's usually advised to use fedora bug report. nouveau. freedesktop. org/wiki/ InstallNouveau
People following this bug tracker might expect you to run latest git of all nouveau components :
http://
(two main reasons for that : 1) git is usually better and has more fixes 2) we do not know what code exactly nouveau is shipping)
As said in https:/ /bugzilla. redhat. com/show_ bug.cgi? id=567412# c6 , using the latest git of xf86-video-nouveau would at least fix the DATA ERROR you see in kernel log and rules that out.
However, according to mwk, the data error is unlikely to be related to the hangs. Also he believes he might have the same problem using recent nouveau code. To confirm that, he would like to know the value of the 400700 register next time the machine hangs : 0x04.net/ ~mwk/pgtest/{peek.c, libio.{ c,h}}
$ wget http://
$ gcc peek.c libio.c -lpciaccess -o peek
# ./peek 0x400700