Bug 872182 - Process /usr/libexec/xscreensaver/pinion was killed by signal 11 (SIGSEV)
Summary: Process /usr/libexec/xscreensaver/pinion was killed by signal 11 (SIGSEV)
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: mesa
Version: 16
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-11-01 13:37 UTC by Peter H. Jones
Modified: 2013-02-13 08:26 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-02-13 08:26:23 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
compressed tar of core dump archive (1.17 MB, application/octet-stream)
2012-11-05 14:08 UTC, Peter H. Jones
no flags Details
compressed tar of core dump archive (1.13 MB, application/octet-stream)
2012-11-16 03:22 UTC, Peter H. Jones
no flags Details
Xorg.0.log requested (53.89 KB, text/plain)
2012-11-16 14:13 UTC, Peter H. Jones
no flags Details
ABRT log file of another occurrence (30.01 KB, text/plain)
2012-11-20 21:12 UTC, Peter H. Jones
no flags Details

Description Peter H. Jones 2012-11-01 13:37:46 UTC
Description of problem:


Version-Release number of selected component (if applicable):
xscreensaver-gl-extras-5.20-1.fc16.x86_64
kernel xscreensaver-gl-extras-5.20-1.fc16.x86_64


How reproducible:
Don't know, appeared in ABRT

Actual results:
Process /usr/libexec/xscreensaver/pinion was killed by signal 11 (SIGSEV)

Expected results:
No abort

Additional info:
Attepting to report resuts in retrace error.

