Bug 62681 - linux-3.12.0 rc3 nouveau: screen corruption after resume
Summary: linux-3.12.0 rc3 nouveau: screen corruption after resume
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: Video(DRI - non Intel) (show other bugs)
Hardware: x86-64 Linux
: P1 high
Assignee: drivers_video-dri
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-10-07 16:37 UTC by Rich Coe
Modified: 2013-10-16 15:53 UTC (History)
0 users

See Also:
Kernel Version: 3.12
Subsystem:
Regression: Yes
Bisected commit-id:

Attachments
shows display corruption (127.90 KB, image/jpeg)
2013-10-07 16:37 UTC, Rich Coe 		Details
Add an attachment (proposed patch, testcase, etc.)

Description Rich Coe 2013-10-07 16:37:24 UTC 
Created attachment 110381 [details]
shows display corruption

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 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
Comment 1 Rich Coe 2013-10-16 15:53:24 UTC 
I found https://bugs.freedesktop.org/show_bug.cgi?id=69982 
which suggests booting with nouveau.config=NvMSI=0 

I haven't tried it yet, as I've been currently running under 
boot parameter nouveau.noaccel=1, and the system hasn't crashed yet.
Note You need to log in before you can comment on or make changes to this bug.