Bug 1996302 - System freezes after kernel OOPS in locks_free_lock_context
Summary: System freezes after kernel OOPS in locks_free_lock_context
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 34
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-08-21 17:30 UTC by Alexander Zuev
Modified: 2021-10-21 16:50 UTC (History)
18 users (show)

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-10-21 16:50:26 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
journalctl --no-hostname -k (168.34 KB, text/plain)
2021-08-21 17:30 UTC, Alexander Zuev
no flags Details

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.


Note You need to log in before you can comment on or make changes to this bug.