touch-packages team mailing list archive

[Iain Lane <iain@xxxxxxxxxxxxxxxxxxx>]

On Sun, Mar 08, 2015 at 06:50:58PM -0000, Martin Pitt wrote:
> Ah, thanks. I misunderstood you then.
> 
> Can you say with certain confidence that the kernel/graphics driver
> crash (that's what it seems to be) only happens with systemd, but not
> with  upstart? Perhaps there's some difference in how we shut down
> X.org/lightdm under either. Can you reliably switch users or just
> start/stop your session under upstart and systemd? (The latter is the
> part that causes graphics driver/kernel crashes on my machine
> occasionally, but it doesn't seem init specific)

OK, just checked with upstart - poweroff is fine there.

Seems session start is fine too: I just tried 10 times under both and
that works too.

-- 
Iain Lane                                  [ iain@xxxxxxxxxxxxxxxxxxx ]
Debian Developer                                   [ laney@xxxxxxxxxx ]
Ubuntu Developer                                   [ laney@xxxxxxxxxx ]

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

Title:
  System doesn't power off when shutting down

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  1. Open the session indicator (cog in top-right)
  2. Shut Down...
  3. Shut Down
  4. The monitors go blank
  5. The system doesn't power off (waited > 5 minutes)

  Things which do work

   - poweroff -f
   - Changing to a debug shell and shutting down using login1.Manager PowerOff

  I can't use the system-shutdown/ functionality since shutdown doesn't
  get that far. I can't SSH in since network is down. I can't switch VT
  when it's in this state so I'm not able to interact with the system. I
  can't see anything on the monitors since they are turned off.

  Any tips on how to get useful debugging information? I'll attach
  journalctl from the previous boot but the last message is the journal
  shutting down so it's not that useful I don't think. Also syslog.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-4ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar  3 12:57:33 2015
  InstallationDate: Installed on 2012-10-07 (876 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-7-generic root=UUID=980689ca-e7d9-4a99-8230-33b8b6e917cd ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw systemd.debug-shell nomdmonddf nomdmonisw
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2013-05-07 (665 days ago)
  dmi.bios.date: 08/17/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1201
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z77-V LX
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1201:bd08/17/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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