← Back to team overview

desktop-packages team mailing list archive

[Bug 1509326] Re: Various instabilities after resuming from standby


Okay... I'm seeing some glitches with Nouveau, but not all.
1) Spontaneous wake-ups, not going to sleep when told to, and similar are gone.
2) There is still improper detection of monitor configuration changes between suspend and resume. Dlosing and reopening the lid fixed that in one instance, don't know whether that is a general rule.

Now that monitor detection is clearly identified as an unrelated problem, I agree it should go to a separate problem report.
How do I proceed about the spontaneous wake-ups?

You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.

  Various instabilities after resuming from standby

Status in xorg package in Ubuntu:

Bug description:
  None of these problems are readily reproducible, I'm having a roughly
  30:70 chance of a successful standby. Things that I have seen happen:

  1) Click on Whisker menu -> Logoff ("Abmelden") button ->
  Logoff/Restart/Reboot/Standby dialog (no Hibernate option, I think
  it's blacklisted for my machine) -> Click on "Shutdown" -> no
  shutdown, I get the login screen.

  2) Trying to go to standby from the Logoff button in the login screen
  after seeing (1) -> monitor switches off, then on, login screen again.

  3) After (2), close the lid, open it, standby procedure from login
  screen -> works. Sometimes.

  4) After (2), remove machine from docking station, standby procedure
  from login screen -> works. Sometimes.

  5) Machine is in standby, I press the power button, I get some text
  mode messages, monitor flashes and shows graphic content (mostly a
  mouse cursor on some background, too fast to properly see), then the
  screen goes dark. Ctrl-Alt-F1 works, Ctrl-Alt-F7 simply makes the
  screen dark again (both the builtin laptop screen and one of the
  external, connected-through-docking-station screens).

  6) The effects from (5) can also happen right after cold booting the

  7) I *think* on a few occasions, I tried to shutdown the machine and
  nothing happened at all.

  8) On some rarer occasions, nothing would happen after the shutdown
  command, and trying to issue another shutdown resulted in a message
  amounting to "can't do another action while the previous action is in
  progress"; I remember pstree reported some hung process that was
  connected to shutdown, and I couldn't kill it (not even kill -9). I
  cannot reproduce this, and I didn't take notes so I can't be more

  I have no idea which of these effects are related to a common cause and which are independent.
  I have been unable to find out anything given that no individual phenomenon is reproducible with any reliability.
  I hope the attached debug info will help, but I fully expect this to require much more diagnosis.

  - Docking station PR02X
  - Two 2560x1440 Dell U2515H monitors, one on each video output of the docking station
  - nVidia Quadro 2000M, using the proprietary driver (Nouveau cannot drive two 2560x1440 screens)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-31-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.registry: Binary: ""
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  346.96  Sun Aug 23 22:29:21 PDT 2015
   GCC version:  gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13)
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Oct 23 13:40:40 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
   bbswitch, 0.7, 3.19.0-28-generic, x86_64: installed
   bbswitch, 0.7, 3.19.0-30-generic, x86_64: installed
   bbswitch, 0.7, 3.19.0-31-generic, x86_64: installed
   nvidia-346, 346.96, 3.19.0-31-generic, x86_64: installed
   NVIDIA Corporation GF106GLM [Quadro 2000M] [10de:0dda] (rev a1) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:04a3]
  InstallationDate: Installed on 2015-08-24 (59 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
   upstart: indicator-sound-main-Prozess (11841) wurde von TERM-Signal beendet
   upstart: indicator-application-main-Prozess (11843) wurde von TERM-Signal beendet
  MachineType: Dell Inc. Precision M4600
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-31-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/26/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 08V9YG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: dmi:bvnDellInc.:bvrA16:bd12/26/2013:svnDellInc.:pnPrecisionM4600:pvr01:rvnDellInc.:rn08V9YG:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision M4600
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1~vivid2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1
  xserver.bootTime: Thu Oct 22 10:57:03 2015
  xserver.configfile: default
  xserver.errors: open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log

  xserver.version: 2:1.17.1-0ubuntu3.1

To manage notifications about this bug go to: