Bug 1073692 - Systemd generated coredump
Summary: Systemd generated coredump
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-03-06 23:57 UTC by Zdenek Kabelac
Modified: 2014-06-21 03:52 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-21 03:52:59 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
bt full (7.61 KB, text/plain)
2014-03-06 23:57 UTC, Zdenek Kabelac
no flags Details

Description Zdenek Kabelac 2014-03-06 23:57:35 UTC
Created attachment 871710 [details]
bt full

Description of problem:

Noticed crash of systemd:

[74441.852978] systemd[1]: Starting user-0.slice.
[74441.854126] systemd[1]: Created slice user-0.slice.
[74441.856994] systemd[1]: Starting User Manager for UID 0...
[74441.873493] systemd[1]: Starting Session 148 of user root.
[74441.876338] systemd[1]: Started Session 148 of user root.
[74441.931357] systemd[1]: Started User Manager for UID 0.
[74441.932174] systemd[1]: segfault at 7fd4afa42320 ip 00007fd4f70aa4ba sp 00007fffab25b180 error 4 in systemd[7fd4f6fef000+11f000]
[74442.009212] systemd[1]: Caught <SEGV>, dumped core as pid 1546.
[74442.011249] systemd[1]: Freezing execution.
[74442.289651] i2c i2c-2: NAK from device addr 0x50 msg #0
[74448.953060] i2c i2c-2: NAK from device addr 0x50 msg #0


#0  0x00007fd4f5907bdb in raise (sig=sig@entry=11) at ../nptl/sysdeps/unix/sysv/linux/pt-raise.c:37
#1  0x00007fd4f7068c3c in crash.2510 (sig=11) at ../src/core/main.c:151
#2  <signal handler called>
#3  0x00007fd4f70aa4ba in manager_invoke_notify_message (m=m@entry=0x7fd4f7df0150, u=0x7fd4f7e0e060, pid=1542, 
    buf=buf@entry=0x7fffab25b240 "READY=1\nSTATUS=Startup finished in 29ms.", n=n@entry=40) at ../src/core/manager.c:1335
#4  0x00007fd4f70aa769 in manager_dispatch_notify_fd.part.9 (userdata=0x7fd4f7df0150) at ../src/core/manager.c:1405
#5  0x00007fd4f70b0d41 in source_dispatch (s=0x7fd4f7dfb4f0) at ../src/libsystemd/sd-event/sd-event.c:1861
#6  0x00007fd4f70b2930 in sd_event_run (e=0x7fd4f7df0720, timeout=<optimized out>) at ../src/libsystemd/sd-event/sd-event.c:2117
#7  0x00007fd4f702aa84 in manager_loop (m=0x7fd4f7df0150) at ../src/core/manager.c:1844
#8  0x00007fd4f700ff86 in main (argc=5, argv=0x7fffab25cf38) at ../src/core/main.c:1693



Version-Release number of selected component (if applicable):
systemd-210-3.fc21.x86_64


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Lennart Poettering 2014-03-11 02:06:11 UTC
Fixed in git.


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