Bug 1033977

Summary: [abrt] virtuoso-opensource-6.1.6-5.fc20: gpf_notice: Process /usr/bin/virtuoso-t was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: sean_mccully
Component: virtuoso-opensourceAssignee: Rex Dieter <rdieter>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: ct760ster, cunio, jludvice, kvolny, ltinkl, paul.lipps, pingou, rdieter, tcarlin, than
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/c2bb9c46c829a7ffad499c6298fd4c80f03fc6ce
Whiteboard: abrt_hash:48729e585bfb13115075b17acd92fdc0543645dc
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-30 12:27:24 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description sean_mccully 2013-11-24 22:47:18 UTC
Version-Release number of selected component:
virtuoso-opensource-6.1.6-5.fc20

Additional info:
reporter:       libreport-2.1.9
backtrace_rating: 4
cmdline:        /usr/bin/virtuoso-t +foreground +configfile /tmp/virtuoso_dT1903.ini +wait
crash_function: gpf_notice
executable:     /usr/bin/virtuoso-t
kernel:         3.11.9-300.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 gpf_notice at Dkutil.c:84
 #1 it_cp_check_node at insert.c:1172
 #2 it_check_compact at insert.c:1294
 #3 wi_check_all_compact at insert.c:1332
 #4 bp_stat_action at disk.c:998
 #5 bp_get_buffer_1 at disk.c:1129
 #6 page_wait_access at gate.c:178
 #7 itc_dive_transit at gate.c:898
 #8 itc_page_insert_search at search.c:2400
 #9 itc_search at search.c:1538

Potential duplicate: bug 859764

Comment 1 sean_mccully 2013-11-24 22:47:25 UTC
Created attachment 828440 [details]
File: backtrace

Comment 2 sean_mccully 2013-11-24 22:47:28 UTC
Created attachment 828441 [details]
File: cgroup

Comment 3 sean_mccully 2013-11-24 22:47:31 UTC
Created attachment 828442 [details]
File: core_backtrace

Comment 4 sean_mccully 2013-11-24 22:47:34 UTC
Created attachment 828443 [details]
File: dso_list

Comment 5 sean_mccully 2013-11-24 22:47:37 UTC
Created attachment 828444 [details]
File: environ

Comment 6 sean_mccully 2013-11-24 22:47:40 UTC
Created attachment 828445 [details]
File: exploitable

Comment 7 sean_mccully 2013-11-24 22:47:43 UTC
Created attachment 828446 [details]
File: limits

Comment 8 sean_mccully 2013-11-24 22:47:46 UTC
Created attachment 828447 [details]
File: maps

Comment 9 sean_mccully 2013-11-24 22:47:49 UTC
Created attachment 828448 [details]
File: open_fds

Comment 10 sean_mccully 2013-11-24 22:47:52 UTC
Created attachment 828449 [details]
File: proc_pid_status

Comment 11 sean_mccully 2013-11-24 22:47:55 UTC
Created attachment 828450 [details]
File: var_log_messages

Comment 12 Karel Volný 2014-02-19 13:53:27 UTC
Another user experienced a similar problem:

don't know, it just crashed in the background

reporter:       libreport-2.1.12
backtrace_rating: 4
cmdline:        /usr/bin/virtuoso-t +foreground +configfile /tmp/virtuoso_BC1155.ini +wait
crash_function: gpf_notice
executable:     /usr/bin/virtuoso-t
kernel:         3.12.8-300.fc20.x86_64
package:        virtuoso-opensource-6.1.6-5.fc20
reason:         virtuoso-t killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 13 Karel Volný 2014-06-14 18:57:19 UTC
Another user experienced a similar problem:

it crashed in the background

reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        /usr/bin/virtuoso-t +foreground +configfile /tmp/virtuoso_dT1694.ini +wait
crash_function: gpf_notice
executable:     /usr/bin/virtuoso-t
kernel:         3.14.6-200.fc20.x86_64
package:        virtuoso-opensource-6.1.6-5.fc20
reason:         virtuoso-t killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 14 Thom Carlin 2014-07-01 23:02:43 UTC
Another user experienced a similar problem: ditto

Comment 15 Fedora End Of Life 2015-05-29 09:50:46 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 16 Jaroslav Reznik 2015-06-30 12:27:24 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.