Bug 1372555

Summary: F25 WS Alpha2 Kernel Displays Redundant Text to Console During Boot
Product: [Fedora] Fedora Reporter: bob <redzilla.coralnut>
Component: systemdAssignee: systemd-maint
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 25CC: dennis, eloranta, gansalmon, ichavero, itamar, johannbg, jonathan, kernel-maint, kevin, lnykryn, madhu.chinakonda, mchehab, msekleta, muadda, ssahani, s, systemd-maint, zbyszek
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-12 10:20:51 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
photo of boot sequence none

Description bob 2016-09-02 04:36:42 UTC
Created attachment 1197046 [details]
photo of boot sequence

Description of problem:

Booting a new bare metal install of F25 Workstation Alpha2, installed from the Live DVD.

During boot, the console output is redundant.  Each message is written to screen twice.  See attached photo.

Version-Release number of selected component (if applicable):

F25 WS Alpha 2

How reproducible:

Boot

Steps to Reproduce:
1. Install to Disk
2. Boot
3.

Actual results:

Redundant status messages displayed on-screen.

Expected results:

No redundancy.

Additional info:

See attached photo.

Comment 1 Josh Boyer 2016-09-02 11:50:37 UTC
None of those are from the kernel.  That is purely userspace.

Comment 2 Kevin Fenzi 2016-09-02 15:59:44 UTC
This looks like a systemd issue?

Comment 3 Jussi Eloranta 2016-12-25 21:48:17 UTC
I am also seeing this after updating from 24 to 25 (not beta/alpha but the actual release). Most of the boot messages appear in double. It has happened on couple of computers but not all of them?! systemctl list-units does not show anything unusual on the affected systems.

Comment 4 Zbigniew Jędrzejewski-Szmek 2017-01-12 00:16:36 UTC
Maybe the kernel console is configured twice. How does /proc/cmdline look?

Comment 5 Jussi Eloranta 2017-01-12 06:08:58 UTC
THis is from a system that shows this problem:

BOOT_IMAGE=/vmlinuz-4.9.2-200.fc25.x86_64 root=/dev/mapper/fedora-root ro rd.lvm
.lv=fedora/root rd.lvm.lv=fedora/swap rhgb quiet LANG=en_US.UTF-8

Comment 6 Fedora End Of Life 2017-11-16 19:51:30 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. 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 '25'.

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 25 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 2017-12-12 10:20:51 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.