linux-kernel - High-resolution timer warning

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <ad74a60a-5c5a-fd48-5177-c6fd11d95e85@gmx.com>
Date:   Sat, 22 Oct 2022 08:42:44 +0800
From:   Qu Wenruo <quwenruo.btrfs@....com>
To:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: High-resolution timer warning

Hi,

Got a hrtimer warning here:

[ 3782.069752] ------------[ cut here ]------------
[ 3782.069760] WARNING: CPU: 0 PID: 0 at kernel/time/hrtimer.c:1713
__hrtimer_run_queues+0x16d/0x2c0
[ 3782.069767] Modules linked in: netconsole rpcsec_gss_krb5 auth_rpcgss
[... skip modules ...]
[ 3782.069875]  pcc_cpufreq():1 [last unloaded: netconsole]
[ 3782.069882] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.0.2-arch1-1
#1 50c0f0880a1bf780734fcafd72b58c22e0d25b99
[ 3782.069887] Hardware name: Micro-Star International Co., Ltd.
MS-7A40/B450I GAMING PLUS AC (MS-7A40), BIOS A.G0 07/25/2022
[ 3782.069889] RIP: 0010:__hrtimer_run_queues+0x16d/0x2c0
[ 3782.069893] Code: 47 38 01 0f 85 46 ff ff ff 31 d2 4c 89 f6 4c 89 ff
e8 f7 fa ff ff 41 83 46 10 01 41 83 46 10 01 4c 39 7b 58 0f 84 39 ff ff
ff <0f> 0b e9 32 ff ff ff 65 8b 05 2d 73 ec 4a 89 c0 48 0f a3 05 2b b5
[ 3782.069897] RSP: 0018:ffffa9e640003f28 EFLAGS: 00010007
[ 3782.069900] RAX: 0000000000000001 RBX: ffff9c819ea24280 RCX:
ffffffffb74ae1c8
[ 3782.069902] RDX: ffffa9e64545bd19 RSI: ffff9c819ea242e0 RDI:
ffff9c819ea24800
[ 3782.069905] RBP: 0000000000000001 R08: 000003707b03c7ae R09:
7fffffffffffffff
[ 3782.070017] R10: 000003707ad0ead9 R11: 000000000000050a R12:
ffff9c819ea24280
[ 3782.070019] R13: 0000000000000006 R14: ffff9c819ea242c0 R15:
ffff9c819ea24800
[ 3782.070021] FS:  0000000000000000(0000) GS:ffff9c819ea00000(0000)
knlGS:0000000000000000
[ 3782.070024] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 3782.070026] CR2: 00007fde07380000 CR3: 00000001503ca000 CR4:
0000000000750ef0
[ 3782.070028] PKRU: 55555554
[ 3782.070030] Call Trace:
[ 3782.070033]  <IRQ>
[ 3782.070092]  hrtimer_interrupt+0xf8/0x210
[ 3782.070095]  __sysvec_apic_timer_interrupt+0x61/0x110
[ 3782.070099]  sysvec_apic_timer_interrupt+0x6d/0x90
[ 3782.070104]  </IRQ>
[ 3782.070106]  <TASK>
[ 3782.070108]  asm_sysvec_apic_timer_interrupt+0x1a/0x20
[ 3782.070111] RIP: 0010:cpuidle_enter_state+0xe2/0x420
[ 3782.070170] Code: 00 00 31 ff e8 6f 0c 7d ff 45 84 ff 74 16 9c 58 0f
1f 40 00 f6 c4 02 0f 85 25 03 00 00 31 ff e8 14 cb 83 ff fb 0f 1f 44 00
00 <45> 85 f6 0f 88 85 01 00 00 49 63 d6 48 8d 04 52 48 8d 04 82 49 8d
[ 3782.070172] RSP: 0018:ffffffffb6c03e40 EFLAGS: 00000246
[ 3782.070175] RAX: ffff9c819ea32d40 RBX: ffff9c7a82273400 RCX:
0000000000000000
[ 3782.070177] RDX: 0000000000000000 RSI: fffffffcf1e429ac RDI:
0000000000000000
[ 3782.070179] RBP: 0000000000000001 R08: 0000000000000002 R09:
00000000229837f7
[ 3782.070181] R10: 00000000000000bf R11: 0000000000000007 R12:
ffffffffb6d4b940
[ 3782.070183] R13: 0000037094ec80f3 R14: 0000000000000001 R15:
0000000000000000
[ 3782.070186]  cpuidle_enter+0x2d/0x40
[ 3782.070189]  do_idle+0x1ed/0x270
[ 3782.070193]  cpu_startup_entry+0x1d/0x20
[ 3782.070195]  rest_init+0xc8/0xd0
[ 3782.070252]  arch_call_rest_init+0xe/0x1c
[ 3782.070257]  start_kernel+0x97a/0x9a3
[ 3782.070260]  secondary_startup_64_no_verify+0xe5/0xeb
[ 3782.070264]  </TASK>
[ 3782.070266] ---[ end trace 0000000000000000 ]---

 From the timestamp, no other related messages around that warning.

The CPU is Ryzen 5900X, no OC or whatever, with 16Gx2 DDR4 3200 RAM.

Recently I'm experiencing a lot of random crash, system hangs, user
space app (mostly proton/wine games) crashs, and have already set up
netconsole to catch the dying message, but to my surprise, no more crash
yet but the above warning caught my eyes.

Is this a known problem related to the specific CPU?
And would it be related to the frequent crash I experienced recently?

Thanks,
Qu