Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1946989 - f34 kernel hangs while starting LVM volumes at boot time
Summary: f34 kernel hangs while starting LVM volumes at boot time
Keywords:
Status: CLOSED DUPLICATE of bug 1945596
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-04-07 12:46 UTC by Jeff Layton
Modified: 2021-04-07 14:33 UTC (History)
19 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-04-07 14:33:36 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jeff Layton 2021-04-07 12:46:42 UTC
1. Please describe the problem:

    After f33->f34 upgrade, laptop hangs while starting LVM volumes when I boot to the f34 kernel. It hangs with the message:

    "A start job is running for /dev/mapper/fedora_localhost--live-root" (and also for fedora_localhost--live-swap).

    I let it run for 10 mins or so and it never got past that point. If I boot to the previously installed f33 kernel (which is also v5.11.11), then it comes up fine.

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

    kernel-5.11.11-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 :

    Yes. I've upgraded fedora on this laptop several times, and have never had a problem. If I boot to this kernel:

    kernel-5.11.11-200.fc33.x86_64

    ...then it works fine.

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

    Yes. It happens every time

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

   Yes. Looks like the same problem manifests on the rawhide kernel (5.12.0-0.rc6.184.fc35.x86_64)

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.

    The problem occurs before it starts logging to the journal. I can attach the log from a successful boot, but that probably won't demonstrate the issue. Let me know if you need it.

Comment 1 Justin M. Forbes 2021-04-07 14:33:36 UTC

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


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