System Hangs after being in Power Safe Mode

Bug #1879176 reported by Frank Krauss
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-release-upgrader (Ubuntu)
New
Undecided
Unassigned

Bug Description

Dear Sirs,
I'm a long term user of Ubuntu.
I have been using Bionic Beaver for a little while and I find it
seems to Hang a lot more than my previous version Trusty Tahr.
Normally these Hangs occur when switching between different users.
Yesterdays Hang was different.
This one occurred by the following sequence of events:
1. The System had been idle for a while.
2. The Monitor was blank in Power Save mode.
3. I pressed the Enter key expecting to log onto my User.
4. The entire screen stayed black EXCEPT for the Top of the Screen
   that had the "Activities Day and time etc" on it.
5. I could move the Mouse around the Screen but I got no response
   from the system when Clicking the Mouse or pressing any Keys.
I used the SysRq - Magic Key combination to get the following information
ALT + PrtScrn, ALT + CREISUB
The system re-booted and gave me the usual files in /var/crash
I used the crash program with the Symbols file and in the backtrace section
   under the exception line it says:
           exception RIP mwait_idle+132
   in the disassembly of mwait_idle, the line at +132 is
     mov %gs:0x78974cb4(%rip),%r12d # 0x10350
Any information that I can supply to you I will be glad to in order to
aid you in solving this problem.
I'm computer literate and so I can follow any directions that
you want to give to me.
I have enjoyed using Ubutnu for many years but I do need a Stable
environment for my Development work and for my Users satisfaction.
Yours truly,
Frank Krauss
(208)-547-4452
<email address hidden>

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-release-upgrader-core 1:18.04.37
ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18
Uname: Linux 5.3.0-51-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.14
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Sun May 17 11:14:20 2020
InstallationDate: Installed on 2020-04-20 (26 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: dist-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.update-manager.release-upgrades: 2020-05-17T10:26:59.443734
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.14
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2020-04-20 (26 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
Package: ubuntu-release-upgrader (not installed)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18
Tags: bionic dist-upgrade
Uname: Linux 5.3.0-51-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video
_MarkForUpload: True

Revision history for this message
Frank Krauss (fmfkrauss) wrote :
tags: added: apport-collected
description: updated
Revision history for this message
Frank Krauss (fmfkrauss) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Frank Krauss (fmfkrauss) wrote :

Sirs,
I added the output of "apport-collect 1879176" to this Report.
Frank Krauss

Revision history for this message
Frank Krauss (fmfkrauss) wrote :

Dear Sirs,
Please feel free to close out this Bug.
The Solution was to run with the 4.15.0 Nucleus.
The problem was probably caused by the fact that my Computer System was 10+ years old
and so it couldn't support the new HWE code in the 5.x Series.
If you look at bug 1877890 you will see a fuller description of the problem.
Yours truly,
Frank Krauss

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.