Bug 1644884

Summary: ttyAMA ttyAMA0: tty_open: tty->count(2) != (#fd's(1) + #kopen's(0))
Product: [Fedora] Fedora Reporter: Paul Whalen <pwhalen>
Component: bcm283x-firmwareAssignee: Peter Robinson <pbrobinson>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 29CC: labbott, pbrobinson, pwhalen
Target Milestone: ---   
Target Release: ---   
Hardware: aarch64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-11-17 01:07:14 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:
Bug Depends On:    
Bug Blocks: 1269538    

Description Paul Whalen 2018-10-31 19:43:57 UTC
Description of problem:
When attempting to boot Fedora-IoT-29-20181021.0.aarch64.raw.xz on the Raspberry Pi 3, error messages are repeated during the boot:

[   37.303537] ttyAMA ttyAMA0: tty_open: tty->count(2) != (#fd's(1) + #kopen's(0))
[   37.316886] ttyAMA ttyAMA0: tty_release: tty->count(2) != (#fd's(1) + #kopen's(0))
[   37.347499] ttyAMA ttyAMA0: tty_open: tty->count(2) != (#fd's(1) + #kopen's(0))
[   37.361430] ttyAMA ttyAMA0: tty_release: tty->count(2) != (#fd's(1) + #kopen's(0))
[   37.393199] ttyAMA ttyAMA0: tty_open: tty->count(2) != (#fd's(1) + #kopen's(0))
[   37.407066] ttyAMA ttyAMA0: tty_release: tty->count(2) != (#fd's(1) + #kopen's(0))
[   37.447078] ttyAMA ttyAMA0: tty_open: tty->count(2) != (#fd's(1) + #kopen's(0))


Version-Release number of selected component (if applicable):
bcm283x-firmware-20181009-1.fbad640.fc29

How reproducible:
Most of the time. The system does boot to initial-setup.

Comment 1 Paul Whalen 2018-10-31 19:58:11 UTC
Goes away when all consoles are removed from the kargs, output is correctly displayed on the serial console.

Comment 2 Peter Robinson 2018-11-17 01:07:14 UTC
This was console options conflicting with bluetooth and is now fixed in IoT nightly builds.