Call Trace dump found in system startup

Support
1

As we need to figure out our next Linux distribution for on-prem systems, we started evaluating ALMA distribution. The first ALMA system installation booted up successfully, however, I found below Call Trace from dmesg.

[    0.097221] CR2: ffff98ed59c03000 CR3: 0000000017c10001 CR4: 00000000000606f0
[    0.097234] Call Trace:
[    0.097235]  <TASK>
[    0.097237]  ? show_trace_log_lvl+0x1c4/0x2df
[    0.097242]  ? show_trace_log_lvl+0x1c4/0x2df
[    0.097245]  ? __change_page_attr_set_clr+0x4b/0xb0
[    0.097247]  ? __change_page_attr+0x2bf/0x2f0
[    0.097250]  ? __warn+0x81/0x110
[    0.097252]  ? __change_page_attr+0x2bf/0x2f0
[    0.097255]  ? report_bug+0x10a/0x140
[    0.097261]  ? console_unlock+0xec/0x320
[    0.097266]  ? handle_bug+0x3c/0x70
[    0.097273]  ? exc_invalid_op+0x14/0x70
[    0.097274]  ? asm_exc_invalid_op+0x16/0x20
[    0.097279]  ? __change_page_attr+0x2bf/0x2f0
[    0.097282]  ? __change_page_attr+0x2bf/0x2f0
[    0.097285]  __change_page_attr_set_clr+0x4b/0xb0
[    0.097288]  kernel_map_pages_in_pgd+0xcd/0xf9
[    0.097295]  efi_update_mappings+0x36/0x95
[    0.097300]  efi_memattr_apply_permissions+0x226/0x27f
[    0.097304]  ? __pfx_efi_update_mem_attr+0x10/0x10
[    0.097307]  ? efi_free_boot_services+0x231/0x269
[    0.097309]  __efi_enter_virtual_mode+0x1bc/0x1eb
[    0.097312]  efi_enter_virtual_mode+0x34/0x3e
[    0.097314]  start_kernel+0x42b/0x4c2
[    0.097319]  secondary_startup_64_no_verify+0xe5/0xeb
[    0.097324]  </TASK>
[    0.097326] ---[ end trace d9a5f7d4f9c33909 ]---

The hardware name is Hardware name: VMware, Inc. VMware7,1/440BX Desktop Reference Platform, BIOS VMW71.00V.18227214.B64.2106252220 06/25/2021.

ALMA distribution is Linux version 5.14.0-362.13.1.el9_3.x86_64 (mockbuild@x64-builder01.almalinux.org) (gcc (GCC) 11.4.1 20230605 (Red Hat 11.4.1-2), GNU ld version 2.35.2-42.el9) #1 SMP PREEMPT_DYNAMIC Thu Dec 21 07:12:43 EST 2023

Please help me understand if this Call Trace indicates any issues? Or do I need to provide more relevant information for support?

2

What processor do you have in the VM host?

3

This is my processor from dmidecode -t processor command:

Processor Information
	Socket Designation: CPU 0
	Type: Central Processor
	Family: Unknown
	Manufacturer: GenuineIntel
	ID: F0 06 03 00 FF FB 8B 0F
	Version: Intel(R) Xeon(R) Gold 6240R CPU @ 2.40GHz
	Voltage: 3.3 V
	External Clock: Unknown
	Max Speed: 2283 MHz
	Current Speed: 2283 MHz
	Status: Populated, Enabled
	Upgrade: ZIF Socket
	L1 Cache Handle: Not Provided
	L2 Cache Handle: Not Provided
	L3 Cache Handle: Not Provided
	Serial Number: Not Specified
	Asset Tag: Not Specified
	Part Number: Not Specified
	Core Count: 1
	Core Enabled: 1
	Characteristics:
		64-bit capable
		Execute Protection
4

I’d suggest the relevant bits to Google are "asm_exc_invalid_op" AND "__change_page_attr", which yields WARNING: at arch/x86/mm/pat/set_memory.c:626 __change_page_attr() - Red Hat Customer Portal. Does that look like your issue?

5

The Redhat knowledge link is relevant. I read the article through. Our VMware is running a slightly lower version. The document said it requires a higher VMware version 7.0. Will work on patching the VMware first to see if it solves the WARNING issue. Thank you!