This morning I updated my Tumbleweed system which installed kernel 4.14.0-1-default. Now when I boot I see the following error messages which do not appear when I boot 4.13.12-1-default kernel
acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
kfd kfd: kgd2kfd_probe failed
now I have seen elsewhere that the first message can be ignored but I dont understand why these now appear on the new kernel. My system runs an AMD x86-64 processor by the way. I have not seen any issues (yet) but I dont like new errors popping up like this.
Anyone any ideas please?
Stuart
Just updated to 20171120, also running on an AMD x86-64.
I’m also seeing: “acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM”
but not: “kfd kfd: kgd2kfd_probe failed”
additionally, I’m seeing:
ACPI Exception: Could not find/resolve named package element: LNKA (20170728/dspkginit-381)
multiple (11 in fact) times.
Also the same line with “LNKB”, “LNKC”, and “LNKD”, again multiple (11 times each).
No idea at this stage, so far there appears no adverse effects, off to Google… :\
I dont get the ACPI Exception and the only messages relating to LNKA through F are
ACPI: PCI Interrupt Link [LNKA] (IRQs 10 11 14 15) *0
one for each.
Stuart
Google didn’t return anything particularly useful.
Poster on the manjaro forum is seeing a similar ACPI Exception ( https://forum.manjaro.org/t/error-at-journal-in-the-boot-in-the-kernel-4-14/35126 )
There was another snapshot released 20171121 which included, amongst others, a rebuild of the kernel, still seeing the “problem”. I’ll see what happens over the next day or so, unsure as to whether it warrants a bug report…
There have been a couple of updates to kernel 4.14 recently but I still see the same two errors on every boot of the system using 4.14.
Just looked at Google and a debian bug report shows up which gave me some clues to look further and I see the following messages relating to kfd:-
3.162254] kfd kfd: Initialized module
4.148214] kfd kfd: DID 6779 is missing in supported_devices
4.148218] kfd kfd: kgd2kfd_probe failed
which seems to show something is missing, how do I find out what DID 6779 is?
Stuart
Assuming the DID 6779 is a device ID of some sort an LSPCI shows that my Radeon CAICOS gfx card as the only one associated with 6779, so could that be correct? Anyway I still dont see any problems as far as I can tell.
Stuart
It looks perhaps as if the kfd “errors” have always been there, but silent.
This patch https://patchwork.freedesktop.org/patch/171967/ seems to be the reason for them now being displayed rather than simply ignored. I’m guessing, but don’t know, they are fairly benign.