Debian Bug report logs - #973323
u-boot-rockchip: hangs consistently at "Booting using the fdt blob at 0x01f00000"

Display info messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: "H. Muller" <hxmuller@gmail.com>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: u-boot-rockchip: hangs consistently at "Booting using the fdt blob at 0x01f00000"

Date: Wed, 28 Oct 2020 16:23:45 -0400

Package: u-boot-rockchip
Version: 2020.10+dfsg-1
Severity: important
Tags: upstream
X-Debbugs-Cc: hxmuller@gmail.com

Dear Vagrant Cascadian,

This report is specific to the RockPro64 but the Pinebook Pro is also
affected as its <board>_defconfig is similar. This report is generated
on a Raspberry PI 3 model B v1.2 so take the automatically included
System Information below with a grain of salt.

When booting u-boot v2020.10 using the default configuration for the
RockPro64 (rockpro64-rk3399_defconfig) it is expected that it boot 
successfully everytime.

But what happens whether u-boot is installed to micro SD card or SPI
NOR flash, is that most of the time it will fail to boot and hang
at "Booting using the fdt blob at 0x01f00000". If you press and hold
the power button down until the board is powered down and restart it,
and repeat, it will eventually boot the kernel and the system.

It am unsure where the actual problem lies although I strongly
suspect that the SPI configuration for the rk3399 u-boot port is the
culprit. I am too new to the u-boot code base, device tree, etc., to
be sure.

A workaround that satisfactorily allows the board to boot _everytime_
is to change environment storage location from SPI to FAT. After
running `make rockpro64-rk3399_defconfig` I ran `make menuconfig`
and made the following changes:

[ ] Enable overwriting environment
[ ] Environment is not stored
[ ] Environment in EEPROM
[*] Environment is in a FAT filesystem
[ ] Environment is in a EXT4 filesystem
[ ] Environment in flash memory
[ ] Environment in an MMC device
[ ] Environment in a NAND device
[ ] Environment in a non-volatile RAM
[ ] Environment is in OneNAND
[ ] Environment is in remote memory space
[ ] Environment is in SPI flash
(mmc) Name of the block device for the environment
(1:1) Device and partition for where to store the environemt in FAT
(uboot.env) Name of the FAT file to use for the environment
(0x8000) Environment Size
[*] Relocate gd->env_addr
(1) mmc device number
(1) mmc partition number
[ ] Create default environment from file
[ ] Add run-time information to the environment
[ ] Always append the environment with new data
[ ] Permit write access only to listed variables
[ ] Block forced environment operations
[ ] Add a 'ver' environment variable with the U-Boot version

Note that the above is specific to storing the environment on a
micro SD card. The device and partition information would necessarily
have to be modified to use eMMC.

The workaround is a good temporary solution until the real problem
can be corrected, but it would be nice to store the environment in SPI
if one wished to. I am able to boot reliably whether u-boot is
installed to SPI or micro SD card using this workaround.

I have not tested this on my Pinebook Pro yet, but I suspect it will
resolve the issues I have been having with it also (stock u-boot 
v2020.10).

Best,

H

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: arm64 (aarch64)

Kernel: Linux 5.8.0-2-arm64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

u-boot-rockchip depends on no packages.

Versions of packages u-boot-rockchip recommends:
ii  arm-trusted-firmware  2.3+dfsg-3
ii  python3               3.8.2-3
ii  u-boot-tools          2020.10+dfsg-1

u-boot-rockchip suggests no packages.

-- no debconf information

Message #10 received at 973323@bugs.debian.org (full text, mbox, reply):

From: Vagrant Cascadian <vagrant@debian.org>

To: u-boot@lists.denx.de

Cc: Simon Glass <sjg@chromium.org>, Philipp Tomsich <philipp.tomsich@theobroma-systems.com>, Kever Yang <kever.yang@rock-chips.com>, 973323@bugs.debian.org, 980434@bugs.debian.org

Subject: Boot failure triggered by USB on rockpro64-rk3399 and pinebook-pro-rk3399

Date: Wed, 20 Jan 2021 16:08:33 -0800

[Message part 1 (text/plain, inline)]

