Bug 32337 - [865] EIR stuck: 0x00000010 starting X
Summary: [865] EIR stuck: 0x00000010 starting X
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/intel (show other bugs)
Version: unspecified
Hardware: All Linux (All)
: medium normal
Assignee: Chris Wilson
QA Contact: Xorg Project Team
Keywords: NEEDINFO
Depends on:
Reported: 2010-12-12 08:03 UTC by Miroslav C
Modified: 2011-01-19 05:47 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

heres full dmesg when im inside X (30.55 KB, text/plain)
2010-12-12 08:03 UTC, Miroslav C
no flags Details
heres full Xorg.log (23.42 KB, application/octet-stream)
2010-12-12 08:08 UTC, Miroslav C
no flags Details
heres full dmesg when im system boots in runlevel 3 all ok (30.55 KB, text/plain)
2010-12-12 08:17 UTC, Miroslav C
no flags Details
heres i915_error_state log (693.25 KB, text/plain)
2010-12-13 13:33 UTC, Miroslav C
no flags Details

Description Miroslav C 2010-12-12 08:03:20 UTC
Created attachment 41041 [details]
heres full dmesg when im inside X 

Hello! Sorry if i made a mistake this is my first bug report.
im using 82865g chipset
i have installed kernel
libdrm 2.4.23
mesa 7.9 
lastest intel 2.13.902
xorg-server 1.9.2
slackware distro slackware-current
heres what happens when system boots up in runlevel 3 everything is okay no kms error
when inside X windows i do get 
[drm:i915_report_and_clear_eir] *ERROR* EIR stuck: 0x00000010, masking [  289.466006] render error detected, EIR: 0x00000010
after a while then when i do dmesg|grep drm nothing is returned

i dont have xorg.conf

if theres anything else that you need please let me know.

thank you very much

in attachment im sending you full dmesg log
Comment 1 Miroslav C 2010-12-12 08:08:02 UTC
Created attachment 41042 [details]
heres full Xorg.log
Comment 2 Miroslav C 2010-12-12 08:17:17 UTC
Created attachment 41044 [details]
heres full dmesg when im system boots in runlevel 3 all ok

this attachment show full dmesg when system boots in runlevel 3 theres no error untill i log in inside X
Comment 3 Chris Wilson 2010-12-12 16:32:25 UTC
Thankyou for wasting my time.
Comment 4 Miroslav C 2010-12-12 23:07:06 UTC
(In reply to comment #3)
> Thankyou for wasting my time.

Could you please tell me why the error msg appears when i enter inside x?
thank you very much
Comment 5 Chris Wilson 2010-12-13 02:55:31 UTC
Not until I've had time to analyse the information. The error indicates a page table error, but as I have neither the actual PGTBL_ER register to tell me which exact error it was, nor the contents of the various display registers along with what buffers have been allocated within the GTT, there is a lot of guesswork involved. In the meantime, grab a /sys/kernel/debug/dri/0/i915_error_state from drm-intel-next which contains additional information to diagnose this condition and *STOP* faffing around with the summary. (The summary is used by our scripts to classify bugs and for me to be able to immediately recognise bugs.)
Comment 6 Miroslav C 2010-12-13 13:33:24 UTC
Created attachment 41087 [details]
heres i915_error_state log 

Thank you for letting me know i attached the file as requested.If theres anything else i can do to help you please let me know. Thank you very much.
Comment 7 Chris Wilson 2011-01-19 05:47:44 UTC
I believe this is fixed by:

commit b7f1de289c50beb4998611ba5373e539efd0f79f
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Tue Dec 14 16:09:31 2010 +0000

    drm/i915: Wait for vblank before unpinning old fb
    Be paranoid and ensure that the vblank has passed and the scanout has
    switched to the new fb, before unpinning the old one and possibly
    tearing down its PTEs.
    Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>

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.