Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1684931 - Kernel 4.20.x only: A start job is running for udev wait for Complete Device Initialization [NEEDINFO]
Summary: Kernel 4.20.x only: A start job is running for udev wait for Complete Device ...
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 29
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2019-03-03 21:53 UTC by saif1988
Modified: 2019-04-09 20:44 UTC (History)
16 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed:
labbott: needinfo? (saif1988)

Attachments (Terms of Use)

Description saif1988 2019-03-03 21:53:59 UTC
1. Please describe the problem:
On my two laptops running fedora 29, upgrading to any Linux Kernel 4.20.x causes boot process to hang on this step for about 45 seconds before continuing to normal. Rolling back to previous Kernel 4.19.x doesn't have this issue.

2. What is the Version-Release number of the kernel:
4.20.x. Currently on 4.20.13-200.fc29.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 :
I've tried various 4.20.x but they all have the same problem.

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

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``:
Sorry these are work laptops, I can't risk testing this.

6. Are you 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.
No aparent errors on journalctl -b. Let me know how can I further help.

Comment 1 Laura Abbott 2019-04-09 20:44:11 UTC
We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 29 kernel bugs.
Fedora XX has now been rebased to 5.0.6  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.
If you have moved on to Fedora 30, and are still experiencing this issue, please change the version to Fedora 30.
If you experience different issues, please open a new bug report for those.

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