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 1700856 - data abort in U-Boot when attempting to boot Allwinner A20 SBC's from SATA
Summary: data abort in U-Boot when attempting to boot Allwinner A20 SBC's from SATA
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: uboot-tools
Version: 30
Hardware: armhfp
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Peter Robinson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: AcceptedBlocker
Depends On:
Blocks: F30FinalBlocker
TreeView+ depends on / blocked
 
Reported: 2019-04-17 13:40 UTC by Paul Whalen
Modified: 2019-04-23 23:44 UTC (History)
7 users (show)

Fixed In Version: uboot-tools-2019.04-1.fc30
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-04-23 23:44:05 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Paul Whalen 2019-04-17 13:40:24 UTC 
Description of problem:
Attempting to boot Allwinner A20 based SBC's from SATA disk results in a data abort in uboot.

Version-Release number of selected component (if applicable):
U-Boot 2019.04-rcX

How reproducible:
Every time, tested on Banana Pi and Cubietruck. 

Actual results:
U-Boot 2019.04-rc4 (Mar 20 2019 - 15:48:13 +0000) Allwinner Technology

CPU:   Allwinner A20 (SUN7I)
Model: Cubietech Cubietruck
I2C:   ready
DRAM:  2 GiB
MMC:   mmc@1c0f000: 0, mmc@1c12000: 1
Loading Environment from FAT... ** No valid partitions found **
Setting up a 1024x768 vga console (overscan 0x0)
In:    serial
Out:   vga
Err:   vga
Allwinner mUSB OTG (Peripheral)
SCSI:  Target spinup took 0 ms.
AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl SATA mode
flags: ncq stag pm led clo only pmp pio slum part ccc apst 

Net:   sunxi_set_gate: (CLK#66) unhandled
eth0: ethernet@1c50000
Warning: usb_ether using MAC address from ROM
, eth1: usb_ether
starting USB...
USB0:   USB EHCI 1.00
USB1:   USB OHCI 1.0
USB2:   USB EHCI 1.00
USB3:   USB OHCI 1.0
scanning bus 0 for devices... 1 USB Device(s) found
scanning bus 1 for devices... 1 USB Device(s) found
scanning bus 2 for devices... 1 USB Device(s) found
scanning bus 3 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot:  0 
switch to partitions #0, OK
mmc0 is current device
** Invalid partition 1 **
scanning bus for devices...
data abort
pc : [<bef8b82a>]          lr : [<bef86e51>]
reloc pc : [<4a01c82a>]    lr : [<4a017e51>]
sp : baf46510  ip : 0000001c     fp : 000000c0
r10: 00000000  r9 : baf4eed8     r8 : 00000000
r7 : baf46790  r6 : befd4094     r5 : befdbd30  r4 : befdbd30
r3 : 00000000  r2 : 00000000     r1 : ea000016  r0 : befdbd30
Flags: nZcv  IRQs off  FIQs off  Mode SVC_32
Code: e92dbd10 f8d045f0 b0858080 1000f8d8 (f8d14604) 
Resetting CPU ...

resetting ...


Additional info:
Working with mmc boot.
Comment 1 Fedora Update System 2019-04-18 22:41:32 UTC 
arm-image-installer-2.12-1.fc30 uboot-tools-2019.04-1.fc30 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-71dc167df7
Comment 2 Fedora Blocker Bugs Application 2019-04-18 22:43:38 UTC 
Proposed as a Blocker for 30-final by Fedora user pbrobinson using the blocker tracking app because:

 The U-Boot 2019.04 GA release.

There's fixes for a number of devices we support on ARMv7/aarch64 inclduing AllWinner, Tegra and i.MX6 devices.
Comment 3 Zbigniew Jędrzejewski-Szmek 2019-04-19 08:31:38 UTC 
Dunno, it's a pretty big change to do at this stage. v2019.01..v2019.04 is 1193 commits.
Comment 4 Peter Robinson 2019-04-19 12:34:10 UTC 
(In reply to Zbigniew Jędrzejewski-Szmek from comment #3)
> Dunno, it's a pretty big change to do at this stage. v2019.01..v2019.04 is
> 1193 commits.

We're already shipping 2019.04-rc4 if you actually look at what's tagged in F-30, this is just going from the very last rc of 2019.04 to the GA release. It has a bunch of fixes for a number of devices. So it's not 1193 commits at all!!
Comment 5 Fedora Update System 2019-04-19 15:54:34 UTC 
arm-image-installer-2.12-1.fc30, uboot-tools-2019.04-1.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-71dc167df7
Comment 6 Zbigniew Jędrzejewski-Szmek 2019-04-20 07:45:59 UTC 
Ah, OK, in dist-git it's just a few patches.

+1 blocker
Comment 7 Peter Robinson 2019-04-20 08:11:29 UTC 
(In reply to Zbigniew Jędrzejewski-Szmek from comment #6)
> Ah, OK, in dist-git it's just a few patches.

Yep, I'm not (completely) insane ;-) It would have landed before freeze but I was on PTO completely away from internets so it was a little delayed than my usual planning and it fixes a few nasty issues with supported devices.
Comment 8 Geoffrey Marr 2019-04-22 17:47:25 UTC 
Discussed during the 2019-04-22 blocker review meeting: [1]

The decision to classify this bug as an "AcceptedBlocker" was made as it violates the following criteria:

"All release-blocking images must boot in their supported configurations. ... Supported ARM platforms are those listed by the ARM team at Architectures/ARM/Supported_Platforms."

[1] https://meetbot.fedoraproject.org/fedora-blocker-review/2019-04-22/f30-blocker-review.2019-04-22-16.00.txt
Comment 9 Fedora Update System 2019-04-23 23:44:05 UTC 
arm-image-installer-2.12-1.fc30, uboot-tools-2019.04-1.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.