Bug 1996302

Summary: System freezes after kernel OOPS in locks_free_lock_context
Product: [Fedora] Fedora Reporter: Alexander Zuev <a2leexx>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 34CC: acaringi, adscvr, airlied, alciregi, bskeggs, hdegoede, jarodwilson, jeremy, jglisse, jonathan, josef, kernel-maint, lgoncalv, linville, masami256, mchehab, ptalbert, steved
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-10-21 16:50:26 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
journalctl --no-hostname -k none

Description Alexander Zuev 2021-08-21 17:30:39 UTC
Created attachment 1816357 [details]
journalctl --no-hostname -k

1. Please describe the problem:

My laptop suddenly freezes after kernel OOPS. I can't even login via VT (but REISUB key combination works). This usually happens once every 4-10 days.

2. What is the Version-Release number of the kernel:

5.13.10

3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  

The first time the problem appeared in the kernel 5.13.4. 

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:

I can't reproduce this issue. But usually it occurs during launching some program (Firefox, Spyder and etc.)

Comment 1 Alexander Zuev 2021-08-25 20:01:42 UTC
I want to clarify that I have not used third-party modules with the 5.13.10 kernel and there was hang when using the 5.13.12 kernel (the latest kernel at moment of writing this comment, also without third-party modules).

Comment 2 Alexander Zuev 2021-10-21 16:48:24 UTC
It looks like the bug has been fixed in the 5.13.13 kernel. I haven't encountered this issue for almost two months.