Posting ABRT log output below:
--- Running analyze_RetraceServer ---
Querying server settings
Preparing an archive to upload
Uploading 904472 bytes
Upload successful
Retrace job started
Initializing virtual root
Initializing virtual root
Initializing virtual root
Initializing virtual root
Initializing virtual root
Initializing virtual root
Retrace job failed
Retrace failed. Try again later and if the problem persists report this issue please.
Analyzing crash data 
WARNING:root:No debuginfo found for '6ea944a55b98fe300f8aaed46ce1749ae008c7f1' (None)
WARNING:root:No debuginfo found for '3266204f0fac2a478dda7888df76957d8b2f77b9' (None)
WARNING:root:No debuginfo found for 'aaff54d66aa533d6cf7f22582420a7edc69aea67' (/usr/lib64/libGL.so.1)
WARNING:root:No debuginfo found for '71abd4ec83f255a0767af3be2dda73455bbc2ad9' (/usr/lib64/libGLU.so.1)
WARNING:root:No debuginfo found for '7343d35696ce251688ece0a26e457e61ca805cfd' (/usr/lib64/libXxf86vm.so.1)
WARNING:root:No debuginfo found for 'f8f4d8e260ee8f3b262936920270ace01b2da537' (/lib64/libpthread.so.0)
WARNING:root:No debuginfo found for 'd0c6e13f00a20952a72a945c929efb175fd760e3' (/usr/lib64/libSM.so.6)
WARNING:root:No debuginfo found for '25b834f4c4dc534708635ff1064e2fe02a366a62' (/usr/lib64/libICE.so.6)
WARNING:root:No debuginfo found for '40dc5e32f96a3d6d6728301becc415c9af4a68bb' (/usr/lib64/libXt.so.6)
WARNING:root:No debuginfo found for '4c842320387ff7f6f91b7842b223c16518be909f' (/usr/lib64/libX11.so.6)
WARNING:root:No debuginfo found for '11e343f1da2a0c5c61502657909b8c4fe5e21b72' (/usr/lib64/libXmu.so.6)
WARNING:root:No debuginfo found for 'dc998e8c1e1dc44c684b9b86e753945a868e134a' (/usr/lib64/libXext.so.6)
WARNING:root:No debuginfo found for '3437fbc1b9876f2d55c8c9beffbda021a61b1e61' (/lib64/libm.so.6)
WARNING:root:No debuginfo found for '2e4f144d6c8fb2dbb214fdbea0c327b05fa70a78' (/lib64/libc.so.6)
WARNING:root:No debuginfo found for '36a149d1e2c29890b616402f6bc5e3f69ca2738e' (/usr/lib64/libXdamage.so.1)
WARNING:root:No debuginfo found for '163b323da65b708418226eb5fa8b057c731d1475' (/usr/lib64/libXfixes.so.3)
WARNING:root:No debuginfo found for '632fc539af09eb4a85682be1034d7a99fc864a95' (/usr/lib64/libdrm.so.2)
WARNING:root:No debuginfo found for '58803db420709341d8e6a713b18e54a6e1824272' (/lib64/libdl.so.2)
WARNING:root:No debuginfo found for '3ba5302e34546a45e9a85ac3429e7bc6ed624011' (/usr/lib64/libstdc++.so.6)
WARNING:root:No debuginfo found for '75eaece6e0d1e075520cdfad5c398fdab4370846' (/lib64/libgcc_s.so.1)
WARNING:root:No debuginfo found for 'e7160fedcf92e2c07f8883f15c71d703b9e7abcb' (/lib64/ld-linux-x86-64.so.2)
WARNING:root:No debuginfo found for '7a896ce784b97721d1f6960bfba25e60511c0178' (/lib64/libuuid.so.1)
WARNING:root:No debuginfo found for '7994f114cf7189e482f2665fae8e351ed8bc05e3' (/usr/lib64/libxcb.so.1)
WARNING:root:No debuginfo found for '6cded60dd119fb8b8aa41b264e12931cb2c7b67f' (/lib64/librt.so.1)
WARNING:root:No debuginfo found for '1c6a95451ee19617be5abea3d121f0226d21ddda' (/usr/lib64/libXau.so.6)
WARNING:root:No debuginfo found for '13bd265cb8078c8fc2d9dcd59bd14d52a1446f3a' (/usr/lib64/dri/r600_dri.so)
WARNING:root:No debuginfo found for 'e3c88cb9ea428bd61f4064dbd53acae2d396a1ec' (/usr/lib64/libffi.so.5)
WARNING:root:No debuginfo found for '4b4285058f7f6b39b7e7c45df83fd36c6833bfe4' (/lib64/libselinux.so.1)
WARNING:root:No debuginfo found for 'bf404f1f16ae38c405a644f7f2a5a3de02e5d158' (/lib64/libexpat.so.1)
WARNING:root:No debuginfo found for '455ba5e1f9bfbe95b5d751aade0fe830576d21c6' (/usr/lib64/llvm/libLLVM-2.9.so)
WARNING:root:No debuginfo found for 'c2d49d72ec1a1e68b39c3724693f83f44d80a259' (/usr/lib64/libXcursor.so.1)
WARNING:root:No debuginfo found for '0911ea7c180d733724f89037b8e8a34e64024aec' (/usr/lib64/libXrender.so.1)
/usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.3-py2.6-linux-x86_64.egg/sqlalchemy/sql/expression.py:1802: SAWarning: The IN-predicate on "packages.build_id" was invoked with an empty sequence. This results in a contradiction, which nonetheless can be expensive to evaluate.  Consider alternative strategies for improved performance.
  return self._in_impl(operators.in_op, operators.notin_op, other)
WARNING:root:Unable to find binary package for 'aaff54d66aa533d6cf7f22582420a7edc69aea67' (/usr/lib64/libGL.so.1)
WARNING:root:Unable to find binary package for '71abd4ec83f255a0767af3be2dda73455bbc2ad9' (/usr/lib64/libGLU.so.1)
WARNING:root:Unable to find binary package for '7343d35696ce251688ece0a26e457e61ca805cfd' (/usr/lib64/libXxf86vm.so.1)
WARNING:root:Unable to find binary package for 'f8f4d8e260ee8f3b262936920270ace01b2da537' (/lib64/libpthread.so.0)
WARNING:root:Unable to find binary package for 'd0c6e13f00a20952a72a945c929efb175fd760e3' (/usr/lib64/libSM.so.6)
WARNING:root:Unable to find binary package for '25b834f4c4dc534708635ff1064e2fe02a366a62' (/usr/lib64/libICE.so.6)
WARNING:root:Unable to find binary package for '40dc5e32f96a3d6d6728301becc415c9af4a68bb' (/usr/lib64/libXt.so.6)
WARNING:root:Unable to find binary package for '4c842320387ff7f6f91b7842b223c16518be909f' (/usr/lib64/libX11.so.6)
WARNING:root:Unable to find binary package for '11e343f1da2a0c5c61502657909b8c4fe5e21b72' (/usr/lib64/libXmu.so.6)
WARNING:root:Unable to find binary package for 'dc998e8c1e1dc44c684b9b86e753945a868e134a' (/usr/lib64/libXext.so.6)
WARNING:root:Unable to find binary package for '3437fbc1b9876f2d55c8c9beffbda021a61b1e61' (/lib64/libm.so.6)
WARNING:root:Unable to find binary package for '2e4f144d6c8fb2dbb214fdbea0c327b05fa70a78' (/lib64/libc.so.6)
WARNING:root:Unable to find binary package for '36a149d1e2c29890b616402f6bc5e3f69ca2738e' (/usr/lib64/libXdamage.so.1)
WARNING:root:Unable to find binary package for '163b323da65b708418226eb5fa8b057c731d1475' (/usr/lib64/libXfixes.so.3)
WARNING:root:Unable to find binary package for '632fc539af09eb4a85682be1034d7a99fc864a95' (/usr/lib64/libdrm.so.2)
WARNING:root:Unable to find binary package for '58803db420709341d8e6a713b18e54a6e1824272' (/lib64/libdl.so.2)
WARNING:root:Unable to find binary package for '3ba5302e34546a45e9a85ac3429e7bc6ed624011' (/usr/lib64/libstdc++.so.6)
WARNING:root:Unable to find binary package for '75eaece6e0d1e075520cdfad5c398fdab4370846' (/lib64/libgcc_s.so.1)
WARNING:root:Unable to find binary package for 'e7160fedcf92e2c07f8883f15c71d703b9e7abcb' (/lib64/ld-linux-x86-64.so.2)
WARNING:root:Unable to find binary package for '7a896ce784b97721d1f6960bfba25e60511c0178' (/lib64/libuuid.so.1)
WARNING:root:Unable to find binary package for '7994f114cf7189e482f2665fae8e351ed8bc05e3' (/usr/lib64/libxcb.so.1)
WARNING:root:Unable to find binary package for '6cded60dd119fb8b8aa41b264e12931cb2c7b67f' (/lib64/librt.so.1)
WARNING:root:Unable to find binary package for '1c6a95451ee19617be5abea3d121f0226d21ddda' (/usr/lib64/libXau.so.6)
WARNING:root:Unable to find binary package for '13bd265cb8078c8fc2d9dcd59bd14d52a1446f3a' (/usr/lib64/dri/r600_dri.so)
WARNING:root:Unable to find binary package for 'e3c88cb9ea428bd61f4064dbd53acae2d396a1ec' (/usr/lib64/libffi.so.5)
WARNING:root:Unable to find binary package for '4b4285058f7f6b39b7e7c45df83fd36c6833bfe4' (/lib64/libselinux.so.1)
WARNING:root:Unable to find binary package for 'bf404f1f16ae38c405a644f7f2a5a3de02e5d158' (/lib64/libexpat.so.1)
WARNING:root:Unable to find binary package for '455ba5e1f9bfbe95b5d751aade0fe830576d21c6' (/usr/lib64/llvm/libLLVM-2.9.so)
WARNING:root:Unable to find binary package for 'c2d49d72ec1a1e68b39c3724693f83f44d80a259' (/usr/lib64/libXcursor.so.1)
WARNING:root:Unable to find binary package for '0911ea7c180d733724f89037b8e8a34e64024aec' (/usr/lib64/libXrender.so.1)
OK
Initializing virtual root Error 26:
=== OUTPUT ===
INFO: mock.py version 1.1.18 starting...
State Changed: init plugins
INFO: selinux enabled
State Changed: start
State Changed: lock buildroot
State Changed: shell
rpm2cpio: /packages/*: No such file or directory
cpio: premature end of archive
State Changed: unlock buildroot


(exited with 1)

Comment 1 Mamoru TASAKA 2012-11-01 13:52:11 UTC
Maybe the coredump for this segv is left under ~/.cache/abrt ? If so, would you take backtrace for this?

Comment 2 Peter H. Jones 2012-11-01 16:09:14 UTC
It wasn't there. Maybe in /var/spool/abrt, but it wasn't obvious. I can look again later.

I tried generating a local GNU backtrace, but I could not submit it because the backtrace was unusable. Is it still worthwhile to find the coredump?

Comment 3 Mamoru TASAKA 2012-11-02 00:34:37 UTC
(In reply to comment #1)
> Maybe the coredump for this segv is left under ~/.cache/abrt ? If so, would
> you take backtrace for this?

Well, actually under ~/.cache/abrt/spool/ccpp-XXXXXXXX/.

(In reply to comment #2)
> It wasn't there. Maybe in /var/spool/abrt, but it wasn't obvious. I can look
> again later.
> 
> I tried generating a local GNU backtrace, but I could not submit it because
> the backtrace was unusable. Is it still worthwhile to find the coredump?

Unless coredump I cannot figure out what is the cause, so I appreciate it if you can.

Comment 4 Peter H. Jones 2012-11-05 14:08:13 UTC
Created attachment 638647 [details]
compressed tar of core dump archive

The files generated by abrt are in $HOME/.abrt/spool . Here is the tar of all the files in this morning's occurrence. Hope it helps.

Comment 5 Mamoru TASAKA 2012-11-06 00:40:34 UTC
Would you take backtrace from coredump by yourself? Currently I have no x86_64 machine available, and even if I get the one, it may be impossible to generate backtrace from your coredump on that machine.

Comment 6 Mamoru TASAKA 2012-11-06 00:55:11 UTC
(I checked "backtrace" file in the tarball but the generated backtrace was incomplete)

Comment 7 Mamoru TASAKA 2012-11-07 14:40:26 UTC
Well, now I could access one x86_64 machine, so I tried to get proper backtrace using mock environment, however gdb complains about "No symbol table info available", even if proper debuginfo rpms are installed... Currently I don't know how to debug this...

Comment 8 Peter H. Jones 2012-11-08 13:51:49 UTC
From my yum.log:

Nov 06 07:28:29 Installed: kernel-3.6.5-2.fc16.x86_64
Nov 08 07:51:00 Updated: 1:xscreensaver-base-5.20-3.fc16.x86_64
Nov 08 07:51:02 Updated: 1:xscreensaver-extras-base-5.20-3.fc16.x86_64
Nov 08 07:51:02 Updated: 1:xscreensaver-gl-base-5.20-3.fc16.x86_64
Nov 08 07:51:12 Updated: xulrunner-16.0.2-1.fc16.x86_64
Nov 08 07:51:25 Updated: firefox-16.0.2-1.fc16.x86_64
Nov 08 07:51:32 Updated: 1:xscreensaver-gl-extras-5.20-3.fc16.x86_64
Nov 08 07:51:37 Updated: 1:xscreensaver-extras-5.20-3.fc16.x86_64

Since I now have an updated xscreensaver, I propose to wait for a new occurrence before putting more effort in analyzing the dumps I already have.

Comment 9 Mamoru TASAKA 2012-11-08 14:07:17 UTC
Okay, if this issue reproduces, please let me know it then. Thank you for reporting anyway.

Comment 10 Peter H. Jones 2012-11-16 03:22:24 UTC
Created attachment 646164 [details]
compressed tar of core dump archive

Got the bug again. I have uploaded the compressed tar produced by ABRT. Once again, ABRT says the backtrace is unusable.

Comment 11 Mamoru TASAKA 2012-11-16 08:11:32 UTC
Just for sure:

* Would you write the result of the below?
$ rpm -qf /usr/libexec/xscreensaver/pinion /usr/lib64/libGL.so.1 /usr/lib64/libGLU.so.1 /lib64/libc.so.6 /usr/lib64/libX11.so.6

* Also would you attach /etc/X11/xorg.conf (if this exists) and /var/log/Xorg.0.log ?

Comment 12 Peter H. Jones 2012-11-16 14:13:00 UTC
Created attachment 646335 [details]
Xorg.0.log requested

I have several files with similar names. I am uploading the one that was requested.

Comment 13 Mamoru TASAKA 2012-11-16 17:33:21 UTC
And would you show me the result of the commend in my comment 12 for confirmation? Thank you.

Comment 14 Mamoru TASAKA 2012-11-16 17:39:57 UTC
Oops, in my comment 11, sorry.

Comment 15 Mamoru TASAKA 2012-11-16 17:43:37 UTC
Oh, it was on dso_list file...

Comment 16 Peter H. Jones 2012-11-17 20:48:22 UTC
I don't have /etc/X11/xorg.conf, just a directory with one file, 
/etc/X11/xorg.conf/00-system-setup-keyboard.conf, containing:
# This file is autogenerated by system-setup-keyboard. Any 
# modifications will be lost.

Section "InputClass"
        Identifier      "system-setup-keyboard"
        MatchIsKeyboard "on"
        Option          "XkbModel"      "pc105"
        Option          "XkbLayout"     "us"
        Option          "XkbVariant"    "intl"
        Option          "XkbOptions"    "terminate:ctrl_alt_bksp,"
EndSection

AFAIK I haven't modified this file.

Comment 17 Mamoru TASAKA 2012-11-19 09:21:39 UTC
gdb maintainer, would you have some idea why I cannot generate proper backtrace even if I install debuginfo rpms (which I assume are proper)? Any help is appreciated.

Comment 18 Jan Kratochvil 2012-11-19 10:08:51 UTC
The Comment 10 crash is at 0x7f1b361fe460:
  Type Offset   VirtAddr       PhysAddr       FileSiz  MemSiz   Flg Align
  LOAD 0x77b000 0x7f1b361fe000 0x000000000000 0x080000 0x080000 RWE 0x1000
maps:
7f1b361f6000-7f1b361fe000 rw-s 10b39a000 00:05 6683 /dev/dri/card0
7f1b361fe000-7f1b3627e000 rwxp 00000000 00:00 0
7f1b3627e000-7f1b3627f000 rw-s 10b399000 00:05 6683 /dev/dri/card0

The address does not belong to any ELF executable there.

RWE is unusual on GNU/Linux.  And the code looks like some gfx acceleration:
(gdb) x/20i $pc
=> 0x7f1b361fe460:	movss  (%r15,%rcx,1),%xmm2
   0x7f1b361fe466:	movss  0x4(%r15,%rcx,1),%xmm3
   0x7f1b361fe46d:	movss  (%r15,%rdi,1),%xmm4

So I believe it is some JIT code, GDB has framework for JIT debugging but I do not whether the drivers provide some features for it.  Moreover it is not loaded automatically by GDB so one would need to know what to execute in GDB.

Comment 19 Mamoru TASAKA 2012-11-19 13:45:49 UTC
Jan, thank you for analysing.

Comment 20 Peter H. Jones 2012-11-20 21:12:02 UTC
Created attachment 648840 [details]
ABRT log file of another occurrence

Comment 21 Mamoru TASAKA 2012-11-29 01:00:51 UTC
Judging from Jan's comment, once reassigning to mesa(-dri-drivers) and asking for help.

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

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 16'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 16 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 to click on 
"Clone This Bug" and open it against that version of Fedora.

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: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 23 Fedora End Of Life 2013-02-13 08:26:26 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.