Created attachment 40499 [details] graphic corruptions after I switched back to :0 directly after starting :1 I am getting corrupted graphics on display :0 as soon as I start another session. I am not getting corrupted graphics on the second display :1. This is on a ThinkPad T42 with with Radeon KMS: 00:01.0 PCI bridge: Intel Corporation 82855PM Processor to AGP Controller (rev 03) (prog-if 00 [Normal decode]) 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: 96 Bus: primary=00, secondary=01, subordinate=01, sec-latency=64 I/O behind bridge: 00003000-00003fff Memory behind bridge: c0100000-c01fffff Prefetchable memory behind bridge: e0000000-e7ffffff Secondary status: 66MHz+ FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- <SERR- <PERR- BridgeCtl: Parity- SERR- NoISA+ VGA+ MAbort- >Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- 01:00.0 VGA compatible controller: ATI Technologies Inc RV350 [Mobility Radeon 9600 M10] (prog-if 00 [VGA controller]) Subsystem: IBM Device 0550 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B+ DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 66 (2000ns min), Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 11 Region 0: Memory at e0000000 (32-bit, prefetchable) [size=128M] Region 1: I/O ports at 3000 [size=256] Region 2: Memory at c0100000 (32-bit, non-prefetchable) [size=64K] [virtual] Expansion ROM at c0120000 [disabled] [size=128K] Capabilities: [58] AGP version 2.0 Status: RQ=80 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW+ AGP3- Rate=x1,x2,x4 Command: RQ=32 ArqSz=0 Cal=0 SBA+ AGP+ GART64- 64bit- FW- Rate=x4 Capabilities: [50] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Kernel driver in use: radeon And kernel: martin@shambhala:~> cat /proc/version Linux version 2.6.36-tp42-gtt-vram-apart-v2-dirty (martin@shambhala) (gcc version 4.4.5 (Debian 4.4.5-4) ) #1 PREEMPT Thu Oct 21 12:10:49 CEST 2010 (which is a plain 2.6.36 with second last patch I think to fix bug #28402) And the following userspace: martin@shambhala:~> apt-show-versions | egrep "(xserver-xorg/|xserver-xorg-core/|xserver-xorg-video-radeon/|libgl1-mesa-dri/|kdelibs5/|kde-window-manager/|libqt4-gui/)" kde-window-manager/experimental-snapshots uptodate 4:4.5.1-0r2 kdelibs5/experimental-snapshots uptodate 4:4.5.3-0r1 libgl1-mesa-dri/experimental uptodate 7.9+repack-1 libqt4-gui/squeeze uptodate 4:4.6.3-4 xserver-xorg/squeeze uptodate 1:7.5+8 xserver-xorg-core/squeeze uptodate 2:1.7.7-9 xserver-xorg-video-radeon/squeeze uptodate 1:6.13.1-2+squeeze1 I am using KDE 4.5 with OpenGL compositing enabled on both sessions. But graphics corruption on display :0 also happens, when I start GNOME without compositing on the second display :1.
Created attachment 40500 [details] it gets worse after some time graphics corruption get worse after some time.
Hmmm, now I get graphics corruption on the second display as well. So it does not seem to be limited to the first display
Its difficult to say, when this last did not happen. It certainly didn't happen without before I enabled Radeon KMS on kernel 2.6.33. But I think I didn't see this in 2.6.33 either. Then bug #28402 let me skip some kernel versions. I am not sure about 2.6.35 with patch for bug #28402 tough. Even more difficult to say for userspace versions.
Ok, these corruption does not seem to appear when I disabled compositing by pressing Alt-Shift-F12 on display :0 and shortly after I start the second KDE session on display :1 as well. So this seems to be related to having to instances of Radeon KMS X.org displays running at the same time. Since I already tried with :1 without compositing, it might be sufficient, when :0 runs without compositing. I try with :0 without and :1 with compositing after I am confident that both without compositing run stable. Bug 23622 - probably radeon kms / memory shortage related scheduling while atomic https://bugzilla.kernel.org/show_bug.cgi?id=23622 might be related to this one. I will also compile a 2.6.37-rc3 and test it as well.
Currently testing with 2.6.37-rc3. Running two sessions for about an hour and no graphics corruption yet. So there is hope that this issue has been fixed in the meanwhile. Thanks.
Two quick. Graphics corruption still happened, it took a bit longer but then some small corruptions appeared and it got worse again. Thus disabling compositing on both desktops for now. That appears to work.
Hmmm, it seems to me, that graphics corruptions occur after the first TTM memory allocation failure messages which I reported to Bug 23622 - probably radeon kms / memory shortage related scheduling while atomic https://bugzilla.kernel.org/show_bug.cgi?id=23622
Mass closure: This bug has been untouched for more than six years, and is not obviously still valid. Please reopen this bug or file a new report if you continue to experience issues with current releases.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.