Bug 1207887 - Segmentation fault in X.Org server after error in radeon kernel device driver module
Summary: Segmentation fault in X.Org server after error in radeon kernel device driver...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-ati
Version: 21
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: 2015-04-01 00:36 UTC by gitne
Modified: 2015-12-02 17:48 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-12-02 10:43:08 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Xorg error log (3.58 KB, text/plain)
2015-04-01 00:36 UTC, gitne
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1207874 0 unspecified CLOSED Recursive error in radeon device driver module after resume from hibernation 2021-02-22 00:41:40 UTC

Description gitne 2015-04-01 00:36:56 UTC
Created attachment 1009343 [details]
Xorg error log

Description of problem:
The X.Org server produces a segmentation fault after a recursive error in the radeon kernel device driver module when resuming from hibernation. This error is always reproducible.

Version-Release number of selected component (if applicable):
X.Org X Server 1.16.3
Release Date: 2014-12-20
X Protocol Version 11, Revision 0
Build Operating System:  3.17.8-300.bz1178975.fc21.x86_64 
Current Operating System: Linux gitne 3.18.9-200.fc21.x86_64 #1 SMP Mon Mar 9 15:10:50 UTC 2015 x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.18.9-200.fc21.x86_64 root=UUID=XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX ro resume=UUID=XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX rd.lvm=0 rd.md=0 rd.dm=0 rd.luks=0 norandmaps nowatchdog noexec=on clocksource=hpet
Build Date: 31 January 2015  11:23:27PM
Build ID: xorg-x11-server 1.16.3-2.fc21 
Current version of pixman: 0.32.6
Linux 3.18.9-200.fc21.x86_64 #1 SMP Mon Mar 9 15:10:50 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux (and later)

Steps to reproduce:
1. Run specified X.Org server and kernel on AMD A10-7800 Radeon R7
2. Hibernate (suspend to disk).
3. Resume.

Actual results:
X.Org server recovers into software rendering mode after a segmentation fault.

Expected results:
X.Org server should recover into VESA or software rendering mode without a segmentation fault (fallback gracefully).

Additional info:
See attached logs and linked bug id 1207874.

Comment 1 Fedora End Of Life 2015-11-04 12:51:13 UTC
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. 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 EOL if it remains open with a Fedora  'version'
of '21'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 21 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 this bug is closed as described in the policy above.

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 2015-12-02 10:43:10 UTC
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

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.