systemd-journald crashed with SIGABRT in dev_kmsg_record()

Bug #1500193 reported by dimitris
42
This bug affects 5 people
Affects Status Importance Assigned to Milestone
systemd (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

I don't know details

ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: systemd 225-1ubuntu4
ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1
Uname: Linux 4.2.0-11-generic x86_64
ApportVersion: 2.19-0ubuntu1
Architecture: amd64
Date: Sun Sep 27 01:21:55 2015
ExecutablePath: /lib/systemd/systemd-journald
InstallationDate: Installed on 2015-09-26 (1 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
Lsusb:
 Bus 003 Device 002: ID 8087:8000 Intel Corp.
 Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 064e:c341 Suyin Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC
ProcCmdline: /lib/systemd/systemd-journald
ProcEnviron:
 LANG=el_GR.UTF-8
 PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-11-generic.efi.signed root=UUID=38873c09-af33-49bc-a9cb-4762d8e857d1 ro quiet splash vt.handoff=7
Signal: 6
SourcePackage: systemd
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 __libc_start_main (main=0x55ee81dd0440, argc=1, argv=0x7fff46d4c1f8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff46d4c1e8) at libc-start.c:289
 ?? ()
Title: systemd-journald crashed with SIGABRT in __libc_start_main()
UdevLog: Error: [Errno 2] Δεν υπάρχει τέτοιο αρχείο ή κατάλογος: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 01/16/2014
dmi.bios.vendor: Insyde
dmi.bios.version: F.61
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 2166
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 29.42
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnInsyde:bvrF.61:bd01/16/2014:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr098B110000404100000620180:rvnHewlett-Packard:rn2166:rvr29.42:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP Pavilion 15 Notebook PC
dmi.product.version: 098B110000404100000620180
dmi.sys.vendor: Hewlett-Packard

Revision history for this message
dimitris (dimitrakhs9) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 dev_kmsg_record (l=49, p=0x7fff46d49dd2 "1004", s=0x7fff46d4beb0) at ../src/journal/journald-kmsg.c:150
 server_read_dev_kmsg.lto_priv.256 (s=0x7fff46d4beb0) at ../src/journal/journald-kmsg.c:348
 source_dispatch.lto_priv.254 (s=0x55ee82e696b0) at ../src/libsystemd/sd-event/sd-event.c:2116
 sd_event_dispatch (e=0x55ee82e691e0) at ../src/libsystemd/sd-event/sd-event.c:2472
 sd_event_run (timeout=<optimized out>, e=0x55ee82e691e0) at ../src/libsystemd/sd-event/sd-event.c:2500

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in systemd (Ubuntu):
importance: Undecided → Medium
summary: - systemd-journald crashed with SIGABRT in __libc_start_main()
+ systemd-journald crashed with SIGABRT in dev_kmsg_record()
tags: removed: need-amd64-retrace
Revision history for this message
Seth Arnold (seth-arnold) wrote : Bug is not a security issue

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

information type: Private Security → Public
Revision history for this message
Seth Arnold (seth-arnold) wrote :

If the kernel pipe mismatch messages keep happening, please also file a bug against the linux kernel with "ubuntu-bug linux". That feels like a separate issue that probably needs to be addressed.

Thanks

tags: added: artful
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in systemd (Ubuntu):
status: New → Confirmed
Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

Happened today at the start of the system

tags: added: cosmic
tags: added: bionic
Dan Streetman (ddstreet)
Changed in systemd (Ubuntu):
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.