Bug#534133: Bug#523415: corrupted rendering

[Kurt Roeckx <kurt@roeckx.be>]

On Mon, Jun 15, 2009 at 11:49:56PM +0200, Kurt Roeckx wrote:
> > 
> > The released 2.6.30 seems to be fixing that issue too.  Currently
> > don't see anything wrong.
> 
> Of course it starts just after you send a mail.

So since version 2.6.29 I see random corruption on my screen in X,
but not on the console (with a framebuffer).

I have an intel 82830 chipset:
0:02.0 0300: 8086:3577 (rev 03) (prog-if 00 [VGA controller])
        Subsystem: 1043:1492
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Interrupt: pin A routed to IRQ 10
        Region 0: Memory at f0000000 (32-bit, prefetchable) [size=128M]
        Region 1: Memory at e7800000 (32-bit, non-prefetchable) [size=512K]
        Expansion ROM at <unassigned> [disabled]
        Capabilities: [d0] Power Management version 1
                Flags: PMEClk- DSI+ D1+ D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:02.1 0380: 8086:3577
        Subsystem: 1043:1492
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0 (2500ns max)
        Region 0: Memory at e8000000 (32-bit, prefetchable) [size=128M]
        Region 1: Memory at e7000000 (32-bit, non-prefetchable) [size=512K]
        Capabilities: [d0] Power Management version 1
                Flags: PMEClk- DSI+ D1+ D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-


In 2.6.30 I mostly see things like text where it shouldn't be, pixels not being drawn, text just not shown,
...


Please let me know if you need any other info.


Kurt