It seems rockpro64-rk3399 and pinebook-pro-rk3399 fail to boot when usb
is started. It hangs indefinitely at:

  ## Flattened Device Tree blob at 01f00000
     Booting using the fdt blob at 0x1f00000

I have observed this also using 2020.10 on rockpro64-rk3399, though on
pinebook-pro-rk3399 usb does not work and so it basically avoids
triggering the issue.

Setting CONFIG_USE_PREBOOT=n in the config works around the problem,
though obviously by breaking usb keyboard support or booting from USB
devices.


Related bugs in Debian and manjaro:

  https://bugs.debian.org/973323
  https://bugs.debian.org/980434
  https://gitlab.manjaro.org/manjaro-arm/packages/core/uboot-rockpro64/-/issues/4


Boot log:

U-Boot 2021.01+dfsg-1 (Jan 17 2021 - 03:50:13 +0000)

SoC: Rockchip rk3399
Reset cause: POR
Model: Pine64 RockPro64 v2.1
DRAM:  3.9 GiB 
PMIC:  RK808   
MMC:   mmc@fe310000: 2, mmc@fe320000: 1, sdhci@fe330000: 0
Loading Environment from SPIFlash... SF: Detected gd25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Model: Pine64 RockPro64 v2.1
Net:   eth0: ethernet@fe300000
starting USB...
Bus usb@fe380000: USB EHCI 1.00
Bus usb@fe3a0000: USB OHCI 1.0
Bus usb@fe3c0000: USB EHCI 1.00
Bus usb@fe3e0000: USB OHCI 1.0
Bus dwc3: usb maximum-speed not found
Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.10
scanning bus usb@fe380000 for devices... 1 USB Device(s) found
scanning bus usb@fe3a0000 for devices... 1 USB Device(s) found
scanning bus usb@fe3c0000 for devices... 1 USB Device(s) found
scanning bus usb@fe3e0000 for devices... 1 USB Device(s) found
scanning bus dwc3 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot:  0
=> printenv preboot
preboot=usb start
=> usb reset   
resetting USB...
Bus usb@fe380000: USB EHCI 1.00
Bus usb@fe3a0000: USB OHCI 1.0
Bus usb@fe3c0000: USB EHCI 1.00
Bus usb@fe3e0000: USB OHCI 1.0
Bus dwc3: usb maximum-speed not found
Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.10  
scanning bus usb@fe380000 for devices... 1 USB Device(s) found
scanning bus usb@fe3a0000 for devices... 1 USB Device(s) found
scanning bus usb@fe3c0000 for devices... 1 USB Device(s) found
scanning bus usb@fe3e0000 for devices... 1 USB Device(s) found
scanning bus dwc3 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
=> boot
Card did not respond to voltage select! : -110
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
Found /extlinux/extlinux.conf
Retrieving file: /extlinux/extlinux.conf
144 bytes read in 5 ms (27.3 KiB/s)
1:      Debian-Installer
Retrieving file: /initrd.gz
28995285 bytes read in 1287 ms (21.5 MiB/s)
Retrieving file: /vmlinuz
26922864 bytes read in 1195 ms (21.5 MiB/s)
Retrieving file: /dtbs/rockchip/rk3399-rockpro64.dtb
56849 bytes read in 13 ms (4.2 MiB/s)
Moving Image from 0x2080000 to 0x2200000, end=3c50000
## Flattened Device Tree blob at 01f00000
   Booting using the fdt blob at 0x1f00000



live well,
  vagrant

[signature.asc (application/pgp-signature, inline)]

Message #15 received at 973323@bugs.debian.org (full text, mbox, reply):

From: Kever Yang <kever.yang@rock-chips.com>

To: Vagrant Cascadian <vagrant@debian.org>, u-boot@lists.denx.de

Cc: Simon Glass <sjg@chromium.org>, Philipp Tomsich <philipp.tomsich@theobroma-systems.com>, 973323@bugs.debian.org, 980434@bugs.debian.org

Subject: Re: Boot failure triggered by USB on rockpro64-rk3399 and pinebook-pro-rk3399

Date: Thu, 21 Jan 2021 11:37:16 +0800

Hi Vagrant,

    Do you know which version is the last version that works in this case?

    The firmware is from eMMC and it's wired for USB to affect the boot 
process.

