https://bugs.freedesktop.org/show_bug.cgi?id=36934

--- Comment #2 from almos aaalmosss@gmail.com 2011-05-13 03:36:35 PDT --- Created an attachment (id=46675) --> (https://bugs.freedesktop.org/attachment.cgi?id=46675) Xorg.0.log

https://bugs.freedesktop.org/show_bug.cgi?id=36934

--- Comment #4 from almos aaalmosss@gmail.com 2011-05-13 03:38:10 PDT --- Created an attachment (id=46677) --> (https://bugs.freedesktop.org/attachment.cgi?id=46677) glxinfo

https://bugs.freedesktop.org/show_bug.cgi?id=36934

--- Comment #6 from almos aaalmosss@gmail.com 2011-08-03 05:22:44 PDT --- I observed that this corruption is often accompanied by these messages on the console from which I start a game: radeon: mmap failed, errno: 1 Mesa: User error: GL_OUT_OF_MEMORY in glTexImage radeon: mmap failed, errno: 1 radeon: mmap failed, errno: 1 radeon: mmap failed, errno: 1 radeon: mmap failed, errno: 1 radeon: mmap failed, errno: 1 radeon: mmap failed, errno: 1 radeon: mmap failed, errno: 1 radeon: mmap failed, errno: 1 radeon: mmap failed, errno: 1

Some of the corruption disappears after a suspend-resume cycle. Can this be a memory-accounting bug?

A possibly unrelated question: what happens if the scene to be rendered needs more than VRAM+GART amount of data?

https://bugs.freedesktop.org/show_bug.cgi?id=36934

Michel Dänzer michel@daenzer.net changed:

What |Removed |Added ---------------------------------------------------------------------------- Attachment #46676|application/octet-stream |text/plain mime type| |

https://bugs.freedesktop.org/show_bug.cgi?id=36934

--- Comment #7 from Michel Dänzer michel@daenzer.net 2011-08-09 03:34:33 PDT --- (In reply to comment #6)

I observed that this corruption is often accompanied by these messages on the console from which I start a game:

What exactly does 'often' mean? If it's not always, it probably can't (fully) explain the problem...

radeon: mmap failed, errno: 1 Mesa: User error: GL_OUT_OF_MEMORY in glTexImage

Looks like this app ran out of memory. (errno: 1 means EPERM, not sure how that can happen...)

A possibly unrelated question: what happens if the scene to be rendered needs more than VRAM+GART amount of data?

It's up to the userspace drivers to split it up into smaller chunks that can fit.

A couple of random things to try would be radeon.agpmode=4 and =-1, disabling tiling, ... Trying a newer kernel and possibly r300g driver probably wouldn't hurt either.

https://bugs.freedesktop.org/show_bug.cgi?id=36934

--- Comment #9 from almos aaalmosss@gmail.com 2011-08-30 14:51:08 PDT --- Created an attachment (id=50722) --> (https://bugs.freedesktop.org/attachment.cgi?id=50722) corrupted image in firefox

Now I found a good example of this corruption. When Firefox displays a large image it is frequently filled with garbage, and due to the size of the image, it is clearly visible that the garbage is the remnants of previously displayed images. I think the newly created surfaces in texture-from-pixmap operations are not flushed properly. Or something like that.

In the attachment http://static.szanalmas.hu/postpix/71876_1.jpg should be shown (don't worry it doesn't make any sense even in Hungarian). The startled Misato is the actual desktop background (with the folderview plasmoid in the upper left corner), the '1' in the green circle is a frame from a recently played youtube video, and some of the other garbage are also identifiable.

After a few tab switches this image got clear, but doing a back-forward on that tab made it filled with different garbage. I think redrawing the image clears it, and a realloc leaves it uninitialized again.

https://bugs.freedesktop.org/show_bug.cgi?id=36934

--- Comment #11 from almos aaalmosss@gmail.com 2011-09-13 14:59:31 PDT --- (In reply to comment #10)

(In reply to comment #7)

...

A couple of random things to try would be radeon.agpmode=4 and =-1, disabling tiling, ...

Have you tried any of these?

Now I tried radeon.agpmode=-1 for a couple of days, but this issue didn't appear. I could only reproduce the corruption of the image mentioned in comment 9. Usually it takes several days of uptime for the corruption to start to appear noticeably, so the experiment might have been too short. I'll try it again later.

https://bugs.freedesktop.org/show_bug.cgi?id=36934

--- Comment #13 from auxsvr@gmail.com 2011-10-22 04:12:01 PDT --- Apparently, there are two kinds of corruption in my case.

The first one is triggered by display of large pixmaps or textures, and manifests itself with corruption of fonts, menus, decorations, icons and widgets all over the screen. It is easy to trigger this by scrolling quickly through a PDF file in okular, or after running Google earth or a game. After some tests for several hours, it appears that the cause is the Virtualbox kernel modules. In fact, after removing them, I haven't been able to trigger this type of corruption again.

The second one is the one manifested in Firefox with large pixmaps, described in comment 9. If I open that image in Firefox and magnify it to 1:1, then it appears black. Returning to the original magnification makes it appear partly corrupted with the contents of other windows (I'm using kwin with compositing). Opening and zooming the same image in Chrome does not exhibit the corruption. I haven't found a way to resolve this yet.

https://bugs.freedesktop.org/show_bug.cgi?id=36934

--- Comment #15 from almos aaalmosss@gmail.com 2011-10-22 07:00:31 PDT --- Since I upgraded to mesa 7.11 I experience significantly less corruption than with 7.10. It still happens sometimes, though. Now I removed the virtualbox modules to give it a try.

Meanwhile, I also tried to reproduce the firefox image corruption in a vnc screen, and it didn't happen, while running firefox normally is still bad. I think it means this is not a bug in firefox, but in xorg/mesa/libdrm/linux somewhere.

https://bugs.freedesktop.org/show_bug.cgi?id=36934

--- Comment #17 from auxsvr@gmail.com 2011-10-28 11:26:57 PDT --- I'm afraid the virtualbox modules have nothing to do with this.

A hopefully helpful observation:

When I first load the large image in firefox, zooming in and out several times works fine, without any corruption and Xorg uses 87 MB of RSS memory. It is after changing desktop, scrolling in okular etc that it becomes corrupted. When it becomes corrupted, Xorg use drops to 54 MB of RSS memory. Doesn't this lead to the conclusion that there is some error during memory management? If this were a hardware error, wouldn't Xorg memory use remain constant?

https://bugs.freedesktop.org/show_bug.cgi?id=36934

almos aaalmosss@gmail.com changed:

What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED

--- Comment #19 from almos aaalmosss@gmail.com --- This hasn't occurred for quite a while. I assume it's fixed in the current version of the driver stack. Closing.