Not booting at all times

Bug #1773232 reported by steven krol on 2018-05-24
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
High
Unassigned
Bionic
High
Unassigned

Bug Description

I'm running Linux kernel 4.17rc5. (this problem is also with the 4.16 kernel and 4.15). My computer randomly freezes up after a hour of less and sometimes it works for more then a day. But when I check the kern.log or syslog it does not show any messages at the time of crashing. So is there a way that I can find you why it crashes?

Also, after a crash it sometimes refuses to boot at all. It will give me a black screen. After restarting for 20 or more times it boots up. Sometimes my password doesn't work while booting even though I use the same (correct) password after the restart.

I have made a video on this issue here: https://www.youtube.com/watch?v=gqH8ySXOUmk&feature=youtu.be
(the video is a bit out of focus, forgot the manual focus. I have speeded up someparts to make it more pleasant to watch)

I'd like to include some logs but Can't find any relevant logs since it does not log during the period of the error. I Have attached a picture of my screen that it will sometimes show.

The moment it did boot up I was using kernel 4.15 (but with that version not all of my screens work)
After the reboot I used the kernel 4.17r5 again and it did work.
This happens to me a lot and it can take a lot of restarting in order to boot.

In the video it didnt show the problem that my password would not be recognised. However this sometimes happens too.