Thanks,

- Kever

On 2021/1/21 上午8:08, Vagrant Cascadian wrote:
> It seems rockpro64-rk3399 and pinebook-pro-rk3399 fail to boot when usb
> is started. It hangs indefinitely at:
>
>    ## Flattened Device Tree blob at 01f00000
>       Booting using the fdt blob at 0x1f00000
>
> I have observed this also using 2020.10 on rockpro64-rk3399, though on
> pinebook-pro-rk3399 usb does not work and so it basically avoids
> triggering the issue.
>
> Setting CONFIG_USE_PREBOOT=n in the config works around the problem,
> though obviously by breaking usb keyboard support or booting from USB
> devices.
>
>
> Related bugs in Debian and manjaro:
>
>    https://bugs.debian.org/973323
>    https://bugs.debian.org/980434
>    https://gitlab.manjaro.org/manjaro-arm/packages/core/uboot-rockpro64/-/issues/4
>
>
> Boot log:
>
> U-Boot 2021.01+dfsg-1 (Jan 17 2021 - 03:50:13 +0000)
>
> SoC: Rockchip rk3399
> Reset cause: POR
> Model: Pine64 RockPro64 v2.1
> DRAM:  3.9 GiB
> PMIC:  RK808
> MMC:   mmc@fe310000: 2, mmc@fe320000: 1, sdhci@fe330000: 0
> Loading Environment from SPIFlash... SF: Detected gd25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB
> *** Warning - bad CRC, using default environment
>
> In:    serial
> Out:   serial
> Err:   serial
> Model: Pine64 RockPro64 v2.1
> Net:   eth0: ethernet@fe300000
> starting USB...
> Bus usb@fe380000: USB EHCI 1.00
> Bus usb@fe3a0000: USB OHCI 1.0
> Bus usb@fe3c0000: USB EHCI 1.00
> Bus usb@fe3e0000: USB OHCI 1.0
> Bus dwc3: usb maximum-speed not found
> Register 2000140 NbrPorts 2
> Starting the controller
> USB XHCI 1.10
> scanning bus usb@fe380000 for devices... 1 USB Device(s) found
> scanning bus usb@fe3a0000 for devices... 1 USB Device(s) found
> scanning bus usb@fe3c0000 for devices... 1 USB Device(s) found
> scanning bus usb@fe3e0000 for devices... 1 USB Device(s) found
> scanning bus dwc3 for devices... 1 USB Device(s) found
>         scanning usb for storage devices... 0 Storage Device(s) found
> Hit any key to stop autoboot:  0
> => printenv preboot
> preboot=usb start
> => usb reset
> resetting USB...
> Bus usb@fe380000: USB EHCI 1.00
> Bus usb@fe3a0000: USB OHCI 1.0
> Bus usb@fe3c0000: USB EHCI 1.00
> Bus usb@fe3e0000: USB OHCI 1.0
> Bus dwc3: usb maximum-speed not found
> Register 2000140 NbrPorts 2
> Starting the controller
> USB XHCI 1.10
> scanning bus usb@fe380000 for devices... 1 USB Device(s) found
> scanning bus usb@fe3a0000 for devices... 1 USB Device(s) found
> scanning bus usb@fe3c0000 for devices... 1 USB Device(s) found
> scanning bus usb@fe3e0000 for devices... 1 USB Device(s) found
> scanning bus dwc3 for devices... 1 USB Device(s) found
>         scanning usb for storage devices... 0 Storage Device(s) found
> => boot
> Card did not respond to voltage select! : -110
> switch to partitions #0, OK
> mmc1 is current device
> Scanning mmc 1:1...
> Found /extlinux/extlinux.conf
> Retrieving file: /extlinux/extlinux.conf
> 144 bytes read in 5 ms (27.3 KiB/s)
> 1:      Debian-Installer
> Retrieving file: /initrd.gz
> 28995285 bytes read in 1287 ms (21.5 MiB/s)
> Retrieving file: /vmlinuz
> 26922864 bytes read in 1195 ms (21.5 MiB/s)
> Retrieving file: /dtbs/rockchip/rk3399-rockpro64.dtb
> 56849 bytes read in 13 ms (4.2 MiB/s)
> Moving Image from 0x2080000 to 0x2200000, end=3c50000
> ## Flattened Device Tree blob at 01f00000
>     Booting using the fdt blob at 0x1f00000
>
>
>
> live well,
>    vagrant

