From owner-freebsd-arm@freebsd.org Sun Jan 7 21:23:47 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6B9C4E5E79E for ; Sun, 7 Jan 2018 21:23:47 +0000 (UTC) (envelope-from peter@rulingia.com) Received: from vps.rulingia.com (vps.rulingia.com [103.243.244.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.rulingia.com", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EA8E6798EF for ; Sun, 7 Jan 2018 21:23:43 +0000 (UTC) (envelope-from peter@rulingia.com) Received: from server.rulingia.com (ppp59-167-167-3.static.internode.on.net [59.167.167.3]) by vps.rulingia.com (8.15.2/8.15.2) with ESMTPS id w07LChZn040592 (version=TLSv1.2 cipher=DHE-RSA-CHACHA20-POLY1305 bits=256 verify=OK) for ; Mon, 8 Jan 2018 08:12:50 +1100 (AEDT) (envelope-from peter@rulingia.com) X-Bogosity: Ham, spamicity=0.000000 Received: from server.rulingia.com (localhost.rulingia.com [127.0.0.1]) by server.rulingia.com (8.15.2/8.15.2) with ESMTPS id w07LCb2L066957 (version=TLSv1.2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256 verify=NO) for ; Mon, 8 Jan 2018 08:12:37 +1100 (AEDT) (envelope-from peter@server.rulingia.com) Received: (from peter@localhost) by server.rulingia.com (8.15.2/8.15.2/Submit) id w07LCbAt066956 for FreeBSD-arm@FreeBSD.org; Mon, 8 Jan 2018 08:12:37 +1100 (AEDT) (envelope-from peter) Date: Mon, 8 Jan 2018 08:12:37 +1100 From: Peter Jeremy To: FreeBSD-arm@FreeBSD.org Subject: FreeBSD on the Pinebook Message-ID: <20180107211237.GA66684@server.rulingia.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="7JfCtLOvnd9MIVvH" Content-Disposition: inline X-PGP-Key: http://www.rulingia.com/keys/peter.pgp User-Agent: Mutt/1.9.1 (2017-09-22) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Jan 2018 21:23:47 -0000 --7JfCtLOvnd9MIVvH Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Is any work being done to get FreeBSD running on the Pinebook? https://www.pine64.org/?page_id=3D3707 https://wiki.freebsd.org/FreeBSD/arm/Allwinner shows the A64 and Pine64 are supported but there's no framebuffer support listed so I presume it doesn't work (at least usefully) on the Pinebook. --=20 Peter Jeremy --7JfCtLOvnd9MIVvH Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJaUo1FXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRFRUIyOTg2QzMwNjcxRTc0RTY1QzIyN0Ux NkE1OTdBMEU0QTIwQjM0AAoJEBall6Dkogs02dYQAIFAVGOXLogBXxuiE/KvmzmG tGFAGq5ZNma22/aossZ998O5W2XsRdYigU4Qc4VjtymUuOTqP+3q9UUu5OIBwm5y XE/mo+BaY7p9P+bMUZ04F+OKMZOM4De30mKMRIuApxCni9FUU29S9495pE3C9nk+ vUb0gQsRwInDe29bLiw9uKxKuLqv+nJjIPUxikVBI7nAaofyld5obeK4kxsc4ALQ wOZUDt7gkekeXNr5uhrcN5KoCSY6oO5FhZUyOoB6tHylKzEVjragKvSLkPMwN1G9 voSn05WAEERj2qKsuMSVSK6NFlqUd2bjOiytBglx+CkCA2fE/egbg5zH5+1lBkyO 1CneP67QAG3T5uW69TEXlWJ81e6vnL9nqLb1228K54kr+YnPOprGjx61kl0sKlGY g0q6ibQb1R5jC0+iS1AZjQpk8rGCiP8r7PFeLXMOIjQFD75TABahXuIWgZn6Z6Rd BRtZpbnIQmloirPq11WOrA0jRTVZPOHjDhlbw6Vl4b9Xowu+68E1gT5PbYDXWTEn Ep2LI92dtLgTnQAs5yUQhUO/Wa6N6ZgZM1mnT4liiDS/kHpe6eBQI7jPEfzNgg+y F8Unfte1m+Q6L4S2L1XHxqkS3r7X/jf7DFjUaG0HfGjw/GzgR8Bfk6Ts3Uu+dGV6 QQAuThElM2n7lNgUjFYK =XSR5 -----END PGP SIGNATURE----- --7JfCtLOvnd9MIVvH-- From owner-freebsd-arm@freebsd.org Mon Jan 8 01:20:58 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 12841E6C62C for ; Mon, 8 Jan 2018 01:20:58 +0000 (UTC) (envelope-from unto.foru13@gmail.com) Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c:c09::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9CF2D82354 for ; Mon, 8 Jan 2018 01:20:57 +0000 (UTC) (envelope-from unto.foru13@gmail.com) Received: by mail-wm0-x233.google.com with SMTP id 64so11423124wme.3 for ; Sun, 07 Jan 2018 17:20:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=dc6xzkyqXSQueNhcGbvJrHV3vIRh6vbZ1JmQL5+vyHM=; b=u2YwH2MIrjSEuhLTy+3qS+CJIRCm+yIVum+wwwdvBVVWCXjtL1PaKOIWdDIeQK9IAK QdoHp7J7ko2AiKfn2FiCZqNTZkSWsuUdYmcl3MNpYpRDwzi83pm5kwwaCHa/5E39lRss GynDu/r3DaCl7fRNHZW9GRrt85mVeGwCKsSqYk0Yw7ge3TOZPXL5G5x02gb6XF5oAM7t zxHgD6sNexYswqdaugP+erIEYecREvFAgDTHrPXVF/ncl/wihwUCYFPnY33kevIKjf1u 8AKKjXXuhByn8qA/zFV/1OX2t0t0DeeiRW7hfxjzB6hw5Wujqgl17qLVjkH7+f1VPW61 tiiA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=dc6xzkyqXSQueNhcGbvJrHV3vIRh6vbZ1JmQL5+vyHM=; b=OXkL1VqyHNJV/+fWM5/2OGKHcrlV23Ovn7VSuVi3WDZKvdDhUtCPTl/G/zGtwB3DsK ak4grSckKa8nIl7wrEdB4GXQ4rlM9CSXXE393a+Mb+0P/blUr9rbQkqSTrldro90DBuY Gzm2NTxhIumSZD2ibA3nTEp86qPe1woj6BNwnQXTGe2Rs4slGGyrVZJaInp3/kH1YXfg Aw2i0Ojiat63L/Rgtm9d/E2HgLs9xwfo9fOZRSNPhS/wt5XCL9IhLEP41+TUV25d5yj7 OJd2NpRXuuWgQNDvghDDiWdVcYJQeTQjGWqsxIeREW7euRUaaSF+5TI1EQ7cuGAMFBH7 gdqw== X-Gm-Message-State: AKGB3mLRav0FWRch0KWbXjugzdJfXYx4z2VL0vMr3MHi+tc5Qqwi1/pk bDUVjbcEGqHrOjA6SsAS7iPDd1vGQZZXSSFzBDMRVw== X-Google-Smtp-Source: ACJfBotcGYDdNN+Vxqw9HBDouTXlahWBM70wMT7zJXB4fDXK7h9TbU3uFrzsLMJqQ/BtyTM5IWr4AoxC8QYr6li85gY= X-Received: by 10.80.179.45 with SMTP id q42mr14514879edd.71.1515374455469; Sun, 07 Jan 2018 17:20:55 -0800 (PST) MIME-Version: 1.0 Received: by 10.80.219.73 with HTTP; Sun, 7 Jan 2018 17:20:55 -0800 (PST) From: =?UTF-8?B?6Zi/6YeR?= Date: Mon, 8 Jan 2018 09:20:55 +0800 Message-ID: Subject: Orange pi one ,receive panic: bad pte2 To: freebsd-arm@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2018 01:20:58 -0000 Hello all, when I access SD files a lot (ex: find files,make port),I often got errors => panic: bad pte2, I thought maybe is my SD card problem,so I mount root file (/) to USB disk. the problem remain same. How could I fix this?? my board is Orange pi one FreeBSD 12.0-CURRENT #0 r326307M: Wed Jan 3 07:17:09 CST 2018 root@VirtualBox pi:/opt/head_obj/obj/opt/head/arm.armv6/sys/GENERIC arm FreeBSD clang version 5.0.0 (tags/RELEASE_500/final 312559) (based on LLVM 5.0.0svn) error messages => root@pi:/usr/ports/lang/python # make /bin/sh ../libtool --tag=CC --mode=link cc -O -pipe -Wno-error -fno-strict-aliasing -Wallpmap_remove_pages: pmap 0xc4b3f474 va 0x200a8000 pte2 0 panic: bad pte2 cpuid = 1 time = 1515036921 KDB: stack backtrace: db_trace_self() at db_trace_self pc = 0xc055f250 lr = 0xc005ef0c (db_trace_self_wrapper+0x30) sp = 0xde53bb80 fp = 0xde53bc98 db_trace_self_wrapper() at db_trace_self_wrapper+0x30 pc = 0xc005ef0c lr = 0xc026a318 (vpanic+0x158) sp = 0xde53bca0 fp = 0xde53bcc0 r4 = 0x00000100 r5 = 0x00000001 r6 = 0xc06e4869 r7 = 0xc092f530 vpanic() at vpanic+0x158 pc = 0xc026a318 lr = 0xc026a3b0 (kproc_shutdown) sp = 0xde53bcc8 fp = 0xde53bccc r4 = 0x00000000 r5 = 0x59e42001 r6 = 0xc19874b0 r7 = 0x00000001 r8 = 0xc4b3f474 r9 = 0xc1987000 r10 = 0xc19874f0 kproc_shutdown() at kproc_shutdown pc = 0xc026a3b0 lr = 0xc0578598 (pmap_remove_pages+0x8d0) sp = 0xde53bcd4 fp = 0xde53bd30 r4 = 0xc026a3b0 r5 = 0xde53bcd4 pmap_remove_pages() at pmap_remove_pages+0x8d0 pc = 0xc0578598 lr = 0xc05336c8 (vmspace_exit+0xc8) sp = 0xde53bd38 fp = 0xde53bd58 r4 = 0xc4b3f470 r5 = 0x00000001 r6 = 0xc09af630 r7 = 0xc4af4000 r8 = 0xc4b3f474 r9 = 0xc4b3f3c0 r10 = 0xc4aefae0 vmspace_exit() at vmspace_exit+0xc8 pc = 0xc05336c8 lr = 0xc022b5ec (exit1+0x5a4) sp = 0xde53bd60 fp = 0xde53bda8 r4 = 0xc4af4000 r5 = 0x00000000 r6 = 0xc4af4160 r7 = 0xc2c8301c r8 = 0xc4af40bc r9 = 0xc4af40ac r10 = 0xc4aefae0 exit1() at exit1+0x5a4 pc = 0xc022b5ec lr = 0xc022b048 (exit1) sp = 0xde53bdb0 fp = 0xde53bdb0 r4 = 0x00000000 r5 = 0xc0820964 r6 = 0xc4af4000 r7 = 0x00000000 r8 = 0x00000000 r9 = 0xc4aefae0 r10 = 0xc4aefd70 exit1() at exit1 pc = 0xc022b048 lr = 0xc05824ac (swi_handler+0x2c4) sp = 0xde53bdb8 fp = 0xde53be40 r4 = 0xc4af4000 r5 = 0x00000000 r6 = 0x00000000 r7 = 0xc4aefae0 r8 = 0xc4aefd70 r9 = 0xde53bdb0 r10 = 0xc022b048 swi_handler() at swi_handler+0x2c4 pc = 0xc05824ac lr = 0xc0561c20 (swi_exit) sp = 0xde53be48 fp = 0xbfbfe368 r4 = 0x00000000 r5 = 0xbfbfe150 r6 = 0x00032914 r7 = 0x00000001 r8 = 0xbfbfe3e8 r9 = 0x00000000 r10 = 0xbfbfe460 swi_exit() at swi_exit pc = 0xc0561c20 lr = 0xc0561c20 (swi_exit) sp = 0xde53be48 fp = 0xbfbfe368 KDB: enter: panic [ thread pid 8246 tid 100144 ] ********************************************************** other panic => config.status: creating src/Makefile pmap_remove_pages: pmap 0xc36ab0b4 va 0x202ed000 pte2 0 panic: bad pte2 cpuid = 3 time = 1515372625 KDB: stack backtrace: db_trace_self() at db_trace_self pc = 0xc055f250 lr = 0xc005ef0c (db_trace_self_wrapper+0x30) sp = 0xde0fbb80 fp = 0xde0fbc98 db_trace_self_wrapper() at db_trace_self_wrapper+0x30 pc = 0xc005ef0c lr = 0xc026a318 (vpanic+0x158) sp = 0xde0fbca0 fp = 0xde0fbcc0 r4 = 0x00000100 r5 = 0x00000001 r6 = 0xc06e4869 r7 = 0xc092f530 vpanic() at vpanic+0x158 pc = 0xc026a318 lr = 0xc026a3b0 (kproc_shutdown) sp = 0xde0fbcc8 fp = 0xde0fbccc r4 = 0x00000000 r5 = 0x4a731801 r6 = 0xc195eac8 r7 = 0x00000001 r8 = 0xc36ab0b4 r9 = 0xc195e000 r10 = 0xc195eb08 kproc_shutdown() at kproc_shutdown pc = 0xc026a3b0 lr = 0xc0578598 (pmap_remove_pages+0x8d0) sp = 0xde0fbcd4 fp = 0xde0fbd30 r4 = 0xc026a3b0 r5 = 0xde0fbcd4 pmap_remove_pages() at pmap_remove_pages+0x8d0 pc = 0xc0578598 lr = 0xc05336c8 (vmspace_exit+0xc8) sp = 0xde0fbd38 fp = 0xde0fbd58 r4 = 0xc36ab0b0 r5 = 0x00000001 r6 = 0xc09af630 r7 = 0xc360bac8 r8 = 0xc36ab0b4 r9 = 0xc36ab000 r10 = 0xc340a000 vmspace_exit() at vmspace_exit+0xc8 pc = 0xc05336c8 lr = 0xc022b5ec (exit1+0x5a4) sp = 0xde0fbd60 fp = 0xde0fbda8 r4 = 0xc360bac8 r5 = 0x00000000 r6 = 0xc360bc28 r7 = 0xc2c8301c r8 = 0xc360bb84 r9 = 0xc360bb74 r10 = 0xc340a000 exit1() at exit1+0x5a4 pc = 0xc022b5ec lr = 0xc022b048 (exit1) sp = 0xde0fbdb0 fp = 0xde0fbdb0 r4 = 0x00000000 r5 = 0xc0820964 r6 = 0xc360bac8 r7 = 0x00000000 r8 = 0x00000000 r9 = 0xc340a000 r10 = 0xc340a290 exit1() at exit1 pc = 0xc022b048 lr = 0xc05824ac (swi_handler+0x2c4) sp = 0xde0fbdb8 fp = 0xde0fbe40 r4 = 0xc360bac8 r5 = 0x00000000 r6 = 0x00000000 r7 = 0xc340a000 r8 = 0xc340a290 r9 = 0xde0fbdb0 r10 = 0xc022b048 swi_handler() at swi_handler+0x2c4 pc = 0xc05824ac lr = 0xc0561c20 (swi_exit) sp = 0xde0fbe48 fp = 0xbfbfe220 r4 = 0x00000000 r5 = 0xbfbfe008 r6 = 0x00032914 r7 = 0x00000001 r8 = 0xbfbfe2a0 r9 = 0x00000000 r10 = 0xbfbfe2ac swi_exit() at swi_exit pc = 0xc0561c20 lr = 0xc0561c20 (swi_exit) sp = 0xde0fbe48 fp = 0xbfbfe220 KDB: enter: panic [ thread pid 3818 tid 100087 ] Stopped at $d.3: ldrb r15, [r15, r15, ror r15]! db> bt Tracing pid 3818 tid 100087 td 0xc340a000 db_trace_self() at db_trace_self pc = 0xc055f250 lr = 0xc005bd00 (db_stack_trace+0x108) sp = 0xde0fb958 fp = 0xde0fb970 db_stack_trace() at db_stack_trace+0x108 pc = 0xc005bd00 lr = 0xc005b95c (db_command+0x268) sp = 0xde0fb978 fp = 0xde0fba18 r4 = 0x00000001 r5 = 0x00000000 r6 = 0xc06b24d4 r10 = 0x00000000 db_command() at db_command+0x268 pc = 0xc005b95c lr = 0xc005b6e4 (db_command_loop+0x74) sp = 0xde0fba20 fp = 0xde0fba30 r4 = 0xc067853c r5 = 0xc06a9d75 r6 = 0xc09ac664 r7 = 0xde0fbc00 r8 = 0xc08209a0 r9 = 0xc07afae8 r10 = 0xc093fe10 db_command_loop() at db_command_loop+0x74 pc = 0xc005b6e4 lr = 0xc005f094 (db_trap+0x12c) sp = 0xde0fba38 fp = 0xde0fbb50 r4 = 0x00000000 r5 = 0xc09ac670 r6 = 0xc093fe30 r10 = 0xc093fe10 db_trap() at db_trap+0x12c pc = 0xc005f094 lr = 0xc02b26e4 (kdb_trap+0x17c) sp = 0xde0fbb58 fp = 0xde0fbb80 r4 = 0x00000000 r5 = 0x00000001 r6 = 0xc093fe30 r7 = 0xde0fbc00 kdb_trap() at kdb_trap+0x17c pc = 0xc02b26e4 lr = 0xc05838fc (undefinedinstruction+0x30c) sp = 0xde0fbb88 fp = 0xde0fbbf8 r4 = 0x00000000 r5 = 0x00000000 r6 = 0xc0583540 r7 = 0xe7ffffff r8 = 0xde0fbc00 r9 = 0x00000001 r10 = 0xc02b1e30 undefinedinstruction() at undefinedinstruction+0x30c pc = 0xc05838fc lr = 0xc0561c90 (exception_exit) sp = 0xde0fbc00 fp = 0xde0fbc98 r4 = 0xa00000d3 r5 = 0x00000001 r6 = 0xc06e4869 r7 = 0xc092f530 r8 = 0xde0fbcd4 r9 = 0xc340a000 r10 = 0xc09afb28 exception_exit() at exception_exit pc = 0xc0561c90 lr = 0xc02b1e20 (kdb_enter+0x48) sp = 0xde0fbc90 fp = 0xde0fbc98 r0 = 0xc093fe20 r1 = 0x00000000 r2 = 0xde0fbbcc r3 = 0x00000215 r4 = 0xc06a9c4b r5 = 0x00000001 r6 = 0xc06e4869 r7 = 0xc092f530 r8 = 0xde0fbcd4 r9 = 0xc340a000 r10 = 0xc09afb28 r12 = 0x20000000 $a.4() at $a.4 pc = 0xc02b1e34 lr = 0xc026a33c (vpanic+0x17c) sp = 0xde0fbca0 fp = 0xde0fbcc0 r4 = 0x00000100 r10 = 0xc09afb28 vpanic() at vpanic+0x17c pc = 0xc026a33c lr = 0xc026a3b0 (kproc_shutdown) sp = 0xde0fbcc8 fp = 0xde0fbccc r4 = 0x00000000 r5 = 0x4a731801 r6 = 0xc195eac8 r7 = 0x00000001 r8 = 0xc36ab0b4 r9 = 0xc195e000 r10 = 0xc195eb08 kproc_shutdown() at kproc_shutdown pc = 0xc026a3b0 lr = 0xc0578598 (pmap_remove_pages+0x8d0) sp = 0xde0fbcd4 fp = 0xde0fbd30 r4 = 0xc026a3b0 r5 = 0xde0fbcd4 pmap_remove_pages() at pmap_remove_pages+0x8d0 pc = 0xc0578598 lr = 0xc05336c8 (vmspace_exit+0xc8) sp = 0xde0fbd38 fp = 0xde0fbd58 r4 = 0xc36ab0b0 r5 = 0x00000001 r6 = 0xc09af630 r7 = 0xc360bac8 r8 = 0xc36ab0b4 r9 = 0xc36ab000 r10 = 0xc340a000 vmspace_exit() at vmspace_exit+0xc8 pc = 0xc05336c8 lr = 0xc022b5ec (exit1+0x5a4) sp = 0xde0fbd60 fp = 0xde0fbda8 r4 = 0xc360bac8 r5 = 0x00000000 r6 = 0xc360bc28 r7 = 0xc2c8301c r8 = 0xc360bb84 r9 = 0xc360bb74 r10 = 0xc340a000 exit1() at exit1+0x5a4 pc = 0xc022b5ec lr = 0xc022b048 (exit1) sp = 0xde0fbdb0 fp = 0xde0fbdb0 r4 = 0x00000000 r5 = 0xc0820964 r6 = 0xc360bac8 r7 = 0x00000000 r8 = 0x00000000 r9 = 0xc340a000 r10 = 0xc340a290 exit1() at exit1 pc = 0xc022b048 lr = 0xc05824ac (swi_handler+0x2c4) sp = 0xde0fbdb8 fp = 0xde0fbe40 r4 = 0xc360bac8 r5 = 0x00000000 r6 = 0x00000000 r7 = 0xc340a000 r8 = 0xc340a290 r9 = 0xde0fbdb0 r10 = 0xc022b048 swi_handler() at swi_handler+0x2c4 pc = 0xc05824ac lr = 0xc0561c20 (swi_exit) sp = 0xde0fbe48 fp = 0xbfbfe220 r4 = 0x00000000 r5 = 0xbfbfe008 r6 = 0x00032914 r7 = 0x00000001 r8 = 0xbfbfe2a0 r9 = 0x00000000 r10 = 0xbfbfe2ac swi_exit() at swi_exit pc = 0xc0561c20 lr = 0xc0561c20 (swi_exit) sp = 0xde0fbe48 fp = 0xbfbfe220 From owner-freebsd-arm@freebsd.org Mon Jan 8 01:49:05 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3D1BCE6DB73 for ; Mon, 8 Jan 2018 01:49:05 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-141.reflexion.net [208.70.210.141]) (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 E031282F81 for ; Mon, 8 Jan 2018 01:49:04 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 15900 invoked from network); 8 Jan 2018 01:48:57 -0000 Received: from unknown (HELO rtc-sm-01.app.dca.reflexion.local) (10.81.150.1) by 0 (rfx-qmail) with SMTP; 8 Jan 2018 01:48:57 -0000 Received: by rtc-sm-01.app.dca.reflexion.local (Reflexion email security v8.40.4) with SMTP; Sun, 07 Jan 2018 20:48:57 -0500 (EST) Received: (qmail 4233 invoked from network); 8 Jan 2018 01:48:57 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 8 Jan 2018 01:48:57 -0000 Received: from [192.168.1.25] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id A1FECEC8BF3; Sun, 7 Jan 2018 17:48:56 -0800 (PST) From: Mark Millard Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Orange pi one ,receive panic: bad pte2 Date: Sun, 7 Jan 2018 17:48:56 -0800 References: To: =?utf-8?B?6Zi/6YeR?= , Freebsd-arm In-Reply-To: Message-Id: <8DD425C1-FEF4-4BC0-9A80-916B50620896@dsl-only.net> X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2018 01:49:05 -0000 On 2018-Jan-7, at 5:20 PM, =E9=98=BF=E9=87=91 = wrote: > when I access SD files a lot (ex: find files,make port),I often got = errors > =3D> panic: bad pte2, > I thought maybe is my SD card problem,so I mount root file (/) to USB = disk. > the problem remain same. > How could I fix this?? >=20 >=20 > my board is Orange pi one >=20 > FreeBSD 12.0-CURRENT #0 r326307M: Wed Jan 3 07:17:09 CST 2018 > root@VirtualBox pi:/opt/head_obj/obj/opt/head/arm.armv6/sys/GENERIC = arm > FreeBSD clang version 5.0.0 (tags/RELEASE_500/final 312559) (based on = LLVM > 5.0.0svn) >=20 . . . I saw such back on such old versions as well. For example: = https://lists.freebsd.org/pipermail/freebsd-hackers/2017-December/051942.h= tml is is report for the RPi2B V1.1 . -r326726 showed the "bad pte2" problem. But your example does not involve exec_elf32_imgact . (My examples might not have run into all cases of failure.) head -r327485 has not done such for me. Also, by then head had a fix for a boot-sometimes-hangs issue introduced in -r326347 . (There still can be hangups when plugging in USB drives after booting, at least on Pine64+ 2GBs.) =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-arm@freebsd.org Mon Jan 8 07:04:35 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EE5C9E7C0B1 for ; Mon, 8 Jan 2018 07:04:35 +0000 (UTC) (envelope-from bkwildasinn@gmail.com) Received: from mail-ua0-x229.google.com (mail-ua0-x229.google.com [IPv6:2607:f8b0:400c:c08::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A7DF86CFA9 for ; Mon, 8 Jan 2018 07:04:35 +0000 (UTC) (envelope-from bkwildasinn@gmail.com) Received: by mail-ua0-x229.google.com with SMTP id e39so6188851uae.12 for ; Sun, 07 Jan 2018 23:04:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=lCCkV5eJjYAXiZiDbLwBuo0BQ0LqmAEZaS1oBOlxI5o=; b=pVpsZvYEGJCWP+1IkR91LC7ml7F40Qh5TUaU/i6qhH3twD5cVHhAuzaDlnlUwTg9KX gwm22ARR19IazIM72O2vvWETKEX+jL0SYv8I2kjJZDJeTE3/0ZECfkerhvSAug9WLDTo jbPlV1s3fsIHFLzDo/Fug5n8Q4sb8Byjz9GHXEkohRDRDilf/DwVg63Vl7BQ6oYYE4zQ /QzZLJXpYquZupbPTS7lT2113+beNhneXL5nL/m8Xcd1/k/7Y+CDvD+zq1PUkdOY8r2J +3wlVigvB3tVRmtZIH+EuCNeBRofvmYFb64kuDxitfC3vOjte0q89H74+nIhXVwvPNcr Yrug== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=lCCkV5eJjYAXiZiDbLwBuo0BQ0LqmAEZaS1oBOlxI5o=; b=AjtZmA7VuUMTbnlEPPmPxyupfMoz5xyRmm1dw//uc79oomY3mBY4YO/wV1N3U1oPD9 xCo/sOh7gXwYs5Q8VB1x4fNvfv9kIestaxeBHy3NvcznGWB6U5fVLmB69wjCjvq8HTaf 65yk24aXVks4DnEya2virHYgmwbfSVb4t7Jhx02HZDYnmZcGGuJh95gV2hAOVYBRzyJz lPerSoOfZzbGuhfSeN5BgNnWP1kvfxWdjxOJxChszr231MYHHnWjB7vQj4LBYbKkgXPs 04XlUm289Y9eOpRGuiKuSMPtEC0UYQKq19YSiQIfy2fgFYloF+KOluo6XQCzr9Q71N8L 2DtQ== X-Gm-Message-State: AKwxyte59HE/ccAfWQfqkxuIQ5GutcetaL5Jqag8fB0BXdClbyNiApmR /w0mGl/4cj+vB2qMkj5kbbkIozB4l3Y08XzpCRw= X-Google-Smtp-Source: ACJfBouPe+xdyc5sp6RpClaRwMUrDzXAc+r583ocJY7ekq5m/uC9WihPvDMAA+yy5+H8ov6JGrU4dS9JL19aouynugU= X-Received: by 10.176.20.97 with SMTP id c30mr10476629uae.178.1515395074281; Sun, 07 Jan 2018 23:04:34 -0800 (PST) MIME-Version: 1.0 Received: by 10.159.34.230 with HTTP; Sun, 7 Jan 2018 23:04:33 -0800 (PST) Received: by 10.159.34.230 with HTTP; Sun, 7 Jan 2018 23:04:33 -0800 (PST) In-Reply-To: References: From: Brian Wildasinn Date: Sun, 7 Jan 2018 23:04:33 -0800 Message-ID: Subject: en-freebsd-doc missing in pkg.freebsd.org/FreeBSD:11:armv6/latest/All, but present in FreeBSD:11:amd64. To: freebsd-arm@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2018 07:04:36 -0000 Hellos, Looks like freebsd docs for world languages on armv6 packages are present while english has gone missing. Brian From owner-freebsd-arm@freebsd.org Mon Jan 8 10:58:46 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F40A8E63EA8 for ; Mon, 8 Jan 2018 10:58:45 +0000 (UTC) (envelope-from adridg@freebsd.org) Received: from smtp03.mail.online.nl (smtp03.mail.online.nl [194.134.25.73]) by mx1.freebsd.org (Postfix) with ESMTP id C2178759ED for ; Mon, 8 Jan 2018 10:58:45 +0000 (UTC) (envelope-from adridg@freebsd.org) Received: from smtp.online.nl (s55969a9e.adsl.online.nl [85.150.154.158]) by smtp03.mail.online.nl (Postfix) with ESMTP id 8AE681C00A6; Mon, 8 Jan 2018 11:49:14 +0100 (CET) From: Adriaan de Groot To: freebsd-arm@freebsd.org Subject: Re: FreeBSD on the Pinebook Date: Mon, 08 Jan 2018 11:49:08 +0100 Message-ID: <13327268.6xbMAFijLa@beastie.bionicmutton.org> Organization: FreeBSD In-Reply-To: <20180107211237.GA66684@server.rulingia.com> References: <20180107211237.GA66684@server.rulingia.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart3029089.GWLuFgd64g"; micalg="pgp-sha256"; protocol="application/pgp-signature" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2018 10:58:46 -0000 --nextPart3029089.GWLuFgd64g Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" On Sunday, 7 January 2018 22:12:37 CET Peter Jeremy wrote: > Is any work being done to get FreeBSD running on the Pinebook? > https://www.pine64.org/?page_id=3707 The hardware is pretty much interchangeable, except for the way the serial port works over the audio jack. The Pinebook is roughly / basically the pine64 board with some ports wired to the outside of the case. Linux images for the Pinebook work just fine on the Pine64+ board after replacing the u-boot blocks with Pine64+ versions thereof. I could borrow a Pinebook and check that the Pine64+ FreeBSD image boots on it just to be sure; I've got an audio-to-serial-pinout cable kicking around for this purpose, but .. > https://wiki.freebsd.org/FreeBSD/arm/Allwinner shows the A64 and Pine64 > are supported but there's no framebuffer support listed so I presume it > doesn't work (at least usefully) on the Pinebook. . without video output, there's not much use for the whole thing. Note there's just been a new binary-blob MALI 400 driver published on the Pine wiki, who knows what effect that might have. (I haven't tried latest Linux images with that new driver, getting the DRM blob to play nice with other kernels is quite an exercise). Basically I'd suggest getting the Pine64 to support video first, and then worrying about devices using it -- something similar applies to the Rock64 mentioned here recently (although that's a MALI 450 GPU, which I think FreeBSD supports on the ODROID C2+ .. gah, too many hardware variants running through my head, I'll get coffee first). [ade] --nextPart3029089.GWLuFgd64g Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- iHUEABEIAB0WIQTVFBoRsP760fy+Jisy7lRaPghTTwUCWlNMpAAKCRAy7lRaPghT T5FgAP9U8DWmGWTpCQtH49UN61PrJ7N9S9mFxs3RjUK2+4yUBgEA2bruWtjjxD/n e14TuXRoJzpmwfZfXEymzRV1M+9m0Hc= =geTy -----END PGP SIGNATURE----- --nextPart3029089.GWLuFgd64g-- From owner-freebsd-arm@freebsd.org Mon Jan 8 12:19:19 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 06321E6883C for ; Mon, 8 Jan 2018 12:19:19 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.blih.net", Issuer "mail.blih.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4F0B17855F; Mon, 8 Jan 2018 12:19:17 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) by mail.blih.net (OpenSMTPD) with ESMTP id e45a8726; Mon, 8 Jan 2018 13:19:15 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; s=mail; bh=gbplROJA7rdivKmdoPp/cC3d4mM=; b=ikXR7SUAK2UISOmrzQulbVRdlY5T MKnBhBnTEMY2hleV77k+Izn6cRvu+yLE8wdEwyr/Yk53/COXJUP7cJWgQebitHw3 /cd4qeE9hzJmHqm/KM9jzK6G9l2Gm45GInhVD/bjBuAr7ccsbCDNt1AF4QNZ0mKM tdiPKb6mc+a/RVc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; q=dns; s= mail; b=BhPcy2klYA60k318zLrpkoxOPi72MPyNKuqK+bFlKSvGDzmh5ctOaAlb o0pc1PagxEXLi3hkpULKLwaSg/HYdVuUkyG8/iqJCcIysE2JZtkMNDbJ8VHn943z /tMGp2JY53G/dGzB8kXvJ4rDw8HIBhXdvwn+3VDVusO5FAA5SxM= Received: from arcadia (evadot.gandi.net [217.70.181.36]) by mail.blih.net (OpenSMTPD) with ESMTPSA id 32c8f31a TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Mon, 8 Jan 2018 13:19:15 +0100 (CET) Date: Mon, 8 Jan 2018 13:19:14 +0100 From: Emmanuel Vadot To: Adriaan de Groot Cc: freebsd-arm@freebsd.org Subject: Re: FreeBSD on the Pinebook Message-Id: <20180108131914.53117e4b3e61fbaed6793b5e@bidouilliste.com> In-Reply-To: <13327268.6xbMAFijLa@beastie.bionicmutton.org> References: <20180107211237.GA66684@server.rulingia.com> <13327268.6xbMAFijLa@beastie.bionicmutton.org> X-Mailer: Sylpheed 3.6.0 (GTK+ 2.24.31; amd64-portbld-freebsd12.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2018 12:19:19 -0000 On Mon, 08 Jan 2018 11:49:08 +0100 Adriaan de Groot wrote: > On Sunday, 7 January 2018 22:12:37 CET Peter Jeremy wrote: > > Is any work being done to get FreeBSD running on the Pinebook? > > https://www.pine64.org/?page_id=3707 > > The hardware is pretty much interchangeable, except for the way the serial > port works over the audio jack. The Pinebook is roughly / basically the pine64 > board with some ports wired to the outside of the case. Linux images for the > Pinebook work just fine on the Pine64+ board after replacing the u-boot blocks > with Pine64+ versions thereof. Same for FreeBSD > I could borrow a Pinebook and check that the Pine64+ FreeBSD image boots on it > just to be sure; I've got an audio-to-serial-pinout cable kicking around for > this purpose, but .. > > > https://wiki.freebsd.org/FreeBSD/arm/Allwinner shows the A64 and Pine64 > > are supported but there's no framebuffer support listed so I presume it > > doesn't work (at least usefully) on the Pinebook. > > . without video output, there's not much use for the whole thing. Note > there's just been a new binary-blob MALI 400 driver published on the Pine > wiki, who knows what effect that might have. (I haven't tried latest Linux > images with that new driver, getting the DRM blob to play nice with other > kernels is quite an exercise). It has nothing to do with MALI, MALI is the gpu (discrete GPU one could say) and even with MALI support (which we don't have and, I think, never will) we still need display engine driver (which drives the framebuffer, hdmi, lcd etc ...) > Basically I'd suggest getting the Pine64 to support video first, and then > worrying about devices using it -- something similar applies to the Rock64 > mentioned here recently (although that's a MALI 450 GPU, which I think FreeBSD > supports on the ODROID C2+ .. gah, too many hardware variants running through > my head, I'll get coffee first). > > [ade] I have efifb mostly working on Pine64 but our pmap code needs some love. -- Emmanuel Vadot From owner-freebsd-arm@freebsd.org Mon Jan 8 15:40:33 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 604B6E731AB for ; Mon, 8 Jan 2018 15:40:33 +0000 (UTC) (envelope-from hlh@restart.be) Received: from tignes.restart.be (tignes.restart.be [IPv6:2001:41d0:8:bdbe:0:1::]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "tignes.restart.be", Issuer "CA master" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 28C5E80AD1 for ; Mon, 8 Jan 2018 15:40:33 +0000 (UTC) (envelope-from hlh@restart.be) X-Comment: SPF check N/A for local connections - client-ip=192.168.25.127; helo=restart.be; envelope-from=hlh@restart.be; receiver=freebsd-arm@freebsd.org DKIM-Filter: OpenDKIM Filter v2.10.3 tignes.restart.be 3zFfcG5jhszsKv Received: from restart.be (norquay.tunnel.bel [192.168.25.127]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.restart.be", Issuer "CA master" (verified OK)) by tignes.restart.be (Postfix) with ESMTPS id 3zFfcG5jhszsKv for ; Mon, 8 Jan 2018 16:40:30 +0100 (CET) Received: from chamonix.restart.bel (chamonix.restart.bel [192.168.24.9]) (authenticated bits=0) by restart.be (8.15.2/8.15.2) with ESMTPSA id w08FeSah046801 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Mon, 8 Jan 2018 16:40:29 +0100 (CET) (envelope-from hlh@restart.be) To: FreeBSD-arm@FreeBSD.org From: Henri Hennebert Subject: Pine64+ - 12.0-CURRENT #0 r327665 don't detect awg0 Message-ID: <98a73723-005d-1178-b8b7-beeb65ba5ad5@restart.be> Date: Mon, 8 Jan 2018 16:40:28 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: fr-classic Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2018 15:40:33 -0000 Hello, When I boot 12.0-CURRENT #0 r327665 in verbose mode with U-Boot 2017.09 (Dec 12 2017 - 21:15:33 +0000) on Pine64+ I get: simplebus0: mem 0x1c30000-0x1c31fff,0x1c00030-0x1c00033 irq 27 compat allwinner,sun50i-a64-emac (no driver attached) Henri From owner-freebsd-arm@freebsd.org Mon Jan 8 15:51:25 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E945FE73A2E for ; Mon, 8 Jan 2018 15:51:25 +0000 (UTC) (envelope-from byond.lenox@gmail.com) Received: from mail-io0-f180.google.com (mail-io0-f180.google.com [209.85.223.180]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B92C3816D8 for ; Mon, 8 Jan 2018 15:51:22 +0000 (UTC) (envelope-from byond.lenox@gmail.com) Received: by mail-io0-f180.google.com with SMTP id 87so14551993ior.5 for ; Mon, 08 Jan 2018 07:51:22 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=qAYPiSRY+uDjbr2XK3YV/HWjrmggjzHdY1bbiXW2new=; b=aOT9iBvIc8HqQTbIfKqZQX31N9dHCRsRL85G9Ou66UXgZjysaCp57lDvplfi9cGpt3 y5Bauu3dVt9bb53k84lfGWSLUHxHe32+c8QZMt74EEoGUAlO8TcTzcQ4vngpgqGm0fpc b2tosp5TK80oY3UeR7W68OGvKYUtSTKbKr5XpSPz/LLdCBemdveV680DxqtF2J0efKoC zgF20nG4D6mTeIyhomTiX3Zr8UdJD/uSVCXCVPGth/PV6eqg0YrU0R9UUlN7M7RhzOkS ZKJvxL0j2kBIe/Cfk+mueZvvts/Cij2w2zR42cbGrbtXEbLuuOZUYqRkKxF70Tr1iTWT QByA== X-Gm-Message-State: AKwxytcOj4aJauq0hbENVBr7PKFQnxqQpyTtOhpUGz+8A7YxODqpviZW ohvzKb0hFU+PE/KBdGILAXvoK+Yi X-Google-Smtp-Source: ACJfBouBxGph5Ue6uu84R/S3i21KmCKeC0Lel6bxz3sX/3dedvRrcY6i5FCHmWcV3/4CioAnQRK3dQ== X-Received: by 10.107.97.24 with SMTP id v24mr11148088iob.222.1515426302309; Mon, 08 Jan 2018 07:45:02 -0800 (PST) Received: from mail-io0-f173.google.com (mail-io0-f173.google.com. [209.85.223.173]) by smtp.gmail.com with ESMTPSA id 3sm7092002itk.19.2018.01.08.07.45.01 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 08 Jan 2018 07:45:01 -0800 (PST) Received: by mail-io0-f173.google.com with SMTP id k18so14507270ioc.11 for ; Mon, 08 Jan 2018 07:45:01 -0800 (PST) X-Received: by 10.107.5.142 with SMTP id 136mr12066340iof.239.1515426301164; Mon, 08 Jan 2018 07:45:01 -0800 (PST) MIME-Version: 1.0 Received: by 10.107.149.147 with HTTP; Mon, 8 Jan 2018 07:44:40 -0800 (PST) In-Reply-To: <98a73723-005d-1178-b8b7-beeb65ba5ad5@restart.be> References: <98a73723-005d-1178-b8b7-beeb65ba5ad5@restart.be> From: Kyle Evans Date: Mon, 8 Jan 2018 09:44:40 -0600 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Pine64+ - 12.0-CURRENT #0 r327665 don't detect awg0 To: Henri Hennebert Cc: "freebsd-arm@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2018 15:51:26 -0000 On Mon, Jan 8, 2018 at 9:40 AM, Henri Hennebert wrote: > Hello, > > When I boot 12.0-CURRENT #0 r327665 in verbose mode with > U-Boot 2017.09 (Dec 12 2017 - 21:15:33 +0000) on Pine64+ > I get: > > simplebus0: mem 0x1c30000-0x1c31fff,0x1c00030-0x1c00033 > irq 27 compat allwinner,sun50i-a64-emac (no driver attached) Hi, Can you post the rest of this dmesg, so we can see fully what's going on with awg/syscon interaction? > Henri Thanks, Kyle Evans From owner-freebsd-arm@freebsd.org Mon Jan 8 16:03:33 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 60081E74624 for ; Mon, 8 Jan 2018 16:03:33 +0000 (UTC) (envelope-from hlh@restart.be) Received: from tignes.restart.be (tignes.restart.be [IPv6:2001:41d0:8:bdbe:0:1::]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "tignes.restart.be", Issuer "CA master" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id CBA8F8229C; Mon, 8 Jan 2018 16:03:32 +0000 (UTC) (envelope-from hlh@restart.be) X-Comment: SPF check N/A for local connections - client-ip=192.168.25.127; helo=restart.be; envelope-from=hlh@restart.be; receiver=kevans@freebsd.org DKIM-Filter: OpenDKIM Filter v2.10.3 tignes.restart.be 3zFg6p6L4VzsVn Received: from restart.be (norquay.tunnel.bel [192.168.25.127]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.restart.be", Issuer "CA master" (verified OK)) by tignes.restart.be (Postfix) with ESMTPS id 3zFg6p6L4VzsVn; Mon, 8 Jan 2018 17:03:30 +0100 (CET) Received: from chamonix.restart.bel (chamonix.restart.bel [192.168.24.9]) (authenticated bits=0) by restart.be (8.15.2/8.15.2) with ESMTPSA id w08G3SOK047013 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 8 Jan 2018 17:03:29 +0100 (CET) (envelope-from hlh@restart.be) Subject: Re: Pine64+ - 12.0-CURRENT #0 r327665 don't detect awg0 To: Kyle Evans Cc: "freebsd-arm@freebsd.org" References: <98a73723-005d-1178-b8b7-beeb65ba5ad5@restart.be> From: Henri Hennebert Message-ID: <44f39a02-a989-c077-d163-1406e64a53de@restart.be> Date: Mon, 8 Jan 2018 17:03:28 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: fr-classic Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2018 16:03:33 -0000 On 01/08/2018 16:44, Kyle Evans wrote: > On Mon, Jan 8, 2018 at 9:40 AM, Henri Hennebert wrote: >> Hello, >> >> When I boot 12.0-CURRENT #0 r327665 in verbose mode with >> U-Boot 2017.09 (Dec 12 2017 - 21:15:33 +0000) on Pine64+ >> I get: >> >> simplebus0: mem 0x1c30000-0x1c31fff,0x1c00030-0x1c00033 >> irq 27 compat allwinner,sun50i-a64-emac (no driver attached) > > Hi, > > Can you post the rest of this dmesg, so we can see fully what's going > on with awg/syscon interaction? OK boot -v -s Booting... Using DTB provided by EFI at 0x48000000. KDB: debugger backends: ddb KDB: current backend: ddb Found 4 CPUs in the device tree Copyright (c) 1992-2018 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 12.0-CURRENT #0 r327665M: Mon Jan 8 13:55:28 CET 2018 root@nakiska.restart.bel:/usr/obj/usr/src/arm64.aarch64/sys/NORQUAY arm64 FreeBSD clang version 5.0.1 (tags/RELEASE_501/final 320880) (based on LLVM 5.0.1) VT: init without driver. Preloaded elf kernel "/boot/kernel/kernel" at 0xffff000000d45000. Preloaded boot_entropy_cache "/boot/entropy" at 0xffff000000d45db0. Starting CPU 1 (1) Starting CPU 2 (2) Starting CPU 3 (3) FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs random: read 3840 bytes from preloaded cache random: unblocking device. arc4random: read 32 bytes from preloaded cache ULE: setup cpu 0 ULE: setup cpu 1 ULE: setup cpu 2 ULE: setup cpu 3 random: entropy device external interface nfslock: pseudo-device crypto: kbd0 at kbdmux0 mem: null: openfirm: random: harvesting attach, 8 bytes (4 bits) from nexus0 ofwbus0: clk_fixed0: on ofwbus0 random: harvesting attach, 8 bytes (4 bits) from clk_fixed0 clk_fixed1: on ofwbus0 random: harvesting attach, 8 bytes (4 bits) from clk_fixed1 clk_fixed2: on ofwbus0 random: harvesting attach, 8 bytes (4 bits) from clk_fixed2 simplebus0: on ofwbus0 aw_ccung0: mem 0x1c20000-0x1c203ff on simplebus0 aw_ccung0: Setting pll_periph0 as parent for ahb1 aw_ccung0: Setting pll_periph0 as parent for ahb2 aw_ccung0: Setting pll_ddr0 as parent for dram Clock: pll_cpux, parent: osc24M(0), freq: 816000000 Clock: pll_audio, parent: osc24M(0), freq: 24571428 Clock: pll_periph0_2x, parent: osc24M(0), freq: 600000000 Clock: pll_periph1_2x, parent: osc24M(0), freq: 600000000 Clock: pll_ddr0, parent: osc24M(0), freq: 408000000 Clock: pll_ddr1, parent: osc24M(0), freq: 1344000000 Clock: pll_video0, parent: osc24M(0), freq: 30303 Clock: pll_video1, parent: osc24M(0), freq: 30303 Clock: pll_ve, parent: osc24M(0), freq: 30303 Clock: pll_gpu, parent: osc24M(0), freq: 30303 Clock: pll_de, parent: osc24M(0), freq: 30303 Clock: pll_hsic, parent: osc24M(0), freq: 1200000 Clock: apb2, parent: osc24M(1), freq: 24000000 Clock: nand, parent: osc24M(0), freq: 24000000 Clock: mmc0, parent: pll_periph0_2x(1), freq: 50000000 Clock: mmc1, parent: osc24M(0), freq: 24000000 Clock: mmc2, parent: osc24M(0), freq: 24000000 Clock: ts, parent: osc24M(0), freq: 24000000 Clock: ce, parent: osc24M(0), freq: 24000000 Clock: spi0, parent: osc24M(0), freq: 24000000 Clock: spi1, parent: osc24M(0), freq: 24000000 Clock: spdif, parent: pll_audio(0), freq: 24571428 Clock: dram, parent: pll_ddr0(0), freq: 408000000 Clock: de, parent: pll_periph0_2x(0), freq: 600000000 Clock: deinterlace, parent: pll_periph0(0), freq: 300000000 Clock: csi-sclk, parent: pll_periph0(0), freq: 300000000 Clock: csi-mclk, parent: osc24M(0), freq: 24000000 Clock: ve, parent: pll_ve(0), freq: 30303 Clock: hdmi, parent: pll_video0(0), freq: 30303 Clock: mbus, parent: pll_periph0_2x(1), freq: 200000000 Clock: gpu, parent: pll_gpu(0), freq: 30303 Clock: ahb1, parent: pll_periph0(3), freq: 300000000 Clock: ahb2, parent: pll_periph0(1), freq: 150000000 Clock: cpux, parent: pll_cpux(2), freq: 816000000 Clock: i2s0mux, parent: pll_audio-8x(0), freq: 196571424 Clock: i2s1mux, parent: pll_audio-8x(0), freq: 196571424 Clock: i2s2mux, parent: pll_audio-8x(0), freq: 196571424 Clock: axi, parent: cpux(0), freq: 204000000 Clock: apb1, parent: ahb1(0), freq: 75000000 Clock: apb, parent: cpux(0), freq: 272000000 Clock: osc12M, parent: osc24M(0), freq: 12000000 Clock: pll_periph0, parent: pll_periph0_2x(0), freq: 300000000 Clock: pll_periph1, parent: pll_periph1_2x(0), freq: 300000000 Clock: pll_audio-2x, parent: pll_audio(0), freq: 49142856 Clock: pll_audio-4x, parent: pll_audio(0), freq: 98285712 Clock: pll_audio-8x, parent: pll_audio(0), freq: 196571424 Clock: bus-mipi-dsi, parent: ahb1(0), freq: 300000000 Clock: bus-ce, parent: ahb1(0), freq: 300000000 Clock: bus-dma, parent: ahb1(0), freq: 300000000 Clock: bus-mmc0, parent: ahb1(0), freq: 300000000 Clock: bus-mmc1, parent: ahb1(0), freq: 300000000 Clock: bus-mmc2, parent: ahb1(0), freq: 300000000 Clock: bus-nand, parent: ahb1(0), freq: 300000000 Clock: bus-dram, parent: ahb1(0), freq: 300000000 Clock: bus-emac, parent: ahb2(0), freq: 150000000 Clock: bus-ts, parent: ahb1(0), freq: 300000000 Clock: bus-hstimer, parent: ahb1(0), freq: 300000000 Clock: bus-spi0, parent: ahb1(0), freq: 300000000 Clock: bus-spi1, parent: ahb1(0), freq: 300000000 Clock: bus-otg, parent: ahb1(0), freq: 300000000 Clock: bus-ehci0, parent: ahb1(0), freq: 300000000 Clock: bus-ehci1, parent: ahb2(0), freq: 150000000 Clock: bus-ohci0, parent: ahb1(0), freq: 300000000 Clock: bus-ohci1, parent: ahb2(0), freq: 150000000 Clock: bus-ve, parent: ahb1(0), freq: 300000000 Clock: bus-tcon0, parent: ahb1(0), freq: 300000000 Clock: bus-tcon1, parent: ahb1(0), freq: 300000000 Clock: bus-deinterlace, parent: ahb1(0), freq: 300000000 Clock: bus-csi, parent: ahb1(0), freq: 300000000 Clock: bus-hdmi, parent: ahb1(0), freq: 300000000 Clock: bus-de, parent: ahb1(0), freq: 300000000 Clock: bus-gpu, parent: ahb1(0), freq: 300000000 Clock: bus-msgbox, parent: ahb1(0), freq: 300000000 Clock: bus-spinlock, parent: ahb1(0), freq: 300000000 Clock: bus-codec, parent: apb1(0), freq: 75000000 Clock: bus-spdif, parent: apb1(0), freq: 75000000 Clock: bus-pio, parent: apb1(0), freq: 75000000 Clock: bus-ths, parent: apb1(0), freq: 75000000 Clock: bus-i2s0, parent: apb1(0), freq: 75000000 Clock: bus-i2s1, parent: apb1(0), freq: 75000000 Clock: bus-i2s2, parent: apb1(0), freq: 75000000 Clock: bus-i2c0, parent: apb2(0), freq: 24000000 Clock: bus-i2c1, parent: apb2(0), freq: 24000000 Clock: bus-i2c2, parent: apb2(0), freq: 24000000 Clock: bus-src, parent: apb2(0), freq: 24000000 Clock: bus-uart0, parent: apb2(0), freq: 24000000 Clock: bus-uart1, parent: apb2(0), freq: 24000000 Clock: bus-uart2, parent: apb2(0), freq: 24000000 Clock: bus-uart3, parent: apb2(0), freq: 24000000 Clock: bus-uart4, parent: apb2(0), freq: 24000000 Clock: bus-dbg, parent: ahb1(0), freq: 300000000 Clock: usb-phy0, parent: osc24M(0), freq: 24000000 Clock: usb-phy1, parent: osc24M(0), freq: 24000000 Clock: usb-hsic, parent: pll_hsic(0), freq: 1200000 Clock: usb-hsic-12M, parent: osc12M(0), freq: 12000000 Clock: usb-ohci0, parent: osc12M(0), freq: 12000000 Clock: usb-ohci1, parent: usb-ohci0(0), freq: 12000000 Clock: dram-ve, parent: dram(0), freq: 408000000 Clock: dram-csi, parent: dram(0), freq: 408000000 Clock: dram-deinterlace, parent: dram(0), freq: 408000000 Clock: dram-ts, parent: dram(0), freq: 408000000 Clock: csi-misc, parent: osc24M(0), freq: 24000000 Clock: ac-dig, parent: pll_audio(0), freq: 24571428 Clock: ac-dig-4x, parent: pll_audio-4x(0), freq: 98285712 Clock: avs, parent: osc24M(0), freq: 24000000 Clock: hdmi-ddc, parent: osc24M(0), freq: 24000000 random: harvesting attach, 8 bytes (4 bits) from aw_ccung0 aw_ccung1: mem 0x1f01400-0x1f014ff on simplebus0 Clock: ar100, parent: osc32k(0), freq: 32768 Clock: apb0, parent: ahb0(0), freq: 32768 Clock: ahb0, parent: ar100(0), freq: 32768 Clock: apb0-pio, parent: apb0(0), freq: 32768 Clock: apb0-ir, parent: apb0(0), freq: 32768 Clock: apb0-timer, parent: apb0(0), freq: 32768 Clock: apb0-rsb, parent: apb0(0), freq: 32768 Clock: apb0-uart, parent: apb0(0), freq: 32768 Clock: apb0-i2c, parent: apb0(0), freq: 32768 Clock: apb0-twd, parent: apb0(0), freq: 32768 random: harvesting attach, 8 bytes (4 bits) from aw_ccung1 random: harvesting attach, 8 bytes (4 bits) from simplebus0 regfix0: on ofwbus0 random: harvesting attach, 8 bytes (4 bits) from regfix0 random: harvesting attach, 8 bytes (4 bits) from ofwbus0 psci0: on ofwbus0 psci0: PSCI version 0.2 compatible random: harvesting attach, 8 bytes (4 bits) from psci0 awusbphy0: mem 0x1c19400-0x1c19413,0x1c1a800-0x1c1a803,0x1c1b800-0x1c1b803 on simplebus0 random: harvesting attach, 8 bytes (4 bits) from awusbphy0 gic0: mem 0x1c81000-0x1c81fff,0x1c82000-0x1c83fff,0x1c84000-0x1c85fff,0x1c86000-0x1c87fff irq 23 on simplebus0 gic0: pn 0x2, arch 0x2, rev 0x1, implementer 0x43b irqs 224 random: harvesting attach, 8 bytes (4 bits) from gic0 gpio0: mem 0x1c20800-0x1c20bff irq 12,13,14 on simplebus0 gpiobus0: on gpio0 random: harvesting attach, 8 bytes (4 bits) from gpiobus0 Processing 1 pin-config node(s) in pinctrl-0 for mmc@1c0f000 Processing 1 pin-config node(s) in pinctrl-0 for serial@1c28000 Processing 1 pin-config node(s) in pinctrl-0 for i2c@1c2b000 Processing 1 pin-config node(s) in pinctrl-0 for ethernet@01c30000 Processing 1 pin-config node(s) in pinctrl-0 for mmc@1c0f000 Processing 1 pin-config node(s) in pinctrl-0 for serial@1c28000 Processing 1 pin-config node(s) in pinctrl-0 for i2c@1c2b000 Processing 1 pin-config node(s) in pinctrl-0 for ethernet@01c30000 random: harvesting attach, 8 bytes (4 bits) from gpio0 gpio1: mem 0x1f02c00-0x1f02fff irq 26 on simplebus0 gpiobus1: on gpio1 random: harvesting attach, 8 bytes (4 bits) from gpiobus1 Processing 1 pin-config node(s) in pinctrl-0 for mmc@1c0f000 Processing 1 pin-config node(s) in pinctrl-0 for serial@1c28000 Processing 1 pin-config node(s) in pinctrl-0 for i2c@1c2b000 Processing 1 pin-config node(s) in pinctrl-0 for ethernet@01c30000 Processing 1 pin-config node(s) in pinctrl-0 for mmc@1c0f000 Processing 1 pin-config node(s) in pinctrl-0 for serial@1c28000 Processing 1 pin-config node(s) in pinctrl-0 for i2c@1c2b000 Processing 1 pin-config node(s) in pinctrl-0 for ethernet@01c30000 random: harvesting attach, 8 bytes (4 bits) from gpio1 generic_timer0: irq 0,1,2,3 on ofwbus0 Timecounter "ARM MPCore Timecounter" frequency 24000000 Hz quality 1000 Event timer "ARM MPCore Eventtimer" frequency 24000000 Hz quality 1000 random: harvesting attach, 8 bytes (4 bits) from generic_timer0 rtc0: mem 0x1f00000-0x1f00053 irq 24,25 on simplebus0 rtc0: Using external oscillator rtc0: registered as a time-of-day clock, resolution 1.000000s random: harvesting attach, 8 bytes (4 bits) from rtc0 cpulist0: on ofwbus0 cpu0: on cpulist0 cpu0: missing 'clock-frequency' property arm64_cpu0: register <0> random: harvesting attach, 8 bytes (4 bits) from arm64_cpu0 random: harvesting attach, 8 bytes (4 bits) from cpu0 cpu1: on cpulist0 cpu1: missing 'clock-frequency' property arm64_cpu1: register <1> random: harvesting attach, 8 bytes (4 bits) from arm64_cpu1 random: harvesting attach, 8 bytes (4 bits) from cpu1 cpu2: on cpulist0 cpu2: missing 'clock-frequency' property arm64_cpu2: register <2> random: harvesting attach, 8 bytes (4 bits) from arm64_cpu2 random: harvesting attach, 8 bytes (4 bits) from cpu2 cpu3: on cpulist0 cpu3: missing 'clock-frequency' property arm64_cpu3: register <3> random: harvesting attach, 8 bytes (4 bits) from arm64_cpu3 random: harvesting attach, 8 bytes (4 bits) from cpu3 random: harvesting attach, 8 bytes (4 bits) from cpulist0 aw_mmc0: mem 0x1c0f000-0x1c0ffff irq 4 on simplebus0 mmc0: on aw_mmc0 random: harvesting attach, 8 bytes (4 bits) from mmc0 random: harvesting attach, 8 bytes (4 bits) from aw_mmc0 simplebus0: mem 0x1c10000-0x1c10fff irq 5 disabled compat allwinner,sun50i-a64-mmc (no driver attached) simplebus0: mem 0x1c11000-0x1c11fff irq 6 disabled compat allwinner,sun50i-a64-emmc (no driver attached) simplebus0: mem 0x1c19000-0x1c193ff irq 7 compat allwinner,sun8i-a33-musb (no driver attached) simplebus0: mem 0x1c1a000-0x1c1a0ff irq 8 disabled compat allwinner,sun50i-a64-ehci (no driver attached) simplebus0: mem 0x1c1a400-0x1c1a4ff irq 9 disabled compat allwinner,sun50i-a64-ohci (no driver attached) ehci0: mem 0x1c1b000-0x1c1b0ff irq 10 on simplebus0 usbus0: EHCI version 1.0 usbus0 on ehci0 ehci0: usbpf: Attached random: harvesting attach, 8 bytes (4 bits) from usbus0 random: harvesting attach, 8 bytes (4 bits) from ehci0 ohci0: mem 0x1c1b400-0x1c1b4ff irq 11 on simplebus0 usbus1 on ohci0 ohci0: usbpf: Attached random: harvesting attach, 8 bytes (4 bits) from usbus1 random: harvesting attach, 8 bytes (4 bits) from ohci0 gpioc0: on gpio0 random: harvesting attach, 8 bytes (4 bits) from gpioc0 uart0: <16750 or compatible> mem 0x1c28000-0x1c283ff irq 15 on simplebus0 uart0: console (115384,n,8,1) uart0: fast interrupt uart0: PPS capture mode: DCD random: harvesting attach, 8 bytes (4 bits) from uart0 simplebus0: mem 0x1c28400-0x1c287ff irq 16 disabled compat snps,dw-apb-uart (no driver attached) simplebus0: mem 0x1c28800-0x1c28bff irq 17 disabled compat snps,dw-apb-uart (no driver attached) simplebus0: mem 0x1c28c00-0x1c28fff irq 18 disabled compat snps,dw-apb-uart (no driver attached) simplebus0: mem 0x1c29000-0x1c293ff irq 19 disabled compat snps,dw-apb-uart (no driver attached) simplebus0: mem 0x1c2ac00-0x1c2afff irq 20 disabled compat allwinner,sun6i-a31-i2c (no driver attached) simplebus0: mem 0x1c2b000-0x1c2b3ff irq 21 compat allwinner,sun6i-a31-i2c (no driver attached) simplebus0: mem 0x1c2b400-0x1c2b7ff irq 22 disabled compat allwinner,sun6i-a31-i2c (no driver attached) gpioc1: on gpio1 random: harvesting attach, 8 bytes (4 bits) from gpioc1 simplebus0: mem 0x1c30000-0x1c31fff,0x1c00030-0x1c00033 irq 27 compat allwinner,sun50i-a64-emac (no driver attached) cryptosoft0: crypto: assign cryptosoft0 driver id 0, flags 0x6000000 crypto: cryptosoft0 registers alg 1 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 2 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 3 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 4 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 5 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 16 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 6 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 7 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 18 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 19 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 20 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 8 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 15 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 9 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 10 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 13 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 14 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 11 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 22 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 23 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 25 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 24 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 26 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 27 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 28 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 21 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 17 flags 0 maxoplen 0 random: harvesting attach, 8 bytes (4 bits) from cryptosoft0 Device configuration finished. procfs registered Timecounters tick every 1.000 msec vlan: initialized, using hash tables with chaining lo0: bpf attached IPsec: Initialized Security Association Processing. arc4random: read 32 bytes from preloaded cache arc4random: read 32 bytes from preloaded cache arc4random: read 32 bytes from preloaded cache tcp_init: net.inet.tcp.tcbhashsize auto tuned to 16384 usbus0: 480Mbps High Speed USB v2.0 usbus1: 12Mbps Full Speed USB v1.0 pflog0: bpf attached mmc0: Probing bus ugen1.1: at usbus1 uhub0: on usbus1 ugen0.1: at usbus0 uhub1: on usbus0 mmc0: SD 2.0 interface conditions: OK mmc0: SD probe: OK (OCR: 0x40ff8000) mmc0: Current OCR: 0x00ff8000 mmc0: Probing cards mmc0: New card detected (CID 9c534f5553443030101ea1b29701066d) mmc0: New card detected (CSD 400e00325b59000075cf7f800a400029) mmc0: Card at relative address 0x1388 added: mmc0: card: SDHC USD00 1.0 SN 1EA1B297 MFG 06/2016 by 156 SO mmc0: quirks: 0 mmc0: bus: 4bit, 50MHz (high speed timing) mmc0: memory: 30883840 blocks, erase sector 8192 blocks mmc0: setting transfer rate to 50.000MHz (high speed timing) mmcsd0: 16GB at mmc0 50.0MHz/4bit/65535-block random: harvesting attach, 8 bytes (4 bits) from mmcsd0 Release APs GEOM: new disk mmcsd0 CPU 0: ARM Cortex-A53 r0p4 affinity:GEOM_PART: partition 1 on (mmcsd0, MBR) is not aligned on 4194304 bytes 0 GEOM_PART: partition 2 on (mmcsd0, MBR) is not aligned on 4194304 bytes Instruction Set Attributes 0 = Instruction Set Attributes 1 = <> Processor Features 0 = Processor Features 1 = <0> Memory Model Features 0 = <4k Granule,64k Granule,MixedEndian,S/NS Mem,16bit ASID,1TB PA> Memory Model Features 1 = <> Memory Model Features 2 = <32b CCIDX,48b VA> Debug Features 0 = <2 CTX Breakpoints,4 Watchpoints,6 Breakpoints,PMUv3,Debug v8> Debug Features 1 = <0> GEOM_PART: partition 1 on (diskid/DISK-1EA1B297, MBR) is not aligned on 4194304 bytes Auxiliary Features 0 = <0> GEOM_PART: partition 2 on (diskid/DISK-1EA1B297, MBR) is not aligned on 4194304 bytes Auxiliary Features 1 = <0> CPU 1: ARM Cortex-A53 r0p4 affinity: 1 CPU 2: ARM Cortex-A53 r0p4 affinity: 2 CPU 3: ARM Cortex-A53 r0p4 affinity: 3 Trying to mount root from ufs:/dev/mmcsd0s2 [rw,noatime]... uhub0: 1 port with 1 removable, self powered random: harvesting attach, 8 bytes (4 bits) from uhub0 rtc0: providing initial system time start_init: trying /sbin/init Enter full pathname of shell or RETURN for /bin/sh: uhub1: 1 port with 1 removable, self powered random: harvesting attach, 8 bytes (4 bits) from uhub1 ugen0.2: at usbus0 uhub2 on uhub1 uhub2: on usbus0 uhub2: 4 ports with 4 removable, self powered random: harvesting attach, 8 bytes (4 bits) from uhub2 ugen0.3: at usbus0 uhub3 on uhub2 uhub3: on usbus0 uhub3: 4 ports with 4 removable, self powered random: harvesting attach, 8 bytes (4 bits) from uhub3 ugen0.4: at usbus0 umass0 on uhub2 umass0: on usbus0 umass0:0:0: Attached to scbus0 random: harvesting attach, 8 bytes (4 bits) from umass0 GEOM: new disk da0 pass0 at umass-sim0 bus 0 scbus0 target 0 lun 0 pass0: Fixed Direct Access SPC-4 SCSI device pass0: Serial Number 575841314535314B54313238 pass0: 40.000MB/s transfers da0 at umass-sim0 bus 0 scbus0 target 0 lun 0 da0: Fixed Direct Access SPC-4 SCSI device da0: Serial Number 575841314535314B54313238 da0: 40.000MB/s transfers da0: 953867MB (1953519616 512 byte sectors) da0: quirks=0x2 da0: Delete methods: # date 201801081711 Mon Jan 8 17:11:00 CET 2018 # exit > >> Henri > > Thanks, > > Kyle Evans > From owner-freebsd-arm@freebsd.org Mon Jan 8 16:07:26 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0908EE74898 for ; Mon, 8 Jan 2018 16:07:26 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.blih.net", Issuer "mail.blih.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4B276823E8; Mon, 8 Jan 2018 16:07:24 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) by mail.blih.net (OpenSMTPD) with ESMTP id 83c2d931; Mon, 8 Jan 2018 17:07:21 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; s=mail; bh=zFh6pTiJ4fRgQRlAGN9J8xRpNF8=; b=tW7P4Qyu4UdJemGI0jci6yMyNfKz EZJoLFS8lRAOjwr5wZC5gFH0g1mIiN/oe8JbuXciEwp/lDJIXN3yu4n9t7W40GIS jowF4dBX/oGbjgKhzvpMzx7GPZMns9dY1VRy1bWpsUe9sPK38P1yBshiZUncwk1J jrGPv8BZ6myE1sI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; q=dns; s= mail; b=psD/vLMjxO3MNgI3GwvTmQ7Lm1m8BJb60QI7n7gOqTW75aHs6YFyAkDI mAlt5KdDI86Ct5dStHlKVKJFGmDEs/OkN7BhwCDz7RVYDFaRtfHG4GiRKucoCIRu Q0p0iORBrCWas1ERslL/yqr6Xh5be5Xblm7xa6QQcli1yFyEtLs= Received: from arcadia (evadot.gandi.net [217.70.181.36]) by mail.blih.net (OpenSMTPD) with ESMTPSA id 7b59750c TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Mon, 8 Jan 2018 17:07:17 +0100 (CET) Date: Mon, 8 Jan 2018 17:07:17 +0100 From: Emmanuel Vadot To: Henri Hennebert Cc: Kyle Evans , "freebsd-arm@freebsd.org" Subject: Re: Pine64+ - 12.0-CURRENT #0 r327665 don't detect awg0 Message-Id: <20180108170717.0b4c03a15a518e834bc9c61b@bidouilliste.com> In-Reply-To: <44f39a02-a989-c077-d163-1406e64a53de@restart.be> References: <98a73723-005d-1178-b8b7-beeb65ba5ad5@restart.be> <44f39a02-a989-c077-d163-1406e64a53de@restart.be> X-Mailer: Sylpheed 3.6.0 (GTK+ 2.24.31; amd64-portbld-freebsd12.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2018 16:07:26 -0000 On Mon, 8 Jan 2018 17:03:28 +0100 Henri Hennebert wrote: > On 01/08/2018 16:44, Kyle Evans wrote: > > On Mon, Jan 8, 2018 at 9:40 AM, Henri Hennebert wrote: > >> Hello, > >> > >> When I boot 12.0-CURRENT #0 r327665 in verbose mode with > >> U-Boot 2017.09 (Dec 12 2017 - 21:15:33 +0000) on Pine64+ > >> I get: > >> > >> simplebus0: mem 0x1c30000-0x1c31fff,0x1c00030-0x1c00033 > >> irq 27 compat allwinner,sun50i-a64-emac (no driver attached) > > > > Hi, > > > > Can you post the rest of this dmesg, so we can see fully what's going > > on with awg/syscon interaction? > OK boot -v -s > Booting... > Using DTB provided by EFI at 0x48000000. > KDB: debugger backends: ddb > KDB: current backend: ddb > Found 4 CPUs in the device tree > Copyright (c) 1992-2018 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD is a registered trademark of The FreeBSD Foundation. > FreeBSD 12.0-CURRENT #0 r327665M: Mon Jan 8 13:55:28 CET 2018 > root@nakiska.restart.bel:/usr/obj/usr/src/arm64.aarch64/sys/NORQUAY > arm64 You most likely forgot to add ext_resources into your kernel config file. You might want to include GENERIC and remove device/options rather than rolling your own config (or track each addition made to GENERIC). Cheers, -- Emmanuel Vadot From owner-freebsd-arm@freebsd.org Mon Jan 8 16:24:29 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A55D0E75A5E for ; Mon, 8 Jan 2018 16:24:29 +0000 (UTC) (envelope-from byond.lenox@gmail.com) Received: from mail-io0-f174.google.com (mail-io0-f174.google.com [209.85.223.174]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7C18D83669; Mon, 8 Jan 2018 16:24:29 +0000 (UTC) (envelope-from byond.lenox@gmail.com) Received: by mail-io0-f174.google.com with SMTP id n14so14783983iob.4; Mon, 08 Jan 2018 08:24:29 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Ony0aQ3yVF2gd53Jfc5nl5V9r3jgEoGoUDaZmLVAGz0=; b=FXHLe0gFhn9ujJXDRZAvyGnvJAIoPux/z0E67pKPVHmUpOymqEmgVDbf8qJkdIbUXa Xhp0oye/3FmGxtoRGCFvojul7YkBU6iLDZQbbSXDAvS+pQiT+u2t3q4/NVQDHJP9qwhE TPnns+We/EIkZiwR2uNeelaOaGCNOPyjd02MzzJyNOwtD4iLviaEHkeXW+J/RZwb7jo7 oOiAm3VijVkxRX3TWm8T0tuOHsltUtj2uToisMphpZkI9UGcO5BhfyezcPT31J8fZbaG kKhlZ7j6Xh3UYlqeD8LuZz6Viwp42HxYPd9zB/fEGZSTHHKlziQ4HEkswFkcNbl6TCWz PuaQ== X-Gm-Message-State: AKwxytfsPyIcf/A0oGff+u96jLTN/7hW+nTKLcK0aeI6ANYIZ62Rm3JD 58wlfQi14kNKMbYLQssmJTtcuOZn X-Google-Smtp-Source: ACJfBosSjVoZZsfwZdHLajHmS9cLsrXCRLJX3F3WzF8+Q5PQpxXKHXWv2/yKqZcDuEnWcJpEptFllA== X-Received: by 10.107.18.147 with SMTP id 19mr12401380ios.197.1515428340800; Mon, 08 Jan 2018 08:19:00 -0800 (PST) Received: from mail-io0-f180.google.com (mail-io0-f180.google.com. [209.85.223.180]) by smtp.gmail.com with ESMTPSA id e139sm7255343ite.8.2018.01.08.08.19.00 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 08 Jan 2018 08:19:00 -0800 (PST) Received: by mail-io0-f180.google.com with SMTP id v30so14760684iov.7; Mon, 08 Jan 2018 08:19:00 -0800 (PST) X-Received: by 10.107.151.131 with SMTP id z125mr8178792iod.224.1515428340077; Mon, 08 Jan 2018 08:19:00 -0800 (PST) MIME-Version: 1.0 Received: by 10.107.149.147 with HTTP; Mon, 8 Jan 2018 08:18:39 -0800 (PST) In-Reply-To: <20180108170717.0b4c03a15a518e834bc9c61b@bidouilliste.com> References: <98a73723-005d-1178-b8b7-beeb65ba5ad5@restart.be> <44f39a02-a989-c077-d163-1406e64a53de@restart.be> <20180108170717.0b4c03a15a518e834bc9c61b@bidouilliste.com> From: Kyle Evans Date: Mon, 8 Jan 2018 10:18:39 -0600 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Pine64+ - 12.0-CURRENT #0 r327665 don't detect awg0 To: Emmanuel Vadot , Henri Hennebert Cc: Kyle Evans , "freebsd-arm@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2018 16:24:29 -0000 On Mon, Jan 8, 2018 at 10:07 AM, Emmanuel Vadot wrote: > On Mon, 8 Jan 2018 17:03:28 +0100 > Henri Hennebert wrote: > >> On 01/08/2018 16:44, Kyle Evans wrote: >> > On Mon, Jan 8, 2018 at 9:40 AM, Henri Hennebert wrote: >> >> Hello, >> >> >> >> When I boot 12.0-CURRENT #0 r327665 in verbose mode with >> >> U-Boot 2017.09 (Dec 12 2017 - 21:15:33 +0000) on Pine64+ >> >> I get: >> >> >> >> simplebus0: mem 0x1c30000-0x1c31fff,0x1c00030-0x1c00033 >> >> irq 27 compat allwinner,sun50i-a64-emac (no driver attached) >> > >> > Hi, >> > >> > Can you post the rest of this dmesg, so we can see fully what's going >> > on with awg/syscon interaction? >> OK boot -v -s >> Booting... >> Using DTB provided by EFI at 0x48000000. >> KDB: debugger backends: ddb >> KDB: current backend: ddb >> Found 4 CPUs in the device tree >> Copyright (c) 1992-2018 The FreeBSD Project. >> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 >> The Regents of the University of California. All rights reserved. >> FreeBSD is a registered trademark of The FreeBSD Foundation. >> FreeBSD 12.0-CURRENT #0 r327665M: Mon Jan 8 13:55:28 CET 2018 >> root@nakiska.restart.bel:/usr/obj/usr/src/arm64.aarch64/sys/NORQUAY >> arm64 > > You most likely forgot to add ext_resources into your kernel config > file. > You might want to include GENERIC and remove device/options rather > than rolling your own config (or track each addition made to GENERIC). > Indeed- your config would've been broken by/without r327563, https://svnweb.freebsd.org/base/head/sys/arm64/conf/GENERIC?r1=326501&r2=327563 That should bring back awg. From owner-freebsd-arm@freebsd.org Mon Jan 8 16:24:44 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9B32AE75AA1 for ; Mon, 8 Jan 2018 16:24:44 +0000 (UTC) (envelope-from hlh@restart.be) Received: from tignes.restart.be (tignes.restart.be [IPv6:2001:41d0:8:bdbe:0:1::]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "tignes.restart.be", Issuer "CA master" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 5F4E8836C5; Mon, 8 Jan 2018 16:24:44 +0000 (UTC) (envelope-from hlh@restart.be) X-Comment: SPF check N/A for local connections - client-ip=192.168.25.127; helo=restart.be; envelope-from=hlh@restart.be; receiver=kevans@freebsd.org DKIM-Filter: OpenDKIM Filter v2.10.3 tignes.restart.be 3zFgb716sPzr5Y Received: from restart.be (norquay.tunnel.bel [192.168.25.127]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.restart.be", Issuer "CA master" (verified OK)) by tignes.restart.be (Postfix) with ESMTPS id 3zFgb716sPzr5Y; Mon, 8 Jan 2018 17:24:34 +0100 (CET) Received: from chamonix.restart.bel (chamonix.restart.bel [192.168.24.9]) (authenticated bits=0) by restart.be (8.15.2/8.15.2) with ESMTPSA id w08GOXo9047240 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 8 Jan 2018 17:24:34 +0100 (CET) (envelope-from hlh@restart.be) Subject: Re: Pine64+ - 12.0-CURRENT #0 r327665 don't detect awg0 To: Kyle Evans , Emmanuel Vadot Cc: "freebsd-arm@freebsd.org" References: <98a73723-005d-1178-b8b7-beeb65ba5ad5@restart.be> <44f39a02-a989-c077-d163-1406e64a53de@restart.be> <20180108170717.0b4c03a15a518e834bc9c61b@bidouilliste.com> From: Henri Hennebert Message-ID: Date: Mon, 8 Jan 2018 17:24:33 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2018 16:24:44 -0000 On 01/08/2018 17:18, Kyle Evans wrote: > On Mon, Jan 8, 2018 at 10:07 AM, Emmanuel Vadot wrote: >> On Mon, 8 Jan 2018 17:03:28 +0100 >> Henri Hennebert wrote: >> >>> On 01/08/2018 16:44, Kyle Evans wrote: >>>> On Mon, Jan 8, 2018 at 9:40 AM, Henri Hennebert wrote: >>>>> Hello, >>>>> >>>>> When I boot 12.0-CURRENT #0 r327665 in verbose mode with >>>>> U-Boot 2017.09 (Dec 12 2017 - 21:15:33 +0000) on Pine64+ >>>>> I get: >>>>> >>>>> simplebus0: mem 0x1c30000-0x1c31fff,0x1c00030-0x1c00033 >>>>> irq 27 compat allwinner,sun50i-a64-emac (no driver attached) >>>> >>>> Hi, >>>> >>>> Can you post the rest of this dmesg, so we can see fully what's going >>>> on with awg/syscon interaction? >>> OK boot -v -s >>> Booting... >>> Using DTB provided by EFI at 0x48000000. >>> KDB: debugger backends: ddb >>> KDB: current backend: ddb >>> Found 4 CPUs in the device tree >>> Copyright (c) 1992-2018 The FreeBSD Project. >>> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 >>> The Regents of the University of California. All rights reserved. >>> FreeBSD is a registered trademark of The FreeBSD Foundation. >>> FreeBSD 12.0-CURRENT #0 r327665M: Mon Jan 8 13:55:28 CET 2018 >>> root@nakiska.restart.bel:/usr/obj/usr/src/arm64.aarch64/sys/NORQUAY >>> arm64 >> >> You most likely forgot to add ext_resources into your kernel config >> file. >> You might want to include GENERIC and remove device/options rather >> than rolling your own config (or track each addition made to GENERIC). >> > > Indeed- your config would've been broken by/without r327563, > https://svnweb.freebsd.org/base/head/sys/arm64/conf/GENERIC?r1=326501&r2=327563 > > That should bring back awg. > Sorry for the noise and thank you for your time! Henri From owner-freebsd-arm@freebsd.org Mon Jan 8 16:28:29 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ECB98E75E30 for ; Mon, 8 Jan 2018 16:28:29 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.blih.net", Issuer "mail.blih.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 2E0B183A29; Mon, 8 Jan 2018 16:28:27 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) by mail.blih.net (OpenSMTPD) with ESMTP id 1f78e3c1; Mon, 8 Jan 2018 17:28:25 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; s=mail; bh=4RlHlITC4iw+EJWWG834j3HHdyo=; b=MIEu3n1jMWIyrI+p0SuBdZTH4o8l Nce9CPbGa6NVllTSJH2/E0lEVKMy1VlsZnaWyJmT4eaGg965+/XRKgWrHxye9L+k blOHxtMVAEy2e+sf8gTOsvF4r2Ec+aS9Itz9RzBcWFQisMdCRrMjC2J4xVkO7uOH P1IKmZhavYSSlcs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; q=dns; s= mail; b=qYVGvXjU4N7aEqqc9U+YRVVCRKUQ7aD09XHyDTU01/ADPr78x/ERQHAm hHfz7mHcg2xPbQl/mYBjR00j0KzB6yx092Rgs98d4h28P2ESOpVR8dXOadDOxiqI XpXtWUsiWgUc7Qt467vg4b1b6en4WVT1lP0cxuNXFVcRmO8aoTs= Received: from arcadia (evadot.gandi.net [217.70.181.36]) by mail.blih.net (OpenSMTPD) with ESMTPSA id a2eef1c6 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Mon, 8 Jan 2018 17:28:25 +0100 (CET) Date: Mon, 8 Jan 2018 17:28:24 +0100 From: Emmanuel Vadot To: Henri Hennebert Cc: Kyle Evans , "freebsd-arm@freebsd.org" Subject: Re: Pine64+ - 12.0-CURRENT #0 r327665 don't detect awg0 Message-Id: <20180108172824.9ebc897e11dd72dc8c692ce3@bidouilliste.com> In-Reply-To: References: <98a73723-005d-1178-b8b7-beeb65ba5ad5@restart.be> <44f39a02-a989-c077-d163-1406e64a53de@restart.be> <20180108170717.0b4c03a15a518e834bc9c61b@bidouilliste.com> X-Mailer: Sylpheed 3.6.0 (GTK+ 2.24.31; amd64-portbld-freebsd12.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2018 16:28:30 -0000 On Mon, 8 Jan 2018 17:24:33 +0100 Henri Hennebert wrote: > On 01/08/2018 17:18, Kyle Evans wrote: > > On Mon, Jan 8, 2018 at 10:07 AM, Emmanuel Vadot wrote: > >> On Mon, 8 Jan 2018 17:03:28 +0100 > >> Henri Hennebert wrote: > >> > >>> On 01/08/2018 16:44, Kyle Evans wrote: > >>>> On Mon, Jan 8, 2018 at 9:40 AM, Henri Hennebert wrote: > >>>>> Hello, > >>>>> > >>>>> When I boot 12.0-CURRENT #0 r327665 in verbose mode with > >>>>> U-Boot 2017.09 (Dec 12 2017 - 21:15:33 +0000) on Pine64+ > >>>>> I get: > >>>>> > >>>>> simplebus0: mem 0x1c30000-0x1c31fff,0x1c00030-0x1c00033 > >>>>> irq 27 compat allwinner,sun50i-a64-emac (no driver attached) > >>>> > >>>> Hi, > >>>> > >>>> Can you post the rest of this dmesg, so we can see fully what's going > >>>> on with awg/syscon interaction? > >>> OK boot -v -s > >>> Booting... > >>> Using DTB provided by EFI at 0x48000000. > >>> KDB: debugger backends: ddb > >>> KDB: current backend: ddb > >>> Found 4 CPUs in the device tree > >>> Copyright (c) 1992-2018 The FreeBSD Project. > >>> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > >>> The Regents of the University of California. All rights reserved. > >>> FreeBSD is a registered trademark of The FreeBSD Foundation. > >>> FreeBSD 12.0-CURRENT #0 r327665M: Mon Jan 8 13:55:28 CET 2018 > >>> root@nakiska.restart.bel:/usr/obj/usr/src/arm64.aarch64/sys/NORQUAY > >>> arm64 > >> > >> You most likely forgot to add ext_resources into your kernel config > >> file. > >> You might want to include GENERIC and remove device/options rather > >> than rolling your own config (or track each addition made to GENERIC). > >> > > > > Indeed- your config would've been broken by/without r327563, > > https://svnweb.freebsd.org/base/head/sys/arm64/conf/GENERIC?r1=326501&r2=327563 > > > > That should bring back awg. > > > Sorry for the noise and thank you for your time! > > Henri No problem, just remember to test GENERIC when you have problem, I and other FreeBSD dev always make sure that GENERIC works before commiting. -- Emmanuel Vadot From owner-freebsd-arm@freebsd.org Mon Jan 8 16:32:55 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A6CADE76367 for ; Mon, 8 Jan 2018 16:32:55 +0000 (UTC) (envelope-from mail@sezi.eu) Received: from mail.fizon.de (mail.fizon.de [195.149.99.106]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 485F81F1 for ; Mon, 8 Jan 2018 16:32:54 +0000 (UTC) (envelope-from mail@sezi.eu) Received: from sz-mbp.level0.hanse.fizon.de ([10.210.74.76]) (authenticated bits=0) by mail.fizon.de (8.14.5/8.14.5) with ESMTP id w08GFSet068644 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 8 Jan 2018 17:15:28 +0100 (CET) (envelope-from mail@sezi.eu) From: Sebastian Zietz Content-Type: multipart/signed; boundary="Apple-Mail=_7A4F5423-B09A-407A-BDBF-7F80FAA234BE"; protocol="application/pgp-signature"; micalg=pgp-sha512 Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: SPI support for Allwinner H3 Message-Id: <4FF6329A-636A-4180-9FE9-E89BDEA7F916@sezi.eu> Date: Mon, 8 Jan 2018 17:15:27 +0100 To: FreeBSD-arm@freebsd.org X-Mailer: Apple Mail (2.3445.5.20) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2018 16:32:55 -0000 --Apple-Mail=_7A4F5423-B09A-407A-BDBF-7F80FAA234BE Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi All, is there any chance to get the hardware SPI working on the NanoPI Neo? = The FreeBSD Wiki says SPI (Work in progress). Does somebody maybe has a branch to play around with? Thanks! -- Sebastian Zietz --Apple-Mail=_7A4F5423-B09A-407A-BDBF-7F80FAA234BE Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQEzBAEBCgAdFiEEhihu4ou5b7cwLNJkbvFysy0LB3cFAlpTmR8ACgkQbvFysy0L B3d36gf+K5aeKVLrpB9dNN2/jHKOgbRD3v9ypiFqIB/cZgrxe/aooZ+sSFlHLnTJ UBav8Vr0iefq/VvLogJY89Qj3gh3DSKvyUU7hMckDJueug0KoiCUuJsG9w45OMoA lH4+khP4QXanKDqPTSv6euriy4KHZH/gHWbIANmq4lgMn8gwCAb5onlGL/HJaVEL 8LqYd8Kf3Tf1Qmw18W4XabrLVv7qhh9c/8EdX662B8kZif8SXA3zDdGBYZwoeM+P nSXB4OaNlh4/gPQCYUsswi6jQcbJz8K+OPimD9lQugSVUirFfW1XAgIjbgGahoF9 FQaTyTaPBE/LTX5ZNm/wdizrtqorPg== =MO+Y -----END PGP SIGNATURE----- --Apple-Mail=_7A4F5423-B09A-407A-BDBF-7F80FAA234BE-- From owner-freebsd-arm@freebsd.org Mon Jan 8 23:10:07 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 216F2E6A1BD for ; Mon, 8 Jan 2018 23:10:07 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [69.239.235.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id DE35F7A6CD for ; Mon, 8 Jan 2018 23:10:06 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id w08N9w49033386 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 8 Jan 2018 15:09:59 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w08N9wLt033385; Mon, 8 Jan 2018 15:09:58 -0800 (PST) (envelope-from fbsd) Date: Mon, 8 Jan 2018 15:09:57 -0800 From: bob prohaska To: Mark Millard Cc: freebsd-arm@freebsd.org Subject: Re: RPI2 boot hangs with red light on Message-ID: <20180108230957.GA33370@www.zefox.net> References: <20180102222730.GB10596@www.zefox.net> <3EE68320-8359-495D-AFCE-098A2220C6AE@dsl-only.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3EE68320-8359-495D-AFCE-098A2220C6AE@dsl-only.net> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2018 23:10:07 -0000 On Tue, Jan 02, 2018 at 03:50:40PM -0800, Mark Millard wrote: > > I use a file that includes GENERIC. > As far as I know at this point RPI2 is > no longer maintained. Aye, there's the rub. GENERIC works. Bulky, at over 10MB, however. RPI2 was around 8MB. Thanks for cluing me in! bob prohaska From owner-freebsd-arm@freebsd.org Tue Jan 9 00:38:01 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 43627E6F498 for ; Tue, 9 Jan 2018 00:38:01 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-112.reflexion.net [208.70.210.112]) (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 EBADE7DA55 for ; Tue, 9 Jan 2018 00:38:00 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 24695 invoked from network); 9 Jan 2018 00:37:53 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 9 Jan 2018 00:37:53 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v8.40.4) with SMTP; Mon, 08 Jan 2018 19:37:53 -0500 (EST) Received: (qmail 9863 invoked from network); 9 Jan 2018 00:37:53 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 9 Jan 2018 00:37:53 -0000 Received: from [192.168.1.25] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 6702BEC950D; Mon, 8 Jan 2018 16:37:52 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: RPI2 boot hangs with red light on From: Mark Millard In-Reply-To: <20180108230957.GA33370@www.zefox.net> Date: Mon, 8 Jan 2018 16:37:51 -0800 Cc: freebsd-arm@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <4575C772-CEC0-4F64-8F04-F820568B51AF@dsl-only.net> References: <20180102222730.GB10596@www.zefox.net> <3EE68320-8359-495D-AFCE-098A2220C6AE@dsl-only.net> <20180108230957.GA33370@www.zefox.net> To: bob prohaska X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Jan 2018 00:38:01 -0000 On 2018-Jan-8, at 3:09 PM, bob prohaska wrote: > On Tue, Jan 02, 2018 at 03:50:40PM -0800, Mark Millard wrote: >>=20 >> I use a file that includes GENERIC. >> As far as I know at this point RPI2 is >> no longer maintained. >=20 > Aye, there's the rub. GENERIC works. > Bulky, at over 10MB, however. RPI2 > was around 8MB. While after the include I primarily adjust the debug/non-debug types of status of things, as I understand other types of lines can override what is included vs. excluded from the kernel. So if one knows what one is doing about what is optional vs. not for their purposes, smaller kernels are possible while still being based on GENERIC. (And, so, being somewhat auto-updating as GENERIC progresses.) Using powerpc64 as an example, the below adds filemon and geom_label to the kernel (because I have a context for which dynamic loading of modules crashes the kernel): # more /usr/src/sys/powerpc/conf/GENERIC64vtsc-NODBG=20 # # GENERIC -- Custom configuration for the powerpc/powerpc64 # include "GENERIC64" ident GENERIC64vtsc-NODBG makeoptions DEBUG=3D-g # Build kernel with gdb(1) = debug symbols nooptions PS3 # Sony Playstation 3 = HACK!!! to allow sc options KDB # Enable kernel debugger support options ALT_BREAK_TO_DEBUGGER options BREAK_TO_DEBUGGER # For minimum debugger support (stable branch) use: options KDB_TRACE # Print a stack trace for a = panic options DDB # Enable the kernel debugger options GDB # HACK!!! ... # Extra stuff: #options VERBOSE_SYSINIT # Enable verbose sysinit = messages #options BOOTVERBOSE=3D1 #options BOOTHOWTO=3DRB_VERBOSE #options KTR #options KTR_MASK=3DKTR_TRAP ##options KTR_CPUMASK=3D0xF #options KTR_VERBOSE # HACK!!! to allow sc for 2560x1440 display on Radeon X1950 that vt = historically mishandled during booting device sc #device kbdmux # HACK: already listed by vt options SC_OFWFB # OFW frame buffer options SC_DFLT_FONT # compile font in makeoptions SC_DFLT_FONT=3Dcp437 # Disable any extra checking for. . . nooptions DEADLKRES # Enable the deadlock resolver nooptions INVARIANTS # Enable calls of extra sanity = checking nooptions INVARIANT_SUPPORT # Extra sanity checks of = internal structures, required by INVARIANTS nooptions WITNESS # Enable checks to detect = deadlocks and cycles nooptions WITNESS_SKIPSPIN # Don't run witness on spinlocks = for speed nooptions DIAGNOSTIC nooptions MALLOC_DEBUG_MAXZONES # Separate malloc(9) zones device filemon device geom_label It also has sc in the kernel, in addition to vt, but I had to disable PS3 support to allow such back when I did this. =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-arm@freebsd.org Wed Jan 10 02:17:21 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 60412E5C36E for ; Wed, 10 Jan 2018 02:17:21 +0000 (UTC) (envelope-from tom@ycombinator.com) Received: from mail-yb0-x22f.google.com (mail-yb0-x22f.google.com [IPv6:2607:f8b0:4002:c09::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 345237CB4E for ; Wed, 10 Jan 2018 02:17:21 +0000 (UTC) (envelope-from tom@ycombinator.com) Received: by mail-yb0-x22f.google.com with SMTP id j7so6814565ybl.3 for ; Tue, 09 Jan 2018 18:17:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ycombinator.com; s=google; h=mime-version:from:date:message-id:subject:to; bh=P0eRJY9Iz/TidSUXdLdCEvUGfSrzehnl8SQReXxuwfA=; b=ZXdXMdTUEe0CTl0DPYnfxNTSK1wvj6HC8q5PaSKeI1JU5z3ftTB3sy5sse8A7UPZew cwZSn39z6Y2qebisCohklxAO674R5LH3DGrpj/h8pex6Fl1Wn6h8nBi0qErbx1yRHAMO 5jiAIIiY8RfFymNJmrILXeMxUO4jyv6CrF8Mc= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=P0eRJY9Iz/TidSUXdLdCEvUGfSrzehnl8SQReXxuwfA=; b=Pwf26BQpwiM30XTCBKlaLCDsJtsMABuHMTUdixicRe60D+oAn4Hwhbz6tvd4D56MT7 YZZZ2N18FXo8ehs0sA8VdaNZ5kna4tiawdFLHwFcELT9iduXyeS0DeTwOIqt13QY5wEG Peaw6KODFQqe3JSOm+zZSvEN0pSh3Zp7wkSAOci40L+QzgNtClsUina5LixyMu9y0i8S cpspBVOSqM1K7bqW6orwos0lA0dsH+M9SZQnsL0jxm3l4e/sfY7dLAidqGv5gzvGT7cq IbEjnVxNKB26tcneFU9MKSsjUapWPCX+YvD5xbrER5oFOGhKboZ4W1UC31bMVaXwLEtk CuXA== X-Gm-Message-State: AKGB3mL+gPpBiv0wPKMxhtWS0AmUiD8dhx/irE/7VTiaZBZ784u2i3Vt HkWRhgJMwRDNhMbAsV74fxX5Xy65x3CQGroWT47yWO+m X-Google-Smtp-Source: ACJfBot9qwCdhauy1lXobW4NAhbgyAh7Az1nCL3TXpwNAnn0ku9ZrR9RxiT2FHJOJLe8uTVSXEDw4U+MDOUCBHkEHZM= X-Received: by 10.37.216.144 with SMTP id p138mr15662515ybg.61.1515550640076; Tue, 09 Jan 2018 18:17:20 -0800 (PST) MIME-Version: 1.0 Received: by 10.37.58.197 with HTTP; Tue, 9 Jan 2018 18:17:19 -0800 (PST) From: Tom Sparks Date: Tue, 9 Jan 2018 18:17:19 -0800 Message-ID: Subject: Booting on RPI2 with uSD and USB To: freebsd-arm Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jan 2018 02:17:21 -0000 I use RPI's with FreeBSD around YC pretty extensively and I found a fun one today when I was trying out the ARMv7 builds for the RPI2. Typically I have a micro SD for the root disk, then a USB flash for data and swap. I'd never had a problem before with previous builds but it seems that there's a new probe-ordering issue somewhere. I put a new snapshot onto the micro sd, booted, and then the loader tried to boot off of the USB (which failed). It looks like disk0 is being defined as the USB instead of the microsd after the loader comes in. Anyone else seen this? -- Tom Sparks Systems Engineer From owner-freebsd-arm@freebsd.org Wed Jan 10 02:26:51 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0FA83E5CD41 for ; Wed, 10 Jan 2018 02:26:51 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1b.ore.mailhop.org (outbound1b.ore.mailhop.org [54.200.247.200]) (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 E6E9C7D1A6 for ; Wed, 10 Jan 2018 02:26:50 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: a6b77b4b-f5ad-11e7-8486-0934409070aa X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 73.78.92.27 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [73.78.92.27]) by outbound1.ore.mailhop.org (Halon) with ESMTPSA id a6b77b4b-f5ad-11e7-8486-0934409070aa; Wed, 10 Jan 2018 02:26:23 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id w0A2QgKp006319; Tue, 9 Jan 2018 19:26:42 -0700 (MST) (envelope-from ian@freebsd.org) Message-ID: <1515551202.44630.64.camel@freebsd.org> Subject: Re: Booting on RPI2 with uSD and USB From: Ian Lepore To: Tom Sparks , freebsd-arm Date: Tue, 09 Jan 2018 19:26:42 -0700 In-Reply-To: References: Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jan 2018 02:26:51 -0000 On Tue, 2018-01-09 at 18:17 -0800, Tom Sparks wrote: > I use RPI's with FreeBSD around YC pretty extensively and I found a fun one > today when I was trying out the ARMv7 builds for the RPI2. > > Typically I have a micro SD for the root disk, then a USB flash for data > and swap. I'd never had a problem before with previous builds but it seems > that there's a new probe-ordering issue somewhere. I put a new snapshot > onto the micro sd, booted, and then the loader tried to boot off of the USB > (which failed). It looks like disk0 is being defined as the USB instead of > the microsd after the loader comes in. > > Anyone else seen this? > You can make ubldr use the sdcard anyway; at the u-boot prompt do   setenv loaderdev mmc   saveenv -- Ian From owner-freebsd-arm@freebsd.org Fri Jan 12 21:29:33 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 35D6AE7D2A0 for ; Fri, 12 Jan 2018 21:29:33 +0000 (UTC) (envelope-from tuexen@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 1FFE880B95 for ; Fri, 12 Jan 2018 21:29:33 +0000 (UTC) (envelope-from tuexen@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 1BCF2E7D29F; Fri, 12 Jan 2018 21:29:33 +0000 (UTC) Delivered-To: arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1B76BE7D29E for ; Fri, 12 Jan 2018 21:29:33 +0000 (UTC) (envelope-from tuexen@freebsd.org) Received: from drew.franken.de (mail-n.franken.de [193.175.24.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.franken.de", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D8DB180B94 for ; Fri, 12 Jan 2018 21:29:32 +0000 (UTC) (envelope-from tuexen@freebsd.org) Received: from [IPv6:2003:cd:6bec:5d00:9149:3c3e:3ac9:9f76] (p200300CD6BEC5D0091493C3E3AC99F76.dip0.t-ipconnect.de [IPv6:2003:cd:6bec:5d00:9149:3c3e:3ac9:9f76]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTPSA id 4FE46721BBD2E for ; Fri, 12 Jan 2018 22:29:23 +0100 (CET) From: Michael Tuexen Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: tcpdump reporting strange packets on RPi3 Message-Id: Date: Fri, 12 Jan 2018 22:29:18 +0100 To: "freebsd-arm@freebsd.org" X-Mailer: Apple Mail (2.3445.5.20) X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=disabled version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail-n.franken.de X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jan 2018 21:29:33 -0000 Dear all, when running FreeBSD head on a RPi and using tcpdump on the ue0 = interface, I do see strange packets. Something like 01:59:44.000000 a5:a5:a5:a5:a5:a5 > a5:a5:a5:a5:a5:a5, ethertype Unknown = (0xa5a5), length 666370074:=20 0x0000: a5a5 a5a5 a5a5 a5a5 a5a5 a5a5 a5a5 a5a5 = ................ 0x0010: a5a5 a5a5 a5a5 a5a5 a5a5 a5a5 a5a5 a5a5 = ................ 0x0020: a5a5 a5a5 a5a5 a5a5 a5a5 a5a5 a5a5 a5a5 = ................ 0x0030: a5a5 a5a5 .... gets reported... Any ideas what went wrong? Best regards Michael= From owner-freebsd-arm@freebsd.org Sat Jan 13 00:54:33 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 922D3E62E23 for ; Sat, 13 Jan 2018 00:54:33 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [69.239.235.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 5170568EF8 for ; Sat, 13 Jan 2018 00:54:32 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id w0D0sRjA048733 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 12 Jan 2018 16:54:28 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w0D0sRCY048732; Fri, 12 Jan 2018 16:54:27 -0800 (PST) (envelope-from fbsd) Date: Fri, 12 Jan 2018 16:54:26 -0800 From: bob prohaska To: freebsd-arm@freebsd.org Subject: Builworld stalls on rpi2 Message-ID: <20180113005426.GA48702@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Jan 2018 00:54:33 -0000 Trying to self-host a build of r327859 using a GENERIC kernel at r327664, make seems to stall, with top showing last pid: 28822; load averages: 3.12, 3.95, 5.09 up 0+08:39:01 16:39:49 50 processes: 1 running, 47 sleeping, 2 waiting CPU: 0.0% user, 0.0% nice, 0.2% system, 0.9% interrupt, 98.9% idle Mem: 527M Active, 16M Inact, 98M Laundry, 148M Wired, 86M Buf, 3272K Free Swap: 2048M Total, 52M Used, 1996M Free, 2% Inuse PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND 769 bob 1 20 0 6204K 1344K CPU0 0 3:02 0.68% top 674 bob 1 20 0 11188K 1636K select 1 0:18 0.04% sshd 719 root 1 20 0 4572K 552K select 0 0:03 0.01% make 28760 root 1 52 0 346M 302M pfault 2 13:59 0.00% c++ 28812 root 1 52 0 208M 167M pfault 2 2:54 0.00% c++ 28815 root 1 52 0 212M 171M pfault 1 2:20 0.00% c++ 22172 root 1 20 0 13036K 4484K select 2 2:09 0.00% make 28820 root 1 52 0 145M 104M pfault 1 2:00 0.00% c++ 21438 root 1 20 0 7092K 556K select 0 0:05 0.00% make 695 root 1 20 0 4016K 552K select 1 0:04 0.00% make 593 root 1 20 0 8156K 1596K vmwait 1 0:04 0.00% sendmail 20119 root 1 20 0 4516K 548K select 1 0:03 0.00% make 21427 root 1 20 0 4484K 556K select 2 0:02 0.00% make 590 root 1 20 0 10148K 1552K vmwait 1 0:02 0.00% sshd 22168 root 1 20 0 3956K 560K select 0 0:02 0.00% make 600 root 1 20 0 4960K 0K WAIT 2 0:01 0.00% 461 root 1 20 0 4916K 1020K select 1 0:01 0.00% syslogd The machine seems dead, none of the ssh sessions responds to keystrokes, nor the serial console. There are a smattering of smsc0: warning: Failed to write register 0x114 smsc0: warning: Failed to read register 0x114 smsc0: warning: MII is busy smsc0: warning: Failed to write register 0x114 The machine still answers ping. Typing escape control-b does not bring up a debugger, did the keysequence change? Power cycling seems to be the only way out. Thanks for reading, and any suggestions. bob prohaska From owner-freebsd-arm@freebsd.org Sat Jan 13 01:59:53 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3C6B4E67655 for ; Sat, 13 Jan 2018 01:59:53 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-134.reflexion.net [208.70.210.134]) (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 E03286BF3C for ; Sat, 13 Jan 2018 01:59:52 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 19916 invoked from network); 13 Jan 2018 01:53:05 -0000 Received: from unknown (HELO mail-cs-02.app.dca.reflexion.local) (10.81.19.2) by 0 (rfx-qmail) with SMTP; 13 Jan 2018 01:53:05 -0000 Received: by mail-cs-02.app.dca.reflexion.local (Reflexion email security v8.40.4) with SMTP; Fri, 12 Jan 2018 20:53:05 -0500 (EST) Received: (qmail 15122 invoked from network); 13 Jan 2018 01:53:05 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 13 Jan 2018 01:53:05 -0000 Received: from [192.168.1.25] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 831DBEC944A; Fri, 12 Jan 2018 17:53:04 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Builworld stalls on rpi2 [various processes stuck in pfault and vmwait with 1996M Free Swap listed by top] From: Mark Millard In-Reply-To: <20180113005426.GA48702@www.zefox.net> Date: Fri, 12 Jan 2018 17:53:03 -0800 Cc: Freebsd-arm , FreeBSD Hackers Content-Transfer-Encoding: quoted-printable Message-Id: <19904500-5819-47AC-9666-7103ED87C1CA@dsl-only.net> References: <20180113005426.GA48702@www.zefox.net> To: bob prohaska X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Jan 2018 01:59:53 -0000 On 2018-Jan-12, at 4:54 PM, bob prohaska wrote: > Trying to self-host a build of r327859 using a GENERIC kernel at =20 > r327664, make seems to stall, with top showing >=20 > last pid: 28822; load averages: 3.12, 3.95, 5.09 up 0+08:39:01 = 16:39:49 > 50 processes: 1 running, 47 sleeping, 2 waiting > CPU: 0.0% user, 0.0% nice, 0.2% system, 0.9% interrupt, 98.9% idle > Mem: 527M Active, 16M Inact, 98M Laundry, 148M Wired, 86M Buf, 3272K = Free > Swap: 2048M Total, 52M Used, 1996M Free, 2% Inuse >=20 > PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU = COMMAND > 769 bob 1 20 0 6204K 1344K CPU0 0 3:02 0.68% = top > 674 bob 1 20 0 11188K 1636K select 1 0:18 0.04% = sshd > 719 root 1 20 0 4572K 552K select 0 0:03 0.01% = make > 28760 root 1 52 0 346M 302M pfault 2 13:59 0.00% = c++ > 28812 root 1 52 0 208M 167M pfault 2 2:54 0.00% = c++ > 28815 root 1 52 0 212M 171M pfault 1 2:20 0.00% = c++ > 22172 root 1 20 0 13036K 4484K select 2 2:09 0.00% = make > 28820 root 1 52 0 145M 104M pfault 1 2:00 0.00% = c++ > 21438 root 1 20 0 7092K 556K select 0 0:05 0.00% = make > 695 root 1 20 0 4016K 552K select 1 0:04 0.00% = make > 593 root 1 20 0 8156K 1596K vmwait 1 0:04 0.00% = sendmail > 20119 root 1 20 0 4516K 548K select 1 0:03 0.00% = make > 21427 root 1 20 0 4484K 556K select 2 0:02 0.00% = make > 590 root 1 20 0 10148K 1552K vmwait 1 0:02 0.00% = sshd > 22168 root 1 20 0 3956K 560K select 0 0:02 0.00% = make > 600 root 1 20 0 4960K 0K WAIT 2 0:01 0.00% = > 461 root 1 20 0 4916K 1020K select 1 0:01 0.00% = syslogd >=20 > The machine seems dead, none of the ssh sessions responds to = keystrokes,=20 > nor the serial console. There are a smattering of=20 > smsc0: warning: Failed to write register 0x114 > smsc0: warning: Failed to read register 0x114 > smsc0: warning: MII is busy > smsc0: warning: Failed to write register 0x114 >=20 > The machine still answers ping. Typing escape control-b does not > bring up a debugger, did the keysequence change? Power cycling seems > to be the only way out. With or without: options ALT_BREAK_TO_DEBUGGER For with: ~^B (with being and ^ being ) is an alternate with this. I've see the smsc0 messages before but I'm not up to -r327664+ yet. This has been with a non-debug kernel running. I've had building large ports get into such states, especially while at least one large link operation was active with other fairly large processes, as I remember. Note all the pfault and vmwait lines. It looks like -r327316 and -r327468 did not happen to avoid this. It looks like the paging/swaping has gotten stuck in some way. How tied that might be to smsc0 messages, I've no clue. You might get through by using -j3 or -j2 or -j1 which likely would use less process space at once (worst case) than -j4 happened to. Of course there are other time consequences as you approach -j1 (or no explicit -j for the buildworld at all). =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-arm@freebsd.org Sat Jan 13 02:43:50 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 504A2E6A9D5; Sat, 13 Jan 2018 02:43:50 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [69.239.235.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 2568E6DD1F; Sat, 13 Jan 2018 02:43:49 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id w0D2hlL8049243 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 12 Jan 2018 18:43:48 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w0D2hlMs049242; Fri, 12 Jan 2018 18:43:47 -0800 (PST) (envelope-from fbsd) Date: Fri, 12 Jan 2018 18:43:46 -0800 From: bob prohaska To: Mark Millard Cc: Freebsd-arm , FreeBSD Hackers , bob prohaska Subject: Re: Builworld stalls on rpi2 [various processes stuck in pfault and vmwait with 1996M Free Swap listed by top] Message-ID: <20180113024346.GB48702@www.zefox.net> References: <20180113005426.GA48702@www.zefox.net> <19904500-5819-47AC-9666-7103ED87C1CA@dsl-only.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <19904500-5819-47AC-9666-7103ED87C1CA@dsl-only.net> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Jan 2018 02:43:50 -0000 On Fri, Jan 12, 2018 at 05:53:03PM -0800, Mark Millard wrote: > > On 2018-Jan-12, at 4:54 PM, bob prohaska wrote: > > > > > The machine still answers ping. Typing escape control-b does not > > bring up a debugger, did the keysequence change? Power cycling seems > > to be the only way out. > > With or without: > > options ALT_BREAK_TO_DEBUGGER > > For with: ~^B (with being > and ^ being ) is an alternate with > this. > The line options ALT_BREAK_TO_DEBUGGER does not appear in the GENERIC kernel, but neither does the ue identifier for ethernet. I thought perhaps both were included from elsewhere. Maybe not. I'll add it. > I've see the smsc0 messages before but I'm > not up to -r327664+ yet. This has been with > a non-debug kernel running. > > I've had building large ports get into such states, > especially while at least one large link operation > was active with other fairly large processes, > as I remember. > > Note all the pfault and vmwait lines. It looks like > -r327316 and -r327468 did not happen to avoid this. > It looks like the paging/swaping has gotten stuck > in some way. How tied that might be to smsc0 > messages, I've no clue. > > You might get through by using -j3 or -j2 or -j1 which > likely would use less process space at once (worst case) > than -j4 happened to. > > Of course there are other time consequences as you > approach -j1 (or no explicit -j for the buildworld > at all). > > > I'd rather not slow things down, but slow is better than crashed.... 8-) Thanks for writing! bob prohaska From owner-freebsd-arm@freebsd.org Sat Jan 13 02:50:44 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 14E91E6B6EF for ; Sat, 13 Jan 2018 02:50:44 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1b.ore.mailhop.org (outbound1b.ore.mailhop.org [54.200.247.200]) (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 EBBC06E1B8 for ; Sat, 13 Jan 2018 02:50:43 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: 7b484a21-f80c-11e7-8486-0934409070aa X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 73.78.92.27 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [73.78.92.27]) by outbound1.ore.mailhop.org (Halon) with ESMTPSA id 7b484a21-f80c-11e7-8486-0934409070aa; Sat, 13 Jan 2018 02:50:15 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id w0D2oa4u007301; Fri, 12 Jan 2018 19:50:36 -0700 (MST) (envelope-from ian@freebsd.org) Message-ID: <1515811836.44630.114.camel@freebsd.org> Subject: Re: Builworld stalls on rpi2 [various processes stuck in pfault and vmwait with 1996M Free Swap listed by top] From: Ian Lepore To: bob prohaska , Mark Millard Cc: Freebsd-arm Date: Fri, 12 Jan 2018 19:50:36 -0700 In-Reply-To: <20180113024346.GB48702@www.zefox.net> References: <20180113005426.GA48702@www.zefox.net> <19904500-5819-47AC-9666-7103ED87C1CA@dsl-only.net> <20180113024346.GB48702@www.zefox.net> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Jan 2018 02:50:44 -0000 On Fri, 2018-01-12 at 18:43 -0800, bob prohaska wrote: > On Fri, Jan 12, 2018 at 05:53:03PM -0800, Mark Millard wrote: > > > > > > On 2018-Jan-12, at 4:54 PM, bob prohaska ; > > wrote: > > > > > > > > > > > The machine still answers ping. Typing escape control-b does not > > > bring up a debugger, did the keysequence change? Power cycling > > > seems > > > to be the only way out. > > With or without: > > > > options         ALT_BREAK_TO_DEBUGGER > > > > For with: ~^B (with being > > and ^ being ) is an alternate with > > this. > > > The line  > options         ALT_BREAK_TO_DEBUGGER > does not appear in the GENERIC kernel, but > neither does the ue identifier for ethernet. > I thought perhaps both were included from > elsewhere. Maybe not. I'll add it. > It's in std.armv7, which is included from GENERIC. -- Ian From owner-freebsd-arm@freebsd.org Sat Jan 13 03:07:07 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CFBFDE6D6C8 for ; Sat, 13 Jan 2018 03:07:07 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [69.239.235.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 9DF3F6F535; Sat, 13 Jan 2018 03:07:07 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id w0D375BJ049319 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 12 Jan 2018 19:07:06 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w0D373ET049318; Fri, 12 Jan 2018 19:07:03 -0800 (PST) (envelope-from fbsd) Date: Fri, 12 Jan 2018 19:07:03 -0800 From: bob prohaska To: Ian Lepore Cc: Mark Millard , Freebsd-arm , bob prohaska Subject: Re: Builworld stalls on rpi2 [various processes stuck in pfault and vmwait with 1996M Free Swap listed by top] Message-ID: <20180113030703.GC48702@www.zefox.net> References: <20180113005426.GA48702@www.zefox.net> <19904500-5819-47AC-9666-7103ED87C1CA@dsl-only.net> <20180113024346.GB48702@www.zefox.net> <1515811836.44630.114.camel@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1515811836.44630.114.camel@freebsd.org> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Jan 2018 03:07:07 -0000 On Fri, Jan 12, 2018 at 07:50:36PM -0700, Ian Lepore wrote: > On Fri, 2018-01-12 at 18:43 -0800, bob prohaska wrote: > > On Fri, Jan 12, 2018 at 05:53:03PM -0800, Mark Millard wrote: > > > > > > > > > On 2018-Jan-12, at 4:54 PM, bob prohaska ; > > > wrote: > > > > > > > > > > > > > > > The machine still answers ping. Typing escape control-b does not > > > > bring up a debugger, did the keysequence change? Power cycling > > > > seems > > > > to be the only way out. > > > With or without: > > > > > > options?????????ALT_BREAK_TO_DEBUGGER > > > > > > For with: ~^B (with being > > > and ^ being ) is an alternate with > > > this. > > > > > The line? > > options?????????ALT_BREAK_TO_DEBUGGER > > does not appear in the GENERIC kernel, but > > neither does the ue identifier for ethernet. > > I thought perhaps both were included from > > elsewhere. Maybe not. I'll add it. > > > > It's in std.armv7, which is included from GENERIC. Thank you, I'll undo my change. The GENERIC kernel has grown to about 10 MB. Can it be slimmed usefully on an RPI2? I got it down to about 8, but that's a small gain and it wouldn't stay running for more than a couple days.. Thanks for writing! bob prohaska From owner-freebsd-arm@freebsd.org Sat Jan 13 03:58:48 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B01ADE708CB for ; Sat, 13 Jan 2018 03:58:48 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-125.reflexion.net [208.70.210.125]) (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 6D0FD717FD for ; Sat, 13 Jan 2018 03:58:47 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 4541 invoked from network); 13 Jan 2018 02:58:41 -0000 Received: from unknown (HELO mail-cs-02.app.dca.reflexion.local) (10.81.19.2) by 0 (rfx-qmail) with SMTP; 13 Jan 2018 02:58:41 -0000 Received: by mail-cs-02.app.dca.reflexion.local (Reflexion email security v8.40.4) with SMTP; Fri, 12 Jan 2018 21:58:41 -0500 (EST) Received: (qmail 10921 invoked from network); 13 Jan 2018 02:58:40 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 13 Jan 2018 02:58:40 -0000 Received: from [192.168.1.25] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 10FC7EC7C39; Fri, 12 Jan 2018 18:58:40 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Builworld stalls on rpi2 [various processes stuck in pfault and vmwait with 1996M Free Swap listed by top] From: Mark Millard In-Reply-To: <20180113024346.GB48702@www.zefox.net> Date: Fri, 12 Jan 2018 18:58:39 -0800 Cc: Freebsd-arm , FreeBSD Hackers Content-Transfer-Encoding: quoted-printable Message-Id: <866A14D4-2D81-4C2E-B902-0AD05514E709@dsl-only.net> References: <20180113005426.GA48702@www.zefox.net> <19904500-5819-47AC-9666-7103ED87C1CA@dsl-only.net> <20180113024346.GB48702@www.zefox.net> To: bob prohaska X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Jan 2018 03:58:48 -0000 On 2018-Jan-12, at 6:43 PM, bob prohaska wrote: > On Fri, Jan 12, 2018 at 05:53:03PM -0800, Mark Millard wrote: >>=20 >> On 2018-Jan-12, at 4:54 PM, bob prohaska = wrote: >>=20 >>>=20 >>> The machine still answers ping. Typing escape control-b does not >>> bring up a debugger, did the keysequence change? Power cycling seems >>> to be the only way out. >>=20 >> With or without: >>=20 >> options ALT_BREAK_TO_DEBUGGER >>=20 >> For with: ~^B (with being >> and ^ being ) is an alternate with >> this. >>=20 >=20 > The line=20 > options ALT_BREAK_TO_DEBUGGER > does not appear in the GENERIC kernel, but > neither does the ue identifier for ethernet. > I thought perhaps both were included from > elsewhere. Maybe not. I'll add it. >=20 >=20 I tend to include GENERIC in another file and then specify things I want as well or instead: # more /usr/src/sys/arm/conf/GENERIC-NODBG=20 include "GENERIC" ident GENERIC-NODBG makeoptions DEBUG=3D-g # Build kernel with gdb(1) = debug symbols options ALT_BREAK_TO_DEBUGGER options KDB # Enable kernel debugger support # For minimum debugger support (stable branch) use: options KDB_TRACE # Print a stack trace for a = panic options DDB # Enable the kernel debugger # Extra stuff: #options VERBOSE_SYSINIT # Enable verbose sysinit = messages #options BOOTVERBOSE=3D1 #options BOOTHOWTO=3DRB_VERBOSE options KLD_DEBUG #options KTR #options KTR_MASK=3DKTR_TRAP ##options KTR_CPUMASK=3D0xF #options KTR_VERBOSE # Disable any extra checking for. . . nooptions INVARIANTS # Enable calls of extra sanity = checking nooptions INVARIANT_SUPPORT # Extra sanity checks of = internal structures, required by INVARIANTS nooptions WITNESS # Enable checks to detect = deadlocks and cycles nooptions WITNESS_SKIPSPIN # Don't run witness on spinlocks = for speed nooptions DIAGNOSTIC nooptions BUF_TRACKING nooptions FULL_BUF_TRACKING nooptions DEADLKRES # Enable the deadlock resolver nooptions USB_DEBUG nooptions USB_REQ_DEBUG nooptions USB_VERBOSE # more /usr/src/sys/arm/conf/GENERIC-DBG include "GENERIC" ident GENERIC-DBG makeoptions DEBUG=3D-g # Build kernel with gdb(1) = debug symbols options ALT_BREAK_TO_DEBUGGER options KDB # Enable kernel debugger support # For minimum debugger support (stable branch) use: options KDB_TRACE # Print a stack trace for a = panic options DDB # Enable the kernel debugger # Extra stuff: #options VERBOSE_SYSINIT # Enable verbose sysinit = messages #options BOOTVERBOSE=3D1 #options BOOTHOWTO=3DRB_VERBOSE #options KLD_DEBUG #options KTR #options KTR_MASK=3DKTR_TRAP|KTR_PROC ##options KTR_CPUMASK=3D0xF #options KTR_VERBOSE # Enable any extra checking for. . . options INVARIANTS # Enable calls of extra sanity = checking options INVARIANT_SUPPORT # Extra sanity checks of = internal structures, required by INVARIANTS options WITNESS # Enable checks to detect = deadlocks and cycles options WITNESS_SKIPSPIN # Don't run witness on spinlocks = for speed nooptions DIAGNOSTIC options BUF_TRACKING options FULL_BUF_TRACKING options DEADLKRES # Enable the deadlock resolver options USB_DEBUG #options USB_REQ_DEBUG #options USB_VERBOSE This avoids changing the official GENERIC. Of course I have to specify the non-default file name for the build. >> I've see the smsc0 messages before but I'm >> not up to -r327664+ yet. This has been with >> a non-debug kernel running. >>=20 >> I've had building large ports get into such states, >> especially while at least one large link operation >> was active with other fairly large processes, >> as I remember. >>=20 >> Note all the pfault and vmwait lines. It looks like >> -r327316 and -r327468 did not happen to avoid this. >> It looks like the paging/swaping has gotten stuck >> in some way. How tied that might be to smsc0 >> messages, I've no clue. >>=20 >> You might get through by using -j3 or -j2 or -j1 which >> likely would use less process space at once (worst case) >> than -j4 happened to. >>=20 >> Of course there are other time consequences as you >> approach -j1 (or no explicit -j for the buildworld >> at all). >>=20 >>=20 >=20 > I'd rather not slow things down, but slow is better than > crashed.... =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-arm@freebsd.org Sat Jan 13 06:03:29 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1B82FE766FE for ; Sat, 13 Jan 2018 06:03:29 +0000 (UTC) (envelope-from wma@semihalf.com) Received: from mail-qk0-x22b.google.com (mail-qk0-x22b.google.com [IPv6:2607:f8b0:400d:c09::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C7E0D75C47 for ; Sat, 13 Jan 2018 06:03:28 +0000 (UTC) (envelope-from wma@semihalf.com) Received: by mail-qk0-x22b.google.com with SMTP id d21so11337354qkj.3 for ; Fri, 12 Jan 2018 22:03:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=semihalf-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=102NKjObmyLsE5ys7jl3S4pPmzx9jGTtpBd8nJjL6mw=; b=05lK4VE6V2jWunhtjfOaChWdGlqFMp5jEyQbtVyLeTaaS7kR6GgyCsL6Gb+gW86tOU eQvl0/UBY16yLD6ay8tuqC476H+vAGd5bPK/jjZUE3Dm+9Reo0IMP3oBMyDjRfbBp06P ETRj9E4Em6gFIyk2o14d1fs0+DW09I/z6B4fovjI5DL3Gf6Lflvx4lE6CNPZ7cUkvMvs 6TVtbluWQKrK/nCohxLLJ82De7QLoPe14IJ4j44gHuIL+Cb/3sSIbFBdM3GjTtm0ipLZ 97dG6zHEszo90Wazx2YoRcyfC6qeN5/6VQJBhg14DBY7i03+itnJtYM7jqgzaZ27OkEs gh1A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=102NKjObmyLsE5ys7jl3S4pPmzx9jGTtpBd8nJjL6mw=; b=hGR3uYCDBYt0ixMMp9gyXCempgn4HccwAmhyw3qHKd2iJSi1D7I6tjJfE10Xy8bgFA clzV0sxj6wxzRnvjzcWHMEKmJiyfhZDWlOsexFH82gDUFczcU8rB1c2ZEsGbjBRc2cPN 3Hb2sK780GLMVfMSUL4FsAViEeD1APOFNd4f5ZsjrGvnz15UkcNyhm/5XRIELZaN3luW Qm7GQQeqfV60fRu+rBVq3BCWPq5Jk22ztrblYubGGlwIm18kB4xbbzAS2Dt3J+zokzYf vIBfIjxnpIUr/MXdpwFlBfgvcAh4BEZm27Pic9YAMT6JZHouCD7uycNQ8emjcTbaEwVa 2Gxg== X-Gm-Message-State: AKwxytdvCoRuBE2zb84ES4wqTUMbsatvcY21v5K7pjxHQSbVnSxcipDU UNQEbmJik+7LpbDq3nRcjFJ+2dBX3FrLiSia+1iKvJ10 X-Google-Smtp-Source: ACJfBosRfXzHekLygjVXINWcEvKfsDJ6WKhcMELqb4hdS0/NjhVlEtzb198SfVECHYAf50vhNQFHZPCYWezbS9yMntU= X-Received: by 10.233.220.130 with SMTP id q124mr24828332qkf.170.1515823408030; Fri, 12 Jan 2018 22:03:28 -0800 (PST) MIME-Version: 1.0 Received: by 10.200.57.103 with HTTP; Fri, 12 Jan 2018 22:03:27 -0800 (PST) In-Reply-To: References: From: Wojciech Macek Date: Sat, 13 Jan 2018 07:03:27 +0100 Message-ID: Subject: Re: tcpdump reporting strange packets on RPi3 To: Michael Tuexen Cc: freebsd-arm@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Jan 2018 06:03:29 -0000 Adding missing list... W dniu sobota, 13 stycznia 2018 Wojciech Macek napisa=C5=82(a): > Yes, its a problem with 32-bit BPF ioctl compat support. I'm planning to submit a patch next week. > > Regards, > Wojtek > wma@ > > W dniu pi=C4=85tek, 12 stycznia 2018 Michael Tuexen napisa=C5=82(a): >> Dear all, >> >> when running FreeBSD head on a RPi and using tcpdump on the ue0 interface, I do >> see strange packets. Something like >> >> 01:59:44.000000 a5:a5:a5:a5:a5:a5 > a5:a5:a5:a5:a5:a5, ethertype Unknown (0xa5a5), length 666370074: >> 0x0000: a5a5 a5a5 a5a5 a5a5 a5a5 a5a5 a5a5 a5a5 ................ >> 0x0010: a5a5 a5a5 a5a5 a5a5 a5a5 a5a5 a5a5 a5a5 ................ >> 0x0020: a5a5 a5a5 a5a5 a5a5 a5a5 a5a5 a5a5 a5a5 ................ >> 0x0030: a5a5 a5a5 .... >> >> gets reported... Any ideas what went wrong? >> >> Best regards >> Michael >> _______________________________________________ >> freebsd-arm@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-arm >> To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" >> From owner-freebsd-arm@freebsd.org Sat Jan 13 09:08:59 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0A2EEE7F108; Sat, 13 Jan 2018 09:08:59 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id 648EF7D1AF; Sat, 13 Jan 2018 09:08:57 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.55.3]) by phk.freebsd.dk (Postfix) with ESMTP id B30F827342; Sat, 13 Jan 2018 09:08:49 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.15.2/8.15.2) with ESMTPS id w0D98X3F036829 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 13 Jan 2018 09:08:33 GMT (envelope-from phk@critter.freebsd.dk) Received: (from phk@localhost) by critter.freebsd.dk (8.15.2/8.15.2/Submit) id w0D98XhH036828; Sat, 13 Jan 2018 09:08:33 GMT (envelope-from phk) To: Mark Millard cc: bob prohaska , FreeBSD Hackers , Freebsd-arm Subject: Re: Builworld stalls on rpi2 [various processes stuck in pfault and vmwait with 1996M Free Swap listed by top] In-reply-to: <19904500-5819-47AC-9666-7103ED87C1CA@dsl-only.net> From: "Poul-Henning Kamp" References: <20180113005426.GA48702@www.zefox.net> <19904500-5819-47AC-9666-7103ED87C1CA@dsl-only.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <36826.1515834513.1@critter.freebsd.dk> Content-Transfer-Encoding: quoted-printable Date: Sat, 13 Jan 2018 09:08:33 +0000 Message-ID: <36827.1515834513@critter.freebsd.dk> X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Jan 2018 09:08:59 -0000 -------- In message <19904500-5819-47AC-9666-7103ED87C1CA@dsl-only.net>, Mark Milla= rd wr ites: >> Trying to self-host a build of r327859 using a GENERIC kernel at = >> r327664, make seems to stall, with top showing In all likelyhood you do not have enough swap configured, getting through the llvm compilation takes insane amounts of VM these days. At the very least you can forget anything about make -j N for N>1 -- = Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe = Never attribute to malice what can adequately be explained by incompetence= . From owner-freebsd-arm@freebsd.org Sat Jan 13 14:54:06 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 745AFE6CCAA for ; Sat, 13 Jan 2018 14:54:06 +0000 (UTC) (envelope-from tuexen@freebsd.org) Received: from drew.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.franken.de", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3B5F368809 for ; Sat, 13 Jan 2018 14:54:06 +0000 (UTC) (envelope-from tuexen@freebsd.org) Received: from [IPv6:2003:cd:6bec:5d00:9149:3c3e:3ac9:9f76] (p200300CD6BEC5D0091493C3E3AC99F76.dip0.t-ipconnect.de [IPv6:2003:cd:6bec:5d00:9149:3c3e:3ac9:9f76]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTPSA id 3B4FF721E280C; Sat, 13 Jan 2018 15:54:02 +0100 (CET) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: Re: tcpdump reporting strange packets on RPi3 From: Michael Tuexen In-Reply-To: Date: Sat, 13 Jan 2018 15:53:57 +0100 Cc: freebsd-arm@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Wojciech Macek X-Mailer: Apple Mail (2.3445.5.20) X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=disabled version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail-n.franken.de X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Jan 2018 14:54:06 -0000 > On 13. Jan 2018, at 07:03, Wojciech Macek wrote: >=20 >=20 > Adding missing list... >=20 > W dniu sobota, 13 stycznia 2018 Wojciech Macek = napisa=C5=82(a): > > Yes, its a problem with 32-bit BPF ioctl compat support. I'm = planning to submit a patch next week. Great. I'm happy to test it. Just to be clear: The RPi3 I'm using runs a 64-bit kernel and world: FreeBSD rpi3 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r327876: Fri Jan 12 = 16:48:55 CET 2018 = tuexen@rpi3:/usr/home/tuexen/head/sys/arm64/compile/TCP arm64 Best regards Michael > > > > Regards, > > Wojtek > > wma@ > > > > W dniu pi=C4=85tek, 12 stycznia 2018 Michael Tuexen = napisa=C5=82(a): > >> Dear all, > >> > >> when running FreeBSD head on a RPi and using tcpdump on the ue0 = interface, I do > >> see strange packets. Something like > >> > >> 01:59:44.000000 a5:a5:a5:a5:a5:a5 > a5:a5:a5:a5:a5:a5, ethertype = Unknown (0xa5a5), length 666370074: > >> 0x0000: a5a5 a5a5 a5a5 a5a5 a5a5 a5a5 a5a5 a5a5 = ................ > >> 0x0010: a5a5 a5a5 a5a5 a5a5 a5a5 a5a5 a5a5 a5a5 = ................ > >> 0x0020: a5a5 a5a5 a5a5 a5a5 a5a5 a5a5 a5a5 a5a5 = ................ > >> 0x0030: a5a5 a5a5 .... > >> > >> gets reported... Any ideas what went wrong? > >> > >> Best regards > >> Michael > >> _______________________________________________ > >> freebsd-arm@freebsd.org mailing list > >> https://lists.freebsd.org/mailman/listinfo/freebsd-arm > >> To unsubscribe, send any mail to = "freebsd-arm-unsubscribe@freebsd.org" > >> From owner-freebsd-arm@freebsd.org Sat Jan 13 15:57:35 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0A040E70026 for ; Sat, 13 Jan 2018 15:57:35 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-115.reflexion.net [208.70.210.115]) (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 A98F16AA52 for ; Sat, 13 Jan 2018 15:57:33 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 32715 invoked from network); 13 Jan 2018 15:50:47 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 13 Jan 2018 15:50:47 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v8.40.4) with SMTP; Sat, 13 Jan 2018 10:50:47 -0500 (EST) Received: (qmail 22258 invoked from network); 13 Jan 2018 15:50:47 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 13 Jan 2018 15:50:47 -0000 Received: from [192.168.1.25] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 086D2EC93F7; Sat, 13 Jan 2018 07:50:47 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Builworld stalls on rpi2 [various processes stuck in pfault and vmwait with 1996M Free Swap listed by top] From: Mark Millard In-Reply-To: <36827.1515834513@critter.freebsd.dk> Date: Sat, 13 Jan 2018 07:50:46 -0800 Cc: bob prohaska , FreeBSD Hackers , Freebsd-arm Content-Transfer-Encoding: quoted-printable Message-Id: <3EDDDF6B-684A-436E-A2F5-3868BB279951@dsl-only.net> References: <20180113005426.GA48702@www.zefox.net> <19904500-5819-47AC-9666-7103ED87C1CA@dsl-only.net> <36827.1515834513@critter.freebsd.dk> To: Poul-Henning Kamp X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Jan 2018 15:57:35 -0000 On 2018-Jan-13, at 1:08 AM, Poul-Henning Kamp = wrote: > In message <19904500-5819-47AC-9666-7103ED87C1CA@dsl-only.net>, Mark = Millard wr > ites: >=20 >>> Trying to self-host a build of r327859 using a GENERIC kernel at =20 >>> r327664, make seems to stall, with top showing [That text is Bob Prohaska's, not mine.] > In all likelyhood you do not have enough swap configured, getting > through the llvm compilation takes insane amounts of VM these days. As I remember, for the 1 GiByte of RAM that a RPi2B V1.1 has, the boot sequence complains about having Swap: 2048M Total without also adjusting some other defaults, reporting the intended maximum is smaller. As I remember the figure it reports for the intended maximum for the defaults was between 1.6 GiBytes and 1.7 GiBytes. (I do not remember the detailed figure.) [I assume a RPi2B V1.1 (cortex-a7) based instead of the cortex-a53 based V1.2.] [An RPi3 with 1 GiByte of RAM and the aarch64 FreeBSD allows more swap before complaining, something over 3.5 GiBytes of as I remember.] The interesting part of Bob's report was that top showed only a little swap used at the time: Swap: 2048M Total, 52M Used, 1996M Free, 2% Inuse But it shows: Mem: 527M Active, 16M Inact, 98M Laundry, 148M Wired, 86M Buf, 3272K = Free as well, apparently insufficient free memory to put the available swap space to use? FreeBSD's head looks to need to be more aggressive about swapping out so that it keeps enough free-space to allow swapping to occur (at least for some types of contexts). For reference, the pfaults and vmwaits listed by top were: 28760 root 1 52 0 346M 302M pfault 2 13:59 0.00% = c++ 28812 root 1 52 0 208M 167M pfault 2 2:54 0.00% = c++ 28815 root 1 52 0 212M 171M pfault 1 2:20 0.00% = c++ 28820 root 1 52 0 145M 104M pfault 1 2:00 0.00% = c++ 593 root 1 20 0 8156K 1596K vmwait 1 0:04 0.00% = sendmail 590 root 1 20 0 10148K 1552K vmwait 1 0:02 0.00% = sshd > At the very least you can forget anything about make -j N for N>1 I made a similar suggestion. I'll note that I've seen similar hangups with building large ports after a bunch of other ports had already built. After rebooting when I try again the build completes. So, it appears that the prior activity helped work things into reaching the hung-up state. (Fragmentation of some kind?) In general it has been easier (and faster) to build things on the RPi3 than on the RPi2B V1.1, despite both having 1 GiByte of RAM. This suggests 32-bit address space or armv7 specific issues might be involved. =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-arm@freebsd.org Sat Jan 13 17:34:42 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 298BCE74E3C for ; Sat, 13 Jan 2018 17:34:42 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [69.239.235.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 0DF1B6E4DB for ; Sat, 13 Jan 2018 17:34:40 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id w0DHRWAK051801 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 13 Jan 2018 09:27:33 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w0DHRVxV051800; Sat, 13 Jan 2018 09:27:31 -0800 (PST) (envelope-from fbsd) Date: Sat, 13 Jan 2018 09:27:31 -0800 From: bob prohaska To: Mark Millard Cc: freebsd-arm@freebsd.org, bob prohaska Subject: Re: Builworld stalls on rpi2 Message-ID: <20180113172731.GB51530@www.zefox.net> References: <20180113005426.GA48702@www.zefox.net> <5D61DF2C-2CEB-442C-8CBC-1EE0988CF2BC@dsl-only.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5D61DF2C-2CEB-442C-8CBC-1EE0988CF2BC@dsl-only.net> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Jan 2018 17:34:42 -0000 On Sat, Jan 13, 2018 at 08:32:20AM -0800, Mark Millard wrote: > Does your 2 GiByte swap-space RPi2 "dmesg -a" output > (or serial console history) show any messages about the > swap-space size and a potential adjustment to a related > kernel parameter? > Yes, console history contains the line warning: total configured swap (524288 pages) exceeds maximum recommended amount (405460 pages). Since top reported what looked like ample swap, and buildworld seemed to run successfully, I didn't heed the warning: increase kern.maxswzone or reduce amount of swap. message. Would it be helpful to do so now? gpart show da0 reports => 0 122544516 da0 BSD (58G) 0 4194304 1 freebsd-ufs (2.0G) 4194304 4194304 2 freebsd-swap (2.0G) 8388608 6291456 4 freebsd-ufs (3.0G) 14680064 107864452 5 freebsd-ufs (51G) The units are somewhat baffling, since the apparent swap partition size does not match (numerically) the dmesg value. Thanks for writing! bob prohaska From owner-freebsd-arm@freebsd.org Sat Jan 13 17:48:15 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C2F77E75B77 for ; Sat, 13 Jan 2018 17:48:15 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [69.239.235.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 9F6BE6F095 for ; Sat, 13 Jan 2018 17:48:15 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id w0DHmGol051860 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Sat, 13 Jan 2018 09:48:17 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w0DHmFwn051859 for freebsd-arm@freebsd.org; Sat, 13 Jan 2018 09:48:16 -0800 (PST) (envelope-from fbsd) Date: Sat, 13 Jan 2018 09:48:15 -0800 From: bob prohaska To: freebsd-arm@freebsd.org Subject: Re: Builworld stalls on rpi2 [various processes stuck in pfault] Message-ID: <20180113174815.GC51530@www.zefox.net> References: <201801131646.w0DGkXtK051654@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201801131646.w0DGkXtK051654@www.zefox.net> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Jan 2018 17:48:15 -0000 On Sat, Jan 13, 2018 at 09:08:33AM +0000, Poul-Henning Kamp wrote: > > In all likelyhood you do not have enough swap configured, getting > through the llvm compilation takes insane amounts of VM these days. > 2048M of swap are configured on a USB flash drive. Highest usage seen was just shy of 1000M, apparently when clang was being linked. > At the very least you can forget anything about make -j N for N>1 > Prior to the v6-v7 split j4 worked well and finished in about 18 hours, j>4 didn't seem faster but did not freeze. There seems also to be a problem with u-boot, which I (perhaps mistakenly) upgraded at about the same time. It began to emit streams of Timeout poll on interrupt endpoint messages. They were eliminated by simply disconnecting the USB mouse and keyboard (both old Dell units). I haven't yet tried another keyboard. Thanks for reading, and any ideas! bob prohaska From owner-freebsd-arm@freebsd.org Sat Jan 13 17:51:49 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7D13BE75ED7 for ; Sat, 13 Jan 2018 17:51:49 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-100.reflexion.net [208.70.210.100]) (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 28A746F360 for ; Sat, 13 Jan 2018 17:51:48 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 8967 invoked from network); 13 Jan 2018 17:51:42 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 13 Jan 2018 17:51:42 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v8.40.4) with SMTP; Sat, 13 Jan 2018 12:51:42 -0500 (EST) Received: (qmail 7965 invoked from network); 13 Jan 2018 17:51:42 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 13 Jan 2018 17:51:42 -0000 Received: from [192.168.1.25] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id CD77BEC942D; Sat, 13 Jan 2018 09:51:41 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Builworld stalls on rpi2 [various processes stuck in pfault and vmwait with 1996M Free Swap listed by top] From: Mark Millard In-Reply-To: <20180113172731.GB51530@www.zefox.net> Date: Sat, 13 Jan 2018 09:51:41 -0800 Cc: Freebsd-arm , FreeBSD Hackers Content-Transfer-Encoding: quoted-printable Message-Id: References: <20180113005426.GA48702@www.zefox.net> <5D61DF2C-2CEB-442C-8CBC-1EE0988CF2BC@dsl-only.net> <20180113172731.GB51530@www.zefox.net> To: bob prohaska X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Jan 2018 17:51:49 -0000 On 2018-Jan-13, at 9:27 AM, bob prohaska wrote: > On Sat, Jan 13, 2018 at 08:32:20AM -0800, Mark Millard wrote: >> Does your 2 GiByte swap-space RPi2 "dmesg -a" output >> (or serial console history) show any messages about the >> swap-space size and a potential adjustment to a related >> kernel parameter? >>=20 > Yes, console history contains the line >=20 > warning: total configured swap (524288 pages) exceeds maximum = recommended amount (405460 pages). >=20 > Since top reported what looked like ample swap, and buildworld seemed = to > run successfully, I didn't heed the >=20 > warning: increase kern.maxswzone or reduce amount of swap. >=20 > message.=20 >=20 > Would it be helpful to do so now? gpart show da0 reports >=20 > =3D> 0 122544516 da0 BSD (58G) > 0 4194304 1 freebsd-ufs (2.0G) > 4194304 4194304 2 freebsd-swap (2.0G) > 8388608 6291456 4 freebsd-ufs (3.0G) > 14680064 107864452 5 freebsd-ufs (51G) >=20 > The units are somewhat baffling, since the apparent swap partition > size does not match (numerically) the dmesg value. [gpart is showing in 512 Byte units, probably matching a drive-organization characteristic.] page =3D 4 KiBytes So 405460 pages =3D 1621840 KiBytes, so a little over 1.54 GiBytes. For reference: 524288 pages =3D 2097152 KiBytes, so exactly 2.0 GiBytes. Note: 2*2097152 =3D=3D 4194304 exactly, so the 512 Byte count is an exact match to the 2.0 GiByte swap size. When there is only 1 GiByte of RAM, I'm not sure if increasing kern.maxswzone is a good tradeoff or not. Historically I've kept the swap space within the recommended maximum for the default kern.maxswzone value. But for the RPi2B V1.1 context, I've not tried a self-hosted buildworld in a long time, doing cross builds instead. =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-arm@freebsd.org Sat Jan 13 22:09:00 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3A5FAEB212A for ; Sat, 13 Jan 2018 22:09:00 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-147.reflexion.net [208.70.210.147]) (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 F2AEA7A695 for ; Sat, 13 Jan 2018 22:08:59 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 14531 invoked from network); 13 Jan 2018 22:02:18 -0000 Received: from unknown (HELO rtc-sm-01.app.dca.reflexion.local) (10.81.150.1) by 0 (rfx-qmail) with SMTP; 13 Jan 2018 22:02:18 -0000 Received: by rtc-sm-01.app.dca.reflexion.local (Reflexion email security v8.40.4) with SMTP; Sat, 13 Jan 2018 17:02:18 -0500 (EST) Received: (qmail 29175 invoked from network); 13 Jan 2018 22:02:18 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 13 Jan 2018 22:02:18 -0000 Received: from [192.168.1.25] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 5BB56EC9004; Sat, 13 Jan 2018 14:02:17 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Builworld stalls on rpi2 [various processes stuck in pfault and vmwait with 1996M Free Swap listed by top] From: Mark Millard In-Reply-To: Date: Sat, 13 Jan 2018 14:02:16 -0800 Cc: FreeBSD Hackers , Freebsd-arm Content-Transfer-Encoding: quoted-printable Message-Id: <3CEAAA69-1C79-4545-8ED6-D277A65BBAB1@dsl-only.net> References: <20180113005426.GA48702@www.zefox.net> <5D61DF2C-2CEB-442C-8CBC-1EE0988CF2BC@dsl-only.net> <20180113172731.GB51530@www.zefox.net> To: bob prohaska X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Jan 2018 22:09:00 -0000 On 2018-Jan-13, at 9:51 AM, Mark Millard wrote: > On 2018-Jan-13, at 9:27 AM, bob prohaska = wrote: >=20 >> On Sat, Jan 13, 2018 at 08:32:20AM -0800, Mark Millard wrote: >>> Does your 2 GiByte swap-space RPi2 "dmesg -a" output >>> (or serial console history) show any messages about the >>> swap-space size and a potential adjustment to a related >>> kernel parameter? >>>=20 >> Yes, console history contains the line >>=20 >> warning: total configured swap (524288 pages) exceeds maximum = recommended amount (405460 pages). >>=20 >> Since top reported what looked like ample swap, and buildworld seemed = to >> run successfully, I didn't heed the >>=20 >> warning: increase kern.maxswzone or reduce amount of swap. >>=20 >> message.=20 >>=20 >> Would it be helpful to do so now? gpart show da0 reports >>=20 >> =3D> 0 122544516 da0 BSD (58G) >> 0 4194304 1 freebsd-ufs (2.0G) >> 4194304 4194304 2 freebsd-swap (2.0G) >> 8388608 6291456 4 freebsd-ufs (3.0G) >> 14680064 107864452 5 freebsd-ufs (51G) >>=20 >> The units are somewhat baffling, since the apparent swap partition >> size does not match (numerically) the dmesg value. >=20 > [gpart is showing in 512 Byte units, probably matching > a drive-organization characteristic.] >=20 > page =3D 4 KiBytes > So 405460 pages =3D 1621840 KiBytes, so a little over 1.54 GiBytes. >=20 > For reference: > 524288 pages =3D 2097152 KiBytes, so exactly 2.0 GiBytes. >=20 > Note: 2*2097152 =3D=3D 4194304 exactly, so the 512 Byte count > is an exact match to the 2.0 GiByte swap size. >=20 > When there is only 1 GiByte of RAM, I'm not sure if increasing > kern.maxswzone is a good tradeoff or not. >=20 > Historically I've kept the swap space within the recommended > maximum for the default kern.maxswzone value. But for the RPi2B > V1.1 context, I've not tried a self-hosted buildworld in a > long time, doing cross builds instead. On a RPi2B V1.1 I get: db> print *maxswzone 0 The code in swap_pager_swap_init has : /* * Initialize our zone, guessing on the number we need based * on the number of pages in the system. */ n =3D vm_cnt.v_page_count / 2; if (maxswzone && n > maxswzone / sizeof(struct swblk)) n =3D maxswzone / sizeof(struct swblk); which means that maxswzone is ignored because it is zero and vm_cnt.v_page_count / 2 is used directly. Setting maxswzone can not make n any larger, only smaller. it would appear that "increase kern.maxswzone" only applies when one already has set the figure manually in a manor that restricts n. Quoting "man 8 loader" : kern.maxswzone Limits the amount of KVM to be used to hold swap = metadata, which directly governs the maximum amount of swap the system can support, at the rate of approximately 200 = MB of swap space per 1 MB of metadata. This value is = specified in bytes of KVA space. If no value is provided, the = system allocates enough memory to handle an amount of swap = that corresponds to eight times the amount of physical = memory present in the system. Note that swap metadata can be fragmented, which = means that the system can run out of space before it reaches the theoretical limit. Therefore, care should be taken = to not configure more swap than approximately half of the theoretical maximum. Running out of space for swap metadata can leave the = system in an unrecoverable state. Therefore, you should = only change this parameter if you need to greatly extend = the KVM reservation for other resources such as the buffer = cache or kern.ipc.nmbclusters. Modifies kernel option VM_SWZONE_SIZE_MAX. Multiple points relative to the above: Note that "care should be taken to not configure more swap than = approximately half of the theoretical maximum" because "swap metadata can be = fragmented" and "the system can run out of space before it reaches the theoretical = limit". Looking at the swapon_check_swzone code the message is reporting the "half" figure, not the theoretical maximum. But there is also: you should only change this parameter if you need to greatly extend = the KVM reservation for other resources such as the buffer = cache or kern.ipc.nmbclusters. Modifies kernel option VM_SWZONE_SIZE_MAX. If I read all this right, it says that reducing swap is normally the intended handling when the message is reported unless one has been adjusting various kernel resource reservations. That would be consistent with the maxswzone only being able to decrease n in the code that I quoted earlier. Given that 1 GiByte of RAM and 2 GiByte of Swap reports that the maximum recommended swap is about 1.54 GiBytes (converting from pages), the: If no value is provided, the system allocates enough memory to handle an amount of swap = that corresponds to eight times the amount of physical = memory present in the system. just seems to not apply directly to an RPi2B V1.1: 1.54 is much less = than 8*1. =3D=3D=3D Mark Millard markmi at dsl-only.net