Bug 24444

Summary:	Failed to get unique processor _UID since kernel 4.14.89-server-1.mga6, older kernels don't show the error, buit 4.14.100-server-1.mga6 does, too
Product:	Mageia	Reporter:	Markus Mertens <Mertens.MPT>
Component:	RPM Packages	Assignee:	Kernel and Drivers maintainers <kernel>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	marja11, ouaurelien
Version:	6
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	kernel-4.14.100	CVE:
Status comment:
Attachments:	lscpu lspci

Description Markus Mertens 2019-02-28 12:27:56 CET

Description of problem:

Since I upgraded to kernel 4.14.89-server-1.mga6 the first messages while booting are:

Feb 25 12:53:58 localhost kernel: [    2.466386] acpi LNXCPU:14: Failed to get unique processor _UID (0xff)
Feb 25 12:53:58 localhost kernel: [    2.466405] acpi LNXCPU:15: Failed to get unique processor _UID (0xff)
Feb 25 12:53:58 localhost kernel: [    2.466418] acpi LNXCPU:16: Failed to get unique processor _UID (0xff)
Feb 25 12:53:58 localhost kernel: [    2.466431] acpi LNXCPU:17: Failed to get unique processor _UID (0xff)
...
Feb 25 12:53:58 localhost kernel: [    2.468072] acpi LNXCPU:8f: Failed to get unique processor _UID (0xff)
Feb 25 12:53:58 localhost kernel: [    2.468349] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])

It does not happen with older kernel releases, but 4.14.100-server-1.mga6 has the same problem.


How reproducible:

It happens always on my system.


Steps to Reproduce:

Just boot.

Comment 1 Markus Mertens 2019-02-28 12:29:16 CET

Created attachment 10807 [details]
lscpu

Comment 2 Markus Mertens 2019-02-28 12:29:46 CET

Created attachment 10808 [details]
lspci

Marja Van Waes 2019-02-28 19:32:46 CET

Summary: Failed to get unique processor _UID => Failed to get unique processor _UID since kernel 4.14.89-server-1.mga6, older kernels don't show the error, buit 4.14.100-server-1.mga6 does, too
CC: (none) => marja11
Source RPM: (none) => kernel-4.14.100
Assignee: bugsquad => kernel

Comment 3 Aurelien Oudelet 2020-08-16 22:44:41 CEST

Mageia 6 changed to end-of-life (EOL) status on 2019-09-30. It is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

Package Maintainer: If you wish for this bug to remain open because you plan 
to fix it in a currently maintained version, simply change the 'version' to 
a later Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we 
weren't able to fix it before Mageia 6's end of life. If you are able to 
reproduce it against a later version of Mageia, you are encouraged to click 
on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a more recent
Mageia release includes newer upstream software that fixes bugs or makes them
obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

Best regards,
Aurélien
Bugsquad Team

CC: (none) => ouaurelien
Resolution: (none) => OLD
Status: NEW => RESOLVED