Bug 1394446

Summary:	boot hangs if USB keyboard or mouse is attached
Product:	[Fedora] Fedora	Reporter:	todd_lewis
Component:	arm-boot-config	Assignee:	Brendan Conoboy <blc>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	26	CC:	blc, dennis
Target Milestone:	---
Target Release:	---
Hardware:	armv7hl
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-05-29 11:32:19 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:

Description todd_lewis 2016-11-12 01:17:11 UTC

Description of problem: Raspberry pi 3 boot hangs at "scanning bus 0 for devices..." in rpi3-u-boot.bin if USB keyboard or mouse is attached.


Version-Release number of selected component (if applicable):
Several of the nightly builds, up to the most recent I tried: Fedora-Mate-armhfp-25-20161108.n.1-sda.raw.xz


How reproducible: Always


Steps to Reproduce:
1. Install as per docs
2. Attempt to boot
3.

Actual results:
"Net:   Net Initialization Skipped
 No ethernet found.
 starting USB...
 USB0:   Core Release 2.80a
 scanning bus 0 for devices..."
[no further output]

Expected results:
The rest of the boot.

Additional info: Unplugging the USB keyboard and mouse before applying power gets past this point. Once past the "scanning bus 0" message, plugging them back in allows the system to function normally.

Also, this same pi3 boots without issue using the raspian distribution, so I'm sure it isn't a hardware issue. It was also working with the Fedora 24 distro on the raspian kernel before that, but I'm hoping for an all-Fedora solution.

Comment 1 Fedora End Of Life 2017-02-28 10:36:12 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle.
Changing version to '26'.

Comment 2 Fedora End Of Life 2018-05-03 08:20:56 UTC

This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. 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 '26'.

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 26 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 3 Fedora End Of Life 2018-05-29 11:32:19 UTC

Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
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.