Bug 29006 - [82845G] goes black on login - "Failed to submit batchbuffer"
Summary: [82845G] goes black on login - "Failed to submit batchbuffer"
Status: RESOLVED DUPLICATE of bug 26345
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/intel (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: medium major
Assignee: Carl Worth
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-11 05:50 UTC by 20100711
Modified: 2010-07-11 07:26 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
As titled (16.24 KB, application/octet-stream)
2010-07-11 05:50 UTC, 20100711
no flags Details

Description 20100711 2010-07-11 05:50:44 UTC
Created attachment 36945 [details]
As titled

I hope this is a duplicate (meaning you are already working
on fixing it :) ).

The intel graphics drivers have continually become worse and
worse over the past several months (crashing more and more
often as newer versions come out), until I can no longer log
in (using KDE) at all. A few seconds after I try, the screen
goes completely black, and I can not recover any video (even
a console) without rebooting. I am now reduced to using the
console.

Some information:

00:02.0 VGA compatible controller: Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device (rev 01) (prog-if 00 [VGA controller])
        Subsystem: Compaq Computer Corporation Device 00ba

i686 Intel(R) Pentium(R) 4 CPU 2.00GHz GenuineIntel GNU/Linux

$ qlist -Iv xf86-video-intel
x11-drivers/xf86-video-intel-2.9.1

$ qlist -Iv xorg-server
x11-base/xorg-server-1.7.6

$ qlist -Iv mesa
media-libs/mesa-7.7.1

# qlist -Iv libdrm
x11-libs/libdrm-2.4.18_pre20100211-r1

linux-2.6.32-gentoo-r7

Gentoo (of course :) )

Compaq Evo D510 USDT (Ultra Slim Desktop)

VGA


xorg.conf:

Section "ServerLayout"
    Identifier  "X.org Configured"
    Screen      0 "Screen0" 0 0
EndSection

Section "Monitor"
    Identifier  "Monitor0"
    VendorName  "Monitor Vendor"
    ModelName   "Monitor Model"
EndSection

Section "Device"
    Identifier  "Card0"
    Driver      "intel"
    VendorName  "Intel Corporation"
    BoardName   "82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device"
    BusID       "PCI:0:2:0"
EndSection

Section "Screen"
    Identifier "Screen0"
    Device     "Card0"
    Monitor    "Monitor0"
    DefaultDepth    24
    SubSection "Display"
        Depth       24
    EndSubSection
EndSection


I will attach the Xorg.0.log.


The kdm.log might also be of some interest:

X.Org X Server 1.7.6
Release Date: 2010-03-17
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.32-gentoo-r7 i686 
Current Operating System: Linux system 2.6.32-gentoo-r7 #1 Fri Apr 9 05:00:34 UTC 2010 i686
Kernel command line: root=/dev/sda6
Build Date: 30 June 2010  04:13:56PM
 
Current version of pixman: 0.17.2
        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sat Jul 10 15:15:42 2010
(==) Using config file: "/etc/X11/xorg.conf"
FATAL: Module fbcon not found.
QFont::fromString: Invalid description 'Serif,20,5,0,50,0'
QFont::fromString: Invalid description 'Sans Serif,10,5,0,50,0'
QFont::fromString: Invalid description 'Sans Serif,10,5,0,75,0'
intel_bufmgr_gem.c:1152: Error setting memory domains 126 (00000040 00000000): Input/output error .

Fatal server error:
Failed to submit batchbuffer: Input/output error


Please consult the The X.Org Foundation support 
         at http://wiki.x.org
 for help. 
Please also check the log file at "/var/log/Xorg.0.log" for additional information.

X: i830_batchbuffer.h:79: intel_batch_emit_dword: Assertion `pI830->batch_ptr != ((void *)0)' failed.


From /var/log/messages:

Jul 10 15:15:43 system kernel: [  197.505810] render error detected, EIR: 0x00000010
Jul 10 15:15:43 system kernel: [  197.505820] [drm:i915_handle_error] *ERROR* EIR stuck: 0x00000010, masking
Jul 10 15:15:43 system kernel: [  197.505832] render error detected, EIR: 0x00000010
Jul 10 15:16:22 system kernel: [  236.606653] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
Jul 10 15:16:22 system kernel: [  236.606663] render error detected, EIR: 0x00000000
Jul 10 15:16:22 system kernel: [  236.606668] i915: Waking up sleeping processes
Jul 10 15:16:22 system kernel: [  236.606710] reboot required
Jul 10 15:16:22 system kernel: [  236.607406] [drm:i915_do_wait_request] *ERROR* i915_do_wait_request returns -5 (awaiting 876 at 874)
Jul 10 15:16:22 system kernel: [  236.608109] [drm:i915_gem_execbuffer] *ERROR* Execbuf while wedged
Jul 10 15:16:23 system kernel: [  236.773358] [drm] DAC-5: set mode 1280x1024 1b
Jul 10 15:16:23 system kdm[3172]: X server for display :0 terminated unexpectedly
Jul 10 15:16:23 system kernel: [  237.436509] [drm:i915_gem_execbuffer] *ERROR* Execbuf while wedged
Jul 10 15:16:23 system kernel: [  237.572627] [drm] DAC-5: set mode 1280x1024 1b
Jul 10 15:16:23 system kdm[3172]: X server died during startup
Jul 10 15:16:23 system kdm[3172]: X server for display :0 cannot be started, session disabled


If you need anything else, let me know, and I will try to
help. Don't even think about asking me to use a later
kernel, though. I tried 2.6.34-gentoo-r1, and the machine
goes completely black (and locks up) before even starting
X (with no log whatsoever).
Comment 1 Chris Wilson 2010-07-11 07:26:15 UTC
We have big issues with GEM on i8xx. i845 is even more troublesome as it has some errata that we fail to workaround that affect reprogramming the GTT.

My presumption is that this is the very same bug, and the current workaround is to use UMS+EXA.

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


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.