Ubuntu suspends after login

Bug #1745651 reported by Floyd Taylor
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Ubuntu 16.04.3 LTS enters suspend mode immediately after entering password. This began after previous update which included new kernel and continues after updating today 2018-01-26 which also included new kernel. System is Dell Precision Workstation M4600 laptop with Intel i7-2820QM CPU, 8GB RAM, Nvidia Quadro 1000M Graphics. System wakes up immediately after pressing power button and otherwise appears to be operating normally

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubuntu-release-upgrader-core 1:16.04.23
ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: Unity
Date: Fri Jan 26 12:45:39 2018
InstallationDate: Installed on 2017-08-08 (171 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)
---
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC2: floyd 2392 F.... pulseaudio
 /dev/snd/controlC1: floyd 2392 F.... pulseaudio
 /dev/snd/controlC0: floyd 2392 F.... pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=f66bfa77-de5a-42e9-95d0-991e7d737151
InstallationDate: Installed on 2017-08-08 (178 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: Dell Inc. Precision M4600
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
Package: linux (not installed)
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed root=UUID=6cf37c1b-ee15-41c1-b7a2-e5b7cdfb00e6 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-32-generic N/A
 linux-backports-modules-4.13.0-32-generic N/A
 linux-firmware 1.157.15
Tags: xenial
Uname: Linux 4.13.0-32-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 12/26/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A16
dmi.board.asset.tag: FBTaylorJr
dmi.board.name: 08V9YG
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.asset.tag: FBTaylorJr
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.

Revision history for this message
Floyd Taylor (fbtjr) wrote :
affects: ubuntu-release-upgrader (Ubuntu) → linux (Ubuntu)
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1745651

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Floyd Taylor (fbtjr) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Floyd Taylor (fbtjr) wrote : CRDA.txt

apport information

Revision history for this message
Floyd Taylor (fbtjr) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Floyd Taylor (fbtjr) wrote : IwConfig.txt

apport information

Revision history for this message
Floyd Taylor (fbtjr) wrote : JournalErrors.txt

apport information

Revision history for this message
Floyd Taylor (fbtjr) wrote : Lspci.txt

apport information

Revision history for this message
Floyd Taylor (fbtjr) wrote : Lsusb.txt

apport information

Revision history for this message
Floyd Taylor (fbtjr) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Floyd Taylor (fbtjr) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Floyd Taylor (fbtjr) wrote : ProcEnviron.txt

apport information

Revision history for this message
Floyd Taylor (fbtjr) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Floyd Taylor (fbtjr) wrote : ProcModules.txt

apport information

Revision history for this message
Floyd Taylor (fbtjr) wrote : PulseList.txt

apport information

Revision history for this message
Floyd Taylor (fbtjr) wrote : RfKill.txt

apport information

Revision history for this message
Floyd Taylor (fbtjr) wrote : UdevDb.txt

apport information

Revision history for this message
Floyd Taylor (fbtjr) wrote : WifiSyslog.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Floyd Taylor (fbtjr) wrote :

After following the emailed instruction to run apport-collect 1745651 the thought occurred that perhaps you needed that to be run immediately after power-up & login when the problem occurs. The system had been up for several days when the log files were collected.

Please let me know if I need to collect & submit the log files immediately after a cold startup.

Thank you for your interest in solving this bug.

Floyd Taylor

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.15 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Floyd Taylor (fbtjr) wrote :

Sorry for delay in responding. I was traveling away from system with problem.

Bug did not occur in 4.13.0-31 generic

Bug appeared after update to 4.13.0-32 generic

Bug appears to be fixed in 4.13.0-36 generic which installed along with other updates when I returned from travel.

I am relatively new to Linux & Ubuntu. The system exhibiting the problem is one I rely on for everyday work. I chose to install the "LTS" version under the assumption that it was the more stable, better tested version. I am not at all familiar with the methods of installing and trying different releases and do not want to risk the system I rely on. I did discover that the "Advanced" startup options for Ubuntu allow me to run every previous version since the initial install. That allowed me to provide the information above. I hope the information provided is adequate. I will post again if the bug reappears after any future update to the LTS version.

Thanks for your assistance.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Floyd Taylor (fbtjr) wrote :

Tags: added: kernel-fixed-upstream

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.