Bug 1225063

Summary:	[Firmware Bug]: CPU 0: APIC ID mismatch. CPUID: 0x0000 APIC: 0x0010
Product:	[openSUSE] openSUSE Tumbleweed	Reporter:	John Shand <jshand2013>
Component:	Other	Assignee:	Takashi Iwai <tiwai>
Status:	NEW ---	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None	CC:	jshand2013
Version:	Current	Flags:	tiwai: needinfo? (jshand2013)
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	dmesg log plymouth startup debug logs plymouth shutdown debug logs dmesg log dmesg log hardware info lsmod log

Description John Shand 2024-05-22 19:29:43 UTC

Hi guys,

Since the last update of tumbleweed and the one before that i have noticed that plymouth didn't seem to switch to the normal screen showing the small circle that rotates.  instead it gives you another screen with 3 little dots on the bottom and in some places question marks

i'm wondering if these issues below could be the cause:

[Firmware Bug]: CPU   0: APIC ID mismatch. CPUID: 0x0000 APIC: 0x0010
[Firmware Bug]: CPU   1: APIC ID mismatch. CPUID: 0x0001 APIC: 0x0011

I have attached dmesg log for more information

many thanks

Comment 1 John Shand 2024-05-22 19:30:14 UTC

Created attachment 875037 [details]
dmesg log

Comment 2 John Shand 2024-05-24 19:23:44 UTC

Created attachment 875092 [details]
plymouth startup debug logs

Comment 3 John Shand 2024-05-24 19:24:20 UTC

Created attachment 875093 [details]
plymouth shutdown debug logs

Comment 4 John Shand 2024-05-24 19:25:01 UTC

it seems that at the start there maybe files missing of file have the wrong permissions to run correctly

Comment 5 Takashi Iwai 2024-07-08 07:50:27 UTC

The early 6.9.x kernel had some issues.  Please retest with the latest 6.9.x kernel.

Comment 6 John Shand 2024-07-08 08:56:25 UTC

(In reply to Takashi Iwai from comment #5)
> The early 6.9.x kernel had some issues.  Please retest with the latest 6.9.x
> kernel.

i'm afraid it still shows with this kernel:

Linux johns-pc 6.9.7-1-default #1 SMP PREEMPT_DYNAMIC Fri Jun 28 05:50:47 UTC 2024 (a5efffa) x86_64 x86_64 x86_64 GNU/Linux

i guess i'll wait and see if 6.9.8 will do the same

Comment 7 Takashi Iwai 2024-07-09 15:59:19 UTC

I guess those ACPI issues are irrelevant with your graphics problem.
The log says:

[   13.470950] [  T328] amdgpu 0000:01:00.0: amdgpu: SI support provided by radeon.
[   13.470958] [  T328] amdgpu 0000:01:00.0: amdgpu: Use radeon.si_support=0 amdgpu.si_support=1 to override.

But somehow your system doesn't seem enabling radeon driver.  Do you have a blacklist or such?

If not, try to add those options (radeon.si_support=0 amdgpu.si_support=1) to boot options and retest.

Comment 8 John Shand 2024-07-09 20:03:43 UTC

(In reply to Takashi Iwai from comment #7)
> I guess those ACPI issues are irrelevant with your graphics problem.
> The log says:
> 
> [   13.470950] [  T328] amdgpu 0000:01:00.0: amdgpu: SI support provided by
> radeon.
> [   13.470958] [  T328] amdgpu 0000:01:00.0: amdgpu: Use radeon.si_support=0
> amdgpu.si_support=1 to override.
> 
> But somehow your system doesn't seem enabling radeon driver.  Do you have a
> blacklist or such?
> 
> If not, try to add those options (radeon.si_support=0 amdgpu.si_support=1)
> to boot options and retest.

I will try those options, however, i have always had the radeon driver blacklisted as it cause flickering issue with my screen.  will let you know how i get on

Comment 9 John Shand 2024-07-09 20:14:09 UTC

(In reply to Takashi Iwai from comment #7)
> I guess those ACPI issues are irrelevant with your graphics problem.
> The log says:
> 
> [   13.470950] [  T328] amdgpu 0000:01:00.0: amdgpu: SI support provided by
> radeon.
> [   13.470958] [  T328] amdgpu 0000:01:00.0: amdgpu: Use radeon.si_support=0
> amdgpu.si_support=1 to override.
> 
> But somehow your system doesn't seem enabling radeon driver.  Do you have a
> blacklist or such?
> 
> If not, try to add those options (radeon.si_support=0 amdgpu.si_support=1)
> to boot options and retest.

i have made those changes in grub and rebooted and no change.  the flickering seems to have stopped though.  i have included a few log file to see if it is my specific hardware or not

Comment 10 John Shand 2024-07-09 20:14:44 UTC

Created attachment 875974 [details]
dmesg log

Comment 11 John Shand 2024-07-09 20:15:52 UTC

Created attachment 875975 [details]
dmesg log

Comment 12 John Shand 2024-07-09 20:16:45 UTC

Created attachment 875976 [details]
hardware info

Comment 13 John Shand 2024-07-09 20:17:38 UTC

Created attachment 875977 [details]
lsmod log

Comment 14 Takashi Iwai 2024-07-10 05:35:41 UTC

(In reply to John Shand from comment #9)
> (In reply to Takashi Iwai from comment #7)
> > I guess those ACPI issues are irrelevant with your graphics problem.
> > The log says:
> > 
> > [   13.470950] [  T328] amdgpu 0000:01:00.0: amdgpu: SI support provided by
> > radeon.
> > [   13.470958] [  T328] amdgpu 0000:01:00.0: amdgpu: Use radeon.si_support=0
> > amdgpu.si_support=1 to override.
> > 
> > But somehow your system doesn't seem enabling radeon driver.  Do you have a
> > blacklist or such?
> > 
> > If not, try to add those options (radeon.si_support=0 amdgpu.si_support=1)
> > to boot options and retest.
> 
> i have made those changes in grub and rebooted and no change.  the
> flickering seems to have stopped though.

So, the fundamental problem ("plymouth didn't seem to switch to the normal screen") is fixed by that?

The kernel messages about the firmware bug can be ignored.  It means there is some bugs in the BIOS firmware, but it's likely harmless for your use case.
Try to update your BIOS.