From nobody Mon Apr 15 11:00:11 2024 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4VJ42W06gmz5G5Ss for ; Mon, 15 Apr 2024 11:00:19 +0000 (UTC) (envelope-from fred@thegalacticzoo.com) Received: from nmtao202.oxsus-vadesecure.net (mta-232b.oxsus-vadesecure.net [15.204.3.7]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4VJ42V1NRTz46kQ for ; Mon, 15 Apr 2024 11:00:18 +0000 (UTC) (envelope-from fred@thegalacticzoo.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=webcom.xion.oxcs.net header.s=mail1 header.b=dhsrNbOs; dmarc=pass (policy=quarantine) header.from=thegalacticzoo.com; spf=pass (mx1.freebsd.org: domain of fred@thegalacticzoo.com designates 15.204.3.7 as permitted sender) smtp.mailfrom=fred@thegalacticzoo.com; arc=pass ("oxsus-vadesecure.net:s=arc-202309-rsa2048:i=1") ARC-Seal: i=1; a=rsa-sha256; d=oxsus-vadesecure.net; s=arc-202309-rsa2048; t=1713178813; cv=none; b=jQPl+HRy5OwV1/B8wRA+GpTdb/qdP9lFpdEU/G/Wr79jjLNy4tFgHGQdyB2hDuU6MaYkaVQtx/pNrrrBKIlpD30dZwmmM/V4xxWtGi2sCG85fFXuoa3H/lDN/gXp6YdPlVMI7RwaOd84WrM2B2YDo9yxGUuC8fdDou/yf0IhlBpQjwrCQYgpYRiOP8khkFvEqmAJeRPuqcPkBRHoGS9exvl2ril0siNzWLWrD91/UoQg7tlcTOzftY4AyDinP34nAPfd0RDV+xHlxS1spDxkkesdxDbYMx3g96fK26ehNyXqa9cDT49NtmhJh1rRh0oSKMGIRINyUSH6IZs7QdteJA== ARC-Message-Signature: i=1; a=rsa-sha256; d=oxsus-vadesecure.net; s=arc-202309-rsa2048; t=1713178813; c=relaxed/relaxed; h=from:reply-to:subject:date:to:cc:resent-date:resent-from:resent-to:resent-cc:in-reply-to:references:list-id:list-help:list-unsubscribe:list-subscribe:list-post:list-owner:list-archive; bh=S3pvNzfwOtLaJZA+HnVJBa9S5rsKD0bpcyCAnoqJJO8=; b=jHI+dzrYL+V4bvr8egE4Er4EFqg4+M4X91w77JX5MhRpEUFIkKfhOGnw4NdZZVbWqcJpn38TI4Dat1fff2dUeBsHP3zl2kAbWqKaB9eYTXY0olmi5H+U/oChn5QMkk3a6ayIpPAGL4XYjm+SL23Vw6Lix00IWMOQLXHwlCgLvtLdoiz6O6uy2JKEGL25QTtEXIMYiyT90Y3OD3+nqTyS4iCmDToG342DfrGKBN0+hpSSl4wIygFqoaPczwxcUlhR674HmlAVqRA4gItiSXmGulWhWp034+yYBe7IumQbhJ06BzZxoCRD8vKu4neWeHuwdYJDCx2+oiVVRXuGfSMSJg== ARC-Authentication-Results: i=1; DKIM-Signature: v=1; a=rsa-sha256; bh=S3pvNzfwOtLaJZA+HnVJBa9S5rsKD0bpcyCAno qJJO8=; c=relaxed/relaxed; d=webcom.xion.oxcs.net; h=from:reply-to: subject:date:to:cc:resent-date:resent-from:resent-to:resent-cc: in-reply-to:references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:list-owner:list-archive; q=dns/txt; s=mail1; t=1713178813; x=1713783613; b=dhsrNbOsWrC22VR07iPmtL9RLvrfZC+1eO1ldJc2M IbYXwE94R8ZuXH7u1ylKefBEaz38NsDGtUXsEyLDnXw3TrHJmkF62wCXbzdg4rpbgsPDo/5 HRrryK5GPvaTmd74re/v2EASUJ9P2Q+ctzwjZ3MVW61XX2nGyIEiM7by+prDVAcXY2topp+ pRmje7YtbI4hVeFktUxpXLuGbnrK/iQ1PLGl8Hg6wRHfwKyYUNTBLrzBXtHvkKX7g7QQYBr NQBSqerZpLW3Q47fV6Y7sEpbYDVAraM9F4dYNjlLN4cPV59fRpEB9BWNiMtPTUKMthePQ5f mfB9RDBztYoF4kb7g== Received: from proxy-13.proxy.cloudus.ewr.xion.oxcs.net ([76.14.243.145]) by oxsus2nmtao02p.internal.vadesecure.com with ngmta id d4385940-17c66f0daf3ffb58; Mon, 15 Apr 2024 11:00:13 +0000 From: "Fred L. Finster" Subject: Re: Loading vmm JTAG Board FLIRC JEFF PROBE or Tigard Probe To: freebsd-arm@freebsd.org Cc: "fredfinster58@gmail.com" Message-ID: Date: Mon, 15 Apr 2024 04:00:11 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0 List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.90 / 15.00]; FAKE_REPLY(1.00)[]; ARC_ALLOW(-1.00)[oxsus-vadesecure.net:s=arc-202309-rsa2048:i=1]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.999]; DMARC_POLICY_ALLOW(-0.50)[thegalacticzoo.com,quarantine]; R_SPF_ALLOW(-0.20)[+ip4:15.204.3.4/30]; R_DKIM_ALLOW(-0.20)[webcom.xion.oxcs.net:s=mail1]; ONCE_RECEIVED(0.10)[]; MIME_GOOD(-0.10)[text/plain]; RCVD_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; FROM_HAS_DN(0.00)[]; ASN(0.00)[asn:16276, ipnet:15.204.0.0/17, country:FR]; FREEMAIL_CC(0.00)[gmail.com]; TO_DN_EQ_ADDR_SOME(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; RWL_MAILSPIKE_POSSIBLE(0.00)[15.204.3.7:from]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[15.204.3.7:from]; MID_RHS_MATCH_FROM(0.00)[]; DKIM_TRACE(0.00)[webcom.xion.oxcs.net:+] X-Rspamd-Queue-Id: 4VJ42V1NRTz46kQ > From: John F Carr > Date: Sun, 14 Apr 2024 12:17:22 UTC > > See bug https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277559. It was suspected to be specific to the heterogenous Rockchip RK3399 but perhaps it is more widespread. > > When I first hit the bug there was a 30-50% chance that the first kldload vmm would hang the system so hard I couldn't even invoke the debugger with break on a serial console. Later, with no relevant changes to source code, it would take about 2,000 load/unload pairs to hang the system. If that 1-in-2000 chance is typical this bug could affect all systems. Give it a try on your 128 core system: > > # while kldload vmm ; do echo -n . ; kldunload vmm ; done > > If anybody can tell me how to debug at the hardware level using JTAG, I can give it a try on my RockPro64 and see where the kernel is stuck. I have used hardware level debugging tools, but they were always black boxes my employer bought with instructions included. I hope hardware debugging finds the problem and solution to your kldload vmm issue Here i share a JTAG circuit board to purchase for interfacing with Raspberry Pi 4B, 3B, 400 with OpenOCD and aarch64-gdb JTAG Hardware post at forums.freebsd.org https://forums.freebsd.org/threads/debugging-arm64-booting-of-freebsd-ghostbsd-kernel-for-raspberry-pi-4-what-tool-do-you-use-any-jtag-hardware-kernel-debug.90436/ From reading the specifications I like the FLIRC JEFF Probe that can be bought from Amazon or AliExpress. It has a TTL UART Serial Port to USB and a TTL JTAG to USB that can be connected with OPENOCD.org and GDB or LLDB connected to the OpenOCD https://flirc.tv/products/flirc-jeffprobe?variant=43085036585192 https://macoy.me/blog/programming/RaspberryPi5Debugging Using a Raspberry Pi PICO board or RP2040 for SWD Serial Wire Debug for Raspberry Pi 5 hardware. ~~~~~~~~~~~~~~~~~~~~~~~~~~~ I have used the Black Magic Probe (BMP) 3.3V TTL Serial UART for connecting to UART0 for the serial console boot up messages. The BMP JTAG port interfaces with 32bit ARM and not 64 bit ARM, except for supporting OPENOCD onto the JTAG port of the BMP. I also am presently using an orange colored Tigard Board from CrowdSupply.com My Blogpost about connecting this up to Tigard Board. Should be the same or similar for a FLIRC Jeff Probe https://ghostbsd-arm64.blogspot.com/2024/02/tigard-ft232h-board-connectons-to.html I welcome your questions, suggestions and improvements to my blogpost and other materials shared. I, too, am starting blind and learning how to put all this together to be usable for debugging through JTAG software on the Raspberry Pi 4B hardware. Your feedback helps me too and make better documentation for others to use in the future. https://ghostbsd-arm64.blogspot.com/2024/03/compile-gdb-for-aarch64-target-to-use.html Compiling GDB for aarch64 target. I need to add Python built into GDB. Will update this blog post to include Python language. Very useful for one tool that I found and wish to use, that requires the --with-python and --with-python-libdir configuration of GDB. https://forums.raspberrypi.com/viewtopic.php?t=364475 To keep the mailing list clean reading, I turn off the HTML So you copy a URL and paste into your open browser window or use Lynx (links) browser for a quick easy view of a text URL link. Hope, I did not forget a URL link to share while I was recompiling aarch64-gdb with python enabled. Here is aarch64 GDB QEMU UEFI debugging explanation: https://krinkinmu.github.io/2020/12/26/position-independent-executable.html https://surma.dhev/postits/arm64/ Bootstrapping Arm64 hardware, QEMU https://www.vinnie.work/blog/2020-11-06-baremetal-rpi4-setup/ Very good explanations and setup of OpenOCD, aarch64-gdb https://macoy.me/blog/programming/RaspberryPi5Debugging Raspberry Pi 4B JTAG hardware debug setup , Raspberry Pi 5 SWD serial wired debug setup Sending this email now Fred L. Finster https://ghostbsd-arm64.blogspot.com http://ghostbsdarm64.hopto.org/packages/ https://ghostbsd-arm64.blogspot.com/2024/01/january-19-2024-howto-download.html Create your own bootable USB Flash drive stick. > >> On Apr 14, 2024, at 04:50, tuexen@freebsd.org wrote: >> >> Dear all, >> >> using the sources for kernel/world of yesterday running >> kldload vmm >> on a 128 core Ampere system runs just fine: >> >> CPU 0: ARM Neoverse-N1 r3p1 affinity: 18 0 0 >> Cache Type = <64 byte D-cacheline,64 byte I-cacheline,PIPT ICache,64 byte ERG,64 byte CWG,IDC> >> Instruction Set Attributes 0 = >> Instruction Set Attributes 1 = >> Instruction Set Attributes 2 = <> >> Processor Features 0 = >> Processor Features 1 = >> Memory Model Features 0 = >> Memory Model Features 1 = >> Memory Model Features 2 = >> Debug Features 0 = >> Debug Features 1 = <> >> Auxiliary Features 0 = <> >> Auxiliary Features 1 = <> >> AArch32 Instruction Set Attributes 5 = >> AArch32 Media and VFP Features 0 = >> AArch32 Media and VFP Features 1 = >> >> However, doing the same on a 32 core Ampere system results in >> the system becoming unresponsive. No reaction on the console, >> no message there, no response over the network. >> >> CPU 0: APM eMAG 8180 r3p2 affinity: 0 0 >> Cache Type = <64 byte D-cacheline,64 byte I-cacheline,PIPT ICache,64 byte ERG,64 byte CWG> >> Instruction Set Attributes 0 = >> Instruction Set Attributes 1 = <> >> Instruction Set Attributes 2 = <> >> Processor Features 0 = >> Processor Features 1 = <> >> Memory Model Features 0 = >> Memory Model Features 1 = <8bit VMID> >> Trying to mount root from ufs:/dev/ada0p2 [rw]... >> Memory Model Features 2 = <32bit CCIDX,48bit VA> >> Debug Features 0 = >> Debug Features 1 = <> >> Auxiliary Features 0 = <> >> Auxiliary Features 1 = <> >> AArch32 Instruction Set Attributes 5 = >> AArch32 Media and VFP Features 0 = >> AArch32 Media and VFP Features 1 = >> >> Any idea, what is going wrong? >> >> Best regards >> Michael > -- Fred Finster GhostBSD-Arm64.blogspot.com t.me/ghostbsd Telegram Channel GhostBSD.org website ghostbsdarm64.hopto.org/packages From nobody Mon Apr 15 13:58:32 2024 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4VJ80G4MFWz5Gdq4 for ; Mon, 15 Apr 2024 13:58:38 +0000 (UTC) (envelope-from fred@thegalacticzoo.com) Received: from nmtao201.oxsus-vadesecure.net (mta-231a.oxsus-vadesecure.net [15.204.3.4]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4VJ80F4wFTz4V6n for ; Mon, 15 Apr 2024 13:58:37 +0000 (UTC) (envelope-from fred@thegalacticzoo.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=webcom.xion.oxcs.net header.s=mail1 header.b=h+pgO9k3; dmarc=pass (policy=quarantine) header.from=thegalacticzoo.com; spf=pass (mx1.freebsd.org: domain of fred@thegalacticzoo.com designates 15.204.3.4 as permitted sender) smtp.mailfrom=fred@thegalacticzoo.com; arc=pass ("oxsus-vadesecure.net:s=arc-202309-rsa2048:i=1") ARC-Seal: i=1; a=rsa-sha256; d=oxsus-vadesecure.net; s=arc-202309-rsa2048; t=1713189516; cv=none; b=NV/wA8qUg5atOxZdd7S80bt8gYoU6P8zbNlu+2Uj/7AoeDanwNvVXvP/0K6o97CkL2bpUGX66jC6mSZeh0SBTdTOVAIx4/M0CD2ZKKI49Kkunbf10SrGmfMzYPzZRRIbz437lajTayR0mHimBmLstSHJaIpmEqRIfdKB9rf+pmWVDTByCaWjPymMpbuzOejAL6nK3gOnlF+5UcZZH2q9vQAEp0BgPn51xeCqXEVJjlDbzjjEaMSjzQ24DCTK6XBd/q1miNA8TcDmt4OvQPNSPg1cAswnnNuaMmSWeM597jy83xUGIzoglu4SfiEaX9tqghD4XvRnTOGCSNIBGyvaFg== ARC-Message-Signature: i=1; a=rsa-sha256; d=oxsus-vadesecure.net; s=arc-202309-rsa2048; t=1713189516; c=relaxed/relaxed; h=from:reply-to:subject:date:to:cc:resent-date:resent-from:resent-to:resent-cc:in-reply-to:references:list-id:list-help:list-unsubscribe:list-subscribe:list-post:list-owner:list-archive; bh=E1BOnsN7AfuDgTkTv/Ek0V4FwbeG3UTleWAtQ+cZDbA=; b=RiiWG78g2EtG3SJmHMWnC0oLAd4pGBXvLCDLrYUI9UgTJmIBK1ub1uYTmL6EG28U2uyUP70pLF7vARakIu6oxlFWLay32F6n9A7y9mHpI+iTEf1kyJi261HbkcQiNoDFPS9fCilBjvNb/aOdJ3CRwor+dVUdFCObgFAaSmszMKkEDL16dUvacCrDG1sXI3aU4iwtKYVKLeyguOdiPodyxOJ5RGMeDouyYH+s92BYilBIQ/CD8Q1DFj9nGjkKC3hnLZrNldxykbA0cBXgBLgcEKMd1GY69FuaG/k2cikqjHMHOf4eDUMvgFrwiALR/BNfD00e97VSfnpwHvQkAkeY+g== ARC-Authentication-Results: i=1; DKIM-Signature: v=1; a=rsa-sha256; bh=E1BOnsN7AfuDgTkTv/Ek0V4FwbeG3UTleWAtQ+ cZDbA=; c=relaxed/relaxed; d=webcom.xion.oxcs.net; h=from:reply-to: subject:date:to:cc:resent-date:resent-from:resent-to:resent-cc: in-reply-to:references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:list-owner:list-archive; q=dns/txt; s=mail1; t=1713189516; x=1713794316; b=h+pgO9k3k7Cwf9VN/bRaDCiNcVsmFE/W8fDf3IjIa 4Z14jqyWUQjWTG6VvV44NXr9DIzbC4KE7F5Y+3WYzKAg9PzenKX5NsmWTPaa8v9VZSa6iMS m6TwNGNuhjf9cXMxmThgxSMMHo8DRND0EGfw+rOGVPGILoO9IuMzmz2pJTxlbPbLNYgRi/L 6rBfAKBUZ00YtObduzOKUIA6/EyntGvNCfa+iSadmxUsR3buVBnzNuaOt2cBP0myvhFYK8l XPD2J+Pu2vBmArazy0R9V6tLNKhVexsPpVOLP+j4wsm+hWkCVq0IXQCDkgaiDtW4NhNDt57 5AijfOK6RYZw73O+A== Received: from proxy-4.proxy.cloudus.ewr.xion.oxcs.net ([76.14.243.145]) by oxsus2nmtao01p.internal.vadesecure.com with ngmta id 2cb4280e-17c678c9722e027b; Mon, 15 Apr 2024 13:58:36 +0000 Content-Type: multipart/alternative; boundary="------------QIuk0Uuykn40P0G00J80shzd" Message-ID: <73029bbf-76b5-4cb5-ac44-4ac6150a88e8@thegalacticzoo.com> Date: Mon, 15 Apr 2024 06:58:32 -0700 List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Content-Language: en-US To: freebsd-arm@freebsd.org Cc: julf@julf.com From: Fred Finster Subject: Re: Raspberry Pi 4 and M.2 SATA SSD recognized but not booting or available for install - unsupported interface X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.85 / 15.00]; FAKE_REPLY(1.00)[]; ARC_ALLOW(-1.00)[oxsus-vadesecure.net:s=arc-202309-rsa2048:i=1]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.96)[-0.956]; DMARC_POLICY_ALLOW(-0.50)[thegalacticzoo.com,quarantine]; R_DKIM_ALLOW(-0.20)[webcom.xion.oxcs.net:s=mail1]; R_SPF_ALLOW(-0.20)[+ip4:15.204.3.4/30]; ONCE_RECEIVED(0.10)[]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; XM_UA_NO_VERSION(0.01)[]; RCVD_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:16276, ipnet:15.204.0.0/17, country:FR]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RWL_MAILSPIKE_POSSIBLE(0.00)[15.204.3.4:from]; MID_RHS_MATCH_FROM(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[15.204.3.4:from]; TO_DN_NONE(0.00)[]; RCVD_TLS_LAST(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org]; DKIM_TRACE(0.00)[webcom.xion.oxcs.net:+] X-Rspamd-Queue-Id: 4VJ80F4wFTz4V6n This is a multi-part message in MIME format. --------------QIuk0Uuykn40P0G00J80shzd Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit ZFS  ,  UFS  here are some webpages for Raspberry Pi 4B running FreeBSD 14.0-RELEASE I can show you how to transfer files from a booted USB Flash Disk drive Stick to make your own USB SSD with a bootable ZFS file system using about 4 or 5 shell script files to make the move of copying files from a USB flash drive to a ZFS USB SSD. If you help me test, find errors, make corrections.  I will gladly help you Julf and others who are interested in running FreeBSD on a USB SSD with an installed ZFS file system. This is the bootable GhostBSD image I created.  You can use the FreeBSD 14.0-RELEASE RPI image. I have setup a shell script to download  the FreeBSD image for your and to uncompress this compressed XZ image. Select '0' to download the checksum value Select '1' to download the FreeBSD 14.0-RELEASE image Select '2' to download the GhostBSD-Arm64 image file from my package NGINX web server http://ghostbsdarm64.hopto.org/packages/ Select '3' to download from any URL you select This is a 6k shell script file to download and perform the tasks for you. http://ghostbsdarm64.hopto.org/packages/write_freebsd_img_dd_to_da1.sh http://ghostbsdarm64.hopto.org/packages/Ghost14_5G_selfbuilt_raspi4b_Feb27_2.img.xz This is a 728Megabyte file to downloaded by the previous 6k shell script file when selecting option '2' . 500 GB setup for UFS ? https://ghostbsd-arm64.blogspot.com/2022/02/booting-500-gb-ssd-on-freebsd-arm64-140.html 500 GB setup for Raspberry Pi 4B with FreeBSD O/S https://ghostbsd-arm64.blogspot.com/2023/07/learning-zfs-on-root-setup-for.html https://ghostbsd-arm64.blogspot.com/2024/04/create-ghostbsd-usb-ssd-500gb-or-larger.html This is most for x86_64 but the commands are the same. https://ghostbsd-arm64.blogspot.com/2023/10/honey-i-broke-my-zfs-usb-sata-ssd-1-tb.html Here are short details, about how I fixed a boot problem with my ZFS disk for Raspberry Pi 4B. https://ghostbsd-arm64.blogspot.com/2024/01/hdmi-audio-sound-patches-into-ghostbsd.html Here are details for setting up the audio patch files to compile for FreeBSD and GhostBSD Here are details for setting up the 4 shell script files to create a ZFS USB SSD. https://ghostbsd-arm64.blogspot.com/2023/12/zfs-boot-on-root-setup-for-usb-ssd.html I am sending now, Julf.  Reach out to me.  I can help you achieve a working Desktop on Arm64 booting from a USB SSD. Fred Finster fred@thegalacticzoo.com fredfinster58@gmail.com > */From:/* Johan Helsingius > */Date:/* Thu, 11 Apr 2024 17:47:52 UTC > On 11/04/2024 19:38, Mark Millard wrote: > > Which image(s)? > > I think it was the memstick one. > > > Only the likes of, say, > > > > FreeBSD-14.0-STABLE-arm64-aarch64-RPI-20240404-72c3d91294c4-267114.img.xz > > and: > > FreeBSD-15.0-CURRENT-arm64-aarch64-RPI-20240404-112783ebbc31-269103.img.xz > > and: > > FreeBSD-14.0-RELEASE-arm64-aarch64-RPI.img.xz > > > > are set up with the extra materials that I referenced for the RPi*'s. Note: > > Those are UFS based, not ZFS based. > > Ah! I see! Bummer that none of them are ZFS based, but I guess I can > live with UFS on a RPi - it just means I have to have yet another > backup procedure. > > > What did you put in da1p1 (efiboot0) ? That area you have > > to deal with for bsdinstall usage. Some folks extract and > > copy over what is in the msdosfs in a: > > > > *-arm64-aarch64-RPI-*.img.xz > > > > as a means of getting an officially-built set of such > > materials when they want to customize other aspects. > > Would that make it possible to do a ZFS-based environment? > > Julf > --------------QIuk0Uuykn40P0G00J80shzd Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit

ZFS  ,  UFS  here are some webpages for Raspberry Pi 4B running FreeBSD 14.0-RELEASE


I can show you how to transfer files from a booted USB Flash Disk drive Stick to make your own USB SSD with a bootable ZFS file system using about 4 or 5 shell script files to make the move of copying files from a USB flash drive to a ZFS USB SSD.

If you help me test, find errors, make corrections.  I will gladly help you Julf and others who are interested in running FreeBSD on a USB SSD with an installed ZFS file system.

This is the bootable GhostBSD image I created.  You can use the FreeBSD 14.0-RELEASE RPI image.

I have setup a shell script to download  the FreeBSD image for your and to uncompress this compressed XZ image.  

Select '0' to download the checksum value
Select '1' to download the FreeBSD 14.0-RELEASE image
Select '2' to download the GhostBSD-Arm64 image file from my package NGINX web server  http://ghostbsdarm64.hopto.org/packages/ 
Select '3' to download from any URL you select


This is a 6k shell script file to download and perform the tasks for you.
http://ghostbsdarm64.hopto.org/packages/write_freebsd_img_dd_to_da1.sh

http://ghostbsdarm64.hopto.org/packages/Ghost14_5G_selfbuilt_raspi4b_Feb27_2.img.xz  This is a 728Megabyte file to downloaded by the previous 6k shell script file when selecting option '2' .


500 GB setup for UFS ?
https://ghostbsd-arm64.blogspot.com/2022/02/booting-500-gb-ssd-on-freebsd-arm64-140.html

500 GB setup for Raspberry Pi 4B with FreeBSD O/S
https://ghostbsd-arm64.blogspot.com/2023/07/learning-zfs-on-root-setup-for.html

https://ghostbsd-arm64.blogspot.com/2024/04/create-ghostbsd-usb-ssd-500gb-or-larger.html   This is most for x86_64 but the commands are the same.

https://ghostbsd-arm64.blogspot.com/2023/10/honey-i-broke-my-zfs-usb-sata-ssd-1-tb.html  Here are short details, about how I fixed a boot problem with my ZFS disk for Raspberry Pi 4B.

https://ghostbsd-arm64.blogspot.com/2024/01/hdmi-audio-sound-patches-into-ghostbsd.html  Here are details for setting up the audio patch files to compile for FreeBSD and GhostBSD

Here are details for setting up the 4 shell script files to create a ZFS USB SSD.

https://ghostbsd-arm64.blogspot.com/2023/12/zfs-boot-on-root-setup-for-usb-ssd.html

I am sending now, Julf.  Reach out to me.  I can help you achieve a working Desktop on Arm64 booting from a USB SSD.

Fred Finster
fred@thegalacticzoo.com
fredfinster58@gmail.com


From: Johan Helsingius <julf_at_Julf.com>
Date: Thu, 11 Apr 2024 17:47:52 UTC 
On 11/04/2024 19:38, Mark Millard wrote:
> Which image(s)?

I think it was the memstick one.

> Only the likes of, say,
> 
> FreeBSD-14.0-STABLE-arm64-aarch64-RPI-20240404-72c3d91294c4-267114.img.xz
> and:
> FreeBSD-15.0-CURRENT-arm64-aarch64-RPI-20240404-112783ebbc31-269103.img.xz
> and:
> FreeBSD-14.0-RELEASE-arm64-aarch64-RPI.img.xz
> 
> are set up with the extra materials that I referenced for the RPi*'s. Note:
> Those are UFS based, not ZFS based.

Ah! I see! Bummer that none of them are ZFS based, but I guess I can
live with UFS on a RPi - it just means I have to have yet another
backup procedure.

> What did you put in da1p1 (efiboot0) ? That area you have
> to deal with for bsdinstall usage. Some folks extract and
> copy over what is in the msdosfs in a:
> 
> *-arm64-aarch64-RPI-*.img.xz
> 
> as a means of getting an officially-built set of such
> materials when they want to customize other aspects.

Would that make it possible to do a ZFS-based environment?

	Julf

--------------QIuk0Uuykn40P0G00J80shzd-- From nobody Mon Apr 15 14:15:17 2024 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4VJ8Mc186Sz5GgW5 for ; Mon, 15 Apr 2024 14:15:24 +0000 (UTC) (envelope-from julf@Julf.com) Received: from outbound1.mail.transip.nl (outbound1.mail.transip.nl [149.210.149.72]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4VJ8MY6mbLz4cGl for ; Mon, 15 Apr 2024 14:15:21 +0000 (UTC) (envelope-from julf@Julf.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=julf.com header.s=transip-a header.b=ofat7Eba; dmarc=pass (policy=quarantine) header.from=julf.com; spf=pass (mx1.freebsd.org: domain of julf@Julf.com designates 149.210.149.72 as permitted sender) smtp.mailfrom=julf@Julf.com Received: from submission9.mail.transip.nl (unknown [10.103.8.160]) by outbound1.mail.transip.nl (Postfix) with ESMTP id 4VJ8MV4k5SzRhrs for ; Mon, 15 Apr 2024 16:15:18 +0200 (CEST) Received: from [172.24.42.151] (julf.connected.by.freedominter.net [45.138.231.4]) by submission9.mail.transip.nl (Postfix) with ESMTPA id 4VJ8MT1xYpz1y2m for ; Mon, 15 Apr 2024 16:15:17 +0200 (CEST) Message-ID: <663ad239-8635-44fd-a645-75842655ee8b@Julf.com> Date: Mon, 15 Apr 2024 16:15:17 +0200 List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Raspberry Pi 4 and M.2 SATA SSD recognized but not booting or available for install - unsupported interface To: freebsd-arm@freebsd.org References: <73029bbf-76b5-4cb5-ac44-4ac6150a88e8@thegalacticzoo.com> Content-Language: en-GB, sv-FI, nl-NL From: Johan Helsingius In-Reply-To: <73029bbf-76b5-4cb5-ac44-4ac6150a88e8@thegalacticzoo.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Scanned-By: ClueGetter at submission9.mail.transip.nl DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; s=transip-a; d=julf.com; t=1713190517; h=from:subject:to:references: in-reply-to:date:mime-version:content-type; bh=lxc3cgcWV1IbKiN22YE555iv3G3V3aZ5RPErux49m9E=; b=ofat7EbaWVDTt7ac9Dcs47AIftZ2raq1dqTowOLtufz9KHdXNjzsfXjoU3GHW9Bm1QHjFV zU/NzpGc1wnkg3esu0TrVz2apysetKnZ5jhwcAe/hjYG/8+jtNOyA2zlDq7Q+vZYI0lurG GBP8Wq7aBWfZi2DbXOKNVV3f2CS+0/C7YRWgKxXETVeMIYJA9CJ2Gg6SpCcQpZbqcmnbh8 5x1sR747ugPcjk5O5wHbkxGNtwP3NUXzgo92VcQQ515Ly1M+dzai4N+wK08jgNiBAX+pxS 1rGIGSLQh27N6HCfZVIYqUx7f4ZLlwnbjTMCf1qh8A7h/zblPWR/TSYFzbtqEQ== X-Report-Abuse-To: abuse@transip.nl X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.08 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.994]; DMARC_POLICY_ALLOW(-0.50)[julf.com,quarantine]; R_DKIM_ALLOW(-0.20)[julf.com:s=transip-a]; R_SPF_ALLOW(-0.20)[+ip4:149.210.149.72]; RCVD_IN_DNSWL_LOW(-0.10)[149.210.149.72:from]; MIME_GOOD(-0.10)[text/plain]; XM_UA_NO_VERSION(0.01)[]; RCPT_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:20857, ipnet:149.210.128.0/17, country:NL]; RCVD_VIA_SMTP_AUTH(0.00)[]; MIME_TRACE(0.00)[0:+]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org]; ARC_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCVD_TLS_LAST(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; DKIM_TRACE(0.00)[julf.com:+] X-Rspamd-Queue-Id: 4VJ8MY6mbLz4cGl Thanks, this is great info! I do now have my RPi 4 successfully running 14.0-RELEASE-p6, but happy to try your image if you want me to help with testing. Julf On 15/04/2024 15:58, Fred Finster wrote: > ZFS  ,  UFS  here are some webpages for Raspberry Pi 4B running FreeBSD > 14.0-RELEASE > > > I can show you how to transfer files from a booted USB Flash Disk drive > Stick to make your own USB SSD with a bootable ZFS file system using > about 4 or 5 shell script files to make the move of copying files from a > USB flash drive to a ZFS USB SSD. > > If you help me test, find errors, make corrections.  I will gladly help > you Julf and others who are interested in running FreeBSD on a USB SSD > with an installed ZFS file system. > > This is the bootable GhostBSD image I created.  You can use the FreeBSD > 14.0-RELEASE RPI image. > > I have setup a shell script to download  the FreeBSD image for your and > to uncompress this compressed XZ image. > > Select '0' to download the checksum value > Select '1' to download the FreeBSD 14.0-RELEASE image > Select '2' to download the GhostBSD-Arm64 image file from my package > NGINX web server http://ghostbsdarm64.hopto.org/packages/ > Select '3' to download from any URL you select > > > This is a 6k shell script file to download and perform the tasks for you. > http://ghostbsdarm64.hopto.org/packages/write_freebsd_img_dd_to_da1.sh > > http://ghostbsdarm64.hopto.org/packages/Ghost14_5G_selfbuilt_raspi4b_Feb27_2.img.xz This is a 728Megabyte file to downloaded by the previous 6k shell script file when selecting option '2' . > > > 500 GB setup for UFS ? > https://ghostbsd-arm64.blogspot.com/2022/02/booting-500-gb-ssd-on-freebsd-arm64-140.html > > 500 GB setup for Raspberry Pi 4B with FreeBSD O/S > https://ghostbsd-arm64.blogspot.com/2023/07/learning-zfs-on-root-setup-for.html > > https://ghostbsd-arm64.blogspot.com/2024/04/create-ghostbsd-usb-ssd-500gb-or-larger.html This is most for x86_64 but the commands are the same. > > https://ghostbsd-arm64.blogspot.com/2023/10/honey-i-broke-my-zfs-usb-sata-ssd-1-tb.html Here are short details, about how I fixed a boot problem with my ZFS disk for Raspberry Pi 4B. > > https://ghostbsd-arm64.blogspot.com/2024/01/hdmi-audio-sound-patches-into-ghostbsd.html Here are details for setting up the audio patch files to compile for FreeBSD and GhostBSD > > Here are details for setting up the 4 shell script files to create a ZFS > USB SSD. > > https://ghostbsd-arm64.blogspot.com/2023/12/zfs-boot-on-root-setup-for-usb-ssd.html > > I am sending now, Julf.  Reach out to me.  I can help you achieve a > working Desktop on Arm64 booting from a USB SSD. > > Fred Finster > fred@thegalacticzoo.com > fredfinster58@gmail.com > > >> */From:/* Johan Helsingius >> */Date:/* Thu, 11 Apr 2024 17:47:52 UTC >> On 11/04/2024 19:38, Mark Millard wrote: >> > Which image(s)? >> >> I think it was the memstick one. >> >> > Only the likes of, say, >> > >> > FreeBSD-14.0-STABLE-arm64-aarch64-RPI-20240404-72c3d91294c4-267114.img.xz >> > and: >> > FreeBSD-15.0-CURRENT-arm64-aarch64-RPI-20240404-112783ebbc31-269103.img.xz >> > and: >> > FreeBSD-14.0-RELEASE-arm64-aarch64-RPI.img.xz >> > >> > are set up with the extra materials that I referenced for the RPi*'s. Note: >> > Those are UFS based, not ZFS based. >> >> Ah! I see! Bummer that none of them are ZFS based, but I guess I can >> live with UFS on a RPi - it just means I have to have yet another >> backup procedure. >> >> > What did you put in da1p1 (efiboot0) ? That area you have >> > to deal with for bsdinstall usage. Some folks extract and >> > copy over what is in the msdosfs in a: >> > >> > *-arm64-aarch64-RPI-*.img.xz >> > >> > as a means of getting an officially-built set of such >> > materials when they want to customize other aspects. >> >> Would that make it possible to do a ZFS-based environment? >> >> Julf >> > From nobody Mon Apr 15 14:42:13 2024 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4VJ8yj0Vkhz5Gk0y for ; Mon, 15 Apr 2024 14:42:21 +0000 (UTC) (envelope-from fred@thegalacticzoo.com) Received: from nmtao202.oxsus-vadesecure.net (mta-232a.oxsus-vadesecure.net [15.204.3.6]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4VJ8yg5PSdz4hvs for ; Mon, 15 Apr 2024 14:42:19 +0000 (UTC) (envelope-from fred@thegalacticzoo.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=webcom.xion.oxcs.net header.s=mail1 header.b=nEgeuboM; dmarc=pass (policy=quarantine) header.from=thegalacticzoo.com; spf=pass (mx1.freebsd.org: domain of fred@thegalacticzoo.com designates 15.204.3.6 as permitted sender) smtp.mailfrom=fred@thegalacticzoo.com; arc=pass ("oxsus-vadesecure.net:s=arc-202309-rsa2048:i=1") ARC-Seal: i=1; a=rsa-sha256; d=oxsus-vadesecure.net; s=arc-202309-rsa2048; t=1713192138; cv=none; b=AQQO4nFgNoifV9vnYYiK872umwbtIxe8tcnsPkhq/rocp1MGRkxXUufwkrvsIGAf72nm/9tEsPfqHKyAJ7SMLtjntUvIzIIfBDxaW7NoKPzoXHe5AXwKCbodb/DmYvYeTzlX0i1M7kyt0EpcjDg+u1svEhI37FKdE9WMvkZNFUr/FUO1Bqb7gmMEzq1+yvT6SIdcSls515DuqyZsavsQHiIbwWWa493WpJK5z1mbpDESejzFcrSLrulhcW4V+7zZIWS2LNvKiNdIRWRlmX4bGaaDZMaDWAIQ3n6VIiE+y1kOGJps/9Gzx32UWbGRJu7/BwQJw2uG+rsT421uDpT1Ww== ARC-Message-Signature: i=1; a=rsa-sha256; d=oxsus-vadesecure.net; s=arc-202309-rsa2048; t=1713192138; c=relaxed/relaxed; h=from:reply-to:subject:date:to:cc:resent-date:resent-from:resent-to:resent-cc:in-reply-to:references:list-id:list-help:list-unsubscribe:list-subscribe:list-post:list-owner:list-archive; bh=UmrgJ8pqGtfJNdsE+bpwUVIrwmAWUE7fdo8wU+OvEkk=; b=d80BP4VjCU/09gklw9OblkzD6Jeir3htkV1IqFcZ0nwnam8IYKJo+H9BNEw7lO6AZn4WAcrQs6TcId+sEEOUX4AfArzgTrayfmcPehx+OB3genlt1IIjiaj0iZ1zi4Lz+e+nsXXiMy3bBazIwpFjSImJH6vDA4ZAtdsDrYaTIr4BnhHX3BBGnJJaAT0Vi+s954TCRFiOJDRZPDhzGwPjmwyF5+j5IhEjNIh28NN+Ro+wVEfMbgAU20v4TOh20+R0xsZrNv+z/1bYTIna7fKLOl9FwzzVw11VA1UfehydD5/ck7+cnKxE3/NcI8MC7kCAgzZ+MhCwmaSJf7olP55BMA== ARC-Authentication-Results: i=1; DKIM-Signature: v=1; a=rsa-sha256; bh=UmrgJ8pqGtfJNdsE+bpwUVIrwmAWUE7fdo8wU+ OvEkk=; c=relaxed/relaxed; d=webcom.xion.oxcs.net; h=from:reply-to: subject:date:to:cc:resent-date:resent-from:resent-to:resent-cc: in-reply-to:references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:list-owner:list-archive; q=dns/txt; s=mail1; t=1713192138; x=1713796938; b=nEgeuboM+s43tsDtZDalnoUof/UeHhbSyu4NzmXA8 KSTgxNw8yR8e4AfaHRzf8xY6TslPy8a4TdZo7vaQMwpkfmNSxOAKpw+I27lrANJakKuizaK 81do2YTfnYjUk+xg5F7Wuw+jlcGBN17qgAB/QhVhVkql8EIGwwsKQ+Apk3MrtJI3nX7k7fv 6T+0uige6gRtk29w36BXSKwXZML12TFv6fbRccW88PyYrW8gWLgUCV0OqUueMLsTByZkVSI 4aGKN82k6DrkLUKndw9zDxpK8FhCvspwb24yYONaLoGlqxCK/01Ps+R/NZXYe0UKIZd+fQ5 LbtEFj+eTDEF2Uo1Q== Received: from proxy-4.proxy.cloudus.ewr.xion.oxcs.net ([76.14.243.145]) by oxsus2nmtao02p.internal.vadesecure.com with ngmta id 2c735eee-17c67b2bb0b7ab73; Mon, 15 Apr 2024 14:42:17 +0000 Content-Type: multipart/alternative; boundary="------------xunBvrVvR1oHL80M0JZf6UpP" Message-ID: <47cd665c-7b1c-402e-8534-f5837390eb4c@thegalacticzoo.com> Date: Mon, 15 Apr 2024 07:42:13 -0700 List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Content-Language: en-US From: Fred Finster To: freebsd-arm@freebsd.org Cc: julf@julf.com, fred@thegalacticzoo.com, fredfinster58@gmail.com Subject: FreeBSD , GhostBSD tools for building a GPT SSD X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.89 / 15.00]; ARC_ALLOW(-1.00)[oxsus-vadesecure.net:s=arc-202309-rsa2048:i=1]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.996]; DMARC_POLICY_ALLOW(-0.50)[thegalacticzoo.com,quarantine]; R_DKIM_ALLOW(-0.20)[webcom.xion.oxcs.net:s=mail1]; R_SPF_ALLOW(-0.20)[+ip4:15.204.3.4/30]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; ONCE_RECEIVED(0.10)[]; XM_UA_NO_VERSION(0.01)[]; RCVD_COUNT_ONE(0.00)[1]; RCVD_IN_DNSWL_NONE(0.00)[15.204.3.6:from]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:16276, ipnet:15.204.0.0/17, country:FR]; RWL_MAILSPIKE_POSSIBLE(0.00)[15.204.3.6:from]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org]; FROM_HAS_DN(0.00)[]; FREEMAIL_CC(0.00)[julf.com,thegalacticzoo.com,gmail.com]; RCPT_COUNT_THREE(0.00)[4]; FROM_EQ_ENVFROM(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_NONE(0.00)[]; RCVD_TLS_LAST(0.00)[]; DKIM_TRACE(0.00)[webcom.xion.oxcs.net:+] X-Rspamd-Queue-Id: 4VJ8yg5PSdz4hvs This is a multi-part message in MIME format. --------------xunBvrVvR1oHL80M0JZf6UpP Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit > */From:/* Johan Helsingius > */Date:/* Mon, 15 Apr 2024 14:15:17 UTC > Thanks, this is great info! I do now have my RPi 4 successfully > running 14.0-RELEASE-p6, but happy to try your image if you want > me to help with testing. > > Julf Yes,  I would like you to test using a FreeBSD or ghostbsd.org/download (written to a USB flash drive stick and booted from USB flash drive)  or, a Linux x86_64 image to run that 6K shell script.   I have my Raspberry Pi 4B, running Poudriere package builder currently now on single Raspi4B hardware, so the download aspect will be slow, but steady. > > This is a 6k shell script file to download and perform the tasks for you. > http://ghostbsdarm64.hopto.org/packages/write_freebsd_img_dd_to_da1.sh Other Telegram groups Arm Open-Source https://t.me/+ST6N61pnu3Di8zgk Arm Open-Source welcome to join and comment on anything Arm Open-Source software. https://t.me/ghostbsd_dev/24054  GhostBSD ARM64 Development telegram group 2.)  Can you md5deep your boot files in the 'efi'  MSDOSFS esp FAT16 or FAT32 partition, Julf? https://ghostbsd-arm64.blogspot.com/2021/05/audit-your-boot-files-with-md5deep.html Other URLS to read FYI,  'search' on words like:  wifi, 500, ZFS, UFS, Poudriere: https://ghostbsd-arm64.blogspot.com/2022/02/booting-500-gb-ssd-on-freebsd-arm64-140.html https://ghostbsd-arm64.blogspot.com/2023/12/look-inside-usb-flash-drive-partition.html https://ghostbsd-arm64.blogspot.com/2023/11/creating-ghost14-aarch64-arm64-boot.html https://ghostbsd-arm64.blogspot.com/2023/11/arm64-boot-usb-flash-drive-hey-buddy.html --------------xunBvrVvR1oHL80M0JZf6UpP Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit

From: Johan Helsingius <julf_at_Julf.com>
Date: Mon, 15 Apr 2024 14:15:17 UTC 
Thanks, this is great info! I do now have my RPi 4 successfully
running 14.0-RELEASE-p6, but happy to try your image if you want
me to help with testing.

	Julf
Yes,  I would like you to test using a FreeBSD or ghostbsd.org/download (written to a USB flash drive stick and booted from USB flash drive)  or, a Linux x86_64 image to run that 6K shell script.   I have my Raspberry Pi 4B, running Poudriere package builder currently now on single Raspi4B hardware, so the download aspect will be slow, but steady.

> 
> This is a 6k shell script file to download and perform the tasks for you.
> http://ghostbsdarm64.hopto.org/packages/write_freebsd_img_dd_to_da1.sh

Other Telegram groups  Arm Open-Source
https://t.me/+ST6N61pnu3Di8zgk   Arm Open-Source welcome to join and comment on 
anything Arm Open-Source software.

https://t.me/ghostbsd_dev/24054  GhostBSD ARM64 Development telegram group

2.)  Can you md5deep your boot files in the 'efi'  MSDOSFS esp FAT16 or FAT32 partition, Julf?

