Computer crashes on shutdown

Bug #1623092 reported by Antonios Hadjigeorgalis
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

This bug has occurred twice in the past week. My motherboard is set up to turn on at 6am in the morning. The morning after this bug occurs it does not automatically start up. The bug occurs on shutdown and leaves the computer unresponsive with the text of the kernel log bug report on the screen. I've had to do a hard shutdown at this point, holding the power button until the machine powers down fully.

I am happy to do whatever troubleshooting you suggest. I used `ubuntu-bug linux` to file this report.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-36-generic 4.4.0-36.55
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: antonios 4898 F.... pulseaudio
 /dev/snd/controlC0: antonios 4898 F.... pulseaudio
CurrentDesktop: Unity
Date: Tue Sep 13 11:09:38 2016
HibernationDevice: RESUME=UUID=d39f2337-8ee7-4d9d-9202-41a04c955dfd
InstallationDate: Installed on 2012-09-14 (1459 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1)
IwConfig:
 lo no wireless extensions.

 docker0 no wireless extensions.

 eth0 no wireless extensions.
MachineType: System manufacturer System Product Name
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic root=UUID=50ef8abe-641b-49fd-8a81-60aca8cd440f ro
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-36-generic N/A
 linux-backports-modules-4.4.0-36-generic N/A
 linux-firmware 1.157.3
RfKill:

SourcePackage: linux
UpgradeStatus: Upgraded to xenial on 2016-08-08 (35 days ago)
dmi.bios.date: 09/06/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2105
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8Z77-M PRO
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.:bvr2105:bd09/06/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-MPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

Revision history for this message
Antonios Hadjigeorgalis (antonioshadji) wrote :
Revision history for this message
Antonios Hadjigeorgalis (antonioshadji) wrote :

This is the section of the kern.log that was showing on the screen at the time of the crash.

Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
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.8 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.8-rc6

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Antonios Hadjigeorgalis (antonioshadji) wrote :

The current kernel was installed on 8/30/16 so the issue has only been happening since the install. I have automatic updates enabled so there have been various other updates added. The crash occurred once before this report and then has not reoccurred since the report.

I have installed the 4.8rc6 kernel you suggested and will test it out.

I included my apt history showing the 36.55 kernel install and all subsequent updates.

Revision history for this message
Antonios Hadjigeorgalis (antonioshadji) wrote :

Immediately after installing the 4.8rc6 kernel, my system crashed again on shutdown when I rebooted to launch the new kernel. The crash occurred running on the old kernel before the reboot.

Now the system will not boot to the graphical user interface, regardless of which kernel I choose in grub screen. I get a screen popup saying:
The system is running in low-graphics mode

Your screen, graphics card, and input device settings
could not be detected correctly. You will need to configure these yourself.

When I hit OK, I get a message box with the following options:
Try running with default graphical mode
Reconfigure graphics
Troubleshoot the error
Exit to console login

the 1st and 4th option take me to a console login
the 2nd and 3rd options just return to the same message box

I tested with all available kernels, 4.8rc6, 4.4.0-36, 3.13.0-77 and all produce this same result. I also tried recovery mode and checked the disks with fsck.
 the machine is running in low graphics mode with a few options to see the xorg.log or try to reconfigure the graphics.

Revision history for this message
Antonios Hadjigeorgalis (antonioshadji) wrote :

This file is the result of running ubuntu-bug linux --save=report.txt on the system in the current state.

Revision history for this message
Antonios Hadjigeorgalis (antonioshadji) wrote :

I was able to boot the system from a live usb. I believe that means this is not a hardware failure.

Revision history for this message
Antonios Hadjigeorgalis (antonioshadji) wrote :

results of systemctl status lightdm.service

● lightdm.service - Light Display Manager
   Loaded: loaded (/lib/systemd/system/lightdm.service; enabled; vendor preset: enabled)
  Drop-In: /lib/systemd/system/display-manager.service.d
           └─xdiagnose.conf
   Active: inactive (dead) (Result: exit-code) since Sat 2016-09-17 15:55:08 EDT; 13min ago
     Docs: man:lightdm(1)
  Process: 2486 ExecStart=/usr/sbin/lightdm (code=exited, status=1/FAILURE)
  Process: 2481 ExecStartPre=/bin/sh -c [ "$(basename $(cat /etc/X11/default-display-manager 2>/dev/null))" = "lightdm" ] (code=exited, sta
 Main PID: 2486 (code=exited, status=1/FAILURE)

Sep 17 15:55:07 antonios-linux systemd[1]: lightdm.service: Failed with result 'exit-code'.
Sep 17 15:55:08 antonios-linux systemd[1]: lightdm.service: Service hold-off time over, scheduling restart.
Sep 17 15:55:08 antonios-linux systemd[1]: Stopped Light Display Manager.
Sep 17 15:55:08 antonios-linux systemd[1]: lightdm.service: Start request repeated too quickly.
Sep 17 15:55:08 antonios-linux systemd[1]: Failed to start Light Display Manager.

Revision history for this message
Antonios Hadjigeorgalis (antonioshadji) wrote :

On the last crash after installing the 4.8rc6 kernel, but before booting into it, something happened to one or more of lightdm, unity-greeter, or unity. I reinstalled those 3 packages before getting my desktop to come back. I also purged all versions of virtualbox.

I'm now running on the 4.8rc6 kernel and have full functionality. The system boots much slower in this kernel. I will report further if there is another crash on shutdown or if there are no crashes in the next week.

If there are further troubleshooting measures to assist your investigation please let me know.

Revision history for this message
Antonios Hadjigeorgalis (antonioshadji) wrote :

I ran the 4.8rc6 kernel until the 4.4.0-38-generic kernel was released. I have been running on 4.4.0-38 with no crashes on shutdown.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
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.