Bug 614833 - [abrt] crash in xorg-x11-server-Xorg-1.7.6-4.fc12: raise: Process /usr/bin/Xorg was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in xorg-x11-server-Xorg-1.7.6-4.fc12: raise: Process /usr/bin/Xo...
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-server
Version: 12
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:db893b79cff825ce690d7cfbd77...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-07-15 11:11 UTC by gabriel
Modified: 2010-12-03 13:14 UTC (History)
1 user (show)

Clone Of:
Last Closed: 2010-12-03 13:14:40 UTC

Attachments (Terms of Use)
File: backtrace (7.54 KB, text/plain)
2010-07-15 11:11 UTC, gabriel
no flags Details

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Bugzilla 614513 None None None Never

Internal Trackers: 614513

Description gabriel 2010-07-15 11:11:54 UTC
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/bin/Xorg :4 -br -verbose -auth /var/run/gdm/auth-for-gdm-1GvAKL/database -nolisten tcp
component: xorg-x11-server
crash_function: raise
executable: /usr/bin/Xorg
global_uuid: db893b79cff825ce690d7cfbd774bdf6c40fffd2
package: xorg-x11-server-Xorg-1.7.6-4.fc12
rating: 4
reason: Process /usr/bin/Xorg was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)

Comment 1 gabriel 2010-07-15 11:11:57 UTC
Created attachment 432042 [details]
File: backtrace

Comment 2 gabriel 2010-07-15 11:29:14 UTC
xorg hungup keyboard and mouse, black screen

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

Driver      "intel"

i probe with:
Option      "DRI"         "false"
Option      "NoAccel"     "true"
Option      "AccelMethod" "UXA"
Option      "AccelMethod" "EXA"

as kernel parameters

Comment 3 gabriel 2010-07-15 11:47:40 UTC
Jul 15 08:23:00 localhost kernel: [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
Jul 15 08:23:00 localhost kernel: render error detected, EIR: 0x00000000
Jul 15 08:23:00 localhost kernel: [drm:i915_do_wait_request] *ERROR* i915_do_wait_request returns -5 (awaiting 78960 at 78957)

Comment 4 gabriel 2010-07-15 11:48:25 UTC
uname -r

Comment 5 Bug Zapper 2010-11-03 11:56:43 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 

Comment 6 Bug Zapper 2010-12-03 13:14:40 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.