Bug 2162259 - [abrt] rasdaemon: ___pthread_mutex_lock(): rasdaemon killed by SIGSEGV
Summary: [abrt] rasdaemon: ___pthread_mutex_lock(): rasdaemon killed by SIGSEGV
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: rasdaemon
Version: 37
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Mauro Carvalho Chehab
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:d22ee91948cdb19ecaa31def0b8...
: 2195930 2196264 2225272 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-01-19 08:38 UTC by sheepdestroyer
Modified: 2023-12-07 14:57 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2023-12-07 14:57:33 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (80.91 KB, text/plain)
2023-01-19 08:38 UTC, sheepdestroyer
no flags Details
File: core_backtrace (17.28 KB, text/plain)
2023-01-19 08:38 UTC, sheepdestroyer
no flags Details
File: cpuinfo (2.50 KB, text/plain)
2023-01-19 08:38 UTC, sheepdestroyer
no flags Details
File: dso_list (398 bytes, text/plain)
2023-01-19 08:38 UTC, sheepdestroyer
no flags Details
File: environ (420 bytes, text/plain)
2023-01-19 08:38 UTC, sheepdestroyer
no flags Details
File: exploitable (82 bytes, text/plain)
2023-01-19 08:38 UTC, sheepdestroyer
no flags Details
File: limits (1.29 KB, text/plain)
2023-01-19 08:38 UTC, sheepdestroyer
no flags Details
File: maps (3.97 KB, text/plain)
2023-01-19 08:38 UTC, sheepdestroyer
no flags Details
File: mountinfo (2.83 KB, text/plain)
2023-01-19 08:38 UTC, sheepdestroyer
no flags Details
File: open_fds (1.59 KB, text/plain)
2023-01-19 08:38 UTC, sheepdestroyer
no flags Details
File: proc_pid_status (1.33 KB, text/plain)
2023-01-19 08:38 UTC, sheepdestroyer
no flags Details
File: var_log_messages (8.58 KB, text/plain)
2023-01-19 08:38 UTC, sheepdestroyer
no flags Details

Description sheepdestroyer 2023-01-19 08:38:22 UTC
Version-Release number of selected component:
rasdaemon-0.6.8-2.fc37

Additional info:
reporter:       libreport-2.17.4
backtrace_rating: 4
cgroup:         0::/system.slice/rasdaemon.service
cmdline:        /usr/sbin/rasdaemon -f -r
crash_function: ___pthread_mutex_lock
executable:     /usr/sbin/rasdaemon
journald_cursor: s=5008a8daea714be1bb7b597061914d69;i=1cb29;b=2c1592c73ce74878a81d6d322b0fae84;m=444dbcf61;t=5f259c96aeb87;x=bd2f85c0325c4cf3
kernel:         6.0.18-300.fc37.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 1 (5 frames)
 #0 ___pthread_mutex_lock at pthread_mutex_lock.c:80
 #1 sqlite3_finalize at /usr/src/debug/sqlite-3.40.0-1.fc37.x86_64/sqlite3.c:87366
 #2 ras_mc_event_closedb.isra.0 at /usr/src/debug/rasdaemon-0.6.8-2.fc37.x86_64/ras-record.c:923
 #3 handle_ras_events_cpu at /usr/src/debug/rasdaemon-0.6.8-2.fc37.x86_64/ras-events.c:608
 #5 clone3 at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Comment 1 sheepdestroyer 2023-01-19 08:38:25 UTC
Created attachment 1939100 [details]
File: backtrace

Comment 2 sheepdestroyer 2023-01-19 08:38:26 UTC
Created attachment 1939101 [details]
File: core_backtrace

Comment 3 sheepdestroyer 2023-01-19 08:38:27 UTC
Created attachment 1939102 [details]
File: cpuinfo

Comment 4 sheepdestroyer 2023-01-19 08:38:29 UTC
Created attachment 1939103 [details]
File: dso_list

Comment 5 sheepdestroyer 2023-01-19 08:38:30 UTC
Created attachment 1939104 [details]
File: environ

Comment 6 sheepdestroyer 2023-01-19 08:38:31 UTC
Created attachment 1939105 [details]
File: exploitable

Comment 7 sheepdestroyer 2023-01-19 08:38:32 UTC
Created attachment 1939106 [details]
File: limits

Comment 8 sheepdestroyer 2023-01-19 08:38:33 UTC
Created attachment 1939107 [details]
File: maps

Comment 9 sheepdestroyer 2023-01-19 08:38:34 UTC
Created attachment 1939108 [details]
File: mountinfo

Comment 10 sheepdestroyer 2023-01-19 08:38:35 UTC
Created attachment 1939109 [details]
File: open_fds

Comment 11 sheepdestroyer 2023-01-19 08:38:36 UTC
Created attachment 1939110 [details]
File: proc_pid_status

Comment 12 sheepdestroyer 2023-01-19 08:38:37 UTC
Created attachment 1939111 [details]
File: var_log_messages

Comment 13 redhat 2023-05-06 16:33:46 UTC
*** Bug 2195930 has been marked as a duplicate of this bug. ***

Comment 14 redhat 2023-05-08 13:37:32 UTC
*** Bug 2196264 has been marked as a duplicate of this bug. ***

Comment 15 redhat 2023-07-24 20:28:20 UTC
*** Bug 2225272 has been marked as a duplicate of this bug. ***

Comment 16 Aoife Moloney 2023-11-23 01:00:42 UTC
This message is a reminder that Fedora Linux 37 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05.
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
'version' of '37'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 37 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 Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 17 Aoife Moloney 2023-12-07 14:57:33 UTC
Fedora Linux 37 entered end-of-life (EOL) status on 2023-12-05.

Fedora Linux 37 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 Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

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.