Hi Vincent, On Fri, Nov 15, 2019 at 01:43:07PM +0100, Vincent Lefevre wrote: > Control: found -1 4.19.67-2+deb10u2 > > On 2018-11-29 09:21:31 +0100, Vincent Lefevre wrote: > > I get the following errors at boot time: > > > > Nov 29 09:04:20 cventin kernel: acpi LNXCPU:06: Failed to get unique > > processor _UID (0xff) > > Nov 29 09:04:20 cventin kernel: acpi LNXCPU:07: Failed to get unique > > processor _UID (0xff) > > Nov 29 09:04:20 cventin kernel: acpi LNXCPU:08: Failed to get unique > > processor _UID (0xff) > > Nov 29 09:04:20 cventin kernel: acpi LNXCPU:09: Failed to get unique > > processor _UID (0xff) > > Nov 29 09:04:20 cventin kernel: acpi LNXCPU:0a: Failed to get unique > > processor _UID (0xff) > > Nov 29 09:04:20 cventin kernel: acpi LNXCPU:0b: Failed to get unique > > processor _UID (0xff) > > Nov 29 09:04:20 cventin kernel: acpi LNXCPU:0c: Failed to get unique > > processor _UID (0xff) > > [...] > > Nov 29 09:04:21 cventin kernel: acpi LNXCPU:8f: Failed to get unique > > processor _UID (0xff) > > > > There were no such errors before linux-image-4.18.0-3-amd64. > > Still occurs in the Debian/stable kernel.
Looking through some of opened bugs for src:linux noticed yours for #914967. This might actually not be a kernel issue, from [1]. [1] https://bugzilla.kernel.org/show_bug.cgi?id=203925 Regards, Salvatore
