Bug 1328229 - Dracut hangs on 4.4.6 kernels after "started pre-pivot and cleanup hook"
Summary: Dracut hangs on 4.4.6 kernels after "started pre-pivot and cleanup hook"
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 23
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-18 19:06 UTC by Wouter De Borger
Modified: 2016-12-20 20:01 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-12-20 20:01:19 UTC
Type: Bug


Attachments (Terms of Use)
config files (40.00 KB, application/x-tar)
2016-04-18 19:06 UTC, Wouter De Borger
no flags Details
Screenshot of dracut output (3.98 MB, image/jpeg)
2016-04-18 19:07 UTC, Wouter De Borger
no flags Details
systemd log (1.24 MB, image/jpeg)
2016-04-23 08:15 UTC, Wouter De Borger
no flags Details

Description Wouter De Borger 2016-04-18 19:06:52 UTC
Created attachment 1148271 [details]
config files

Description of problem:

After a kernel upgrade from 4.3.5-300 to 4.4.6-300 or 4.4.6-301 the boot process hangs at "started pre-pivot and cleanup hook"

My machine uses LVM on software raid.

The 4.3.5-300 kernel still boots without problems.

I will attach all information requested in https://fedoraproject.org/wiki/How_to_debug_Dracut_problems

I don't have a dump of the kernel output (can't get a shell), but I have a picture of my screen. (If anyone can instruct me on how to get it, I would be happy to try)

Comment 1 Wouter De Borger 2016-04-18 19:07:53 UTC
Created attachment 1148272 [details]
Screenshot of dracut output

Comment 2 Harald Hoyer 2016-04-20 08:32:09 UTC
(In reply to Wouter De Borger from comment #1)
> Created attachment 1148272 [details]
> Screenshot of dracut output

looks all good from the dracut side of things.

I would add debug parameters for systemd on the kernel command line:

"systemd.log_target=console systemd.log_level=debug"

Comment 3 Wouter De Borger 2016-04-23 08:15:49 UTC
Created attachment 1149971 [details]
systemd log

Comment 4 Wouter De Borger 2016-04-23 08:16:50 UTC
Thank you for looking into this, I added the requested logs.

Comment 5 Harald Hoyer 2016-08-22 09:14:26 UTC
Hmm, I see

"Failed to remove source manager-ask-password from epoll"

reassigning to systemd.

Comment 6 Fedora End Of Life 2016-11-25 07:23:38 UTC
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 7 Fedora End Of Life 2016-12-20 20:01:19 UTC
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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