FS#70296 - Random freeze with 5.11.x kernels

Attached to Project: Arch Linux
Opened by DDW (downloader03) - Monday, 05 April 2021, 11:09 GMT
Last edited by Toolybird (Toolybird) - Sunday, 04 June 2023, 03:40 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Jan Alexander Steffens (heftig)
Architecture x86_64
Severity Critical
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:
On 5.11 kernel series, there is occasionally random hard freeze , needs hard reset.
Hardware is fully tested under windows and all of them are fully healthy.
No freeze under 5.10 kernel series.

Additional info:
* package version(s) :
Arch Linux
Kernel : 5.11.11
CPU : Intel Haswell G3250
RAM : DDR3 8GB
MB : Gigabytes H81M-S2PV
GPU : Radeon HD 4650

* link to upstream bug report, if any :
https://bugzilla.kernel.org/show_bug.cgi?id=212087
https://bugzilla.kernel.org/show_bug.cgi?id=212543

* config and/or log files etc. :
Log from 5.11.11:
Apr 4 15:47:20 xxx kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 3: be00000000800400
Apr 4 15:47:20 xxx kernel: mce: [Hardware Error]: TSC 0 ADDR ffffffffc07e06cc MISC ffffffffc07e06cc
Apr 4 15:47:20 xxx kernel: mce: [Hardware Error]: PROCESSOR 0:306c3 TIME 1617535033 SOCKET 0 APIC 0 microcode 28

Apr 4 15:47:20 xxx kernel: mce: [Hardware Error]: CPU 1: Machine Check: 0 Bank 3: be00000000800400
Apr 4 15:47:20 xxx kernel: mce: [Hardware Error]: TSC 0 ADDR ffffffffc0e4b269 MISC ffffffffc0e4b269
Apr 4 15:47:20 xxx kernel: mce: [Hardware Error]: PROCESSOR 0:306c3 TIME 1617535033 SOCKET 0 APIC 2 microcode 28

Steps to reproduce:
It occurs automatically without any specific symptom or notice.
This task depends upon

Closed by  Toolybird (Toolybird)
Sunday, 04 June 2023, 03:40 GMT
Reason for closing:  Upstream
Additional comments about closing:  Clearly an upstream issue. If still happening, please report upstream to the kernel folks.
Comment by Konstantinos Charitakis (Alopex) - Tuesday, 06 April 2021, 07:42 GMT
I've seen loads of problems in 1.11 caused by GPUs, only those made my AMD and if I'm not mistaken you have one, maybe downgrade to 1.10 or hop on the LTS release
Comment by Magnus (DeArchDev) - Sunday, 09 January 2022, 14:21 GMT
You can try upgrading to the stable kernel(5.15) or LTS(5.10) and if this is a upstream bug(I'm saying this as you have linked the upstream bug in the description), then you should probably not file an issue in archlinux's bugs page as the arch team can't do anything about it due to it being upstream. If you want to discuss about your issue and find fixes related to it, I recommend posting it in the arch forums

Loading...