[Bug 1754921] Re: systemd-journald crashed with SIGABRT in fsync()
Apport retracing service
1754921 at bugs.launchpad.net
Sun Mar 11 06:10:00 UTC 2018
*** This bug is a duplicate of bug 1750855 ***
https://bugs.launchpad.net/bugs/1750855
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1750855, so is being marked as such. Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Please continue to report any other bugs you may
find.
** Attachment removed: "CoreDump.gz"
https://bugs.launchpad.net/bugs/1754921/+attachment/5075591/+files/CoreDump.gz
** Attachment removed: "Disassembly.txt"
https://bugs.launchpad.net/bugs/1754921/+attachment/5075594/+files/Disassembly.txt
** Attachment removed: "ProcMaps.txt"
https://bugs.launchpad.net/bugs/1754921/+attachment/5075600/+files/ProcMaps.txt
** Attachment removed: "ProcStatus.txt"
https://bugs.launchpad.net/bugs/1754921/+attachment/5075602/+files/ProcStatus.txt
** Attachment removed: "Registers.txt"
https://bugs.launchpad.net/bugs/1754921/+attachment/5075603/+files/Registers.txt
** Attachment removed: "Stacktrace.txt"
https://bugs.launchpad.net/bugs/1754921/+attachment/5075604/+files/Stacktrace.txt
** Attachment removed: "ThreadStacktrace.txt"
https://bugs.launchpad.net/bugs/1754921/+attachment/5075605/+files/ThreadStacktrace.txt
** This bug has been marked a duplicate of private bug 1750855
** Information type changed from Private to Public
** Tags removed: need-amd64-retrace
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1754921
Title:
systemd-journald crashed with SIGABRT in fsync()
Status in systemd package in Ubuntu:
New
Bug description:
Just after booting.
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: systemd 237-3ubuntu4
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
Date: Sat Mar 10 19:47:42 2018
ExecutablePath: /lib/systemd/systemd-journald
InstallationDate: Installed on 2018-03-08 (2 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180307)
JournalErrors:
-- Logs begin at Sat 2018-03-10 11:26:25 EET, end at Sun 2018-03-11 08:02:14 EET. --
мар 11 07:30:38 hostname systemd-udevd[409]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0xc022d, key code 103): Invalid argument
мар 11 07:30:38 hostname systemd-udevd[409]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0xc022e, key code 108): Invalid argument
мар 11 07:30:44 hostname spice-vdagent[2673]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
мар 11 07:31:08 hostname pulseaudio[2555]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)
MachineType: Intel Thurley
ProcCmdline: /lib/systemd/systemd-journald
ProcEnviron:
LANG=ru_UA.UTF-8
LANGUAGE=ru_UA:ru
PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=76ae456f-1793-40e3-ac19-2829d2667881 ro quiet splash vt.handoff=1
Signal: 6
SourcePackage: systemd
StacktraceTop:
fsync (fd=27) at ../sysdeps/unix/sysv/linux/fsync.c:27
?? () from /lib/systemd/libsystemd-shared-237.so
journal_file_append_object () from /lib/systemd/libsystemd-shared-237.so
?? () from /lib/systemd/libsystemd-shared-237.so
journal_file_append_entry () from /lib/systemd/libsystemd-shared-237.so
SystemdDelta:
[EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf
[EXTENDED] /lib/systemd/system/user at .service → /lib/systemd/system/user at .service.d/timeout.conf
2 overridden configuration files found.
Title: systemd-journald crashed with SIGABRT in fsync()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 05/13/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080016
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: X58
dmi.board.vendor: Mainboard
dmi.board.version: V3.10
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Intel
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080016:bd05/13/2017:svnIntel:pnThurley:pvrToBeFilledByO.E.M.:rvnMainboard:rnX58:rvrV3.10:cvnIntel:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: High-End Desktop
dmi.product.name: Thurley
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: Intel
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1754921/+subscriptions
More information about the foundations-bugs
mailing list