Xubuntu 18.04 sometimes freezes when turned on on logo

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 1842865

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.

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

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

Kai-Heng Feng (kaihengfeng), with kernel 5.3 the same problem. I can not turn off the computer using alt+SysRq+R E I S O

@Maxim Smih: Why did you subscribe all those teams and individuals? If you don't have a good reason (I doubt you have) it's bad manners.

 @Gunnar Hjalmarsson (gunnarhj) :
 https://bugzilla.kernel.org/show_bug.cgi?id=204779

Please try the different "reboot=" parameters described here:
https://www.kernel.org/doc/html/latest/admin-guide/kernel-parameters.html

Unfortunately, I did not understand what needs to be done. How to try other parameters "reboot="?

"reboot=p", "reboot=a", etc.

If I understand correctly, you need to write "reboot = p", "reboot = a. In the terminal. These commands do not overload the computer.

https://wiki.ubuntu.com/Kernel/KernelBootParameters

reboot = o is necessary so that during the freeze you can turn off the computer using alt + SysRq + REISUO. Or fix the computer freeze problem?

Now I'm testing the 4.15 kernel. While the computer does not freeze

It use different method to reboot.

But if it's a regression (once worked on 4.15), can you please perform a kernel bisection?

I do not know how to divide the core into parts

Would it be possible for you to do a kernel bisection?

First, find the last good -rc kernel and the first bad -rc kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/

Then,
$ sudo apt build-dep linux
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
$ cd linux
$ git bisect start
$ git bisect good $(the good version you found)
$ git bisect bad $(the bad version found)
$ make localmodconfig
$ make -j`nproc` deb-pkg
Install the newly built kernel, then reboot with it.
If the issue still happens,
$ git bisect bad
Otherwise,
$ git bisect good
Repeat to "make -j`nproc` deb-pkg" until you find the commit that causes the regression.

This bug does not always appear. Maybe in a week it will appear, and maybe right away. I will try to do what you wrote, but I can’t guarantee what happens. In the new kernel release, is there a chance that there will be no problem?

 When typing, this gives make localmodconfig - "arch/x86/Makefile:184: *** Compiler lacks asm-goto support.. Останов.
"

What's the output of `gcc --version`?

Reading package lists ... Done
Building a dependency tree
Reading status information ... Done
The gcc package is not available, but is listed in the dependency list of another
package. This may mean that the package is missing, out of date, or
available from sources not mentioned in sources.list

So I guess `sudo apt build-dep linux` was missed?

sudo apt build-dep linux - Reading package lists ... Done
E: You must fill out sources.list by putting the source package URIs of the source packages

It’s hard for me to complete all the steps that you described. I can say that the computer works well with the 4.15 kernel. With kernel 5.0 is bad. I will also test the 4.18 kernel and write to you.

https://help.ubuntu.com/community/Repositories/Ubuntu

Thank you for the article. Now I'll see how the computer works with the 4.18 kernel. Most likely it is a kernel 5.0 problem or systemd

here is no such problem with the 4.18.0.25 kernel. It happens that after 90 seconds it turns off. And with a new core, he writes that he will turn off after 90 seconds, but he will not turn off.

here is no such problem with the 5.0.0-15 kernel

Can you please test 5.0.0-37?

Hi there,

I have the similar problem.
How can I help for debugging?

While I'm testing the kernel 5.0.0-37

Hi there,
Seems like I resolved my issue which is the same as this one by upgrading firmware on BIOS from F13 to F14. Mi motherboard is GIGABYTE B360 HD3(https://www.gigabyte.com/Motherboard/B360-HD3-rev-10#kf).

I recently updated the BIOS since the computer did not turn on with the 4.15 kernel

The kernel 5.0.0-37 most likely solved the problem. Comp did not freeze. If something changes, I will write.