https://bugs.freedesktop.org/show_bug.cgi?id=54681
--- Comment #1 from Robert Hancock <[email protected]> --- This bug is still occurring with kernel-3.6.6-1.fc17.x86_64 and xorg-x11-drv-nouveau-0.0.16-37.20120306gitf5d1cd2.fc17.x86_64. I also get errors like this sometimes when the crash occurs: [Nov 13 19:01:29 newcastle kernel: [ 41.878583] [drm] nouveau 0000:01:00.0: EvoCh 2 Mthd 0x0080 Data 0x00000000 (0x000b 0x05) Nov 13 19:01:30 newcastle kernel: [ 42.458475] [drm] nouveau 0000:01:00.0: EvoCh 2 Mthd 0x0080 Data 0x00000000 (0x100b 0x05) Nov 13 19:01:36 newcastle kernel: [ 48.447320] [drm] nouveau 0000:01:00.0: EvoCh 2 Mthd 0x0080 Data 0x00000000 (0x100b 0x05) Nov 13 19:01:47 newcastle kernel: [ 59.468318] [drm] nouveau 0000:01:00.0: Failed to idle channel 2. Nov 13 19:01:50 newcastle kernel: [ 62.533759] [drm] nouveau 0000:01:00.0: Failed to idle channel 4. Nov 13 19:01:59 newcastle kernel: [ 68.933395] [drm] nouveau 0000:01:00.0: EvoCh 2 Mthd 0x0080 Data 0x00000000 (0x100b 0x05) I realized that I had my main monitor connected to what the driver calls DVI-I-2 and the TV connected to DVI-I-1. If I reverse the connections to put the TV on port 2 instead, it works a bit better in that I can connect/disconnect the TV and extend the display onto it without things blowing up. But doing things in the Display app like disabling the main monitor and using just the TV, then disabling the TV and turning the monitor back on, will trigger such crashes again. -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Nouveau mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/nouveau
