Ubuntu 19.10 doesn't shutdown

Bug #1860800 reported by Leonard
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Hello guys,

I can't shutdown Ubuntu 19.10. When I try, the shutdown screen appears. The first two dots below the ubuntu logo, turn orange and then it freezes. Reboot works fine.

The debug-shell is no use, because at the freeze point I can't type in commands. When I press ESC to see what's going on during shutdown, the last message to appear ist "[Some weird number] reboot: power down. Last time I pressed ESC during shutdown the "weird number" was 85.270119. I also tried to shutdown with the terminal commands "sudo shutdown now", "sudo shutdown -P now", "sudo shutdown -h now", "poweroff" and "sudo poweroff -f". All of them had the effect as describe above except the command "sudo poweroff -f". After I typed in the command, I authenticated and following messages appeared: "Powering off...". At this point it freezed. I could still see the desktop and every visible window, but I couldn't perform any actions; not even keyboard shortcuts worked. It also did not help to change 'GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"' in /etc/default/grub to 'GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi=force"' and run "update-grub".

Once the following command combo did work: "sudo swapoff -a && systemctl poweroff", but the I reinstalled Ubuntu and now it doesn't work any more.

In the application "Additional Drivers" I selected the proprietary
and tested driver of NVIDIA, but I can't to this for my WLAN-Card
(correct word?), because the "Additional Drivers" says it's not working,
but my WLAN works fine. I've got only Bluetooth problems. The displayed
name of the WLAN-Card is: "Intel Corporation: Wireless 7260 (Dual Band
Wireless-AC 7260)". I also tried to manually install a driver it didn't
help.

 When I wake up the laptop, a black screen appears with some error
messages, but only for a very short time so I can't make a photo of it.
I tried once and the text was unreadable.

I have the latest BIOS and my Computer model is MSI PX60 2QD.

It doesn't work with Arch Linux either.

Thanks for your help :)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: leonard 1724 F.... pulseaudio
 /dev/snd/controlC1: leonard 1724 F.... pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 19.10
InstallationDate: Installed on 2020-01-18 (7 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: Micro-Star International Co., Ltd. PX60 2QD
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=04df7493-393f-447e-bfb3-3dc43c2ee645 ro quiet splash acpi=force vt.handoff=7
ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
RelatedPackageVersions:
 linux-restricted-modules-5.3.0-26-generic N/A
 linux-backports-modules-5.3.0-26-generic N/A
 linux-firmware 1.183.3
Tags: eoan
Uname: Linux 5.3.0-26-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 11/03/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E16H6IMS.110
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: MS-16H6
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:0.B
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 10
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16H6IMS.110:bd11/03/2015:svnMicro-StarInternationalCo.,Ltd.:pnPX602QD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16H6:rvrREV0.B:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: PX60 2QD
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1860800/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
affects: ubuntu → linux (Ubuntu)
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1860800

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
tags: added: eoan
Revision history for this message
Leonard (leonard-linux) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Leonard (leonard-linux) wrote : CRDA.txt

apport information

Revision history for this message
Leonard (leonard-linux) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Leonard (leonard-linux) wrote : IwConfig.txt

apport information

Revision history for this message
Leonard (leonard-linux) wrote : Lspci.txt

apport information

Revision history for this message
Leonard (leonard-linux) wrote : Lsusb.txt

apport information

Revision history for this message
Leonard (leonard-linux) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Leonard (leonard-linux) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Leonard (leonard-linux) wrote : ProcEnviron.txt

apport information

Revision history for this message
Leonard (leonard-linux) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Leonard (leonard-linux) wrote : ProcModules.txt

apport information

Revision history for this message
Leonard (leonard-linux) wrote : PulseList.txt

apport information

Revision history for this message
Leonard (leonard-linux) wrote : RfKill.txt

apport information

Revision history for this message
Leonard (leonard-linux) wrote : UdevDb.txt

apport information

Revision history for this message
Leonard (leonard-linux) wrote : WifiSyslog.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
description: updated
Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Please remove "acpi=force", and try the following kernel parameter instead: "reboot=b", "reboot=a" "reboot=k", "reboot=t", "reboot=e" or "reboot=p".

Revision history for this message
Leonard (leonard-linux) wrote : Re: [Bug 1860800] Re: Ubuntu 19.10 doesn't shutdown

Thank you very much for your help Kai-Heng Feng and please excuse me for
answering that late. I tried out every kernel parameter you wrote but
unfortunately it didn't work. I even shutdown twice when I changed the
kernel parameter. I also ran "sudo update-grub" every time I edited
/etc/default/grub. Luckily the kernel parameter "reboot=a" triggered a
message I haven't had before: "A stop job is running for Make remote
CUPS printers available locally". Could there be the problem? Is it
possible that a BIOS setting is preventing my laptop from shutting down
correctly? And if yes, what setting could it be?

When I first recognized that the my laptop isn't shutting down properly,
I installed Windows to see if it worked with Windows and it did. But
Windows didn't load the touchpad drivers correctly, so I couldn't use it.

I've also made some changes this week: I installed Kali Linux on a
second hard drive. After changing the kernel parameter some messages
appeared during boot, but they went away to fast, so I couldn't read
them good. All I could read is that it is connected with the hard drive
on which Ubuntu is installed.

I hope that helps you helping me :)

