Bug 1071575 - For some files, Gnumeric can get the radeonsi driver to freeze the whole kernel because of a GPU lockup (atombios is stuck in a loop executing some shenanigans)
Summary: For some files, Gnumeric can get the radeonsi driver to freeze the whole kern...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-amd
Version: 20
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Orphan Owner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-03-01 20:40 UTC by Jean-François Fortin Tam
Modified: 2015-06-29 19:11 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-06-29 19:11:56 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
gnumeric file that triggers the bug (5.03 KB, application/x-gnumeric)
2014-03-01 20:40 UTC, Jean-François Fortin Tam
no flags Details
journalctl output (4.12 KB, text/plain)
2014-03-01 20:41 UTC, Jean-François Fortin Tam
no flags Details

Description Jean-François Fortin Tam 2014-03-01 20:40:19 UTC
Created attachment 869496 [details]
gnumeric file that triggers the bug

This is some pretty crazy event but I can reproduce it 100% of the time simply by:

1. Opening the attached .gnumeric spreadsheet
2. Right-clicking on the 2nd chart (the bars), accessing its properties dialog
3. In the plot's hierarchy tree on the left, click the last item: "Series1"

Boom. The kernel locks up: X is frozen, whatever music that was playing gets stuck into a loop, you can't switch to virtual terminals, and you have to force a hard reset by power-cycling the machine.

When doing further testing, I logged myself into SSH pre-emptively and ran "journalctl -f" in the hope of glimpsing what went wrong right before the kernel goes belly up, and I was lucky enough to find out that the radeonsi driver is locking up. Attaching the output of journalctl so you can see what's going on.

Would be good to have upstream know about this...


Note: I also checked if gnumeric was segfaulting or anything like that by running it through gdb over SSH, but it encounters no problem whatsoever. So this is really the video driver's problem.

Comment 1 Jean-François Fortin Tam 2014-03-01 20:41:26 UTC
Created attachment 869497 [details]
journalctl output

Comment 2 Fedora End Of Life 2015-05-29 11:07:00 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 '20'.

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 20 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 3 Fedora End Of Life 2015-06-29 19:11:56 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.