Re: raspberry pi 4 model b: xhci0: host system error
> Date: Mon, 1 Nov 2021 22:33:50 + > From: Klemens Nanni I just committed a fix for this. Should be in the next snapshot. > Neither RAMDISK nor GENERIC.MP from snapshots boot on my Raspberry 4 > Model B unless I disable xhci(4). > > I flashed miniroot70.img to an SD card, booted from it, did a default > install to it and booted the new system from it. > > Both times, `boot /bsd -c' and "disable xhci" were needed to bypass the > hard hang; after that, the system is fully functional. > > Same story with 7.0 release. > > No USB device is connected. > > I made no modification to u-boot, neither did I use the EDK2 based UEFI > firmware. > > FWIW, this happens with stock EEPROM firwmare dating a few months back > as well as the latest version obtained via `rpi-eeprom-update -a -d' on > Raspberry OS Lite. > > > Is this a known error? > Something missing in u-boot? > > > U-Boot 2021.10 (Oct 23 2021 - 05:09:34 -0600) > > DRAM: 7.9 GiB > RPI 4 Model B (0xd03114) > MMC: mmcnr@7e30: 1, emmc2@7e34: 0 > Loading Environment from FAT... Unable to read "uboot.env" from mmc0:1... In: >serial > Out: vidconsole > Err: vidconsole > Net: eth0: ethernet@7d58 > PCIe BRCM: link up, 5.0 Gbps x1 (SSC) > starting USB... > Bus xhci_pci: Register 5000420 NbrPorts 5 > Starting the controller > USB XHCI 1.00 > scanning bus xhci_pci for devices... 2 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 > Scanning mmc 0:1... > libfdt fdt_check_header(): FDT_ERR_BADMAGIC > Card did not respond to voltage select! : -110 > Scanning disk mm...@7e30.blk... > Disk mm...@7e30.blk not ready > Scanning disk em...@7e34.blk... > Found 3 disks > No EFI system partition > BootOrder not defined > EFI boot manager: Cannot load any image > Found EFI removable media binary efi/boot/bootaa64.efi > 170790 bytes read in 34 ms (4.8 MiB/s) > libfdt fdt_check_header(): FDT_ERR_BADMAGIC > Booting /efi\boot\bootaa64.efi > disks: sd0* > >> OpenBSD/arm64 BOOTAA64 1.6 > boot> b /bsd -c > booting sd0a:/bsd: 9107364+1900048+573712+827488 > [667656+109+1098336+640675]=0xfa1eb0 > type 0x0 pa 0x0 va 0x0 pages 0x1 attr 0x8 > type 0x7 pa 0x1000 va 0x1000 pages 0x1ff attr 0x8 > type 0x2 pa 0x20 va 0x20 pages 0x4000 attr 0x8 > type 0x7 pa 0x420 va 0x420 pages 0x3cf0 attr 0x8 > type 0x9 pa 0x7ef va 0x7ef pages 0x20 attr 0x8 > type 0x7 pa 0x7f1 va 0x7f1 pages 0x31ee2 attr 0x8 > type 0x2 pa 0x39df2000 va 0x39df2000 pages 0xe attr 0x8 > type 0x4 pa 0x39e0 va 0x39e0 pages 0x1 attr 0x8 > type 0x7 pa 0x39e01000 va 0x39e01000 pages 0x1 attr 0x8 > type 0x2 pa 0x39e02000 va 0x39e02000 pages 0x100 attr 0x8 > type 0x1 pa 0x39f02000 va 0x39f02000 pages 0x2a attr 0x8 > type 0x4 pa 0x39f2c000 va 0x39f2c000 pages 0x8 attr 0x8 > type 0x6 pa 0x39f34000 va 0x1b7302 pages 0x1 attr 0x8008 > type 0x4 pa 0x39f35000 va 0x39f35000 pages 0x3 attr 0x8 > type 0x6 pa 0x39f38000 va 0x1b73024000 pages 0x3 attr 0x8008 > type 0x4 pa 0x39f3b000 va 0x39f3b000 pages 0x1 attr 0x8 > type 0x6 pa 0x39f3c000 va 0x1b73028000 pages 0x4 attr 0x8008 > type 0x4 pa 0x39f4 va 0x39f4 pages 0x8 attr 0x8 > type 0x2 pa 0x39f48000 va 0x39f48000 pages 0x1408 attr 0x8 > type 0x5 pa 0x3b35 va 0x1b7443c000 pages 0x10 attr 0x8008 > type 0x2 pa 0x3b36 va 0x3b36 pages 0xa0 attr 0x8 > type 0x0 pa 0x3ef5c000 va 0x3ef5c000 pages 0x1 attr 0x8 > type 0x4 pa 0x4000 va 0x4000 pages 0xbc000 attr 0x8 > type 0xb pa 0xfe10 va 0x1b7444c000 pages 0x1 attr 0x8000 > type 0x4 pa 0x1 va 0x1 pages 0x10 attr 0x8 > [ using 2407744 bytes of bsd ELF symbol table ] > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > Copyright (c) 1995-2021 OpenBSD. All rights reserved. https://www.OpenBSD.org > > OpenBSD 7.0-current (GENERIC.MP) #1369: Sat Oct 30 22:11:08 MDT 2021 > dera...@arm64.openbsd.org:/usr/src/sys/arch/arm64/compile/GENERIC.MP > real mem = 8419872768 (8029MB) > avail mem = 8128700416 (7752MB) > User Kernel Config > UKC> enable xhci > 156 xhci* enabled > 219 xhci* enabled > 340 xhci* enabled > UKC> exit > Continuing... > random: good seed from bootblocks > mainbus0 at root: Raspberry Pi 4 Model B Rev 1.4 > cpu0 at mainbus0 mpidr 0: ARM Cortex-A72 r0p3 > cpu0: 48KB 64b/line 3-way L1 PIPT I-cache, 32KB 64b/line 2-way L1 D-cache > cpu0: 1024KB 64b/line 16-way L2 cache >
Re: raspberry pi 4 model b: xhci0: host system error
On Sat, Nov 06, 2021 at 07:53:57PM +0100, Paul de Weerd wrote: > It's not so much throughput as it is latency. From the rpi to its > gateway I see solid RTTs (note that I'm SSH'd into the raspberry to > run this command): > > 64 bytes from 192.168.34.1: icmp_seq=0 ttl=255 time=1.870 ms > 64 bytes from 192.168.34.1: icmp_seq=1 ttl=255 time=2.738 ms > 64 bytes from 192.168.34.1: icmp_seq=2 ttl=255 time=2.995 ms > 64 bytes from 192.168.34.1: icmp_seq=3 ttl=255 time=2.617 ms > 64 bytes from 192.168.34.1: icmp_seq=4 ttl=255 time=2.735 ms > 64 bytes from 192.168.34.1: icmp_seq=5 ttl=255 time=2.774 ms > 64 bytes from 192.168.34.1: icmp_seq=6 ttl=255 time=2.717 ms > 64 bytes from 192.168.34.1: icmp_seq=7 ttl=255 time=2.655 ms > 64 bytes from 192.168.34.1: icmp_seq=8 ttl=255 time=2.726 ms > 64 bytes from 192.168.34.1: icmp_seq=9 ttl=255 time=2.788 ms > > --- 192.168.34.1 ping statistics --- > 10 packets transmitted, 10 packets received, 0.0% packet loss > round-trip min/avg/max/std-dev = 1.870/2.661/2.995/0.281 ms > > The other direction is a lot more erratic: > > 64 bytes from 192.168.34.129: icmp_seq=0 ttl=255 time=52.829 ms > 64 bytes from 192.168.34.129: icmp_seq=1 ttl=255 time=67.423 ms > 64 bytes from 192.168.34.129: icmp_seq=2 ttl=255 time=296.138 ms > 64 bytes from 192.168.34.129: icmp_seq=3 ttl=255 time=115.754 ms > 64 bytes from 192.168.34.129: icmp_seq=4 ttl=255 time=37.241 ms > 64 bytes from 192.168.34.129: icmp_seq=5 ttl=255 time=61.002 ms > 64 bytes from 192.168.34.129: icmp_seq=6 ttl=255 time=290.358 ms > 64 bytes from 192.168.34.129: icmp_seq=7 ttl=255 time=108.851 ms > 64 bytes from 192.168.34.129: icmp_seq=8 ttl=255 time=30.519 ms > 64 bytes from 192.168.34.129: icmp_seq=9 ttl=255 time=55.587 ms > > --- 192.168.34.129 ping statistics --- > 10 packets transmitted, 10 packets received, 0.0% packet loss > round-trip min/avg/max/std-dev = 30.519/111.570/296.138/94.467 ms > > When the raspberry is doing traffic (i.e. pinging its gateway or > downloading a file), replies come a lot faster (similar to RTT's when > pinging from the raspberry) This could be wifi-client power management, in which case there is nothing to worry about. You are not losing any packets. I would assume frames get buffered in the AP while the wifi chip on the rpi is taking a short power-saving nap. The beacon period of an AP is usually about 100ms and it might take a beacon or two for the client to wake up and see the message from the AP that tells it about frames which have been buffered for it. These RTTs of <= 300 ms fit into that picture.
Re: raspberry pi 4 model b: xhci0: host system error
On Fri, Nov 05, 2021 at 01:00:21PM +, Klemens Nanni wrote: | From https://github.com/pftf/RPi4#additional-notes : | | A 3 GB RAM limit is enforced by default, even if you are using a | Raspberry Pi 4 model that has 4 GB or 8 GB of RAM, on account that the | OS must patch DMA access, to work around a hardware bug that is present | in the Broadcom SoC. For Linux this usually translates to using a | recent kernel (version 5.8 or later) and for Windows this requires the | installation of a filter driver. If you are running an OS that has been | adequately patched, you can disable the 3 GB limit by going to Device | Manager → Raspberry Pi Configuration → Advanced Settings in the UEFI | settings. | | Does that work for you? It does, see dmesg included below. On Fri, Nov 05, 2021 at 02:59:05PM +, Stuart Henderson wrote: | On 2021/11/05 09:32, Paul de Weerd wrote: | > Linking brcmfmac43455-sdio.raspberrypi,4-model-b.txt (which is what is | > used with u-boot, I believe) to this name in /etc/firmware fixed bwfm0 | > for me (although performance isn't great, but that's also the case | > when using u-boot). | | btw I *don't* have that problem (1.31 here). wlan performance isn't great | either (70Mb on VHT-MCS0 mode 11ac / -45dBm reported) but usable. | (ethernet performance OTOH *is* pretty good - ~800Mb). It's not so much throughput as it is latency. From the rpi to its gateway I see solid RTTs (note that I'm SSH'd into the raspberry to run this command): 64 bytes from 192.168.34.1: icmp_seq=0 ttl=255 time=1.870 ms 64 bytes from 192.168.34.1: icmp_seq=1 ttl=255 time=2.738 ms 64 bytes from 192.168.34.1: icmp_seq=2 ttl=255 time=2.995 ms 64 bytes from 192.168.34.1: icmp_seq=3 ttl=255 time=2.617 ms 64 bytes from 192.168.34.1: icmp_seq=4 ttl=255 time=2.735 ms 64 bytes from 192.168.34.1: icmp_seq=5 ttl=255 time=2.774 ms 64 bytes from 192.168.34.1: icmp_seq=6 ttl=255 time=2.717 ms 64 bytes from 192.168.34.1: icmp_seq=7 ttl=255 time=2.655 ms 64 bytes from 192.168.34.1: icmp_seq=8 ttl=255 time=2.726 ms 64 bytes from 192.168.34.1: icmp_seq=9 ttl=255 time=2.788 ms --- 192.168.34.1 ping statistics --- 10 packets transmitted, 10 packets received, 0.0% packet loss round-trip min/avg/max/std-dev = 1.870/2.661/2.995/0.281 ms The other direction is a lot more erratic: 64 bytes from 192.168.34.129: icmp_seq=0 ttl=255 time=52.829 ms 64 bytes from 192.168.34.129: icmp_seq=1 ttl=255 time=67.423 ms 64 bytes from 192.168.34.129: icmp_seq=2 ttl=255 time=296.138 ms 64 bytes from 192.168.34.129: icmp_seq=3 ttl=255 time=115.754 ms 64 bytes from 192.168.34.129: icmp_seq=4 ttl=255 time=37.241 ms 64 bytes from 192.168.34.129: icmp_seq=5 ttl=255 time=61.002 ms 64 bytes from 192.168.34.129: icmp_seq=6 ttl=255 time=290.358 ms 64 bytes from 192.168.34.129: icmp_seq=7 ttl=255 time=108.851 ms 64 bytes from 192.168.34.129: icmp_seq=8 ttl=255 time=30.519 ms 64 bytes from 192.168.34.129: icmp_seq=9 ttl=255 time=55.587 ms --- 192.168.34.129 ping statistics --- 10 packets transmitted, 10 packets received, 0.0% packet loss round-trip min/avg/max/std-dev = 30.519/111.570/296.138/94.467 ms When the raspberry is doing traffic (i.e. pinging its gateway or downloading a file), replies come a lot faster (similar to RTT's when pinging from the raspberry) On Fri, Nov 05, 2021 at 04:05:26PM +0100, Mark Kettenis wrote: | Go into the firmware configuration menu and switch from ACPI to Device | Tree (DT). That is what Stuart is using and should fix the wifi | problem. Thanks, that worked indeed. Again, dmesg below. Paul --- dmesg OpenBSD 7.0-current (GENERIC.MP) #1374: Wed Nov 3 15:40:43 MDT 2021 dera...@arm64.openbsd.org:/usr/src/sys/arch/arm64/compile/GENERIC.MP real mem = 4135923712 (3944MB) avail mem = 3976343552 (3792MB) random: good seed from bootblocks mainbus0 at root: Raspberry Pi 4 Model B Rev 1.4 psci0 at mainbus0: PSCI 1.1, SMCCC 1.2 cpu0 at mainbus0 mpidr 0: ARM Cortex-A72 r0p3 cpu0: 48KB 64b/line 3-way L1 PIPT I-cache, 32KB 64b/line 2-way L1 D-cache cpu0: 1024KB 64b/line 16-way L2 cache cpu0: CRC32,ASID16 cpu1 at mainbus0 mpidr 1: ARM Cortex-A72 r0p3 cpu1: 48KB 64b/line 3-way L1 PIPT I-cache, 32KB 64b/line 2-way L1 D-cache cpu1: 1024KB 64b/line 16-way L2 cache cpu1: CRC32,ASID16 cpu2 at mainbus0 mpidr 2: ARM Cortex-A72 r0p3 cpu2: 48KB 64b/line 3-way L1 PIPT I-cache, 32KB 64b/line 2-way L1 D-cache cpu2: 1024KB 64b/line 16-way L2 cache cpu2: CRC32,ASID16 cpu3 at mainbus0 mpidr 3: ARM Cortex-A72 r0p3 cpu3: 48KB 64b/line 3-way L1 PIPT I-cache, 32KB 64b/line 2-way L1 D-cache cpu3: 1024KB 64b/line 16-way L2 cache cpu3: CRC32,ASID16 efi0 at mainbus0: UEFI 2.7 efi0: https://github.com/pftf/RPi4 rev 0x1 smbios0 at efi0: SMBIOS 3.3.0 smbios0: vendor https://github.com/pftf/RPi4 version "UEFI Firmware v1.32" date 10/19/2021 smbios0: Raspberry Pi Foundation Raspberry Pi 4 Model B ap
Re: raspberry pi 4 model b: xhci0: host system error
> Date: Fri, 5 Nov 2021 14:59:05 + > From: Stuart Henderson > > On 2021/11/05 09:32, Paul de Weerd wrote: > > Linking brcmfmac43455-sdio.raspberrypi,4-model-b.txt (which is what is > > used with u-boot, I believe) to this name in /etc/firmware fixed bwfm0 > > for me (although performance isn't great, but that's also the case > > when using u-boot). > > btw I *don't* have that problem (1.31 here). wlan performance isn't great > either (70Mb on VHT-MCS0 mode 11ac / -45dBm reported) but usable. > (ethernet performance OTOH *is* pretty good - ~800Mb). Paul, Go into the firmware configuration menu and switch from ACPI to Device Tree (DT). That is what Stuart is using and should fix the wifi problem. > OpenBSD 7.0-current (GENERIC.MP) #1374: Wed Nov 3 15:40:43 MDT 2021 > dera...@arm64.openbsd.org:/usr/src/sys/arch/arm64/compile/GENERIC.MP > real mem = 4134588416 (3943MB) > avail mem = 3975053312 (3790MB) > random: good seed from bootblocks > mainbus0 at root: Raspberry Pi 4 Model B Rev 1.2 > psci0 at mainbus0: PSCI 1.1, SMCCC 1.2 > cpu0 at mainbus0 mpidr 0: ARM Cortex-A72 r0p3 > cpu0: 48KB 64b/line 3-way L1 PIPT I-cache, 32KB 64b/line 2-way L1 D-cache > cpu0: 1024KB 64b/line 16-way L2 cache > cpu0: CRC32,ASID16 > cpu1 at mainbus0 mpidr 1: ARM Cortex-A72 r0p3 > cpu1: 48KB 64b/line 3-way L1 PIPT I-cache, 32KB 64b/line 2-way L1 D-cache > cpu1: 1024KB 64b/line 16-way L2 cache > cpu1: CRC32,ASID16 > cpu2 at mainbus0 mpidr 2: ARM Cortex-A72 r0p3 > cpu2: 48KB 64b/line 3-way L1 PIPT I-cache, 32KB 64b/line 2-way L1 D-cache > cpu2: 1024KB 64b/line 16-way L2 cache > cpu2: CRC32,ASID16 > cpu3 at mainbus0 mpidr 3: ARM Cortex-A72 r0p3 > cpu3: 48KB 64b/line 3-way L1 PIPT I-cache, 32KB 64b/line 2-way L1 D-cache > cpu3: 1024KB 64b/line 16-way L2 cache > cpu3: CRC32,ASID16 > efi0 at mainbus0: UEFI 2.7 > efi0: https://github.com/pftf/RPi4 rev 0x1 > smbios0 at efi0: SMBIOS 3.3.0 > smbios0: vendor https://github.com/pftf/RPi4 version "UEFI Firmware v1.31" > date 09/09/2021 > smbios0: Raspberry Pi Foundation Raspberry Pi 4 Model B > apm0 at mainbus0 > "system" at mainbus0 not configured > "axi" at mainbus0 not configured > simplebus0 at mainbus0: "soc" > bcmclock0 at simplebus0 > bcmmbox0 at simplebus0 > bcmgpio0 at simplebus0 > bcmaux0 at simplebus0 > ampintc0 at simplebus0 nirq 256, ncpu 4 ipi: 0, 1: "interrupt-controller" > bcmtmon0 at simplebus0 > bcmdmac0 at simplebus0: DMA0 DMA2 DMA4 DMA5 DMA6 DMA7 DMA8 DMA9 > "timer" at simplebus0 not configured > pluart0 at simplebus0: console > com0 at simplebus0: ns16550, no working fifo > "local_intc" at simplebus0 not configured > bcmdog0 at simplebus0 > bcmirng0 at simplebus0 > "firmware" at simplebus0 not configured > "power" at simplebus0 not configured > "mailbox" at simplebus0 not configured > sdhc0 at simplebus0 > sdhc0: SDHC 3.0, 250 MHz base clock > sdmmc0 at sdhc0: 4-bit, sd high-speed, mmc high-speed > "gpiomem" at simplebus0 not configured > "fb" at simplebus0 not configured > "vcsm" at simplebus0 not configured > "clocks" at mainbus0 not configured > "phy" at mainbus0 not configured > "clk-27M" at mainbus0 not configured > "clk-108M" at mainbus0 not configured > simplebus1 at mainbus0: "emmc2bus" > sdhc1 at simplebus1 > sdhc1: SDHC 3.0, 100 MHz base clock > sdmmc1 at sdhc1: 8-bit, sd high-speed, mmc high-speed, ddr52, dma > "arm-pmu" at mainbus0 not configured > agtimer0 at mainbus0: 54000 kHz > simplebus2 at mainbus0: "scb" > bcmpcie0 at simplebus2 > pci0 at bcmpcie0 > ppb0 at pci0 dev 0 function 0 "Broadcom BCM2711" rev 0x10 > pci1 at ppb0 bus 1 > xhci0 at pci1 dev 0 function 0 "VIA VL805 xHCI" rev 0x01: intx, xHCI 1.0 > usb0 at xhci0: USB revision 3.0 > uhub0 at usb0 configuration 1 interface 0 "VIA xHCI root hub" rev 3.00/1.00 > addr 1 > bse0 at simplebus2: address dc:a6:32:8b:e1:b7 > brgphy0 at bse0 phy 1: BCM54210E 10/100/1000baseT PHY, rev. 2 > "dma" at simplebus2 not configured > "hevc-decoder" at simplebus2 not configured > "rpivid-local-intc" at simplebus2 not configured > "h264-decoder" at simplebus2 not configured > "vp9-decoder" at simplebus2 not configured > gpioleds0 at mainbus0: no LEDs > "sd_io_1v8_reg" at mainbus0 not configured > "sd_vcc_reg" at mainbus0 not configured > "fixedregulator_3v3" at mainbus0 not configured > "fixedregulator_5v0" at mainbus0 not configured > simplebus3 at mainbus0: "v3dbus" >
Re: raspberry pi 4 model b: xhci0: host system error
On 2021/11/05 09:32, Paul de Weerd wrote: > Linking brcmfmac43455-sdio.raspberrypi,4-model-b.txt (which is what is > used with u-boot, I believe) to this name in /etc/firmware fixed bwfm0 > for me (although performance isn't great, but that's also the case > when using u-boot). btw I *don't* have that problem (1.31 here). wlan performance isn't great either (70Mb on VHT-MCS0 mode 11ac / -45dBm reported) but usable. (ethernet performance OTOH *is* pretty good - ~800Mb). OpenBSD 7.0-current (GENERIC.MP) #1374: Wed Nov 3 15:40:43 MDT 2021 dera...@arm64.openbsd.org:/usr/src/sys/arch/arm64/compile/GENERIC.MP real mem = 4134588416 (3943MB) avail mem = 3975053312 (3790MB) random: good seed from bootblocks mainbus0 at root: Raspberry Pi 4 Model B Rev 1.2 psci0 at mainbus0: PSCI 1.1, SMCCC 1.2 cpu0 at mainbus0 mpidr 0: ARM Cortex-A72 r0p3 cpu0: 48KB 64b/line 3-way L1 PIPT I-cache, 32KB 64b/line 2-way L1 D-cache cpu0: 1024KB 64b/line 16-way L2 cache cpu0: CRC32,ASID16 cpu1 at mainbus0 mpidr 1: ARM Cortex-A72 r0p3 cpu1: 48KB 64b/line 3-way L1 PIPT I-cache, 32KB 64b/line 2-way L1 D-cache cpu1: 1024KB 64b/line 16-way L2 cache cpu1: CRC32,ASID16 cpu2 at mainbus0 mpidr 2: ARM Cortex-A72 r0p3 cpu2: 48KB 64b/line 3-way L1 PIPT I-cache, 32KB 64b/line 2-way L1 D-cache cpu2: 1024KB 64b/line 16-way L2 cache cpu2: CRC32,ASID16 cpu3 at mainbus0 mpidr 3: ARM Cortex-A72 r0p3 cpu3: 48KB 64b/line 3-way L1 PIPT I-cache, 32KB 64b/line 2-way L1 D-cache cpu3: 1024KB 64b/line 16-way L2 cache cpu3: CRC32,ASID16 efi0 at mainbus0: UEFI 2.7 efi0: https://github.com/pftf/RPi4 rev 0x1 smbios0 at efi0: SMBIOS 3.3.0 smbios0: vendor https://github.com/pftf/RPi4 version "UEFI Firmware v1.31" date 09/09/2021 smbios0: Raspberry Pi Foundation Raspberry Pi 4 Model B apm0 at mainbus0 "system" at mainbus0 not configured "axi" at mainbus0 not configured simplebus0 at mainbus0: "soc" bcmclock0 at simplebus0 bcmmbox0 at simplebus0 bcmgpio0 at simplebus0 bcmaux0 at simplebus0 ampintc0 at simplebus0 nirq 256, ncpu 4 ipi: 0, 1: "interrupt-controller" bcmtmon0 at simplebus0 bcmdmac0 at simplebus0: DMA0 DMA2 DMA4 DMA5 DMA6 DMA7 DMA8 DMA9 "timer" at simplebus0 not configured pluart0 at simplebus0: console com0 at simplebus0: ns16550, no working fifo "local_intc" at simplebus0 not configured bcmdog0 at simplebus0 bcmirng0 at simplebus0 "firmware" at simplebus0 not configured "power" at simplebus0 not configured "mailbox" at simplebus0 not configured sdhc0 at simplebus0 sdhc0: SDHC 3.0, 250 MHz base clock sdmmc0 at sdhc0: 4-bit, sd high-speed, mmc high-speed "gpiomem" at simplebus0 not configured "fb" at simplebus0 not configured "vcsm" at simplebus0 not configured "clocks" at mainbus0 not configured "phy" at mainbus0 not configured "clk-27M" at mainbus0 not configured "clk-108M" at mainbus0 not configured simplebus1 at mainbus0: "emmc2bus" sdhc1 at simplebus1 sdhc1: SDHC 3.0, 100 MHz base clock sdmmc1 at sdhc1: 8-bit, sd high-speed, mmc high-speed, ddr52, dma "arm-pmu" at mainbus0 not configured agtimer0 at mainbus0: 54000 kHz simplebus2 at mainbus0: "scb" bcmpcie0 at simplebus2 pci0 at bcmpcie0 ppb0 at pci0 dev 0 function 0 "Broadcom BCM2711" rev 0x10 pci1 at ppb0 bus 1 xhci0 at pci1 dev 0 function 0 "VIA VL805 xHCI" rev 0x01: intx, xHCI 1.0 usb0 at xhci0: USB revision 3.0 uhub0 at usb0 configuration 1 interface 0 "VIA xHCI root hub" rev 3.00/1.00 addr 1 bse0 at simplebus2: address dc:a6:32:8b:e1:b7 brgphy0 at bse0 phy 1: BCM54210E 10/100/1000baseT PHY, rev. 2 "dma" at simplebus2 not configured "hevc-decoder" at simplebus2 not configured "rpivid-local-intc" at simplebus2 not configured "h264-decoder" at simplebus2 not configured "vp9-decoder" at simplebus2 not configured gpioleds0 at mainbus0: no LEDs "sd_io_1v8_reg" at mainbus0 not configured "sd_vcc_reg" at mainbus0 not configured "fixedregulator_3v3" at mainbus0 not configured "fixedregulator_5v0" at mainbus0 not configured simplebus3 at mainbus0: "v3dbus" "bootloader" at mainbus0 not configured dt: 445 probes sdmmc1: can't enable card uhub1 at uhub0 port 1 configuration 1 interface 0 "VIA Labs USB2.0 Hub" rev 2.10/4.21 addr 2 bwfm0 at sdmmc0 function 1 manufacturer 0x02d0, product 0xa9a6 at sdmmc0 function 2 not configured manufacturer 0x02d0, product 0xa9a6 at sdmmc0 function 3 not configured uhub2 at uhub1 port 4 configuration 1 interface 0 "Genesys Logic USB2.0 Hub" rev 2.00/77.64 addr 3 uhidev0 at uhub2 port 3 configuration 1 interface 0 "RDing TEMPerV1.4" rev 2.00/0.01 addr 4 uhidev0: iclass 3/1, 1 report id ukbd0 at uhidev0 reportid 1: 8 variable keys, 5 key codes wskbd0 at ukbd0 mux 1 uhidev1 at uhub2 port
Re: raspberry pi 4 model b: xhci0: host system error
On Fri, Nov 05, 2021 at 09:32:52AM +0100, Paul de Weerd wrote: > I recently got an RPi4 for a project at home and had the same error. > > On Tue, Nov 02, 2021 at 02:09:29PM +, Klemens Nanni wrote: > | After reading through openbsd-arm after sthen's suggestion I only tried > | u-boot.bin from 6.9-release* and that lets 7.0-current xhci(4) attach. > | > | * U-Boot 2021.01 (Apr 16 2021 - 15:39:01 +1000) > > I tried the version from the latest u-boot pkg, but that didn't solve > the xhci issue. I ended up using the UEFI firmware (v1.32) from > https://github.com/pftf/RPi4 (found via the arm64 installation > instructions); with that, xhci works and USB devices behind it are > found and work (I tested with a ugold(4) temperature and humidity > sensor). Good to know that 1.32 is working as our INSTALL.arm64 mentions 1.21 as the (last) known to work version. > With UEFI, available memory went from 4GB to 3GB (not a blocker for > me) and bwfm(4) stopped working with this complaint: >From https://github.com/pftf/RPi4#additional-notes : A 3 GB RAM limit is enforced by default, even if you are using a Raspberry Pi 4 model that has 4 GB or 8 GB of RAM, on account that the OS must patch DMA access, to work around a hardware bug that is present in the Broadcom SoC. For Linux this usually translates to using a recent kernel (version 5.8 or later) and for Windows this requires the installation of a filter driver. If you are running an OS that has been adequately patched, you can disable the 3 GB limit by going to Device Manager → Raspberry Pi Configuration → Advanced Settings in the UEFI settings. Does that work for you?
Re: raspberry pi 4 model b: xhci0: host system error
I recently got an RPi4 for a project at home and had the same error. On Tue, Nov 02, 2021 at 02:09:29PM +, Klemens Nanni wrote: | After reading through openbsd-arm after sthen's suggestion I only tried | u-boot.bin from 6.9-release* and that lets 7.0-current xhci(4) attach. | | * U-Boot 2021.01 (Apr 16 2021 - 15:39:01 +1000) I tried the version from the latest u-boot pkg, but that didn't solve the xhci issue. I ended up using the UEFI firmware (v1.32) from https://github.com/pftf/RPi4 (found via the arm64 installation instructions); with that, xhci works and USB devices behind it are found and work (I tested with a ugold(4) temperature and humidity sensor). With UEFI, available memory went from 4GB to 3GB (not a blocker for me) and bwfm(4) stopped working with this complaint: bwfm0: failed loadfirmware of file brcmfmac43455-sdio.openbsd,acpi.txt Linking brcmfmac43455-sdio.raspberrypi,4-model-b.txt (which is what is used with u-boot, I believe) to this name in /etc/firmware fixed bwfm0 for me (although performance isn't great, but that's also the case when using u-boot). dmesg for u-boot and uefi below. Paul --- u-boot dmesg - OpenBSD 7.0-current (GENERIC.MP) #1374: Wed Nov 3 15:40:43 MDT 2021 dera...@arm64.openbsd.org:/usr/src/sys/arch/arm64/compile/GENERIC.MP real mem = 4124905472 (3933MB) avail mem = 3965665280 (3781MB) random: good seed from bootblocks mainbus0 at root: Raspberry Pi 4 Model B Rev 1.4 cpu0 at mainbus0 mpidr 0: ARM Cortex-A72 r0p3 cpu0: 48KB 64b/line 3-way L1 PIPT I-cache, 32KB 64b/line 2-way L1 D-cache cpu0: 1024KB 64b/line 16-way L2 cache cpu0: CRC32,ASID16 cpu1 at mainbus0 mpidr 1: ARM Cortex-A72 r0p3 cpu1: 48KB 64b/line 3-way L1 PIPT I-cache, 32KB 64b/line 2-way L1 D-cache cpu1: 1024KB 64b/line 16-way L2 cache cpu1: CRC32,ASID16 cpu2 at mainbus0 mpidr 2: ARM Cortex-A72 r0p3 cpu2: 48KB 64b/line 3-way L1 PIPT I-cache, 32KB 64b/line 2-way L1 D-cache cpu2: 1024KB 64b/line 16-way L2 cache cpu2: CRC32,ASID16 cpu3 at mainbus0 mpidr 3: ARM Cortex-A72 r0p3 cpu3: 48KB 64b/line 3-way L1 PIPT I-cache, 32KB 64b/line 2-way L1 D-cache cpu3: 1024KB 64b/line 16-way L2 cache cpu3: CRC32,ASID16 efi0 at mainbus0: UEFI 2.8 efi0: Das U-Boot rev 0x20211000 apm0 at mainbus0 "system" at mainbus0 not configured "axi" at mainbus0 not configured simplebus0 at mainbus0: "soc" bcmclock0 at simplebus0 bcmmbox0 at simplebus0 bcmgpio0 at simplebus0 bcmaux0 at simplebus0 ampintc0 at simplebus0 nirq 256, ncpu 4 ipi: 0, 1: "interrupt-controller" bcmtmon0 at simplebus0 bcmdmac0 at simplebus0: DMA0 DMA2 DMA4 DMA5 DMA6 DMA7 DMA8 DMA9 "timer" at simplebus0 not configured pluart0 at simplebus0: console "local_intc" at simplebus0 not configured bcmdog0 at simplebus0 bcmirng0 at simplebus0 "firmware" at simplebus0 not configured "power" at simplebus0 not configured "mailbox" at simplebus0 not configured sdhc0 at simplebus0 sdhc0: SDHC 3.0, 250 MHz base clock sdmmc0 at sdhc0: 4-bit, sd high-speed, mmc high-speed "gpiomem" at simplebus0 not configured "fb" at simplebus0 not configured "vcsm" at simplebus0 not configured "clocks" at mainbus0 not configured "phy" at mainbus0 not configured "clk-27M" at mainbus0 not configured "clk-108M" at mainbus0 not configured simplebus1 at mainbus0: "emmc2bus" sdhc1 at simplebus1 sdhc1: SDHC 3.0, 100 MHz base clock sdmmc1 at sdhc1: 8-bit, sd high-speed, mmc high-speed, ddr52, dma "arm-pmu" at mainbus0 not configured agtimer0 at mainbus0: 54000 kHz simplebus2 at mainbus0: "scb" bcmpcie0 at simplebus2 pci0 at bcmpcie0 ppb0 at pci0 dev 0 function 0 "Broadcom BCM2711" rev 0x20 pci1 at ppb0 bus 1 "VIA VL805 xHCI" rev 0x01 at pci1 dev 0 function 0 not configured bse0 at simplebus2: address e4:5f:01:5c:a2:d1 brgphy0 at bse0 phy 1: BCM54210E 10/100/1000baseT PHY, rev. 2 "dma" at simplebus2 not configured "hevc-decoder" at simplebus2 not configured "rpivid-local-intc" at simplebus2 not configured "h264-decoder" at simplebus2 not configured "vp9-decoder" at simplebus2 not configured gpioleds0 at mainbus0: no LEDs "sd_io_1v8_reg" at mainbus0 not configured "sd_vcc_reg" at mainbus0 not configured "fixedregulator_3v3" at mainbus0 not configured "fixedregulator_5v0" at mainbus0 not configured simplebus3 at mainbus0: "v3dbus" "bootloader" at mainbus0 not configured dt: 445 probes scsibus0 at sdmmc1: 2 targets, initiator 0 sd0 at scsibus0 targ 1 lun 0: removable sd0: 29492MB, 512 bytes/sector, 60399616 sectors bwfm0 at sdmmc0 function 1 manufacturer 0x02d0, product 0xa9a6 at sdmmc0 function 2 not configured manufacturer 0x02d0, product 0xa9a6 at sdmmc0 function 3 not configured vscsi0 at root scsibu
Re: raspberry pi 4 model b: xhci0: host system error
On Tue, Nov 02, 2021 at 11:44:25AM +0100, Mark Kettenis wrote: > > Date: Tue, 2 Nov 2021 00:05:49 + > > From: Klemens Nanni > > > > On Mon, Nov 01, 2021 at 10:40:33PM +, Stuart Henderson wrote: > > > On 2021/11/01 22:33, Klemens Nanni wrote: > > > 7.0-release is definitely known. EDK2-based definitely works. Older U-Boot > > > should work. > > > > > > > U-Boot 2021.10 (Oct 23 2021 - 05:09:34 -0600) > > > > > > Not sure the state of -current builds but I think that is probably a few > > > hours too early. Try updating the loader on your boot partition to > > > share/u-boot/rpi_arm64/u-boot.bin from u-boot-aarch64-2021.10p1 > > > > This image differs from the one contained in the snapshot and I tried it > > but with no avail: same "host system error". > > > > I'll look further into it. > > So my u-boot "fix" didn't work. I'll probably look into fixing the > kernel properly. But if you want to see if reverting more u-boot > commits helps, go ahead. After reading through openbsd-arm after sthen's suggestion I only tried u-boot.bin from 6.9-release* and that lets 7.0-current xhci(4) attach. * U-Boot 2021.01 (Apr 16 2021 - 15:39:01 +1000)
Re: raspberry pi 4 model b: xhci0: host system error
> Date: Tue, 2 Nov 2021 00:05:49 + > From: Klemens Nanni > > On Mon, Nov 01, 2021 at 10:40:33PM +, Stuart Henderson wrote: > > On 2021/11/01 22:33, Klemens Nanni wrote: > > 7.0-release is definitely known. EDK2-based definitely works. Older U-Boot > > should work. > > > > > U-Boot 2021.10 (Oct 23 2021 - 05:09:34 -0600) > > > > Not sure the state of -current builds but I think that is probably a few > > hours too early. Try updating the loader on your boot partition to > > share/u-boot/rpi_arm64/u-boot.bin from u-boot-aarch64-2021.10p1 > > This image differs from the one contained in the snapshot and I tried it > but with no avail: same "host system error". > > I'll look further into it. So my u-boot "fix" didn't work. I'll probably look into fixing the kernel properly. But if you want to see if reverting more u-boot commits helps, go ahead.
Re: raspberry pi 4 model b: xhci0: host system error
On 2021/11/02 00:05, Klemens Nanni wrote: > On Mon, Nov 01, 2021 at 10:40:33PM +, Stuart Henderson wrote: > > On 2021/11/01 22:33, Klemens Nanni wrote: > > 7.0-release is definitely known. EDK2-based definitely works. Older U-Boot > > should work. > > > > > U-Boot 2021.10 (Oct 23 2021 - 05:09:34 -0600) > > > > Not sure the state of -current builds but I think that is probably a few > > hours too early. Try updating the loader on your boot partition to > > share/u-boot/rpi_arm64/u-boot.bin from u-boot-aarch64-2021.10p1 > > This image differs from the one contained in the snapshot and I tried it > but with no avail: same "host system error". > > I'll look further into it. > see the "USB keyboard stops working on RPI4" thread on arm@ if you haven't already
Re: raspberry pi 4 model b: xhci0: host system error
On Mon, Nov 01, 2021 at 10:40:33PM +, Stuart Henderson wrote: > On 2021/11/01 22:33, Klemens Nanni wrote: > 7.0-release is definitely known. EDK2-based definitely works. Older U-Boot > should work. > > > U-Boot 2021.10 (Oct 23 2021 - 05:09:34 -0600) > > Not sure the state of -current builds but I think that is probably a few > hours too early. Try updating the loader on your boot partition to > share/u-boot/rpi_arm64/u-boot.bin from u-boot-aarch64-2021.10p1 This image differs from the one contained in the snapshot and I tried it but with no avail: same "host system error". I'll look further into it.
Re: raspberry pi 4 model b: xhci0: host system error
On 2021/11/01 22:33, Klemens Nanni wrote: > Neither RAMDISK nor GENERIC.MP from snapshots boot on my Raspberry 4 > Model B unless I disable xhci(4). > > I flashed miniroot70.img to an SD card, booted from it, did a default > install to it and booted the new system from it. > > Both times, `boot /bsd -c' and "disable xhci" were needed to bypass the > hard hang; after that, the system is fully functional. > > Same story with 7.0 release. > > No USB device is connected. > > I made no modification to u-boot, neither did I use the EDK2 based UEFI > firmware. > > FWIW, this happens with stock EEPROM firwmare dating a few months back > as well as the latest version obtained via `rpi-eeprom-update -a -d' on > Raspberry OS Lite. > > > Is this a known error? > Something missing in u-boot? 7.0-release is definitely known. EDK2-based definitely works. Older U-Boot should work. > U-Boot 2021.10 (Oct 23 2021 - 05:09:34 -0600) Not sure the state of -current builds but I think that is probably a few hours too early. Try updating the loader on your boot partition to share/u-boot/rpi_arm64/u-boot.bin from u-boot-aarch64-2021.10p1 > > DRAM: 7.9 GiB > RPI 4 Model B (0xd03114) > MMC: mmcnr@7e30: 1, emmc2@7e34: 0 > Loading Environment from FAT... Unable to read "uboot.env" from mmc0:1... In: >serial > Out: vidconsole > Err: vidconsole > Net: eth0: ethernet@7d58 > PCIe BRCM: link up, 5.0 Gbps x1 (SSC) > starting USB... > Bus xhci_pci: Register 5000420 NbrPorts 5 > Starting the controller > USB XHCI 1.00 > scanning bus xhci_pci for devices... 2 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 > Scanning mmc 0:1... > libfdt fdt_check_header(): FDT_ERR_BADMAGIC > Card did not respond to voltage select! : -110 > Scanning disk mm...@7e30.blk... > Disk mm...@7e30.blk not ready > Scanning disk em...@7e34.blk... > Found 3 disks > No EFI system partition > BootOrder not defined > EFI boot manager: Cannot load any image > Found EFI removable media binary efi/boot/bootaa64.efi > 170790 bytes read in 34 ms (4.8 MiB/s) > libfdt fdt_check_header(): FDT_ERR_BADMAGIC > Booting /efi\boot\bootaa64.efi > disks: sd0* > >> OpenBSD/arm64 BOOTAA64 1.6 > boot> b /bsd -c > booting sd0a:/bsd: 9107364+1900048+573712+827488 > [667656+109+1098336+640675]=0xfa1eb0 > type 0x0 pa 0x0 va 0x0 pages 0x1 attr 0x8 > type 0x7 pa 0x1000 va 0x1000 pages 0x1ff attr 0x8 > type 0x2 pa 0x20 va 0x20 pages 0x4000 attr 0x8 > type 0x7 pa 0x420 va 0x420 pages 0x3cf0 attr 0x8 > type 0x9 pa 0x7ef va 0x7ef pages 0x20 attr 0x8 > type 0x7 pa 0x7f1 va 0x7f1 pages 0x31ee2 attr 0x8 > type 0x2 pa 0x39df2000 va 0x39df2000 pages 0xe attr 0x8 > type 0x4 pa 0x39e0 va 0x39e0 pages 0x1 attr 0x8 > type 0x7 pa 0x39e01000 va 0x39e01000 pages 0x1 attr 0x8 > type 0x2 pa 0x39e02000 va 0x39e02000 pages 0x100 attr 0x8 > type 0x1 pa 0x39f02000 va 0x39f02000 pages 0x2a attr 0x8 > type 0x4 pa 0x39f2c000 va 0x39f2c000 pages 0x8 attr 0x8 > type 0x6 pa 0x39f34000 va 0x1b7302 pages 0x1 attr 0x8008 > type 0x4 pa 0x39f35000 va 0x39f35000 pages 0x3 attr 0x8 > type 0x6 pa 0x39f38000 va 0x1b73024000 pages 0x3 attr 0x8008 > type 0x4 pa 0x39f3b000 va 0x39f3b000 pages 0x1 attr 0x8 > type 0x6 pa 0x39f3c000 va 0x1b73028000 pages 0x4 attr 0x8008 > type 0x4 pa 0x39f4 va 0x39f4 pages 0x8 attr 0x8 > type 0x2 pa 0x39f48000 va 0x39f48000 pages 0x1408 attr 0x8 > type 0x5 pa 0x3b35 va 0x1b7443c000 pages 0x10 attr 0x8008 > type 0x2 pa 0x3b36 va 0x3b36 pages 0xa0 attr 0x8 > type 0x0 pa 0x3ef5c000 va 0x3ef5c000 pages 0x1 attr 0x8 > type 0x4 pa 0x4000 va 0x4000 pages 0xbc000 attr 0x8 > type 0xb pa 0xfe10 va 0x1b7444c000 pages 0x1 attr 0x8000 > type 0x4 pa 0x1 va 0x1 pages 0x10 attr 0x8 > [ using 2407744 bytes of bsd ELF symbol table ] > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > Copyright (c) 1995-2021 OpenBSD. All rights reserved. https://www.OpenBSD.org > > OpenBSD 7.0-current (GENERIC.MP) #1369: Sat Oct 30 22:11:08 MDT 2021 > dera...@arm64.openbsd.org:/usr/src/sys/arch/arm64/compile/GENERIC.MP > real mem = 8419872768 (8029MB) > avail mem = 8128700416 (7752MB) > User Kernel Config > UKC> enable xhci > 156 xhci* enabled > 219 xhci* enabled > 340 xhci* enabled > UKC> exit > Continuing... > random: good seed from bootblocks > mainbus0 at root: Raspberry Pi 4 Model
raspberry pi 4 model b: xhci0: host system error
Neither RAMDISK nor GENERIC.MP from snapshots boot on my Raspberry 4 Model B unless I disable xhci(4). I flashed miniroot70.img to an SD card, booted from it, did a default install to it and booted the new system from it. Both times, `boot /bsd -c' and "disable xhci" were needed to bypass the hard hang; after that, the system is fully functional. Same story with 7.0 release. No USB device is connected. I made no modification to u-boot, neither did I use the EDK2 based UEFI firmware. FWIW, this happens with stock EEPROM firwmare dating a few months back as well as the latest version obtained via `rpi-eeprom-update -a -d' on Raspberry OS Lite. Is this a known error? Something missing in u-boot? U-Boot 2021.10 (Oct 23 2021 - 05:09:34 -0600) DRAM: 7.9 GiB RPI 4 Model B (0xd03114) MMC: mmcnr@7e30: 1, emmc2@7e34: 0 Loading Environment from FAT... Unable to read "uboot.env" from mmc0:1... In: serial Out: vidconsole Err: vidconsole Net: eth0: ethernet@7d58 PCIe BRCM: link up, 5.0 Gbps x1 (SSC) starting USB... Bus xhci_pci: Register 5000420 NbrPorts 5 Starting the controller USB XHCI 1.00 scanning bus xhci_pci for devices... 2 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 Scanning mmc 0:1... libfdt fdt_check_header(): FDT_ERR_BADMAGIC Card did not respond to voltage select! : -110 Scanning disk mm...@7e30.blk... Disk mm...@7e30.blk not ready Scanning disk em...@7e34.blk... Found 3 disks No EFI system partition BootOrder not defined EFI boot manager: Cannot load any image Found EFI removable media binary efi/boot/bootaa64.efi 170790 bytes read in 34 ms (4.8 MiB/s) libfdt fdt_check_header(): FDT_ERR_BADMAGIC Booting /efi\boot\bootaa64.efi disks: sd0* >> OpenBSD/arm64 BOOTAA64 1.6 boot> b /bsd -c booting sd0a:/bsd: 9107364+1900048+573712+827488 [667656+109+1098336+640675]=0xfa1eb0 type 0x0 pa 0x0 va 0x0 pages 0x1 attr 0x8 type 0x7 pa 0x1000 va 0x1000 pages 0x1ff attr 0x8 type 0x2 pa 0x20 va 0x20 pages 0x4000 attr 0x8 type 0x7 pa 0x420 va 0x420 pages 0x3cf0 attr 0x8 type 0x9 pa 0x7ef va 0x7ef pages 0x20 attr 0x8 type 0x7 pa 0x7f1 va 0x7f1 pages 0x31ee2 attr 0x8 type 0x2 pa 0x39df2000 va 0x39df2000 pages 0xe attr 0x8 type 0x4 pa 0x39e0 va 0x39e0 pages 0x1 attr 0x8 type 0x7 pa 0x39e01000 va 0x39e01000 pages 0x1 attr 0x8 type 0x2 pa 0x39e02000 va 0x39e02000 pages 0x100 attr 0x8 type 0x1 pa 0x39f02000 va 0x39f02000 pages 0x2a attr 0x8 type 0x4 pa 0x39f2c000 va 0x39f2c000 pages 0x8 attr 0x8 type 0x6 pa 0x39f34000 va 0x1b7302 pages 0x1 attr 0x8008 type 0x4 pa 0x39f35000 va 0x39f35000 pages 0x3 attr 0x8 type 0x6 pa 0x39f38000 va 0x1b73024000 pages 0x3 attr 0x8008 type 0x4 pa 0x39f3b000 va 0x39f3b000 pages 0x1 attr 0x8 type 0x6 pa 0x39f3c000 va 0x1b73028000 pages 0x4 attr 0x8008 type 0x4 pa 0x39f4 va 0x39f4 pages 0x8 attr 0x8 type 0x2 pa 0x39f48000 va 0x39f48000 pages 0x1408 attr 0x8 type 0x5 pa 0x3b35 va 0x1b7443c000 pages 0x10 attr 0x8008 type 0x2 pa 0x3b36 va 0x3b36 pages 0xa0 attr 0x8 type 0x0 pa 0x3ef5c000 va 0x3ef5c000 pages 0x1 attr 0x8 type 0x4 pa 0x4000 va 0x4000 pages 0xbc000 attr 0x8 type 0xb pa 0xfe10 va 0x1b7444c000 pages 0x1 attr 0x8000 type 0x4 pa 0x1 va 0x1 pages 0x10 attr 0x8 [ using 2407744 bytes of bsd ELF symbol table ] Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2021 OpenBSD. All rights reserved. https://www.OpenBSD.org OpenBSD 7.0-current (GENERIC.MP) #1369: Sat Oct 30 22:11:08 MDT 2021 dera...@arm64.openbsd.org:/usr/src/sys/arch/arm64/compile/GENERIC.MP real mem = 8419872768 (8029MB) avail mem = 8128700416 (7752MB) User Kernel Config UKC> enable xhci 156 xhci* enabled 219 xhci* enabled 340 xhci* enabled UKC> exit Continuing... random: good seed from bootblocks mainbus0 at root: Raspberry Pi 4 Model B Rev 1.4 cpu0 at mainbus0 mpidr 0: ARM Cortex-A72 r0p3 cpu0: 48KB 64b/line 3-way L1 PIPT I-cache, 32KB 64b/line 2-way L1 D-cache cpu0: 1024KB 64b/line 16-way L2 cache cpu0: CRC32,ASID16 cpu1 at mainbus0 mpidr 1: ARM Cortex-A72 r0p3 cpu1: 48KB 64b/line 3-way L1 PIPT I-cache, 32KB 64b/line 2-way L1 D-cache cpu1: 1024KB 64b/line 16-way L2 cache cpu1: CRC32,ASID16 cpu2 at mainbus0 mpidr 2: ARM Cortex-A72 r0p3 cpu2: 48KB 64b/line 3-way L1 PIPT I-cache, 32KB 64b/line 2-way L1 D-cache cpu2: 1024KB 64b/line 16-way L2 cache cpu2: CRC32,ASID16 cpu3 at mainbus0 mpidr 3: ARM Cortex-A72 r0p3 cpu3: 48KB 64b/line 3-way L1 PIPT I-cache, 32KB 64b/line 2-way L1 D-cache cpu3: 1024KB 64b/line 16-way L2 cache cpu3: CRC32,ASID16 efi0 at mainbus0: UEFI 2.8 efi0: Das U-Boot rev 0x20211000 apm0 at mainbus0 simplefb0 at mainbus0: 1824x984, 32bpp wsdisplay0 at simplefb0 mux
Re: Raspberry Pi 4 Model B
On Fri, 23 Jul 2021 23:17:47 +1000
Jonathan Gray wrote:
> On Fri, Jul 23, 2021 at 02:32:33PM +0200, Mark Kettenis wrote:
> > > Date: Fri, 23 Jul 2021 13:13:27 +0200
> > > From: Marcus Glocker
> > >
> > > On Thu, 22 Jul 2021 23:44:54 +0200
> > > Marcus Glocker wrote:
> > >
> > > > On Thu, 22 Jul 2021 23:07:30 +0200 (CEST)
> > > > Mark Kettenis wrote:
> > > >
> > > > > > Date: Thu, 22 Jul 2021 22:59:28 +0200
> > > > > > From: Marcus Glocker
> > > > > >
> > > > > > I can install and boot an 6.9 on it (although XHCI fails to
> > > > > > initialize), but with a miniroot69.img snapshot of today,
> > > > > > I'm getting a panic with the RAMDISK kernel before the
> > > > > > installation procedure starts.
> > > > > >
> > > > > > Is this something known?
> > > > >
> > > > > There was a similar report the other day. No clue;
> > > > > do_el0_error should never happen.
> > > >
> > > > I see. At least when I try to boot a GENERIC kernel, I get a
> > > > little more trace:
> > > >
> > > > root on sd0a (90e0fb227dbf7852.a) swap on sd0b dump on sd0b
> > > > WARNING: CHECK AND RESET THE DATE!
> > > > gpio0 at bcmgpio0: 58 pins
> > > > bwfm0: address dc:a6:32:da:a4:73
> > > > panic: do_el0_error
> > > > Stopped at panic+0x160:cmp w21, #0x0
> > > > TIDPIDUID PRFLAGS PFLAGS CPU COMMAND
> > > > * 12906 15435 0 0 00 init
> > > > 195339 1 0 0x2 02K init
> > > > db_enter() at panic+0x15c
> > > > panic() at do_el0_error+0x10
> > > > radeon_combios_check_hardcoded_edid() at handle_el0_error+0x74
> > > > handle_el0_error() at 0x1788fadeb0
> > > > address 0x7d0828 is invalid
> > > > https://www.openbsd.org/ddb.html describes the minimum info
> > > > required in bug reports. Insufficient info makes it difficult
> > > > to find and fix bugs. ddb{0}>
> > > >
> > > > radeon_combios_check_hardcoded_edid()? Need to dig a little
> > > > deeper ...
> > >
> > > When I disable bcmpcie(4) the panic is gone and the RPI4 boots up
> > > fine. I also noticed that the bus_space_writes e.g. in
> > > bcmpcie_attach() take very long to complete. It's like 5-10
> > > seconds for one bus write to complete. Any idea what could go
> > > wrong in that area?
> >
> > eeprom -p output could help
> >
> > also, you could try older u-boot versions.
>
> and/or newer versions as the report mentioned U-Boot 2021.04
>
> arm64 snapshots don't seem to have 2021.07 yet which is available in
> ports and amd64 packages.
OK, thanks for the hints. bcmpcie(4) works with U-Boot 2021.01 and
current. I'll have a try what happens with U-Boot 2021.07 next.
xhci(4) is still unhappy:
bcmpcie0 at simplebus3
pci0 at bcmpcie0
ppb0 at pci0 dev 0 function 0 "Broadcom BCM2711" rev 0x10
pci1 at ppb0 bus 1
xhci0 at pci1 dev 0 function 0 "VIA VL805 xHCI" rev 0x01: intx, xHCI 1.0
xhci0: reset timeout
xhci0: init failed, error=5
I'll play around with that a bit more.
FWIW, this is the eeprom -p output using U-Boot 2021.04:
Node 0x48
name: ''
memreserve: 3b40.04c0
serial-number: '1000f6cc6310'
compatible: 'raspberrypi,4-model-b' + 'brcm,bcm2711'
model: 'Raspberry Pi 4 Model B Rev 1.4'
#address-cells: 0002
#size-cells: 0001
interrupt-parent: 0001
Node 0x110
name: 'framebuffer'
compatible: 'simple-framebuffer'
status: 'disabled'
Node 0x15c
name: 'system'
linux,serial: 1000.f6cc6310
linux,revision: 00d03114
Node 0x190
name: 'axi'
Node 0x198
name: 'vc_mem'
reg: 3ec0.4000.c000
Node 0x1c4
name: 'aliases'
i2c_arm: '/soc/i2c@7e804000'
i2c: '/soc/i2c@7e804000'
i2c_vc: '/soc/i2c0mux/i2c@0'
serial0: '/soc/serial@7e201000'
serial1: '/soc/serial@7e215040'
emmc2bus: '/emmc2bus'
ethernet0: '/scb/ethernet@7d58'
pcie0: '/scb/pcie@7d50'
blconfig: '/reserved-memory/nvram@0'
audio: '/soc/mailbox@7e00b840/bcm2835_audio'
aux: '/soc/aux@7e215000'
sound: '/soc/sound'
soc: '/soc'
dma: '/soc/dma@7e007000'
watchdog: '/soc/watchdog@7e10'
random:
Re: Raspberry Pi 4 Model B
On Fri, Jul 23, 2021 at 02:32:33PM +0200, Mark Kettenis wrote:
> > Date: Fri, 23 Jul 2021 13:13:27 +0200
> > From: Marcus Glocker
> >
> > On Thu, 22 Jul 2021 23:44:54 +0200
> > Marcus Glocker wrote:
> >
> > > On Thu, 22 Jul 2021 23:07:30 +0200 (CEST)
> > > Mark Kettenis wrote:
> > >
> > > > > Date: Thu, 22 Jul 2021 22:59:28 +0200
> > > > > From: Marcus Glocker
> > > > >
> > > > > I can install and boot an 6.9 on it (although XHCI fails to
> > > > > initialize), but with a miniroot69.img snapshot of today, I'm
> > > > > getting a panic with the RAMDISK kernel before the installation
> > > > > procedure starts.
> > > > >
> > > > > Is this something known?
> > > >
> > > > There was a similar report the other day. No clue; do_el0_error
> > > > should never happen.
> > >
> > > I see. At least when I try to boot a GENERIC kernel, I get a little
> > > more trace:
> > >
> > > root on sd0a (90e0fb227dbf7852.a) swap on sd0b dump on sd0b
> > > WARNING: CHECK AND RESET THE DATE!
> > > gpio0 at bcmgpio0: 58 pins
> > > bwfm0: address dc:a6:32:da:a4:73
> > > panic: do_el0_error
> > > Stopped at panic+0x160:cmp w21, #0x0
> > > TIDPIDUID PRFLAGS PFLAGS CPU COMMAND
> > > * 12906 15435 0 0 00 init
> > > 195339 1 0 0x2 02K init
> > > db_enter() at panic+0x15c
> > > panic() at do_el0_error+0x10
> > > radeon_combios_check_hardcoded_edid() at handle_el0_error+0x74
> > > handle_el0_error() at 0x1788fadeb0
> > > address 0x7d0828 is invalid
> > > https://www.openbsd.org/ddb.html describes the minimum info required
> > > in bug reports. Insufficient info makes it difficult to find and fix
> > > bugs. ddb{0}>
> > >
> > > radeon_combios_check_hardcoded_edid()? Need to dig a little deeper
> > > ...
> >
> > When I disable bcmpcie(4) the panic is gone and the RPI4 boots up fine.
> > I also noticed that the bus_space_writes e.g. in bcmpcie_attach() take
> > very long to complete. It's like 5-10 seconds for one bus write to
> > complete. Any idea what could go wrong in that area?
>
> eeprom -p output could help
>
> also, you could try older u-boot versions.
and/or newer versions as the report mentioned U-Boot 2021.04
arm64 snapshots don't seem to have 2021.07 yet which is available in
ports and amd64 packages.
Re: Raspberry Pi 4 Model B
> Date: Fri, 23 Jul 2021 13:13:27 +0200
> From: Marcus Glocker
>
> On Thu, 22 Jul 2021 23:44:54 +0200
> Marcus Glocker wrote:
>
> > On Thu, 22 Jul 2021 23:07:30 +0200 (CEST)
> > Mark Kettenis wrote:
> >
> > > > Date: Thu, 22 Jul 2021 22:59:28 +0200
> > > > From: Marcus Glocker
> > > >
> > > > I can install and boot an 6.9 on it (although XHCI fails to
> > > > initialize), but with a miniroot69.img snapshot of today, I'm
> > > > getting a panic with the RAMDISK kernel before the installation
> > > > procedure starts.
> > > >
> > > > Is this something known?
> > >
> > > There was a similar report the other day. No clue; do_el0_error
> > > should never happen.
> >
> > I see. At least when I try to boot a GENERIC kernel, I get a little
> > more trace:
> >
> > root on sd0a (90e0fb227dbf7852.a) swap on sd0b dump on sd0b
> > WARNING: CHECK AND RESET THE DATE!
> > gpio0 at bcmgpio0: 58 pins
> > bwfm0: address dc:a6:32:da:a4:73
> > panic: do_el0_error
> > Stopped at panic+0x160:cmp w21, #0x0
> > TIDPIDUID PRFLAGS PFLAGS CPU COMMAND
> > * 12906 15435 0 0 00 init
> > 195339 1 0 0x2 02K init
> > db_enter() at panic+0x15c
> > panic() at do_el0_error+0x10
> > radeon_combios_check_hardcoded_edid() at handle_el0_error+0x74
> > handle_el0_error() at 0x1788fadeb0
> > address 0x7d0828 is invalid
> > https://www.openbsd.org/ddb.html describes the minimum info required
> > in bug reports. Insufficient info makes it difficult to find and fix
> > bugs. ddb{0}>
> >
> > radeon_combios_check_hardcoded_edid()? Need to dig a little deeper
> > ...
>
> When I disable bcmpcie(4) the panic is gone and the RPI4 boots up fine.
> I also noticed that the bus_space_writes e.g. in bcmpcie_attach() take
> very long to complete. It's like 5-10 seconds for one bus write to
> complete. Any idea what could go wrong in that area?
eeprom -p output could help
also, you could try older u-boot versions.
Re: Raspberry Pi 4 Model B
On Thu, 22 Jul 2021 23:07:30 +0200 (CEST)
Mark Kettenis wrote:
> > Date: Thu, 22 Jul 2021 22:59:28 +0200
> > From: Marcus Glocker
> >
> > I can install and boot an 6.9 on it (although XHCI fails to
> > initialize), but with a miniroot69.img snapshot of today, I'm
> > getting a panic with the RAMDISK kernel before the installation
> > procedure starts.
> >
> > Is this something known?
>
> There was a similar report the other day. No clue; do_el0_error
> should never happen.
I see. At least when I try to boot a GENERIC kernel, I get a little
more trace:
root on sd0a (90e0fb227dbf7852.a) swap on sd0b dump on sd0b
WARNING: CHECK AND RESET THE DATE!
gpio0 at bcmgpio0: 58 pins
bwfm0: address dc:a6:32:da:a4:73
panic: do_el0_error
Stopped at panic+0x160:cmp w21, #0x0
TIDPIDUID PRFLAGS PFLAGS CPU COMMAND
* 12906 15435 0 0 00 init
195339 1 0 0x2 02K init
db_enter() at panic+0x15c
panic() at do_el0_error+0x10
radeon_combios_check_hardcoded_edid() at handle_el0_error+0x74
handle_el0_error() at 0x1788fadeb0
address 0x7d0828 is invalid
https://www.openbsd.org/ddb.html describes the minimum info required in bug
reports. Insufficient info makes it difficult to find and fix bugs.
ddb{0}>
radeon_combios_check_hardcoded_edid()? Need to dig a little deeper ...
Re: Raspberry Pi 4 Model B
> Date: Thu, 22 Jul 2021 22:59:28 +0200 > From: Marcus Glocker > > I can install and boot an 6.9 on it (although XHCI fails to > initialize), but with a miniroot69.img snapshot of today, I'm getting a > panic with the RAMDISK kernel before the installation procedure starts. > > Is this something known? There was a similar report the other day. No clue; do_el0_error should never happen. > U-Boot 2021.04 (May 06 2021 - 13:23:28 -0600) > > DRAM: 7.9 GiB > RPI 4 Model B (0xd03114) > MMC: mmcnr@7e30: 1, emmc2@7e34: 0 > Loading Environment from FAT... *** Warning - bad CRC, using default > environment > > In:serial > Out: vidconsole > Err: vidconsole > Net: eth0: ethernet@7d58 > PCIe BRCM: link up, 5.0 Gbps x1 (SSC) > starting USB... > Bus xhci_pci: Register 5000420 NbrPorts 5 > Starting the controller > USB XHCI 1.00 > scanning bus xhci_pci for devices... 2 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 > Scanning mmc 0:1... > libfdt fdt_check_header(): FDT_ERR_BADMAGIC > Card did not respond to voltage select! : -110 > Scanning disk mm...@7e30.blk... > Disk mm...@7e30.blk not ready > Scanning disk em...@7e34.blk... > ** Unrecognized filesystem type ** > Found 3 disks > No EFI system partition > BootOrder not defined > EFI boot manager: Cannot load any image > Found EFI removable media binary efi/boot/bootaa64.efi > 170646 bytes read in 35 ms (4.6 MiB/s) > libfdt fdt_check_header(): FDT_ERR_BADMAGIC > Booting /efi\boot\bootaa64.efi > disks: sd0* > >> OpenBSD/arm64 BOOTAA64 1.6 > boot> > cannot open sd0a:/etc/random.seed: No such file or directory > booting sd0a:/bsd: 2561088+696988+13013064+633000 > [214440+109+592320+231137]=0x1401370 > type 0x0 pa 0x0 va 0x0 pages 0x1 attr 0x8 > type 0x7 pa 0x1000 va 0x1000 pages 0x1ff attr 0x8 > type 0x2 pa 0x20 va 0x20 pages 0x4000 attr 0x8 > type 0x7 pa 0x420 va 0x420 pages 0x3cf0 attr 0x8 > type 0x9 pa 0x7ef va 0x7ef pages 0x20 attr 0x8 > type 0x7 pa 0x7f1 va 0x7f1 pages 0x31ef1 attr 0x8 > type 0x4 pa 0x39e01000 va 0x39e01000 pages 0x1 attr 0x8 > type 0x7 pa 0x39e02000 va 0x39e02000 pages 0x1 attr 0x8 > type 0x2 pa 0x39e03000 va 0x39e03000 pages 0x100 attr 0x8 > type 0x1 pa 0x39f03000 va 0x39f03000 pages 0x2a attr 0x8 > type 0x0 pa 0x39f2d000 va 0x39f2d000 pages 0x7 attr 0x8 > type 0x4 pa 0x39f34000 va 0x39f34000 pages 0x1 attr 0x8 > type 0x6 pa 0x39f35000 va 0x7a3797000 pages 0x1 attr 0x8008 > type 0x4 pa 0x39f36000 va 0x39f36000 pages 0x2 attr 0x8 > type 0x0 pa 0x39f38000 va 0x39f38000 pages 0x1 attr 0x8 > type 0x6 pa 0x39f39000 va 0x7a379b000 pages 0x3 attr 0x8008 > type 0x4 pa 0x39f3c000 va 0x39f3c000 pages 0x1 attr 0x8 > type 0x6 pa 0x39f3d000 va 0x7a379f000 pages 0x4 attr 0x8008 > type 0x0 pa 0x39f41000 va 0x39f41000 pages 0x1 attr 0x8 > type 0x4 pa 0x39f42000 va 0x39f42000 pages 0x1 attr 0x8 > type 0x0 pa 0x39f43000 va 0x39f43000 pages 0x1 attr 0x8 > type 0x4 pa 0x39f44000 va 0x39f44000 pages 0x2 attr 0x8 > type 0x0 pa 0x39f46000 va 0x39f46000 pages 0x1 attr 0x8 > type 0x4 pa 0x39f47000 va 0x39f47000 pages 0x2 attr 0x8 > type 0x2 pa 0x39f49000 va 0x39f49000 pages 0x1407 attr 0x8 > type 0x5 pa 0x3b35 va 0x7a4bb2000 pages 0x10 attr 0x8008 > type 0x2 pa 0x3b36 va 0x3b36 pages 0xa0 attr 0x8 > type 0x0 pa 0x3ef5c000 va 0x3ef5c000 pages 0x1 attr 0x8 > type 0x4 pa 0x4000 va 0x4000 pages 0xbc000 attr 0x8 > type 0xb pa 0xfe10 va 0x7a4bc2000 pages 0x1 attr 0x8000 > type 0x4 pa 0x1 va 0x1 pages 0x10 attr 0x8 > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > Copyright (c) 1995-2021 OpenBSD. All rights reserved. https://www.OpenBSD.org > > OpenBSD 6.9-current (RAMDISK) #1176: Thu Jul 22 01:02:54 MDT 2021 > dera...@arm64.openbsd.org:/usr/src/sys/arch/arm64/compile/RAMDISK > real mem = 8419934208 (8029MB) > avail mem = 8124317696 (7747MB) > random: good seed from bootblocks > mainbus0 at root: Raspberry Pi 4 Model B Rev 1.4 > cpu0 at mainbus0 mpidr 0: ARM Cortex-A72 r0p3 > cpu0: 48KB 64b/line 3-way L1 PIPT I-cache, 32KB 64b/line 2-way L1 D-cache > cpu0: 1024KB 64b/line 16-way L2 cache > cpu0: CRC32,ASID16 > efi0 at mainbus0: UEFI 2.8 > efi0: Das U-Boot rev 0x20210400 > simplefb0 at mainbus0: 1920x1200, 32bpp > wsdisplay0 at simplefb0 > wsdisplay0: screen 0 added (std, vt100 emulation) > "system" at mainbus0 not configured > "axi" at mainbus0 not configur
Raspberry Pi 4 Model B
I can install and boot an 6.9 on it (although XHCI fails to initialize), but with a miniroot69.img snapshot of today, I'm getting a panic with the RAMDISK kernel before the installation procedure starts. Is this something known? U-Boot 2021.04 (May 06 2021 - 13:23:28 -0600) DRAM: 7.9 GiB RPI 4 Model B (0xd03114) MMC: mmcnr@7e30: 1, emmc2@7e34: 0 Loading Environment from FAT... *** Warning - bad CRC, using default environment In:serial Out: vidconsole Err: vidconsole Net: eth0: ethernet@7d58 PCIe BRCM: link up, 5.0 Gbps x1 (SSC) starting USB... Bus xhci_pci: Register 5000420 NbrPorts 5 Starting the controller USB XHCI 1.00 scanning bus xhci_pci for devices... 2 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 Scanning mmc 0:1... libfdt fdt_check_header(): FDT_ERR_BADMAGIC Card did not respond to voltage select! : -110 Scanning disk mm...@7e30.blk... Disk mm...@7e30.blk not ready Scanning disk em...@7e34.blk... ** Unrecognized filesystem type ** Found 3 disks No EFI system partition BootOrder not defined EFI boot manager: Cannot load any image Found EFI removable media binary efi/boot/bootaa64.efi 170646 bytes read in 35 ms (4.6 MiB/s) libfdt fdt_check_header(): FDT_ERR_BADMAGIC Booting /efi\boot\bootaa64.efi disks: sd0* >> OpenBSD/arm64 BOOTAA64 1.6 boot> cannot open sd0a:/etc/random.seed: No such file or directory booting sd0a:/bsd: 2561088+696988+13013064+633000 [214440+109+592320+231137]=0x1401370 type 0x0 pa 0x0 va 0x0 pages 0x1 attr 0x8 type 0x7 pa 0x1000 va 0x1000 pages 0x1ff attr 0x8 type 0x2 pa 0x20 va 0x20 pages 0x4000 attr 0x8 type 0x7 pa 0x420 va 0x420 pages 0x3cf0 attr 0x8 type 0x9 pa 0x7ef va 0x7ef pages 0x20 attr 0x8 type 0x7 pa 0x7f1 va 0x7f1 pages 0x31ef1 attr 0x8 type 0x4 pa 0x39e01000 va 0x39e01000 pages 0x1 attr 0x8 type 0x7 pa 0x39e02000 va 0x39e02000 pages 0x1 attr 0x8 type 0x2 pa 0x39e03000 va 0x39e03000 pages 0x100 attr 0x8 type 0x1 pa 0x39f03000 va 0x39f03000 pages 0x2a attr 0x8 type 0x0 pa 0x39f2d000 va 0x39f2d000 pages 0x7 attr 0x8 type 0x4 pa 0x39f34000 va 0x39f34000 pages 0x1 attr 0x8 type 0x6 pa 0x39f35000 va 0x7a3797000 pages 0x1 attr 0x8008 type 0x4 pa 0x39f36000 va 0x39f36000 pages 0x2 attr 0x8 type 0x0 pa 0x39f38000 va 0x39f38000 pages 0x1 attr 0x8 type 0x6 pa 0x39f39000 va 0x7a379b000 pages 0x3 attr 0x8008 type 0x4 pa 0x39f3c000 va 0x39f3c000 pages 0x1 attr 0x8 type 0x6 pa 0x39f3d000 va 0x7a379f000 pages 0x4 attr 0x8008 type 0x0 pa 0x39f41000 va 0x39f41000 pages 0x1 attr 0x8 type 0x4 pa 0x39f42000 va 0x39f42000 pages 0x1 attr 0x8 type 0x0 pa 0x39f43000 va 0x39f43000 pages 0x1 attr 0x8 type 0x4 pa 0x39f44000 va 0x39f44000 pages 0x2 attr 0x8 type 0x0 pa 0x39f46000 va 0x39f46000 pages 0x1 attr 0x8 type 0x4 pa 0x39f47000 va 0x39f47000 pages 0x2 attr 0x8 type 0x2 pa 0x39f49000 va 0x39f49000 pages 0x1407 attr 0x8 type 0x5 pa 0x3b35 va 0x7a4bb2000 pages 0x10 attr 0x8008 type 0x2 pa 0x3b36 va 0x3b36 pages 0xa0 attr 0x8 type 0x0 pa 0x3ef5c000 va 0x3ef5c000 pages 0x1 attr 0x8 type 0x4 pa 0x4000 va 0x4000 pages 0xbc000 attr 0x8 type 0xb pa 0xfe10 va 0x7a4bc2000 pages 0x1 attr 0x8000 type 0x4 pa 0x1 va 0x1 pages 0x10 attr 0x8 Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2021 OpenBSD. All rights reserved. https://www.OpenBSD.org OpenBSD 6.9-current (RAMDISK) #1176: Thu Jul 22 01:02:54 MDT 2021 dera...@arm64.openbsd.org:/usr/src/sys/arch/arm64/compile/RAMDISK real mem = 8419934208 (8029MB) avail mem = 8124317696 (7747MB) random: good seed from bootblocks mainbus0 at root: Raspberry Pi 4 Model B Rev 1.4 cpu0 at mainbus0 mpidr 0: ARM Cortex-A72 r0p3 cpu0: 48KB 64b/line 3-way L1 PIPT I-cache, 32KB 64b/line 2-way L1 D-cache cpu0: 1024KB 64b/line 16-way L2 cache cpu0: CRC32,ASID16 efi0 at mainbus0: UEFI 2.8 efi0: Das U-Boot rev 0x20210400 simplefb0 at mainbus0: 1920x1200, 32bpp wsdisplay0 at simplefb0 wsdisplay0: screen 0 added (std, vt100 emulation) "system" at mainbus0 not configured "axi" at mainbus0 not configured simplebus0 at mainbus0: "soc" bcmclock0 at simplebus0 bcmmbox0 at simplebus0 bcmgpio0 at simplebus0 bcmaux0 at simplebus0 ampintc0 at simplebus0 nirq 256, ncpu 4: "interrupt-controller" syscon0 at simplebus0: "avs-monitor" "thermal" at syscon0 not configured bcmdmac0 at simplebus0: DMA0 DMA2 DMA4 DMA5 DMA6 DMA7 DMA8 DMA9 "timer" at simplebus0 not configured pluart0 at simplebus0: console "local_intc" at simplebus0 not configured bcmdog0 at simplebus0 bcmirng0 at simplebus0 "firmware" at simplebus0 not configured "power" at simplebus0 not configured "mailbox" at
