amdgpu system sometimes takes an extremely long time to boot

Bug #1569436 reported by Per Parker
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

I noticed this problem after I corrected the system clock from another OS (fixing the time on any of my OSs causes the others to display an incorrect time...). Ordinarily Ubuntu 16.04 starts in about 30 seconds on my system and displays the splash screen during early initialization. When the system clock is wrong, the splash screen is not displayed and the system takes about 5 minutes to start.

Additionally, when the screen saver is on, it takes about 5 minutes from moving the mouse for the screens to turn on (there are two, if that matters)

I think this is related to libdrm-amdgpu1 because dmesg gives me hundreds of messages looking like:

[ 308.832210] Failed to send Message.
[ 309.230389] Failed to send Previous Message.

These messages originate from a drm source file:
https://github.com/torvalds/linux/blob/master/drivers/gpu/drm/amd/powerplay/smumgr/tonga_smumgr.c
(There's another amdgpu file with the same messages but my GPU is tonga architecture)

I'm not entirely sure that the system clock is responsible but this seems to be an intermittent problem and I haven't noticed any other contributing factors.

$ lsb_release -rd
Description: Ubuntu Xenial Xerus (development branch)
Release: 16.04

$ apt-cache policy libdrm-amdgpu1
libdrm-amdgpu1:
  Installed: 2.4.67-1
  Candidate: 2.4.67-1
  Version table:
 *** 2.4.67-1 500
        500 http://ca.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: libdrm-amdgpu1 2.4.67-1
ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
Uname: Linux 4.4.0-18-generic x86_64
.tmp.unity.support.test.0:

ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
BootLog:

CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Tue Apr 12 11:33:56 2016
Dependencies:
 gcc-6-base 6-20160405-0ubuntu2
 libc6 2.23-0ubuntu2
 libdrm2 2.4.67-1
 libgcc1 1:6-20160405-0ubuntu2
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Tonga PRO [Radeon R9 285/380] [1002:6939] (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd Tonga PRO [Radeon R9 285/380] [1458:229d]
InstallationDate: Installed on 2016-03-21 (21 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
MachineType: Gigabyte Technology Co., Ltd. X58A-UD5
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic root=UUID=b3ebe998-0b62-447a-9406-abf7f5e1f94c ro quiet splash vt.handoff=7
SourcePackage: libdrm
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/01/2011
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: FD
dmi.board.name: X58A-UD5
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFD:bd02/01/2011:svnGigabyteTechnologyCo.,Ltd.:pnX58A-UD5:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnX58A-UD5:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: X58A-UD5
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.12.2+16.04.20160331-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Tue Apr 12 11:21:51 2016
xserver.configfile: default
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.3-1ubuntu2
xserver.video_driver: amdgpu

Revision history for this message
Per Parker (wisalam) wrote :
Revision history for this message
Per Parker (wisalam) wrote :

Normal dmesg for reference.

Per Parker (wisalam)
description: updated
summary: - System takes an extremely long time to boot when system clock inaccurate
+ amdgpu system sometimes takes an extremely long time to boot
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

the source is the kernel

affects: libdrm (Ubuntu) → linux (Ubuntu)
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
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.