Message #20 received at 973323@bugs.debian.org (full text, mbox, reply):

From: Alper Nebi Yasak <alpernebiyasak@gmail.com>

To: Kever Yang <kever.yang@rock-chips.com>, Vagrant Cascadian <vagrant@debian.org>, u-boot@lists.denx.de

Cc: Simon Glass <sjg@chromium.org>, Philipp Tomsich <philipp.tomsich@theobroma-systems.com>, 973323@bugs.debian.org, 980434@bugs.debian.org

Subject: Re: Boot failure triggered by USB on rockpro64-rk3399 and pinebook-pro-rk3399

Date: Thu, 21 Jan 2021 12:12:35 +0300

On 21/01/2021 03:08, Vagrant Cascadian wrote:
> It seems rockpro64-rk3399 and pinebook-pro-rk3399 fail to boot when usb
> is started. It hangs indefinitely at:
> 
>   ## Flattened Device Tree blob at 01f00000
>      Booting using the fdt blob at 0x1f00000
> 
> I have observed this also using 2020.10 on rockpro64-rk3399, though on
> pinebook-pro-rk3399 usb does not work and so it basically avoids
> triggering the issue.
> 
> Setting CONFIG_USE_PREBOOT=n in the config works around the problem,
> though obviously by breaking usb keyboard support or booting from USB
> devices.

This might be the same as [1] where running "usb stop" would hang, but
disabling CONFIG_USB_OHCI_HCD and CONFIG_USB_OHCI_GENERIC gets the board
to boot (still breaks the keyboard). Might help narrow things down.

[1] https://lists.denx.de/pipermail/u-boot/2020-November/432931.html


On 21/01/2021 06:37, Kever Yang wrote:
>      Do you know which version is the last version that works in this case?

The email I linked above has some versions they've tested, in case this
is the same issue.

Message #25 received at 973323@bugs.debian.org (full text, mbox, reply):

From: Jonathan Gray <jsg@jsg.id.au>

To: Kever Yang <kever.yang@rock-chips.com>

Cc: Vagrant Cascadian <vagrant@debian.org>, u-boot@lists.denx.de, Simon Glass <sjg@chromium.org>, Philipp Tomsich <philipp.tomsich@theobroma-systems.com>, 973323@bugs.debian.org, 980434@bugs.debian.org, kurt@openbsd.org, jagan@amarulasolutions.com

Subject: Re: Boot failure triggered by USB on rockpro64-rk3399 and pinebook-pro-rk3399

Date: Fri, 22 Jan 2021 12:31:07 +1100

U-Boot 2020.07 worked, broken on rockpro64 by

commit 3ae64582fb8ceead4fc464cd2055eb3eaef78ccc (refs/bisect/bad)
Author: Jagan Teki <jagan@amarulasolutions.com>
Date:   Mon Jul 20 14:53:09 2020 +0530

    rockchip: rockpro64: Enable USB3.0 Host
    
    Enable USB3.0 Host support for RockPro64 boards.
    
    Signed-off-by: Jagan Teki <jagan@amarulasolutions.com>
    Reviewed-by: Kever Yang <kever.yang@rock-chips.com>

according to Kurt Miller who bisected this when the same problem was
encountered booting OpenBSD.  I don't have any rk3399 myself.

https://marc.info/?l=openbsd-ports&m=161005506031482&w=2
https://marc.info/?l=openbsd-ports&m=161012461223737&w=2

We ended up disabling CONFIG_USE_PREBOOT in rk3399 targets to fix
booting via non-usb as well.

