Bug 1963797 - kernel BUG at lib/list_debug.c:51!
Summary: kernel BUG at lib/list_debug.c:51!
Keywords:
Status: CLOSED DUPLICATE of bug 1963782
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 34
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-05-24 05:13 UTC by cornel panceac
Modified: 2021-05-24 22:29 UTC (History)
19 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2021-05-24 22:29:23 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
crash log (6.67 KB, text/plain)
2021-05-24 05:13 UTC, cornel panceac
no flags Details

Description cornel panceac 2021-05-24 05:13:55 UTC
Created attachment 1786264 [details]
crash log

1. Please describe the problem:
kernel crashes when trying to login in GDM

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

5.12.5-300.fc34.x86_64 

3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :

GDM login works fine with the kernel from Fedora 33 ( 5.11.21-200.fc33.x86_64 ) .

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

yes

- start Fedora 34
- press enter to login on currently selected user

At this point the crash happens (i never reach the point where i can enter password, or select a different GUI session like XFCE).


5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:
-N/A

6. Are you running any modules that not shipped with directly Fedora's kernel?:

As far as i know i am not running any modules that not shipped with directly Fedora's kernel.

7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.

Comment 1 Justin M. Forbes 2021-05-24 22:29:23 UTC

*** This bug has been marked as a duplicate of bug 1963782 ***


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