Bug 1147118 - [abrt] systemd: _xbegin(): systemd killed by SIGILL
Summary: [abrt] systemd: _xbegin(): systemd killed by SIGILL
Keywords:
Status: CLOSED DUPLICATE of bug 1146967
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 20
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:c3f32ed0fc791b3b6fb1bc5a651...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-27 03:27 UTC by Bill
Modified: 2014-09-27 23:10 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-09-27 23:10:41 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (12.35 KB, text/plain)
2014-09-27 03:27 UTC, Bill
no flags Details
File: cgroup (167 bytes, text/plain)
2014-09-27 03:27 UTC, Bill
no flags Details
File: core_backtrace (3.96 KB, text/plain)
2014-09-27 03:27 UTC, Bill
no flags Details
File: dso_list (2.21 KB, text/plain)
2014-09-27 03:27 UTC, Bill
no flags Details
File: exploitable (103 bytes, text/plain)
2014-09-27 03:27 UTC, Bill
no flags Details
File: limits (1.29 KB, text/plain)
2014-09-27 03:27 UTC, Bill
no flags Details
File: maps (9.81 KB, text/plain)
2014-09-27 03:27 UTC, Bill
no flags Details
File: open_fds (133 bytes, text/plain)
2014-09-27 03:27 UTC, Bill
no flags Details
File: proc_pid_status (902 bytes, text/plain)
2014-09-27 03:27 UTC, Bill
no flags Details
File: var_log_messages (15.39 KB, text/plain)
2014-09-27 03:27 UTC, Bill
no flags Details

Description Bill 2014-09-27 03:27:17 UTC
Description of problem:
Occurred shortly after logging in to gnome shell. I suspect the problem is due to below. I removed the minidlna package as I switched to using rygel via gnome media sharing. However removing the minidlna package did not clean up the systemd setup for minidlna. I have now manually disabled the minidlna.service. Hopefuly that should work around the problem but  it really appears to be a packaging error.

systemctl status minidlna.service
minidlna.service - MiniDLNA is a DLNA/UPnP-AV server software
   Loaded: loaded (/usr/lib/systemd/system/minidlna.service; enabled)
   Active: failed (Result: core-dump) since Sat 2014-09-27 13:47:25 NZST; 26min ago
  Process: 1112 ExecStart=/usr/sbin/minidlnad -S (code=dumped, signal=ILL)
 Main PID: 1112 (code=dumped, signal=ILL)
   CGroup: /system.slice/minidlna.service

Sep 27 13:47:25 e6540 systemd[1]: Started MiniDLNA is a DLNA/UPnP-AV server...e.
Sep 27 13:47:25 e6540 systemd[1]: minidlna.service: main process exited, co...LL
Sep 27 13:47:25 e6540 systemd[1]: Unit minidlna.service entered failed state.
Hint: Some lines were ellipsized, use -l to show in full.

Version-Release number of selected component:
systemd-208-22.fc20

Additional info:
reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        (inidlnad) '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' ''
crash_function: _xbegin
environ:        
executable:     /usr/lib/systemd/systemd
kernel:         3.16.3-200.fc20.x86_64
runlevel:       unknown
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 _xbegin at ../nptl/sysdeps/unix/sysv/linux/x86/hle.h:53
 #1 __lll_lock_elision at ../nptl/sysdeps/unix/sysv/linux/x86/elision-lock.c:56
 #2 __pthread_mutex_lock at ../nptl/pthread_mutex_lock.c:91
 #3 _nss_files_getgrnam_r at nss_files/files-grp.c:32
 #4 __getgrnam_r at ../nss/getXXbyYY_r.c:266
 #5 getgrnam at ../nss/getXXbyYY.c:116
 #6 get_group_creds at ../src/shared/util.c:4405
 #7 enforce_groups at ../src/core/execute.c:588
 #8 exec_spawn at ../src/core/execute.c:1312
 #9 service_spawn at ../src/core/service.c:1865

Comment 1 Bill 2014-09-27 03:27:21 UTC
Created attachment 941773 [details]
File: backtrace

Comment 2 Bill 2014-09-27 03:27:22 UTC
Created attachment 941774 [details]
File: cgroup

Comment 3 Bill 2014-09-27 03:27:23 UTC
Created attachment 941775 [details]
File: core_backtrace

Comment 4 Bill 2014-09-27 03:27:25 UTC
Created attachment 941776 [details]
File: dso_list

Comment 5 Bill 2014-09-27 03:27:26 UTC
Created attachment 941777 [details]
File: exploitable

Comment 6 Bill 2014-09-27 03:27:27 UTC
Created attachment 941778 [details]
File: limits

Comment 7 Bill 2014-09-27 03:27:29 UTC
Created attachment 941779 [details]
File: maps

Comment 8 Bill 2014-09-27 03:27:30 UTC
Created attachment 941780 [details]
File: open_fds

Comment 9 Bill 2014-09-27 03:27:31 UTC
Created attachment 941781 [details]
File: proc_pid_status

Comment 10 Bill 2014-09-27 03:27:33 UTC
Created attachment 941782 [details]
File: var_log_messages

Comment 11 Zbigniew Jędrzejewski-Szmek 2014-09-27 23:10:41 UTC
Other bugs nonwithstanding, SIGKILL is probably caused by the firmware problem.

*** This bug has been marked as a duplicate of bug 1146967 ***


Note You need to log in before you can comment on or make changes to this bug.