Created attachment 118503 [details]
Running kernel 4.3-rcX I can usually boot to a good nouveau session, however if I reboot the system the display is squashed and ghosted across the screen.
I have a capture of the kernel log showing a FIFO that has failed to reset. Rebooting again doesn't clear the error - nor does shutting down and starting again - I typically need to go and boot an older kernel ubuntu 3.13.0-58-generic in this case. I haven't tested shutting down the system for a prolonged period after the corruption yet.
Attached is the kernel log of
dmesg-4.3.0-rc1.txt (totally broken both screens)
dmesg-4.3.0-rc3.txt (totally broken both screens)
dmesg-4.3.0-rc3-onescreen-good.txt (totally broken on one screen)
Also note this error is readily replicated with one screen present - the laptop display. I'll attach a dump of that too.
Created attachment 118504 [details]
Created attachment 118505 [details]
How are the screens plugged in? Can you provide the dmesg when booted with
This looks like a non-optimus setup, is that right?
Yes, that's a non-optimus setup.
I'll get you that capture. Right now I have this weird artifact on my primary laptop screen that won't go away after booting the system a number of times @ the 4.3.0-rcX kernel - I'm assuming the system isn't actually resetting the nvidia when I power down (some sort of warm boot) - so I've disconnected the power and I'm letting the battery run flat.
I'm attaching a picture of the artifact that persisting through resets (note it's still there even after leaving the system powered off overnight)
Created attachment 118512 [details]
Also useful to know if the issue happens with 4.2. The nouveau driver got basically rewritten in 4.3, a regression easily could have crept in.
Just to confirm.
1. First boot is normal
2. Issue a reboot
3. Get corrupted screen
4. Need to completely allow power to drain (so presumably there is some warm boot foolery going on here with the BIOS when I just do a power down)
Requested dmesg attached.
I'll compile a 4.2 tag and let you know.
Created attachment 118515 [details]