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
Bug 1594402 - aarch64 kernel has CONFIG_CMDLINE="console=ttyAMA0", unlike other arches, should probably be removed
Summary: aarch64 kernel has CONFIG_CMDLINE="console=ttyAMA0", unlike other arches, sho...
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: rawhide
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Peter Robinson
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: ARMTracker
TreeView+ depends on / blocked
Reported: 2018-06-22 20:45 UTC by Adam Williamson
Modified: 2019-05-14 01:52 UTC (History)
19 users (show)

Fixed In Version: 4.18.0-0.rc2.git1.1.fc29.aarch64
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2018-06-25 23:17:55 UTC
Type: Bug

Attachments (Terms of Use)

Description Adam Williamson 2018-06-22 20:45:29 UTC
This is kind of an offshoot of . One thing I figured out while investigating that bug is that the Fedora aarch64 kernel builds have this in their kernel config:


that's not done for any other arch (not even armv7hl) - only aarch64. It basically 'bakes' console=ttyAMA0 into the cmdline on any boot of a Fedora aarch64 kernel. You can specify *additional* consoles, but you can never *not* have a console on ttyAMA0.

This has various consequences. Not least, it means that if an aarch64 system actually has both a 'real' display and a serial console on ttyAMA0 - e.g. a typical aarch64 VM - you will not get plymouth displayed on its physical display unless you manually add 'console=tty0' to its boot parameters, due to details of how plymouth works. plymouth will only show up on the serial console.

pbrobinson and pwhalen seem to be of the opinion that this was basically an ugly hack from the early early days and it should probably go away now, so I'm filing this bug to make sure this isn't forgotten.

I also happened to notice a small inconsistency between the other arches here. Other arm arch configs (armv7hl, armv7hl-debug, armv7hl-lpae, armv7hl-lpae-debug) have CONFIG_CMDLINE="" , but all the other arches do not mention it at all (not even an 'is not set' line). I'm not sure if this is significant, just thought I'd mention it.

Comment 1 Peter Robinson 2018-06-23 10:56:49 UTC
I'm looking at this.

Comment 2 Peter Robinson 2018-06-25 16:56:52 UTC
I've pushed this, it'll be in the rc2 build, I've not tested as much as I'd have liked due to dealing with other issues so we'll see how we get on with this.

Comment 3 Adam Williamson 2018-06-25 16:58:40 UTC

Comment 4 Peter Robinson 2018-06-25 23:17:55 UTC
So looks fine via serial console on:
* mustang
* Pine64
* Dragonboard 410c

Boot tested on Raspberry Pi 3B+ but not tested serial console but it's not ttyAMA0 anyway.

Config looks fine:
$ grep CONFIG_CMDLINE /boot/config-4.18.0-0.rc2.git1.1.fc29.aarch64 

So I think this should be all good, kernel should be in tomorrow's compose

Comment 5 Adam Williamson 2018-06-25 23:32:30 UTC
thanks, now I guess I get to take all those workarounds I wrote into openqa tests back out again :)

Comment 6 Adam Williamson 2019-03-29 22:17:40 UTC
So, it seems that that actually does not do the trick. See , which goes a long way around the houses, but eventually works out that, right after I took the workaround out of the openQA tests (the 'workaround' is to pass 'console=tty0' on the cmdline), this broke again - aarch64 tests stopped seeing boot messages. Somehow I forgot about this whole thing, though, and wasted a bunch of time trying to figure out why.

For now I'm going to put the workaround back in the openQA tests.

Comment 7 Hans de Goede 2019-03-30 11:36:17 UTC
Is the qemu based vm on which openQA is running perhaps using devicetree rather then UEFI ?  In devicetree it is possible the indicate the prefered/defailt console= value by setting stdout-path in the chosen node in devicetree:

Doing a "grep -R stdout-path arch/arm64/boot/dts" in the kernel tree shows that most
dts files define stdout-path and point this to the serial0 or serial1 alias.

Comment 8 Adam Williamson 2019-03-31 00:35:39 UTC
No, it's UEFI.

Comment 9 Hans de Goede 2019-03-31 07:43:07 UTC
(In reply to Adam Williamson from comment #8)
> No, it's UEFI.

Well could still be something similar, ACPI tables can embed devicetree-data and on aarch64 this is sometimes being used AFAIK.

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