[Bug 1906552] Re: "Synchronous Abort" handler and reboot loop on rpi

[Mathew Hodson]

** Changed in: u-boot (Ubuntu)
   Importance: Undecided => High

** Changed in: u-boot (Ubuntu Focal)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1906552

Title:
  "Synchronous Abort" handler and reboot loop on rpi

Status in u-boot package in Ubuntu:
  New
Status in u-boot source package in Focal:
  New

Bug description:
  I first noticed this on a focal daily image (http://cdimage.ubuntu.com
  /ubuntu-server/focal/daily-preinstalled/20201202/ or the current
  pending one should be able to reproduce it). On the rpi400 device, it
  goes into a reboot loop. I'm also seeing this behavior with the
  current uc20 arm64 images on rpi400, and I suspect the same problem
  could be happening on cm4, but I can't confirm that yet because I
  don't have one in front of me.

  Here's the output I'm getting from serial before it goes into the reboot loop (it gives this output each time it reboots):
  U-Boot 2020.10+dfsg-1ubuntu0~20.04.1 (Nov 12 2020 - 17:05:18 +0000)

  DRAM:  3.9 GiB
  RPI: Board rev 0x13 outside known range
  RPI Unknown model (0xc03130)
  MMC:   mmcnr at 7e300000: 1, emmc2 at 7e340000: 0
  Loading Environment from FAT... ** No partition table - mmc 0 **
  In:    serial
  Out:   vidconsole
  Err:   vidconsole
  Net:   eth0: ethernet at 7d580000
  PCIe BRCM: link up, 5.0 Gbps x1 (SSC)
  starting USB...
  Bus xhci_pci: probe failed, error -110
  No working controllers found
  Hit any key to stop autoboot:  0
  switch to partitions #0, OK
  mmc0 is current device
  ** No partition table - mmc 0 **
  Card did not respond to voltage select!
  starting USB...
  Bus xhci_pci: probe failed, error -110
  No working controllers found
  USB is stopped. Please issue 'usb start' first.
  starting USB...
  Bus xhci_pci: probe failed, error -110
  No working controllers found
  "Synchronous Abort" handler, esr 0x96000044
  elr: 000000000009c1c0 lr : 0000000000091edc (reloc)
  elr: 000000003b3751c0 lr : 000000003b36aedc
  x0 : 0000000000000031 x1 : 0000000000000051
  x2 : 20d51c1000580003 x3 : 409400002fd519f2
  x4 : 20d2800800d51e10 x5 : 0000000000000014
  x6 : 000000003b3d2e40 x7 : 20d2800800d51df0
  x8 : 0000000000000000 x9 : 0000000000000008
  x10: 00000000ffffffd0 x11: 000000000000000d
  x12: 0000000000000006 x13: 000000000001869f
  x14: 000000003af2ceb0 x15: 0000000000000002
  x16: 000000003b377278 x17: 33a26b1e70c6e1df
  x18: 000000003af38d90 x19: 0000000000000021
  x20: 000000003b3d2d00 x21: 000000003afcac50
  x22: 000000000000000b x23: 00000000ffffffff
  x24: 0000000000000002 x25: 000000003b3e5594
  x26: 000000003b3bee1b x27: 000000003b3c74cb
  x28: 0000000000000020 x29: 000000003af2c4f0

  Code: a9410803 8b130001 b2400273 f9000413 (f9000c62)
  Resetting CPU ...

  resetting ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/1906552/+subscriptions