16.10 hangs on shutdown

Bug #1640200 reported by David
22
This bug affects 4 people
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/controlC1: david 22172 F.... pulseaudio
 /dev/snd/controlC0: david 22172 F.... pulseaudio
 /dev/snd/controlC2: david 22172 F.... pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 16.10
HibernationDevice: RESUME=UUID=7ede9358-a634-4d7a-ba7f-6f3ef9e433bb
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=/boot/vmlinuz-4.8.0-26-lowlatency root=UUID=60158545-3519-4bb6-8178-79f862ba7f87 ro recovery nomodeset
ProcVersionSignature: Ubuntu 4.8.0-26.28-lowlatency 4.8.0
RelatedPackageVersions:
 linux-restricted-modules-4.8.0-26-lowlatency N/A
 linux-backports-modules-4.8.0-26-lowlatency N/A
 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.asset.tag: No Asset Tag
dmi.chassis.type: 8
dmi.chassis.vendor: Gateway
dmi.chassis.version: Rev.1
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr9D.05:bd05/23/2008:svnGateway:pnM-1629:pvr3409925R:rvnGateway:rn:rvr9D.05:cvnGateway:ct8:cvrRev.1:
dmi.product.name: M-1629
dmi.product.version: 3409925R
dmi.sys.vendor: Gateway

Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

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.

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

apport information

tags: added: apport-collected yakkety
description: updated
Revision history for this message
David (dkahn10) wrote : CRDA.txt

apport information

Revision history for this message
David (dkahn10) wrote : CurrentDmesg.txt

apport information

Revision history for this message
David (dkahn10) wrote : IwConfig.txt

apport information

Revision history for this message
David (dkahn10) wrote : JournalErrors.txt

apport information

Revision history for this message
David (dkahn10) wrote : Lspci.txt

apport information

Revision history for this message
David (dkahn10) wrote : Lsusb.txt

apport information

Revision history for this message
David (dkahn10) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
David (dkahn10) wrote : ProcEnviron.txt

apport information

Revision history for this message
David (dkahn10) wrote : ProcInterrupts.txt

apport information

Revision history for this message
David (dkahn10) wrote : ProcModules.txt

apport information

Revision history for this message
David (dkahn10) wrote : PulseList.txt

apport information

Revision history for this message
David (dkahn10) wrote : UdevDb.txt

apport information

Revision history for this message
David (dkahn10) wrote : WifiSyslog.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
David (dkahn10) wrote :

please see attached screen shot. not sure if related. please advise.
Thanks,

David

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.9 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.9-rc4

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

This issue has been around my stock Ubuntu installation at least since 15.04 and continues to persist after the upgrade to 16.10. I have tried all the workarounds of #1464917 without success.

I have my doubts that the kernel upgrade as suggested by Joseph will remedy the situation but will give it a try and report back.

Given the severity of this and the old issue especially in production environments, it would be great if we can bump up the importance.

Revision history for this message
David (dkahn10) wrote : Re: [Bug 1640200] Re: 16.10 hangs on shutdown
Download full text (3.4 KiB)

Thank you,

On Mon, Nov 21, 2016 at 6:58 AM, monochromec <email address hidden> wrote:

