16.10 hangs on shutdown
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
Medium
|
Unassigned |
Bug Description
This bug is about my Gateway M1629 not shutting down screen stops at reached . I can reproduce it every time. I also have a problem with booting up ( may be related) that has to do with the timing. If I click on ubunto LTS in grub screen it boots to a black screen. But if I make it wait by clicking on boot options and then back to ubuntu it boots fine!
The bug about hanging was reported so many times. I am not sure if is the kernel or the bios? too many answers but never one fix! can someone help please?
Thanks,
David
---
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/pcmC1D0p: david 22172 F...m pulseaudio
/dev/snd/
/dev/snd/
/dev/snd/
CurrentDesktop: XFCE
DistroRelease: Ubuntu 16.10
HibernationDevice: RESUME=
InstallationDate: Installed on 2016-11-03 (5 days ago)
InstallationMedia: Ubuntu-Studio 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
MachineType: Gateway M-1629
Package: linux (not installed)
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=
ProcVersionSign
RelatedPackageV
linux-
linux-
linux-firmware 1.161
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
Tags: yakkety
Uname: Linux 4.8.0-26-lowlatency x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 05/23/2008
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 9D.05
dmi.board.vendor: Gateway
dmi.board.version: 9D.05
dmi.chassis.
dmi.chassis.type: 8
dmi.chassis.vendor: Gateway
dmi.chassis.
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: M-1629
dmi.product.
dmi.sys.vendor: Gateway
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
apport-collect 1640200
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.