Description of problem udevd shutting down during boot Version-Release number of selected component (if applicable): kernel-3.12.6-200.fc19.x86_64.debug How reproducible: Tried only once Steps to Reproduce: 1. Boot in single mode 2. journalctl -xb 3. Actual results: Call traces, eventually hangs Expected results: Normal boot Additional info: kernel-3.12.5 boots OK
Created attachment 843901 [details] journalctl -xb output
Created attachment 843902 [details] dmesg output
Created attachment 843903 [details] /var/log/messages
*** Bug 1047564 has been marked as a duplicate of this bug. ***
I think the component should be "kernel", or perhaps "udev". I could not correct that last week because my internet connection was awful.
So nouveau kind of lost its mind with vblank stuff, and then memory allocations started failing. Do you have a dmesg from a boot that works?
*********** MASS BUG UPDATE ************** 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 19 kernel bugs. Fedora 19 has now been rebased to 3.13.5-100.fc19. Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** 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 19 kernel bugs. Fedora 19 has now been rebased to 3.14.4-100.fc19. 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 20, and are still experiencing this issue, please change the version to Fedora 20. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 4 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.