https://bugzilla.novell.com/show_bug.cgi?id=844325 https://bugzilla.novell.com/show_bug.cgi?id=844325#c0 Summary: linux-3.12.0 rc3 nouveau: screen corruption after resume Classification: openSUSE Product: openSUSE Factory Version: 13.1 Beta 1 Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: rcoe@wi.rr.com QAContact: qa-bugs@suse.de Found By: --- Blocker: --- Created an attachment (id=561707) --> (http://bugzilla.novell.com/attachment.cgi?id=561707) display corruption User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:23.0) Gecko/20100101 Firefox/23.0 I had this issue on linux-3.12.0-rc2 and thought it had been fixed in linux-3.12.0-rc3, but it just happened again. I installed linux kernel 3.12 from http://download.opensuse.org/repositories/Kernel:/HEAD/standard/ to debug and test another issue on opensuse 12.3. I dock my laptop after using it for two days undocked. The resume is normal, and I start the netork. I enabled the second monitor with xrandr --output LVDS-1 --auto xrandr --output DP-2 --auto xrandr --output DP-2 --primary --output LVDS-1 --right-of DP-2 Both displays are funky -- parts of windows in blocks are displayed all over, like in the attached picture. I attempt to switch back to one monitor xrandr --output LVDS-1 --primary --output DP-2 --off xrandr --fb 1600x900 The second monitor turns off, but the primary display is still messed up. If I stop Xorg, and it restarts, the following messages are in the kernel log [276069.408906] nouveau E[ PDISP][0000:01:00.0] chid 1 mthd 0x0080 data 0x00000000 0x000b5080 [276247.160437] nouveau E[ PDISP][0000:01:00.0] chid 1 mthd 0x0080 data 0x00000000 0x100b5080 [276415.088799] nouveau E[ PDISP][0000:01:00.0][0xc000857d][ffff88021d083640] channel stalled Reproducible: Always Steps to Reproduce: 1. resume laptop 2. enable 2 monitors -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.