On Thu, Jan 21, 2021 at 11:37:16AM +0800, Kever Yang wrote:
> Hi Vagrant,
> 
>     Do you know which version is the last version that works in this case?
> 
>     The firmware is from eMMC and it's wired for USB to affect the boot
> process.
> 
> Thanks,
> 
> - Kever
> 
> On 2021/1/21 上午8:08, Vagrant Cascadian wrote:
> > It seems rockpro64-rk3399 and pinebook-pro-rk3399 fail to boot when usb
> > is started. It hangs indefinitely at:
> > 
> >    ## Flattened Device Tree blob at 01f00000
> >       Booting using the fdt blob at 0x1f00000
> > 
> > I have observed this also using 2020.10 on rockpro64-rk3399, though on
> > pinebook-pro-rk3399 usb does not work and so it basically avoids
> > triggering the issue.
> > 
> > Setting CONFIG_USE_PREBOOT=n in the config works around the problem,
> > though obviously by breaking usb keyboard support or booting from USB
> > devices.
> > 
> > 
> > Related bugs in Debian and manjaro:
> > 
> >    https://bugs.debian.org/973323
> >    https://bugs.debian.org/980434
> >    https://gitlab.manjaro.org/manjaro-arm/packages/core/uboot-rockpro64/-/issues/4
> > 
> > 
> > Boot log:
> > 
> > U-Boot 2021.01+dfsg-1 (Jan 17 2021 - 03:50:13 +0000)
> > 
> > SoC: Rockchip rk3399
> > Reset cause: POR
> > Model: Pine64 RockPro64 v2.1
> > DRAM:  3.9 GiB
> > PMIC:  RK808
> > MMC:   mmc@fe310000: 2, mmc@fe320000: 1, sdhci@fe330000: 0
> > Loading Environment from SPIFlash... SF: Detected gd25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB
> > *** Warning - bad CRC, using default environment
> > 
> > In:    serial
> > Out:   serial
> > Err:   serial
> > Model: Pine64 RockPro64 v2.1
> > Net:   eth0: ethernet@fe300000
> > starting USB...
> > Bus usb@fe380000: USB EHCI 1.00
> > Bus usb@fe3a0000: USB OHCI 1.0
> > Bus usb@fe3c0000: USB EHCI 1.00
> > Bus usb@fe3e0000: USB OHCI 1.0
> > Bus dwc3: usb maximum-speed not found
> > Register 2000140 NbrPorts 2
> > Starting the controller
> > USB XHCI 1.10
> > scanning bus usb@fe380000 for devices... 1 USB Device(s) found
> > scanning bus usb@fe3a0000 for devices... 1 USB Device(s) found
> > scanning bus usb@fe3c0000 for devices... 1 USB Device(s) found
> > scanning bus usb@fe3e0000 for devices... 1 USB Device(s) found
> > scanning bus dwc3 for devices... 1 USB Device(s) found
> >         scanning usb for storage devices... 0 Storage Device(s) found
> > Hit any key to stop autoboot:  0
> > => printenv preboot
> > preboot=usb start
> > => usb reset
> > resetting USB...
> > Bus usb@fe380000: USB EHCI 1.00
> > Bus usb@fe3a0000: USB OHCI 1.0
> > Bus usb@fe3c0000: USB EHCI 1.00
> > Bus usb@fe3e0000: USB OHCI 1.0
> > Bus dwc3: usb maximum-speed not found
> > Register 2000140 NbrPorts 2
> > Starting the controller
> > USB XHCI 1.10
> > scanning bus usb@fe380000 for devices... 1 USB Device(s) found
> > scanning bus usb@fe3a0000 for devices... 1 USB Device(s) found
> > scanning bus usb@fe3c0000 for devices... 1 USB Device(s) found
> > scanning bus usb@fe3e0000 for devices... 1 USB Device(s) found
> > scanning bus dwc3 for devices... 1 USB Device(s) found
> >         scanning usb for storage devices... 0 Storage Device(s) found
> > => boot
> > Card did not respond to voltage select! : -110
> > switch to partitions #0, OK
> > mmc1 is current device
> > Scanning mmc 1:1...
> > Found /extlinux/extlinux.conf
> > Retrieving file: /extlinux/extlinux.conf
> > 144 bytes read in 5 ms (27.3 KiB/s)
> > 1:      Debian-Installer
> > Retrieving file: /initrd.gz
> > 28995285 bytes read in 1287 ms (21.5 MiB/s)
> > Retrieving file: /vmlinuz
> > 26922864 bytes read in 1195 ms (21.5 MiB/s)
> > Retrieving file: /dtbs/rockchip/rk3399-rockpro64.dtb
> > 56849 bytes read in 13 ms (4.2 MiB/s)
> > Moving Image from 0x2080000 to 0x2200000, end=3c50000
> > ## Flattened Device Tree blob at 01f00000
> >     Booting using the fdt blob at 0x1f00000
> > 
> > 
> > 
> > live well,
> >    vagrant
> 
> 
> 

