← Back to team overview

touch-packages team mailing list archive

[Bug 1433426] Re: systemd crashed with SIGSEGV in _IO_acquire_lock_fct()

 

Closing that report now, as it has been only seen 1 time.

** Changed in: systemd (Ubuntu)
       Status: Triaged => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1433426

Title:
  systemd crashed with SIGSEGV in _IO_acquire_lock_fct()

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Got that crash on cold boot, before loading the graphic process

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-4ubuntu5
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: i386
  Date: Wed Mar 18 05:57:18 2015
  ExecutablePath: /lib/systemd/systemd
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  ProcCmdline: (agetty)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro
  SegvAnalysis:
   Segfault happened at: 0xb742e16c <__GI__IO_fputs+172>:	testl  $0x8000,(%esi)
   PC (0xb742e16c) ok
   source "$0x8000" ok
   destination "(%esi)" (0x00000000) not located in a known VMA region (needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: systemd
  StacktraceTop:
   _IO_acquire_lock_fct (p=<synthetic pointer>) at libioP.h:888
   __GI__IO_fputs (str=0xbf9c8d8e "1118\n", fp=0xb931be00) at iofputs.c:38
   ?? ()
   ?? ()
   ?? ()
  Title: systemd crashed with SIGSEGV in _IO_acquire_lock_fct()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

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


References