On 04.02.20 15:36, Kai-Heng Feng wrote:
> Please remove "acpi=force", and try the following kernel parameter
> instead: "reboot=b", "reboot=a" "reboot=k", "reboot=t", "reboot=e" or
> "reboot=p".
>

Revision history for this message
Leonard (leonard-linux) wrote :

Now my laptop sometimes doesn't reboot. When it should boot, it tries to but soon breaks down. When I unplag the charger and a wait a few seconds it will boot. Can anyone explain this? I will test if the same problem appears with other distributions and write it here.

Revision history for this message
Leonard (leonard-linux) wrote :

First: I solved the reboot problem. I removed the kernel parameter "reboot=p" from /etc/default/grub.

Second: I found the following message in /var/log/syslog.1: "Feb 22 13:09:38 MSI kernel: [ 1.183278] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver". Could that be the problem? If that is the problem, how to get another ACPI driver?

I attached the whole syslog.1 file, probably there is more useful information for you.

Leonard

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Can you please see if reboot works when there's no previous suspend attempt?

I can see this after system resume from suspend:
[ 3403.666188] PM: dpm_run_callback(): usb_dev_resume+0x0/0x20 returns -5
[ 3403.666191] PM: Device 2-1.8 failed to resume async: error -5

Revision history for this message
Leonard (leonard-linux) wrote :

Reboot always works :) Do you have the same problem?

On 30/03/2020 10:21, Kai-Heng Feng wrote:
> Can you please see if reboot works when there's no previous suspend
> attempt?
>
> I can see this after system resume from suspend:
> [ 3403.666188] PM: dpm_run_callback(): usb_dev_resume+0x0/0x20 returns -5
> [ 3403.666191] PM: Device 2-1.8 failed to resume async: error -5
>

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Sorry, should rephrase to "Can you please see if shutdown works when there's no previous suspend attempt?"

Revision history for this message
Leonard (leonard-linux) wrote :
Download full text (4.4 KiB)

Yes, I can. It doesn't.

Thank you for your help,
leonard-linux