Message #28 received at 973323-submitter@bugs.debian.org (full text, mbox, reply):

From: Vagrant Cascadian <noreply@salsa.debian.org>

To: 973323-submitter@bugs.debian.org

Subject: Bug#973323 marked as pending in u-boot

Date: Fri, 22 Jan 2021 04:53:07 +0000

Control: tag -1 pending

Hello,

Bug #973323 in u-boot reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/debian/u-boot/-/commit/41bb6a78202f2e9b1f56f20657812a4daf2b5c88

------------------------------------------------------------------------
debian/patches: Disable USE_PREBOOT on rockpro64 and pinebook-pro to
workaround boot failure triggered by USB initialization.
(Closes: #973323, #980434)

Reported upstream:

  https://lists.denx.de/pipermail/u-boot/2021-January/438098.html
------------------------------------------------------------------------

(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/973323

Message #35 received at 973323-close@bugs.debian.org (full text, mbox, reply):

From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>

To: 973323-close@bugs.debian.org

Subject: Bug#973323: fixed in u-boot 2021.01+dfsg-2

Date: Fri, 22 Jan 2021 05:03:51 +0000

Source: u-boot
Source-Version: 2021.01+dfsg-2
Done: Vagrant Cascadian <vagrant@debian.org>

We believe that the bug you reported is fixed in the latest version of
u-boot, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 973323@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Vagrant Cascadian <vagrant@debian.org> (supplier of updated u-boot package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Thu, 21 Jan 2021 20:36:56 -0800
Source: u-boot
Architecture: source
Version: 2021.01+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Vagrant Cascadian <vagrant@debian.org>
Changed-By: Vagrant Cascadian <vagrant@debian.org>
Closes: 973323 980434
Changes:
 u-boot (2021.01+dfsg-2) unstable; urgency=medium
 .
   * debian/patches: Disable USE_PREBOOT on rockpro64 and pinebook-pro to
     workaround boot failure triggered by USB initialization.
     (Closes: #973323, #980434)
Checksums-Sha1:
 c8338b7a14582db33e2f60ac0bb133d85f4224a5 2895 u-boot_2021.01+dfsg-2.dsc
 04f893de0e85b887f0290634e3a2f1c2ff029c09 43352 u-boot_2021.01+dfsg-2.debian.tar.xz
 160ed208eb00ca733577b15126f0c49e47d6ef26 9869 u-boot_2021.01+dfsg-2_amd64.buildinfo
Checksums-Sha256:
 80c8f84798b1b7038a552bca8fcdb01c7e9dab79dd86f7d59e613753ce1afdc0 2895 u-boot_2021.01+dfsg-2.dsc
 e4c99522f4b9efc8d051d4cf82fd91c8d9cafbb16b486bf0035bc1457edea650 43352 u-boot_2021.01+dfsg-2.debian.tar.xz
 c29aa0f744aa97f627964e41025b1e5ca49640c14488674112e4150b23dc4418 9869 u-boot_2021.01+dfsg-2_amd64.buildinfo
Files:
 a90f4b1998d7c532d147e7c0c174e6a3 2895 admin optional u-boot_2021.01+dfsg-2.dsc
 d878f5773713614e59c883efc1286e17 43352 admin optional u-boot_2021.01+dfsg-2.debian.tar.xz
 36479ac15bf7bccd0a33503c43291fe6 9869 admin optional u-boot_2021.01+dfsg-2_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iIkEARYKADEWIQRlgHNhO/zFx+LkXUXcUY/If5cWqgUCYApaAxMcdmFncmFudEBk
ZWJpYW4ub3JnAAoJENxRj8h/lxaqaGkA/ROOHqSljcHic7JxsWSXV0rTwttyqADj
XNyG07NXuyJmAQDesyxGlnT0z3V3+iGSY9rKB0JuJyjq4wlvHPEiw3FTBA==
=6LQm
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.