From owner-freebsd-arm@freebsd.org Sun Jul 1 00:32:17 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E709BFE04C8 for ; Sun, 1 Jul 2018 00:32:16 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic314-21.consmr.mail.ne1.yahoo.com (sonic314-21.consmr.mail.ne1.yahoo.com [66.163.189.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7B297920A1 for ; Sun, 1 Jul 2018 00:32:16 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: 6kiSxyMVM1lyE_2yNwgnorHdOtuYdCeFxwsapbHdIjCp1M9WNp7qSbFBaRB4UQV coxbTbRaWXwxF9kitngvCMF1HMl5dXa4_Rg_yJsw7Bb8ozpuUIv.31nUctcGnSZBxHmNkiFJjK70 dRy54gXBtEuAHzU4d4KEpcNO.1BLoYPdWV8WOHACEHpXZmVJJCSaZeRQhINa90njqjs50QaSQlhP QlAz1FpLGZOYofxbpEUWtvYM4D9xkLMonAVsUs4ghnOVtb2i3sHCua83wsi2leMPKvux8ZIzzZIn 3SIhNqCa7OQVBo1NWGyTxV5Sbzfdp1eFFDnnteDgE1NetQY3fBjrrbXOQp0oWkoDsYRZtA1FAHWP 57RBaAm5EEKDDtzNJuahecM_Ngb8lcjdfa5tysWniEYGLDrcg1BaZCn1UGna.Xz7OyIsrXp8crq6 WU63d19Z9cjWVYQrUd3JxwFHUmLaeabZI_diV7XCwl5qRsKJaO5XsAET4D868ff_JIIiO.ewnpJ2 eELJQSFQRRSKWrZiE.gw4b9vHCKrLNY61KeKlDmFz2olKScdj.8jiJWtSWvfRm1A2HJ49lXwYwo8 8rrcvC84QAgqhGA.FYfeikJFejEP2gG_WQA92G0UZYBGL6.X0w5KPLFSD._JgcYLWUzycUw9wcv8 9h.B5XG.jXs2jJP6Njt_YPUIx6FzCnsmCVCt3dBMmE8M_r33NWbGndKZAIPM2.CF_pzFVhsnzZoq GlzlS0qk4sQ3Y4.qYn76VjMvdUJ3tYF4NjYdzjeknh.6xQ__LNzgHARIATiHTqvSpzZPRFvG7iXO kH1CRq6nsiolhWPcQ50reIZGKVeXhyMgK58UFL.fR5QxJBOw_Z5qv4C_GPsyhY4eVhiHESCtNCFE 5bx5czA4aliLpGEpdJFVl1_FI5ReXSq3ZWXRoQewkw33Tv8bWTbDiDyg2QATa69oVIT90K5A6d1r PHaTXnZC6vqguCFRT5AehbND.GHPH8soruA-- Received: from sonic.gate.mail.ne1.yahoo.com by sonic314.consmr.mail.ne1.yahoo.com with HTTP; Sun, 1 Jul 2018 00:32:08 +0000 Received: from ip70-189-131-151.lv.lv.cox.net (EHLO [192.168.0.105]) ([70.189.131.151]) by smtp421.mail.ne1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 6d9cd597039287776f32ac791069d102; Sun, 01 Jul 2018 00:32:04 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\)) Subject: Re: devmatch: Malformed NOMATCH string: '$' From: Mark Millard In-Reply-To: <20180630232102.GB47792@www.zefox.net> Date: Sat, 30 Jun 2018 17:32:03 -0700 Cc: Warner Losh , "freebsd-arm@freebsd.org" Content-Transfer-Encoding: quoted-printable Message-Id: References: <20180630221821.GA47792@www.zefox.net> <20180630232102.GB47792@www.zefox.net> To: bob prohaska X-Mailer: Apple Mail (2.3445.8.2) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jul 2018 00:32:17 -0000 On 2018-Jun-30, at 4:21 PM, bob prohaska wrote: > On Sat, Jun 30, 2018 at 05:07:06PM -0600, Warner Losh wrote: >> See UPDATING. I fixed this. >>=20 > I'm halfway between chicken and egg at the moment and can't look yet.=20= > Will it keep until I can checkout a source tree? There may be quite > a few reboots in the meantime. >=20 > . . . I think Warner L. was referring to ( I looked at UPDATING from head -r335812 but this entry is older ): 20180530: The kernel / userland interface for devinfo changed, so you'll need a new kernel and userland as a pair for it to work = (rebuilding lib/libdevinfo is all that's required). devinfo and devmatch = will not work, but everything else will when there's a mismatch. If I understand right, having devinfo and devmatch not working is not necessarily a status of being fundamentally broken overall. (Just less automatic?) But I've never had to deal with the messages. > . . . >>=20 >> On Sat, Jun 30, 2018 at 4:18 PM, bob prohaska = wrote: >>=20 >>> In booting up a new snapshot for the rpi3 dated June 28 a message on = the >>> console says >>> devmatch: Malformed NOMATCH string: '$' >>> which repeats perhaps twenty times and then goes away. >>>=20 >>> =46rom the man page it seems fairly harmless. Is this correct? =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-arm@freebsd.org Sun Jul 1 01:46:15 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C8F77FE238D for ; Sun, 1 Jul 2018 01:46:15 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x22b.google.com (mail-io0-x22b.google.com [IPv6:2607:f8b0:4001:c06::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 571E394542 for ; Sun, 1 Jul 2018 01:46:15 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x22b.google.com with SMTP id k3-v6so11773677iog.3 for ; Sat, 30 Jun 2018 18:46:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=hVlSUXC7P66enhxuee0/RCI35uJ8FtjQ+A3YkUHxS60=; b=KdHI6oNwoD9lOgFlOp73OO7H8oChxcxj9F4bHAAvwwD9PQndoCTiMhsLuYcRzAzPiH uK02PASMWqAZauXYNN8Znu+t3o1dHMI8FnN54plz3WHEPwIXSCl/pHf/qTVvkLNG1Sh/ XaJ/qvk3k3ldXYL4qx8/TMaF8XgrlRjvFBgiZBJIuxVRn5C4lldv4fn4RZjPgxJqyEcB sHhD3mvydC6zxJH6You3hJEtHhNKxvMQG3uu3m1PmXznzozVzu65Sr0oRznz8j3XF2zA pIyEV9ovpH7+RBFPY7sJ3Pyhx7EjtQiMqQ0aiNisl7H3YKnkLBDDVeCe1jBHdhrHchws 69oA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=hVlSUXC7P66enhxuee0/RCI35uJ8FtjQ+A3YkUHxS60=; b=Uwtd9bAkB9JwJqwthtU1b5SqlO6DdEHvra/viSNEZl3qTUC/hYBuaOQMto2CxbYbrb PCGxsMksCvxFX3wzqY3btKo/KtPUOgj8AfFzY+b8myuD0Enwvx5zE1y5oqkHVFEW8WUI 6CHTQFjOqr+ef2QKxq0se7xFzLES2ccyQWoGobwbgX0z8tIVUC6/rJlwkXWl+yDeb5wK NMbTbgUSD5fTF+dE2b7xbtf50IEmz7MklXoTe3myZyNt4jEzrefEgDGFLsBdOtIhN0bs HfWmYdqLJ/GT0s5Pn9b/CnP5N466LHUwpqjr8VANc608AQ2sFrwhuCkgVvCjS9N8sCVy VgJQ== X-Gm-Message-State: APt69E3rFiVbzoorFqiJ+z6YqI6DuO3Ez9YTTF3TO6cIQOVGOPn45yF+ 1Ed4fxcEwFy1DswhxfvclEIhmiGq4OoW1LgUBUZ7xevy X-Google-Smtp-Source: AAOMgpe4i6tz8WmJUfFv2v6mCOHp4ZUkvmT/LQCq0raYofql+Avlx/6X2gDABlLiMTwK4SAse5MYcAlsD3CLsYgI/s0= X-Received: by 2002:a6b:d40c:: with SMTP id l12-v6mr3996499iog.37.1530409574510; Sat, 30 Jun 2018 18:46:14 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 2002:a4f:5945:0:0:0:0:0 with HTTP; Sat, 30 Jun 2018 18:46:13 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: References: <20180630221821.GA47792@www.zefox.net> <20180630232102.GB47792@www.zefox.net> From: Warner Losh Date: Sat, 30 Jun 2018 19:46:13 -0600 X-Google-Sender-Auth: wJeeENqTHWRQvoxVQz6PFZiC31E Message-ID: Subject: Re: devmatch: Malformed NOMATCH string: '$' To: Mark Millard Cc: bob prohaska , "freebsd-arm@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jul 2018 01:46:16 -0000 On Sat, Jun 30, 2018 at 6:32 PM, Mark Millard wrote: > > > On 2018-Jun-30, at 4:21 PM, bob prohaska wrote: > > > On Sat, Jun 30, 2018 at 05:07:06PM -0600, Warner Losh wrote: > >> See UPDATING. I fixed this. > >> > > I'm halfway between chicken and egg at the moment and can't look yet. > > Will it keep until I can checkout a source tree? There may be quite > > a few reboots in the meantime. > > > > . . . > > I think Warner L. was referring to ( I looked at UPDATING > from head -r335812 but this entry is older ): > > 20180530: > The kernel / userland interface for devinfo changed, so you'll > need a new kernel and userland as a pair for it to work (rebuilding > lib/libdevinfo is all that's required). devinfo and devmatch will > not work, but everything else will when there's a mismatch. > > If I understand right, having devinfo and devmatch not working is > not necessarily a status of being fundamentally broken overall. > (Just less automatic?) But I've never had to deal with the messages. > No, I was referring to... Hmmm, doesn't seem to have been committed. 20180628: r335753 introduced a new quoting method. However, etc/devd/devmatch.conf needed to be changed to work with it. This change was made with r335763 and requires a mergemaster / etcupdate / etc to update the installed file. Just pushed it. sorry for the confusion. Warner > > . . . > >> > >> On Sat, Jun 30, 2018 at 4:18 PM, bob prohaska > wrote: > >> > >>> In booting up a new snapshot for the rpi3 dated June 28 a message on > the > >>> console says > >>> devmatch: Malformed NOMATCH string: '$' > >>> which repeats perhaps twenty times and then goes away. > >>> > >>> From the man page it seems fairly harmless. Is this correct? > > > === > Mark Millard > marklmi at yahoo.com > ( dsl-only.net went > away in early 2018-Mar) > > From owner-freebsd-arm@freebsd.org Sun Jul 1 02:53:42 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 77F25FE4C3E for ; Sun, 1 Jul 2018 02:53:42 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (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 C73449686B for ; Sun, 1 Jul 2018 02:53:41 +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 w612rtZP049371 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 30 Jun 2018 19:53:56 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w612rtFM049370; Sat, 30 Jun 2018 19:53:55 -0700 (PDT) (envelope-from fbsd) Date: Sat, 30 Jun 2018 19:53:54 -0700 From: bob prohaska To: Trev Cc: freebsd-arm@freebsd.org, bob prohaska Subject: Re: RPI3 swap experiments Message-ID: <20180701025354.GA49303@www.zefox.net> References: <20180627054027.GA22144@www.zefox.net> <20180627194217.GA27793@www.zefox.net> <20180628022457.GA30110@www.zefox.net> <7B9D272D-3EDE-46FA-8A1C-AEE65047167C@yahoo.com> <20180628163328.GA33408@www.zefox.net> <51e208b4-9f14-58f7-1e70-6ef8db2c0bed@sentry.org> <20180629155131.GA35717@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jul 2018 02:53:42 -0000 On Sun, Jul 01, 2018 at 09:42:15AM +1000, Trev wrote: > bob prohaska wrote on 30/06/2018 01:51: > > On Fri, Jun 29, 2018 at 10:28:25PM +1000, Trev wrote: > >> > >> Jun 29 20:20:35 rpi3 kernel: pid 66844 (c++), uid 0, was killed: out of > >> swap space > >> > >> At the time of "out of swap" only 157M of the 4G swap was in use. The > >> 4GB swap partition is on a 4GB USB2 memory key (da1p1), everything else > >> is on the sdcard. There are no excessively long ms/w being recorded. > >> There are no USB or other related errors. > >> > > > > That's a little surprising, and disturbing. By my experience your setup > > should have run to completion. > > > > Do you see a "too much swap" complaint? I don't know if it's a problem, > > but 4 GB of swap triggers one on my RPi3. 3 GB does not. 2 GB is enough > > to finish -j4 buildworld. > > Jun 30 23:32:12 rpi3 kernel: pid 60735 (c++), uid 0, was killed: out of > swap space > > No go with 2GB (I deleted the da0p1 swap partition; destroyed da0; then > remade it it with a 2GB p1; then rebooted - no "too much swap" > complaints). Out of swap with 56M of 2GB used. And this was with make > -j2 buildworld. > It just crossed my mind that the successful -j4 buildworlds that used USB swap (both mechanical and flash) separate from /usr and /var placed the swap on a powered USB hub. It would be exceeding strange if that proved helpful, but as things are going.... The other successful -j4 buildworlds put swap on the root microSD card. I'd rate that a harder experiment, even if there is free space on the card. My talents with gpart leave much to be desired. If you're properly gifted it might also be worth trying. > Here's the top and gstat stats leading up to, at the time of out of swap > and just after: > > last pid: 61290; load averages: 2.42, 2.27, 2.19 up 0+12:23:41 > 23:32:07 > 33 processes: 2 running, 31 sleeping > > Mem: 609M Active, 296K Inact, 95M Laundry, 176M Wired, 97M Buf, 20M Free > Swap: 2048M Total, 47M Used, 2001M Free, 2% Inuse > 0 0 0 0 0.0 0 0 0.0 0.0 mmcsd0s2a > 4 68 0 0 0.0 68 1487 20.9 36.7 da0p1 > > last pid: 61294; load averages: 2.42, 2.27, 2.19 up 0+12:23:42 > 23:32:08 > 33 processes: 2 running, 31 sleeping > > Mem: 612M Active, 180K Inact, 94M Laundry, 176M Wired, 97M Buf, 19M Free > Swap: 2048M Total, 49M Used, 1999M Free, 2% Inuse > 0 0 0 0 0.0 0 0 0.0 0.0 mmcsd0s2a > 4 110 0 0 0.0 110 3653 24.3 77.8 da0p1 > > last pid: 61298; load averages: 2.42, 2.27, 2.19 up 0+12:23:43 > 23:32:09 > 33 processes: 2 running, 31 sleeping > > Mem: 614M Active, 248K Inact, 90M Laundry, 176M Wired, 97M Buf, 20M Free > Swap: 2048M Total, 53M Used, 1995M Free, 2% Inuse > 0 0 0 0 0.0 0 0 0.0 0.0 mmcsd0s2a > 0 28 0 0 0.0 28 2737 157.7 113.7 da0p1 > > last pid: 61302; load averages: 2.42, 2.27, 2.19 up 0+12:23:45 > 23:32:11 > 33 processes: 2 running, 31 sleeping > > Mem: 322M Active, 297M Inact, 88M Laundry, 176M Wired, 97M Buf, 17M Free > Swap: 2048M Total, 55M Used, 1993M Free, 2% Inuse > 0 0 0 0 0.0 0 0 0.0 0.0 mmcsd0s2a > 5 0 0 0 0.0 0 0 0.0 0.0 da0p1 > > last pid: 61306; load averages: 2.42, 2.27, 2.19 up 0+12:23:46 > 23:32:12 > 33 processes: 1 running, 32 sleeping > > Mem: 326M Active, 164K Inact, 379M Laundry, 176M Wired, 97M Buf, 19M Free > Swap: 2048M Total, 56M Used, 1992M Free, 2% Inuse > 0 0 0 0 0.0 0 0 0.0 0.0 mmcsd0s2a > 6 0 0 0 0.0 0 0 0.0 0.0 da0p1 > > last pid: 61310; load averages: 2.39, 2.27, 2.19 up 0+12:23:47 > 23:32:13 > 33 processes: 1 running, 32 sleeping > > Mem: 331M Active, 184K Inact, 379M Laundry, 176M Wired, 97M Buf, 14M Free > Swap: 2048M Total, 56M Used, 1992M Free, 2% Inuse > 0 0 0 0 0.0 0 0 0.0 0.0 mmcsd0s2a > 6 0 0 0 0.0 0 0 0.0 0.0 da0p1 > > [OUT OF SWAP at 23:32:14 captured immediately below] > > last pid: 61315; load averages: 2.39, 2.27, 2.19 up 0+12:23:48 > 23:32:14 > 33 processes: 1 running, 32 sleeping > > Mem: 78M Active, 176K Inact, 315M Laundry, 174M Wired, 97M Buf, 332M Free > Swap: 2048M Total, 56M Used, 1992M Free, 2% Inuse > 0 0 0 0 0.0 0 0 0.0 0.0 mmcsd0s2a > 0 48 37 710 126.2 11 1186 341.9 26.4 da0p1 > > last pid: 61320; load averages: 2.39, 2.27, 2.19 up 0+12:23:49 > 23:32:15 > 33 processes: 2 running, 31 sleeping > > Mem: 55M Active, 848K Inact, 1644K Laundry, 174M Wired, 97M Buf, 669M Free > Swap: 2048M Total, 48M Used, 2000M Free, 2% Inuse > 0 0 0 0 0.0 0 0 0.0 0.0 mmcsd0s2a > 0 0 0 0 0.0 0 0 0.0 0.0 da0p1 The delays look much better than I've seen on successful -j4 buildworlds. From owner-freebsd-arm@freebsd.org Sun Jul 1 07:12:30 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6B47C1037737 for ; Sun, 1 Jul 2018 07:12:30 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic315-10.consmr.mail.gq1.yahoo.com (sonic315-10.consmr.mail.gq1.yahoo.com [98.137.65.34]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E2D2C833ED for ; Sun, 1 Jul 2018 07:12:29 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: an3blREVM1lSHi3K.y8_jgDOoQ00o25LByJ.KlphWIITdPcdZR3KFg_SIZHGddf aDBCZZr.CoJd2MXebOj4gxYc5os.WOAm0Z4WIxEyn08kGJrzmpy1N_gXv3lYjtg8jMctLzXJVBdy mkW7y.fB52b5nO1z1P8wXy7H2B_3fEI6aTq_cK1VT41AuetqQrknb7O5W7HdJTbT2vQAKu0VA9iz 2zCEqaFeFK5HN1SV.b.qdn8zAOZ3JJgEzUkn.xNJ1XL3_kBHCoac5qZkoGdt6WWiwbz24yuOU_en Sp6Z0NqLjPnuiVUQJa7gVqFdNQfNi0D5z_o7EhDmIMeeNdEkFmQi6w8LQ3WPSDtdr8YfmpqR7HNL S7Kkq_NUXDyNH9wndNraDbNJbe5fyUENV0R_4mUdQ4Mgfa5EwnmbtpX8hhdAT6SP6S2sKNve7i2h OIxTlNmdjswlfoEoAgg7nMl_uXXLSzlZQp3E8oEKzHBXcyFKHB5Yc8cHH6NJ5KMfxAKFSKjmRbpI k1P0yH6QwQx1ML4FSkIvYm0cm6M8PytRZ5Wxe3Q26TStZMBR35178LFLTTS9A_WtMkeKK1PFknu7 6VgnwQu8asUJnI9PmtNSa4oyJkOslgC_gsTjx4JliDdiYGtdYlo95NmbvXnPcO1_NR44ESjnodWA gDfn9jKuQXmKYS1hiCWY5ZaKisjrK7Dc6y9nRTIckf2DT6nktBjdkFOVRttgENIecU_F5uMRZR3C EUSc2IggzJI3HJQtd9ZD_XhVET.TRUsC06Q.Jj2p9J3ccQQWwPVOBvAZmET6YUx.lDGOYpped.3n GgheAJ98OyemyNL84ZzcrU4MDT2He_U4PbLzcEBtJteKtVyjHRuJfh37n2.zp.U7Dfc97r.1pcMy al_FDGj_4fjcFcgR._E3UB0k3ukjf3Ni42WeV9QRV14w4kXUI12i467UW_JhyT8rzDijo0hMhJsF c9a8FCgrkDckdrxnCiK9YnaSb_pBj7HE- Received: from sonic.gate.mail.ne1.yahoo.com by sonic315.consmr.mail.gq1.yahoo.com with HTTP; Sun, 1 Jul 2018 07:12:28 +0000 Received: from ip70-189-131-151.lv.lv.cox.net (EHLO [192.168.0.105]) ([70.189.131.151]) by smtp407.mail.gq1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 2ab294b36eedae912c556efcde594b8a; Sun, 01 Jul 2018 06:42:01 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\)) Subject: Re: RPI3 swap experiments From: Mark Millard In-Reply-To: <20180701025354.GA49303@www.zefox.net> Date: Sat, 30 Jun 2018 23:42:00 -0700 Cc: Trev , freebsd-arm@freebsd.org Content-Transfer-Encoding: 7bit Message-Id: <5202FC09-B76A-4E03-BC2F-8144B505E0BA@yahoo.com> References: <20180627054027.GA22144@www.zefox.net> <20180627194217.GA27793@www.zefox.net> <20180628022457.GA30110@www.zefox.net> <7B9D272D-3EDE-46FA-8A1C-AEE65047167C@yahoo.com> <20180628163328.GA33408@www.zefox.net> <51e208b4-9f14-58f7-1e70-6ef8db2c0bed@sentry.org> <20180629155131.GA35717@www.zefox.net> <20180701025354.GA49303@www.zefox.net> To: bob prohaska X-Mailer: Apple Mail (2.3445.8.2) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jul 2018 07:12:30 -0000 On 2018-Jun-30, at 7:53 PM, bob prohaska wrote: > On Sun, Jul 01, 2018 at 09:42:15AM +1000, Trev wrote: >> bob prohaska wrote on 30/06/2018 01:51: >>> On Fri, Jun 29, 2018 at 10:28:25PM +1000, Trev wrote: >>>> >>>> Jun 29 20:20:35 rpi3 kernel: pid 66844 (c++), uid 0, was killed: out of >>>> swap space >>>> >>>> At the time of "out of swap" only 157M of the 4G swap was in use. The >>>> 4GB swap partition is on a 4GB USB2 memory key (da1p1), everything else >>>> is on the sdcard. There are no excessively long ms/w being recorded. >>>> There are no USB or other related errors. >>>> >>> >>> That's a little surprising, and disturbing. By my experience your setup >>> should have run to completion. >>> >>> Do you see a "too much swap" complaint? I don't know if it's a problem, >>> but 4 GB of swap triggers one on my RPi3. 3 GB does not. 2 GB is enough >>> to finish -j4 buildworld. >> >> Jun 30 23:32:12 rpi3 kernel: pid 60735 (c++), uid 0, was killed: out of >> swap space >> >> No go with 2GB (I deleted the da0p1 swap partition; destroyed da0; then >> remade it it with a 2GB p1; then rebooted - no "too much swap" >> complaints). Out of swap with 56M of 2GB used. And this was with make >> -j2 buildworld. >> > It just crossed my mind that the successful -j4 buildworlds that used > USB swap (both mechanical and flash) separate from /usr and /var placed > the swap on a powered USB hub. It would be exceeding strange if that > proved helpful, but as things are going.... Power issues have been mentioned before in this exchange, but it can be more like what one might notice with a oscilloscope than with a Digital Multi-Meter. If the device sometimes (even very briefly) requires more than the rpi3 provides (voltage or current) the device will likely fail sometimes despite a DMM not showing anything interesting. The same device might work fine on a powered hub that always provides sufficient voltage and current (on all time scales involved). I've had these sorts of situations before. Without a proper set of instruments to monitor for power problems with, it is a pain to figure out for sure if such is what is going on. So I tend to use a powered hub for USB storage. > The other successful -j4 buildworlds put swap on the root microSD card. > I'd rate that a harder experiment, even if there is free space on the card. > My talents with gpart leave much to be desired. If you're properly gifted > it might also be worth trying. > > . . . === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-arm@freebsd.org Sun Jul 1 11:31:44 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 77014FF4180 for ; Sun, 1 Jul 2018 11:31:44 +0000 (UTC) (envelope-from freebsd-arm@sentry.org) Received: from shadow.sentry.org (shadow.sentry.org [210.8.237.106]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "shadow.sentry.org", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AF3EB8C7F9 for ; Sun, 1 Jul 2018 11:31:43 +0000 (UTC) (envelope-from freebsd-arm@sentry.org) Received: from shadow.sentry.org (localhost [127.0.0.1]) by shadow.sentry.org (8.15.2/8.15.2) with ESMTP id w61BVd7n062835 for ; Sun, 1 Jul 2018 21:31:39 +1000 (AEST) (envelope-from freebsd-arm@sentry.org) Subject: Re: RPI3 swap experiments To: freebsd-arm@freebsd.org References: <20180627054027.GA22144@www.zefox.net> <20180627194217.GA27793@www.zefox.net> <20180628022457.GA30110@www.zefox.net> <7B9D272D-3EDE-46FA-8A1C-AEE65047167C@yahoo.com> <20180628163328.GA33408@www.zefox.net> <51e208b4-9f14-58f7-1e70-6ef8db2c0bed@sentry.org> <20180629155131.GA35717@www.zefox.net> <20180701025354.GA49303@www.zefox.net> <5202FC09-B76A-4E03-BC2F-8144B505E0BA@yahoo.com> From: Trev Message-ID: <8d9e3204-4975-435e-04eb-0fdecfbdcb6c@sentry.org> Date: Sun, 1 Jul 2018 21:31:39 +1000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.3 MIME-Version: 1.0 In-Reply-To: <5202FC09-B76A-4E03-BC2F-8144B505E0BA@yahoo.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.2 (shadow.sentry.org [0.0.0.0]); Sun, 01 Jul 2018 21:31:39 +1000 (AEST) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jul 2018 11:31:44 -0000 > Mark Millard wrote on 01/07/2018 16:42: > > On 2018-Jun-30, at 7:53 PM, bob prohaska wrote: [...] >> It just crossed my mind that the successful -j4 buildworlds that used >> USB swap (both mechanical and flash) separate from /usr and /var placed >> the swap on a powered USB hub. It would be exceeding strange if that >> proved helpful, but as things are going.... > Power issues have been mentioned before in this exchange, but it can be > more like what one might notice with a oscilloscope than with a Digital > Multi-Meter. If the device sometimes (even very briefly) requires more > than the rpi3 provides (voltage or current) the device will likely > fail sometimes despite a DMM not showing anything interesting. The > same device might work fine on a powered hub that always provides > sufficient voltage and current (on all time scales involved). > > I've had these sorts of situations before. Without a proper set of > instruments to monitor for power problems with, it is a pain to > figure out for sure if such is what is going on. > > So I tend to use a powered hub for USB storage. My RPi2B is connected to a pocket router via ethernet and USB for power, and thence wirelessly to the wifi router at the fibre NTD. The pocket router kept getting corrupted settings and losing connectivity. So I replaced it. Same thing with the new one. I finally figured out that it was a USB power issue - adding `max_usb_current=1` in the config.txt file to double the current from 600mA to 1.2A fixed it. I hadn't considered power to be an issue for the RPi3B+ - it has a 3A PSU (limited to 2.5A by the RPi's polyfuse) and does not need the config.txt tweak as it already supplies up to 1.2A by default according to an RPi Engineer: https://www.raspberrypi.org/forums/viewtopic.php?p=930695#p930695 Admittedly, I haven't been watching when "out of swap" occurs to see if the red power LED goes out momentarily. However, since replacing the 2.5A PSU with the 3A one I've not seen any red LED fade outs which used to randomly occur with the 2.5A PSU. I'm currently -j4 compiling with an external USB hard drive connected to a powered hub, so when that finishes, I'll add the USB memory key for swap to the hub and see if it makes a difference. From owner-freebsd-arm@freebsd.org Sun Jul 1 12:14:19 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3DAE8FF577B for ; Sun, 1 Jul 2018 12:14:19 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CB5F68DE04 for ; Sun, 1 Jul 2018 12:14:18 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smtp.greenhost.nl ([213.108.110.112]) by smarthost1.greenhost.nl with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from ) id 1fZbF5-00070q-C6 for freebsd-arm@freebsd.org; Sun, 01 Jul 2018 14:14:11 +0200 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: freebsd-arm@freebsd.org Date: Sun, 01 Jul 2018 14:14:11 +0200 Subject: RPI3B+ does not reboot MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Ronald Klop" Message-ID: User-Agent: Opera Mail/12.16 (FreeBSD) X-Authenticated-As-Hash: 398f5522cb258ce43cb679602f8cfe8b62a256d1 X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: / X-Spam-Score: -0.2 X-Spam-Status: No, score=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50 autolearn=disabled version=3.4.0 X-Scan-Signature: c74461a82029b6293650421ecb57b64a X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jul 2018 12:14:19 -0000 Hello, My RPI3B+ does not reboot if I run GENERIC-NODEBUG. It works properly on a GENERIC kernel. # uname -a FreeBSD rpi3 12.0-CURRENT FreeBSD 12.0-CURRENT #2 r335679: Thu Jun 28 02:33:01 CEST 2018 builder@rpi3:/mnt/ssd/data/src/obj-head/mnt/ssd/data/src/head/arm64.aarch64/sys/GENERIC-NODEBUG arm64 The output ends with: All buffers synced. Uptime: 1d1h28m21s Rebooting... And then it does not do anything and I have to do a power off/on cycle. Any thoughts about this? I have a serial cable connected so I can run some debugging commands if necessary. Regards, Ronald. From owner-freebsd-arm@freebsd.org Sun Jul 1 12:31:23 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 661DBFF5F18 for ; Sun, 1 Jul 2018 12:31:23 +0000 (UTC) (envelope-from trev@sentry.org) Received: from shadow.sentry.org (shadow.sentry.org [210.8.237.106]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "shadow.sentry.org", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 957C28E6D8 for ; Sun, 1 Jul 2018 12:31:22 +0000 (UTC) (envelope-from trev@sentry.org) Received: from shadow.sentry.org (localhost [127.0.0.1]) by shadow.sentry.org (8.15.2/8.15.2) with ESMTP id w61CVI97069317 for ; Sun, 1 Jul 2018 22:31:18 +1000 (AEST) (envelope-from trev@sentry.org) Subject: Re: RPI3B+ does not reboot To: freebsd-arm@freebsd.org References: From: Trevor Roydhouse Organization: Sentry Message-ID: <2d463b29-5af1-4122-08d9-a38c0f03c447@sentry.org> Date: Sun, 1 Jul 2018 22:31:18 +1000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.3 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.2 (shadow.sentry.org [0.0.0.0]); Sun, 01 Jul 2018 22:31:18 +1000 (AEST) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jul 2018 12:31:23 -0000 Ronald Klop wrote on 01/07/2018 22:14: > Hello, > > My RPI3B+ does not reboot if I run GENERIC-NODEBUG. It works properly on > a GENERIC kernel. > > # uname -a > FreeBSD rpi3 12.0-CURRENT FreeBSD 12.0-CURRENT #2 r335679: Thu Jun 28 > 02:33:01 CEST 2018 > builder@rpi3:/mnt/ssd/data/src/obj-head/mnt/ssd/data/src/head/arm64.aarch64/sys/GENERIC-NODEBUG > arm64 > > The output ends with: > All buffers synced. > Uptime: 1d1h28m21s > Rebooting... > > > And then it does not do anything and I have to do a power off/on cycle. My RPi3B+ running with the default GENERIC kernel intermittently fails to reboot with "reboot" but when it does, it outputs "CPU reset failed" over the serial connection. I don't think I've noticed the failure with "shutdown -r now". FreeBSD rpi3.sentry.org 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r335317: Mon Jun 18 17:37:04 UTC 2018 root@releng3.nyi.freebsd.org:/usr/obj/usr/src/arm64.aarch64/sys/GENERIC arm64 From owner-freebsd-arm@freebsd.org Sun Jul 1 15:08:23 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 42BF5FF8FC4 for ; Sun, 1 Jul 2018 15:08:23 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (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 CD83E72898 for ; Sun, 1 Jul 2018 15:08:22 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id w61F8ISg028541; Sun, 1 Jul 2018 08:08:18 -0700 (PDT) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd-rwg@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id w61F8HM5028540; Sun, 1 Jul 2018 08:08:17 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201807011508.w61F8HM5028540@pdx.rh.CN85.dnsmgr.net> Subject: Re: RPI3 swap experiments In-Reply-To: <8d9e3204-4975-435e-04eb-0fdecfbdcb6c@sentry.org> To: Trev Date: Sun, 1 Jul 2018 08:08:17 -0700 (PDT) CC: freebsd-arm@freebsd.org X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jul 2018 15:08:23 -0000 > > Mark Millard wrote on 01/07/2018 16:42: > > > On 2018-Jun-30, at 7:53 PM, bob prohaska wrote: > [...] > >> It just crossed my mind that the successful -j4 buildworlds that used > >> USB swap (both mechanical and flash) separate from /usr and /var placed > >> the swap on a powered USB hub. It would be exceeding strange if that > >> proved helpful, but as things are going.... > > > Power issues have been mentioned before in this exchange, but it can be > > more like what one might notice with a oscilloscope than with a Digital > > Multi-Meter. If the device sometimes (even very briefly) requires more > > than the rpi3 provides (voltage or current) the device will likely > > fail sometimes despite a DMM not showing anything interesting. The > > same device might work fine on a powered hub that always provides > > sufficient voltage and current (on all time scales involved). > > > > I've had these sorts of situations before. Without a proper set of > > instruments to monitor for power problems with, it is a pain to > > figure out for sure if such is what is going on. > > > > So I tend to use a powered hub for USB storage. > > My RPi2B is connected to a pocket router via ethernet and USB for power, > and thence wirelessly to the wifi router at the fibre NTD. The pocket > router kept getting corrupted settings and losing connectivity. So I > replaced it. Same thing with the new one. I finally figured out that it > was a USB power issue - adding `max_usb_current=1` in the config.txt > file to double the current from 600mA to 1.2A fixed it. > > I hadn't considered power to be an issue for the RPi3B+ - it has a 3A > PSU (limited to 2.5A by the RPi's polyfuse) and does not need the The polyfuse is fast acting (ms to 10's of ms) when at 200 to 300% overload, typical acting time at labeled value is 4 hours, and at 20% overload (3A for a 2.5A device) is going to be between those values. Your power draw is not a nice flat line but fairly noisy and spikey, the pulse current allowed through a 2.5A polyfuse without tripping it is fairly significant so you are actually probably getting a good deal of that 3A's used. The RPI3 is known to be marginally at 2.5A if you use any power drawing USB devices plugged into the ports. > config.txt tweak as it already supplies up to 1.2A by default according > to an RPi Engineer: > https://www.raspberrypi.org/forums/viewtopic.php?p=930695#p930695 Well though the ports might be able to provide 1.2A, doing so would only leave 1.3A of power to run the board itself from a 2.5A supply and I really doubt that your gona run a buildworld -j4 on anything much less than 2A in use by the CPU and memory chips. > > Admittedly, I haven't been watching when "out of swap" occurs to see if > the red power LED goes out momentarily. However, since replacing the > 2.5A PSU with the 3A one I've not seen any red LED fade outs which used > to randomly occur with the 2.5A PSU. You can not see the noise on power signals with a LED, you need significant and somewhat elaborate test instrumentation, at a minimum a 100MHz, preferably faster, oscilliscope is needed. > > I'm currently -j4 compiling with an external USB hard drive connected to > a powered hub, so when that finishes, I'll add the USB memory key for > swap to the hub and see if it makes a difference. I would not even attempt to use more than one USB storage on a RPI3 without a powered hub, and if a powered hub was avaliable I would put all the storage behind that hub. Noisy power is a nightmare to trouble shoot without proper equipment. -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-arm@freebsd.org Sun Jul 1 19:25:48 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E03E3FD4F8E for ; Sun, 1 Jul 2018 19:25:48 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (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 57EEA7A653 for ; Sun, 1 Jul 2018 19:25:47 +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 w61JQ2sn052729 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 1 Jul 2018 12:26:03 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w61JQ24N052728; Sun, 1 Jul 2018 12:26:02 -0700 (PDT) (envelope-from fbsd) Date: Sun, 1 Jul 2018 12:26:01 -0700 From: bob prohaska To: Trevor Roydhouse Cc: freebsd-arm@freebsd.org, bob prohaska Subject: Re: RPI3B+ does not reboot Message-ID: <20180701192601.GB52656@www.zefox.net> References: <2d463b29-5af1-4122-08d9-a38c0f03c447@sentry.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2d463b29-5af1-4122-08d9-a38c0f03c447@sentry.org> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jul 2018 19:25:49 -0000 On Sun, Jul 01, 2018 at 10:31:18PM +1000, Trevor Roydhouse wrote: > My RPi3B+ running with the default GENERIC kernel intermittently fails > to reboot with "reboot" but when it does, it outputs "CPU reset failed" > over the serial connection. I don't think I've noticed the failure with > "shutdown -r now". > I saw a "reset failed" once, I think it was after shutdown -r now, invoked from single-user on the June 28 snapshot. So far it's hasn't returned in ~5 reboots. bob prohaska From owner-freebsd-arm@freebsd.org Sun Jul 1 19:45:25 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0985CFD560A for ; Sun, 1 Jul 2018 19:45:25 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (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 660FE7AFE5 for ; Sun, 1 Jul 2018 19:45:24 +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 w61JHfVe052702 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 1 Jul 2018 12:17:42 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w61JHfoJ052701; Sun, 1 Jul 2018 12:17:41 -0700 (PDT) (envelope-from fbsd) Date: Sun, 1 Jul 2018 12:17:41 -0700 From: bob prohaska To: Mark Millard Cc: Trev , freebsd-arm@freebsd.org, bob prohaska Subject: Re: RPI3 swap experiments Message-ID: <20180701191741.GA52656@www.zefox.net> References: <20180627194217.GA27793@www.zefox.net> <20180628022457.GA30110@www.zefox.net> <7B9D272D-3EDE-46FA-8A1C-AEE65047167C@yahoo.com> <20180628163328.GA33408@www.zefox.net> <51e208b4-9f14-58f7-1e70-6ef8db2c0bed@sentry.org> <20180629155131.GA35717@www.zefox.net> <20180701025354.GA49303@www.zefox.net> <5202FC09-B76A-4E03-BC2F-8144B505E0BA@yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5202FC09-B76A-4E03-BC2F-8144B505E0BA@yahoo.com> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jul 2018 19:45:25 -0000 On Sat, Jun 30, 2018 at 11:42:00PM -0700, Mark Millard wrote: > > > So I tend to use a powered hub for USB storage. > It occurs to me that a powered hub provides more than power: It provides delay. Likely not much, but a flash device has none of the rotational or seek delay of a mechanical drive. At least occasionally, a flash device might respond quicker than any plausible mechanical one. If the host isn't ready, it'd miss the response. Most "disk" driver software was written in the days of mechanical disks, is it possible assumptions about minimum response delay were made? There's doubtless a "re-training" scheme to get host and device back in sync, but if the timings remain wrong that would prolong the confusion. Thanks for reading, bob prohaska From owner-freebsd-arm@freebsd.org Sun Jul 1 20:11:45 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7B57AFDA5EC for ; Sun, 1 Jul 2018 20:11:45 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (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 E4B337C1E0 for ; Sun, 1 Jul 2018 20:11:44 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id w61KBZin029691; Sun, 1 Jul 2018 13:11:35 -0700 (PDT) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd-rwg@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id w61KBZka029690; Sun, 1 Jul 2018 13:11:35 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201807012011.w61KBZka029690@pdx.rh.CN85.dnsmgr.net> Subject: Re: RPI3 swap experiments In-Reply-To: <20180701191741.GA52656@www.zefox.net> To: bob prohaska Date: Sun, 1 Jul 2018 13:11:35 -0700 (PDT) CC: Mark Millard , freebsd-arm@freebsd.org X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jul 2018 20:11:45 -0000 > On Sat, Jun 30, 2018 at 11:42:00PM -0700, Mark Millard wrote: > > > > > > So I tend to use a powered hub for USB storage. > > > > It occurs to me that a powered hub provides more than power: It provides delay. > Likely not much, but a flash device has none of the rotational or seek delay > of a mechanical drive. At least occasionally, a flash device might respond > quicker than any plausible mechanical one. If the host isn't ready, it'd miss > the response. Most "disk" driver software was written in the days of mechanical > disks, is it possible assumptions about minimum response delay were made? > There's doubtless a "re-training" scheme to get host and device back in sync, > but if the timings remain wrong that would prolong the confusion. IIRC the "delay" through a usb hub, as long as your not doing transactional translation (TT, ie 480 mb/s down to a 12mb/s device) is on the order of microseconds, this is the same weither it is a powered or un powered hub. I doubt that any flash drive can respond faster than a spinning rust drive with a cache can, as the cache is DRAM with tens of nano seconds access time. Flash drives DO have an access delay, the FTL still has to do the mapping funcions, and a page of flash has to be pulled into a read buffer. I actually believe that even the fastest USB flash drives are still slower than any modern spinning rust at this operation. Modern cheap 500G laptop drives are doing well past 140MB/s in a sustained sequestion read operation. I have not seen USB flash sticks that do this. You need to move to SSD type drives to get faster, and it would be rather pointless to run SSD on USB unless your using USB3. -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-arm@freebsd.org Sun Jul 1 21:01:26 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 44BA1FDC09B for ; Sun, 1 Jul 2018 21:01:26 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6D6537DEF5 for ; Sun, 1 Jul 2018 21:01:25 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 8033921A76 for ; Sun, 1 Jul 2018 21:01:24 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w61L1OXu048246 for ; Sun, 1 Jul 2018 21:01:24 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w61L1ObM048233 for freebsd-arm@FreeBSD.org; Sun, 1 Jul 2018 21:01:24 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201807012101.w61L1ObM048233@kenobi.freebsd.org> X-Authentication-Warning: kenobi.freebsd.org: bugzilla set sender to bugzilla-noreply@FreeBSD.org using -f From: bugzilla-noreply@FreeBSD.org To: freebsd-arm@FreeBSD.org Subject: Problem reports for freebsd-arm@FreeBSD.org that need special attention Date: Sun, 1 Jul 2018 21:01:24 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jul 2018 21:01:26 -0000 To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- New | 220297 | arch(7) rename arm64 to aarch64 respecting `uname 1 problems total for which you should take action. From owner-freebsd-arm@freebsd.org Sun Jul 1 21:17:20 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6ED2CFDD25F for ; Sun, 1 Jul 2018 21:17:20 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (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 D37C17F3FB for ; Sun, 1 Jul 2018 21:17:19 +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 w61LHXxP052986 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 1 Jul 2018 14:17:34 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w61LHXlx052985; Sun, 1 Jul 2018 14:17:33 -0700 (PDT) (envelope-from fbsd) Date: Sun, 1 Jul 2018 14:17:33 -0700 From: bob prohaska To: "Rodney W. Grimes" Cc: Mark Millard , freebsd-arm@freebsd.org, bob prohaska Subject: Re: RPI3 swap experiments Message-ID: <20180701211733.GC52656@www.zefox.net> References: <20180701191741.GA52656@www.zefox.net> <201807012011.w61KBZka029690@pdx.rh.CN85.dnsmgr.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201807012011.w61KBZka029690@pdx.rh.CN85.dnsmgr.net> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jul 2018 21:17:20 -0000 On Sun, Jul 01, 2018 at 01:11:35PM -0700, Rodney W. Grimes wrote: > > IIRC the "delay" through a usb hub, as long as your not doing transactional > translation (TT, ie 480 mb/s down to a 12mb/s device) is on the order of > microseconds, this is the same weither it is a powered or un powered hub. > > I doubt that any flash drive can respond faster than a spinning rust > drive with a cache can, as the cache is DRAM with tens of nano seconds > access time. > > Flash drives DO have an access delay, the FTL still has to do the mapping > funcions, and a page of flash has to be pulled into a read buffer. I > actually believe that even the fastest USB flash drives are still > slower than any modern spinning rust at this operation. > There is a sorted list of gstat output from one of my tests at http://www.zefox.net/~fbsd/rpi3/swaptests/3gbusbflash/readdelay.sort The first few lines suggest that microSD responds in less than a millisecond, direct-connected USB flash requires 1.2 milliseconds and hub-connected USB flash takes 1.6 milliseconds. I'm not sure how representative these numbers are, the -u option was used in sort. There's a similar list for a mechanical drive at http://www.zefox.net/~fbsd/rpi3/swaptests/newtests/1.3gbusbmechanical_swapinfo/readdelay.sort where the minimum delay is 6.4 milliseconds. It's tempting to think that at least occasionally flash storage beats mechanical storage. The mechanical drive I used is an old 2.5" salvaged from a Dell compact desktop computer, stuffed into a USB enclosure, so it surely isn't the fastest in the world. Thanks for reading! bob prohaska From owner-freebsd-arm@freebsd.org Mon Jul 2 07:26:56 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 94411FE19CE for ; Mon, 2 Jul 2018 07:26:56 +0000 (UTC) (envelope-from jamie@catflap.org) Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [IPv6:2001:19f0:300:2185:a:dead:bad:faff]) (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 6504777965 for ; Mon, 2 Jul 2018 07:26:56 +0000 (UTC) (envelope-from jamie@catflap.org) Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [104.207.135.49]) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5) with ESMTP id w627QrOl071362; Mon, 2 Jul 2018 08:26:53 +0100 (BST) (envelope-from jamie@donotpassgo.dyslexicfish.net) Received: (from jamie@localhost) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5/Submit) id w627QqsL071353; Mon, 2 Jul 2018 08:26:52 +0100 (BST) (envelope-from jamie) From: Jamie Landeg-Jones Message-Id: <201807020726.w627QqsL071353@donotpassgo.dyslexicfish.net> Date: Mon, 02 Jul 2018 08:26:51 +0100 Organization: Dyslexic Fish To: marklmi@yahoo.com, jamie@catflap.org, fbsd@www.zefox.net Cc: imp@bsdimp.com, freebsd-arm@freebsd.org Subject: Re: RPI3 swap experiments, was Re: GPT vs MBR for swap devices References: <25F1A4BA-FBFC-4C32-85DD-5F5BA71A2B1A@yahoo.com> <20180620023253.GA89924@www.zefox.net> <1D86911D-20D1-494A-822B-1C07C5598CB1@yahoo.com> <10CAC122-399D-459E-9153-ABD7E753777E@yahoo.com> <20180623143218.GA6905@www.zefox.net> <03C2D3C4-6E90-4054-AF79-BD7FE2B7958D@yahoo.com> <20180624231020.GA11132@www.zefox.net> <20180626052451.GA17293@www.zefox.net> <201806261040.w5QAeBKq035183@donotpassgo.dyslexicfish.net> In-Reply-To: User-Agent: Heirloom mailx 12.4 7/29/08 MIME-Version: 1.0 Content-Type: application/octet-stream Content-Transfer-Encoding: base64 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (donotpassgo.dyslexicfish.net [104.207.135.49]); Mon, 02 Jul 2018 08:26:53 +0100 (BST) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jul 2018 07:26:56 -0000 U29ycnkgZm9yIHRoZSBkZWxheSBpbiByZXBseWluZy4gT24gdGhlIHdlZWtlbmQsIEkgZHVn IG91dCBteSBwaSdzLCBhbmQgbm90ZXMsCmFuZCB1bmZvcnR1bmF0ZWx5IEkgd2FzIG1pc3Rh a2VuLgoKSSBoYXZlIGEgcnBpMiBhbmQgYW4gcnBpMyB3aGljaCBJIHdhcyBzZXR0aW5nIHVw IGF0IHRoZSBzYW1lIHRpbWUgKGl0IHR1cm5zIG91dAoiYSBmZXcgbW9udGhzIGFnbyIgd2Fz IGFjdHVhbGx5IE9jdG9iZXIuCgpJdCB3YXMgdGhlIFJQSTIgdGhhdCBnYXZlIG1lIHZmcyBl cnJvcnMgdW5kZXIgbG9hZCAtIHRoZSBSUEkzIEkgY291bGRuJ3QgZ2V0CnRvIGJvb3QgYXQg YWxsLgoKVGhlIGdvb2QgbmV3LCBpcywgSSBoYXZlIGxvYWRlZCB0aGUgbGF0ZXN0IGltYWdl LApGcmVlQlNELTEyLjAtQ1VSUkVOVC1hcm02NC1hYXJjaDY0LVJQSTMtMjAxODA2MjgtcjMz NTc2MC5pbWcgYW5kIGl0IGxvYWRzIGZpbmUuCgpBcyBzdWNoIEkgaGF2ZSBhIHZpcmdpbiBS UEkzIHdpdGggbmV3IHNkY2FyZCwgYW5kIGEgbmV3IFVTQiBzdGljaywgYW5kIEknbQp3aWxs aW5nIHRvIGNvbmZpZ3VyZSBpdCBob3dldmVyIHlvdSB3YW50LCB0byBoZWxwIHRoZSB0ZXN0 aW5nLgoKV2hhdCBkbyB5b3UgdGhpbmsgd291bGQgYmUgdGhlIGJlc3QgdGhpbmdzIHRvIGRv IG5leHQ/IFRyeSBhbmQgZW11bGF0ZSBCb2JzCnByb2JsZW0sIG9yIHRyeSBzb21lIG90aGVy IHN0cmVzcyB0ZXN0cz8KCkNoZWVycywgSmFtaWUKLi4KGwo= From owner-freebsd-arm@freebsd.org Mon Jul 2 07:31:12 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A8EEDFE267C for ; Mon, 2 Jul 2018 07:31:12 +0000 (UTC) (envelope-from jamie@catflap.org) Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [IPv6:2001:19f0:300:2185:a:dead:bad:faff]) (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 5951D77E2D for ; Mon, 2 Jul 2018 07:31:12 +0000 (UTC) (envelope-from jamie@catflap.org) Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [104.207.135.49]) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5) with ESMTP id w627VA0L072407; Mon, 2 Jul 2018 08:31:11 +0100 (BST) (envelope-from jamie@donotpassgo.dyslexicfish.net) Received: (from jamie@localhost) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5/Submit) id w627VAcY072406; Mon, 2 Jul 2018 08:31:10 +0100 (BST) (envelope-from jamie) From: Jamie Landeg-Jones Message-Id: <201807020731.w627VAcY072406@donotpassgo.dyslexicfish.net> Date: Mon, 02 Jul 2018 08:31:10 +0100 Organization: Dyslexic Fish To: marklmi@yahoo.com, jamie@catflap.org, fbsd@www.zefox.net Cc: imp@bsdimp.com, freebsd-arm@freebsd.org Subject: Re: RPI3 swap experiments, was Re: GPT vs MBR for swap devices References: <25F1A4BA-FBFC-4C32-85DD-5F5BA71A2B1A@yahoo.com> <20180620023253.GA89924@www.zefox.net> <1D86911D-20D1-494A-822B-1C07C5598CB1@yahoo.com> <10CAC122-399D-459E-9153-ABD7E753777E@yahoo.com> <20180623143218.GA6905@www.zefox.net> <03C2D3C4-6E90-4054-AF79-BD7FE2B7958D@yahoo.com> <20180624231020.GA11132@www.zefox.net> <20180626052451.GA17293@www.zefox.net> <201806261040.w5QAeBKq035183@donotpassgo.dyslexicfish.net> In-Reply-To: User-Agent: Heirloom mailx 12.4 7/29/08 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (donotpassgo.dyslexicfish.net [104.207.135.49]); Mon, 02 Jul 2018 08:31:11 +0100 (BST) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jul 2018 07:31:12 -0000 Sorry for the delay in replying. On the weekend, I dug out my pi's, and notes, and unfortunately I was mistaken. I have a rpi2 and an rpi3 which I was setting up at the same time (it turns out "a few months ago" was actually October. It was the RPI2 that gave me vfs errors under load - the RPI3 I couldn't get to boot at all. The good new, is, I have loaded the latest image, FreeBSD-12.0-CURRENT-arm64-aarch64-RPI3-20180628-r335760.img and it loads fine. As such I have a virgin RPI3 with new sdcard, and a new USB stick, and I'm willing to configure it however you want, to help the testing. What do you think would be the best things to do next? Try and emulate Bobs problem, or try some other stress tests? Cheers, Jamie From owner-freebsd-arm@freebsd.org Mon Jul 2 09:22:05 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F16F1FF02ED for ; Mon, 2 Jul 2018 09:22:04 +0000 (UTC) (envelope-from freebsd-arm@sentry.org) Received: from shadow.sentry.org (shadow.sentry.org [210.8.237.106]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "shadow.sentry.org", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 252A77D30B for ; Mon, 2 Jul 2018 09:22:03 +0000 (UTC) (envelope-from freebsd-arm@sentry.org) Received: from shadow.sentry.org (localhost [127.0.0.1]) by shadow.sentry.org (8.15.2/8.15.2) with ESMTP id w629LrkE080036 for ; Mon, 2 Jul 2018 19:21:55 +1000 (AEST) (envelope-from freebsd-arm@sentry.org) Subject: Re: RPI3 swap experiments To: freebsd-arm@freebsd.org References: <20180627194217.GA27793@www.zefox.net> <20180628022457.GA30110@www.zefox.net> <7B9D272D-3EDE-46FA-8A1C-AEE65047167C@yahoo.com> <20180628163328.GA33408@www.zefox.net> <51e208b4-9f14-58f7-1e70-6ef8db2c0bed@sentry.org> <20180629155131.GA35717@www.zefox.net> <20180629233937.GC35717@www.zefox.net> <0f137e06-214a-3e8c-a216-f061ec04ac2c@sentry.org> <20180630005145.GA43801@www.zefox.net> From: Trev Message-ID: <6f3406e2-71f3-d0c2-2b65-703e1a1d3c25@sentry.org> Date: Mon, 2 Jul 2018 19:21:53 +1000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.3 MIME-Version: 1.0 In-Reply-To: <20180630005145.GA43801@www.zefox.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.2 (shadow.sentry.org [0.0.0.0]); Mon, 02 Jul 2018 19:21:55 +1000 (AEST) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jul 2018 09:22:05 -0000 >> bob prohaska wrote on 30/06/2018 09:39: >> In my notes I don't find an RPi3 test case for 2GB swap, only 1, 2.3 and 3. >> I _think_ 2 GB is enough, based on a ~1.4 GB peak, but apparently didn't test it. >> Apologies for the misinformation! Just for info: A successful make -j4 buildworld using swap (2G) and /usr/obj (20G) on an external USB mechanical disk drive on the RPi3B+ used a maximum swap of 1130MB in multi-user with almost nothing else running apart from my logging script calling top, head, gstat and grep every second or two. Now running a make -j4 buildworld with 2G of swap on a USB memory key plugged into a powered USB hub... From owner-freebsd-arm@freebsd.org Mon Jul 2 09:25:15 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F1DF5FF095E for ; Mon, 2 Jul 2018 09:25:14 +0000 (UTC) (envelope-from sparvu@kronometrix.org) Received: from mail.kronometrix.org (mail.kronometrix.org [95.85.46.90]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.kronometrix.org", Issuer "mail.kronometrix.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 55C657D7A7 for ; Mon, 2 Jul 2018 09:25:14 +0000 (UTC) (envelope-from sparvu@kronometrix.org) Received: from [192.168.1.50] (87-100-230-21.bb.dnainternet.fi [87.100.230.21]) (authenticated bits=0) by mail.kronometrix.org (8.15.2/8.15.2) with ESMTPSA id w629HiHI090273 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Mon, 2 Jul 2018 09:17:44 GMT (envelope-from sparvu@kronometrix.org) X-Authentication-Warning: mail: Host 87-100-230-21.bb.dnainternet.fi [87.100.230.21] claimed to be [192.168.1.50] From: Stefan Parvu Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\)) Subject: FreeBSD on latest RPI3+ Message-Id: <9E4BB8D2-DCDC-4C69-BE37-1D0896295B56@kronometrix.org> Date: Mon, 2 Jul 2018 12:17:38 +0300 To: freebsd-arm@freebsd.org X-Mailer: Apple Mail (2.3445.8.2) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jul 2018 09:25:15 -0000 Hi, Do we support already the latest RPI3+ [1] ? Probable that would be FreeBSD 12.0 no back porting to FreeBSD 11.x ? thanks, Stefan [1] https://www.raspberrypi.org/products/raspberry-pi-3-model-b-plus/ From owner-freebsd-arm@freebsd.org Mon Jul 2 11:16:03 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1A7C01013A98 for ; Mon, 2 Jul 2018 11:16:03 +0000 (UTC) (envelope-from freebsd-arm@sentry.org) Received: from shadow.sentry.org (shadow.sentry.org [210.8.237.106]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "shadow.sentry.org", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 43FD18290F for ; Mon, 2 Jul 2018 11:16:01 +0000 (UTC) (envelope-from freebsd-arm@sentry.org) Received: from shadow.sentry.org (localhost [127.0.0.1]) by shadow.sentry.org (8.15.2/8.15.2) with ESMTP id w62BFvPS005369 for ; Mon, 2 Jul 2018 21:15:58 +1000 (AEST) (envelope-from freebsd-arm@sentry.org) Subject: Re: RPI3 swap experiments From: Trev To: freebsd-arm@freebsd.org References: <20180627194217.GA27793@www.zefox.net> <20180628022457.GA30110@www.zefox.net> <7B9D272D-3EDE-46FA-8A1C-AEE65047167C@yahoo.com> <20180628163328.GA33408@www.zefox.net> <51e208b4-9f14-58f7-1e70-6ef8db2c0bed@sentry.org> <20180629155131.GA35717@www.zefox.net> <20180629233937.GC35717@www.zefox.net> <0f137e06-214a-3e8c-a216-f061ec04ac2c@sentry.org> <20180630005145.GA43801@www.zefox.net> <6f3406e2-71f3-d0c2-2b65-703e1a1d3c25@sentry.org> Message-ID: <8e92b2b7-da61-3efb-7231-9fac76b2c1d4@sentry.org> Date: Mon, 2 Jul 2018 21:15:57 +1000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.3 MIME-Version: 1.0 In-Reply-To: <6f3406e2-71f3-d0c2-2b65-703e1a1d3c25@sentry.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.2 (shadow.sentry.org [0.0.0.0]); Mon, 02 Jul 2018 21:15:58 +1000 (AEST) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jul 2018 11:16:03 -0000 Trev wrote on 02/07/2018 19:21: > Now running a make -j4 buildworld with 2G of swap on a USB memory key > plugged into a powered USB hub... No luck, so I think I can now safely discount power issues. The hub had its own 2A PSU, the RPi3B+ has a 3A PSU. FreeBSD rpi3.sentry.org 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r335854: Mon Jul 2 16:03:04 AEST 2018 root@rpi3.sentry.org:/usr/obj/usr/src/arm64.aarch64/sys/RPI3-12.0 arm64 Jul 2 21:02:52 rpi3 kernel: pid 82523 (c++), uid 0, was killed: out of swap space last pid: 82852; load averages: 4.35, 4.33, 4.19 up 0+02:16:01 21:02:50 47 processes: 5 running, 42 sleeping CPU: 78.3% user, 0.0% nice, 7.8% system, 0.3% interrupt, 13.7% idle Mem: 550M Active, 256K Inact, 159M Laundry, 186M Wired, 97M Buf, 9M Free Swap: 2G Total, 143M Used, 2G Free, 6% Inuse 0 0 0 0 0.0 0 0 0.0 0.0 mmcsd0s2a 5 0 0 0 0.0 0 0 0.0 0.0 da0p1 0 0 0 0 0.0 0 0 0.0 0.0 da0p2 last pid: 82856; load averages: 4.35, 4.33, 4.19 up 0+02:16:02 21:02:51 47 processes: 4 running, 43 sleeping CPU: 78.3% user, 0.0% nice, 7.8% system, 0.3% interrupt, 13.7% idle Mem: 520M Active, 412K Inact, 129M Laundry, 185M Wired, 97M Buf, 72M Free Swap: 2G Total, 114M Used, 2G Free, 5% Inuse 0 0 0 0 0.0 0 0 0.0 0.0 mmcsd0s2a 7 455 0 0 0.0 455 7124 9.1 101.7 da0p1 0 0 0 0 0.0 0 0 0.0 0.0 da0p2 [OUT OF SWAP in the 1 sec between the above and below entries] last pid: 82860; load averages: 4.35, 4.33, 4.19 up 0+02:16:04 21:02:53 46 processes: 3 running, 43 sleeping CPU: 78.3% user, 0.0% nice, 7.8% system, 0.3% interrupt, 13.7% idle Mem: 466M Active, 8M Inact, 59M Laundry, 185M Wired, 97M Buf, 187M Free Swap: 2G Total, 80M Used, 2G Free, 3% Inuse 0 1 1 32 2.7 0 0 0.0 0.3 mmcsd0s2a 0 38 38 639 2.6 0 0 0.0 10.0 da0p1 0 0 0 0 0.0 0 0 0.0 0.0 da0p2 From owner-freebsd-arm@freebsd.org Mon Jul 2 12:03:05 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 464C8102064B for ; Mon, 2 Jul 2018 12:03:05 +0000 (UTC) (envelope-from tagattie@yandex.com) Received: from forward103p.mail.yandex.net (forward103p.mail.yandex.net [IPv6:2a02:6b8:0:1472:2741:0:8b7:106]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CC2588490A for ; Mon, 2 Jul 2018 12:03:04 +0000 (UTC) (envelope-from tagattie@yandex.com) Received: from mxback20j.mail.yandex.net (mxback20j.mail.yandex.net [IPv6:2a02:6b8:0:1619::114]) by forward103p.mail.yandex.net (Yandex) with ESMTP id C25BB21845C4 for ; Mon, 2 Jul 2018 15:02:53 +0300 (MSK) Received: from smtp3p.mail.yandex.net (smtp3p.mail.yandex.net [2a02:6b8:0:1472:2741:0:8b6:8]) by mxback20j.mail.yandex.net (nwsmtp/Yandex) with ESMTP id pbMHVJxDOt-2qkC36ab; Mon, 02 Jul 2018 15:02:53 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.com; s=mail; t=1530532973; bh=KXXZBUXgwNd6R1ofDY5G4aeigdOIqHd9KU8xUuMc59E=; h=From:Subject:To:Message-ID:Date; b=lBnp6xNQW+HilZTceBCkTfuE5ao407EvtU2hoHgW+pwEUCdnKyT17HrWl1SUsB7A0 0gkCXKMtF4MbPKELwtZ19R91GBb/RtM2HOXa649OrKHAtrYe1yxoKhtfcsL9PcGxpo 6kbzDwdg5Y+zLusyzHJjOLV9Sb6kN6NCnN2lopx4= Received: by smtp3p.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id VixYoywyC9-2pOSrBLq; Mon, 02 Jul 2018 15:02:52 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.com; s=mail; t=1530532972; bh=KXXZBUXgwNd6R1ofDY5G4aeigdOIqHd9KU8xUuMc59E=; h=From:Subject:To:Message-ID:Date; b=SFnySHPR7KL3xx9BFpSJJRAaLfrPmKqNuGlc3+In3W22aP7tkEqqfYcG5ZzCelym4 9quu9hgQl3NOfX953/8eeJtGwz38yRoSz/aLl9GcNnYo3etOsKsuDUjCSHfwrYWUm2 gHxewVbcAHfXnkGYeZA95p6iNerQ+wIlBROvAJ4c= Authentication-Results: smtp3p.mail.yandex.net; dkim=pass header.i=@yandex.com From: Hiroki Tagato Subject: FreeBSD 11.2 and RPI2 B 1.2 To: freebsd-arm@freebsd.org Message-ID: <3be7e43c-bdc5-263b-c2e6-318dacb815f6@yandex.com> Date: Mon, 2 Jul 2018 21:02:48 +0900 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.9.0 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-2022-jp; format=flowed; delsp=yes Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jul 2018 12:03:05 -0000 Hi, Is anyone successfully running FreeBSD 11.2-RELEASE on RPI2 Model B V1.2 (BCM2837-based)? Once it successfully booted but recent 11.2's hang during boot. Results from my trials are: - 11.2-BETA3: Success - 11.2-RC1: Hang - 11.2-RC3: Hang - 11.2-REL: Hang - Latest 11-STABLE snapshot: Hang - Latest 12-CURRENT snapshot: Success I have filed a PR on this issue with boot logs: Bug 228675 - 11.2-RC1 hangs during boot on RPI2 Model B Ver. 1.2 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228675 Any suggestions are appreciated. Thanks, Hiroki From owner-freebsd-arm@freebsd.org Mon Jul 2 14:05:39 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6A28A102A56B for ; Mon, 2 Jul 2018 14:05:39 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (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 D7F458A27D for ; Mon, 2 Jul 2018 14:05:38 +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 w62E5jeX055721 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 2 Jul 2018 07:05:46 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w62E5iBV055720; Mon, 2 Jul 2018 07:05:44 -0700 (PDT) (envelope-from fbsd) Date: Mon, 2 Jul 2018 07:05:44 -0700 From: bob prohaska To: Jamie Landeg-Jones Cc: bob prohaska , freebsd-arm@freebsd.org Subject: Re: RPI3 swap experiments, was Re: GPT vs MBR for swap devices Message-ID: <20180702140544.GA55574@www.zefox.net> References: <20180623143218.GA6905@www.zefox.net> <03C2D3C4-6E90-4054-AF79-BD7FE2B7958D@yahoo.com> <20180624231020.GA11132@www.zefox.net> <20180626052451.GA17293@www.zefox.net> <201806261040.w5QAeBKq035183@donotpassgo.dyslexicfish.net> <201807020731.w627VAcY072406@donotpassgo.dyslexicfish.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201807020731.w627VAcY072406@donotpassgo.dyslexicfish.net> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jul 2018 14:05:39 -0000 On Mon, Jul 02, 2018 at 08:31:10AM +0100, Jamie Landeg-Jones wrote: > > > It was the RPI2 that gave me vfs errors under load - the RPI3 I couldn't get > to boot at all. > > The good new, is, I have loaded the latest image, > FreeBSD-12.0-CURRENT-arm64-aarch64-RPI3-20180628-r335760.img and it loads fine. > > As such I have a virgin RPI3 with new sdcard, and a new USB stick, and I'm > willing to configure it however you want, to help the testing. > > What do you think would be the best things to do next? Try and emulate Bobs > problem, or try some other stress tests? > I have the same snapshot building world with swap, var, tmp and usr on a Sandisk SDCZ80-064G usb stick. Swap is 3 GB, in 3 partitions of 1 GB each. A -j4 buildworld is running, it's apt to finish shortly. Running a similar test couldn't hurt if no better ideas come along. Adding swap to the microSD card would put you a step ahead of me. If you could get your hands on a Sandisk SDCZ800-064G it would be especially interesting; that's the usb stick that started this goosechase. Hopefully somebody will have better ideas.... bob prohaska From owner-freebsd-arm@freebsd.org Mon Jul 2 15:01:08 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 66136102C313 for ; Mon, 2 Jul 2018 15:01:08 +0000 (UTC) (envelope-from wis@teraspeed.com) Received: from us-smtp-delivery-1.mimecast.com (us-smtp-2.mimecast.com [207.211.31.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "*.mimecast.com", Issuer "DigiCert Global CA G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F33068C953 for ; Mon, 2 Jul 2018 15:01:07 +0000 (UTC) (envelope-from wis@teraspeed.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=samtec.com; s=mimecast20180126; t=1530543661; h=from:subject:date:message-id:to:mime-version:content-type; bh=/dejXvQdvfmv6aA16lz1hVTY5UCHvssZAgQeU8PCNEg=; b=Z0fgX+Qxy8jYqbB+n/H9PtOr8O3hlrH3pBk5jCLagiFObcRBi8sTvAlq6DHHZ3WKrEmxJ5KrLg7kjTPyQ8LpRVMwYRxE+AxMcYGBEKsPy5nycBcaP7NoDkz5mHUHHxS2IrpQqg8clVGXG5aaVau9KnSKuKEmh+uwPL/x72E6cDc= Received: from NAM04-SN1-obe.outbound.protection.outlook.com (mail-sn1nam04lp0085.outbound.protection.outlook.com [216.32.180.85]) (Using TLS) by us-smtp-1.mimecast.com with ESMTP id us-mta-167-RL0pJUzaPBu0V6wqGwcPKQ-1; Mon, 02 Jul 2018 10:58:33 -0400 Received: from BY2PR16MB0149.namprd16.prod.outlook.com (10.163.65.143) by BY2PR16MB0518.namprd16.prod.outlook.com (10.163.191.16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.906.26; Mon, 2 Jul 2018 14:58:30 +0000 Received: from BY2PR16MB0149.namprd16.prod.outlook.com ([fe80::f08c:a560:89f9:3f05]) by BY2PR16MB0149.namprd16.prod.outlook.com ([fe80::f08c:a560:89f9:3f05%3]) with mapi id 15.20.0906.026; Mon, 2 Jul 2018 14:58:30 +0000 From: Wis Macomson To: "freebsd-arm@freebsd.org" Subject: Re: RPI3B+ does not reboot Thread-Topic: Re: RPI3B+ does not reboot Thread-Index: AdQSFJGNow8Et8P9QFiUcQkJdFl0FQ== Date: Mon, 2 Jul 2018 14:58:30 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [50.255.111.2] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; BY2PR16MB0518; 7:kRTHoMKkhV9xbbjLPDvWtUf4u4DPA7rq72XXOekJ7Cy3Ojmk2eQ8WIhgp6ekVQzd7F8pBLtj0gPLJr/uu2Wv7Mru+ek0foG5LkZTxrODc1xlBPK1BIaZNpcHBhi8dQhpubHxJU1c7ZIIISutQ18kOsKRFtsAmMwxixWiJuEh2Oz5ICk5DrtO7G6pXSUa+diSvx2hn3vGBWqIyV8zaJ+ui+wECwvrA16ZlX0k9TymrKgpUWknsC4rWvrB1Jm/s95p; 20:5m/ZSslnx1if2lEfo3RUson2HKDSrxuBak2z3ThdHh4+kRw4111YCbqa4vf0VNh6W5qWs4mvy5DjoWgDtxOgkAh+QS2GRXtakQyLk6z+UX3WhgpU9M3xzH4dmHrBi64HrA0kP04ldYNktO5xvknGRv81pP/5uNJ8MS4ZMqAXbR0= x-ms-exchange-antispam-srfa-diagnostics: SOS; x-ms-office365-filtering-correlation-id: 244bc18e-ce13-43df-3d6c-08d5e02c466d x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989117)(5600053)(711020)(4534165)(4627221)(201703031133081)(201702281549075)(8990107)(2017052603328)(7153060)(7193020); SRVR:BY2PR16MB0518; x-ms-traffictypediagnostic: BY2PR16MB0518: x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(28532068793085)(21748063052155); x-ms-exchange-senderadcheck: 1 x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(5005006)(8121501046)(3231254)(944501410)(52105095)(3002001)(93006095)(93001095)(10201501046)(149027)(150027)(6041310)(20161123558120)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(20161123562045)(20161123564045)(6072148)(201708071742011)(7699016); SRVR:BY2PR16MB0518; BCL:0; PCL:0; RULEID:; SRVR:BY2PR16MB0518; x-forefront-prvs: 07215D0470 x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(366004)(396003)(39850400004)(346002)(376002)(136003)(199004)(189003)(8676002)(256004)(68736007)(478600001)(53936002)(6246003)(5660300001)(476003)(2501003)(66066001)(229853002)(5250100002)(86362001)(14454004)(2906002)(7696005)(486006)(74316002)(81156014)(81166006)(8936002)(102836004)(186003)(6506007)(26005)(7736002)(97736004)(6916009)(33656002)(105586002)(106356001)(6116002)(790700001)(3846002)(54896002)(99286004)(2900100001)(55016002)(6436002)(316002)(25786009)(72206003)(2351001)(5630700001)(9686003)(6306002)(5640700003)(80792005)(32563001); DIR:OUT; SFP:1102; SCL:1; SRVR:BY2PR16MB0518; H:BY2PR16MB0149.namprd16.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; x-microsoft-antispam-message-info: W4E1leyQ6DP+YSeRd1MjMgqHTPr5nBfbwnwZctk08KfjzkgRrOLURiijj0qLSdMjMz8r0HYVgIS3jG0MeZY9X9k8qDresQVhoay5DOvL0Von50Fy294daghba5U3Htp+z2EryaM3FF/6fRwA9+xQXbWV5Z2cwNqzInCFQaBA7e0y6YOAu2YWdqEfSBwsYJh6hn3hge1TWBczBjaX3mdgmV+9rtpsgjgJugBQ15G1oS28HwEea8BeIwDtD9l3dbdRE6oqzWJ1OySMaXCV7CqV4R9yBr3zv06XGaWFLdGY/qgr+opIJn9q8ICD5z3jUKje02/pBtt13QJ4nGG2W07KHyN30NNOVJ8VClwOM9zbqvE= spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM MIME-Version: 1.0 X-OriginatorOrg: teraspeed.com X-MS-Exchange-CrossTenant-Network-Message-Id: 244bc18e-ce13-43df-3d6c-08d5e02c466d X-MS-Exchange-CrossTenant-originalarrivaltime: 02 Jul 2018 14:58:30.5638 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 9943a816-2cec-4883-855e-09a8c36108af X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY2PR16MB0518 X-MC-Unique: RL0pJUzaPBu0V6wqGwcPKQ-1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jul 2018 15:01:08 -0000 Can you disconnect the serial TX data (data to the RPi) and try the reboots= ? It may be that this signal is partially powering the processor through the = input ESD protection diode, leading to very awkward internal states. This h= as been observed on the Rock64 (RK3328 SoC) and Rockpro64 (RK3399). If you can just break the TX connection, you'll be able to see the boot mes= sages. -wis Wis Macomson, Signal Integrity Engineer Oregon, Teraspeed Home Office Office: 541-393-8023=20 www.samtec.com =20 From owner-freebsd-arm@freebsd.org Mon Jul 2 23:20:25 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3D703FE379A for ; Mon, 2 Jul 2018 23:20:25 +0000 (UTC) (envelope-from freebsd-arm@sentry.org) Received: from shadow.sentry.org (shadow.sentry.org [210.8.237.106]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "shadow.sentry.org", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6689A7F90C for ; Mon, 2 Jul 2018 23:20:23 +0000 (UTC) (envelope-from freebsd-arm@sentry.org) Received: from shadow.sentry.org (localhost [127.0.0.1]) by shadow.sentry.org (8.15.2/8.15.2) with ESMTP id w62NKIuk049397 for ; Tue, 3 Jul 2018 09:20:18 +1000 (AEST) (envelope-from freebsd-arm@sentry.org) Subject: Re: RPI3B+ does not reboot To: "freebsd-arm@freebsd.org" References: From: Trev Message-ID: Date: Tue, 3 Jul 2018 09:20:18 +1000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.3 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.2 (shadow.sentry.org [0.0.0.0]); Tue, 03 Jul 2018 09:20:18 +1000 (AEST) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jul 2018 23:20:25 -0000 Wis Macomson wrote on 03/07/2018 00:58: > Can you disconnect the serial TX data (data to the RPi) and try the reboots? > > It may be that this signal is partially powering the processor through the input ESD > protection diode, leading to very awkward internal states. This has been observed on > the Rock64 (RK3328 SoC) and Rockpro64 (RK3399). > > If you can just break the TX connection, you'll be able to see the boot messages. I removed Tx and left Rx and Gnd connected but on the first reboot attempt I still suffered: All buffers synced. Uptime: 11h34m59s Rebooting... cpu_reset failed From owner-freebsd-arm@freebsd.org Tue Jul 3 00:22:37 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 69D3AFE780A for ; Tue, 3 Jul 2018 00:22:37 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (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 C224B81D94 for ; Tue, 3 Jul 2018 00:22:36 +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 w630MoGJ057210 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 2 Jul 2018 17:22:50 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w630Mne8057209; Mon, 2 Jul 2018 17:22:49 -0700 (PDT) (envelope-from fbsd) Date: Mon, 2 Jul 2018 17:22:49 -0700 From: bob prohaska To: Wis Macomson Cc: "freebsd-arm@freebsd.org" , bob prohaska Subject: Re: RPI3B+ does not reboot Message-ID: <20180703002249.GA57112@www.zefox.net> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jul 2018 00:22:37 -0000 On Mon, Jul 02, 2018 at 02:58:30PM +0000, Wis Macomson wrote: > Can you disconnect the serial TX data (data to the RPi) and try the reboots? > > It may be that this signal is partially powering the processor through the input ESD protection diode, leading to very awkward internal states. This has been observed on the Rock64 (RK3328 SoC) and Rockpro64 (RK3399). > > If you can just break the TX connection, you'll be able to see the boot messages. > Updating from the June 28 snapshot (which did it twice) to r335835 seems to make the problem go away. hth, bob prohaska From owner-freebsd-arm@freebsd.org Tue Jul 3 00:38:20 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AB726FE8A41 for ; Tue, 3 Jul 2018 00:38:20 +0000 (UTC) (envelope-from freebsd-wifi@sentry.org) Received: from shadow.sentry.org (shadow.sentry.org [210.8.237.106]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "shadow.sentry.org", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D44B58273F for ; Tue, 3 Jul 2018 00:38:19 +0000 (UTC) (envelope-from freebsd-wifi@sentry.org) Received: from shadow.sentry.org (localhost [127.0.0.1]) by shadow.sentry.org (8.15.2/8.15.2) with ESMTP id w630cFt9053274 for ; Tue, 3 Jul 2018 10:38:16 +1000 (AEST) (envelope-from freebsd-wifi@sentry.org) Subject: Re: RPI3B+ does not reboot To: "freebsd-arm@freebsd.org" References: <20180703002249.GA57112@www.zefox.net> From: Trev Message-ID: <2b1d5d6a-602e-4d53-12a5-0f23c3569101@sentry.org> Date: Tue, 3 Jul 2018 10:38:15 +1000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.3 MIME-Version: 1.0 In-Reply-To: <20180703002249.GA57112@www.zefox.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.2 (shadow.sentry.org [0.0.0.0]); Tue, 03 Jul 2018 10:38:16 +1000 (AEST) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jul 2018 00:38:20 -0000 bob prohaska wrote on 03/07/2018 10:22: > On Mon, Jul 02, 2018 at 02:58:30PM +0000, Wis Macomson wrote: >> Can you disconnect the serial TX data (data to the RPi) and try the reboots? >> >> It may be that this signal is partially powering the processor through the input ESD protection diode, leading to very awkward internal states. This has been observed on the Rock64 (RK3328 SoC) and Rockpro64 (RK3399). >> >> If you can just break the TX connection, you'll be able to see the boot messages. >> > > Updating from the June 28 snapshot (which did it twice) to r335835 seems to make > the problem go away. r335854 compiled Mon Jul 2 16:03:04 AEST 2018 and I still have the "cpu_reset failed" issue :( From owner-freebsd-arm@freebsd.org Tue Jul 3 05:19:11 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CD1EBFFBE67 for ; Tue, 3 Jul 2018 05:19:10 +0000 (UTC) (envelope-from freebsd-arm@sentry.org) Received: from shadow.sentry.org (shadow.sentry.org [210.8.237.106]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "shadow.sentry.org", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 119698C606 for ; Tue, 3 Jul 2018 05:19:09 +0000 (UTC) (envelope-from freebsd-arm@sentry.org) Received: from shadow.sentry.org (localhost [127.0.0.1]) by shadow.sentry.org (8.15.2/8.15.2) with ESMTP id w635J6rv073575 for ; Tue, 3 Jul 2018 15:19:06 +1000 (AEST) (envelope-from freebsd-arm@sentry.org) Subject: Re: RPI3 swap experiments From: Trev To: freebsd-arm@freebsd.org References: <20180627194217.GA27793@www.zefox.net> <20180628022457.GA30110@www.zefox.net> <7B9D272D-3EDE-46FA-8A1C-AEE65047167C@yahoo.com> <20180628163328.GA33408@www.zefox.net> <51e208b4-9f14-58f7-1e70-6ef8db2c0bed@sentry.org> <20180629155131.GA35717@www.zefox.net> <20180629233937.GC35717@www.zefox.net> <0f137e06-214a-3e8c-a216-f061ec04ac2c@sentry.org> <20180630005145.GA43801@www.zefox.net> <6f3406e2-71f3-d0c2-2b65-703e1a1d3c25@sentry.org> <8e92b2b7-da61-3efb-7231-9fac76b2c1d4@sentry.org> Message-ID: Date: Tue, 3 Jul 2018 15:19:06 +1000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.3 MIME-Version: 1.0 In-Reply-To: <8e92b2b7-da61-3efb-7231-9fac76b2c1d4@sentry.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.2 (shadow.sentry.org [0.0.0.0]); Tue, 03 Jul 2018 15:19:06 +1000 (AEST) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jul 2018 05:19:11 -0000 For my final swap experiment, and bearing mind that there is no swap issue with 11-STABLE on the RPi2B running at 900 MHz using USB2 memory keys for swap and /usr, I underclocked the RPi3B+ from 1.4 GHz to 600 MHz with 'powerd -M 600' and double-checked while the make -j4 build was running: trev@rpi3:~ % sysctl -a | grep dev.cpu.0. dev.cpu.0.temperature: 57.9C dev.cpu.0.freq_levels: 1400/-1 600/-1 dev.cpu.0.freq: 600 Alas: Jul 3 12:06:12 rpi3 kernel: pid 60768 (c++), uid 0, was killed: out of swap space Stats with a lucky capture at 12:06:12 below: last pid: 61107; load averages: 3.73, 4.16, 4.07 up 0+02:07:00 12:06:00 49 processes: 1 running, 47 sleeping, 1 waiting CPU: 82.6% user, 0.0% nice, 7.3% system, 0.3% interrupt, 9.9% idle Mem: 578M Active, 196K Inact, 128M Laundry, 188M Wired, 97M Buf, 11M Free Swap: 2G Total, 144M Used, 2G Free, 7% Inuse 0 0 0 0 0.0 0 0 0.0 0.0 mmcsd0s2a 9 0 0 0 0.0 0 0 0.0 0.0 da0p1 0 0 0 0 0.0 0 0 0.0 0.0 da0p2 last pid: 61111; load averages: 3.73, 4.16, 4.07 up 0+02:07:01 12:06:01 49 processes: 1 running, 47 sleeping, 1 waiting CPU: 82.6% user, 0.0% nice, 7.3% system, 0.3% interrupt, 9.9% idle Mem: 578M Active, 128K Inact, 128M Laundry, 188M Wired, 97M Buf, 11M Free Swap: 2G Total, 144M Used, 2G Free, 7% Inuse 0 0 0 0 0.0 0 0 0.0 0.0 mmcsd0s2a 9 397 0 0 0.0 397 5479 23.1 229.5 da0p1 0 0 0 0 0.0 0 0 0.0 0.0 da0p2 last pid: 61115; load averages: 3.73, 4.16, 4.07 up 0+02:07:03 12:06:03 49 processes: 1 running, 47 sleeping, 1 waiting CPU: 82.6% user, 0.0% nice, 7.3% system, 0.3% interrupt, 9.9% idle Mem: 580M Active, 236K Inact, 121M Laundry, 188M Wired, 97M Buf, 16M Free Swap: 2G Total, 149M Used, 2G Free, 7% Inuse 0 0 0 0 0.0 0 0 0.0 0.0 mmcsd0s2a 6 435 38 280 470.3 398 4998 8.2 88.8 da0p1 0 0 0 0 0.0 0 0 0.0 0.0 da0p2 last pid: 61119; load averages: 3.73, 4.16, 4.07 up 0+02:07:04 12:06:04 49 processes: 3 running, 46 sleeping CPU: 82.6% user, 0.0% nice, 7.3% system, 0.3% interrupt, 9.9% idle Mem: 586M Active, 668K Inact, 114M Laundry, 188M Wired, 97M Buf, 16M Free Swap: 2G Total, 155M Used, 2G Free, 7% Inuse 0 0 0 0 0.0 0 0 0.0 0.0 mmcsd0s2a 6 473 20 211 49.7 453 5273 7.9 95.2 da0p1 0 0 0 0 0.0 0 0 0.0 0.0 da0p2 last pid: 61123; load averages: 3.59, 4.13, 4.06 up 0+02:07:05 12:06:05 49 processes: 2 running, 47 sleeping CPU: 82.6% user, 0.0% nice, 7.3% system, 0.3% interrupt, 9.9% idle Mem: 598M Active, 656K Inact, 107M Laundry, 187M Wired, 97M Buf, 11M Free Swap: 2G Total, 160M Used, 2G Free, 7% Inuse 0 0 0 0 0.0 0 0 0.0 0.0 mmcsd0s2a 7 16 0 0 0.0 16 414 12.5 4.9 da0p1 0 0 0 0 0.0 0 0 0.0 0.0 da0p2 last pid: 61127; load averages: 3.59, 4.13, 4.06 up 0+02:07:06 12:06:06 49 processes: 2 running, 47 sleeping CPU: 82.5% user, 0.0% nice, 7.3% system, 0.3% interrupt, 9.9% idle Mem: 593M Active, 5M Inact, 109M Laundry, 187M Wired, 97M Buf, 11M Free Swap: 2G Total, 161M Used, 2G Free, 7% Inuse 0 0 0 0 0.0 0 0 0.0 0.0 mmcsd0s2a 5 140 4 28 1710 136 2013 56.1 200.7 da0p1 0 0 0 0 0.0 0 0 0.0 0.0 da0p2 last pid: 61131; load averages: 3.59, 4.13, 4.06 up 0+02:07:07 12:06:07 49 processes: 4 running, 45 sleeping CPU: 82.5% user, 0.0% nice, 7.3% system, 0.3% interrupt, 9.9% idle Mem: 587M Active, 5M Inact, 116M Laundry, 187M Wired, 97M Buf, 10M Free Swap: 2G Total, 163M Used, 2G Free, 7% Inuse 2 0 0 0 0.0 0 0 0.0 0.0 mmcsd0s2a 7 500 1 4 1.3 499 6302 7.9 99.5 da0p1 0 0 0 0 0.0 0 0 0.0 0.0 da0p2 last pid: 61135; load averages: 3.59, 4.13, 4.06 up 0+02:07:08 12:06:08 49 processes: 2 running, 47 sleeping CPU: 82.5% user, 0.0% nice, 7.3% system, 0.3% interrupt, 9.9% idle Mem: 594M Active, 3M Inact, 110M Laundry, 187M Wired, 97M Buf, 11M Free Swap: 2G Total, 170M Used, 2G Free, 8% Inuse 0 2 0 0 0.0 2 64 157.3 16.0 mmcsd0s2a 6 475 17 92 228.8 458 4500 7.2 89.7 da0p1 0 0 0 0 0.0 0 0 0.0 0.0 da0p2 last pid: 61139; load averages: 3.38, 4.08, 4.04 up 0+02:07:09 12:06:09 49 processes: 2 running, 47 sleeping CPU: 82.5% user, 0.0% nice, 7.3% system, 0.3% interrupt, 9.9% idle Mem: 585M Active, 556K Inact, 120M Laundry, 187M Wired, 97M Buf, 12M Free Swap: 2G Total, 175M Used, 2G Free, 8% Inuse 0 0 0 0 0.0 0 0 0.0 0.0 mmcsd0s2a 6 337 25 220 137.6 312 4575 8.3 70.1 da0p1 0 0 0 0 0.0 0 0 0.0 0.0 da0p2 last pid: 61143; load averages: 3.38, 4.08, 4.04 up 0+02:07:10 12:06:10 49 processes: 3 running, 46 sleeping CPU: 82.5% user, 0.0% nice, 7.3% system, 0.3% interrupt, 9.9% idle Mem: 591M Active, 192K Inact, 114M Laundry, 188M Wired, 97M Buf, 12M Free Swap: 2G Total, 179M Used, 2G Free, 8% Inuse 0 0 0 0 0.0 0 0 0.0 0.0 mmcsd0s2a 1 374 9 64 774.7 365 5552 26.1 239.9 da0p1 0 0 0 0 0.0 0 0 0.0 0.0 da0p2 [OUT OF SWAP at 12:06:12 below] last pid: 61151; load averages: 3.38, 4.08, 4.04 up 0+02:07:12 12:06:12 49 processes: 4 running, 45 sleeping CPU: 82.5% user, 0.0% nice, 7.3% system, 0.3% interrupt, 10.0% idle Mem: 492M Active, 216K Inact, 82M Laundry, 187M Wired, 97M Buf, 144M Free Swap: 2G Total, 147M Used, 2G Free, 7% Inuse 0 2 2 64 3.0 0 0 0.0 0.6 mmcsd0s2a 1 270 226 2374 3.7 44 1199 11.3 54.7 da0p1 0 0 0 0 0.0 0 0 0.0 0.0 da0p2 last pid: 61156; load averages: 3.38, 4.08, 4.04 up 0+02:07:13 12:06:13 49 processes: 4 running, 45 sleeping CPU: 82.5% user, 0.0% nice, 7.3% system, 0.3% interrupt, 10.0% idle Mem: 464M Active, 3M Inact, 65M Laundry, 188M Wired, 97M Buf, 186M Free Swap: 2G Total, 103M Used, 2G Free, 5% Inuse 0 0 0 0 0.0 0 0 0.0 0.0 mmcsd0s2a 0 217 217 1817 1.7 0 0 0.0 36.9 da0p1 0 0 0 0 0.0 0 0 0.0 0.0 da0p2 There are no extraordinarily high ms/w stats. The sdcard records a 157.3 ms/w peak whereas the USB2 memory key's peak is 56.1 ms/w. So I'm not convinced that the USB2 memory key is "too slow". On the other hand, using a USB2 attached hard disk does work... From owner-freebsd-arm@freebsd.org Tue Jul 3 15:54:25 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 25933102C265 for ; Tue, 3 Jul 2018 15:54:25 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AEFA688BAF for ; Tue, 3 Jul 2018 15:54:24 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smtp.greenhost.nl ([213.108.110.112]) by smarthost1.greenhost.nl with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from ) id 1faNd9-0003hZ-CL; Tue, 03 Jul 2018 17:54:16 +0200 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: freebsd-arm@freebsd.org, "Stefan Parvu" Subject: Re: FreeBSD on latest RPI3+ References: <9E4BB8D2-DCDC-4C69-BE37-1D0896295B56@kronometrix.org> Date: Tue, 03 Jul 2018 17:54:15 +0200 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Ronald Klop" Message-ID: In-Reply-To: <9E4BB8D2-DCDC-4C69-BE37-1D0896295B56@kronometrix.org> User-Agent: Opera Mail/12.16 (FreeBSD) X-Authenticated-As-Hash: 398f5522cb258ce43cb679602f8cfe8b62a256d1 X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: / X-Spam-Score: -0.2 X-Spam-Status: No, score=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50 autolearn=disabled version=3.4.0 X-Scan-Signature: a350ae07b5350cdad28cef237d2e7179 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jul 2018 15:54:25 -0000 On Mon, 02 Jul 2018 11:17:38 +0200, Stefan Parvu wrote: > Hi, > > Do we support already the latest RPI3+ [1] ? Probable that would be > FreeBSD 12.0 no back porting to FreeBSD 11.x ? Yes, I have it running out of the box. Just install the RPI3 FreeBSD 12/aarch64 snapshot [1][2]. Since a couple of weeks ethernet is supported. WiFi and bluetooth are not (yet) supported. Regards, Ronald. [1] https://wiki.freebsd.org/FreeBSD/arm/Raspberry%20Pi [2] ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/arm64/aarch64/ISO-IMAGES/12.0 > > thanks, > Stefan > > [1] https://www.raspberrypi.org/products/raspberry-pi-3-model-b-plus/ > _______________________________________________ > 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 Tue Jul 3 18:57:19 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 15CAA103DA18 for ; Tue, 3 Jul 2018 18:57:19 +0000 (UTC) (envelope-from sparvu@kronometrix.org) Received: from mail.kronometrix.org (mail.kronometrix.org [95.85.46.90]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.kronometrix.org", Issuer "mail.kronometrix.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 70B4692244 for ; Tue, 3 Jul 2018 18:57:18 +0000 (UTC) (envelope-from sparvu@kronometrix.org) Received: from [192.168.1.50] (87-100-230-21.bb.dnainternet.fi [87.100.230.21]) (authenticated bits=0) by mail.kronometrix.org (8.15.2/8.15.2) with ESMTPSA id w63IvAW6011012 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 3 Jul 2018 18:57:11 GMT (envelope-from sparvu@kronometrix.org) X-Authentication-Warning: mail: Host 87-100-230-21.bb.dnainternet.fi [87.100.230.21] claimed to be [192.168.1.50] Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\)) Subject: Re: FreeBSD on latest RPI3+ From: Stefan Parvu In-Reply-To: Date: Tue, 3 Jul 2018 21:57:04 +0300 Cc: freebsd-arm@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <1DAB1D3D-DEA3-4904-A290-0EDC4B25217A@kronometrix.org> References: <9E4BB8D2-DCDC-4C69-BE37-1D0896295B56@kronometrix.org> To: Ronald Klop X-Mailer: Apple Mail (2.3445.8.2) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jul 2018 18:57:19 -0000 > Yes, I have it running out of the box. Just install the RPI3 FreeBSD = 12/aarch64 snapshot [1][2]. > Since a couple of weeks ethernet is supported. WiFi and bluetooth are = not (yet) supported. Im experimenting with it already. Are you using this = image:FreeBSD-12.0-CURRENT-arm64-aarch64-RPI3-20180628-r335760.img.xz and this should support the NIC ? Thanks for message, Stefan From owner-freebsd-arm@freebsd.org Tue Jul 3 20:23:59 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B323D1023432 for ; Tue, 3 Jul 2018 20:23:59 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 47C8796AA6 for ; Tue, 3 Jul 2018 20:23:58 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smtp.greenhost.nl ([213.108.110.112]) by smarthost1.greenhost.nl with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from ) id 1faRq8-0007Ar-UU; Tue, 03 Jul 2018 22:23:57 +0200 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: "Stefan Parvu" Cc: freebsd-arm@freebsd.org Subject: Re: FreeBSD on latest RPI3+ References: <9E4BB8D2-DCDC-4C69-BE37-1D0896295B56@kronometrix.org> <1DAB1D3D-DEA3-4904-A290-0EDC4B25217A@kronometrix.org> Date: Tue, 03 Jul 2018 22:23:58 +0200 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Ronald Klop" Message-ID: In-Reply-To: <1DAB1D3D-DEA3-4904-A290-0EDC4B25217A@kronometrix.org> User-Agent: Opera Mail/12.16 (FreeBSD) X-Authenticated-As-Hash: 398f5522cb258ce43cb679602f8cfe8b62a256d1 X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: / X-Spam-Score: -0.2 X-Spam-Status: No, score=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50 autolearn=disabled version=3.4.0 X-Scan-Signature: 2ecd0b53b7de9511489f92806276a3d7 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jul 2018 20:23:59 -0000 On Tue, 03 Jul 2018 20:57:04 +0200, Stefan Parvu wrote: > >> Yes, I have it running out of the box. Just install the RPI3 FreeBSD >> 12/aarch64 snapshot [1][2]. >> Since a couple of weeks ethernet is supported. WiFi and bluetooth are >> not (yet) supported. > > Im experimenting with it already. Are you using this > image:FreeBSD-12.0-CURRENT-arm64-aarch64-RPI3-20180628-r335760.img.xz > and this should support the NIC ? I installed an image of a few weeks ago so the one you mention has the right driver also. The driver is named if_muge. The system should load this driver automaticly at boot. See 'kldstat' if it is loaded or not. With 'ifconfig' it will show up as 'ue0'. What I find anoying is that the mac address of the ethernet changes every time you boot. So I hardcoded this in /etc/rc.conf. ifconfig_ue0="ether 12:34:56:78:90:ab DHCP" Instead of the number above I used one of the random values it used and I happened to register in my dhcp server/router. Regards, Ronald. > Thanks for message, > Stefan From owner-freebsd-arm@freebsd.org Tue Jul 3 20:29:08 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8E7DA1023AF3 for ; Tue, 3 Jul 2018 20:29:08 +0000 (UTC) (envelope-from gonzo@bluezbox.com) Received: from id.bluezbox.com (id.bluezbox.com [45.55.20.155]) (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 2A8A296C65 for ; Tue, 3 Jul 2018 20:29:08 +0000 (UTC) (envelope-from gonzo@bluezbox.com) Received: from localhost ([127.0.0.1] helo=id.bluezbox.com) by id.bluezbox.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.90_1 (FreeBSD)) (envelope-from ) id 1faRv1-000NeQ-2J; Tue, 03 Jul 2018 13:28:59 -0700 Received: (from gonzo@localhost) by id.bluezbox.com (8.15.2/8.15.2/Submit) id w63KSvLZ090917; Tue, 3 Jul 2018 13:28:57 -0700 (PDT) (envelope-from gonzo@bluezbox.com) X-Authentication-Warning: id.bluezbox.com: gonzo set sender to gonzo@bluezbox.com using -f Date: Tue, 3 Jul 2018 13:28:57 -0700 From: Oleksandr Tymoshenko To: Ronald Klop Cc: Stefan Parvu , freebsd-arm@freebsd.org Subject: Re: FreeBSD on latest RPI3+ Message-ID: <20180703202857.GA90907@bluezbox.com> References: <9E4BB8D2-DCDC-4C69-BE37-1D0896295B56@kronometrix.org> <1DAB1D3D-DEA3-4904-A290-0EDC4B25217A@kronometrix.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD/11.1-RELEASE-p4 (amd64) User-Agent: Mutt/1.9.1 (2017-09-22) X-Spam-Level: -- X-Spam-Report: Spam detection software, running on the system "id.bluezbox.com", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see The administrator of that system for details. Content preview: Ronald Klop (ronald-lists@klop.ws) wrote: > On Tue, 03 Jul 2018 20:57:04 +0200, Stefan Parvu > wrote: > > > > >> Yes, I have it running out of the box. Just install the RPI3 F [...] Content analysis details: (-2.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jul 2018 20:29:08 -0000 Ronald Klop (ronald-lists@klop.ws) wrote: > On Tue, 03 Jul 2018 20:57:04 +0200, Stefan Parvu > wrote: > > > > >> Yes, I have it running out of the box. Just install the RPI3 FreeBSD > >> 12/aarch64 snapshot [1][2]. > >> Since a couple of weeks ethernet is supported. WiFi and bluetooth are > >> not (yet) supported. > > > > Im experimenting with it already. Are you using this > > image:FreeBSD-12.0-CURRENT-arm64-aarch64-RPI3-20180628-r335760.img.xz > > and this should support the NIC ? > > > I installed an image of a few weeks ago so the one you mention has the > right driver also. The driver is named if_muge. > The system should load this driver automaticly at boot. > See 'kldstat' if it is loaded or not. > With 'ifconfig' it will show up as 'ue0'. > > What I find anoying is that the mac address of the ethernet changes every > time you boot. So I hardcoded this in /etc/rc.conf. > ifconfig_ue0="ether 12:34:56:78:90:ab DHCP" > > Instead of the number above I used one of the random values it used and I > happened to register in my dhcp server/router. I've just submitted a patch for review that addresses this problem: https://reviews.freebsd.org/D16117 -- gonzo From owner-freebsd-arm@freebsd.org Tue Jul 3 20:31:21 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2A6551023E65 for ; Tue, 3 Jul 2018 20:31:21 +0000 (UTC) (envelope-from sparvu@kronometrix.org) Received: from mail.kronometrix.org (mail.kronometrix.org [95.85.46.90]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.kronometrix.org", Issuer "mail.kronometrix.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id A0BA596EDC for ; Tue, 3 Jul 2018 20:31:20 +0000 (UTC) (envelope-from sparvu@kronometrix.org) Received: from [192.168.1.50] (87-100-230-21.bb.dnainternet.fi [87.100.230.21]) (authenticated bits=0) by mail.kronometrix.org (8.15.2/8.15.2) with ESMTPSA id w63KVHA3011814 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 3 Jul 2018 20:31:18 GMT (envelope-from sparvu@kronometrix.org) X-Authentication-Warning: mail: Host 87-100-230-21.bb.dnainternet.fi [87.100.230.21] claimed to be [192.168.1.50] Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\)) Subject: Re: FreeBSD on latest RPI3+ From: Stefan Parvu In-Reply-To: Date: Tue, 3 Jul 2018 23:31:12 +0300 Cc: freebsd-arm@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <9E4BB8D2-DCDC-4C69-BE37-1D0896295B56@kronometrix.org> <1DAB1D3D-DEA3-4904-A290-0EDC4B25217A@kronometrix.org> To: Ronald Klop X-Mailer: Apple Mail (2.3445.8.2) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jul 2018 20:31:21 -0000 >=20 > I installed an image of a few weeks ago so the one you mention has the = right driver also. The driver is named if_muge. > The system should load this driver automaticly at boot. > See 'kldstat' if it is loaded or not. it is not. I have only the kernel and tmpfs.ko loaded. No NIC present.=20= the image is = FreeBSD-12.0-CURRENT-arm64-aarch64-RPI3-20180628-r335760.img.xz Stefan= From owner-freebsd-arm@freebsd.org Tue Jul 3 20:47:05 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D209510259FF for ; Tue, 3 Jul 2018 20:47:05 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6BEA997959 for ; Tue, 3 Jul 2018 20:47:05 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smtp.greenhost.nl ([213.108.110.112]) by smarthost1.greenhost.nl with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from ) id 1faSCU-00059h-C5; Tue, 03 Jul 2018 22:47:03 +0200 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: "Stefan Parvu" Cc: freebsd-arm@freebsd.org Subject: Re: FreeBSD on latest RPI3+ References: <9E4BB8D2-DCDC-4C69-BE37-1D0896295B56@kronometrix.org> <1DAB1D3D-DEA3-4904-A290-0EDC4B25217A@kronometrix.org> Date: Tue, 03 Jul 2018 22:47:04 +0200 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Ronald Klop" Message-ID: In-Reply-To: User-Agent: Opera Mail/12.16 (FreeBSD) X-Authenticated-As-Hash: 398f5522cb258ce43cb679602f8cfe8b62a256d1 X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: / X-Spam-Score: -0.2 X-Spam-Status: No, score=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50 autolearn=disabled version=3.4.0 X-Scan-Signature: a07cf4f22b7e0347d98fbeb4081a69be X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jul 2018 20:47:06 -0000 On Tue, 03 Jul 2018 22:31:12 +0200, Stefan Parvu wrote: >> >> I installed an image of a few weeks ago so the one you mention has the >> right driver also. The driver is named if_muge. >> The system should load this driver automaticly at boot. >> See 'kldstat' if it is loaded or not. > > it is not. I have only the kernel and tmpfs.ko loaded. No NIC present. > the image is > FreeBSD-12.0-CURRENT-arm64-aarch64-RPI3-20180628-r335760.img.xz > > Stefan Try 'kldload if_muge' as root. From owner-freebsd-arm@freebsd.org Tue Jul 3 21:10:00 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ECBA51027D3C for ; Tue, 3 Jul 2018 21:09:59 +0000 (UTC) (envelope-from freebsd-arm@sentry.org) Received: from shadow.sentry.org (shadow.sentry.org [210.8.237.106]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "shadow.sentry.org", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2350B70943 for ; Tue, 3 Jul 2018 21:09:58 +0000 (UTC) (envelope-from freebsd-arm@sentry.org) Received: from shadow.sentry.org (localhost [127.0.0.1]) by shadow.sentry.org (8.15.2/8.15.2) with ESMTP id w63L9nsq081736 for ; Wed, 4 Jul 2018 07:09:49 +1000 (AEST) (envelope-from freebsd-arm@sentry.org) Subject: Re: RPI3 swap experiments From: Trev To: freebsd-arm@freebsd.org References: <20180627194217.GA27793@www.zefox.net> <20180628022457.GA30110@www.zefox.net> <7B9D272D-3EDE-46FA-8A1C-AEE65047167C@yahoo.com> <20180628163328.GA33408@www.zefox.net> <51e208b4-9f14-58f7-1e70-6ef8db2c0bed@sentry.org> <20180629155131.GA35717@www.zefox.net> <20180629233937.GC35717@www.zefox.net> <0f137e06-214a-3e8c-a216-f061ec04ac2c@sentry.org> <20180630005145.GA43801@www.zefox.net> <6f3406e2-71f3-d0c2-2b65-703e1a1d3c25@sentry.org> <8e92b2b7-da61-3efb-7231-9fac76b2c1d4@sentry.org> Message-ID: <2deaaec3-f78f-0b09-5ca7-27e14c6979f9@sentry.org> Date: Wed, 4 Jul 2018 07:09:49 +1000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.3 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.2 (shadow.sentry.org [0.0.0.0]); Wed, 04 Jul 2018 07:09:49 +1000 (AEST) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jul 2018 21:10:00 -0000 Ok, the final, final swap experiment. I created a 2G swap partition on the SDCard: gpart show => 63 31116225 mmcsd0 MBR (15G) 63 2016 - free - (1.0M) 2079 102400 1 fat32lba [active] (50M) 104479 31011809 2 freebsd (15G) => 0 31011809 mmcsd0s2 BSD (15G) 0 25165824 1 freebsd-ufs (12G) 25165824 4194304 2 freebsd-swap (2.0G) 29360128 1651681 - free - (806M) and, yes, it still died during make -j4 buildworld: Jul 3 22:15:24 rpi3 kernel: pid 57011 (c++), uid 0, was killed: out of swap space (I forgot to start the logging script, so no stats). Conclusion: The only way to buildworld on the RPi3B+ is to use an external USB mechanical hard disk (my hybrid Seagate 500G 2.5" drive required a powered USB hub). No issues on a RPi2B v1.1 with swap and /usr on a USB memory key. From owner-freebsd-arm@freebsd.org Wed Jul 4 00:45:47 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 62D31103D0EB for ; Wed, 4 Jul 2018 00:45:47 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (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 D88517B027 for ; Wed, 4 Jul 2018 00:45:46 +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 w640jtbB062148 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 3 Jul 2018 17:45:56 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w640jtPU062147; Tue, 3 Jul 2018 17:45:55 -0700 (PDT) (envelope-from fbsd) Date: Tue, 3 Jul 2018 17:45:54 -0700 From: bob prohaska To: Trev Cc: freebsd-arm@freebsd.org, bob prohaska Subject: Re: RPI3 swap experiments Message-ID: <20180704004554.GA61273@www.zefox.net> References: <51e208b4-9f14-58f7-1e70-6ef8db2c0bed@sentry.org> <20180629155131.GA35717@www.zefox.net> <20180629233937.GC35717@www.zefox.net> <0f137e06-214a-3e8c-a216-f061ec04ac2c@sentry.org> <20180630005145.GA43801@www.zefox.net> <6f3406e2-71f3-d0c2-2b65-703e1a1d3c25@sentry.org> <8e92b2b7-da61-3efb-7231-9fac76b2c1d4@sentry.org> <2deaaec3-f78f-0b09-5ca7-27e14c6979f9@sentry.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2deaaec3-f78f-0b09-5ca7-27e14c6979f9@sentry.org> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jul 2018 00:45:47 -0000 On Wed, Jul 04, 2018 at 07:09:49AM +1000, Trev wrote: > Ok, the final, final swap experiment. > > I created a 2G swap partition on the SDCard: > > gpart show > => 63 31116225 mmcsd0 MBR (15G) > 63 2016 - free - (1.0M) > 2079 102400 1 fat32lba [active] (50M) > 104479 31011809 2 freebsd (15G) > > => 0 31011809 mmcsd0s2 BSD (15G) > 0 25165824 1 freebsd-ufs (12G) > 25165824 4194304 2 freebsd-swap (2.0G) > 29360128 1651681 - free - (806M) > > and, yes, it still died during make -j4 buildworld: > > Jul 3 22:15:24 rpi3 kernel: pid 57011 (c++), uid 0, was killed: out of > swap space > > (I forgot to start the logging script, so no stats). > > Conclusion: The only way to buildworld on the RPi3B+ is to use an > external USB mechanical hard disk (my hybrid Seagate 500G 2.5" drive > required a powered USB hub). No issues on a RPi2B v1.1 with swap and > /usr on a USB memory key. This is getting curiouser and curioser. I just set up my Pi3 with new storage media using the June 28 snapshot. Swap, /var, /tmp and /usr are on a new (different model number but same specs) Sandisk Extreme Go 64 GB USB flash drive. By all history, buildworld should have failed, but didn't. The system updated itself to r335835 without a hitch. However, running Peter Holms' stress2 suite using the all.sh script did, after fifteen hours on r335835, produce a crash that superficially looks similar to those seen earlier (g_vfs_done(), (da0:umass-sim0:0:0:0):, vm_fault:) ending with Stopped at cluster_write+0x228: ldr x9, [x8, #80]! It's tempting to attribute the difference in behavior to the different USB flash drives. The one that gave the most trouble is labeled Sandisk Extreme Go USB 3.1 model # SDCZ800-064G The one in use now, which seems better-behaved, is labeled Sandisk Extreme USB 3.0 model SDCZ80-064G and is some months older. The practical difference is that the Extreme Go model has replaced the ordinary Extreme, which is now scarce. It looks as if FreeBSD distinguishes them by name but not quirk: The troublemaker (Extreme G USB 3.1) is recognized as da0 at umass-sim0 bus 0 scbus0 target 0 lun 0 da0: Removable Direct Access SPC-4 SCSI device da0: Serial Number 4C530001211014123270 da0: 40.000MB/s transfers da0: 59840MB (122552320 512 byte sectors) da0: quirks=0x2 while the one that works better (Extreme USB 3.0) reports da1 at umass-sim1 bus 1 scbus1 target 0 lun 0 da1: Removable Direct Access SPC-4 SCSI device da1: Serial Number AA010428162242131598 da1: 40.000MB/s transfers da1: 59836MB (122544516 512 byte sectors) da1: quirks=0x2 Details are at http://www.zefox.net/~fbsd/rpi3/swaptests/r335835/ Thanks for reading! bob prohaska From owner-freebsd-arm@freebsd.org Wed Jul 4 04:16:26 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6FAAA102B6FA for ; Wed, 4 Jul 2018 04:16:26 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (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 E524D8408D for ; Wed, 4 Jul 2018 04:16:25 +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 w644GeR6063100 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 3 Jul 2018 21:16:41 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w644GdjG063099; Tue, 3 Jul 2018 21:16:39 -0700 (PDT) (envelope-from fbsd) Date: Tue, 3 Jul 2018 21:16:39 -0700 From: bob prohaska To: freebsd-arm@freebsd.org Subject: gpart trouble Message-ID: <20180704041559.GA63030@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.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jul 2018 04:16:26 -0000 I want to add some swap partitions to the June 28th RPI3 snapshot image on microSD. Growfs was suppressed, so the card has 12 GB of free space: Enter full pathname of shell or RETURN for /bin/sh: Cannot read termcap database; using dumb terminal settings. # mount -o rw / # gpart show mmcsd0 => 63 31116225 mmcsd0 MBR (15G) 63 2016 - free - (1.0M) 2079 102312 1 fat32lba [active] (50M) 104391 5138469 2 freebsd (2.5G) 5242860 25873428 - free - (12G) # gpart add -t freebsd-swap -s 1G mmcsd0 gpart: Invalid argument # gpart add -t freebsd-swap -s 1G /dev/mmcsd0 gpart: Invalid argument # gpart add -t freebsd-swap -s 1GB -l swap mmcsd0 gpart: Invalid argument # It seems to me this worked with an earlier snapshot, has something changed? Thanks for reading! bob prohaska From owner-freebsd-arm@freebsd.org Wed Jul 4 04:23:50 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C253A102C18C for ; Wed, 4 Jul 2018 04:23:50 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (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 3D5C9845FA for ; Wed, 4 Jul 2018 04:23:49 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id w644Nj8M041296; Tue, 3 Jul 2018 21:23:45 -0700 (PDT) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd-rwg@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id w644NirT041295; Tue, 3 Jul 2018 21:23:44 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201807040423.w644NirT041295@pdx.rh.CN85.dnsmgr.net> Subject: Re: gpart trouble In-Reply-To: <20180704041559.GA63030@www.zefox.net> To: bob prohaska Date: Tue, 3 Jul 2018 21:23:43 -0700 (PDT) CC: freebsd-arm@freebsd.org X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jul 2018 04:23:50 -0000 > > I want to add some swap partitions to the June 28th RPI3 snapshot image on microSD. > Growfs was suppressed, so the card has 12 GB of free space: > > Enter full pathname of shell or RETURN for /bin/sh: > Cannot read termcap database; > using dumb terminal settings. > # mount -o rw / > # gpart show mmcsd0 > => 63 31116225 mmcsd0 MBR (15G) ^^^^^ > 63 2016 - free - (1.0M) > 2079 102312 1 fat32lba [active] (50M) > 104391 5138469 2 freebsd (2.5G) > 5242860 25873428 - free - (12G) > > # gpart add -t freebsd-swap -s 1G mmcsd0 > gpart: Invalid argument > # gpart add -t freebsd-swap -s 1G /dev/mmcsd0 > gpart: Invalid argument > # gpart add -t freebsd-swap -s 1GB -l swap mmcsd0 > gpart: Invalid argument > # I do not believe MBR supports "freebsd-swp" as a partition type, we only have 0x165 as a FreeBSD type. I think you want to create a freebsd type at slice 3, and inside that you want to create a freebsd-swp. I am no good with gpart, but fdisk and bsdlabel can do this. > > It seems to me this worked with an earlier snapshot, has something changed? > > Thanks for reading! > > bob prohaska > > _______________________________________________ > 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" > -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-arm@freebsd.org Wed Jul 4 04:29:33 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 95669102C8C0 for ; Wed, 4 Jul 2018 04:29:33 +0000 (UTC) (envelope-from sparvu@kronometrix.org) Received: from mail.kronometrix.org (mail.kronometrix.org [95.85.46.90]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.kronometrix.org", Issuer "mail.kronometrix.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 12550847AA for ; Wed, 4 Jul 2018 04:29:32 +0000 (UTC) (envelope-from sparvu@kronometrix.org) Received: from [192.168.1.50] (87-100-230-21.bb.dnainternet.fi [87.100.230.21]) (authenticated bits=0) by mail.kronometrix.org (8.15.2/8.15.2) with ESMTPSA id w644TUqa016712 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 4 Jul 2018 04:29:30 GMT (envelope-from sparvu@kronometrix.org) X-Authentication-Warning: mail: Host 87-100-230-21.bb.dnainternet.fi [87.100.230.21] claimed to be [192.168.1.50] From: Stefan Parvu Message-Id: Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\)) Subject: Re: FreeBSD on latest RPI3+ Date: Wed, 4 Jul 2018 07:29:24 +0300 In-Reply-To: Cc: freebsd-arm@freebsd.org To: Ronald Klop References: <9E4BB8D2-DCDC-4C69-BE37-1D0896295B56@kronometrix.org> <1DAB1D3D-DEA3-4904-A290-0EDC4B25217A@kronometrix.org> X-Mailer: Apple Mail (2.3445.8.2) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jul 2018 04:29:33 -0000 > Try 'kldload if_muge' as root. yep. thanks. why the module is not automatically loaded during boot ? now Im able to ssh. freebsd@generic:~ % uname -a FreeBSD generic 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r335760: Thu Jun 28 = 16:32:04 UTC 2018 = root@releng3.nyi.freebsd.org:/usr/obj/usr/src/arm64.aarch64/sys/GENERIC = arm64 From owner-freebsd-arm@freebsd.org Wed Jul 4 04:40:23 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B1B27102DB3A for ; Wed, 4 Jul 2018 04:40:23 +0000 (UTC) (envelope-from sparvu@kronometrix.org) Received: from mail.kronometrix.org (mail.kronometrix.org [95.85.46.90]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.kronometrix.org", Issuer "mail.kronometrix.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 1C7C085254 for ; Wed, 4 Jul 2018 04:40:23 +0000 (UTC) (envelope-from sparvu@kronometrix.org) Received: from [192.168.1.50] (87-100-230-21.bb.dnainternet.fi [87.100.230.21]) (authenticated bits=0) by mail.kronometrix.org (8.15.2/8.15.2) with ESMTPSA id w644eLON016820 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Wed, 4 Jul 2018 04:40:21 GMT (envelope-from sparvu@kronometrix.org) X-Authentication-Warning: mail: Host 87-100-230-21.bb.dnainternet.fi [87.100.230.21] claimed to be [192.168.1.50] From: Stefan Parvu Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\)) Subject: RPI3B+ cpu frequency Message-Id: <087D6629-FB9A-476A-9455-BBB6D4F802C0@kronometrix.org> Date: Wed, 4 Jul 2018 07:40:13 +0300 To: freebsd-arm@freebsd.org X-Mailer: Apple Mail (2.3445.8.2) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jul 2018 04:40:23 -0000 Hi, I understood the last RPI3B+ ships with a 1.4GHz 64-bit cpu. Right ? = Booting FreeBSD 12.0 current shows that I have access only to 600MHz. A bit confused, since = this was happening as well on older models, if Im not wrong: do I need to turn on the Turbo = mode to get access to the full speed of the CPU or what ? Why FreeBSD does not boot and by default use the CPU at 1.4GHz ?=20 Thanks, Stefan= From owner-freebsd-arm@freebsd.org Wed Jul 4 04:56:36 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C8AC9102F222 for ; Wed, 4 Jul 2018 04:56:36 +0000 (UTC) (envelope-from sparvu@kronometrix.org) Received: from mail.kronometrix.org (mail.kronometrix.org [95.85.46.90]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.kronometrix.org", Issuer "mail.kronometrix.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 53B6C85F2D for ; Wed, 4 Jul 2018 04:56:36 +0000 (UTC) (envelope-from sparvu@kronometrix.org) Received: from [192.168.1.50] (87-100-230-21.bb.dnainternet.fi [87.100.230.21]) (authenticated bits=0) by mail.kronometrix.org (8.15.2/8.15.2) with ESMTPSA id w644uYkO016988 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 4 Jul 2018 04:56:35 GMT (envelope-from sparvu@kronometrix.org) X-Authentication-Warning: mail: Host 87-100-230-21.bb.dnainternet.fi [87.100.230.21] claimed to be [192.168.1.50] Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\)) Subject: Re: FreeBSD on latest RPI3+ From: Stefan Parvu In-Reply-To: Date: Wed, 4 Jul 2018 07:56:28 +0300 Cc: freebsd-arm@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <49103E03-8C65-4AD7-8B93-FACBCA10CF87@kronometrix.org> References: <9E4BB8D2-DCDC-4C69-BE37-1D0896295B56@kronometrix.org> <1DAB1D3D-DEA3-4904-A290-0EDC4B25217A@kronometrix.org> To: Ronald Klop X-Mailer: Apple Mail (2.3445.8.2) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jul 2018 04:56:37 -0000 >=20 > yep. thanks. why the module is not automatically loaded during boot ? > now Im able to ssh. but it looks after reboot, I need to manually load again the driver. do = I need to wait for another snapshot version in order the get the network properly up and = functioning ?=20 yes, correct as well: I got another MAC address, and another IPv4 from = internal DHCP =20 server. Stefan= From owner-freebsd-arm@freebsd.org Wed Jul 4 05:07:40 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 79B1C103001D for ; Wed, 4 Jul 2018 05:07:40 +0000 (UTC) (envelope-from sparvu@kronometrix.org) Received: from mail.kronometrix.org (mail.kronometrix.org [95.85.46.90]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.kronometrix.org", Issuer "mail.kronometrix.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 0706186482 for ; Wed, 4 Jul 2018 05:07:39 +0000 (UTC) (envelope-from sparvu@kronometrix.org) Received: from [192.168.1.50] (87-100-230-21.bb.dnainternet.fi [87.100.230.21]) (authenticated bits=0) by mail.kronometrix.org (8.15.2/8.15.2) with ESMTPSA id w6457c9C017098 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Wed, 4 Jul 2018 05:07:38 GMT (envelope-from sparvu@kronometrix.org) X-Authentication-Warning: mail: Host 87-100-230-21.bb.dnainternet.fi [87.100.230.21] claimed to be [192.168.1.50] From: Stefan Parvu Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\)) Subject: RPI3B+ UFS filesystem issues Message-Id: Date: Wed, 4 Jul 2018 08:07:32 +0300 To: freebsd-arm@freebsd.org X-Mailer: Apple Mail (2.3445.8.2) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jul 2018 05:07:40 -0000 Are these signal of troubles form the filesystem layer ? Im using a = Transcend 64GB=20 https://fi.transcend-info.com/Products/No-697. Dont know if I can = benefit from this card of its full speed on RPI3B+ . Im using FreeBSD 12.0 current latest 28 June snapshot: FreeBSD generic 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r335760: Thu Jun 28 = 16:32:04 UTC 2018 = root@releng3.nyi.freebsd.org:/usr/obj/usr/src/arm64.aarch64/sys/GENERIC = arm64 lock order reversal: 1st 0xffff000040d299f0 bufwait (bufwait) @ = /usr/src/sys/kern/vfs_bio.c:3916 2nd 0xfffffd001582ba00 dirhash (dirhash) @ = /usr/src/sys/ufs/ufs/ufs_dirhash.c:289 stack backtrace: #0 0xffff0000003eb5e4 at witness_debugger+0x64 #1 0xffff00000038f2cc at _sx_xlock+0x7c #2 0xffff0000006124d4 at ufsdirhash_add+0x38 #3 0xffff000000614f68 at ufs_direnter+0x3b0 #4 0xffff00000061d43c at ufs_makeinode+0x4b8 #5 0xffff000000619b14 at ufs_create+0x38 #6 0xffff0000006ccf10 at VOP_CREATE_APV+0xac #7 0xffff00000045d9c4 at vn_open_cred+0x264 #8 0xffff000000456d00 at kern_openat+0x208 #9 0xffff000000696128 at do_el0_sync+0x4b0 #10 0xffff00000067c9f0 at handle_el0_sync+0x74 lock order reversal: 1st 0xfffffd00038a39c8 ufs (ufs) @ = /usr/src/sys/ufs/ffs/ffs_vfsops.c:1677 2nd 0xffff000040d299f0 bufwait (bufwait) @ = /usr/src/sys/ufs/ffs/ffs_vnops.c:282 3rd 0xfffffd00038a37e8 ufs (ufs) @ /usr/src/sys/kern/vfs_subr.c:2572 stack backtrace: #0 0xffff0000003eb5e4 at witness_debugger+0x64 #1 0xffff00000035c340 at lockmgr_xlock_hard+0x6c #2 0xffff00000035cbbc at __lockmgr_args+0x4ac #3 0xffff00000060da28 at ffs_lock+0x88 #4 0xffff0000006cfc58 at VOP_LOCK1_APV+0xac #5 0xffff00000045e050 at _vn_lock+0x64 #6 0xffff00000044e5b8 at vget+0x78 #7 0xffff0000004413bc at vfs_hash_get+0xec #8 0xffff000000609a58 at ffs_vgetf+0x44 #9 0xffff000000600698 at softdep_sync_buf+0x9f4 #10 0xffff00000060e764 at ffs_syncvnode+0x26c #11 0xffff0000005e8738 at ffs_truncate+0x6b4 #12 0xffff000000615330 at ufs_direnter+0x778 #13 0xffff00000061d43c at ufs_makeinode+0x4b8 #14 0xffff000000619b14 at ufs_create+0x38 #15 0xffff0000006ccf10 at VOP_CREATE_APV+0xac #16 0xffff00000045d9c4 at vn_open_cred+0x264 #17 0xffff000000456d00 at kern_openat+0x208 Thank you, Stefan= From owner-freebsd-arm@freebsd.org Wed Jul 4 05:23:45 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2DD8C103132D for ; Wed, 4 Jul 2018 05:23:45 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (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 7F38786DB1 for ; Wed, 4 Jul 2018 05:23:44 +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 w645NwWm063318 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 3 Jul 2018 22:23:59 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w645NwTp063317; Tue, 3 Jul 2018 22:23:58 -0700 (PDT) (envelope-from fbsd) Date: Tue, 3 Jul 2018 22:23:57 -0700 From: bob prohaska To: "Rodney W. Grimes" Cc: freebsd-arm@freebsd.org, bob prohaska Subject: Re: gpart trouble Message-ID: <20180704052357.GA63177@www.zefox.net> References: <20180704041559.GA63030@www.zefox.net> <201807040423.w644NirT041295@pdx.rh.CN85.dnsmgr.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201807040423.w644NirT041295@pdx.rh.CN85.dnsmgr.net> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jul 2018 05:23:45 -0000 On Tue, Jul 03, 2018 at 09:23:43PM -0700, Rodney W. Grimes wrote: > > > > I want to add some swap partitions to the June 28th RPI3 snapshot image on microSD. > > Growfs was suppressed, so the card has 12 GB of free space: > > > > Enter full pathname of shell or RETURN for /bin/sh: > > Cannot read termcap database; > > using dumb terminal settings. > > # mount -o rw / > > # gpart show mmcsd0 > > => 63 31116225 mmcsd0 MBR (15G) > ^^^^^ > > 63 2016 - free - (1.0M) > > 2079 102312 1 fat32lba [active] (50M) > > 104391 5138469 2 freebsd (2.5G) > > 5242860 25873428 - free - (12G) > > > > # gpart add -t freebsd-swap -s 1G mmcsd0 > > gpart: Invalid argument > > # gpart add -t freebsd-swap -s 1G /dev/mmcsd0 > > gpart: Invalid argument > > # gpart add -t freebsd-swap -s 1GB -l swap mmcsd0 > > gpart: Invalid argument > > # > > I do not believe MBR supports "freebsd-swp" as a > partition type, we only have 0x165 as a FreeBSD > type. > > I think you want to create a freebsd type at slice 3, > and inside that you want to create a freebsd-swp. > Maybe that's what I did, I remember the frustration, but not the details 8-) > I am no good with gpart, but fdisk and bsdlabel can do this. > Oddly enough, neither seems to be installed, though both are present in /usr/src/sbin. Both compiled and installed manually without reported errors. Neither seems able to read the boot microSD card, reporting "invalid fdisk partition table found" and "no valid label found" for bsdlabel. If anybody's got ideas I'm all ears. Might it be helpful to put the card in a USB reader and modify it when it's not booted? I don't remember doing that, but could have. Thanks for reading, bob prohaska > > > > It seems to me this worked with an earlier snapshot, has something changed? > > > > Thanks for reading! > > > > bob prohaska > > > > _______________________________________________ > > 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" > > > > -- > Rod Grimes rgrimes@freebsd.org From owner-freebsd-arm@freebsd.org Wed Jul 4 08:47:37 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 933E31042220 for ; Wed, 4 Jul 2018 08:47:37 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 31A4B8EB0B for ; Wed, 4 Jul 2018 08:47:37 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 6F6C020EDE for ; Wed, 4 Jul 2018 08:47:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w648laN3089623 for ; Wed, 4 Jul 2018 08:47:36 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w648lagA089622 for freebsd-arm@FreeBSD.org; Wed, 4 Jul 2018 08:47:36 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-arm@FreeBSD.org Subject: [Bug 229507] src/sys/arm/cavium/cns11xx/econa.c:392: array index out of range ? Date: Wed, 04 Jul 2018 08:47:36 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: arm X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: dcb314@hotmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-arm@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jul 2018 08:47:37 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D229507 Bug ID: 229507 Summary: src/sys/arm/cavium/cns11xx/econa.c:392: array index out of range ? Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: arm Assignee: freebsd-arm@FreeBSD.org Reporter: dcb314@hotmail.com src/sys/arm/cavium/cns11xx/econa.c:392]: (error) Array 'intc_trigger_table[= 25]' accessed at index 31, which is out of bounds. Source code is for (i =3D 0; i < 32; i++) { if (intc_trigger_table[i].mode !=3D INTC_TRIGGER_UNKNOWN) { Compiling this code with compiler flag -D_FORTIFY_SOURCE=3D2 would also find this problem. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-arm@freebsd.org Wed Jul 4 08:55:55 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 15C0C1042C4E for ; Wed, 4 Jul 2018 08:55:55 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 99A2D8F00A for ; Wed, 4 Jul 2018 08:55:54 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id CBC6021038 for ; Wed, 4 Jul 2018 08:55:53 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w648trB9006944 for ; Wed, 4 Jul 2018 08:55:53 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w648trPg006942 for freebsd-arm@FreeBSD.org; Wed, 4 Jul 2018 08:55:53 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-arm@FreeBSD.org Subject: [Bug 229508] src/sys/arm/freescale/imx/imx_gpio.c:856: array index out of bounds ? Date: Wed, 04 Jul 2018 08:55:53 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: arm X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: dcb314@hotmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-arm@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jul 2018 08:55:55 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D229508 Bug ID: 229508 Summary: src/sys/arm/freescale/imx/imx_gpio.c:856: array index out of bounds ? Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: arm Assignee: freebsd-arm@FreeBSD.org Reporter: dcb314@hotmail.com src/sys/arm/freescale/imx/imx_gpio.c:856]: (error) Array 'sc->gpio_ih[2]' accessed at index 2, which is out of bounds. Source code is for (irq =3D 1; irq <=3D 2; irq++) { if (sc->gpio_ih[irq]) but void *gpio_ih[2]; --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-arm@freebsd.org Wed Jul 4 09:45:49 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5BB841022722 for ; Wed, 4 Jul 2018 09:45:49 +0000 (UTC) (envelope-from herbert@gojira.at) Received: from mail.bsd4all.net (mail.bsd4all.net [IPv6:2a01:4f8:191:217b::25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.bsd4all.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EC9BD712A2 for ; Wed, 4 Jul 2018 09:45:48 +0000 (UTC) (envelope-from herbert@gojira.at) Date: Wed, 4 Jul 2018 11:45:39 +0200 From: "Herbert J. Skuhra" To: freebsd-arm@freebsd.org Subject: Re: gpart trouble Message-ID: <20180704094539.GA70815@mail.bsd4all.net> References: <20180704041559.GA63030@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180704041559.GA63030@www.zefox.net> User-Agent: Mutt/1.10.0 (2018-05-17) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jul 2018 09:45:49 -0000 On Tue, Jul 03, 2018 at 09:16:39PM -0700, bob prohaska wrote: > > I want to add some swap partitions to the June 28th RPI3 snapshot image on microSD. > Growfs was suppressed, so the card has 12 GB of free space: > > Enter full pathname of shell or RETURN for /bin/sh: > Cannot read termcap database; > using dumb terminal settings. > # mount -o rw / > # gpart show mmcsd0 > => 63 31116225 mmcsd0 MBR (15G) > 63 2016 - free - (1.0M) > 2079 102312 1 fat32lba [active] (50M) > 104391 5138469 2 freebsd (2.5G) > 5242860 25873428 - free - (12G) > > # gpart add -t freebsd-swap -s 1G mmcsd0 > gpart: Invalid argument > # gpart add -t freebsd-swap -s 1G /dev/mmcsd0 > gpart: Invalid argument > # gpart add -t freebsd-swap -s 1GB -l swap mmcsd0 > gpart: Invalid argument Try: # gpart show mmcsd0s2 # gpart resize -i 2 mmcsd0 # gpart add -t freebsd-swap -s 1GB mmcsd0s2 -- Herbert From owner-freebsd-arm@freebsd.org Wed Jul 4 09:49:32 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4546E1022CD8 for ; Wed, 4 Jul 2018 09:49:32 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: from hraggstad.unrelenting.technology (hraggstad.unrelenting.technology [71.19.146.151]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hraggstad.unrelenting.technology", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B845271463 for ; Wed, 4 Jul 2018 09:49:31 +0000 (UTC) (envelope-from greg@unrelenting.technology) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=unrelenting.technology; h=date:from:subject:to:message-id; s=default; bh=n3PYRXK/0czL6dfOQu1iB6peWP1L2LJIww/X5gkBNr0=; b=JVE0fLRDoNua3RaklM7WoLPAvect/kXx/wKHK4hDc1aEetEOWsK3NlVC5IaWwbsA+3qVcMFwEdW/mBTk4iRVJAUOf1PRM3LT2HWJTftaAE20wmZnm7tKUxINgAsQtuCIPFSvxbEACIHo2No8IX+8a4gy4XoLbbVjRAb2z5CuRdI= Received: by hraggstad.unrelenting.technology (OpenSMTPD) with ESMTPSA id c83759f2 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Wed, 4 Jul 2018 09:49:21 +0000 (UTC) Date: Wed, 04 Jul 2018 12:49:16 +0300 From: Greg V Subject: Re: RPI3B+ cpu frequency To: Stefan Parvu Cc: freebsd-arm@freebsd.org Message-Id: <1530697756.1544.0@hraggstad.unrelenting.technology> In-Reply-To: <087D6629-FB9A-476A-9455-BBB6D4F802C0@kronometrix.org> References: <087D6629-FB9A-476A-9455-BBB6D4F802C0@kronometrix.org> X-Mailer: geary/0.12.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jul 2018 09:49:32 -0000 On Wed, Jul 4, 2018 at 7:40 AM, Stefan Parvu wrote: > Hi, > > I understood the last RPI3B+ ships with a 1.4GHz 64-bit cpu. Right ? > Booting FreeBSD 12.0 > current shows that I have access only to 600MHz. A bit confused, > since this was happening as > well on older models, if Im not wrong: do I need to turn on the Turbo > mode to get access to > the full speed of the CPU or what ? > > Why FreeBSD does not boot and by default use the CPU at 1.4GHz ? Hi! You should run the 'powerd' service to make it boost to max frequency under load. Or you can force_turbo in config.txt to make the Pi always run at full speed (and waste power). From owner-freebsd-arm@freebsd.org Wed Jul 4 10:41:03 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5E8F81027917 for ; Wed, 4 Jul 2018 10:41:03 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F0B0C732B6 for ; Wed, 4 Jul 2018 10:41:02 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 4E7C121E21 for ; Wed, 4 Jul 2018 10:41:02 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w64Af2fD092079 for ; Wed, 4 Jul 2018 10:41:02 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w64Af2tq092078 for freebsd-arm@FreeBSD.org; Wed, 4 Jul 2018 10:41:02 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-arm@FreeBSD.org Subject: [Bug 229510] src/sys/arm/freescale/vybrid/vf_ehci.c:393: duplicate condition ? Date: Wed, 04 Jul 2018 10:41:00 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: arm X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: dcb314@hotmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-arm@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jul 2018 10:41:03 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D229510 Bug ID: 229510 Summary: src/sys/arm/freescale/vybrid/vf_ehci.c:393: duplicate condition ? Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: arm Assignee: freebsd-arm@FreeBSD.org Reporter: dcb314@hotmail.com src/sys/arm/freescale/vybrid/vf_ehci.c:393] -> [src/sys/arm/freescale/vybrid/vf_ehci.c:399]: (warning) Identical condition 'sc->sc_flags&EHCI_SCFLG_DONEINIT', second condition is always false Source code is if (sc->sc_flags & EHCI_SCFLG_DONEINIT) return (0); /* * only call ehci_detach() after ehci_init() */ if (sc->sc_flags & EHCI_SCFLG_DONEINIT) { ehci_detach(sc); sc->sc_flags &=3D ~EHCI_SCFLG_DONEINIT; } Is the sc_flags field volatile and is changed by some other thread ? --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-arm@freebsd.org Wed Jul 4 11:22:53 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 616F1102AD86 for ; Wed, 4 Jul 2018 11:22:53 +0000 (UTC) (envelope-from trev@sentry.org) Received: from shadow.sentry.org (shadow.sentry.org [210.8.237.106]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "shadow.sentry.org", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 926D47493A for ; Wed, 4 Jul 2018 11:22:52 +0000 (UTC) (envelope-from trev@sentry.org) Received: from shadow.sentry.org (localhost [127.0.0.1]) by shadow.sentry.org (8.15.2/8.15.2) with ESMTP id w64BMlUp060313 for ; Wed, 4 Jul 2018 21:22:47 +1000 (AEST) (envelope-from trev@sentry.org) Subject: Re: gpart trouble To: freebsd-arm@freebsd.org References: <20180704041559.GA63030@www.zefox.net> <201807040423.w644NirT041295@pdx.rh.CN85.dnsmgr.net> <20180704052357.GA63177@www.zefox.net> From: Trev Organization: Sentry Message-ID: <3afd0c1c-a594-51a5-d320-5010796b7491@sentry.org> Date: Wed, 4 Jul 2018 21:22:47 +1000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.3 MIME-Version: 1.0 In-Reply-To: <20180704052357.GA63177@www.zefox.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.2 (shadow.sentry.org [0.0.0.0]); Wed, 04 Jul 2018 21:22:47 +1000 (AEST) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jul 2018 11:22:53 -0000 bob prohaska wrote on 04/07/2018 15:23: > On Tue, Jul 03, 2018 at 09:23:43PM -0700, Rodney W. Grimes wrote: >>> >>> I want to add some swap partitions to the June 28th RPI3 snapshot image on microSD. >>> Growfs was suppressed, so the card has 12 GB of free space: >>> >>> Enter full pathname of shell or RETURN for /bin/sh: >>> Cannot read termcap database; >>> using dumb terminal settings. >>> # mount -o rw / >>> # gpart show mmcsd0 >>> => 63 31116225 mmcsd0 MBR (15G) >> ^^^^^ >>> 63 2016 - free - (1.0M) >>> 2079 102312 1 fat32lba [active] (50M) >>> 104391 5138469 2 freebsd (2.5G) >>> 5242860 25873428 - free - (12G) >>> >>> # gpart add -t freebsd-swap -s 1G mmcsd0 >>> gpart: Invalid argument >>> # gpart add -t freebsd-swap -s 1G /dev/mmcsd0 >>> gpart: Invalid argument >>> # gpart add -t freebsd-swap -s 1GB -l swap mmcsd0 >>> gpart: Invalid argument You need to create BSD disklabel slice along the lines of gpart create -s BSD -n 8 mmmcsd0s1 then add the root partition gpart add -t freebsd-ufs -s 10G mmcsd0s1a then add the swap partition gpart add -t freebsd-swap -s 2G mmcsd0s1b Excuse the formatting, I'm interstate with vnc on an iPad mini which involves lots of scrolling. From owner-freebsd-arm@freebsd.org Wed Jul 4 16:17:52 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EBA43101A46F for ; Wed, 4 Jul 2018 16:17:51 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (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 61C7884CB1 for ; Wed, 4 Jul 2018 16:17:51 +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 w64GI5PB065202 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 4 Jul 2018 09:18:06 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w64GI39T065201; Wed, 4 Jul 2018 09:18:03 -0700 (PDT) (envelope-from fbsd) Date: Wed, 4 Jul 2018 09:18:03 -0700 From: bob prohaska To: "Herbert J. Skuhra" Cc: freebsd-arm@freebsd.org, bob prohaska Subject: Re: gpart trouble Message-ID: <20180704161802.GA64982@www.zefox.net> References: <20180704041559.GA63030@www.zefox.net> <20180704094539.GA70815@mail.bsd4all.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180704094539.GA70815@mail.bsd4all.net> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jul 2018 16:17:52 -0000 On Wed, Jul 04, 2018 at 11:45:39AM +0200, Herbert J. Skuhra wrote: > On Tue, Jul 03, 2018 at 09:16:39PM -0700, bob prohaska wrote: > > > > I want to add some swap partitions to the June 28th RPI3 snapshot image on microSD. > > Growfs was suppressed, so the card has 12 GB of free space: > > > > Enter full pathname of shell or RETURN for /bin/sh: > > Cannot read termcap database; > > using dumb terminal settings. > > # mount -o rw / > > # gpart show mmcsd0 > > => 63 31116225 mmcsd0 MBR (15G) > > 63 2016 - free - (1.0M) > > 2079 102312 1 fat32lba [active] (50M) > > 104391 5138469 2 freebsd (2.5G) > > 5242860 25873428 - free - (12G) > > > > # gpart add -t freebsd-swap -s 1G mmcsd0 > > gpart: Invalid argument > > # gpart add -t freebsd-swap -s 1G /dev/mmcsd0 > > gpart: Invalid argument > > # gpart add -t freebsd-swap -s 1GB -l swap mmcsd0 > > gpart: Invalid argument > > Try: > > # gpart show mmcsd0s2 > # gpart resize -i 2 mmcsd0 > # gpart add -t freebsd-swap -s 1GB mmcsd0s2 > That worked exactly as desired. I ran afoul of the distinction between partitions and slices, thinking resize would enlarge both, like growfs. How would one go about suggesting that an example similar to this be added to the gpart man page? There's nothing obviously like it now. As microSD-booted devices become more common increasing numbers of people will encounter the same puzzle. Thank you very much!! bob prohaska From owner-freebsd-arm@freebsd.org Wed Jul 4 17:50:08 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 50ACF10296DB for ; Wed, 4 Jul 2018 17:50:08 +0000 (UTC) (envelope-from ml@netfence.it) Received: from soth.netfence.it (net-2-44-121-52.cust.vodafonedsl.it [2.44.121.52]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mailserver.netfence.it", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B5BCF8A6C1 for ; Wed, 4 Jul 2018 17:50:06 +0000 (UTC) (envelope-from ml@netfence.it) Received: from alamar.ventu (alamar.local.netfence.it [10.1.2.18]) (authenticated bits=0) by soth.netfence.it (8.15.2/8.15.2) with ESMTPSA id w64Hntjf080816 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Wed, 4 Jul 2018 19:50:03 +0200 (CEST) (envelope-from ml@netfence.it) X-Authentication-Warning: soth.netfence.it: Host alamar.local.netfence.it [10.1.2.18] claimed to be alamar.ventu Subject: Re: FreeBSD on latest RPI3+ To: freebsd-arm@freebsd.org References: <9E4BB8D2-DCDC-4C69-BE37-1D0896295B56@kronometrix.org> From: Andrea Venturoli Message-ID: Date: Wed, 4 Jul 2018 19:49:55 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.9.0 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.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jul 2018 17:50:08 -0000 On 07/03/18 17:54, Ronald Klop wrote: > On Mon, 02 Jul 2018 11:17:38 +0200, Stefan Parvu > wrote: > >> Hi, >> >> Do we support already the latest RPI3+ [1] ? Probable that would be >> FreeBSD 12.0 no back porting to FreeBSD 11.x ? > > Yes, I have it running out of the box. Just install the RPI3 FreeBSD > 12/aarch64 snapshot [1][2]. Hello. The OP question was one I was going to ask myself... Specifically, you said 12 works; but does 11.2? bye & Thanks av. From owner-freebsd-arm@freebsd.org Wed Jul 4 18:01:16 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3AAD6102A7B6 for ; Wed, 4 Jul 2018 18:01:16 +0000 (UTC) (envelope-from sparvu@kronometrix.org) Received: from mail.kronometrix.org (mail.kronometrix.org [95.85.46.90]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.kronometrix.org", Issuer "mail.kronometrix.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id B21728AE37 for ; Wed, 4 Jul 2018 18:01:15 +0000 (UTC) (envelope-from sparvu@kronometrix.org) Received: from [192.168.1.50] (87-100-230-21.bb.dnainternet.fi [87.100.230.21]) (authenticated bits=0) by mail.kronometrix.org (8.15.2/8.15.2) with ESMTPSA id w64I1C1l025065 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 4 Jul 2018 18:01:13 GMT (envelope-from sparvu@kronometrix.org) X-Authentication-Warning: mail: Host 87-100-230-21.bb.dnainternet.fi [87.100.230.21] claimed to be [192.168.1.50] Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\)) Subject: Re: RPI3B+ cpu frequency From: Stefan Parvu In-Reply-To: <1530697756.1544.0@hraggstad.unrelenting.technology> Date: Wed, 4 Jul 2018 21:01:07 +0300 Cc: freebsd-arm@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <774A48FB-F78B-46EA-A018-406D465FEF1B@kronometrix.org> References: <087D6629-FB9A-476A-9455-BBB6D4F802C0@kronometrix.org> <1530697756.1544.0@hraggstad.unrelenting.technology> To: Greg V X-Mailer: Apple Mail (2.3445.8.2) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jul 2018 18:01:16 -0000 > Hi! You should run the 'powerd' service to make it boost to max = frequency under load. > Or you can force_turbo in config.txt to make the Pi always run at full = speed (and waste power). right. thanks. running powerd from rc.conf should be just enough. Do I = need to start powerd in certain mode, adaptive or =E2=80=A6 simple using the default it is just = enough !? Stefan= From owner-freebsd-arm@freebsd.org Wed Jul 4 18:02:46 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B8692102AAE3 for ; Wed, 4 Jul 2018 18:02:46 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: from hraggstad.unrelenting.technology (hraggstad.unrelenting.technology [71.19.146.151]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hraggstad.unrelenting.technology", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3BED78B1DE for ; Wed, 4 Jul 2018 18:02:45 +0000 (UTC) (envelope-from greg@unrelenting.technology) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=unrelenting.technology; h=date:from:subject:to:message-id; s=default; bh=RMIbRtkRm9uwDu3Y2b8/J29JyBYR2IOOvOh8/zqzPEM=; b=MZDN0qylQLWV1Z2EHzVEGJsvlYN8Ihf/NSrL2scpJKpjIrR/KtxCJYiWlaFcgHCqlyrFOyhC6x1dBrWvI8YVYq1RU5sDb6lljOYehBZd/nZpIa0l2GRuIxbvqRy3pEvawU1GMwvcKOnLuQEPFAQcd1fZPDMCLtVCFq9rGJdlvIM= Received: by hraggstad.unrelenting.technology (OpenSMTPD) with ESMTPSA id 7756fc0e TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Wed, 4 Jul 2018 18:02:40 +0000 (UTC) Date: Wed, 04 Jul 2018 21:02:35 +0300 From: Greg V Subject: Re: RPI3B+ cpu frequency To: Stefan Parvu Cc: freebsd-arm@freebsd.org Message-Id: <1530727355.1544.3@hraggstad.unrelenting.technology> In-Reply-To: <774A48FB-F78B-46EA-A018-406D465FEF1B@kronometrix.org> References: <087D6629-FB9A-476A-9455-BBB6D4F802C0@kronometrix.org> <1530697756.1544.0@hraggstad.unrelenting.technology> <774A48FB-F78B-46EA-A018-406D465FEF1B@kronometrix.org> X-Mailer: geary/0.12.2 MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jul 2018 18:02:46 -0000 On Wed, Jul 4, 2018 at 9:01 PM, Stefan Parvu =20 wrote: >> Hi! You should run the 'powerd' service to make it boost to max=20 >> frequency under load. >> Or you can force_turbo in config.txt to make the Pi always run at=20 >> full speed (and waste power). >=20 > right. thanks. running powerd from rc.conf should be just enough. Do=20 > I need to start powerd in > certain mode, adaptive or =85 simple using the default it is just=20 > enough !? IIRC, default is hiadaptive (more aggressively staying high than in=20 normal adaptive). Of course that's good enough. = From owner-freebsd-arm@freebsd.org Wed Jul 4 18:03:50 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 79917102AD2E for ; Wed, 4 Jul 2018 18:03:50 +0000 (UTC) (envelope-from sparvu@kronometrix.org) Received: from mail.kronometrix.org (mail.kronometrix.org [95.85.46.90]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.kronometrix.org", Issuer "mail.kronometrix.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 9B1108B419 for ; Wed, 4 Jul 2018 18:03:49 +0000 (UTC) (envelope-from sparvu@kronometrix.org) Received: from [192.168.1.50] (87-100-230-21.bb.dnainternet.fi [87.100.230.21]) (authenticated bits=0) by mail.kronometrix.org (8.15.2/8.15.2) with ESMTPSA id w64I3le2025093 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 4 Jul 2018 18:03:48 GMT (envelope-from sparvu@kronometrix.org) X-Authentication-Warning: mail: Host 87-100-230-21.bb.dnainternet.fi [87.100.230.21] claimed to be [192.168.1.50] Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\)) Subject: Re: RPI3B+ cpu frequency From: Stefan Parvu In-Reply-To: <1530727355.1544.3@hraggstad.unrelenting.technology> Date: Wed, 4 Jul 2018 21:03:42 +0300 Cc: freebsd-arm@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <326C4819-77CC-4254-8D65-6A0EC84AC83C@kronometrix.org> References: <087D6629-FB9A-476A-9455-BBB6D4F802C0@kronometrix.org> <1530697756.1544.0@hraggstad.unrelenting.technology> <774A48FB-F78B-46EA-A018-406D465FEF1B@kronometrix.org> <1530727355.1544.3@hraggstad.unrelenting.technology> To: Greg V X-Mailer: Apple Mail (2.3445.8.2) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jul 2018 18:03:50 -0000 > IIRC, default is hiadaptive (more aggressively staying high than in = normal adaptive). Of course that's good enough. cheers. will experiment.=20 Stefan= From owner-freebsd-arm@freebsd.org Thu Jul 5 11:37:06 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7F07510433F3 for ; Thu, 5 Jul 2018 11:37:06 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1D38A7731C for ; Thu, 5 Jul 2018 11:37:05 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smtp.greenhost.nl ([213.108.110.112]) by smarthost1.greenhost.nl with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from ) id 1fb2ZF-00048Y-Nk; Thu, 05 Jul 2018 13:36:58 +0200 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: "Stefan Parvu" , "Greg V" Cc: freebsd-arm@freebsd.org Subject: Re: RPI3B+ cpu frequency References: <087D6629-FB9A-476A-9455-BBB6D4F802C0@kronometrix.org> <1530697756.1544.0@hraggstad.unrelenting.technology> Date: Thu, 05 Jul 2018 13:37:00 +0200 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Ronald Klop" Message-ID: In-Reply-To: <1530697756.1544.0@hraggstad.unrelenting.technology> User-Agent: Opera Mail/12.16 (FreeBSD) X-Authenticated-As-Hash: 398f5522cb258ce43cb679602f8cfe8b62a256d1 X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: / X-Spam-Score: 0.5 X-Spam-Status: No, score=0.5 required=5.0 tests=ALL_TRUSTED, BAYES_60 autolearn=disabled version=3.4.0 X-Scan-Signature: 12f61b0c8dc8dcc8c992b8e1fde77987 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jul 2018 11:37:06 -0000 On Wed, 04 Jul 2018 11:49:16 +0200, Greg V wrote: > > > On Wed, Jul 4, 2018 at 7:40 AM, Stefan Parvu > wrote: >> Hi, >> I understood the last RPI3B+ ships with a 1.4GHz 64-bit cpu. Right ? >> Booting FreeBSD 12.0 >> current shows that I have access only to 600MHz. A bit confused, since >> this was happening as >> well on older models, if Im not wrong: do I need to turn on the Turbo >> mode to get access to >> the full speed of the CPU or what ? >> Why FreeBSD does not boot and by default use the CPU at 1.4GHz ? > > Hi! You should run the 'powerd' service to make it boost to max > frequency under load. Tried powerd before and it said there was no frequency driver. But today it works. Don't know if it was my mistake or the driver is new. But thanks for the hint in this answer to try again. :-) Running at 1400 now. Regards, Ronald. > > Or you can force_turbo in config.txt to make the Pi always run at full > speed (and waste power). > > _______________________________________________ > 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 Thu Jul 5 12:54:17 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1B90010268D5 for ; Thu, 5 Jul 2018 12:54:17 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [195.149.99.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "raven.bwct.de", Issuer "raven.bwct.de" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 8758B7AC97 for ; Thu, 5 Jul 2018 12:54:16 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.15.2/8.15.2) with ESMTPS id w65CY3UQ038036 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 5 Jul 2018 14:34:04 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cicely.de; s=default; t=1530794045; bh=bpIPaCJ1uWv91Pw9tVlFAZSk1jLMYsJL8EDQYoQ38j0=; h=Date:From:To:Cc:Subject:Reply-To:References:In-Reply-To; b=TrX20JhIx3C6FjXqHSg8ughkP8ecDh/R7X+MpkFTs5YzxqeqJFF/sB4/65B+iWDtl fE0yQaMynwujiW5gKPYg1dgc9iS+uCp89I5lct83TG2Cio5xVyYHqFE6pfU2hBK/Dn qVmfAAGH9Gug02jA9KLYme6NJ/1qkmoeLRo+fnKE= Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.5/8.14.4) with ESMTP id w65CY1jB014174 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 5 Jul 2018 14:34:01 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.15.2/8.15.2) with ESMTPS id w65CY051090980 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 5 Jul 2018 14:34:00 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.15.2/8.15.2/Submit) id w65CY0Uu090979; Thu, 5 Jul 2018 14:34:00 +0200 (CEST) (envelope-from ticso) Date: Thu, 5 Jul 2018 14:34:00 +0200 From: Bernd Walter To: Greg V Cc: Stefan Parvu , freebsd-arm@freebsd.org Subject: Re: RPI3B+ cpu frequency Message-ID: <20180705123359.GA90906@cicely7.cicely.de> Reply-To: ticso@cicely.de References: <087D6629-FB9A-476A-9455-BBB6D4F802C0@kronometrix.org> <1530697756.1544.0@hraggstad.unrelenting.technology> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1530697756.1544.0@hraggstad.unrelenting.technology> X-Operating-System: FreeBSD cicely7.cicely.de 11.0-STABLE amd64 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 autolearn=ham version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jul 2018 12:54:17 -0000 On Wed, Jul 04, 2018 at 12:49:16PM +0300, Greg V wrote: > > > On Wed, Jul 4, 2018 at 7:40 AM, Stefan Parvu > wrote: > >Hi, > > > >I understood the last RPI3B+ ships with a 1.4GHz 64-bit cpu. Right ? > >Booting FreeBSD 12.0 > >current shows that I have access only to 600MHz. A bit confused, > >since this was happening as > >well on older models, if Im not wrong: do I need to turn on the Turbo > >mode to get access to > >the full speed of the CPU or what ? > > > >Why FreeBSD does not boot and by default use the CPU at 1.4GHz ? > > Hi! You should run the 'powerd' service to make it boost to max > frequency under load. Interesting, didn't know it defaults to the llower freq. On a normal 3 model (it was running at 600): dev.cpu.0.freq_levels: 1200/-1 600/-1 dev.cpu.0.freq: 1200 On another normal 3 model (it only has 1200): dev.cpu.0.freq_levels: 1200/-1 dev.cpu.0.freq: 1200 The strange thing about this difference is that the second is running a cloned image, so theoretically it should also offer 600MHz. Maybe the boards were from a different batch. The second without 600MHz is remote, so I can't do any visual inspections. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-arm@freebsd.org Thu Jul 5 16:46:47 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 606BC103C61A; Thu, 5 Jul 2018 16:46:47 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: from gold.funkthat.com (gate2.funkthat.com [208.87.223.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gate2.funkthat.com", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D57BD8861A; Thu, 5 Jul 2018 16:46:46 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: from gold.funkthat.com (localhost [127.0.0.1]) by gold.funkthat.com (8.15.2/8.15.2) with ESMTPS id w65GLI5X040412 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 5 Jul 2018 09:21:18 -0700 (PDT) (envelope-from jmg@gold.funkthat.com) Received: (from jmg@localhost) by gold.funkthat.com (8.15.2/8.15.2/Submit) id w65GLHsu040411; Thu, 5 Jul 2018 09:21:17 -0700 (PDT) (envelope-from jmg) Date: Thu, 5 Jul 2018 09:21:17 -0700 From: John-Mark Gurney To: Warner Losh Cc: "freebsd-arm@freebsd.org" , "freebsd-arch@freebsd.org" Subject: Re: Armeb removal before 12 Message-ID: <20180705162117.GF2884@funkthat.com> Mail-Followup-To: Warner Losh , "freebsd-arm@freebsd.org" , "freebsd-arch@freebsd.org" References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 11.0-RELEASE-p7 amd64 X-PGP-Fingerprint: D87A 235F FB71 1F3F 55B7 ED9B D5FF 5A51 C0AC 3D65 X-Files: The truth is out there X-URL: https://www.funkthat.com/ X-Resume: https://www.funkthat.com/~jmg/resume.html X-TipJar: bitcoin:13Qmb6AeTgQecazTWph4XasEsP7nGRbAPE X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? User-Agent: Mutt/1.6.1 (2016-04-27) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (gold.funkthat.com [127.0.0.1]); Thu, 05 Jul 2018 09:21:18 -0700 (PDT) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jul 2018 16:46:47 -0000 Warner Losh wrote this message on Wed, Jun 13, 2018 at 10:55 -0600: > I'd like to remove armeb before 12.0. As probably the only person still running armeb, I do not object to it's removal... Heck, even my board is still running a much older release... > It's poorly supported today. And I probably won't be putting in any additional work, mainly as those old boards are terribly slow... I can make a board available if someone has a desire to hack on it.. -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-arm@freebsd.org Thu Jul 5 16:57:34 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3AA91103D5A5 for ; Thu, 5 Jul 2018 16:57:34 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x22d.google.com (mail-io0-x22d.google.com [IPv6:2607:f8b0:4001:c06::22d]) (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 C5EE289016 for ; Thu, 5 Jul 2018 16:57:33 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x22d.google.com with SMTP id v26-v6so8361670iog.5 for ; Thu, 05 Jul 2018 09:57:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=aR2YWqwB5nihSzYmwfTgd+eCFPhlZFwzNfDNqFCBN+c=; b=KsnHIQbF6cyPaU/OdXfF1KRZ3g/a+7oqAuUZdz0cDHXodCCdezmc6nDbxeC/LO6HUg xjqhMp6cw9FoJRIb/MD8h3hqEP+MHiJuwhnKMKOGyOIJtZMYu36AQ5MN9ByEVE3gVy93 NIafZkEeQWMVI97IGaWFCPwpbDw2ACYbUbR8cgdWDSEg/oeuRuAVH6oTZLwlOHxh1Oss i4/eLoRgMrkktgg0Y5E5iW0Q0Ui0rgveMygldBzjSUVjXcFYI43jb/h/4Hj9VDqeo5Oi mV7R3TnqEah0QA/gHmbW6OK7fRCqP019p8Ov1Z7IWczo4FahlRnPYzKDR6Ud8iiLfm+H aI2Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=aR2YWqwB5nihSzYmwfTgd+eCFPhlZFwzNfDNqFCBN+c=; b=etIIYe4TcSD9NtiW1wNAFUNhME/Ns8FIopZIGUS9nZ5W5La2L5Hr6GMk2W+E9Z7NeE g3fUWjik57k74gP70urwMa7fHpcsRN9HsaSnyvKeP/kk+3XOvJjLX9HnbhFJpAsGopjz hS137xeoXh3m6DBg0TypooQC+4w00WBVpcJrC/8r4YFbOS3Pks/cp7M2ghSARvlXSkoT jhhIATDy9lCbUD21mrHjW0JnKQ4JtrTuTV5DLpyKcRlWLLSXwquKO5Lr6Gsn2mTecoKk 7ArZwGi2jA7WuWeT/naSqV5W1/xhwH2SwH4EE6fa83a6Ff11VNFJ+uuex7Zj4g3fHnL8 4CLw== X-Gm-Message-State: APt69E1EjJT4skq2Cpy3g3/1aJ9JM0sh1ANkILoBk7SZgWJIiW8sV5tD FVVFISHJ9PtwSlIgG9sGFpQ/GgNI5qEofS9G7bzwtQ== X-Google-Smtp-Source: AAOMgpfXlDWk4qYF/whsoLG97s+qAv7MvzfRIHi22tBJCyULCELbXyxCHryHTXRxAQP7iiDD3zOFJsyMUURf/HjfnOY= X-Received: by 2002:a6b:280a:: with SMTP id o10-v6mr5625783ioo.168.1530809852919; Thu, 05 Jul 2018 09:57:32 -0700 (PDT) MIME-Version: 1.0 References: <20180705162117.GF2884@funkthat.com> In-Reply-To: <20180705162117.GF2884@funkthat.com> From: Warner Losh Date: Thu, 5 Jul 2018 10:57:21 -0600 Message-ID: Subject: Re: Armeb removal before 12 To: freebsd-arm@freebsd.org, "freebsd-arch@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jul 2018 16:57:34 -0000 On Thu, Jul 5, 2018, 11:21 AM John-Mark Gurney wrote: > Warner Losh wrote this message on Wed, Jun 13, 2018 at 10:55 -0600: > > I'd like to remove armeb before 12.0. > > As probably the only person still running armeb, I do not object to > it's removal... Heck, even my board is still running a much older > release... > > > It's poorly supported today. > > And I probably won't be putting in any additional work, mainly as > those old boards are terribly slow... > > I can make a board available if someone has a desire to hack on it.. I still have 2 of them. Newer boards are so much faster... Warner > > From owner-freebsd-arm@freebsd.org Fri Jul 6 16:33:08 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AC5431038281 for ; Fri, 6 Jul 2018 16:33:08 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from mail.baldwin.cx (bigwig.baldwin.cx [96.47.65.170]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 60D9189CDD for ; Fri, 6 Jul 2018 16:33:08 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from John-Baldwins-MacBook-Pro-2.local (ralph.baldwin.cx [66.234.199.215]) by mail.baldwin.cx (Postfix) with ESMTPSA id A974E10AFD4; Fri, 6 Jul 2018 12:33:07 -0400 (EDT) Subject: Re: RPI3B+ UFS filesystem issues To: Stefan Parvu , freebsd-arm@freebsd.org References: From: John Baldwin Message-ID: <3ac73628-4174-1277-67d9-fadd16e50891@FreeBSD.org> Date: Fri, 6 Jul 2018 09:33:06 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (mail.baldwin.cx); Fri, 06 Jul 2018 12:33:07 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.99.2 at mail.baldwin.cx X-Virus-Status: Clean X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jul 2018 16:33:08 -0000 On 7/3/18 10:07 PM, Stefan Parvu wrote: > Are these signal of troubles form the filesystem layer ? Im using a Transcend 64GB > https://fi.transcend-info.com/Products/No-697. Dont know if I can benefit from this > card of its full speed on RPI3B+ . > > Im using FreeBSD 12.0 current latest 28 June snapshot: > FreeBSD generic 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r335760: Thu Jun 28 16:32:04 UTC 2018 root@releng3.nyi.freebsd.org:/usr/obj/usr/src/arm64.aarch64/sys/GENERIC arm64 > > lock order reversal: > 1st 0xffff000040d299f0 bufwait (bufwait) @ /usr/src/sys/kern/vfs_bio.c:3916 > 2nd 0xfffffd001582ba00 dirhash (dirhash) @ /usr/src/sys/ufs/ufs/ufs_dirhash.c:289 > stack backtrace: > #0 0xffff0000003eb5e4 at witness_debugger+0x64 > #1 0xffff00000038f2cc at _sx_xlock+0x7c > #2 0xffff0000006124d4 at ufsdirhash_add+0x38 > #3 0xffff000000614f68 at ufs_direnter+0x3b0 > #4 0xffff00000061d43c at ufs_makeinode+0x4b8 > #5 0xffff000000619b14 at ufs_create+0x38 > #6 0xffff0000006ccf10 at VOP_CREATE_APV+0xac > #7 0xffff00000045d9c4 at vn_open_cred+0x264 > #8 0xffff000000456d00 at kern_openat+0x208 > #9 0xffff000000696128 at do_el0_sync+0x4b0 > #10 0xffff00000067c9f0 at handle_el0_sync+0x74 > lock order reversal: > 1st 0xfffffd00038a39c8 ufs (ufs) @ /usr/src/sys/ufs/ffs/ffs_vfsops.c:1677 > 2nd 0xffff000040d299f0 bufwait (bufwait) @ /usr/src/sys/ufs/ffs/ffs_vnops.c:282 > 3rd 0xfffffd00038a37e8 ufs (ufs) @ /usr/src/sys/kern/vfs_subr.c:2572 > stack backtrace: > #0 0xffff0000003eb5e4 at witness_debugger+0x64 > #1 0xffff00000035c340 at lockmgr_xlock_hard+0x6c > #2 0xffff00000035cbbc at __lockmgr_args+0x4ac > #3 0xffff00000060da28 at ffs_lock+0x88 > #4 0xffff0000006cfc58 at VOP_LOCK1_APV+0xac > #5 0xffff00000045e050 at _vn_lock+0x64 > #6 0xffff00000044e5b8 at vget+0x78 > #7 0xffff0000004413bc at vfs_hash_get+0xec > #8 0xffff000000609a58 at ffs_vgetf+0x44 > #9 0xffff000000600698 at softdep_sync_buf+0x9f4 > #10 0xffff00000060e764 at ffs_syncvnode+0x26c > #11 0xffff0000005e8738 at ffs_truncate+0x6b4 > #12 0xffff000000615330 at ufs_direnter+0x778 > #13 0xffff00000061d43c at ufs_makeinode+0x4b8 > #14 0xffff000000619b14 at ufs_create+0x38 > #15 0xffff0000006ccf10 at VOP_CREATE_APV+0xac > #16 0xffff00000045d9c4 at vn_open_cred+0x264 > #17 0xffff000000456d00 at kern_openat+0x208 No these are known false positives in the lock order verifier. -- John Baldwin From owner-freebsd-arm@freebsd.org Sat Jul 7 21:34:43 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 86D39102DA95 for ; Sat, 7 Jul 2018 21:34:43 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: from gold.funkthat.com (gate2.funkthat.com [208.87.223.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gate2.funkthat.com", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0C93C8D6DE for ; Sat, 7 Jul 2018 21:34:42 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: from gold.funkthat.com (localhost [127.0.0.1]) by gold.funkthat.com (8.15.2/8.15.2) with ESMTPS id w67LYZEc015105 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Sat, 7 Jul 2018 14:34:35 -0700 (PDT) (envelope-from jmg@gold.funkthat.com) Received: (from jmg@localhost) by gold.funkthat.com (8.15.2/8.15.2/Submit) id w67LYZnP015104 for freebsd-arm@FreeBSD.org; Sat, 7 Jul 2018 14:34:35 -0700 (PDT) (envelope-from jmg) Date: Sat, 7 Jul 2018 14:34:35 -0700 From: John-Mark Gurney To: freebsd-arm@FreeBSD.org Subject: docs for allwinner A64/R18 Crypto Engine Message-ID: <20180707213435.GH2884@funkthat.com> Mail-Followup-To: freebsd-arm@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Operating-System: FreeBSD 11.0-RELEASE-p7 amd64 X-PGP-Fingerprint: D87A 235F FB71 1F3F 55B7 ED9B D5FF 5A51 C0AC 3D65 X-Files: The truth is out there X-URL: https://www.funkthat.com/ X-Resume: https://www.funkthat.com/~jmg/resume.html X-TipJar: bitcoin:13Qmb6AeTgQecazTWph4XasEsP7nGRbAPE X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? User-Agent: Mutt/1.6.1 (2016-04-27) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (gold.funkthat.com [127.0.0.1]); Sat, 07 Jul 2018 14:34:35 -0700 (PDT) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Jul 2018 21:34:43 -0000 Does anyone have docs for the crypto engine, or know someone who could get them to me? I just ordered some boards and was thinking I'd look at adding some support for it. Thanks. -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-arm@freebsd.org Sat Jul 7 23:32:45 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C57CD103A864 for ; Sat, 7 Jul 2018 23:32:45 +0000 (UTC) (envelope-from freebsd-arm@sentry.org) Received: from shadow.sentry.org (shadow.sentry.org [210.8.237.106]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "shadow.sentry.org", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E29D871FC7 for ; Sat, 7 Jul 2018 23:32:44 +0000 (UTC) (envelope-from freebsd-arm@sentry.org) Received: from shadow.sentry.org (localhost [127.0.0.1]) by shadow.sentry.org (8.15.2/8.15.2) with ESMTP id w67NWW71046926 for ; Sun, 8 Jul 2018 09:32:33 +1000 (AEST) (envelope-from freebsd-arm@sentry.org) Subject: Re: RPI3 swap experiments From: Trev To: freebsd-arm@freebsd.org References: <20180627194217.GA27793@www.zefox.net> <20180628022457.GA30110@www.zefox.net> <7B9D272D-3EDE-46FA-8A1C-AEE65047167C@yahoo.com> <20180628163328.GA33408@www.zefox.net> <51e208b4-9f14-58f7-1e70-6ef8db2c0bed@sentry.org> <20180629155131.GA35717@www.zefox.net> <20180629233937.GC35717@www.zefox.net> <0f137e06-214a-3e8c-a216-f061ec04ac2c@sentry.org> <20180630005145.GA43801@www.zefox.net> <6f3406e2-71f3-d0c2-2b65-703e1a1d3c25@sentry.org> <8e92b2b7-da61-3efb-7231-9fac76b2c1d4@sentry.org> <2deaaec3-f78f-0b09-5ca7-27e14c6979f9@sentry.org> Message-ID: Date: Sun, 8 Jul 2018 09:32:32 +1000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.3 MIME-Version: 1.0 In-Reply-To: <2deaaec3-f78f-0b09-5ca7-27e14c6979f9@sentry.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.2 (shadow.sentry.org [0.0.0.0]); Sun, 08 Jul 2018 09:32:33 +1000 (AEST) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Jul 2018 23:32:46 -0000 Trev wrote on 04/07/2018 07:09: > Conclusion: The only way to buildworld on the RPi3B+ is to use an > external USB mechanical hard disk (my hybrid Seagate 500G 2.5" drive > required a powered USB hub). No issues on a RPi2B v1.1 with swap and > /usr on a USB memory key. One last experiment occurred to me: I placed a SanDisk 8GB Ultra micro SDCard in a microSD card reader (this one: https://www.amazon.co.uk/MICRO-SD-MICRO-SDHC-MEMORY-READER/dp/B002WKD0CQ ), created a 2G swap partition and ran make -j4 buildworld SUCCESSFULLY! Twice. uname -aKUp FreeBSD rpi3.sentry.org 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r335854: Mon Jul 2 16:03:04 AEST 2018 root@rpi3.sentry.org:/usr/obj/usr/src/arm64.aarch64/sys/RPI3-12.0 arm64 aarch64 1200069 1200069 gpart show -l da0 => 40 15523760 da0 GPT (7.4G) 40 4194304 1 usdswap (2.0G) 4194344 11329456 - free - (5.4G) # Custom /etc/fstab for FreeBSD embedded images /dev/ufs/rootfs / ufs rw,noatime 1 1 /dev/msdosfs/MSDOSBOOT /boot/msdos msdosfs rw,noatime 0 0 md1 /tmp mfs rw,noatime,-s100m 0 0 md2 /var/log mfs rw,noatime,-s15m 0 0 md3 /var/tmp mfs rw,noatime,-s15m 0 0 /dev/da0p1 none swap sw 0 0 da0 at umass-sim0 bus 0 scbus0 target 0 lun 0 da0: Removable Direct Access SCSI device da0: Serial Number 058F63356432 da0: 40.000MB/s transfers da0: 7580MB (15523840 512 byte sectors) da0: quirks=0x2 The only unusual, but apparently harmless, log messages were: Jul 7 15:39:01 rpi3 kernel: swap_pager: indefinite wait buffer: bufobj: 0, blkno: 143089, size: 327 68 Jul 7 17:46:35 rpi3 kernel: swap_pager: indefinite wait buffer: bufobj: 0, blkno: 14712, size: 8192 Jul 7 17:47:21 rpi3 kernel: swap_pager: indefinite wait buffer: bufobj: 0, blkno: 17239, size: 2457 6 Jul 7 17:47:21 rpi3 kernel: swap_pager: indefinite wait buffer: bufobj: 0, blkno: 20737, size: 8192 Jul 7 17:47:21 rpi3 kernel: swap_pager: indefinite wait buffer: bufobj: 0, blkno: 511807, size: 409 6 Jul 7 18:50:34 rpi3 kernel: swap_pager: indefinite wait buffer: bufobj: 0, blkno: 988, size: 4096 Jul 7 18:50:34 rpi3 kernel: swap_pager: indefinite wait buffer: bufobj: 0, blkno: 318727, size: 655 36 Jul 7 18:55:02 rpi3 kernel: swap_pager: indefinite wait buffer: bufobj: 0, blkno: 354041, size: 286 72 Jul 7 21:45:10 rpi3 kernel: swap_pager: indefinite wait buffer: bufobj: 0, blkno: 164496, size: 491 52 Jul 7 23:04:38 rpi3 kernel: swap_pager: indefinite wait buffer: bufobj: 0, blkno: 372151, size: 655 36