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.
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.