disco 19.04 doesn't shutdown on an Asrock 970 Extreme 4

Bug #1829077 reported by J-Paul BERARD
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

I have a fresh install of Ubuntu 19.04 GNOME 64 bits.
When I choose "Power Off", it closes the session screen but then it displays the red dots who scroll under Ubuntu logo and it never stop completely.
I can listen the hard disk containing my home directory which stops (the system is on a SSD).
Each time, I have to switch off the computer. I can start it again without any problem.

The command "sudo shutdown now" give the same result.
This computer had not this problem with the previous version of Ubuntu.

Proc : AMD Fx 8320
Motherboard : Asrock 970 Extreme 4
graphic card : Radeon 6850
Ram : 8Go
Ubuntu 19.04 is the only OS on the SSD system drive
/home is on a second hard drive

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug report, could you add the journalctl log from a such boot?

affects: gnome-power-manager (Ubuntu) → systemd (Ubuntu)
Revision history for this message
J-Paul BERARD (arverne) wrote :

Thanks for your answer.
Could you tell me how to get this log file ? I have not journalctl.log file.
In var/log/journal, I have a dir with several files, about 250 MB...

Revision history for this message
J-Paul BERARD (arverne) wrote :

Finally, I used this command to get a journal :
journalctl -b -1 > journalExport
You will find the file down

Revision history for this message
Sebastien Bacher (seb128) wrote :

That's the right command, thanks!

Revision history for this message
J-Paul BERARD (arverne) wrote :

Hello,

One more information : I looked on the motherboard which has a "debug" display.
When I shutdown the system and the screen stay with the red dot, the motherboard display an error code : 05 = "OEM initialization before microcode loading"...
(the computer is from 2011 and the Bios updated)

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in systemd (Ubuntu):
status: New → Confirmed
J-Paul BERARD (arverne)
description: updated
Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Does this happen to older Ubuntu releases?

Revision history for this message
J-Paul BERARD (arverne) wrote :

Never !
I had the computer since 2011 I think, and I used all the releases since this time, upgrade or fresh install.
I don't remember having this problem...
(Maybe a different problem : this last days, sometimes, Ubuntu suddenly close and start again...)

Revision history for this message
J-Paul BERARD (arverne) wrote :

And another interesting information :
If I use a live-cd (USB disk) with 19.04 to open a session : the problem is the same
If I use a live-cd (USB-disk) with 18.04 to open a session : the computer stop normally at the end when I remove the USB-disk and press Return !

So, it looks really to be an issue of 19.04.

summary: - disco 19.04 doesn't shutdown
+ disco 19.04 doesn't shutdown on an Asrock 970 Extreme 4
Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

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

Revision history for this message
J-Paul BERARD (arverne) wrote :

Hello,
I didn't reach to start with this new 5.2 kernel !
I installed the 4 .deb packages for my amd64 computer without error message ; I updated Grub (and the kernel 5.2 is in the list) but when I start, in Grub, the kernel 5.2 doesn't appear !
I have uninstalled VirtualBox : no effect
I'm not used to that at all and I don't understand what to do...
Sorry.

Revision history for this message
J-Paul BERARD (arverne) wrote :

YES ! It works !
I reached to start with kernel 5.2 (I had a problem with Grub because of 2 versions of Ubuntu installed on 2 partitions, and it booted not with the right Grub).

So, when I boot with kernel 5.2, the computer stop normally and completely like before.
Thanks !

affects: systemd (Ubuntu) → linux (Ubuntu)
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.