Bug 24391 - OOe corrupted
Summary: OOe corrupted
Status: RESOLVED WONTFIX
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/radeonhd (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Luc Verhaegen
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-08 02:37 UTC by SES
Modified: 2011-10-23 21:55 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Xorg.0.log (36.92 KB, text/plain)
2009-10-08 02:37 UTC, SES
no flags Details
xorg.conf (3.28 KB, text/plain)
2009-10-08 15:46 UTC, SES
no flags Details

Description SES 2009-10-08 02:37:22 UTC
Created attachment 30156 [details]
Xorg.0.log

M/B+CPU: Asus P6T Deluxe V2 (Intel M58) + Intel Core i7 920
Card: MSI Radeon HD 4850 - RV770
Archlinux; kernel 2.6.30-ARCH
X.org X server v1.6.3.901 (1.6.4 RC 1)
Radeonhd v1.2.5.1

Row and column lines in OpenOffice.org Calc disappear. They get (re-)painted if I scroll slowly by pressing the slider arrow, but get worse (disappear in bigger areas) if I just pull/drag the slider with the mouse. The problem is more pronounced in bigger than in smaller spreadsheet documents. I have not noticed any corruption in other apps or on the desktop.

I note two disconcerting messages in Xorg.0.log:

1. 
(II) RADEONHD(0): The detected amount of videoram exceeds the PCI BAR aperture.
(II) RADEONHD(0): Using only 262144kB of the total 1048576kB.
(--) RADEONHD(0): VideoRAM: 262144 kByte

2.
(WW) RADEONHD(0): rhdAtomAllocateFbScratch: FW FB scratch area not located at the end of VRAM. Scratch End: 0x104fec VRAM End: 0x10000000
(II) RADEONHD(0): Cannot get VRAM scratch space. Allocating in main memory instead

The two messages might explain the problem(?). If not, they are bugs in their own right, as it were.
Comment 1 Egbert Eich 2009-10-08 05:54:12 UTC
> The two messages might explain the problem(?). If not, they are bugs in their
> own right, as it were.

Those messages are irrelevant, only informational and certainly not related to your problem. 

Are you saying the lines disappear when you scroll fast but not when you scroll slow?
Acceleration is still somewhat experimental for this chip, to verify that it's this, try to disable it.
Either use 
Option "NoAccel"
in the device section or prevent the drm module from being loaded.
Comment 2 Yang Zhao 2009-10-08 08:12:42 UTC
Known issue with one of the acceleration primitives in r6xx. See bug #21561 and #21855.
Comment 3 SES 2009-10-08 11:20:35 UTC
(In reply to comment #1)
> > The two messages might explain the problem(?). If not, they are bugs in their
> > own right, as it were.
> 
> Those messages are irrelevant, only informational and certainly not related to
> your problem. 
> 
> Are you saying the lines disappear when you scroll fast but not when you scroll
> slow?
> Acceleration is still somewhat experimental for this chip, to verify that it's
> this, try to disable it.
> Either use 
> Option "NoAccel"
> in the device section or prevent the drm module from being loaded.
> 

I will try both and come back to you.
What I am seeing is that there are areas with no lines when I open a spreadsheet; i.e. there are areas where the lines are gone before I touch the sheet. Scrolling slowly out from, and then into these areas again, makes the lines appear as normal. Scrolling fast out and back can have the same repairing effect in a very small sheet, but in a bigger sheet of from 1.4 to 10 MiB, scrolling fast increases the corruption. By scrolling fast I mean moving the sliders themselves with the mouse, not pressing the slider arrows with the mouse.

As to the messages being irrelevant to the spreadsheet problem, I have tried to search for some of the words in those messages, but not found any bug reports about them.
Comment 4 SES 2009-10-08 12:13:42 UTC
(In reply to comment #2)
> Known issue with one of the acceleration primitives in r6xx. See bug #21561 and
> #21855.
> 

OK, thanks. I tried to look for something similar, bu I am apparently not sufficiently technically proficient.
Comment 5 SES 2009-10-08 15:46:13 UTC
Created attachment 30191 [details]
xorg.conf
Comment 6 SES 2009-10-08 15:46:59 UTC
(In reply to comment #1)
(...)
> Either use 
> Option "NoAccel"
> in the device section or prevent the drm module from being loaded.
> 

Commenting Load "drm" --> no difference, no improvement.

Uncommenting Option "NoAccel" --> the problem disappears, but at the cost of much slower repaint and losing my mplayer video playback.

Doing both --> same result as with uncommenting Option "NoAccel".

Guess my best option for now is to accept the disappearing grid/cells.

I enclose my xorg.conf.
Comment 7 SES 2010-06-23 10:42:55 UTC
This may not be the right place for this comment, but after upgrading to xf86-video-radeonhd-1.3.0-2 I no longer see disappering grid lines in OOo calc.

Thanks a lot for your good work!
Comment 8 Jeremy Huddleston Sequoia 2011-10-16 15:59:11 UTC
Does this issue occur with the preferred ati driver (xf86-vide-ati)?  If so, please move this to the Driver/Radeon component.  

Development of radeonhd has pretty much halted and development focus is on the ati driver.  Please see http://www.x.org/wiki/radeonhd

If the issue does not exist in the ati driver (or if there is no response to this message), this bug will be closed as WONTFIX unless someone contributes a patch.
Comment 9 SES 2011-10-22 18:29:21 UTC
The bug disappeared when I switched to the ATI driver, but I forgot to tell it here... I guess this bug may be safely closed.


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.