Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 1170412

Summary: lorax should not specify a console= parameter on aarch64 hosts
Product: [Fedora] Fedora Reporter: Brendan Conoboy <blc>
Component: loraxAssignee: Brian Lane <bcl>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 21CC: anaconda-maint-list, bcl, pbrobinson
Target Milestone: ---Flags: bcl: needinfo?
Target Release: ---   
Hardware: aarch64   
OS: Unspecified   
Whiteboard:
Fixed In Version: lorax-21.33-1.fc21 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1170413 (view as bug list) Environment:
Last Closed: 2015-01-14 23:57:01 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:
Embargoed:
Bug Depends On:    
Bug Blocks: 922257, 1170413    
Attachments:
Description Flags
patch none

Description Brendan Conoboy 2014-12-04 02:43:08 UTC 
Description of problem:

As of version 3.17 the kernel is able to decide which console to use based on the device tree or ACPI table content.  Currently live media creator will always insert 'console=ttyS0,115200' into the kernel command line in the aarch64 template.  Since some aarch64 devices don't use ttyS0, this limits compatibility.  It is better to leave off any console, earlyprintk, or earlycon parameters entirely.

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

The version of lorax used in the fc21_rc1 compose exhibits this behavior.

How reproducible:

Happens every time.  Example configuration from fc21_rc1:

http://arm.koji.fedoraproject.org/compose/f21_RC1/21/Server/aarch64/os/EFI/BOOT/grub.cfg
Comment 1 Peter Robinson 2014-12-04 10:37:48 UTC 
There's now RC5 which was composed with 21.30-1 vs 21.24-1 of RC1, not sure if that would make a difference but it would be good to double check

http://arm.koji.fedoraproject.org/compose/21_RC5/
Comment 2 Brian Lane 2014-12-04 17:42:29 UTC 
Created attachment 964778 [details]
patch

If someone could test this patch with the correct kernel that would be great.
Comment 3 Fedora Update System 2014-12-05 22:28:27 UTC 
lorax-21.32-1.fc21 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/lorax-21.32-1.fc21
Comment 4 Fedora Update System 2014-12-06 10:24:32 UTC 
Package lorax-21.32-1.fc21:
* should fix your issue,
* was pushed to the Fedora 21 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing lorax-21.32-1.fc21'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-16415/lorax-21.32-1.fc21
then log in and leave karma (feedback).
Comment 5 Brian Lane 2014-12-09 00:43:08 UTC 
dmarlin asked about removing these lines from the config:

-serial --speed=115200
-terminal_input serial console
-terminal_output serial console


Should those have been left in? Can someone with access to the various systems confirm that it is ok to remove them?
Comment 6 Fedora Update System 2014-12-13 00:43:24 UTC 
lorax-21.33-1.fc21 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/lorax-21.33-1.fc21
Comment 7 Fedora Update System 2015-01-14 23:57:01 UTC 
lorax-21.33-1.fc21 has been pushed to the Fedora 21 stable repository.  If problems still persist, please make note of it in this bug report.