You are not logged in.
Hello. Apologies for any errors in advance as I don't generally use forums.
Recently I decided to try out the new 12th Gen processors on Arch. Everything seems to run smoothly while the OS is running, but I've come accross one major difficulty. When restarting, shutting down, or hibernating, the system seems to shut down fine in journalctl, except that right after it stops, I get another screen which seems to be Arch trying to reboot.
Starting version 250-4-arch
/dev/nvme0n1p2: clean, 929682/61038592 files, 89587861/244139185 blocks
[ 1938.285023] watchdog: watchdog0: watchdog did not stop!
Unmounting all devices.
umount: /oldroot/sys: target is busy.
Detaching loop devices.
Disassembling stacked devices.Then the terminal freezes and I have to reset the system. None of this is really a clue to where to look next, however, as the only thing mildly interesting is a famous nvidiea bug where /oldroot/sys doesn't unmount, and is likely not to be the cause of the issue.
Some errors show up in journalctl about broken PMU hardware, but that's kind of to be expected with new hardware, so I don't think that is it either. I've included the error just in case.
Jan 05 12:24:37 archdesktop kernel: hw perf events fixed 5 > max(4), clipping!
Jan 05 12:24:37 archdesktop kernel: WARNING: CPU: 0 PID: 1 at arch/x86/events/intel/core.c:5411 intel_pmu_check_num>
Jan 05 12:24:37 archdesktop kernel: Modules linked in:
Jan 05 12:24:37 archdesktop kernel: CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.15.12-arch1-1 #1 eeb185e1d4b23217f1>
Jan 05 12:24:37 archdesktop kernel: Hardware name: ASUS System Product Name/PRIME Z690-A, BIOS 0811 12/15/2021
Jan 05 12:24:37 archdesktop kernel: RIP: 0010:intel_pmu_check_num_counters+0x65/0x87
Jan 05 12:24:37 archdesktop kernel: Code: 4d 00 b8 01 00 00 00 48 d3 e0 48 ff c8 48 89 03 41 8b 34 24 83 fe 04 7e 1>
Jan 05 12:24:37 archdesktop kernel: RSP: 0000:ffffb5c20006be20 EFLAGS: 00010246
Jan 05 12:24:37 archdesktop kernel: RAX: 0000000000000000 RBX: ffff919a001215d0 RCX: 0000000000000000
Jan 05 12:24:37 archdesktop kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
Jan 05 12:24:37 archdesktop kernel: RBP: 000000000000000f R08: 0000000000000000 R09: 0000000000000000
Jan 05 12:24:37 archdesktop kernel: R10: 0000000000000000 R11: 0000000000000000 R12: ffff919a001215e0
Jan 05 12:24:37 archdesktop kernel: R13: ffff919a001215dc R14: ffffffff95a48218 R15: 0000000000000000
Jan 05 12:24:37 archdesktop kernel: FS: 0000000000000000(0000) GS:ffff91a93fc00000(0000) knlGS:0000000000000000
Jan 05 12:24:37 archdesktop kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jan 05 12:24:37 archdesktop kernel: CR2: ffff91a575a01000 CR3: 0000000c74e10001 CR4: 0000000000770ef0
Jan 05 12:24:37 archdesktop kernel: PKRU: 55555554
Jan 05 12:24:37 archdesktop kernel: Call Trace:
Jan 05 12:24:37 archdesktop kernel: <TASK>
Jan 05 12:24:37 archdesktop kernel: intel_pmu_init+0x1948/0x19dc
Jan 05 12:24:37 archdesktop kernel: ? map_vsyscall+0x6e/0x6e
Jan 05 12:24:37 archdesktop kernel: init_hw_perf_events+0x41/0x5f3
Jan 05 12:24:37 archdesktop kernel: ? map_vsyscall+0x6e/0x6e
Jan 05 12:24:37 archdesktop kernel: do_one_initcall+0x54/0x220
Jan 05 12:24:37 archdesktop kernel: kernel_init_freeable+0xfd/0x23c
Jan 05 12:24:37 archdesktop kernel: ? rest_init+0xd0/0xd0
Jan 05 12:24:37 archdesktop kernel: kernel_init+0x16/0x130
Jan 05 12:24:37 archdesktop kernel: ret_from_fork+0x1f/0x30
Jan 05 12:24:37 archdesktop kernel: </TASK>
Jan 05 12:24:37 archdesktop kernel: ---[ end trace ce7ee8ebcb239f40 ]---
Jan 05 12:24:37 archdesktop kernel: Intel PMU driver.
Jan 05 12:24:37 archdesktop kernel: Broken PMU hardware detected, using software events only.
Jan 05 12:24:37 archdesktop kernel: Failed to access perfctr msr (MSR 18e is ffffffffffffffff) Using journalctl I kind of confirmed my findings, that the system shuts down fine from the OS's perspective. There is however a string of hardware errors from the last boot:
Jan 05 12:24:37 archdesktop kernel: BERT: Error records from previous boot:
Jan 05 12:24:37 archdesktop kernel: [Hardware Error]: event severity: fatal
Jan 05 12:24:37 archdesktop kernel: [Hardware Error]: Error 0, type: fatal
Jan 05 12:24:37 archdesktop kernel: [Hardware Error]: section_type: Firmware Error Record Reference
Jan 05 12:24:37 archdesktop kernel: [Hardware Error]: Firmware Error Record Type: SOC Firmware Error Record Type2
Jan 05 12:24:37 archdesktop kernel: [Hardware Error]: Revision: 2
Jan 05 12:24:37 archdesktop kernel: [Hardware Error]: Record Identifier: 8f87f311-c998-4d9e-a0c4-6065518c4f6dAfter that is a hex dump. Searching around has only lead me to people who experienced similar issues mostly with hardware faults, but to my knowledge, the system I am running on is known good with no issues otherwise. There's no system instability during the system running, which is where other people were having issues with, mostly with their kernel hanging during boot.
Here's a pastebin of my entire journalctil -k -b -1
https://pastebin.com/fFD48y6V
The system is a Intel 12700KF with efficiency cores turned off in the bios (wanted to avoid scheduler issues, no apparent change to this issue with them on) running Arch Linux 5.15.12-arch1-1 with 64GB of DDR5. Any help would be appreciated, and I hope I provided enough information. Thanks!
Last edited by koznyshev (2022-01-11 22:57:48)
Offline
Updated my system today after a couple days away, and it seems whatever changed fixed the issue.
Offline