Bug 8299

Summary:

R300 + MergedFB + blender + some movement => lock-up

Product:

DRI

Reporter:

Matthias Bläsing <mblaesing>

Component:

General

Assignee:

Default DRI bug account <dri-devel>

Status:

RESOLVED DUPLICATE

QA Contact:

Severity:

normal

Priority:

high

Version:

XOrg git

Hardware:

x86 (IA32)

OS:

Linux (All)

Whiteboard:

i915 platform:

i915 features:

Attachments:

Description	Flags
xorg.conf	none
see the red marked area - there should be the normal blender window	none
Xorg.0.log	none

Description Matthias Bläsing 2006-09-16 13:18:35 UTC

I own a notebook with this Mobile Radeon 9600:

ATI Technologies Inc RV350 [Mobility Radeon 9600 M10]

when running the card in dualhead setup with merged framebuffer enabled the card
locks up when running blender (I will attach the blender and xorg.conf file).

When loading the file, I rotate the view in the lower right viewport and after
0.5-1 turns the display locks up.

Trying the same with a singlehead setup on the same notebook or running with
LIBGL_ALWAYS_INDIRECT="1" works without lock ups.

I noticed, that when running blender on larger setups (1680x1050-1024x768 =>
2704x1050 or 1680x1050-1400x1050=>3080x1050) parts of the right screen (~ 1/3)
are filled with garbage. Moving glxgears into that area stops the gears and
leads to display corruption there.

Comment 1 Matthias Bläsing 2006-09-16 13:19:02 UTC

Created attachment 7012 [details]
xorg.conf

Comment 2 Matthias Bläsing 2006-09-16 13:28:16 UTC

I just noticed, that the blender file is pretty big (26M) - as I don't know how
good bugzilla reacts to so big attachments. I'm putting the file on webspace:

http://www.kolping-allendorf.de/ff-film-06-dvd.blend

Comment 3 Matthias Bläsing 2006-09-16 14:11:40 UTC

Version Info:
Mesa:       latest cvs
DRM:        latest git
radeon ddx: latest git

Comment 4 Aapo Tahkola 2006-09-16 14:45:55 UTC

Does enabling SWcursor xorg option help?

Comment 5 Matthias Bläsing 2006-09-17 07:02:19 UTC

Yes that helps! But now the area around the cursor is not updated correctly in
blender - when running through the menus or when selecting objects.

But the disstortions on the right side of the big desktop stay - Is there a
limit in the hardware that restricts the area to a smaller space?

Comment 6 Aapo Tahkola 2006-09-17 07:41:09 UTC

Possible dupe of #5147 also.
In any case, I'm not planning to fix this. Sorry.

(In reply to comment #5)
> Yes that helps! But now the area around the cursor is not updated correctly in
> blender - when running through the menus or when selecting objects.

This is normal.

> 
> But the disstortions on the right side of the big desktop stay - Is there a
> limit in the hardware that restricts the area to a smaller space?

Disabling color tiling should help.


*** This bug has been marked as a duplicate of 5376 ***

Comment 7 Matthias Bläsing 2006-09-17 08:59:00 UTC

Actually disabling ColorTiling

Option          "ColorTiling"           "off"

does not help - I'll attach a screen shot, where you can see the effect.

Comment 8 Matthias Bläsing 2006-09-17 08:59:43 UTC

Created attachment 7020 [details]
see the red marked area - there should be the normal blender window

Comment 9 Matthias Bläsing 2006-09-17 09:01:30 UTC

Created attachment 7021 [details]
Xorg.0.log

Log of X startup (ColorTiling should be disabled - but it's not noted in the
log)

Comment 10 Aapo Tahkola 2006-09-17 11:17:54 UTC

(In reply to comment #8)
> Created an attachment (id=7020) [edit]
> see the red marked area - there should be the normal blender window

AFAIK, rv350s are limited to fb width of 2650 when doing 3d rendering.
r480 seems to be able to cope 4000.

One could fix this by rendering multiple times like is already done for clip
rects in drm.

You would need to play with:
-clip rects
-R300_SE_VPORT_XOFFSET and R300_SE_VPORT_YOFFSET
-R300_RB3D_COLOROFFSET0
-R300_RB3D_DEPTHOFFSET

Color and depth offsets need to start at even tiles.

Comment 11 Matthias Bläsing 2006-09-18 05:30:09 UTC

Ok, as I am no experienced programmer in C and graphics programming and there
won't be any free time to learn it, I won't work on it. So my plan would be now
to open a bug report specific to this problem - maybe someone with more
experience in this field finds time to implement that.

BTW: Thx for the help - being able to use blender in dualhead setup at least on
the internal display is really great!

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.