Bug 13564 - [945GM] ET cause xserver freezes with Intel drivers
Summary: [945GM] ET cause xserver freezes with Intel drivers
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/intel (show other bugs)
Version: 7.3 (2007.09)
Hardware: x86 (IA32) Linux (All)
: high major
Assignee: Zou Nan hai
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2007-12-07 11:52 UTC by Michal Fojtik
Modified: 2008-02-29 16:21 UTC (History)
3 users (show)

See Also:
i915 platform:
i915 features:


Attachments
I continue to encounter this bug too (54.02 KB, text/plain)
2007-12-20 11:04 UTC, Brandon Philips
no flags Details
Xorg log after crash (36.92 KB, text/plain)
2008-02-14 17:33 UTC, Martin Tuma
no flags Details

Description Michal Fojtik 2007-12-07 11:52:01 UTC
Xorg freeze after short time when i'll run Enemy Territory. Using latest Intel drivers.
When i'll press power button, notebook shutdowns.
I have X3000 model loaded with latest xfree driver and 2.6.23 kernel.

This DRI messages from dmesg should be related:

[   51.007607] [drm] Initialized drm 1.1.0 20060810
[   51.024159] PCI: Unable to reserve mem region #3:10000000@d0000000 for device 0000:00:02.0
[   51.024192] ACPI: PCI Interrupt 0000:00:02.0[A] -> GSI 16 (level, low) -> IRQ 17
[   51.024204] PCI: Setting latency timer of device 0000:00:02.0 to 64
[   51.024289] [drm] Initialized i915 1.11.0 20070209 on minor 0
[   51.024293] [drm] Used old pci detect: framebuffer loaded

mi@lhasa ~ $ lsmod 
Module                  Size  Used by
i915                   43688  2 
drm                   133016  3 i915
Comment 1 Michal Fojtik 2007-12-08 06:15:59 UTC
I discover this error in Xorg.0.log after crash:


Error in I830WaitLpRing(), timeout for 2 seconds
pgetbl_ctl: 0x3ff80001 pgetbl_err: 0x0
ipeir: 0 iphdr: 2000003
LP ring tail: 10670 head: 10514 len: 1f001 start 0
Err ID (eir): 0 Err Status (esr): 1 Err Mask (emr): ffffffdf
instdone: ffe5fafd instdone_1: ffff7
instpm: 0
memmode: 0 instps: 8001e035
HW Status mask (hwstam): fffecffe
IRQ enable (ier): a2 imr: fffe0000 iir: 10
acthd: 3010514 dma_fadd_p: 105a0
ecoskpd: 307 excc: 0
cache_mode: 6800/180
mi_arb_state: 44
IA_VERTICES_COUNT_QW 0/0
IA_PRIMITIVES_COUNT_QW 0/0
VS_INVOCATION_COUNT_QW 0/0
GS_INVOCATION_COUNT_QW 0/0
GS_PRIMITIVES_COUNT_QW 0/0
CL_INVOCATION_COUNT_QW 0/0
CL_PRIMITIVES_COUNT_QW 0/0
PS_INVOCATION_COUNT_QW 0/0
PS_DEPTH_COUNT_QW 0/0
WIZ_CTL 0
TS_CTL 0  TS_DEBUG_DATA baee46a7
TD_CTL 0 / 0
space: 130716 wanted 131064
(II) intel(0): [drm] removed 1 reserved context for kernel
(II) intel(0): [drm] unmapping 8192 bytes of SAREA 0xf8967000 at 0xb7c0c000

Fatal server error:
lockup

