Arch Linux

vecino

Member

Registered: 2022-12-10

Posts: 139

[SOLVED] 6.1.1-arch1-1 - dmesg

Hi, everything works for me ... today I switched to a new kernel 6.1.1 and in dmesg I see a new message for me that I don't understand. It's OK? Thanks

[    5.894832] ------------[ cut here ]------------
[    5.894887] memcpy: detected field-spanning write (size 32) of single field "&device->entry" at drivers/firmware/google/coreboot_table.c:104 (size 8)
[    5.894954] WARNING: CPU: 2 PID: 245 at drivers/firmware/google/coreboot_table.c:104 coreboot_table_probe+0x1ba/0x1e2 [coreboot_table]
[    5.894988] Modules linked in: pcc_cpufreq(-) coreboot_table(+) acpi_cpufreq mac_hid fuse bpf_preload ext4 crc32c_generic crc16 mbcache jbd2 sdhci_pci cqhci sdhci xhci_pci mmc_core crc32c_intel xhci_pci_renesas
[    5.895055] CPU: 2 PID: 245 Comm: systemd-udevd Not tainted 6.1.1-arch1-1 #1 9bd09188b430be630e611f984454e4f3c489be77
[    5.895098] Hardware name: PC Engines apu2/apu2, BIOS v4.17.0.3 08/22/2022
[    5.895104] RIP: 0010:coreboot_table_probe+0x1ba/0x1e2 [coreboot_table]
[    5.895153] Code: 08 00 00 00 48 89 c6 48 89 04 24 48 c7 c2 00 31 54 c0 48 c7 c7 48 31 54 c0 4c 89 44 24 08 c6 05 f3 1e 00 00 01 e8 b1 11 c8 cd <0f> 0b 4c 8b 44 24 08 48 8b 04 24 e9 71 ff ff ff 41 bf ea ff ff ff
[    5.895162] RSP: 0018:ffffafd300617c20 EFLAGS: 00010286
[    5.895172] RAX: 0000000000000000 RBX: ffff8a9105112400 RCX: 0000000000000027
[    5.895178] RDX: ffff8a917cd21668 RSI: 0000000000000001 RDI: ffff8a917cd21660
[    5.895184] RBP: ffffafd3000bd018 R08: 0000000000000000 R09: ffffafd300617aa8
[    5.895190] R10: 0000000000000003 R11: ffffffff8f4cb768 R12: 0000000000000000
[    5.895195] R13: ffffafd3000bd000 R14: ffff8a9101251810 R15: 0000000000000000
[    5.895201] FS:  00007f5924c28080(0000) GS:ffff8a917cd00000(0000) knlGS:0000000000000000
[    5.895237] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[    5.895243] CR2: 00007f59257f3930 CR3: 0000000001948000 CR4: 00000000000406e0
[    5.895251] Call Trace:
[    5.895261]  <TASK>
[    5.895276]  platform_probe+0x48/0x90
[    5.895297]  really_probe+0xde/0x380
[    5.895311]  ? pm_runtime_barrier+0x54/0x90
[    5.895326]  __driver_probe_device+0x78/0x170
[    5.895369]  driver_probe_device+0x1f/0x90
[    5.895383]  __driver_attach+0xd5/0x1d0
[    5.895424]  ? __device_attach_driver+0x110/0x110
[    5.895437]  bus_for_each_dev+0x8b/0xd0
[    5.895451]  bus_add_driver+0x1b2/0x200
[    5.895468]  driver_register+0x8d/0xe0
[    5.895482]  coreboot_table_driver_init+0x2f/0x1000 [coreboot_table 88ba60255f1ecf81d7bd02d65b11614bb24acd8e]
[    5.895506]  ? 0xffffffffc0547000
[    5.895518]  do_one_initcall+0x5d/0x220
[    5.895568]  do_init_module+0x4a/0x1e0
[    5.895644]  __do_sys_init_module+0x17f/0x1b0
[    5.895668]  do_syscall_64+0x5f/0x90
[    5.895706]  entry_SYSCALL_64_after_hwframe+0x63/0xcd
[    5.895763] RIP: 0033:0x7f5925721eae
[    5.895773] Code: 48 8b 0d dd ee 0c 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d aa ee 0c 00 f7 d8 64 89 01 48
[    5.895809] RSP: 002b:00007ffe23ab2138 EFLAGS: 00000246 ORIG_RAX: 00000000000000af
[    5.895819] RAX: ffffffffffffffda RBX: 000055de69898540 RCX: 00007f5925721eae
[    5.895825] RDX: 00007f5925beb343 RSI: 0000000000003eb7 RDI: 00007f5923d03010
[    5.895830] RBP: 00007f5925beb343 R08: 27d4eb2f165667c5 R09: 85ebca77c2b2ae63
[    5.895835] R10: 00000000000010f1 R11: 0000000000000246 R12: 0000000000020000
[    5.895841] R13: 000055de698ca160 R14: 000055de69898540 R15: 000055de69887e50
[    5.895884]  </TASK>
[    5.895887] ---[ end trace 0000000000000000 ]---

Last edited by vecino (2023-03-02 14:48:19)

xerxes_

Member

Registered: 2018-04-29

Posts: 780

Re: [SOLVED] 6.1.1-arch1-1 - dmesg

No, it's not OK as any 'Call Trace' is not good.
It looks for me as some errors related with coreboot_table (values?) confuses new kernel, something might be related to acpi and cpu frequency scalling, but if you don't experience any hang, freeze, instability or any unexpected behavior with system I would ignore it for now, but observe logs and how your system behave.
For curiosity: did you flash your UEFI  motherboard with coreboot?

Last edited by xerxes_ (2022-12-22 21:37:28)

vecino

Member

Registered: 2022-12-10

Posts: 139

Re: [SOLVED] 6.1.1-arch1-1 - dmesg

So far I haven't had any problems - I have it as a router. I don't use UEFI. PC Engines apu2 with BIOS v4.17.0.3.

chr0mag

Member

From: Vancouver, Canada

Registered: 2017-02-02

Posts: 94

Re: [SOLVED] 6.1.1-arch1-1 - dmesg

I've been seeing the same thing on my APU2C4 since moving to 6.x kernels. I finally got around to logging a bug upstream today: https://github.com/pcengines/apu2-docum … issues/316 .

I haven't noticed any instability or other issues.

vecino

Member

Registered: 2022-12-10

Posts: 139

Re: [SOLVED] 6.1.1-arch1-1 - dmesg

Thanks for that. Bios development for APU has somehow stopped recently - https://pcengines.github.io/#mr-61 (last release date from 2022-07-29). I believe they will fix it.

Last edited by vecino (2023-01-02 15:12:45)

vecino

Member

Registered: 2022-12-10

Posts: 139

Re: [SOLVED] 6.1.1-arch1-1 - dmesg

With last BIOS v4.19.0.1 + kernel 6.1 / 6.2 are call trace gone.

https://pcengines.github.io/#mr-63