https://ghostbsd-arm64.blogspot.com/2021/05/audit-your-boot-files-with-md5deep.html


Other URLS to read FYI,  'search' on words like:  wifi, 500, ZFS, UFS, Poudriere:

https://ghostbsd-arm64.blogspot.com/2022/02/booting-500-gb-ssd-on-freebsd-arm64-140.html

https://ghostbsd-arm64.blogspot.com/2023/12/look-inside-usb-flash-drive-partition.html

https://ghostbsd-arm64.blogspot.com/2023/11/creating-ghost14-aarch64-arm64-boot.html

https://ghostbsd-arm64.blogspot.com/2023/11/arm64-boot-usb-flash-drive-hey-buddy.html

--------------xunBvrVvR1oHL80M0JZf6UpP-- From nobody Mon Apr 15 18:34:52 2024 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4VJG752qXRz5H6M3 for ; Mon, 15 Apr 2024 18:34:57 +0000 (UTC) (envelope-from julf@Julf.com) Received: from outbound2.mail.transip.nl (outbound2.mail.transip.nl [149.210.149.73]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4VJG750qDkz4KKK for ; Mon, 15 Apr 2024 18:34:56 +0000 (UTC) (envelope-from julf@Julf.com) Authentication-Results: mx1.freebsd.org; none Received: from submission13.mail.transip.nl (unknown [10.103.8.164]) by outbound2.mail.transip.nl (Postfix) with ESMTP id 4VJG714PrBzYdZs; Mon, 15 Apr 2024 20:34:53 +0200 (CEST) Received: from [172.24.42.151] (julf.connected.by.freedominter.net [45.138.231.4]) by submission13.mail.transip.nl (Postfix) with ESMTPA id 4VJG704Ns4z1y46; Mon, 15 Apr 2024 20:34:52 +0200 (CEST) Message-ID: <22ce429c-002a-46d1-9a43-bcb78cd4bb29@Julf.com> Date: Mon, 15 Apr 2024 20:34:52 +0200 List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Raspberry Pi 4 and M.2 SATA SSD recognized but not booting or available for install - unsupported interface To: Fred Finster , freebsd-arm@freebsd.org References: <73029bbf-76b5-4cb5-ac44-4ac6150a88e8@thegalacticzoo.com> Content-Language: en-GB, sv-FI, nl-NL From: Johan Helsingius In-Reply-To: <73029bbf-76b5-4cb5-ac44-4ac6150a88e8@thegalacticzoo.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Scanned-By: ClueGetter at submission13.mail.transip.nl DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; s=transip-a; d=julf.com; t=1713206092; h=from:subject:to:references: in-reply-to:date:mime-version:content-type; bh=mc61IvQycLmIqLBiHJrt4n8HgDi/OyDd/elmnWDGZrk=; b=lPcbUhDqwG7E29OZ1VWVcJM21IKZwoJg0xg9pVJGY1F46UIGfs4ldWwqwPrsd6WZRzec6I 74slXSYK1HGoZ7gNSvmUq+VrcPovhoRn5d4sxgSCXsQiKFsTCUMnphMeFCQHObvhGavnHc 37oJBEeDHU3YYVUcHo2b0IxEIEqveb8ZLSYkHWTAppX0ttdHH35AGMVdue2sa/jwHk9YaI i96U9pHr6WOvNOwohbkCp+nIFV3MwAiJPycG+m7HmzVNap+TMDmGS1/VHH0GPeAtcLeVMX trnIjKzmZ9eTWsnNSJQhhPXxygF7nwEXsuH4pDadoSBbInBOeDx7H43J9topqg== X-Report-Abuse-To: abuse@transip.nl X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:20857, ipnet:149.210.128.0/17, country:NL] X-Rspamd-Queue-Id: 4VJG750qDkz4KKK Sure, will try tomorrow! Julf On 15/04/2024 15:58, Fred Finster wrote: > ZFS  ,  UFS  here are some webpages for Raspberry Pi 4B running FreeBSD > 14.0-RELEASE > > > I can show you how to transfer files from a booted USB Flash Disk drive > Stick to make your own USB SSD with a bootable ZFS file system using > about 4 or 5 shell script files to make the move of copying files from a > USB flash drive to a ZFS USB SSD. > > If you help me test, find errors, make corrections.  I will gladly help > you Julf and others who are interested in running FreeBSD on a USB SSD > with an installed ZFS file system. > > This is the bootable GhostBSD image I created.  You can use the FreeBSD > 14.0-RELEASE RPI image. > > I have setup a shell script to download  the FreeBSD image for your and > to uncompress this compressed XZ image. > > Select '0' to download the checksum value > Select '1' to download the FreeBSD 14.0-RELEASE image > Select '2' to download the GhostBSD-Arm64 image file from my package > NGINX web server http://ghostbsdarm64.hopto.org/packages/ > Select '3' to download from any URL you select > > > This is a 6k shell script file to download and perform the tasks for you. > http://ghostbsdarm64.hopto.org/packages/write_freebsd_img_dd_to_da1.sh > > http://ghostbsdarm64.hopto.org/packages/Ghost14_5G_selfbuilt_raspi4b_Feb27_2.img.xz This is a 728Megabyte file to downloaded by the previous 6k shell script file when selecting option '2' . > > > 500 GB setup for UFS ? > https://ghostbsd-arm64.blogspot.com/2022/02/booting-500-gb-ssd-on-freebsd-arm64-140.html > > 500 GB setup for Raspberry Pi 4B with FreeBSD O/S > https://ghostbsd-arm64.blogspot.com/2023/07/learning-zfs-on-root-setup-for.html > > https://ghostbsd-arm64.blogspot.com/2024/04/create-ghostbsd-usb-ssd-500gb-or-larger.html This is most for x86_64 but the commands are the same. > > https://ghostbsd-arm64.blogspot.com/2023/10/honey-i-broke-my-zfs-usb-sata-ssd-1-tb.html Here are short details, about how I fixed a boot problem with my ZFS disk for Raspberry Pi 4B. > > https://ghostbsd-arm64.blogspot.com/2024/01/hdmi-audio-sound-patches-into-ghostbsd.html Here are details for setting up the audio patch files to compile for FreeBSD and GhostBSD > > Here are details for setting up the 4 shell script files to create a ZFS > USB SSD. > > https://ghostbsd-arm64.blogspot.com/2023/12/zfs-boot-on-root-setup-for-usb-ssd.html > > I am sending now, Julf.  Reach out to me.  I can help you achieve a > working Desktop on Arm64 booting from a USB SSD. > > Fred Finster > fred@thegalacticzoo.com > fredfinster58@gmail.com > > >> */From:/* Johan Helsingius >> */Date:/* Thu, 11 Apr 2024 17:47:52 UTC >> On 11/04/2024 19:38, Mark Millard wrote: >> > Which image(s)? >> >> I think it was the memstick one. >> >> > Only the likes of, say, >> > >> > FreeBSD-14.0-STABLE-arm64-aarch64-RPI-20240404-72c3d91294c4-267114.img.xz >> > and: >> > FreeBSD-15.0-CURRENT-arm64-aarch64-RPI-20240404-112783ebbc31-269103.img.xz >> > and: >> > FreeBSD-14.0-RELEASE-arm64-aarch64-RPI.img.xz >> > >> > are set up with the extra materials that I referenced for the RPi*'s. Note: >> > Those are UFS based, not ZFS based. >> >> Ah! I see! Bummer that none of them are ZFS based, but I guess I can >> live with UFS on a RPi - it just means I have to have yet another >> backup procedure. >> >> > What did you put in da1p1 (efiboot0) ? That area you have >> > to deal with for bsdinstall usage. Some folks extract and >> > copy over what is in the msdosfs in a: >> > >> > *-arm64-aarch64-RPI-*.img.xz >> > >> > as a means of getting an officially-built set of such >> > materials when they want to customize other aspects. >> >> Would that make it possible to do a ZFS-based environment? >> >> Julf >> > From nobody Tue Apr 16 10:26:46 2024 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4VJgFR1xDjz5GZgL for ; Tue, 16 Apr 2024 10:26:51 +0000 (UTC) (envelope-from void@f-m.fm) Received: from fout8-smtp.messagingengine.com (fout8-smtp.messagingengine.com [103.168.172.151]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4VJgFQ33CXz53Dq for ; Tue, 16 Apr 2024 10:26:50 +0000 (UTC) (envelope-from void@f-m.fm) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=f-m.fm header.s=fm2 header.b=l2uSKXvF; dkim=pass header.d=messagingengine.com header.s=fm2 header.b=IyV4U2gr; dmarc=pass (policy=none) header.from=f-m.fm; spf=pass (mx1.freebsd.org: domain of void@f-m.fm designates 103.168.172.151 as permitted sender) smtp.mailfrom=void@f-m.fm Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailfout.nyi.internal (Postfix) with ESMTP id 05F5E13800CC for ; Tue, 16 Apr 2024 06:26:49 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Tue, 16 Apr 2024 06:26:49 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=f-m.fm; h=cc :content-type:content-type:date:date:from:from:in-reply-to :message-id:mime-version:reply-to:subject:subject:to:to; s=fm2; t=1713263209; x=1713349609; bh=o8V6wtjDZHZrRAvZ4CR4vX5hblQjGKl3 vpy3EgmI9n4=; b=l2uSKXvFFU2BRlehv2I7DBxdi1n4Z2cp+eg6qVHB/++bvtZR JxtToo827hLidVkuBp6b/4riZNiVVTkUbr3nZ6dXG2BOE6Z4Y3lq5ZtfTwdxqTH6 8nNfO8gTn7HMYNtuVLmFjwhSv6R06aTCli2WFVvwmj0g9vFhacJlZY1IdubsETHk mL59BpQlAuHzwkor39+OUzzm5BDx9lKefDivDr3mHOysDk9pGFk8P2NJ5nhCH+fj p/m++bnvhnXpjIZSs5LidafcZmFzPsGJGJVp8/t+6FvZ55hEJuJu+Bd2ncp4DPlv 5QZwTFgWE0/Y6MyPf46Qcifz5Sac42G6O7fHhg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:message-id :mime-version:reply-to:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t= 1713263209; x=1713349609; bh=o8V6wtjDZHZrRAvZ4CR4vX5hblQjGKl3vpy 3EgmI9n4=; b=IyV4U2grx/Pu5nMuZgz6YFv8mA+N00uuPmTP+TRoj+gHIBElkVm MW4cez3kqfZPTguOMEhN/LoLT1eOymADzUZPxSNzYHupo1Uj+/Q911CiopF3oUg2 v66S905T2gkiz51ZNWNC4IqGJ6+yj9FqdHTaMbK/7a/jaYORaI87nUpXKaDUcb+y yLgIe9XoY9UeiaRr7521kJJhX0sUL/WqPqmRdQAWSaH6yOhB/kyZyT4nImv1eYDK 2DTtA7Mk+Tv+W7tVbl7mH1Z9rLQntazHR8zAOjJGhrft+M6vsCA9G9TQ7t3zAbUw hAaVfmvCAYSQMgiTLbB3Ygb246UmmqgCZJw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrudejhedgtdefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkgggtugesthdtredttd dtvdenucfhrhhomhepvhhoihguuceovhhoihgusehfqdhmrdhfmheqnecuggftrfgrthht vghrnhepkeefudfggfeiueeiffehgfdvffejuddvhfdvieefledvjedthfdvheejhffgle eunecuffhomhgrihhnpehfrhgvvggsshgurdhorhhgnecuvehluhhsthgvrhfuihiivgep tdenucfrrghrrghmpehmrghilhhfrhhomhepvhhoihgusehfqdhmrdhfmh X-ME-Proxy: Feedback-ID: i2541463c:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Tue, 16 Apr 2024 06:26:48 -0400 (EDT) Date: Tue, 16 Apr 2024 11:26:46 +0100 From: void To: freebsd-arm@freebsd.org Subject: arm64 pkg builder Message-ID: Mail-Followup-To: freebsd-arm@freebsd.org List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.58 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.98)[-0.978]; MID_RHS_NOT_FQDN(0.50)[]; DMARC_POLICY_ALLOW(-0.50)[f-m.fm,none]; R_DKIM_ALLOW(-0.20)[f-m.fm:s=fm2,messagingengine.com:s=fm2]; R_SPF_ALLOW(-0.20)[+ip4:103.168.172.128/27]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[103.168.172.151:from]; FREEMAIL_FROM(0.00)[f-m.fm]; RCVD_TLS_LAST(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_COUNT_THREE(0.00)[3]; RCPT_COUNT_ONE(0.00)[1]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; FREEMAIL_ENVFROM(0.00)[f-m.fm]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; TO_DN_NONE(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[f-m.fm:+,messagingengine.com:+]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org]; ASN(0.00)[asn:209242, ipnet:103.168.172.0/24, country:US]; RCVD_VIA_SMTP_AUTH(0.00)[]; MISSING_XM_UA(0.00)[]; DWL_DNSWL_NONE(0.00)[messagingengine.com:dkim] X-Rspamd-Queue-Id: 4VJgFQ33CXz53Dq Hi @arm Is there an ipv4 method to check when the last run happened on the pkg builders *for arm64* and what the results were? I'm asking because rust seems to be at 1.76 on pkg.freebsd.org but 1.77 is in ports. -- From nobody Tue Apr 16 13:43:30 2024 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4VJlcW5MVkz5Gt9D for ; Tue, 16 Apr 2024 13:43:39 +0000 (UTC) (envelope-from SRS0=X0cx=LV=klop.ws=ronald-lists@realworks.nl) Received: from smtp-relay-int.realworks.nl (smtp-relay-int.realworks.nl [194.109.157.24]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4VJlcW3MvGz47GT for ; Tue, 16 Apr 2024 13:43:39 +0000 (UTC) (envelope-from SRS0=X0cx=LV=klop.ws=ronald-lists@realworks.nl) Authentication-Results: mx1.freebsd.org; none Date: Tue, 16 Apr 2024 15:43:30 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=klop.ws; s=rw2; t=1713275010; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=rMC+riWlGDWhoZTENtKoWZ52ft6rZVZ/k3LOtr48b9Q=; b=DYS9UvEJLywzN9BDhe+2jOh6Oo+SLYOEz/ymwaZz/lEjpsKtdGxU9lzgVn9e+PR88NBqSm Wb7FkbM2GimcDTkfisFN3WCF9J6838CKpMd8AUHHXZrOxPVgcJ3Aw9GjgOJrFcCCX552KT XeQqXjLsg03HZ3fGPOqKfYXufn2nW3b1T6TR+INPx0hEAob8JvGSyh0RGyy9dBmj3lDTha ZrohkjHn4IQwzGVPn9YkyPsoQmVpnW30XwQITjkj5RWsU8Rw14iGKTJKRPKI80n18sEeu+ /IXvYdatmmQDNn73Gq2sJP5IRSBaIddoxHi78gFuil6oR+2gULN8xl6N5wMrFg== From: Ronald Klop To: void Cc: freebsd-arm@freebsd.org Message-ID: <1739686710.10628.1713275010610@localhost> In-Reply-To: References: Subject: Re: arm64 pkg builder List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@FreeBSD.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_10627_1707272129.1713275010459" X-Mailer: Realworks (698.6) Importance: Normal X-Priority: 3 (Normal) X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:3265, ipnet:194.109.0.0/16, country:NL] X-Rspamd-Queue-Id: 4VJlcW3MvGz47GT ------=_Part_10627_1707272129.1713275010459 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit You can take a look here. https://pkg-status.freebsd.org/builds?all=1&type=package https://pkg-status.freebsd.org/ampere1/ https://pkg-status.freebsd.org/ampere2/ https://pkg-status.freebsd.org/ampere3/ Hope this helps. Ronald. Van: void Datum: dinsdag, 16 april 2024 12:26 Aan: freebsd-arm@freebsd.org Onderwerp: arm64 pkg builder > > Hi @arm > > Is there an ipv4 method to check when the last run happened on the > pkg builders *for arm64* and what the results were? > > I'm asking because rust seems to be at 1.76 on pkg.freebsd.org > but 1.77 is in ports. > > -- > > > > ------=_Part_10627_1707272129.1713275010459 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit You can take a look here.

