-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Debian 11 instructions for LX2 fail: "Bad DPL image" / "Synchronous Abort" #6
Comments
somehow it looks like the above log still tries to load some stuff from SD. Using slightly modified instructions I get a bit further: => wdt dev watchdog@23a0000 => wdt stop => setenv bootargs arm-smmu.disable-bypass=0 => usb start starting USB... Bus usb3@3100000: Register 200017f NbrPorts 2 Starting the controller USB XHCI 1.00 Bus usb3@3110000: Register 200017f NbrPorts 2 Starting the controller USB XHCI 1.00 scanning bus usb3@3100000 for devices... 1 USB Device(s) found scanning bus usb3@3110000 for devices... 5 USB Device(s) found scanning usb for storage devices... 1 Storage Device(s) found => devnum=0; run usb_boot Device 0: Vendor: Intenso Rev: 1100 Prod: Rainbow Line Type: Removable Hard Disk Capacity: 7620.0 MB = 7.4 GB (15605760 x 512) ... is now current device Scanning usb 0:1... Found /extlinux/extlinux.conf Retrieving file: /extlinux/extlinux.conf 144 bytes read in 3 ms (46.9 KiB/s) 1: Debian-Installer Retrieving file: /initrd.gz 29271227 bytes read in 1694 ms (16.5 MiB/s) Retrieving file: /vmlinuz 27535232 bytes read in 1613 ms (16.3 MiB/s) Retrieving file: /dtbs/fsl-lx2160a-clearfog-cx.dtb Failed to load '/dtbs/fsl-lx2160a-clearfog-cx.dtb' Moving Image from 0x81100000 to 0x81200000, end=82ce0000 ERROR: Did not find a cmdline Flattened Device Tree Could not find a valid device tree SCRIPT FAILED: continuing... libfdt fdt_check_header(): FDT_ERR_BADMAGIC Scanning disk [email protected]... Scanning disk [email protected]... Scanning disk usb_mass_storage.lun0... Found 6 disks No EFI system partition ERROR: invalid device tree So somehow the debian image is missing the dtb files? Strangely enough, http://debian.parspack.com/debian/dists/stable/main/installer-arm64/current/images/device-tree/freescale/ lists them... |
mounting the USB drive showed that the dtb is in [ 50.848946] Unable to handle kernel paging request at virtual address 0000000002000112 [ 50.856861] Mem abort info: │ [ 50.859652] ESR = 0x96000004 [ 50.862701] EC = 0x25: DABT (current EL), IL = 32 bits [ 50.868006] SET = 0, FnV = 0 [ 50.871054] EA = 0, S1PTW = 0 [ 50.874183] Data abort info: [ 50.877058] ISV = 0, ISS = 0x00000004 [ 50.880885] CM = 0, WnR = 0 [ 50.883848] user pgtable: 4k pages, 48-bit VAs, pgdp=000000208a703000 [ 50.890284] [0000000002000112] pgd=0000000000000000, p4d=0000000000000000 [ 50.897076] Internal error: Oops: 96000004 [#1] SMP [ 50.901943] Modules linked in: sd_mod t10_pi crc_t10dif crct10dif_common uas usb_storage scsi_mod xhci_plat_hcd xhci_hcd usbcore at803x xgmac_mdio dwc3 of_mdio sdhci_of_esdhc udc_core fixed_phy sdhci_pltfm libphy dpaa2_console roles ulpi sdhci usb_common spi_nxp_fspi fixed [ 50.926121] CPU: 1 PID: 737 Comm: usb-storage Not tainted 5.10.0-13-arm64 #1 Debian 5.10.106-1 [ 50.934720] Hardware name: SolidRun LX2160A Clearfog CX (DT) [ 50.940369] pstate: 20000005 (nzCv daif -PAN -UAO -TCO BTYPE=--) [ 50.946371] pc : __pi_memcmp+0xd8/0x1c0 [ 50.950205] lr : descriptors_changed+0x134/0x2bc [usbcore] [ 50.955679] sp : ffff8000113bbba0 [ 50.958982] x29: ffff8000113bbba0 x28: 0000000000000000 [ 50.964285] x27: ffff6031019d1850 x26: 0000000000000000 [ 50.969587] x25: 0000000000000000 x24: 0000000000000000 [ 50.974889] x23: ffff60310972d900 x22: 0000000000000008 [ 50.985493] x19: ffff6031019d1800 x18: 00000000fffffffe [ 50.990795] x17: 0000000000000000 x16: 0000000000000000 [ 50.996098] x15: 0000000000000020 x14: 6463682d69636878 [ 51.001399] x13: 20676e6973752034 x12: 0000000000000000 [ 51.006701] x11: 0000000000000008 x10: 0000000000000002 [ 51.012003] x9 : 0000000000000006 x8 : 0000000000000008 [ 51.017305] x7 : ffff91fbe33e0000 x6 : 0000000000000000 [ 51.022607] x5 : 0000000000000000 x4 : 0000000000000020 [ 51.027908] x3 : 0000000000000009 x2 : 0000000000000018 [ 51.033210] x1 : 4000000002000112 x0 : ffff60310972d901 [ 51.038517] Call trace: [ 51.038521] __pi_memcmp+0xd8/0x1c0 [ 51.038527] usb_reset_and_verify_device+0x180/0x430 [usbcore] [ 51.038532] usb_reset_device+0xf4/0x270 [usbcore] [ 51.038539] usb_stor_port_reset+0x70/0x84 [usb_storage] [ 51.060349] usb_stor_invoke_transport+0x258/0x7ec [usb_storage] [ 51.060351] usb_stor_transparent_scsi_command+0x1c/0x30 [usb_storage] [ 51.060356] usb_stor_control_thread+0x294/0x314 [usb_storage] [ 51.078692] kthread+0x130/0x13c [ 51.078696] ret_from_fork+0x10/0x38 [ 51.078701] Code: eb09010a 9a89810b cb0b0042 38401403 (38401424) [ 51.091563] ---[ end trace ca34e69be2530b40 ]--- |
ok, the kernel panic related to usb-storage seems to be some general USB instability that I'm seeing, also with many USB devices not beeing properly recognized, u-boot complaining about XHCI errors, etc. So I did manage to fully install bullseye with the modified image (copying the dtb as described above). I don't have sufficient experince with distro-boot etc. to judge whose fault it is. Should the solid-run u-boot look for the file in a different path? should it try multiple paths before giving up? should the documentation simply be updated? I guess this needs input from @jnettlet. |
I'm using the instructions step-by-step but it fails to boot the kernel, using the concatenation of https://deb.debian.org/debian/dists/bullseye/main/installer-arm64/current/images/netboot/SD-card-images/firmware.none.img.gz and
https://deb.debian.org/debian/dists/bullseye/main/installer-arm64/current/images/netboot/SD-card-images/partition.img.gz on a USB storage device.
The text was updated successfully, but these errors were encountered: