Bug 951103 - knotify4 segfaults on ppc64
Summary: knotify4 segfaults on ppc64
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: orc
Version: 19
Hardware: ppc64
OS: Linux
medium
high
Target Milestone: ---
Assignee: Fabian Deutsch
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-04-11 13:35 UTC by Karsten Hopp
Modified: 2015-02-17 14:58 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-17 14:58:17 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
kcrash file (17.83 KB, text/plain)
2013-04-11 13:35 UTC, Karsten Hopp
no flags Details

Description Karsten Hopp 2013-04-11 13:35:11 UTC
Created attachment 734198 [details]
kcrash file

Description of problem:
Fresh istallation of PPC64 TC6.2 (http://ppc.koji.fedoraproject.org/stage/f19-20130410-TC6.2/ppc64/).
Shortly after startup knotify4 crashes, without any user interaction.

Version-Release number of selected component (if applicable):
kde-runtime-4.10.1-3.fc19

How reproducible:


Steps to Reproduce:
1. install PPc64 with KDE 
2. start vncserver
3. connect to vncserver and wait for the crash reporting assistent to pop up
  
Actual results:
knotify4 segfaults

Comment 1 Rex Dieter 2013-04-11 13:58:03 UTC
Not entirely sure, it's either

something bad in orc:

Thread 4 (Thread 0x3fff7bfef070 (LWP 8764)):
[KCrash Handler]
#6  0x00003fff8598076c in ?? ()
#7  0x00003fff84fa4084 in orc_audio_convert_unpack_float_s32 (d1=0x0, s1=0x4b800000050, n=1610670656) at tmp-orc.c:1154
#8  0x00003fff7bfedd50 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

or gstreamer-related:

Thread 1 (Thread 0x3fff8fc31cc0 (LWP 8075)):
#0  0x00000080eb545468 in __lll_lock_wait (futex=0x100397c4530, private=<optimized out>) at ../nptl/sysdeps/unix/sysv/linux/lowlevellock.c:46
#1  0x00000080eb53ea80 in __GI___pthread_mutex_lock (mutex=<optimized out>) at pthread_mutex_lock.c:85
#2  0x00000080eb936244 in g_rec_mutex_lock (mutex=<optimized out>) at gthread-posix.c:379
#3  0x00000080eb89825c in g_static_rec_mutex_lock (mutex=0x1003938c800) at deprecated/gthread-deprecated.c:716
#4  0x00000080f01bb3dc in gst_base_transform_activate (trans=trans@entry=0x1003973c030, active=active@entry=0) at gstbasetransform.c:2767

Comment 2 Rex Dieter 2013-04-11 14:05:09 UTC
Or, after looking at bug #951109 , I see that these both died in the same lll_futex_wait function.  Here,

Application: KNotify (knotify4), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
46	    lll_futex_wait (futex, 2, private);
[Current thread is 1 (Thread 0x3fff8fc31cc0 (LWP 8075))]

Comment 3 Kevin Kofler 2013-04-11 15:22:21 UTC
When looking at a crash of a multithreaded program, the first thing to do is to identify the active thread, usually the only relevant one. Any thread stuck in something like lll_futex_wait, __lll_lock_wait etc. is NOT active.

The issue looks like an ORC bug. ORC (OIL (Optimized Inner Loops) Runtime Compiler) is a JIT for inner loops used by GStreamer. Reassigning to orc.

Comment 4 Fedora End Of Life 2015-01-09 17:52:39 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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 19 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 5 Fedora End Of Life 2015-02-17 14:58:17 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.