Booting randomly fails at black screen

Bug #1616447 reported by Michael J Gray
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xorg (Ubuntu)
Expired
Low
Unassigned

Bug Description

Problem appears related to Bug #1369216

Successful boot always comes by using recovery mode

gpu-manager problem report

● gpu-manager.service - Detect the available GPUs and deal with any system changes
   Loaded: loaded (/lib/systemd/system/gpu-manager.service; enabled; vendor preset: enabled)
   Active: inactive (dead) since Wed 2016-08-24 12:02:47 BST; 19min ago
  Process: 2601 ExecStart=/usr/bin/gpu-manager --log /var/log/gpu-manager.log (code=exited, status=0/SUCCESS)
 Main PID: 2601 (code=exited, status=0/SUCCESS)

Aug 24 12:02:48 bigasus gpu-manager[2601]: /etc/modprobe.d is not a file
Aug 24 12:02:48 bigasus gpu-manager[2601]: /etc/modprobe.d is not a file
Aug 24 12:02:48 bigasus gpu-manager[2601]: /etc/modprobe.d is not a file
Aug 24 12:02:48 bigasus gpu-manager[2601]: /etc/modprobe.d is not a file
Aug 24 12:02:48 bigasus gpu-manager[2601]: /etc/modprobe.d is not a file
Aug 24 12:02:48 bigasus gpu-manager[2601]: Error: can't open /lib/modules/4.4.0-34-generic/updates/dkms
Aug 24 12:02:48 bigasus gpu-manager[2601]: Error: can't open /lib/modules/4.4.0-34-generic/updates/dkms
Aug 24 12:02:48 bigasus gpu-manager[2601]: update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf
Aug 24 12:02:46 bigasus systemd[1]: Starting Detect the available GPUs and deal with any system changes...
Aug 24 12:02:47 bigasus systemd[1]: Started Detect the available GPUs and deal with any system changes.

System info from journal of boot

kernel: Linux version 4.4.0-34-generic (buildd@lgw01-20) (gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2.1) ) #53-Ubuntu SMP Wed Jul 27 16:06:39 UTC 2016 (Ubuntu 4.4.0-34.53-generic 4.4.15)
Aug 24 12:02:16 bigasus kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic root=UUID=ed792125-175f-4f33-b6f7-0170e63f5ff4 ro recovery nomodeset
Aug 24 12:02:16 bigasus kernel: KERNEL supported cpus:
Aug 24 12:02:16 bigasus kernel: Intel GenuineIntel
Aug 24 12:02:16 bigasus kernel: AMD AuthenticAMD
Aug 24 12:02:16 bigasus kernel: Centaur CentaurHauls

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
Uname: Linux 4.4.0-34-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: KDE
Date: Wed Aug 24 12:32:23 2016
InstallationDate: Installed on 2016-06-11 (74 days ago)
InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Michael J Gray (ubmike) wrote :
Revision history for this message
penalvch (penalvch) wrote :

Michael J Gray, thank you for reporting this and helping make Ubuntu better.

Could you please run the following command once from a terminal by ensuring you have the package xdiagnose installed, and that you click the Yes button for attaching additional debugging information:
apport-collect -p xorg 1616447

When reporting xorg related bugs in the future, please do so via the above method. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

Changed in xorg (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Michael J Gray (ubmike) wrote : Re: [Bug 1616447] Re: Booting randomly fails at black screen

Hello,
I installed package xdiagnose but your command fails when run following
a reboot after an update (so no package upgrade would be in progress)

michael@bigasus:~/Documents$ apport-collect -p xorg 1616447
ERROR: Could not import module, is a package upgrade in progress?
Error: No module named PyQt5.QtCore

Thank you
Mike Gray

On 01/09/16 08:36, Christopher M. Penalver wrote:
> Michael J Gray, thank you for reporting this and helping make Ubuntu
> better.
>
> Could you please run the following command once from a terminal by ensuring you have the package xdiagnose installed, and that you click the Yes button for attaching additional debugging information:
> apport-collect -p xorg 1616447
>
> When reporting xorg related bugs in the future, please do so via the
> above method. You can learn more about this functionality at
> https://wiki.ubuntu.com/ReportingBugs.
>
> ** Changed in: xorg (Ubuntu)
> Importance: Undecided => Low
>
> ** Changed in: xorg (Ubuntu)
> Status: New => Incomplete
>

Revision history for this message
penalvch (penalvch) wrote :

Michael J Gray, one may run the command in a non-KDE environment via http://cdimage.ubuntu.com/daily-live/current/ .

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

[Expired for xorg (Ubuntu) because there has been no activity for 60 days.]

Changed in xorg (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.