https://pkg-status.freebsd.org/builds?all=1&type=package
https://pkg-status.freebsd.org/ampere1/
https://pkg-status.freebsd.org/ampere2/
https://pkg-status.freebsd.org/ampere3/

Hope this helps.

Ronald.


 

Van: void <void@f-m.fm>
Datum: dinsdag, 16 april 2024 12:26
Aan: freebsd-arm@freebsd.org
Onderwerp: arm64 pkg builder

Hi @arm

Is there an ipv4 method to check when the last run happened on the
pkg builders *for arm64* and what the results were?

I'm asking because rust seems to be at 1.76 on pkg.freebsd.org
but 1.77 is in ports.

-- 
 

  ------=_Part_10627_1707272129.1713275010459-- From nobody Tue Apr 16 17:46:52 2024 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4VJs1H3Wmfz5HFhm for ; Tue, 16 Apr 2024 17:46:59 +0000 (UTC) (envelope-from void@f-m.fm) Received: from wfhigh6-smtp.messagingengine.com (wfhigh6-smtp.messagingengine.com [64.147.123.157]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4VJs1G0h2Hz4fJt for ; Tue, 16 Apr 2024 17:46:58 +0000 (UTC) (envelope-from void@f-m.fm) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=f-m.fm header.s=fm2 header.b=XHch1d3v; dkim=pass header.d=messagingengine.com header.s=fm2 header.b=pStI0XBq; dmarc=pass (policy=none) header.from=f-m.fm; spf=pass (mx1.freebsd.org: domain of void@f-m.fm designates 64.147.123.157 as permitted sender) smtp.mailfrom=void@f-m.fm Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailfhigh.west.internal (Postfix) with ESMTP id 2CF601800130 for ; Tue, 16 Apr 2024 13:46:55 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Tue, 16 Apr 2024 13:46:55 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=f-m.fm; h=cc :content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:subject :subject:to:to; s=fm2; t=1713289614; x=1713376014; bh=jM6y0Is8dl Dd/TRU/ux9P21Hzk0wCxx6JV3NiN3FM40=; b=XHch1d3vZ83vdjqmnViY+4iXCS 6c2PZo2W5BlQxhAqtI/3d8i5lbC3F8OP68D+g9tMXeGUQF6waXAJj74P8jB3dE3S E2uQ26s+mJKvMKZka2m82DjFTpHr8tvwe3vZt61ChUPaaoOixhw8Mv7omFksoFiM XDsEl17B6ZA98WyA+5Gr95xmyiPWHcIwobSPU+Oyy54AIcY/ZcEFh7BBBruujBSh lrGbl+I90s5+6Jljb4m1FTL35GHYEw+xE+n9MxA7xzoMVjHcvaiU42dE2gUNufBS wBA6/tdTmJ2pdHb5u0KYIdlvj2L4Em7Exsd9SEMGt3TMxEC+XmT+Z91Dv/Uw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:subject:subject:to :to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; t=1713289614; x=1713376014; bh=jM6y0Is8dlDd/TRU/ux9P21Hzk0w Cxx6JV3NiN3FM40=; b=pStI0XBq+qVwrwsQsrB3BXhNawxvU4tDLQ6O/xwsUFFQ AsJOaRQJGeNI1Ij3QnMiEyD54I0J8UY1JkXl1OOtK5gMSfWtCUzNc+vupsi3fZZl 99NMDZBr83ysOx1v0mrVGykGRPNSKE8RcuPLDpuf6bdBiV0nD6YI1qtV1K7nsJ3e 9xbf7CvTMvXUwzA7By9oD8x0bXXbWyoHlJaJN3WJsgdwMGaJVV0xtrcda84Gk0ud d8kMG0f1QKLk/JHb9wnl4UVvP/fkJ9zaGRiP89NRCiUO8r3yK8LZMkhQMIAMWfOF 0TqGry4ElgC2Nw87SZQgOBWxg1CyCQ6rZJ6bpMHVvA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrudejiedgheehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkfhggtggujgesthdtre dttddtvdenucfhrhhomhepvhhoihguuceovhhoihgusehfqdhmrdhfmheqnecuggftrfgr thhtvghrnheptdfhheeuteejudffkefhtdfhfeekgedtvdeiteevgfejtdfgfeffhfeuie eltdeinecuffhomhgrihhnpehfrhgvvggsshgurdhorhhgnecuvehluhhsthgvrhfuihii vgeptdenucfrrghrrghmpehmrghilhhfrhhomhepvhhoihgusehfqdhmrdhfmh X-ME-Proxy: Feedback-ID: i2541463c:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Tue, 16 Apr 2024 13:46:54 -0400 (EDT) Date: Tue, 16 Apr 2024 18:46:52 +0100 From: void To: freebsd-arm@freebsd.org Subject: Re: arm64 pkg builder Message-ID: Mail-Followup-To: freebsd-arm@freebsd.org References: <1739686710.10628.1713275010610@localhost> List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <1739686710.10628.1713275010610@localhost> X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.21 / 15.00]; DWL_DNSWL_LOW(-1.00)[messagingengine.com:dkim]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.61)[-0.608]; MID_RHS_NOT_FQDN(0.50)[]; DMARC_POLICY_ALLOW(-0.50)[f-m.fm,none]; R_SPF_ALLOW(-0.20)[+ip4:64.147.123.128/27]; R_DKIM_ALLOW(-0.20)[f-m.fm:s=fm2,messagingengine.com:s=fm2]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[64.147.123.157:from]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_ALL(0.00)[]; ARC_NA(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+]; RCPT_COUNT_ONE(0.00)[1]; FROM_HAS_DN(0.00)[]; FREEMAIL_FROM(0.00)[f-m.fm]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; TO_DN_NONE(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[f-m.fm:+,messagingengine.com:+]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org]; ASN(0.00)[asn:29838, ipnet:64.147.123.0/24, country:US]; RCVD_VIA_SMTP_AUTH(0.00)[]; MISSING_XM_UA(0.00)[]; FREEMAIL_ENVFROM(0.00)[f-m.fm] X-Rspamd-Queue-Id: 4VJs1G0h2Hz4fJt On Tue, Apr 16, 2024 at 03:43:30PM +0200, Ronald Klop wrote: >You can take a look here. > >https://pkg-status.freebsd.org/builds?all=1&type=package >https://pkg-status.freebsd.org/ampere1/ >https://pkg-status.freebsd.org/ampere2/ >https://pkg-status.freebsd.org/ampere3/ > >Hope this helps. Yes it does, thank you :D -- From nobody Tue Apr 16 20:16:48 2024 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4VJwLF3vJyz5H12P for ; Tue, 16 Apr 2024 20:16:53 +0000 (UTC) (envelope-from pjfloyd@wanadoo.fr) Received: from msa.smtpout.orange.fr (smtp-75.smtpout.orange.fr [80.12.242.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "*.smtpout.orange.fr", Issuer "DigiCert Global G2 TLS RSA SHA256 2020 CA1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4VJwLD1MCmz47Bt for ; Tue, 16 Apr 2024 20:16:52 +0000 (UTC) (envelope-from pjfloyd@wanadoo.fr) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=wanadoo.fr header.s=t20230301 header.b=QxeNuXY5; dmarc=pass (policy=quarantine) header.from=wanadoo.fr; spf=pass (mx1.freebsd.org: domain of pjfloyd@wanadoo.fr designates 80.12.242.75 as permitted sender) smtp.mailfrom=pjfloyd@wanadoo.fr Received: from [192.168.1.28] ([90.112.30.115]) by smtp.orange.fr with ESMTPA id wpEWrklRHVYR4wpEWrbWGD; Tue, 16 Apr 2024 22:16:48 +0200 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wanadoo.fr; s=t20230301; t=1713298609; bh=RfvAYVUb55Spl33GFpFCuohWsIsLOFTVrwHyS3P0KJU=; h=Message-ID:Date:MIME-Version:To:From:Subject; b=QxeNuXY5tW14ooZBnfEskGlb5RuBiEV7MDhuuowMdDqrwCkzZgQO4pCkN+L4RzVo1 O8+UKVvFYrhELTWqAZJiGGCsTJ84flmVtGmoeTgsv+EfsFuUO3uI01MSMG4XQcGYbD 7OCaKiSLi3Hat0tjfGAEB/mPjfJVuediCwxETV7dX5XLVKbHLOFuuLc4f/kfpT3ov+ gqTNwmuQnrnkUeQj6HBqd2f2wNNt6inOUTno8lXIP0rc0x6cMnS1e8ZsI3lQbl3zUa TmfX0V4Ge3eyqwh3HtebZiq1/uwtOXWRdwYGdzNh06qO9owtBziIpiUyz4tUx0XMFw tJyGG9lQhzjZg== X-ME-Helo: [192.168.1.28] X-ME-Auth: cGpmbG95ZEB3YW5hZG9vLmZy X-ME-Date: Tue, 16 Apr 2024 22:16:49 +0200 X-ME-IP: 90.112.30.115 Message-ID: Date: Tue, 16 Apr 2024 20:16:48 +0000 List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird To: freebsd-arm@freebsd.org Content-Language: en-US From: Paul Floyd Subject: Valgrind on aarch64 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.08 / 15.00]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-0.99)[-0.993]; DMARC_POLICY_ALLOW(-0.50)[wanadoo.fr,quarantine]; R_DKIM_ALLOW(-0.20)[wanadoo.fr:s=t20230301]; R_SPF_ALLOW(-0.20)[+ip4:80.12.242.0/25]; RWL_MAILSPIKE_VERYGOOD(-0.20)[80.12.242.75:from]; ONCE_RECEIVED(0.10)[]; MIME_GOOD(-0.10)[text/plain]; XM_UA_NO_VERSION(0.01)[]; RCVD_TLS_LAST(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; TO_MATCH_ENVRCPT_ALL(0.00)[]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; DWL_DNSWL_NONE(0.00)[wanadoo.fr:dkim]; FREEMAIL_FROM(0.00)[wanadoo.fr]; FROM_HAS_DN(0.00)[]; FREEMAIL_ENVFROM(0.00)[wanadoo.fr]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org]; TO_DN_NONE(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[wanadoo.fr:+]; MID_RHS_MATCH_FROM(0.00)[]; ASN(0.00)[asn:3215, ipnet:80.12.240.0/20, country:FR]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_COUNT_ONE(0.00)[1]; RCVD_IN_DNSWL_NONE(0.00)[80.12.242.75:from] X-Rspamd-Queue-Id: 4VJwLD1MCmz47Bt Hi Valgrind now has support for FreeBSD aarch64. The code has been pushed upstream and I've opened a bugzilla item to update the port. Regards Paul From nobody Tue Apr 16 22:26:08 2024 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4VJzCY17npz5HD2R for ; Tue, 16 Apr 2024 22:26:17 +0000 (UTC) (envelope-from joseph@josephholsten.com) Received: from pb-smtp21.pobox.com (pb-smtp21.pobox.com [173.228.157.53]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4VJzCX6JNKz4lJl for ; Tue, 16 Apr 2024 22:26:16 +0000 (UTC) (envelope-from joseph@josephholsten.com) Authentication-Results: mx1.freebsd.org; none Received: from pb-smtp21.pobox.com (unknown [127.0.0.1]) by pb-smtp21.pobox.com (Postfix) with ESMTP id AC06E3351A; Tue, 16 Apr 2024 18:26:14 -0400 (EDT) (envelope-from joseph@josephholsten.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=pobox.com; h=from:to:cc :subject:date:message-id:in-reply-to:references:mime-version :content-type:content-transfer-encoding; s=sasl; bh=msTwCroKpt6w vzZFkLz/gPUfEZh8btXU5EgdWwNSO6I=; b=MFWq4tQXTdNW8MHbd9dmUocEV6xZ 8YJjMEShhNKjnb0wRqlxTOoeJbuDScJI4rLcBF8hqerkyJt/ibqIZruJVlCOeH23 50+SNYd99dbF2hVEjoZk1GJ4aaJMGu2rT9UjEABiYdGiCVtSfLcIoJWZYonriUAn FJTECEmmXDBZXGo= Received: from pb-smtp21.sea.icgroup.com (unknown [127.0.0.1]) by pb-smtp21.pobox.com (Postfix) with ESMTP id A4A9433519; Tue, 16 Apr 2024 18:26:14 -0400 (EDT) (envelope-from joseph@josephholsten.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=josephholsten.com; h=from:to:cc:subject:date:message-id:in-reply-to:references:mime-version:content-type:content-transfer-encoding; s=2016-12.pbsmtp; bh=9w3fYUwiJCaXTEBOzEXEDc/LhzL+e8UanO930b/r8eI=; b=D28BNw65Vhe5+mSpHRtzZ4ReLrdsVXAtu+CL04mcVbzpBb/vuSycXyv3R9Q00zWJHnBg2OGEGkO5AYc0Rt2lt4ecwjWK+uHiV6IVqhpe3oqDP71ujFcYSREJYrFhls9F5VkHS7RCxv6O0lnxSzeucJ+dBZO+fc0Lk+tq4QSqf6k= Received: from [100.109.181.67] (unknown [50.46.14.150]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pb-smtp21.pobox.com (Postfix) with ESMTPSA id 69BF733518; Tue, 16 Apr 2024 18:26:10 -0400 (EDT) (envelope-from joseph@josephholsten.com) From: "Joseph Holsten" To: "Paul Floyd" Cc: freebsd-arm@freebsd.org Subject: Re: Valgrind on aarch64 Date: Tue, 16 Apr 2024 15:26:08 -0700 X-Mailer: MailMate Trial (1.13.2r5673) Message-ID: <6AF26E1F-A6F1-4796-90E7-605AE9915B8B@josephholsten.com> In-Reply-To: References: List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8"; format=flowed; markup=markdown X-Pobox-Relay-ID: 53891B08-FC40-11EE-AF45-A19503B9AAD1-15777318!pb-smtp21.pobox.com Content-Transfer-Encoding: quoted-printable X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:29838, ipnet:173.228.157.0/24, country:US] X-Rspamd-Queue-Id: 4VJzCX6JNKz4lJl On 16 Apr 2024, at 13:16, Paul Floyd wrote: > Hi > > Valgrind now has support for FreeBSD aarch64. The code has been pushed=20 > upstream and I've opened a bugzilla item to update the port. That=E2=80=99s wonderful! I=E2=80=99ve been wanting to investigate a few = bugs I only=20 see on aarch64, thanks for letting us know. -- Joseph Holsten +1-360-927-7234 joseph@josephholsten.com From nobody Wed Apr 17 16:11:17 2024 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4VKQrS1Sdxz5H9Rk for ; Wed, 17 Apr 2024 16:11:20 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "generic", Issuer "generic" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4VKQrQ6HG6z55xH for ; Wed, 17 Apr 2024 16:11:18 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of fbsd@www.zefox.net has no SPF policy when checking 50.1.20.27) smtp.mailfrom=fbsd@www.zefox.net Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.17.1/8.17.1) with ESMTPS id 43HGBHQm041233 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Wed, 17 Apr 2024 09:11:18 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.17.1/8.17.1/Submit) id 43HGBHh4041232; Wed, 17 Apr 2024 09:11:17 -0700 (PDT) (envelope-from fbsd) Date: Wed, 17 Apr 2024 09:11:17 -0700 From: bob prohaska To: freebsd-arm@freebsd.org Cc: bob prohaska Subject: Tip echoing when it should not? Message-ID: List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit X-Spamd-Bar: + X-Spamd-Result: default: False [1.40 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; AUTH_NA(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; WWW_DOT_DOMAIN(0.50)[]; MID_RHS_WWW(0.50)[]; NEURAL_SPAM_SHORT(0.50)[0.499]; MIME_GOOD(-0.10)[text/plain]; MISSING_XM_UA(0.00)[]; RCVD_TLS_LAST(0.00)[]; TO_DN_SOME(0.00)[]; MIME_TRACE(0.00)[0:+]; ARC_NA(0.00)[]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US]; RCPT_COUNT_TWO(0.00)[2]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org]; R_DKIM_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; DMARC_NA(0.00)[zefox.net]; TO_MATCH_ENVRCPT_SOME(0.00)[]; R_SPF_NA(0.00)[no SPF record] X-Rspamd-Queue-Id: 4VKQrQ6HG6z55xH It appears that tip is mistakenly echoing characters when it picks up a stale connection. I've noticed this problem for a long time now, but this is the clearest example so far of what seems like undesirable behavior. Normally I keep a tip session running on a usb-serial adapter to monitor the GPIO serial console of (several) Raspberry Pi computers. The scheme is to ssh into one Pi, su to root and run tip on the usb-serial adapter, thus getting a console session that displays a login prompt and console messages on the connected Pi. >From time to time a login session is left running, and then the ssh session drops for reasons unclear but likely immaterial to the puzzle. On restarting the tip session at least some of the accumulated console output spews forth. On the face of it that seems good, since it lets me see output that would otherwise be lost. But, after re-connecting to the console, it looks as if some of the stale console output is being echoed back to the originating console and interpreted by that shell (which remains running) as a command. Here is an example. root@www:/home/bob # tip ucom [ucom:dv=/dev/cuaU0:br#115200:pa=none:] Stale lock on cuaU0 PID=1449... overriding. connected sW��cRSwh] Apr 16 18:40:41 www sshd[42733]: error: maximum authentication attempts exceeded for root from 14.225.192.42 port 55170 ssh2 [preauth] Apr 16 18:40:47 www sshd[42737]: error: maximum authentication attempts exceeded for invalid user admin from 14.225.192.42 port 50516 ssh2 [preauth] [lots of old console login failure reports] .... [roughly 100 lines of login failure messages] .... bob@www:~ % Apr 16 13:32:18 www sshd[42185]: fatal: Timeout before authentication for 110.7.52.1xJ^s Apr: No match. bob@www:~ % bob@www:~ % load: 2.98 not a controlling terminal load:: Too many arguments. bob@www:~ % bob@www:~ % ^R Modifier failed. bob@www:~ % bob@www:~ % Apr 16 13:32:18 www sshd[42185]: fatal: Timeout before authentication for Þ×gs^R Apr: No match. bob@www:~ % bob@www:~ % ×^s×^PgcÒÖs×ëgsÒÖs×ëãcJÖ^@Apr 17 08:38:42 www sshd[45444]: error: Fssh_kex_exchange_identification: read: Connection reset by peer Apr 17 08:45:19 www sshd[45466]: error: Fssh_kex_exchange_identification: read: Connection reset by peer It looks like the final lines include error messages issued by the shell running on the serial console. I didn't type them and wonder how input might be delivered to the shell. Is it possible that the usb-serial adapter is echoing received characters when tip has exited due to failure of the ssh session? If so, that seems highly undesirable, since console messages containing valid commands could be acted acted upon with the priviledge associated with the shell, which can be and is sometimes root. Apologies in advance if this is a dumb idea, but I'm seeing lots of very naive ssh attacks and starting to wonder if there's an ulterior motive for them. Thanks for reading, bob prohaska From nobody Thu Apr 18 00:04:54 2024 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4VKdM56CR5z5HR8M for ; Thu, 18 Apr 2024 00:05:05 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mx1.sbone.de (cross.sbone.de [195.201.62.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx1.sbone.de", Issuer "SBone.DE Root Certificate Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4VKdM46RvJz4lk0 for ; Thu, 18 Apr 2024 00:05:04 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of bzeeb-lists@lists.zabbadoz.net designates 195.201.62.131 as permitted sender) smtp.mailfrom=bzeeb-lists@lists.zabbadoz.net Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:4902:0:7404:2:1025]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.sbone.de (Postfix) with ESMTPS id 9B0458D4A177 for ; Thu, 18 Apr 2024 00:04:56 +0000 (UTC) Received: from content-filter.t4-02.sbone.de (content-filter.t4-02.sbone.de [IPv6:fde9:577b:c1a9:4902:0:7404:2:2742]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id 3C9F02D029D8 for ; Thu, 18 Apr 2024 00:04:56 +0000 (UTC) X-Virus-Scanned: amavisd-new at sbone.de Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:4902:0:7404:2:1025]) by content-filter.t4-02.sbone.de (content-filter.t4-02.sbone.de [IPv6:fde9:577b:c1a9:4902:0:7404:2:2742]) (amavisd-new, port 10024) with ESMTP id 1smEEwIF4DsY for ; Thu, 18 Apr 2024 00:04:55 +0000 (UTC) Received: from strong-iwl0.sbone.de (strong-iwl0.sbone.de [IPv6:fde9:577b:c1a9:4902:b66b:fcff:fef3:e3d2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id 47E252D029D2 for ; Thu, 18 Apr 2024 00:04:55 +0000 (UTC) Date: Thu, 18 Apr 2024 00:04:54 +0000 (UTC) From: "Bjoern A. Zeeb" To: freebsd-arm@freebsd.org Subject: suspend/resume on arm64? Message-ID: X-OpenPGP-Key-Id: 0x14003F198FEFA3E77207EE8D2B58B8F83CCF1842 List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset=US-ASCII X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.30 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; R_SPF_ALLOW(-0.20)[+ip4:195.201.62.131]; MIME_GOOD(-0.10)[text/plain]; FROM_HAS_DN(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; ASN(0.00)[asn:24940, ipnet:195.201.0.0/16, country:DE]; RCPT_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+]; MISSING_XM_UA(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org]; DMARC_NA(0.00)[zabbadoz.net]; TO_DN_NONE(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_LAST(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; ARC_NA(0.00)[] X-Rspamd-Queue-Id: 4VKdM46RvJz4lk0 Hi, I don't know but I assume some people have a Pinebook Pro or some other more or less supported Arm64 Laptop? Are they using ACPI? Can we suspend/resume there and if so, how? /bz -- Bjoern A. Zeeb r15:7 From nobody Sun Apr 21 12:33:52 2024 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4VMnqj0KfZz5J7sD for ; Sun, 21 Apr 2024 12:33:53 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4VMnqh2psZz3wtt for ; Sun, 21 Apr 2024 12:33:52 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1713702832; a=rsa-sha256; cv=none; b=DMfAi0zdXOKSzK0C5wxnmedUrcnamnCXdM/DWullEkBU5JoSP7oc9/vROyUztt3s5rWUq8 qugqNbodakoAS71NLLRGM0LEvzpXnEIEDpNQqbx5Rh3sX9l78QnKiyuTdmovRxA0MxTlc4 J6lYgK/BX9b02qgnm9WeY/kCOJWypSa9A24G4SmlERtgRmdOfw0Poz03S0kPI4tmOiUuh6 ZefMyarnY7YHANrX5dJiVj7+CmVF7x1oHo9mUyrYE+VyvVI3g40XlgHL7irjL/tVZtP35k ozD4A9+uZfjArEQbbLX6j0rcTYfyoF6IWahGjm7/uyH41McXZbZuBzkj5ZPlng== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1713702832; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=6XOVVByAW/j6T1DunC2I8LOtYM/5pmJWWMpEM9HpfzE=; b=UXTDY4NkNlH52IrKDXLUwGQsgkGiLWKyWDerRH0W8JwjoHSZkqPsuJ1g2FF8FMWcnd/Jjy qhBnaJeUnjO4C8mR6CulfxeDZ//tMeW+Caim3c67y0X12+8e0t1MSB0REEVGefkv3RN7Ep jPzAX8UAMyMZmyuOJD05ZYp4QQAOM8CMuX1GEx6haBliIZaPYhxaNK6BneGZan9LIl45xF XXH0UBufPHx4fISEZrPJNh0/9Uv1Z2CNIeXX1rcV6G+N99OOKOn1Ksw8fAGGPvUrZmatMn t8oyOyGmclzejCDrwO1jRiiPiLfHx2kpTLFLOyJrraEagTvMUyoW+riAP83fBg== Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4VMnqh1xpyz1KMx for ; Sun, 21 Apr 2024 12:33:52 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 43LCXqGU026768 for ; Sun, 21 Apr 2024 12:33:52 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 43LCXqTx026767 for freebsd-arm@FreeBSD.org; Sun, 21 Apr 2024 12:33:52 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-arm@FreeBSD.org Subject: [Bug 248138] aw_gpio: some hardware does not support reading input while in interrupt mode Date: Sun, 21 Apr 2024 12:33:52 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: arm X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: avg@FreeBSD.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-arm@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@FreeBSD.org MIME-Version: 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D248138 Andriy Gapon changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |Closed Resolution|--- |FIXED --=20 You are receiving this mail because: You are the assignee for the bug.= From nobody Sun Apr 21 21:00:41 2024 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4VN14V192kz5Hm4V for ; Sun, 21 Apr 2024 21:00:42 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4VN14T495Dz40Th for ; Sun, 21 Apr 2024 21:00:41 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1713733241; a=rsa-sha256; cv=none; b=UL3RRo5ZxI/+WbbMcwRVeFKO+50wB7Rcl35SrVoMCoWySlCMwV0cBGEH6jLh2KXX30VFoP 1R2muYgXA16ZjLZVtcTewg74n9hKYMVD4h03fye1HjVJwkCYo1nG9Iw/jt/Ghz/vA2UqI/ 0aRDqAA0nMqSl7LRFst2OYOzGrlBD5c3QsR54iIZK1M6mpEjUut5pZPDoCpwA8cSOzJur9 Qd+yXq7HNUkvgUqeUna7MDjdHYmFkNt3wPAgHlBg7B9OJWoiitOfXYpSSpyXTDLYcU+/Gd CCZfsQ3uloqJL/5OoInaZS86Wf7RwuuPhz6CGkPI3XaUlwgwPY7m+HuHYvkuNg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1713733241; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=aFKmjYoYpOhtGBUuDxmeVHJU/ZEDzIEkMhgUSRNbiuM=; b=x8kQN7BML2n04pxFYEbUMOk9sG9hY25UkxS/dGgkSa5TwLU6RqhwYEawdN62x04qSNKkz5 9XMYhITIvp6MkydkI1YG0vW5hFKrsqPNEwCJV420umRdBWKtnTjcV8dzf77hMMjEHc5EYU pJnrKsNpPRZGfPXb+/8TaqPLtDYRruYeju+zepmhRzVHlwTp8h0FtZoyn1PI0ysur+kulz 5rI5pjjk6Uf0FJyRcQRhn/6bvQ1EeYCCW4fj6Jkh5IKvjrl7TC2L9KfJ9rnm981ejWrpyP VYEHr2creKr5M1SLHrM+C5S2NBfB4/f1/qERJxPPfQMFvSKJ0wVitHOtHQajMw== Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4VN14T3kKDzLBw for ; Sun, 21 Apr 2024 21:00:41 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 43LL0fXa001998 for ; Sun, 21 Apr 2024 21:00:41 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 43LL0fYK001996 for freebsd-arm@FreeBSD.org; Sun, 21 Apr 2024 21:00:41 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <202404212100.43LL0fYK001996@kenobi.freebsd.org> X-Authentication-Warning: kenobi.freebsd.org: bugzilla set sender to bugzilla-noreply@FreeBSD.org using -f From: bugzilla-noreply@FreeBSD.org To: freebsd-arm@FreeBSD.org Subject: Problem reports for freebsd-arm@FreeBSD.org that need special attention Date: Sun, 21 Apr 2024 21:00:41 +0000 List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@FreeBSD.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="17137332414.ACCCC6D3.93982" Content-Transfer-Encoding: 7bit --17137332414.ACCCC6D3.93982 Date: Sun, 21 Apr 2024 21:00:41 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- Open | 264574 | sdhci(4): Support ACPI attachment in BCM2835_sdhc 1 problems total for which you should take action. --17137332414.ACCCC6D3.93982 Date: Sun, 21 Apr 2024 21:00:41 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" 
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and obsolete releases.

