Version-Release number of selected component: systemd-44-21.fc17 Additional info: libreport version: 2.0.18 abrt_version: 2.0.18 backtrace_rating: 4 cmdline: /usr/lib/systemd/systemd crash_function: crash kernel: 3.6.10-2.fc17.x86_64 truncated backtrace: :Thread no. 1 (9 frames) : #1 crash at src/core/main.c:137 : #3 transaction_verify_order_one at src/core/transaction.c:406 : #9 transaction_verify_order at src/core/transaction.c:438 : #10 transaction_activate at src/core/transaction.c:643 : #11 manager_add_job at src/core/manager.c:707 : #12 bus_manager_message_handler at src/core/dbus-manager.c:1612 : #13 _dbus_object_tree_dispatch_and_unlock at dbus-object-tree.c:858 : #15 bus_dispatch at src/core/dbus.c:527 : #16 manager_loop at src/core/manager.c:1454 Potential duplicate bug: 729172
Created attachment 665675 [details] File: core_backtrace
Created attachment 665676 [details] File: environ
Created attachment 665677 [details] File: event_log
Created attachment 665678 [details] File: backtrace
Created attachment 665679 [details] File: limits
Created attachment 665680 [details] File: smolt_data
Created attachment 665681 [details] File: cgroup
Created attachment 665682 [details] File: executable
Created attachment 665683 [details] File: maps
Created attachment 665684 [details] File: dso_list
Created attachment 665685 [details] File: proc_pid_status
Created attachment 665686 [details] File: var_log_messages
Created attachment 665687 [details] File: open_fds
I found a suspicious thing in the backtrace. In frame #3 there is: u = 0x200000243b180 This is outside the mapped address space of the process. Notice though that 0x243b180 would look reasonable, it would be inside the heap area. So this looks very much like memory corruption. A single-bit fault. This could be bad RAM. Could you run memtest86+ on the machine for a few hours? Did the error occur after resume from suspend or hibernation?
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 WONTFIX if it remains open with a Fedora 'version' of '17'. 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 prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 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 to Fedora 17's end of life. 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.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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. Thank you for reporting this bug and we are sorry it could not be fixed.