Xv displays flickering pixel garbage (intrepid)

Bug #267297 reported by Johan Kiviniemi
52
Affects Status Importance Assigned to Milestone
xserver-xorg-driver-ati
Fix Released
High
xserver-xorg-video-ati (Ubuntu)
Fix Released
High
Bryce Harrington
Intrepid
Fix Released
High
Bryce Harrington

Bug Description

Binary package hint: xserver-xorg-video-ati

Since the xserver-xorg-video-radeon update from 1:6.9.0+git20080802.1f3eee36-1ubuntu1 to 1:6.9.0+git20080826.a3cc1d7a-2ubuntu1, all video players using Xv began displaying flickering pixel garbage. The corruption fills the overlay horizontally and fills a varying vertical area beginning from the bottom of the overlay.

The flickering seems to happen each time the frame is updated.

01:00.0 VGA compatible controller: ATI Technologies Inc RV350 AP [Radeon 9600]

Revision history for this message
In , agd5f (agd5f) wrote :

Please attach your xorg log and config.

Revision history for this message
In , Paulo Dias (paulo-miguel-dias) wrote :

Created an attachment (id=18459)
xorg.log

Revision history for this message
In , Paulo Dias (paulo-miguel-dias) wrote :

Created an attachment (id=18460)
xorg.conf

Revision history for this message
In , Paulo Dias (paulo-miguel-dias) wrote :

this bug is very similar in behaviour to bug 16845

Revision history for this message
In , Paulo Dias (paulo-miguel-dias) wrote :

similar but not quitte the same. i can see the video, but with odd colors mixed with it, with all players using Xv.. if i use textured video, the video plays without the garbled colors

Revision history for this message
In , Michel-tungstengraphics (michel-tungstengraphics) wrote :

Does it also happen without Option "BackingStore"?

Revision history for this message
In , Michel-tungstengraphics (michel-tungstengraphics) wrote :

Created an attachment (id=18462)
Pass base offset into RADEONDisplayVideo() explicitly

Does this patch fix the problem? If not, please attach a log file captured after reproducing the problem with the patch applied.

Revision history for this message
In , Paulo Dias (paulo-miguel-dias) wrote :

ok, the patch fixes the bug, changing bug status to fixed.

Revision history for this message
In , Paulo Dias (paulo-miguel-dias) wrote :

unfortunatelly with latest git code 6cebfe257f7ddad855ee743e4eb899bd6fac7f46, the bug appears OCASIONALLY with xv, reopening

Revision history for this message
In , Michel-tungstengraphics (michel-tungstengraphics) wrote :