On Apr 8 2020, at 6:07 pm, Kai-Heng Feng <email address hidden> wrote:
> Sorry, should rephrase to "Can you please see if shutdown works when there's no previous suspend attempt?" -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1860800 Title: Ubuntu 19.10 doesn't shutdown Status in linux package in Ubuntu: Confirmed Bug description: Hello guys, I can't shutdown Ubuntu 19.10. When I try, the shutdown screen appears. The first two dots below the ubuntu logo, turn orange and then it freezes. Reboot works fine. The debug-shell is no use, because at the freeze point I can't type in commands. When I press ESC to see what's going on during shutdown, the last message to appear ist "[Some weird number] reboot: power down. Last time I pressed ESC during shutdown the "weird number" was 85.270119. I also tried to shutdown with the terminal commands "sudo shutdown now", "sudo shutdown -P now", "sudo shutdown -h now", "poweroff" and "sudo poweroff -f". All of them had the effect as describe above exc
ept the command "sudo poweroff -f". After I typed in the command, I authenticated and following messages appeared: "Powering off...". At this point it freezed. I could still see the desktop and every visible window, but I couldn't perform any actions; not even keyboard shortcuts worked. It also did not help to change 'GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"' in /etc/default/grub to 'GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi=force"' and run "update-grub". Once the following command combo did work: "sudo swapoff -a && systemctl poweroff", but the I reinstalled Ubuntu and now it doesn't work any more. In the application "Additional Drivers" I selected the proprietary and tested driver of NVIDIA, but I can't to this for my WLAN-Card (correct word?), because the "Additional Drivers" says it's not working, but my WLAN works fine. I've got only Bluetooth problems. The displayed name of the WLAN-Card is: "Intel Corporation: Wireless 7260 (Dual Band Wireless-AC 7260)". I also tried to m
anually install a driver it didn't help. When I wake up the laptop, a black screen appears with some error messages, but only for a very short time so I can't make a photo of it. I tried once and the text was unreadable. I have the latest BIOS and my Computer model is MSI PX60 2QD. It doesn't work with Arch Linux either. Thanks for your help :) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: leonard 1724 F.... pulseaudio /dev/snd/controlC1: leonard 1724 F.... pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-01-18 (7 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Micro-Star International Co., Ltd. PX60 2QD NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=04df7493-393f-447e-bfb3-3
dc43c2ee645 ro quiet splash acpi=force vt.handoff=7 ProcVers...

Read more...

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.6/

If mainline kernel doesn't work, usually there are some driver prevent the system from shutting down.

Unload driver one by one to see which one is the culprit.

Revision history for this message
Leonard (leonard-linux) wrote :
Download full text (4.7 KiB)

Thank you again for your answer. I switched back to Linux Mint 19.3 Cinnamon having the same issue. Is there also a mainline kernel available for this distribution?

leonard-linux
On Apr 9 2020, at 8:49 am, Kai-Heng Feng <email address hidden> wrote:
> Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.6/ If mainline kernel doesn't work, usually there are some driver prevent the system from shutting down. Unload driver one by one to see which one is the culprit. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1860800 Title: Ubuntu 19.10 doesn't shutdown Status in linux package in Ubuntu: Confirmed Bug description: Hello guys, I can't shutdown Ubuntu 19.10. When I try, the shutdown screen appears. The first two dots below the ubuntu logo, turn orange and then it freezes. Reboot works fine. The debug-shell is no use, because at the freeze point I can't type in commands. When I press ESC to see what's going on during shutdown, the last message to appear ist "[Some weird number] reboot: power down. Last time I pressed ESC during shutdown the "weird number" was 85.270119. I also tried to shutdown with the terminal commands "sudo shut
down now", "sudo shutdown -P now", "sudo shutdown -h now", "poweroff" and "sudo poweroff -f". All of them had the effect as describe above except the command "sudo poweroff -f". After I typed in the command, I authenticated and following messages appeared: "Powering off...". At this point it freezed. I could still see the desktop and every visible window, but I couldn't perform any actions; not even keyboard shortcuts worked. It also did not help to change 'GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"' in /etc/default/grub to 'GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi=force"' and run "update-grub". Once the following command combo did work: "sudo swapoff -a && systemctl poweroff", but the I reinstalled Ubuntu and now it doesn't work any more. In the application "Additional Drivers" I selected the proprietary and tested driver of NVIDIA, but I can't to this for my WLAN-Card (correct word?), because the "Additional Drivers" says it's not working, but my WLAN works fine. I've got only
Bluetooth problems. The displayed name of the WLAN-Card is: "Intel Corporation: Wireless 7260 (Dual Band Wireless-AC 7260)". I also tried to manually install a driver it didn't help. When I wake up the laptop, a black screen appears with some error messages, but only for a very short time so I can't make a photo of it. I tried once and the text was unreadable. I have the latest BIOS and my Computer model is MSI PX60 2QD. It doesn't work with Arch Linux either. Thanks for your help :) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: leonard 1724 F.... pulseaudio /dev/snd/controlC1: leonard 1724 F.... pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-01-18 (7 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Micro-Star International Co., Ltd. PX60...

Read more...

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.