[i965GM] Intrepid RuneScape Fullscreen 3D Java Applet Crashes X

[Githlar]

I have a Dell Inspiron 1525 with the 965GM video chipset.

I have also disabled Xinerama with the xorg.conf option:
Section ServerFlags
  Option "xinerama" "no"
EndSection

Here's what I have to do to reproduce the bug:
Start the RuneScape Java applet. Go to video settings on main screen and go to HD Fullscreen on the highest resolution (in my case 1440x900). A message will pop up saying "Video settings changed, do you want to keep these settings?" and a 10 second countdown. For me, the countdown freezes at 9 and I suddenly get a bunch of blue on the lower third of the X window followed by an infinite loop of X crashes.

This is particularly odd because it seems to work just fine on other resolutions.

Here's an excerpt from my dmesg after this event (which is very hard to get because X is crashing so much that most of the time it won't register a Ctrl+Alt+F1 call):
[ 479.525165] [drm:i915_wait_irq] *ERROR* EBUSY -- rec: 23750 emitted: 23753
[ 481.994134] Xorg[5621]: segfault at 1 ip b7b9ed64 sp bfcbcf40 error 4 in libdri.so[b7b9b000+8000]
[ 482.411148] wlan0: disassociating by local choice (reason=3)
[ 482.412263] bridge-wlan0: disabling the bridge
[ 482.416206] bridge-wlan0: down
[ 482.416397] bridge-wlan0: detached
[ 491.480843] Xorg[7871]: segfault at 6e692f73 ip b7b08d64 sp bfd267a0 error 4 in libdri.so[b7b05000+8000]
[ 503.706566] Xorg[7907]: segfault at 6e692f73 ip b7b28d64 sp bff469c0 error 4 in libdri.so[b7b25000+8000]
[ 516.118841] Xorg[7937]: segfault at 6e692f73 ip b7a74d64 sp bff93210 error 4 in libdri.so[b7a71000+8000]
[ 518.905577] mtrr: base(0xe0000000) is not aligned on a size(0x770000) boundary
[ 745.378036] mtrr: base(0xe0000000) is not aligned on a size(0x770000) boundary

I'm not sure this is the correct package to report for the bug (after all it's a problem with libdri.so). Then again, I'm not sure if it can be reproduced on other video hardware.

Can anybody else confirm this?

[Githlar (githlar-deactivatedaccount)]

Whoops, this is in Intrepid by the way.

[Jouni Mettala (jouni-mettala)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please attach your X server configuration file (/etc/X11/xorg.conf) and X server log file (/var/log/Xorg.0.log) to the bug report as individual uncompressed file attachments using the "Attachment:" box below. Could you please also try to run without any /etc/X11/xorg.conf and let Xorg autodetect your display and video card? Please also attach the /var/log/Xorg.0.log from this attempt. Thanks in advance.

[Iuri Diniz (iuridiniz)]

I think that I have that same bug, but I cannot reproduce it, it's totally random.

the dmesg seems the same:
[ 2383.222761] Xorg[5351]: segfault at 20 ip b7aa5d64 sp bfac32d0 error 4 in libdri.so[b7aa2000+8000]
[ 2391.686717] Xorg[5917]: segfault at 20 ip b7b67d64 sp bfb85fd0 error 4 in libdri.so[b7b64000+8000]
[ 2401.729639] Xorg[5938]: segfault at 20 ip b7aded64 sp bfafe750 error 4 in libdri.so[b7adb000+8000]
[ 2412.049627] Xorg[5959]: segfault at 20 ip b7b37d64 sp bfb57fa0 error 4 in libdri.so[b7b34000+8000]
[ 2414.479769] mtrr: base(0xd0000000) is not aligned on a size(0x7b0000) boundary
[ 2417.774807] mtrr: no MTRR for d0000000,7b0000 found
----------

My computer is a asus eee pc 701, with this pci:

00:02.0 VGA compatible controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 04)
 Subsystem: ASUSTeK Computer Inc. Device 82d9
 Flags: bus master, fast devsel, latency 0, IRQ 16
 Memory at f7f00000 (32-bit, non-prefetchable) [size=512K]
 I/O ports at ec00 [size=8]
 Memory at d0000000 (32-bit, prefetchable) [size=256M]
 Memory at f7ec0000 (32-bit, non-prefetchable) [size=256K]
 Capabilities: [d0] Power Management version 2
 Kernel modules: intelfb, asus_eee

Xorg is using intel module as driver, I'm not using ubuntu kernel, but a kernel from array.org (for eee pc), everything else is from ubuntu (intrepid)

[Carey Underwood (cwillu)]

Githlar, even though luri has attached files, can you still attach the requested information (/etc/X11/xorg.conf, /var/log/xorg.0.log, lspci -vvnn)?

Luri, you're running a different chipset, so although it may be relevant, we still need Githlar's information. If it turns out to be the same bug, then we can move forward from there, otherwise you may want to post a new bug with those same files.

[Githlar (githlar-deactivatedaccount)]

I recently upgraded to Jaunty and I'm having problems that may still be related. However, I didn't try playing for a couple of weeks before upgrading, so I'm not sure if it was the upgrade that broke it or an update that did it.

The problem I'm having now: Entering either HD mode or Fullscreen mode causes X to crash. It crashes in a way where the mouse is still movable, but everything else is frozen. Audio cuts out after a short time (presumably after it runs over its memory buffer). Ctrl+Alt+Backspace doesn't work (I did enable it in Jaunty via to "DontZap" xorg.conf option), Alt+PrntScrn+S/U/B seems to work to an extent. In one of my logs I see an "Emergency Sync Complete," but nothing after that. There is no sign of any trouble in Xorg.0.log, dmesg.0, anything that I can see. Attached are (hopefully) relavant logs.

[Githlar (githlar-deactivatedaccount)]

Maybe you can see something I can't?

[Githlar (githlar-deactivatedaccount)]

To elaborate on the above:

Fullscreen mode in every resolution is now broken. I don't know what that says, but maybe it can be helpful to somebody?

[Bryce Harrington (bryce)]

Githlar, for crash bugs, what we really need in order to begin analysis is a full backtrace. Would you mind reproducing the bug on Jaunty and collecting one? Guidelines for collecting full backtraces can be found at: http://wiki.ubuntu.com/X/Backtracing. Thanks ahead of time.

[Bryce Harrington (bryce)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.