App crashing with "intel_region" / internal mesa error messages

[nancym_1002]

Hi there,
I have been searching on forums about an error I have been getting with my intel driver on Fedora 8, 965 GM and X3100 graphics card.

I am trying to run an application "worldwind java" and it continues to crash with the following error message:
java: intel_regions.c:231: intel_region_data: Assertion `dst_offset + dstx + width + (dsty + height - 1) * dst->pitch * dst->cpp <= dst->pitch * dst->cpp * dst->height' failed.

Googling said it was Mesa related. But I am not sure how to solve this error.

thanks for your help,
nancym.

Additional Info
# glxinfo | grep Mesa
OpenGL renderer string: Mesa DRI Unknown Intel Chipset 4.1.3002 x86/MMX/SSE2
OpenGL version string: 1.4 Mesa 7.0.3


[root@localhost worldwind]# dmesg | grep drm
[drm] Initialized drm 1.1.0 20060810
[drm] Initialized i915 1.6.0 20060119 on minor 0


-------------------------------------------------------------------

[Hlingler]

More useful:
glxinfo | grep render

Looks like a java problem. You running one of the open-source java clones, or the SUN Java ? If not running SUN's Java, try it: http://www.mjmwired.net/resources/mj...a-f8.html#java

V

[nancym_1002]

glxinfo | grep render
direct rendering: Yes
OpenGL renderer string: Mesa DRI Unknown Intel Chipset 4.1.3002 x86/MMX/SSE2

My java version is sun's jdk1.6.0_10
java -version
java version "1.6.0_10"
Java(TM) SE Runtime Environment (build 1.6.0_10-b33)
Java HotSpot(TM) Server VM (build 11.0-b15, mixed mode)

[Hlingler]

OK, please post output:
> rpm -q xorg-x11-drv-i810 xorg-x11-server-Xorg `rpm -qa|grep -i mesa|sort`
> su -c /sbin/lspci | grep -i vga
> grep EE /var/log/Xorg.0.log
> grep WW /var/log/Xorg.0.log

V

[nancym_1002]

V,
Thanks for helping me in this..... Here is the output:

rpm -q xorg-x11-drv-i810 xorg-x11-server-Xorg `rpm -qa|grep -i mesa|sort`
xorg-x11-drv-i810-2.1.1-7.fc8
xorg-x11-server-Xorg-1.3.0.0-47.fc8
mesa-libGL-7.0.2-3.fc8
mesa-libGLU-7.0.2-3.fc8


su -c /sbin/lspci | grep -i vga
00:02.0 VGA compatible controller: Intel Corporation Unknown device 2a12 (rev 03)


grep EE /var/log/Xorg.0.log
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(II) Loading extension MIT-SCREEN-SAVER
(EE) intel(0): SDVO: No active TMDS outputs (0x4000)
(EE) intel(0): Unable to write to SDVOCTRL_E for SDVOB Slave 0x70.
(EE) intel(0): First SDVO output reported failure to sync
(EE) intel(0): First SDVO output reported failure to sync
(EE) intel(0): Unable to write to SDVOCTRL_E for SDVOB Slave 0x70



grep WW /var/log/Xorg.0.log
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(WW) No monitor specified for screen "Screen0".
(WW) The core pointer device wasn't specified explicitly in the layout.
(WW) No FontPath specified. Using compiled-in default.
(WW) intel: No matching Device section for instance (BusID PCI:0:2:1) found
(WW) AIGLX: 3D driver claims to not support visual 0x23
(WW) AIGLX: 3D driver claims to not support visual 0x24
(WW) AIGLX: 3D driver claims to not support visual 0x25
(WW) AIGLX: 3D driver claims to not support visual 0x26
(WW) AIGLX: 3D driver claims to not support visual 0x27
(WW) AIGLX: 3D driver claims to not support visual 0x28
(WW) AIGLX: 3D driver claims to not support visual 0x29
(WW) AIGLX: 3D driver claims to not support visual 0x2a
(WW) AIGLX: 3D driver claims to not support visual 0x2b
(WW) AIGLX: 3D driver claims to not support visual 0x2c
(WW) AIGLX: 3D driver claims to not support visual 0x2d
(WW) AIGLX: 3D driver claims to not support visual 0x2e
(WW) AIGLX: 3D driver claims to not support visual 0x2f
(WW) AIGLX: 3D driver claims to not support visual 0x30
(WW) AIGLX: 3D driver claims to not support visual 0x31
(WW) AIGLX: 3D driver claims to not support visual 0x32
(WW) <default pointer>: No Device specified, looking for one..

I have compiz working. Also the SVDO errors in Xorg.0.log are due to some TV monitor issue...I have added the following in xorg.conf to avoid blank screen at startup:

Section "Monitor"
Identifier "LVDS"
Option "Ignore"
EndSection

Section "Monitor"
Identifier "Unknown-1"
Option "Ignore"
EndSection

Section "Monitor"
Identifier "Unknown-2"
Option "Ignore"
EndSection

Section "Monitor"
Identifier "TV"
Option "Ignore"
EndSection

thanks,
nancym.

[Hlingler]

The AIGLX warnings, while not fatal, are disturbing. Also, there are two acceleration methods used by X11: XAA (older, standard X Acceleration Architecture) and the newer EXA (Experimental ...). I'm thinking that, whichever is being used, you should try the other (I suspect EXA is used by default for 965 GM). There's only one way to find out:
grep -i xaa /var/log/Xorg.0.log
grep -i exa /var/log/Xorg.0.log

Depending on the output, you can then manually add the option to your xorg.conf file to use one or the other, in the "Monitor" Section:
Option "AccelMethod" "XAA" [OR: "EXA"]

You must re-start the X-server after such a change (log out of desktop, then: ALT-CTL-Backspace, log in again).

There are a number of other tweaks/gimmicks/options available yet to try, if that fails to produce results, but it may be an iterative process (and may not ever work...).

V

[nancym_1002]

V,
i agree, the AIGLX warnings are indicating something is wrong. Googling the warnings I got to some ubuntu forums where the problem might be with hardware 3D acceleration not getting supported by default, specifically in intel driver.

http://ubuntuforums.org/showthread.p...9872&page=2#18

I am not sure how to go about it.

Anyways, I had the "XAA" acceleration by default so I changed it to "EXA" in my xorg.conf. The log :
(**) intel(0): Option "AccelMethod" "exa"
(II) Loading sub module "exa"
(II) LoadModule: "exa"
(II) Loading /usr/lib/xorg/modules//libexa.so
(II) Module exa: vendor="X.Org Foundation"
(II) intel(0): 0x00032000-0x00041fff: exa G965 state buffer (64 kB)
(II) intel(0): 0x00e60000-0x04087fff: exa offscreen (51360 kB)


I noticed it made my fonts a bit smaller, but the app (written in Java and OpenGL) however still crashes with same messages. The log has same messages on AIGLX still too . ( If I do AIGLX "false" in ServerFlags section, the messages disappear but not much else)

thanks,
nancym.

[Hlingler]

Well, we've tried the easy stuff - time to dig a little deeper.

Please post the contents of /etc/X11/xorg.conf, and upload your Xorg.0.log to pastebin.com and post a link here (vBulletin attachments are broken at the moment). We'll take a look at the log file and see what's up.

In the meantime, you can install package driconf and play with the DRI settings to see if anything in there helps. Start driconf the first time only as root user from command line, to generate a default /etc/drirc file. Then as any user, adjust your personal settings - try anything and everything. Also, there's a link in the Ubungtu thread back to a post here that suggests disabling 3D desktop effects (while running WINE). Try that, it isn't the same scenario, but maybe it'll help.

V

[nancym_1002]

V,
I will play around with driconf ( set yes to S3TC earlier)...Thanks for taking a look at this.

xorg.conf
http://pastebin.com/m250a1ea

Xorg.0.log
http://pastebin.com/m49a41a8c


I have moved back to XAA acceleration. If you want me to keep "exa" and post those results as well, let me know..

thanks,
nancym.

[Hlingler]

This probably isn't what you want to hear, but: according to my research, this is a bug, and was fixed in the next release: http://www.mail-archive.com/dri-deve.../msg34625.html
Page down and follow the list of responses at bottom to find final disposition.

So: the solution is to upgrade to F9 with newer X11/Xorg.

Post back if you disagree with my conclusions.

V

[nancym_1002]

V,
If its a bug, then I guess I would have to upgrade to F9. I am assuming F9 has the fixed 7_0_branch mesa.

I will post my results when i upgrade. Thanks for your help on this!

-nancym.

[Hlingler]

Actually: F9 uses Mesa 7.1, so the fix mentioned should certainly be included.

This issue seems to be somewhat unique. A Google search of the error message that you posted above yielded only the one linked hit that I linked, other than this thread itself and your post on the WorldWind forum.

If an upgrade to F9 fails to correct the problem, then I think that the matter should be escalated to a bug report to Fedora Project and/or X.Org/DRI and/or (preferably) WorldWind. But let's hope F9 with a newer Mesa fixes it.

Good Luck,
V