(In reply to comment #8)
> ok, the patch fixes the bug, changing bug status to fixed.

That should only be done once the fix is applied to Git.

(In reply to comment #9)
> unfortunatelly with latest git code 6cebfe257f7ddad855ee743e4eb899bd6fac7f46,
> the bug appears OCASIONALLY with xv, reopening

With the patch applied on top of that commit?

Revision history for this message
In , Paulo Dias (paulo-miguel-dias) wrote :

(In reply to comment #10)
> (In reply to comment #8)
> > ok, the patch fixes the bug, changing bug status to fixed.
>
> That should only be done once the fix is applied to Git.

Yes, i updated to git and reapplied the patch. I thought the bug was fixed, unfortunately although is happens much less its STILL there.

Alex on IRC said it MIGHT be a memory allocation bug, and i tend to agree, since this bug can be triggered randomly in and out in the same X session .
>
>
> (In reply to comment #9)
> > unfortunatelly with latest git code 6cebfe257f7ddad855ee743e4eb899bd6fac7f46,
> > the bug appears OCASIONALLY with xv, reopening
>
> With the patch applied on top of that commit?

Yes. Sorry for the closing and reopening, i should have done more tests (i should known better :P) before closing this bug.

Revision history for this message
In , Michel-tungstengraphics (michel-tungstengraphics) wrote :

(In reply to comment #11)
>
> Alex on IRC said it MIGHT be a memory allocation bug, and i tend to agree,
> since this bug can be triggered randomly in and out in the same X session .

So the suspicion is it's a regression caused by Alex's patch bomb? :) If so, can you try the patch against commit a55e85f742d1334bf88e4681e553f025d2de38df?

Also, I was asking you to provide a log file captured after reproducing the problem with the patch applied.

Revision history for this message
In , agd5f (agd5f) wrote :

(In reply to comment #11)
> Alex on IRC said it MIGHT be a memory allocation bug, and i tend to agree,
> since this bug can be triggered randomly in and out in the same X session .

I didn't say it was a memory allocation bug, I said the corruption could be caused by having to reset the overlay base depending on where the allocation was. That said, it does make sense to rule out my patches.

Revision history for this message
Johan Kiviniemi (ion) wrote :

Binary package hint: xserver-xorg-video-ati

Since the xserver-xorg-video-radeon update from 1:6.9.0+git20080802.1f3eee36-1ubuntu1 to 1:6.9.0+git20080826.a3cc1d7a-2ubuntu1, all video players using Xv began displaying flickering pixel garbage. The corruption fills the overlay horizontally and fills a varying vertical area beginning from the bottom of the overlay.

The flickering seems to happen each time the frame is updated.

01:00.0 VGA compatible controller: ATI Technologies Inc RV350 AP [Radeon 9600]

Revision history for this message
Johan Kiviniemi (ion) wrote :
Revision history for this message
Johan Kiviniemi (ion) wrote :
Revision history for this message
A. Tombol (atombol) wrote :

I have the same problem with kubuntu intrepid alpha6, xserver-xorg-video-radeon version 1:6.9.0+git20080826.a3cc1d7a-2ubuntu3

Revision history for this message
In , Paulo Dias (paulo-miguel-dias) wrote :

with latest commit: d0d58b39e49c5ce00bc8bd12f721ad8c7f554b91
i cant reproduce this bug anymore. im not saying im 100% sure its gone, im just saying i cant seem to trigger it.

if no one else complains i think we can close it.

best regards

Revision history for this message
Wouter Stomp (wouterstomp-deactivatedaccount) wrote :

Can you also attach the output of running lspci from the commandline? Thanks.

Revision history for this message
In , Michel-tungstengraphics (michel-tungstengraphics) wrote :

Is that still with the patch applied? I don't see anything in Git that could address this...

Revision history for this message
In , Paulo Dias (paulo-miguel-dias) wrote :

Its without the patch, i think the problem was only active if you enabled the backing store (which leads to a series of other problems) :P

Revision history for this message
In , Bugzi09-fdo-tormod (bugzi09-fdo-tormod) wrote :

With latest git (d82f2938...) I still see these coloured lines using XAA (EXA is fine). Last time I checked (see bug 16845) the patch here fixed the issue.

Revision history for this message
A. Tombol (atombol) wrote :

01:00.0 VGA compatible controller: ATI Technologies Inc RV350 AR [Radeon 9600]
01:00.1 Display controller: ATI Technologies Inc RV350 AR [Radeon 9600] (Secondary)

Revision history for this message
In , Michel-tungstengraphics (michel-tungstengraphics) wrote :

(In reply to comment #16)
> Its without the patch, i think the problem was only active if you enabled the
> backing store (which leads to a series of other problems) :P

That's unlikely to be directly related; you probably just got (un)lucky.

Anyway, I've pushed the patch as commit c359c2a31caf9f75b9fc6b6bcbc3e9dc1fe404ba, with the debugging output unconditional for now. Please don't reopen without attaching a log file captured after reproducing the problem with this fix.

Revision history for this message
sge_kane (sebastian-kannengiesser+launchpad) wrote :

confirmation from here... exact same issue, xv unusable in intrepid alpha 6...

any idea, where the issue is coming from?

Revision history for this message
Bryce Harrington (bryce) wrote :

Can you confirm that reverting back to 1:6.9.0+git20080802.1f3eee36-1ubuntu1 makes the issue go away?

Also, can you provide 'lspci -vvnn'? The generic lspci output doesn't provide the pci id's

Changed in xserver-xorg-video-ati:
assignee: nobody → bryceharrington
importance: Undecided → High
status: New → Triaged
Revision history for this message
Bryce Harrington (bryce) wrote :

Also, I noticed this in the log:

(II) RADEON(0): XAA Render acceleration unsupported on Radeon 9500/9700 and newer. Please use EXA instead.
(II) RADEON(0): Render acceleration disabled
(II) RADEON(0): num quad-pipes is 1
(II) RADEON(0): Using XFree86 Acceleration Architecture (XAA)

Does turning on EXA in xorg.conf make the issue go away? If so, perhaps this is a dupe of #267612

Revision history for this message
Bryce Harrington (bryce) wrote :

Another thing to try (mentioned in another dupe) is:

Option "DMAForXV" "off"

Revision history for this message
Bryce Harrington (bryce) wrote :

269357 may be another dupe of this issue. Sounds like we may need to have certain chipsets use EXA. 'lspci -vvnn' will be important for determining this.

Changed in xserver-xorg-driver-ati:
status: Unknown → Fix Released
Revision history for this message
Tormod Volden (tormodvolden) wrote :

To confirm the upstream fix, you may try the -ati packages in my PPA.

Revision history for this message
A. Tombol (atombol) wrote :

Option "AccelMethod" "EXA" pretty much solved the issue, but it's not perfect
sometimes there's some garbage in the windows, or in the place of minimized windows on the desktop
one of the videos i ran for testing also had some garbage on it, (different from the original bug) which disappeared after re-opening

Revision history for this message
A. Tombol (atombol) wrote :
Revision history for this message
A. Tombol (atombol) wrote :

After a little longer testing I have to say that EXA causes high Xorg usage and laggy desktop for me.
I've disabled it again for now. Tried Option "DMAForXV" "off", but that doesn't solve the original issue.

Revision history for this message
A. Tombol (atombol) wrote :

I've installed xserver-xorg-video-radeon_6.9.0+git20080930.c359c2a3-0ubuntu0tormod_i386.deb from Tormod's PPA.
Now xv is fine, and Xorg doesn't consume so high CPU.
Although "(II) RADEON(0): XAA Render acceleration unsupported on Radeon 9500/9700 and newer. Please use EXA instead." is still in xorg log.
Thank you for the help.

Revision history for this message
Johan Kiviniemi (ion) wrote :

Tormod’s package fixed the problem for me as well.

Revision history for this message
Bryce Harrington (bryce) wrote :

Excellent, thanks. There's five changesets in that package, one of which is the fix for fdo #17254 which we already identified as the upstream of this bug. I'll cherrypick that fix.

Revision history for this message
kelargo (kelong-2000) wrote :

I think I have this bug, too. I just upgraded to Interpid.
Using 1:6.9.0+git20080826.a3cc1d7a-2ubuntu3 (intrepid)
When I went from Hardy to Intrepid, I had to install the ATI driver. The flgr driver disappeared ??

When Intrepid first boots, the display flickers. It tries to display at 1900x1200 (my monitor's resolution)
Then in between flickers, I have to go into the K launcher and select the Display properties.
The resolution goes to a newer value and then everything is more or less ok.

The setting disappears after a reboot. I have to go through the process of resetting the display resolution.

hope this helps! tia!

lspci -vvnn

01:05.0 VGA compatible controller [0300]: ATI Technologies Inc Radeon HD 3200 Graphics [1002:9610]
        Subsystem: Giga-byte Technology Device [1458:d000]
        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, Cache Line Size: 4 bytes
        Interrupt: pin A routed to IRQ 18
        Region 0: Memory at d0000000 (32-bit, prefetchable) [size=256M]
        Region 1: I/O ports at ee00 [size=256]
        Region 2: Memory at fdee0000 (32-bit, non-prefetchable) [size=64K]
        Region 5: Memory at fdd00000 (32-bit, non-prefetchable) [size=1M]
        Capabilities: [50] Power Management version 3
                Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [a0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
                Address: 0000000000000000 Data: 0000

Revision history for this message
Bryce Harrington (bryce) wrote :

Hi Johan,

I've built a package with the patch included which in theory should solve the issue. Would you mind testing and validating that it does indeed fix it?

http://www.bryceharrington.org/ubuntu/Ati/xserver-xorg-video-ati_6.9.0+git20080826.a3cc1d7a-2ubuntu4~bwh2_i386.deb

If you need the amd64 package or need the dbg symbols, those debs are at http://www.bryceharrington.org/ubuntu/Ati as well.

Changed in xserver-xorg-video-ati:
status: Triaged → Fix Committed
Revision history for this message
Bryce Harrington (bryce) wrote :

kelargo, from your description you have some bug other than this one. This bug only shows flickering when playing Xv. You should probably file that as a new bug, via `ubuntu-bug xserver-xorg-video-ati`.

And yes, -fglrx is not yet available for Intrepid users.

Revision history for this message
sge_kane (sebastian-kannengiesser+launchpad) wrote :

Tormods ...0930.deb solved it here... Your patched version Bryce still has the same issue...

By the way, I have this card:

01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Radeon RV250 [Mobility FireGL 9000] [1002:4c66] (rev 01)
 Subsystem: Compaq Computer Corporation Device [0e11:0860]
 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: 128 (2000ns min), Cache Line Size: 32 bytes
 Interrupt: pin A routed to IRQ 10
 Region 0: Memory at 98000000 (32-bit, prefetchable) [size=128M]
 Region 1: I/O ports at 3000 [size=256]
 Region 2: Memory at 90400000 (32-bit, non-prefetchable) [size=64K]
 [virtual] Expansion ROM at 90420000 [disabled] [size=128K]
 Capabilities: <access denied>
 Kernel modules: radeonfb

Revision history for this message
kelargo (kelong-2000) wrote :

ok, thanks. Bug #276903:

Revision history for this message
Bryce Harrington (bryce) wrote :

Hmm, that's rather surprising that the patched driver didn't solve the issue.

Well, here's another one that pulls in the atom bios changes as well. None of the other changes in the 0930 deb look like they'd matter for video issues.

http://bryceharrington.org/ubuntu/AtiBug267297/

Please test this deb and let me know if it solves the issue.

Johan, I'd also like to hear your results from testing http://www.bryceharrington.org/ubuntu/Ati/xserver-xorg-video-ati_6.9.0+git20080826.a3cc1d7a-2ubuntu4~bwh2_i386.deb as well.

Changed in xserver-xorg-video-ati:
status: Fix Committed → In Progress
Revision history for this message
sge_kane (sebastian-kannengiesser+launchpad) wrote :

Hi Bryce,

that package solves the issue. Just out of interest, why not take the upstream version here, i.e. as i've understood Tormod's deb? Thanks for your work on it.

Revision history for this message
Bryce Harrington (bryce) wrote :

Thanks for confirming those two patches fix it.

Well, I wanted to understand *what* changes fixed the bug, so I'm not just blindly copying a new upstream version and risking adding regressions for some people.

However, I understand all the other changes aside from the atom bios patch, and they seem safe. I'd hoped to cherrypick them, and avoid the atom bios changes (and thus risk any chance of regressions), but since we can't, I guess there's not much reason not to take a newer git version. While I can't prove it 100%, I trust the atom bios patch is safe and doubt we'll see much regression risk.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package xserver-xorg-video-ati - 1:6.9.0+git20081003.f9826a56-0ubuntu1

---------------
xserver-xorg-video-ati (1:6.9.0+git20081003.f9826a56-0ubuntu1) intrepid; urgency=low

  * Pull upstream snapshot, up to commit f9826a56 (LP: #277104)
    - Add support for DDC via atom commands for RV410 (LP: #227520?)
    - man page updates (fdo #17887)
    - Make initial rotation work, by initializing acceleration _before_
      setting the mode
    - Fix Xv video corruption by passing base offset into
      RADEONDisplayVideo() explicitly (fdo #17254, LP: #267297)
    - Fix sync-to-vblank hangs after mode switch with DRM vblank-rework.
    - pll adjustments
    - Add quirk to fix macbook hardware (fdo #17625)
  * Drop 103_rotation_reset.patch - already upstream

 -- Bryce Harrington <email address hidden> Fri, 03 Oct 2008 18:56:44 -0700

Changed in xserver-xorg-video-ati:
status: In Progress → Fix Released
Changed in xserver-xorg-driver-ati:
importance: Unknown → High
Changed in xserver-xorg-driver-ati:
importance: High → Unknown
Changed in xserver-xorg-driver-ati:
importance: Unknown → High
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.