One more bug I'm having is that my thrird screen is not being recognised to it sets a lower screen resolution. I have solved this with forcing the screen resolution to 1080x1920 but then the menu bar is not shown correctly. and I have to drag the screen to the right place in the settings in order to have the menu's correctly.
(video: https://youtu.be/Tq-TEeAAIGA) this is what I have to do at startup
Is there anything more I can do to make this bug report more specific?
---
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2018-05-06 (17 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Package: linux (not installed)
Tags: bionic
Uname: Linux 4.17.0-041700rc5-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
---
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2018-05-06 (17 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Package: linux (not installed)
Tags: bionic
Uname: Linux 4.17.0-041700rc5-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
---
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2018-05-06 (18 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Package: linux (not installed)
Tags: bionic
Uname: Linux 4.14.0-041400-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True

steven krol (unisteven1) wrote :

apport information

tags: added: apport-collected bionic
description: updated

apport information

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 1773232

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

apport information

description: updated
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
description: updated

apport information

Joseph Salisbury (jsalisbury) wrote :

Did this issue start happening after an update/upgrade? Was there a kernel version where you were not having this particular problem? This will help determine if the problem you are seeing is the result of a regression, and when this regression was introduced. If this is a regression, we can perform a kernel bisect to identify the commit that introduced the problem.

Changed in linux (Ubuntu):
importance: Undecided → High
Changed in linux (Ubuntu Bionic):
status: New → Incomplete
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Changed in linux (Ubuntu Bionic):
importance: Undecided → High
tags: added: kernel-da-key
Joseph Salisbury (jsalisbury) wrote :

Also, would it be possible for you to test some prior kernels to see if there was a previous good version? If there is a prior good kernel, we can perform a kernel bisect to identify the commit that introduced this bug.

Prior upstream kernels can be found at:
http://kernel.ubuntu.com/~kernel-ppa/mainline/

I would suggesting starting with 4.14, then maybe 4.13, 4.12, etc.

steven krol (unisteven1) wrote :

Allright, I will test out multiple kernels and share the results. However my hardware might not be supported for older kernels, Atleast my multi monitor screen setup will not work < 4.17

steven krol (unisteven1) wrote :

That means I can not test all bugs mentioned. only the starting up bug

steven krol (unisteven1) wrote :

I've tested it on version 4.14 and it seems to boot up every time. However It will only turn on 1 display instead of 3 and at a low resolution. I've repeated the test 5 times with the same results. after that I have tested 4.17 and it hung up again at boot.

Changed in linux (Ubuntu):
status: Incomplete → New
Changed in linux (Ubuntu Bionic):
status: Incomplete → New

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 1773232

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
Changed in linux (Ubuntu Bionic):
status: New → Incomplete

apport information

description: updated

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Changed in linux (Ubuntu Bionic):
status: Incomplete → Confirmed
steven krol (unisteven1) wrote :

I've did some more testing with multiple versions. I've figgured out the bug got introduced between kernel 4.15.0-rc1 and 4.15.0-rc2
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc1/
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc2/
If there is a clear way somewhere that explains me how to do a git bisect, I'd love to help out and narrowing the bug down to the commit.

steven krol (unisteven1) on 2018-06-16
Changed in linux (Ubuntu):
status: Confirmed → New

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 1773232

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
Kai-Heng Feng (kaihengfeng) wrote :

How you do a bisect:

$ 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 v4.15-rc1
$ git bisect bad v4.15-rc2
$ 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.

steven krol (unisteven1) wrote :

When trying to do: make -j`nproc` deb-pkg

I get the following error

unisteven@Stevens-PC:~/Desktop/Bisect/linux$ sudo make -j`nproc` deb-pkg
[sudo] password for unisteven:
Makefile:928: "Cannot use CONFIG_STACK_VALIDATION=y, please install libelf-dev, libelf-devel or elfutils-libelf-devel"
  CHK include/config/kernel.release
make clean
  CLEAN .
  CLEAN arch/x86/purgatory
  CLEAN arch/x86/tools
  CLEAN .tmp_versions
  TAR linux-4.15.0-rc1+.tar.gz
make KBUILD_SRC=
Makefile:928: "Cannot use CONFIG_STACK_VALIDATION=y, please install libelf-dev, libelf-devel or elfutils-libelf-devel"
  CHK include/config/kernel.release
  HOSTCC scripts/basic/fixdep
  CHK include/generated/uapi/linux/version.h
  HOSTCC scripts/basic/bin2c
  HOSTCC arch/x86/tools/relocs_32.o
  HOSTCC arch/x86/tools/relocs_64.o
  HOSTCC arch/x86/tools/relocs_common.o
  CHK include/generated/utsrelease.h
  CC scripts/mod/empty.o
  HOSTCC scripts/selinux/genheaders/genheaders
  HOSTCC scripts/selinux/mdp/mdp
  HOSTCC scripts/mod/mk_elfconfig
  CC scripts/mod/devicetable-offsets.s
  HOSTCC scripts/kallsyms
  HOSTCC scripts/conmakehash
  CHK scripts/mod/devicetable-offsets.h
  MKELF scripts/mod/elfconfig.h
  HOSTCC scripts/mod/modpost.o
  HOSTCC scripts/recordmcount
  HOSTCC scripts/sortextable
  HOSTLD arch/x86/tools/relocs
  HOSTCC scripts/asn1_compiler
  HOSTCC scripts/mod/file2alias.o
  HOSTCC scripts/sign-file
scripts/sign-file.c:25:10: fatal error: openssl/opensslv.h: No such file or directory
 #include <openssl/opensslv.h>
          ^~~~~~~~~~~~~~~~~~~~
compilation terminated.
scripts/Makefile.host:90: recipe for target 'scripts/sign-file' failed
make[3]: *** [scripts/sign-file] Error 1
make[3]: *** Waiting for unfinished jobs....
  HOSTCC scripts/mod/sumversion.o
  CC arch/x86/purgatory/purgatory.o
  AS arch/x86/purgatory/stack.o
  AS arch/x86/purgatory/setup-x86_64.o
  CC arch/x86/purgatory/sha256.o
  AS arch/x86/purgatory/entry64.o
  CC arch/x86/purgatory/string.o
  LD arch/x86/purgatory/purgatory.ro
  BIN2C arch/x86/purgatory/kexec-purgatory.c
  CHK include/generated/timeconst.h
  CC kernel/bounds.s
  HOSTLD scripts/mod/modpost
Makefile:576: recipe for target 'scripts' failed
make[2]: *** [scripts] Error 2
make[2]: *** Waiting for unfinished jobs....
  CHK include/generated/bounds.h
  CC arch/x86/kernel/asm-offsets.s
  GEN scripts/gdb/linux/constants.py
  CHK include/generated/asm-offsets.h
  CALL scripts/checksyscalls.sh
scripts/package/Makefile:86: recipe for target 'deb-pkg' failed
make[1]: *** [deb-pkg] Error 2
Makefile:1339: recipe for target 'deb-pkg' failed
make: *** [deb-pkg] Error 2

steven krol (unisteven1) on 2018-06-22
Changed in linux (Ubuntu):
status: Incomplete → New

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 1773232

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
steven krol (unisteven1) on 2018-07-02
Changed in linux (Ubuntu):
status: Incomplete → New
Changed in linux (Ubuntu):
status: New → Incomplete
Kai-Heng Feng (kaihengfeng) wrote :

Sorry for the late reply. Please install libssl-dev.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers