Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 30 Sep 2018 15:50:55 +0200
From:      Emmanuel Vadot <manu@bidouilliste.com>
To:        bob prohaska <fbsd@www.zefox.net>
Cc:        freebsd-arm@freebsd.org
Subject:   Re: Timeout poll on interrupt endpoint for RPI3 with keyboard and mouse
Message-ID:  <20180930155055.2c35693431e8dfff4eb7d7bd@bidouilliste.com>
In-Reply-To: <20180930132928.GC58381@www.zefox.net>
References:  <20180929185213.GA58381@www.zefox.net> <20180930111208.5df04f5b7fb336cdfcf2fd74@bidouilliste.com> <20180930130930.GB58381@www.zefox.net> <20180930132928.GC58381@www.zefox.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 30 Sep 2018 06:29:28 -0700
bob prohaska <fbsd@www.zefox.net> wrote:

>=20
> I just tried rebooting with HDMI only connected, and that failed in a=20
> different way:
>=20
> ?MMC:   mmc@7e300000: 1
> Loading Environment from FAT... *** Warning - bad CRC, using default envi=
ronment
>=20
> Failed (-5)
> In:    serial
> Out:   vidconsole
> Err:   vidconsole
> Net:   No ethernet found.
> starting USB...
> USB0:   scanning bus 0 for devices... 6 USB Device(s) found
>        scanning usb for storage devices... 2 Storage Device(s) found
> Hit any key to stop autoboot:  0=20
> MMC Device 0 not found
> no mmc device at slot 0
> switch to partitions #0, OK
> mmc1 is current device
> Scanning mmc 1:1...
> Found EFI removable media binary efi/boot/bootaa64.efi
> libfdt fdt_check_header(): FDT_ERR_BADMAGIC
> Scanning disk mmc@7e300000.blk...
> Scanning disk usb_mass_storage.lun0...
> Scanning disk usb_mass_storage.lun0...
> Found 14 disks
> 473400 bytes read in 50 ms (9 MiB/s)
> libfdt fdt_check_header(): FDT_ERR_BADMAGIC
> ## Starting EFI application at 00080000 ...
> Consoles: EFI console =20
> FreeBSD/arm64 EFI loader, Revision 1.1
> (Thu Aug  2 21:57:02 UTC 2018 root@releng3.nyi.freebsd.org)
>=20
>    Command line arguments: loader.efi
>    EFI version: 2.70
>    EFI Firmware: Das U-Boot (rev 0.00)
>    Console: efi (0)
>    Load Path: /\efi\boot\bootaa64.efi
>    Load Device: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(1)/SD(0)/=
HD(1,0x01,0,0x81f,0x18fa8)
> Trying ESP: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(1)/SD(0)/HD(1=
,0x01,0,0x81f,0x18fa8)
> Setting currdev to disk0p1:
> Trying: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(1)/SD(0)/HD(2,0x0=
1,0,0x197c7,0x1d92839)
> Setting currdev to disk0p2:
> Loading /boot/defaults/loader.conf
> ?/boot/kernel/kernel text=3D0x8c5f73 data=3D0x178df8+0x83ddd4 syms=3D[0x8=
+0x122928+0x8+0x115b27]
> /boot/entropy size=3D0x1000
> /boot/kernel/umodem.ko text=3D0x2160 text=3D0x13d0 data=3D0x102c8+0xfd48 =
syms=3D[0x8+0xf18+0x8+0xb62]
>=20
> Hit [Enter] to boot immediately, or any other key for command prompt.
> Booting [/boot/kernel/kernel]...              =20
> Using DTB provided by EFI at 0x7ff8000.
> EFI framebuffer information:
> addr, size     0x3e330000, 0x8ca000
> dimensions     1920 x 1200
> stride         1920
> masks          0x00ff0000, 0x0000ff00, 0x000000ff, 0xff000000
> panic: Too many early devmap mappings 2
> cpuid =3D 0
> time =3D 1
> KDB: stack backtrace:
> #0 0xffff0000003cc660 at ??+0
> #1 0xffff000000387e98 at ??+0
> #2 0xffff000000387c44 at ??+0
> #3 0xffff0000006e4824 at ??+0
> #4 0xffff000000250c38 at ??+0
> #5 0xffff000000253168 at ??+0
> #6 0xffff00000032b81c at ??+0
> #7 0xffff0000006a60a0 at ??+0
> Uptime: 1s

 Looks like the framebuffer size is too big, could you try with this :
diff --git a/sys/arm64/include/pte.h b/sys/arm64/include/pte.h
index acd3f81ab41c..7aa216e92b43 100644
--- a/sys/arm64/include/pte.h
+++ b/sys/arm64/include/pte.h
@@ -109,7 +109,7 @@ typedef     uint64_t
pt_entry_t;             /* page table entry */ /* 0x2 also marks an
invalid address */ #define        L3_PAGE         0x3
=20
-#define        PMAP_MAPDEV_EARLY_SIZE  (L2_SIZE * 4)
+#define        PMAP_MAPDEV_EARLY_SIZE  (L2_SIZE * 8)
=20
 #define        L0_ENTRIES_SHIFT 9
 #define        L0_ENTRIES      (1 << L0_ENTRIES_SHIFT)


> [no response to debugger escape]

 This is too early for debugger.

> The "found 14 disks" seems very wrong.=20
> There are 2 USB flash drives connected.
>=20
> Thanks for reading!
>=20
> bob prohaska


--=20
Emmanuel Vadot <manu@bidouilliste.com> <manu@freebsd.org>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180930155055.2c35693431e8dfff4eb7d7bd>