Bug 1271362
| Summary: | [abrt] systemd: __fsync_nocancel(): systemd-journald killed by SIGABRT | ||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Philip Southam <rhbugzilla> | ||||||||||||||||||||||||
| Component: | systemd | Assignee: | systemd-maint | ||||||||||||||||||||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||||||||||||||
| Priority: | unspecified | ||||||||||||||||||||||||||
| Version: | 23 | CC: | brian, bugzilla, bugzilla, foss, gabriel, geezuslucifer, johannbg, jorti, jsynacek, lnykryn, madstitz, martinojones_2009, mauro.risonho, mikhail.rokhin, mikhail.v.gavrilov, mjs, msekleta, niki.guldbrand, oleg, s, sudhir, systemd-maint, szymon.janc, yonatan.el.amigo, zbyszek | ||||||||||||||||||||||||
| Target Milestone: | --- | Keywords: | Reopened | ||||||||||||||||||||||||
| Target Release: | --- | ||||||||||||||||||||||||||
| Hardware: | x86_64 | ||||||||||||||||||||||||||
| OS: | Unspecified | ||||||||||||||||||||||||||
| URL: | https://retrace.fedoraproject.org/faf/reports/bthash/54a1961df5aba1cdfe034b1a39c7d9a30f42de2f | ||||||||||||||||||||||||||
| Whiteboard: | abrt_hash:86f138cef05397a91495e5cc046d85c78b14939e;VARIANT_ID=workstation; | ||||||||||||||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||||||||||||
| Last Closed: | 2016-01-20 09:44:40 UTC | Type: | --- | ||||||||||||||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||||||||||||||
| Documentation: | --- | CRM: | |||||||||||||||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||||||||||||
| Embargoed: | |||||||||||||||||||||||||||
| Attachments: |
|
||||||||||||||||||||||||||
|
Description
Philip Southam
2015-10-13 18:35:30 UTC
Created attachment 1082566 [details]
File: backtrace
Created attachment 1082567 [details]
File: cgroup
Created attachment 1082568 [details]
File: core_backtrace
Created attachment 1082569 [details]
File: dso_list
Created attachment 1082570 [details]
File: environ
Created attachment 1082571 [details]
File: limits
Created attachment 1082572 [details]
File: maps
Created attachment 1082573 [details]
File: mountinfo
Created attachment 1082574 [details]
File: namespaces
Created attachment 1082575 [details]
File: open_fds
Created attachment 1082576 [details]
File: proc_pid_status
*** Bug 1271363 has been marked as a duplicate of this bug. *** *** Bug 1271365 has been marked as a duplicate of this bug. *** fsync() failed 3 times in a row on your machine. Is your hard drive failing? *** Bug 1254351 has been marked as a duplicate of this bug. *** *** Bug 1282538 has been marked as a duplicate of this bug. *** *** Bug 1277817 has been marked as a duplicate of this bug. *** *** Bug 1284715 has been marked as a duplicate of this bug. *** *** Bug 1262607 has been marked as a duplicate of this bug. *** *** Bug 1290134 has been marked as a duplicate of this bug. *** Another user experienced a similar problem: This happened about ten minutes before an unattended lockup. reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/lib/systemd/systemd-journald crash_function: __fsync_nocancel executable: /usr/lib/systemd/systemd-journald global_pid: 861 kernel: 4.2.6-301.fc23.x86_64 package: systemd-222-8.fc23 reason: systemd-journald killed by SIGABRT runlevel: N 5 type: CCpp uid: 0 *** Bug 1291388 has been marked as a duplicate of this bug. *** I got this also, well, actually bug 1271363 which is closed as a duplicate of this bug. I don't have a failing HDD. So perhaps this problem is something other than failing hardware? When waking from suspend, Abrt sends me to bug 1254351, which sends me here. There is no failing hard drive. a. smartctl attributes are all normal for this Samsung SSD, b. Btrfs scrub comes up clean, c. there are no kernel messages indicating any sort of drive or drive connectivity problem. *** This bug has been marked as a duplicate of bug 1300212 *** |