> This issue has been around my stock Ubuntu installation at least since
> 15.04 and continues to persist after the upgrade to 16.10. I have tried
> all the workarounds of #1464917 without success.
>
> I have my doubts that the kernel upgrade as suggested by Joseph will
> remedy the situation but will give it a try and report back.
>
> Given the severity of this and the old issue especially in production
> environments, it would be great if we can bump up the importance.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1640200
>
> Title:
> 16.10 hangs on shutdown
>
> Status in linux package in Ubuntu:
> Incomplete
>
> 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/controlC1: david 22172 F.... pulseaudio
> /dev/snd/controlC0: david 22172 F.... pulseaudio
> /dev/snd/controlC2: david 22172 F.... pulseaudio
> CurrentDesktop: XFCE
> DistroRelease: Ubuntu 16.10
> HibernationDevice: RESUME=UUID=7ede9358-a634-4d7a-ba7f-6f3ef9e433bb
> 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=/boot/vmlinuz-4.8.0-26-lowlatency
> root=UUID=60158545-3519-4bb6-8178-79f862ba7f87 ro recovery nomodeset
> ProcVersionSignature: Ubuntu 4.8.0-26.28-lowlatency 4.8.0
> RelatedPackageVersions:
> linux-restricted-modules-4.8.0-26-lowlatency N/A
> linux-backports-modules-4.8.0-26-lowlatency N/A
> 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.asset.tag: No Asset Tag
> dmi.chassis.type: 8
> dmi.chassis.vendor: Gateway
> dmi.chassis.version: Rev.1
> dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr9D.05:bd05/23/2008:
> svnGateway:pnM-1629:pvr3409925R:rvnGateway:...

Read more...

Revision history for this message
monochromec (monochromec) wrote :

As already suspected, a kernel upgrade as suggested by Joseph didn't change anything wrt to the issue. It would be great if we can give more specific advice rather than suggesting a vanilla kernel upgrade as a "one cure for all".

@Joseph: When can the community expect an increase in severity as requested above? Given the number of affected people for this and the previous bug (#1464917) and the timeline so far without much progress it would be great if we can prioritize this upstream.

Revision history for this message
David (dkahn10) wrote :
Download full text (3.6 KiB)

Greetings,

Found that I am running the latest kernel. So I have not found a solution
as of yet😣 I am sure it will be resolved with a little attention.

Thanks,

On Tue, Nov 22, 2016, 2:21 AM monochromec <email address hidden> wrote:

> As already suspected, a kernel upgrade as suggested by Joseph didn't
> change anything wrt to the issue. It would be great if we can give more
> specific advice rather than suggesting a vanilla kernel upgrade as a
> "one cure for all".
>
> @Joseph: When can the community expect an increase in severity as
> requested above? Given the number of affected people for this and the
> previous bug (#1464917) and the timeline so far without much progress it
> would be great if we can prioritize this upstream.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1640200
>
> Title:
> 16.10 hangs on shutdown
>
> Status in linux package in Ubuntu:
> Incomplete
>
> 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/controlC1: david 22172 F.... pulseaudio
> /dev/snd/controlC0: david 22172 F.... pulseaudio
> /dev/snd/controlC2: david 22172 F.... pulseaudio
> CurrentDesktop: XFCE
> DistroRelease: Ubuntu 16.10
> HibernationDevice: RESUME=UUID=7ede9358-a634-4d7a-ba7f-6f3ef9e433bb
> 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=/boot/vmlinuz-4.8.0-26-lowlatency
> root=UUID=60158545-3519-4bb6-8178-79f862ba7f87 ro recovery nomodeset
> ProcVersionSignature: Ubuntu 4.8.0-26.28-lowlatency 4.8.0
> RelatedPackageVersions:
> linux-restricted-modules-4.8.0-26-lowlatency N/A
> linux-backports-modules-4.8.0-26-lowlatency N/A
> 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.asset.tag: No Asset Tag
> dmi.chassis.type: 8
...

Read more...

Revision history for this message
penalvch (penalvch) wrote :

David, in order to allow additional upstream developers to examine the issue, at your earliest convenience, could you please test the latest upstream kernel available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind the following:
1) The one to test is at the very top line at the top of the page (not the daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was released upstream.
4) Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically requested to do so.

It is most helpful that after testing of the latest upstream kernel is complete, you mark this report Status Confirmed.

Lastly, to keep this issue relevant to upstream, please continue to periodically check for, and test the latest mainline kernel as it becomes available.

Thank you for your help.

tags: added: bios-outdated-9d.06 vivid
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
Revision history for this message
bigsicret (bigsicret) wrote :

Same problem with debian 9 "Stretch". I had no problem with debian 8.

Revision history for this message
bigsicret (bigsicret) wrote :
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.