[Bug 1707829] [NEW] systemd-resolved crashed with SIGABRT in __epoll_wait_nocancel()

Tue Aug 1 03:23:50 UTC 2017

*** This bug is a duplicate of bug 1605307 ***
    https://bugs.launchpad.net/bugs/1605307

Public bug reported:

Apport told me systemd-resolved crashed when I logged in to my fully
updated Xubuntu Artful amd64 system. This is the same virtual machine
for which I reported bug 1707792 earlier today; potentially relevant
details about the system installed on this machine may be found in that
bug report.

I suspect this is still bug 1707792 (which is a duplicate of bug
1705870), but this also resembles bug 1605307, which was originally
reported against Yakkety but has since also been tagged Zesty and
Artful. Are these all really the same bug?

After the symbolic retrace and depending on what it shows, I will likely
mark this as a duplicate of something else, if that is not done
automatically.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: systemd 234-2ubuntu1
ProcVersionSignature: Ubuntu 4.11.0-12.17-generic 4.11.12
Uname: Linux 4.11.0-12-generic x86_64
ApportVersion: 2.20.6-0ubuntu4
Architecture: amd64
Date: Mon Jul 31 22:16:39 2017
ExecutablePath: /lib/systemd/systemd-resolved
InstallationDate: Installed on 2017-07-31 (0 days ago)
InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170731)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. 
 Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
 Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: VMware, Inc. VMware Virtual Platform
ProcCmdline: /lib/systemd/systemd-resolved
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-12-generic root=UUID=3ebdfb0d-efad-4049-955f-56e299d1acea ro quiet splash
Signal: 6
SourcePackage: systemd
StacktraceTop:
 __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:84
 sd_event_wait () from /lib/systemd/libsystemd-shared-234.so
 sd_event_run () from /lib/systemd/libsystemd-shared-234.so
 sd_event_loop () from /lib/systemd/libsystemd-shared-234.so
 ?? ()
SystemdDelta:
 [EXTENDED]   /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf
 [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
 [EXTENDED]   /lib/systemd/system/user at .service → /lib/systemd/system/user at .service.d/timeout.conf

 3 overridden configuration files found.
Title: systemd-resolved crashed with SIGABRT in __epoll_wait_nocancel()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 07/02/2015
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.

** Affects: systemd (Ubuntu)
     Importance: Undecided
         Status: New

** Tags: amd64 apport-crash artful package-from-proposed

** Information type changed from Private to Public

-- 
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/1707829

Title:
  systemd-resolved crashed with SIGABRT in __epoll_wait_nocancel()

Status in systemd package in Ubuntu:
  New

Bug description:
  Apport told me systemd-resolved crashed when I logged in to my fully
  updated Xubuntu Artful amd64 system. This is the same virtual machine
  for which I reported bug 1707792 earlier today; potentially relevant
  details about the system installed on this machine may be found in
  that bug report.

  I suspect this is still bug 1707792 (which is a duplicate of bug
  1705870), but this also resembles bug 1605307, which was originally
  reported against Yakkety but has since also been tagged Zesty and
  Artful. Are these all really the same bug?

  After the symbolic retrace and depending on what it shows, I will
  likely mark this as a duplicate of something else, if that is not done
  automatically.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-12.17-generic 4.11.12
  Uname: Linux 4.11.0-12-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  Date: Mon Jul 31 22:16:39 2017
  ExecutablePath: /lib/systemd/systemd-resolved
  InstallationDate: Installed on 2017-07-31 (0 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170731)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. 
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcCmdline: /lib/systemd/systemd-resolved
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-12-generic root=UUID=3ebdfb0d-efad-4049-955f-56e299d1acea ro quiet splash
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:84
   sd_event_wait () from /lib/systemd/libsystemd-shared-234.so
   sd_event_run () from /lib/systemd/libsystemd-shared-234.so
   sd_event_loop () from /lib/systemd/libsystemd-shared-234.so
   ?? ()
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /lib/systemd/system/user at .service → /lib/systemd/system/user at .service.d/timeout.conf

   3 overridden configuration files found.
  Title: systemd-resolved crashed with SIGABRT in __epoll_wait_nocancel()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  dmi.bios.date: 07/02/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1707829/+subscriptions