Bug 827792 - f17 caicos amnesia sometimes crashes xorg hd6450
Summary: f17 caicos amnesia sometimes crashes xorg hd6450
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-ati
Version: 17
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-06-03 03:39 UTC by Reartes Guillermo
Modified: 2013-08-01 13:34 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-08-01 13:33:57 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
xorg.0.log.old related to the xorg crash (52.74 KB, application/octet-stream)
2012-06-03 03:39 UTC, Reartes Guillermo
no flags Details

Description Reartes Guillermo 2012-06-03 03:39:22 UTC
Created attachment 588778 [details]
xorg.0.log.old related to the xorg crash

Description of problem:

When launching amnesia, sometimes the game either segfaults or causes 
xorg to crash. After that, launching the game works ok. So the issue is 
in the few seconds after launching it, after the presentations and before
the menu. Once i reach the menu, i can play normally.

Version-Release number of selected component (if applicable):

xorg-x11-drv-ati.x86_64  6.14.4-5.20120417git0bda305f7.fc17
mesa-dri-drivers.x86_64  8.0.3-1.fc17
libtxc_dxtn.x86_64       1:1.0.0-2.fc17

How reproducible:
sometimes

Steps to Reproduce:
1. launch amnesia
2. either segfault (more common) or xorg crash (less common)
3. launch the game again, it works.

Actual results:
random xorg crash on game startup sometimes.

Backtrace:
0: /usr/bin/X (xorg_backtrace+0x36) [0x464de6]
1: /usr/bin/X (0x400000+0x69e39) [0x469e39]
2: /lib64/libpthread.so.0 (0x3b42c00000+0xefe0) [0x3b42c0efe0]
3: /usr/lib64/dri/r600_dri.so (0x7f340ba70000+0x65e72) [0x7f340bad5e72]
4: /usr/lib64/xorg/modules/extensions/libdri2.so (0x7f340d478000+0x1bcc) [0x7f340d479bcc]
5: /usr/lib64/xorg/modules/extensions/libdri2.so (DRI2SwapBuffers+0x182) [0x7f340d47acb2]
6: /usr/lib64/xorg/modules/extensions/libdri2.so (0x7f340d478000+0x3f42) [0x7f340d47bf42]
7: /usr/bin/X (0x400000+0x3439a) [0x43439a]
8: /usr/bin/X (0x400000+0x233e5) [0x4233e5]
9: /lib64/libc.so.6 (__libc_start_main+0xf5) [0x3b42821735]
10: /usr/bin/X (0x400000+0x236bd) [0x4236bd]

Segmentation fault at address 0x50
Fatal server error:
Caught signal 11 (Segmentation fault). Server aborting

Expected results:
no xorg crash

Additional info:
i don't know if the segfault is related to the xorg chash, because it does not 
leave any information. xorg at least leaves a logfile.

Comment 1 Fedora End Of Life 2013-07-04 04:26:21 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 '17'.

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 17'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 17 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, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

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.

Comment 2 Fedora End Of Life 2013-08-01 13:34:02 UTC
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.