(II) AIGLX: Suspending AIGLX clients for VT switch
Error in I830WaitLpRing(), timeout for 2 seconds
pgetbl_ctl: 0x3ff80001 pgetbl_err: 0x0
ipeir: 0 iphdr: 2000003
LP ring tail: 10678 head: 10514 len: 1f001 start 0
Err ID (eir): 0 Err Status (esr): 1 Err Mask (emr): ffffffdf
instdone: ffe5fafd instdone_1: ffff7
instpm: 0
memmode: 0 instps: 8001e035
HW Status mask (hwstam): fffecffe
IRQ enable (ier): a2 imr: fffe0000 iir: 10
acthd: 3010514 dma_fadd_p: 105a0
ecoskpd: 307 excc: 0
cache_mode: 6800/180
mi_arb_state: 44
IA_VERTICES_COUNT_QW 0/0
IA_PRIMITIVES_COUNT_QW 0/0
VS_INVOCATION_COUNT_QW 0/0
GS_INVOCATION_COUNT_QW 0/0
GS_PRIMITIVES_COUNT_QW 0/0
CL_INVOCATION_COUNT_QW 0/0
CL_PRIMITIVES_COUNT_QW 0/0
PS_INVOCATION_COUNT_QW 0/0
PS_DEPTH_COUNT_QW 0/0
WIZ_CTL 0
TS_CTL 0  TS_DEBUG_DATA baee46a7
TD_CTL 0 / 0
space: 130708 wanted 131064

FatalError re-entered, aborting
lockup
Comment 2 Brandon Philips 2007-12-20 11:04:35 UTC
Created attachment 13255 [details]
I continue to encounter this bug too
Comment 3 Gordon Jin 2008-01-29 20:07:41 UTC
Michal, is this triggered only by running Enemy Territory?
Comment 4 Michal Fojtik 2008-02-03 10:43:35 UTC
(In reply to comment #3)
> Michal, is this triggered only by running Enemy Territory?
> 

Hi, no it occured while playing bzflags too after short while. I'll tried disable sounds but it was occured again.

But short time ago, i'll decide to use i810 driver from xorg and recompile mesa from gentoo portage and problem dissapear. Now everything run's fine. glxgears shows ~650fps.
Comment 5 Martin Tuma 2008-02-14 17:33:40 UTC
Created attachment 14322 [details]
Xorg log after crash
Comment 6 Martin Tuma 2008-02-14 17:34:34 UTC
I have also encountered the problem on my 945GM with xf86-video-intel 2.2.0-2. I make a part of the EXA architecture responsible for the crashes, since I could not reproduce it with XAA (and it started to happen after upgrading to version 2.2.0 which first uses EXA as default for 945GM).

In my case, the hangup seems to happen randomly and I can't find a way how to reproduce it (but working with Eclipse seems to bee a good way...). The atached Xorg log (Attachment 14322 [details]) hopefully has some useful information for You.
Comment 7 Zou Nan hai 2008-02-14 18:20:46 UTC
Michal,
Could you provide some more detailed information?

Please refer to 
http://intellinuxgraphics.org/how_to_report_bug.html

Martin,
Is the bug you reported the same? You mean you were playing ET while using Eclipse?
Comment 8 Martin Tuma 2008-02-15 04:51:28 UTC
(In reply to comment #7)
> Martin,
> Is the bug you reported the same? You mean you were playing ET while using
> Eclipse?
> 
The Xorg log looks very similar, so i think it is the same bug, but it doesn't happen when playing ET (i don't even have ET on my PC). It happens randomly when using "normal" applications (no 3D).
Comment 9 Michael Fu 2008-02-20 16:58:21 UTC
Martin, I suggest you to try to upgrade your xserver and 2D driver to latest version and re-test. If you still have issue, would you please open a new bug? 

we will focus on the freeze issue caused by ET. Waiting for Michal's response...

Comment 10 Martin Tuma 2008-02-21 15:45:26 UTC
(In reply to comment #9)
> Martin, I suggest you to try to upgrade your xserver and 2D driver to latest
> version and re-test. If you still have issue, would you please open a new bug? 
> 
> we will focus on the freeze issue caused by ET. Waiting for Michal's
> response...
> 

There have been some Xorg server upgrades since I reported the crash in my distro (Arch linux) and the current Xorg version is 1.4.0.90-7. There hasn't been even a single crash with this version till now (but that doesn't mean it is fixed, since the previous crashes have been also very rare). If it happens again, I will open a new bug. 
Comment 11 Michael Fu 2008-02-29 16:21:12 UTC
thank you, Martin. I'll mark this bug as fixed then.


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.