Status      |    Bug Id | Description
------------+-----------+---------------------------------------------------
Open        |    264574 | sdhci(4): Support ACPI attachment in BCM2835_sdhc

1 problems total for which you should take action.
--17137332414.ACCCC6D3.93982-- From nobody Sun Apr 21 23:14:23 2024 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4VN42m0js2z5HlJ2 for ; Sun, 21 Apr 2024 23:14:24 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4VN42l5yDjz4K6n for ; Sun, 21 Apr 2024 23:14:23 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1713741263; a=rsa-sha256; cv=none; b=FbreBMs0NZCaJB6MSf/9BjY2MRSSyxpu3oC6r4eY68tRBiYHrPeW/1gCMT5POi06DdNY58 s+P2J21WDmvyT+cncNqQ7Ve2VxtajrfWRpkJ9C9XLr6gPpj/xuXJGy2XVLF+1pDNkUQ2F8 dwin39mVU8NhKy4hO0ri1+tmJkudRj4W2by5S77U48jj1HGtEVmPC+lCTDb9Y9KR3puYM7 V7Dcs7i70lR2xfQmepTfTECNTBa/M769CxSCVK3vpJEylazDIcDzI73hCeWgcPGoDeRr62 XpQLIgT60LUZSwD3UoPQJxb4lcwCBrMHU6BbfiMEKCKn1vootUjD/hlaxRa53g== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1713741263; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=c9LCQoLi+QvAWmYSuZvf0Xofakf0ZH/Ez/V6wa6b1ng=; b=Y1IlE11Yf/bQTsQX0YG3AbksGLvIq3pZzog/4Vhe4hndfA/ANWaDbJsfDC1yyA2NgaqitI dLuugqxtm7r3UhLEYvKLYgEIRRyK8HTlwaubl5aUM7XnrnFHg1g702lN9rRkf6d6jUFxtM W/H1lPQrjTLo8KJp57LgI3+ozdjABRvjwUkAmvYxmMnANYtQGs1S0UdEhQMVjW+hplmd0t J5a3GOFQSFcPLU+cmpRbJCOo3R0UwQvc8+6cPRCfLPt9n1vmHodz+a0Leo0UPRVZej6KQx 4Hx6sUoqaHUR8pLngHnlPr7Tp4JKuWc8WUdZD8pyEZr0DThBtd6zDbXkFuPH+A== Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4VN42l5YrgzPfD for ; Sun, 21 Apr 2024 23:14:23 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 43LNENOi016641 for ; Sun, 21 Apr 2024 23:14:23 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 43LNEND9016640 for freebsd-arm@FreeBSD.org; Sun, 21 Apr 2024 23:14:23 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-arm@FreeBSD.org Subject: [Bug 260131] RPI [CM4 /io-ref.-board] panics on pcie with NVMe connected Date: Sun, 21 Apr 2024 23:14:23 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: arm X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: crash X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: maciphone2@googlemail.com X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-arm@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@FreeBSD.org MIME-Version: 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D260131 Klaus K=C3=BCchemann changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Open |Closed Resolution|--- |FIXED --=20 You are receiving this mail because: You are the assignee for the bug.=