Hide Forgot
Created attachment 486643 [details] dmesg after bootup I get regular X lockups during normal operation. I can reproduce this best when moving libreoffice windows between screens but this also happens randomly. I can still move the mouse cursor within a limited range of the screen the pointer is located on. Everything else locks. [ 335.824559] [drm] nouveau 0000:03:00.0: PGRAPH_TRAP_TPDMA_2D - TP 0 - Unknown fault at address 0040fce100 [ 335.824564] [drm] nouveau 0000:03:00.0: PGRAPH_TRAP_TPDMA_2D - TP 0 - e0c: 00000000, e18: 00000000, e1c: 00040000, e20: 00000037, e24: 0c030000 [ 335.824570] [drm] nouveau 0000:03:00.0: PGRAPH - TRAP [ 335.824574] [drm] nouveau 0000:03:00.0: PGRAPH - ch 3 (0x0000f00000) subc 2 class 0x502d mthd 0x0860 data 0x7f7fffff [ 335.824582] [drm] nouveau 0000:03:00.0: VM: trapped write at 0x004015d200 on ch 3 [0x00000f00] PGRAPH/PROP/DST2D reason: PAGE_NOT_PRESENT [ 335.917515] [drm] nouveau 0000:03:00.0: PGRAPH_TRAP_TPDMA_2D - TP 0 - Unknown fault at address 0040fa0100 [ 335.917520] [drm] nouveau 0000:03:00.0: PGRAPH_TRAP_TPDMA_2D - TP 0 - e0c: 00000000, e18: 00000000, e1c: 00040000, e20: 00000037, e24: 0c030000 [ 335.917526] [drm] nouveau 0000:03:00.0: PGRAPH - TRAP [ 335.917531] [drm] nouveau 0000:03:00.0: PGRAPH - ch 3 (0x0000f00000) subc 2 class 0x502d mthd 0x083c data 0x0000001a [ 335.917539] [drm] nouveau 0000:03:00.0: VM: trapped write at 0x0040fa0100 on ch 3 [0x00000f00] PGRAPH/PROP/DST2D reason: PAGE_NOT_PRESENT kernel-2.6.38-1.fc15.x86_64 xorg-x11-drv-nouveau-0.0.16-23.20110303git92db2bc.fc15.x86_64
Created attachment 486645 [details] lspci -vvv
Created attachment 486646 [details] x11 configuration
Created attachment 486647 [details] xorg log
I believe this is likely the same bug I fixed upstream yesterday. It's a long-standing 2D driver bug that only just got exposed (due to the result being much more obvious now) by 2.6.38. There's a F15 build at http://koji.fedoraproject.org/koji/buildinfo?buildID=235224 (xorg-x11-drv-nouveau-0.0.16-24.20110324git8378443.fc15) that contains the fix. Can you give it a shot please?
I installed your build yesterday and did not see the error for the hour or so I did some testing... I will put it to some more in depth testing today and give you more feedback. Thanks!