PC fails to shutdown.

Bug #1861645 reported by Prakash Shenoy
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned
systemd (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I have a pc with Motherboard Gigabyte H370M D3H, Processor Intel Core I3 8100 3.6Ghz 6MbL3, RAM Corsair 16Mb 2400 Hz. I can reboot pc without any problem, but pc is stuck on ubuntu logo when I shutdown. while shutdown keyboard and mouse are turned off but pc remains on. I have to turn the mains power off to shutdown the pc. I think this is a major bug in Ubuntu 19.10. I searched for a solution on the internet but could not find any that works. Kindly help to fix it.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: prakash 1438 F.... pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 19.10
InstallationDate: Installed on 2020-01-31 (2 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
IwConfig:
 lo no wireless extensions.

 eno1 no wireless extensions.
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
 Bus 001 Device 003: ID 1a2c:0e24 China Resource Semico Co., Ltd USB Keyboard
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Gigabyte Technology Co., Ltd. H370M-D3H
Package: systemd 242-7ubuntu3.2
PackageArchitecture: amd64
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic root=UUID=a883551d-0fff-4cdb-bc6d-d442860a0ec0 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
RelatedPackageVersions:
 linux-restricted-modules-5.3.0-29-generic N/A
 linux-backports-modules-5.3.0-29-generic N/A
 linux-firmware 1.183.3
RfKill:

Tags: eoan
Uname: Linux 5.3.0-29-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: 03/14/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F12
dmi.board.asset.tag: Default string
dmi.board.name: H370M D3H-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF12:bd03/14/2019:svnGigabyteTechnologyCo.,Ltd.:pnH370M-D3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnH370MD3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: H370M-D3H
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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 1861645

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
Prakash Shenoy (ppshenoy) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected eoan
description: updated
Revision history for this message
Prakash Shenoy (ppshenoy) wrote : CRDA.txt

apport information

Revision history for this message
Prakash Shenoy (ppshenoy) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Prakash Shenoy (ppshenoy) wrote : Dependencies.txt

apport information

Revision history for this message
Prakash Shenoy (ppshenoy) wrote : Lspci.txt

apport information

Revision history for this message
Prakash Shenoy (ppshenoy) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Prakash Shenoy (ppshenoy) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Prakash Shenoy (ppshenoy) wrote : ProcEnviron.txt

apport information

Revision history for this message
Prakash Shenoy (ppshenoy) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Prakash Shenoy (ppshenoy) wrote : ProcModules.txt

apport information

Revision history for this message
Prakash Shenoy (ppshenoy) wrote : PulseList.txt

apport information

Revision history for this message
Prakash Shenoy (ppshenoy) wrote : SystemdDelta.txt

apport information

Revision history for this message
Prakash Shenoy (ppshenoy) wrote : UdevDb.txt

apport information

Revision history for this message
Prakash Shenoy (ppshenoy) wrote : WifiSyslog.txt

apport information

Revision history for this message
You-Sheng Yang (vicamo) wrote :

@ppshenoy, could you reboot with following kernel parameters and paste the screenshot (probably by camera) when it stuck at shutting down and syslog file?

  1. replace following line in your /etc/default/grub:

       GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

     with:

       GRUB_CMDLINE_LINUX_DEFAULT="systemd.log_level=debug"

  2. run `update-grub` to update grub config
  3. reboot with aforementioned changes
  4. shutdown and take a picture of messages printed in the console mode.
  5. attach both the picture and syslog

Revision history for this message
Prakash Shenoy (ppshenoy) wrote : Re: [Bug 1861645] Re: PC fails to shutdown.
Download full text (4.0 KiB)

Dear Sir,

Thanks for your prompt support. Kindly let me know where can I find the
syslog file.

Regards,

Prakash Shenoy.

On Tue, 4 Feb 2020, 15:45 You-Sheng Yang, <email address hidden>
wrote:

> @ppshenoy, could you reboot with following kernel parameters and paste
> the screenshot (probably by camera) when it stuck at shutting down and
> syslog file?
>
> 1. replace following line in your /etc/default/grub:
>
> GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
>
> with:
>
> GRUB_CMDLINE_LINUX_DEFAULT="systemd.log_level=debug"
>
> 2. run `update-grub` to update grub config
> 3. reboot with aforementioned changes
> 4. shutdown and take a picture of messages printed in the console mode.
> 5. attach both the picture and syslog
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1861645
>
> Title:
> PC fails to shutdown.
>
> Status in linux package in Ubuntu:
> Incomplete
> Status in systemd package in Ubuntu:
> New
>
> Bug description:
> I have a pc with Motherboard Gigabyte H370M D3H, Processor Intel Core I3
> 8100 3.6Ghz 6MbL3, RAM Corsair 16Mb 2400 Hz. I can reboot pc without any
> problem, but pc is stuck on ubuntu logo when I shutdown. while shutdown
> keyboard and mouse are turned off but pc remains on. I have to turn the
> mains power off to shutdown the pc. I think this is a major bug in Ubuntu
> 19.10. I searched for a solution on the internet but could not find any
> that works. Kindly help to fix it.
> ---
> ProblemType: Bug
> ApportVersion: 2.20.11-0ubuntu8.2
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: prakash 1438 F.... pulseaudio
> CurrentDesktop: ubuntu:GNOME
> DistroRelease: Ubuntu 19.10
> InstallationDate: Installed on 2020-01-31 (2 days ago)
> InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
> IwConfig:
> lo no wireless extensions.
>
> eno1 no wireless extensions.
> Lsusb:
> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> Bus 001 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
> Bus 001 Device 003: ID 1a2c:0e24 China Resource Semico Co., Ltd USB
> Keyboard
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> MachineType: Gigabyte Technology Co., Ltd. H370M-D3H
> Package: systemd 242-7ubuntu3.2
> PackageArchitecture: amd64
> ProcFB: 0 i915drmfb
> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic
> root=UUID=a883551d-0fff-4cdb-bc6d-d442860a0ec0 ro quiet splash vt.handoff=7
> ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
> RelatedPackageVersions:
> linux-restricted-modules-5.3.0-29-generic N/A
> linux-backports-modules-5.3.0-29-generic N/A
> linux-firmware 1.183.3
> RfKill:
>
> Tags: eoan
> Uname: Linux 5.3.0-29-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: 03/14/2019
> dmi.bios.vendor: American Megatrends Inc.
> dm...

Read more...

Revision history for this message
Prakash Shenoy (ppshenoy) wrote :

Dear Sir what is the status of the bug I reported. There is no progress after 4th Feb.

Revision history for this message
You-Sheng Yang (vicamo) wrote :

@Prakash, for syslog file, it's under /var/log/syslog.

Revision history for this message
Dan Streetman (ddstreet) wrote :

please reopen if this is still an issue

Changed in systemd (Ubuntu):
status: New → Invalid
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.