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 1951694

Summary: boot hangs with usb keyboard plugged in
Product: [Fedora] Fedora Reporter: Paul Whalen <pwhalen>
Component: uboot-toolsAssignee: Peter Robinson <pbrobinson>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 34CC: awilliam, dan, dennis, jan.public, jean, nrevo, ole.d, pasik, pbrobinson, robatino
Target Milestone: ---   
Target Release: ---   
Hardware: armv7l   
OS: Linux   
Whiteboard: AcceptedBlocker
Fixed In Version: uboot-tools-2021.04-2.fc34 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-04-22 14:53:41 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: 245418, 1829024    

Description Paul Whalen 2021-04-20 18:39:57 UTC
Description of problem:

Attempting to boot an armv7 SBC fails with a usb device plugged in. 

Version-Release number of selected component (if applicable):
uboot-tools-2021.04-1.fc34

How reproducible:
Every time

Steps to Reproduce:
1. Attempt to boot a recent armv7 disk image with usb plugged in
2. System hangs after printing the efi stub messages:

EFI stub: Entering in HYP mode with MMU enabled
EFI stub: Booting Linux Kernel...
EFI stub: Using DTB from configuration table
EFI stub: Exiting boot services and installing virtual address map...

Additional info:

Plugging in the USB device after booting works ok.

Comment 1 Paul Whalen 2021-04-20 18:53:33 UTC
Nominating as a blocker for F34 GA, criteria - "All release-blocking images must boot in their supported configurations." This affects the minimal armhfp disk image when a USB input device is plugged in on boot.

Comment 2 Peter Robinson 2021-04-20 19:58:19 UTC
> Attempting to boot an armv7 SBC fails with a usb device plugged in. 

Please be specific, a Raspberry Pi 2/3 which has onboard USB devices, and a number of aarch64 devices with USB devices attached work fine (I've tested RPi2/3/400, Pinebook Pro, Rock960, and others with various USB devices attached with my testing.

Comment 3 Paul Whalen 2021-04-20 20:08:07 UTC
(In reply to Peter Robinson from comment #2)
> > Attempting to boot an armv7 SBC fails with a usb device plugged in. 
> 
> Please be specific, a Raspberry Pi 2/3 which has onboard USB devices, and a
> number of aarch64 devices with USB devices attached work fine (I've tested
> RPi2/3/400, Pinebook Pro, Rock960, and others with various USB devices
> attached with my testing.

Tested Rpi2/3 and the Cubietruck, all hang with a USB keyboard plugged in. Booting with a USB drive plugged in worked ok.

Comment 4 Paul Whalen 2021-04-20 20:44:11 UTC
Working with uboot-tools-2021.04-0.3.rc2.fc34. Not working in rc3.

Comment 5 Adam Williamson 2021-04-21 15:25:14 UTC
+3 in https://pagure.io/fedora-qa/blocker-review/issue/367 , marking accepted.

Comment 6 Fedora Update System 2021-04-21 18:20:40 UTC
FEDORA-2021-6b01add75e has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-6b01add75e

Comment 7 Fedora Update System 2021-04-21 18:20:48 UTC
FEDORA-2021-6b01add75e has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-6b01add75e

Comment 8 Fedora Update System 2021-04-22 14:53:41 UTC
FEDORA-2021-6b01add75e has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.