(--) PCI:*(0:0:2:0) 8086:27a2:17aa:201a Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller rev 3, Mem @ 0xee100000/524288, 0xd0000000/268435456, 0xee200000/262144, I/O @ 0x00001800/8
During regular computer use (web browsing, vim in console, compiling stuff) screen gets intermittently filled with single colour and stays like that. Not even VT-switching helps.
Everything else seems to be working fine behind this "colourful blanket" as I am able to switch to console, blindly log in as root and type `pm-suspend` :) Resuming from suspend fortunately fixes the display.
Also, this seems to be a regression after upgrading from 2.8.x to 2.9..
Few more things about this issue:
1) One things that seems to be causing the total blackout is when a browser (Webkit-gtk+epiphany) is loading image and displaying it while it loads (I think it is called sequential loading - ie you can see how new lines appear on image)
2) Sometimes when I compile something and there's lots of traffic in terminal (gnome-terminal), some parts of the display shift a bit or just go black (I don't remember seeing any other colours). This corruption is cleared when I either press alt+tab or switch to another workspace.
And I have also dumped GPU contents from few blackouts (don't remember the exact colour, though..)
These are ~month old... if needed I could create some newer ones ;)
Created attachment 31048 [details]
photo of screen showing corruption
The bottom part of the screen is blacked out, and part of the middle screen is switched left (also left side of the terminal is visible on the right side of the screen)
There's also slight corruption on the titlebar of the browser on the background.
What kernel are you using? Linus's tree has some fixes for the flicker...
Currently 2.6.32-rc5-00053-gd995053, but will try a newer one...
Pulled latest kernel and had no luck reproducing these issues :(
I will reopen the bug when I run into this issue again :)
The major issue - screen gets filled with single colour, still occurs with latest kernel.
Fortunately I haven't yet noticed screen corruption.
This was still happening under mesa-7.6.
I also tried to watch a movie today on this laptop and during first 10 minutes of watching I had to go through 3 or 4 suspend cycles :S
Any ideas how to debug it?
Tried testing with external monitor.
It seems that external monitor (VGA1) is not affected by this issue.
I connected external display after I had got a blank screen and this was working fine. I even tried switching back and forth between the displays with Fn+F7 key (this is Lenovo X60s laptop).
Next I tried watching some movies on external display (usually this triggers the screen blanking quite easily), but forunately had no success...
So this issue apparently affects only internal screen (LVDS1).
I tried updating the whole stack, but this is still happening:
Things work fine with kernel 2.6.31-rc5-00470-g85dfd81, so I assume this is actually problem with kernel bits.
No more issues since 2.6.33-rc1-00266-gf42ecb2 :)
(In reply to comment #12)
> No more issues since 2.6.33-rc1-00266-gf42ecb2 :)
I was a bit too hasty here. Apparently everything works fine until first suspend.
After resume, I can notice flicker and these spurious screen blankings.
> --- Comment #13 from Priit Laes (irc: plaes) <email@example.com> 2009-12-24 00:53:53 PST ---
> I was a bit too hasty here. Apparently everything works fine until first
> After resume, I can notice flicker and these spurious screen blankings.
I'm told this might be fixed by the following commit in Eric's tree:
Author: Jesse Barnes <firstname.lastname@example.org>
Date: Thu Dec 17 11:11:13 2009 -0800
drm/i915: remove render reclock support
Didn't have time to test myself yet though... Hopefully that will be
backported to 2.6.32.x at some point.
(In reply to comment #14)
> > --- Comment #13 from Priit Laes (irc: plaes) <email@example.com> 2009-12-24 00:53:53 PST ---
> > I was a bit too hasty here. Apparently everything works fine until first
> > suspend.
> > After resume, I can notice flicker and these spurious screen blankings.
> I'm told this might be fixed by the following commit in Eric's tree:
> commit cf74ecbbff3e3b45bae61d28d2220f74d853e2f0
> Author: Jesse Barnes <firstname.lastname@example.org>
> Date: Thu Dec 17 11:11:13 2009 -0800
> drm/i915: remove render reclock support
> Didn't have time to test myself yet though... Hopefully that will be
> backported to 2.6.32.x at some point.
I tried this patch out, but this doesn't fix this issue :(
have same issue.
*** Bug 25964 has been marked as a duplicate of this bug. ***
As pointed out by jcristau:
Adding i915.powersave=0 works around this issue.
*** This bug has been marked as a duplicate of bug 24314 ***
on Jan 20, 2017 at 14:03:24.
(provided by the Example extension).