Bug 1965533 - kernel-core 5.12.6-300.fc34 in dnf upgrade --refresh doesn't allow login after reboot
Summary: kernel-core 5.12.6-300.fc34 in dnf upgrade --refresh doesn't allow login afte...
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-27 22:14 UTC by Sathiyamoorthy Kothandan
Modified: 2021-05-28 14:41 UTC (History)
19 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2021-05-28 13:54:42 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Sathiyamoorthy Kothandan 2021-05-27 22:14:27 UTC
1. Please describe the problem:
kernel-core 5.12.6-300.fc34 in dnf upgrade --refresh doesn't allow login after reboot

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

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 :

It works fine in kernel-core-5.11.18-300.fc34.x86_64 and it start appear in kernel-core-5.12.6-300.fc34


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

1) dnf upgrade --refresh
2) reboot
3) at login doesn't allow


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``:

alternative solution(work around)
1) boot through previous working version (5.11.18.300 in this case)
2) dnf history undo <ID> --skip-unavailable
3) dnf upgrade --refresh --exclude=kernel-core
4)reboot
5) login works now


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

NO


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-28 13:54:42 UTC

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

Comment 2 Sathiyamoorthy Kothandan 2021-05-28 14:41:28 UTC
login works fine with kernel-core-5.12.7-300.fc34.x86_64 in "dnf upgrade --refresh", please feel free to close this bug.


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