[Bug 103463] [drm:amdgpu_get_bios [amdgpu]] *ERROR* ACPI VFCT table present but broken (too short #2)
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Thu Oct 26 08:18:50 UTC 2017
https://bugs.freedesktop.org/show_bug.cgi?id=103463
Bug ID: 103463
Summary: [drm:amdgpu_get_bios [amdgpu]] *ERROR* ACPI VFCT table
present but broken (too short #2)
Product: DRI
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel at lists.freedesktop.org
Reporter: devurandom at gmx.net
Created attachment 135050
--> https://bugs.freedesktop.org/attachment.cgi?id=135050&action=edit
dmesg (broken boot)
I am seeing messages like the following during startup:
```
[drm:amdgpu_get_bios [amdgpu]] *ERROR* ACPI VFCT table present but broken (too
short #2)
AMD-Vi: Event logged [IO_PAGE_FAULT device=00:00.0 domain=0x0000
address=0x00000000fffc0000 flags=0x0070]
[drm:dce_v11_0_set_pageflip_irq_state [amdgpu]] *ERROR* invalid pageflip crtc
5
[drm:amdgpu_irq_disable_all [amdgpu]] *ERROR* error disabling interrupt (-22)
amdgpu 0000:01:00.0: Fatal error during GPU init
[TTM] Memory type 2 has not been initialized
```
The first message always appears, while the others are not as easily
reproducable. During a boot like this, the second card (AMD Radeon RX 560)
fails to come up and is not available to the system. After a "regular"
startup, `dmesg -l err` shows the following messages:
```
[ 3.056584] [drm:amdgpu_get_bios [amdgpu]] *ERROR* ACPI VFCT table present
but broken (too short #2)
[ 6.592964] ACPI Error: [AFN7] Namespace lookup failure, AE_NOT_FOUND
(20170531/psargs-364)
[ 6.593020] ACPI Error: Method parse/execution failed
\_SB.PCI0.VGA.LCD._BCM, AE_NOT_FOUND (20170531/psparse-550)
[ 6.593062] ACPI Error: Evaluating _BCM failed (20170531/video-364)
[ 6.593207] ACPI Error: [AFN7] Namespace lookup failure, AE_NOT_FOUND
(20170531/psargs-364)
[ 6.593243] ACPI Error: Method parse/execution failed
\_SB.PCI0.PB21.VGA.LCD._BCM, AE_NOT_FOUND (20170531/psparse-550)
[ 6.593286] ACPI Error: Evaluating _BCM failed (20170531/video-364)
[ 6.628143] snd_hda_intel 0000:01:00.1: control 3:0:0:ELD:0 is already
present
[ 6.631508] snd_hda_intel 0000:01:00.1: control 3:0:0:ELD:0 is already
present
[ 6.637737] snd_hda_intel 0000:01:00.1: control 3:0:0:ELD:0 is already
present
```
Other weird behaviour I notice is:
* Hangs of the entire system when I start Steam using `env DRI_PRIME=1 steam`
(nothing reacts to commands anymore, including mouse clicks, the power button
and the num-lock key, and the mouse cursor moves very sluggishly)
* Crashes of KWin when using Alt+Tab (s.b.)
* The firmware and GRUB (and Linux, initially) display at 1024x768, while the
monitor's native resolution is 2560x1080. After the Linux kernel takes over,
the monitor switches back to the native resolution.
* Sometimes the system fails to boot entirely and gets stuck after the "*ERROR*
ACPI VFCT table present but broken" error message
I would hope that someone could guide me in gathering more information about
this and in the best case getting additional output or a backtrace from the
kernel, please.
Please find the full output of dmesg, lshw, lspci, glxinfo attached. Output
taken after a "broken" boot with the AMD Radeon RX 560 not coming up is
suffixed with "broken-boot", while output taken from a system that came up more
completely is suffixed with "regular-boot".
I run Gentoo Linux with following software:
* Linux 4.13.8
* Mesa 17.2.3
* LLVM 5.0.0
I have two graphics cards plugged in:
* AMD Radeon R7 / AMD A10-7800
* AMD Radeon RX 560
The monitor is connected via Display Port to the first card (R7).
If more information would be helpful, please tell me how and I will try to
acquire it.
See-Also: https://bugs.freedesktop.org/show_bug.cgi?id=103234
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20171026/a71f830c/attachment.html>
More information about the dri-devel
mailing list