System halts during shut down and hibernate

Bug #1662078 reported by Guardian
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Triaged
High
Unassigned

Bug Description

The system completely halts while trying to shut down or hibernate. Restart works fine. Tried Ubuntu/lubuntu on different laptop (Acer ES1 533-P4PA) on every system it is having the same problem.

The version I am using is :
              Description: Ubuntu 16.10
              Release : 16.10

I tried several methods like changing the acpi as provided in the form, but none seems to work.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: linux-image-4.8.0-37-generic 4.8.0-37.39
ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16
Uname: Linux 4.8.0-37-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.8.0-37-generic.
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: PCH [HDA Intel PCH], device 0: ALC233 Analog [ALC233 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ll-l2 1463 F.... pulseaudio
Card0.Amixer.info:
 Card hw:0 'PCH'/'HDA Intel PCH at 0x91310000 irq 205'
   Mixer name : 'Realtek ALC233'
   Components : 'HDA:10ec0235,10251084,00100002 HDA:8086280a,80860101,00100000'
   Controls : 42
   Simple ctrls : 13
Date: Mon Feb 6 10:53:50 2017
HibernationDevice: RESUME=UUID=79497307-14e3-4a30-aecc-1efe0b8165d0
InstallationDate: Installed on 2017-02-03 (2 days ago)
InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
 Bus 001 Device 003: ID 0bda:57b3 Realtek Semiconductor Corp.
 Bus 001 Device 002: ID 8087:0aa7 Intel Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer Aspire ES1-533
ProcEnviron:
 LANGUAGE=en_IN:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_IN
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-37-generic.efi.signed root=UUID=90b5ad8e-c7be-433d-9991-fe323bb881fa ro quiet splash vt.handoff=7
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.8.0-37-generic N/A
 linux-backports-modules-4.8.0-37-generic N/A
 linux-firmware 1.161.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/07/2016
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.04
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Stego_AP
dmi.board.vendor: Acer
dmi.board.version: V1.04
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.04
dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.04:bd09/07/2016:svnAcer:pnAspireES1-533:pvrV1.04:rvnAcer:rnStego_AP:rvrV1.04:cvnAcer:ct10:cvrV1.04:
dmi.product.name: Aspire ES1-533
dmi.product.version: V1.04
dmi.sys.vendor: Acer

Revision history for this message
Guardian (guardian007) wrote :
Revision history for this message
Guardian (guardian007) wrote :
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.10 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.10-rc7

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

No, the system was new and I installed a fresh copy of lubuntu 16.10 (as ubuntu was too slow - used live boot). I tried different versions of ubuntu and fedora but all had the same problem.

As you instructed I installed the new upstream kernals but the bug still persists.

Latest upstream version installed : http://paste.ubuntu.com/23949276/

I suggest this must be given some high importance as it will eventually cause permanent HDD failure.(Force shut down is the only option now).

***There is no legacy boot on this laptop and only UEFI booting is the only option. So installed the OS from live boot and installed GRUB file separately. USB 3.0 option is also not present in BIOS.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.kernel.org.

Once this bug is reported upstream, please add the tag: 'kernel-bug-reported-upstream'.

[0] https://wiki.ubuntu.com/Bugs/Upstream/kernel

Changed in linux (Ubuntu):
importance: Medium → High
status: Confirmed → Triaged
Revision history for this message
thk (thkatsou) wrote :

Run dmesg and if you see a message:

Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug

edit /etc/default/grub

GRUB_CMDLINE_LINUX_DEFAULT="pci=nocrs"

and

sudo update-grub

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.