From owner-freebsd-arm@freebsd.org Sun Jun 10 13:25:18 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 C6D251004D60 for ; Sun, 10 Jun 2018 13:25:18 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 357CF81A8F for ; Sun, 10 Jun 2018 13:25:17 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([77.14.81.121]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0Mh6lB-1ff12z3DsX-00MH8B; Sun, 10 Jun 2018 15:25:08 +0200 Date: Sun, 10 Jun 2018 15:24:33 +0200 From: "O. Hartmann" To: Emmanuel Vadot Cc: "O. Hartmann" , "freebsd-arm@freebsd.org" Subject: Re: PINE64: aw_mmc0: controller timeout aw_mmc0: timeout updating clock Message-ID: <20180610152500.18567ade@thor.intern.walstatt.dynvpn.de> In-Reply-To: <20180609193107.077aa9342126f550a88d1f26@bidouilliste.com> References: <20180609180738.694fc3cf@thor.intern.walstatt.dynvpn.de> <20180609193107.077aa9342126f550a88d1f26@bidouilliste.com> Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: base64 X-Provags-ID: V03:K1:HhtTVwZ//xvAg5zpEEscIWTxvGA1kBZsJGW/6Cee4JMUtE0BcT5 C+v0HWb2FXARTg7HWQqUxg5JwLHjoec8dk0fZE3ukYagJQ8VcMoOJ9Bll4Pej0NBNW4zYau XGPUMnLU9qUT+Z29U0pwDkaGGlf0+iIp6DfFqWL1qvWcyIQSNB4Lo0T6F+wKcZlO+ZhPxv/ mWFOEJ0y8sz8YwzVbOdeg== X-UI-Out-Filterresults: notjunk:1;V01:K0:KCpdgM9K0uc=:jwqcQgW+R/ZHeTE6fJOIsE RyNr2480Uejxet4V5UqQx38rX4GcRLm3lN3KwtXWZxTThwKnCt9sMRZBbarNZO6jsWWmy0CuW YJCOKH3ZKPdtAkSklbreBnn7rLHLuMkAQnFJyqYJERxK3QoqQcpKS4AxpZ7z0vE36lf6InIbQ GPjR4R2nde31DQ5AckdDuM44QlYaahrzSfD5CQ3NNpANRvPYjEUKlDcO0ndqU5lG32P+FpO1q g/8rV55svTWhv6gg29T5zU/x5Ni/spNM7yx552yW+pvqXSGsg+hhNY/CHi+r6TbTQAzCldW+f 8R1vx6rMvNCJPGiGPEbjyKJIkpjf5EVzSMPrR80VTOCJ+U0fYtUetW0J+0Le1TdZdDzAzbjwK gTrEOBN1ufdZF7zQqxPFaoBB1I9strpMXiGv7WNcUIe/B4+Fuj8H61ogJM/OJdFYnGZGAWUKD XAy6gcZcUbjGMWC524ItELJAFrmIj00hID0qqZDL0/Sx1mU46lp+fIeBwouTeLio8NZdujWsN VoiY/1J2ZwAZGumtxEYaQLfswyDS6IBj3wIdcIaVdlWZ0My2U3aj7Ab5b+NfAb2Pr4NxDGeKo 1ShaGqGUQbHzCbQJc6eKkK7EqhM0+/iekKvcMEuu+SUIPRqyuNaSgpGDWEljArGiBgDkK6x+q gRURDa+SZ2MgkPud4C/QPLptXx7ntpg4SIL6y5W70xp3RLLVzi9zBZXTrqEMkUwCgoDoWB6Eq p0/u312Ua8E5XrM6FH7iD88mMKKeM5CypKhiLPa0zI+PjpEyno1ohklSgajEaYJ07s1nxXgA1 Y5RNFLW X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Jun 2018 13:25:19 -0000 LS0tLS1CRUdJTiBQR1AgU0lHTkVEIE1FU1NBR0UtLS0tLQ0KSGFzaDogU0hBNTEyDQoNCkFtIFNh dCwgOSBKdW4gMjAxOCAxOTozMTowNyArMDIwMA0KRW1tYW51ZWwgVmFkb3QgPG1hbnVAYmlkb3Vp bGxpc3RlLmNvbT4gc2NocmllYjoNCg0KPiAgSGksDQo+IA0KPiBPbiBTYXQsIDkgSnVuIDIwMTgg MTg6MDc6MTEgKzAyMDANCj4gIk8uIEhhcnRtYW5uIiA8b2hhcnRtYW5uQHdhbHN0YXR0Lm9yZz4g d3JvdGU6DQo+IA0KPiA+IC0tLS0tQkVHSU4gUEdQIFNJR05FRCBNRVNTQUdFLS0tLS0NCj4gPiBI YXNoOiBTSEE1MTINCj4gPiANCj4gPiBSdW5uaW5nIGEgUElORTY0IHdpdGggYSByZWNlbnQgQ1VS UkVOVCAoIEZyZWVCU0QgMTIuMC1DVVJSRU5UICMyNyByMzM0ODc0OiBTYXQgSnVuICA5DQo+ID4g MDk6MzE6MDcgQ0VTVCAyMDE4IGFhcmNoNjQpIGFuZCB0cnlpbmcgdG8gdXBkYXRlIHRoZSBzeXN0 ZW0gdmlhICJwa2cgQmFzZSIgKHNlbGYNCj4gPiBjb21waWxlZCBvbiBhIGFtZDY0IHN5c3RlbSks IGl0IHR1cm5zIG91dCwgdGhhdCB1cGRhdGluZyB0aGUgUGluZTY0IG9uIHN1Y2ggYSB3YXkgaXMN Cj4gPiBhIGV2ZXIgbGFzdGluZyBqb2IuIA0KPiA+IA0KPiA+IERvd25sb2FkaW5nIGlzIGEgdGFz ayBJIG5lZWQgYSBsb3Qgb2YgcGF0aWVuY2UgZXZlbiB3aXRoIHRoZSAxIEdCaXQgTklDIG9mIHRo ZSBQaW5lNjQsDQo+ID4gYnV0IGV4dHJhY3RpbmcgdHVybnMgb3V0IHRvIGJlIGEgc2xvdyBhcyB0 aGUgbW92ZW1lbnQgb2YgYSBnbGFjaWVyIGFuZCBtb3N0IG9mIHRoZQ0KPiA+IHRpbWUgbXkgUGlu ZTY0IGNyYXNoZXMgZHVlIHRvIHRoZSBlcnJvciBzaG93biBiZWxvdy4NCj4gPiANCj4gPiBUaGUg U0QgY2FyZCBpcyBub3QgdGhlIGZhc3Rlc3Qgb25lLCBkbWVzZyByZXBvcnRzDQo+ID4gDQo+ID4g bW1jc2QwOiAxNkdCIDxTREhDIFNEMTZHIDMuMCBTTiAwMTEyNUVBMyBNRkcgMDYvMjAxNSBieSAz OSBQSD4gYXQgbW1jMA0KPiA+IDUwLjBNSHovNGJpdC8zMjc2OC1ibG9jaw0KPiA+IA0KPiA+IGJ1 dCBvbiBvdGhlciBzeXN0ZW1zIHRoZSBwZXJmb3JtYW5jZSBpcyBzdWZmaWNpZW50IC0gYnV0IG5v dCBvbiB0aGUgUGluZTY0LiBJIGhhdmVuJ3QNCj4gPiBjaGVja2VkIHdpdGggb3RoZXIgU0QgY2Fy ZHMgZHVlIHRvIHRoZSBsYWNrIG9mIG90aGVyIHR5cGVzLCBzbyBpZiB0aGUgcmVhc29uIGZvciB0 aGUNCj4gPiB0aW1pbmcgcHJvYmxlbXMgaXMgdGhlIFNEIGNhcmQgYW5kIG5vdCB0aGUgZHJpdmVy LCBJJ2xsIGNoZWNrIHdpdGggYW5vdGhlciBvbmUuIA0KPiA+IA0KPiA+IEJ1dCBjb3VsZCBzb21l b25lIGNoZWNrPyAgDQo+IA0KPiAgIEkga25vdyB0aGVyZSBpcyBzdGlsbCBhIGJ1ZyBzb21ld2hl cmUgaW4gdGhlIGRyaXZlciB0aGF0IGNhdXNlIHRoaXMsDQo+IEkgdXNlIHRvIGJlIGFibGUgdG8g cmVwcm9kdWNlIGl0IHdpdGggcGtnIGluc3RhbGwgbGx2bTUwIGJ1dCBub3QNCj4gYW55bW9yZSBh ZnRlciBteSBsYXRlc3QgY29tbWl0cy4gSSBndWVzcyBJIGhhdmUgYSBuZXcgdGVzdCBjYXNlLg0K PiAgV2hhdCdzIHRoZSBzaXplIG9mIHRoZSBGcmVlQlNELXJ1bnRpbWUtZGVidWctMTIuMC5zMjAx ODA2MDkwNzMxMjENCj4gcGFja2FnZSA/DQo+IA0KPiA+IFdoYXQgaXMgYWJvdXQgTU1DQ0FNPyBJ cyBpdCB3b3J0aCBnaXZpbmcgdGhhdCBhIHRyeSBvciBpcyBpdHMgZGV2ZWxvcG1lbnQgc3RhdGUg dG8NCj4gPiByaXNreSByZWdhcmRpbmcgdGhlIHVzYWdlIG9uIGEgUGluZTY0PyAgDQo+IA0KPiAg Tm8gc3VwcG9ydCBmb3IgTU1DQ0FNIGluIHRoaXMgZHJpdmVyLCBraWJhYkAgaXMgd29ya2luZyBv biBpdC4NCj4gDQo+ID4gVGhhbmtzIGluIGFkdmFuY2UsDQo+ID4gDQo+ID4gb2gNCj4gPiANCj4g PiBbLi4uXQ0KPiA+IFByb2NlZWQgd2l0aCB0aGlzIGFjdGlvbj8gW3kvTl06IHkNCj4gPiBbMS8z NzldIFVwZ3JhZGluZyBGcmVlQlNELXJ1bnRpbWUtZGVidWcgZnJvbSAxMi4wLnMyMDE4MDYwMjEz MjA0MiB0bw0KPiA+IDEyLjAuczIwMTgwNjA5MDczMTIxLi4uIFsxLzM3OV0gRXh0cmFjdGluZyBG cmVlQlNELXJ1bnRpbWUtZGVidWctMTIuMC5zMjAxODA2MDkwNzMxMjE6DQo+ID4gODklYXdfbW1j MDogY29udHJvbGxlciB0aW1lb3V0IGF3X21tYzA6IHRpbWVvdXQgdXBkYXRpbmcgY2xvY2sNCj4g PiBtbWNzZDA6IEVycm9yIGluZGljYXRlZDogMSBUaW1lb3V0DQo+ID4gZ192ZnNfZG9uZSgpOnVm cy9yb290ZnNbV1JJVEUob2Zmc2V0PTEzMTA3MiwgbGVuZ3RoPTMyNzY4KV1lcnJvciA9IDUNCj4g PiBzb2Z0ZGVwX3VwZGF0ZV9pbm9kZWJsb2NrOiBid3JpdGU6IGdvdCBlcnJvciA1IHdoaWxlIGFj Y2Vzc2luZyBmaWxlc3lzdGVtDQo+ID4gYXdfbW1jMDogY29udHJvbGxlciB0aW1lb3V0DQo+ID4g YXdfbW1jMDogdGltZW91dCB1cGRhdGluZyBjbG9jaw0KPiA+IG1tY3NkMDogRXJyb3IgaW5kaWNh dGVkOiAxIFRpbWVvdXQNCj4gPiBnX3Zmc19kb25lKCk6dWZzL3Jvb3Rmc1tXUklURShvZmZzZXQ9 MTk2NjA4LCBsZW5ndGg9MzI3NjgpXWVycm9yID0gNQ0KPiA+IGF3X21tYzA6IGNvbnRyb2xsZXIg dGltZW91dA0KPiA+IGF3X21tYzA6IHRpbWVvdXQgdXBkYXRpbmcgY2xvY2sNCj4gPiBtbWNzZDA6 IEVycm9yIGluZGljYXRlZDogMSBUaW1lb3V0DQo+ID4gZ192ZnNfZG9uZSgpOnVmcy9yb290ZnNb V1JJVEUob2Zmc2V0PTQyNTk4NCwgbGVuZ3RoPTMyNzY4KV1lcnJvciA9IDUNCj4gPiBhd19tbWMw OiBjb250cm9sbGVyIHRpbWVvdXQNCj4gPiBhd19tbWMwOiB0aW1lb3V0IHVwZGF0aW5nIGNsb2Nr DQo+ID4gbW1jc2QwOiBFcnJvciBpbmRpY2F0ZWQ6IDEgVGltZW91dA0KPiA+IGdfdmZzX2RvbmUo KTp1ZnMvcm9vdGZzW1dSSVRFKG9mZnNldD0yMTk1NDU2LCBsZW5ndGg9MzI3NjgpXWVycm9yID0g NQ0KPiA+IGF3X21tYzA6IGNvbnRyb2xsZXIgdGltZW91dA0KPiA+IGF3X21tYzA6IHRpbWVvdXQg dXBkYXRpbmcgY2xvY2sNCj4gPiBtbWNzZDA6IEVycm9yIGluZGljYXRlZDogMSBUaW1lb3V0DQo+ ID4gZ192ZnNfZG9uZSgpOnVmcy9yb290ZnNbV1JJVEUob2Zmc2V0PTIyMjgyMjQsIGxlbmd0aD0z Mjc2OCldZXJyb3IgPSA1DQo+ID4gDQo+ID4gcGtnOiBGYWlsIHRvIHRydW5jYXRlDQo+ID4gZmls ZTogL3Vzci9saWIvZGVidWcvdXNyL3NiaW4vLnByYWxpYXNlcy5kZWJ1Zy5SVm9zbER2NWU3REQ6 SW5wdXQvb3V0cHV0IGVycm9yDQo+ID4gYXdfbW1jMDogY29udHJvbGxlciB0aW1lb3V0IGF3X21t YzA6IHRpbWVvdXQgdXBkYXRpbmcgY2xvY2sNCj4gPiBtbWNzZDA6IEVycm9yIGluZGljYXRlZDog MSBUaW1lb3V0DQo+ID4gZ192ZnNfZG9uZSgpOnVmcy9yb290ZnNbV1JJVEUob2Zmc2V0PTIyNjQ2 Nzg0LCBsZW5ndGg9NDA5NildZXJyb3IgPSA1DQo+ID4gYXdfbW1jMDogY29udHJvbGxlciB0aW1l b3V0DQo+ID4gYXdfbW1jMDogdGltZW91dCB1cGRhdGluZyBjbG9jaw0KPiA+IG1tY3NkMDogRXJy b3IgaW5kaWNhdGVkOiAxIFRpbWVvdXQNCj4gPiBnX3Zmc19kb25lKCk6dWZzL3Jvb3Rmc1tXUklU RShvZmZzZXQ9NjU0NzA0NjQwLCBsZW5ndGg9MzI3NjgpXWVycm9yID0gNQ0KPiA+IA0KPiA+IGF3 X21tYzA6IGNvbnRyb2xsZXIgdGltZW91dA0KPiA+IGF3X21tYzA6IHRpbWVvdXQgdXBkYXRpbmcg Y2xvY2sNCj4gPiBtbWNzZDA6IEVycm9yIGluZGljYXRlZDogMSBUaW1lb3V0DQo+ID4gZ192ZnNf ZG9uZSgpOnVmcy9yb290ZnNbV1JJVEUob2Zmc2V0PTEzMDMyNDg4OTYsIGxlbmd0aD0zMjc2OCld ZXJyb3IgPSA1DQo+ID4gYXdfbW1jMDogY29udHJvbGxlciB0aW1lb3V0DQo+ID4gDQo+ID4gWy4u Ll0NCj4gPiANCj4gPiBhd19tbWMwOiBjb250cm9sbGVyIHRpbWVvdXQNCj4gPiBhd19tbWMwOiB0 aW1lb3V0IHVwZGF0aW5nIGNsb2NrDQo+ID4gbW1jc2QwOiBFcnJvciBpbmRpY2F0ZWQ6IDEgVGlt ZW91dA0KPiA+IGdfdmZzX2RvbmUoKTpwYW5pYzogdm1fZmF1bHRfaG9sZDogZmF1bHQgb24gbm9m YXVsdCBlbnRyeSwgYWRkcjogMHhmZmZmMDAwMDQzMzMwMDAwDQo+ID4gY3B1aWQgPSAxDQo+ID4g dGltZSA9IDEyNjIzNDI4MzcNCj4gPiBLREI6IHN0YWNrIGJhY2t0cmFjZToNCj4gPiAjMCAweGZm ZmYwMDAwMDAzOGIzNGMgYXQga2RiX2JhY2t0cmFjZSsweDYwDQo+ID4gIzEgMHhmZmZmMDAwMDAw MzQzODRjIGF0IHZwYW5pYysweDFhOA0KPiA+ICMyIDB4ZmZmZjAwMDAwMDM0MzZhMCBhdCBwYW5p YysweDQ0DQo+ID4gIzMgMHhmZmZmMDAwMDAwNjBmNjUwIGF0IHZtX2ZhdWx0X2hvbGQrMHgyMGI0 DQo+ID4gIzQgMHhmZmZmMDAwMDAwNjBkNTQ0IGF0IHZtX2ZhdWx0KzB4NjANCj4gPiAjNSAweGZm ZmYwMDAwMDA2NjYxNTQgYXQgZGF0YV9hYm9ydCsweGEwDQo+ID4gIzYgMHhmZmZmMDAwMDAwNjY1 ZmIwIGF0IGRvX2VsMWhfc3luYysweDExYw0KPiA+ICM3IDB4ZmZmZjAwMDAwMDY1MDg3NCBhdCBo YW5kbGVfZWwxaF9zeW5jKzB4NzQNCj4gPiAjOCAweGZmZmYwMDAwMDA2NGU4ZjggYXQgYm91bmNl X2J1c19kbWFtYXBfc3luYysweDI1OA0KPiA+ICM5IDB4ZmZmZjAwMDAwMDYzYzdhMCBhdCBhd19t bWNfcmVxdWVzdCsweDMyYw0KPiA+ICMxMCAweGZmZmYwMDAwMDAxNWEzNTggYXQgbW1jX3dhaXRf Zm9yX3JlcXVlc3QrMHgxMjANCj4gPiAjMTEgMHhmZmZmMDAwMDAwMTYzMTljIGF0IG1tY3NkX3J3 KzB4MTk4DQo+ID4gIzEyIDB4ZmZmZjAwMDAwMDE2MWQ5OCBhdCBtbWNzZF90YXNrKzB4MjIwDQo+ ID4gIzEzIDB4ZmZmZjAwMDAwMDMwNjQ5MCBhdCBmb3JrX2V4aXQrMHg5MA0KPiA+IFVwdGltZTog MjBtMnMNCj4gPiANCj4gPiBVLUJvb3QgU1BMIDIwMTguMDMgKE1heSAyOSAyMDE4IC0gMTc6MjI6 MjUgKzAwMDApDQo+ID4gRFJBTTogMjA0OCBNaUINCj4gPiBUcnlpbmcgdG8gYm9vdCBmcm9tIE1N QzENCj4gPiANCj4gPiANCj4gPiBVLUJvb3QgMjAxOC4wMyAoTWF5IDI5IDIwMTggLSAxNzoyMjoy NSArMDAwMCkgQWxsd2lubmVyIFRlY2hub2xvZ3kNCj4gPiANCj4gPiBDUFU6ICAgQWxsd2lubmVy IEE2NCAoU1VONTBJKQ0KPiA+IE1vZGVsOiBQaW5lNjQrDQo+ID4gRFJBTTogIDIgR2lCDQo+ID4g TU1DOiAgIFNVTlhJIFNEL01NQzogMA0KPiA+IExvYWRpbmcgRW52aXJvbm1lbnQgZnJvbSBGQVQu Li4gKioqIFdhcm5pbmcgLSBiYWQgQ1JDLCB1c2luZyBkZWZhdWx0IGVudmlyb25tZW50DQo+ID4g DQo+ID4gRmFpbGVkICgtNSkNCj4gPiBMb2FkaW5nIEVudmlyb25tZW50IGZyb20gTU1DLi4uICoq KiBXYXJuaW5nIC0gYmFkIENSQywgdXNpbmcgZGVmYXVsdCBlbnZpcm9ubWVudA0KPiA+IA0KPiA+ IEZhaWxlZCAoLTUpDQo+ID4gSW46ICAgIHNlcmlhbA0KPiA+IE91dDogICBzZXJpYWwNCj4gPiBF cnI6ICAgc2VyaWFsDQo+ID4gTmV0OiAgIHBoeSBpbnRlcmZhY2U3DQo+ID4gZXRoMDogZXRoZXJu ZXRAMDFjMzAwMDANCj4gPiBzdGFydGluZyBVU0IuLi4NCj4gPiBVU0IwOiAgIFVTQiBFSENJIDEu MDANCj4gPiBVU0IxOiAgIFVTQiBPSENJIDEuMA0KPiA+IHNjYW5uaW5nIGJ1cyAwIGZvciBkZXZp Y2VzLi4uIDEgVVNCIERldmljZShzKSBmb3VuZA0KPiA+ICAgICAgICBzY2FubmluZyB1c2IgZm9y IHN0b3JhZ2UgZGV2aWNlcy4uLiAwIFN0b3JhZ2UgRGV2aWNlKHMpIGZvdW5kDQo+ID4gSGl0IGFu eSBrZXkgdG8gc3RvcCBhdXRvYm9vdDogIDIgDQo+ID4gDQo+ID4gLSAtLSANCj4gPiBPLiBIYXJ0 bWFubg0KPiA+IA0KPiA+IEljaCB3aWRlcnNwcmVjaGUgZGVyIE51dHp1bmcgb2RlciDcYmVybWl0 dGx1bmcgbWVpbmVyIERhdGVuIGb8cg0KPiA+IFdlcmJlendlY2tlIG9kZXIgZvxyIGRpZSBNYXJr dC0gb2RlciBNZWludW5nc2ZvcnNjaHVuZyAopyAyOCBBYnMuIDQgQkRTRykuDQo+ID4gLS0tLS1C RUdJTiBQR1AgU0lHTkFUVVJFLS0tLS0NCj4gPiANCj4gPiBpTFVFQVJNS0FCMFdJUVFaVlpNekF0 d0MyVC84NlRyUzUyOGZ5RmhZbEFVQ1d4djdTZ0FLQ1JEUzUyOGZ5RmhZDQo+ID4gbE5uY0FmOUVs RGM5WkM5Y1NWSmJxL0xyRmdDNnhqTGN6Y0lEVUJITkdnTFR5VmVZV2lRdm8zVE44U2dDaVRnYQ0K PiA+IEZpemdhNmRJSEdyUS9Sd21HdHhlUjhyZmlVUDJBZjBROHlWRUk5dkE3a1gwbmlMbjFHL0l4 YVFYeThJRnc3V2MNCj4gPiBGbjk0QzBjSnIvMmlxRXNnU0xzcnFmTWZhVkZIbHdOQ0J6UzVXcitE aS85eThSOFo0UWJzDQo+ID4gPTNZUDINCj4gPiAtLS0tLUVORCBQR1AgU0lHTkFUVVJFLS0tLS0N Cj4gPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiA+ IGZyZWVic2QtYXJtQGZyZWVic2Qub3JnIG1haWxpbmcgbGlzdA0KPiA+IGh0dHBzOi8vbGlzdHMu ZnJlZWJzZC5vcmcvbWFpbG1hbi9saXN0aW5mby9mcmVlYnNkLWFybQ0KPiA+IFRvIHVuc3Vic2Ny aWJlLCBzZW5kIGFueSBtYWlsIHRvICJmcmVlYnNkLWFybS11bnN1YnNjcmliZUBmcmVlYnNkLm9y ZyIgIA0KPiANCj4gDQoNClRoZXJlIG9jY3VycyBhbm90aGVyIHByb2JsZW0gZnJvbSB0aW1lIHRv IHRpbWU6DQoNClsuLi5dDQpbMzYvMjMwXSBFeHRyYWN0aW5nIEZyZWVCU0QtbGlibWVtc3RhdC1k ZXZlbG9wbWVudC0xMi4wLnMyMDE4MDYxMDA2NDcwNDogICAwJWxvY2sgb3JkZXINCnJldmVyc2Fs OiAxc3QgMHhmZmZmZmQwMDI1M2E3MDY4IHVmcyAodWZzKQ0KQCAvcG9vbC9zb3VyY2VzL0NVUlJF TlQvc3JjL3N5cy9rZXJuL3Zmc19zdWJyLmM6MjU3MiAybmQgMHhmZmZmMDAwMDQwZDVkMzUwIGJ1 ZndhaXQNCihidWZ3YWl0KSBAIC9wb29sL3NvdXJjZXMvQ1VSUkVOVC9zcmMvc3lzL3Vmcy9mZnMv ZmZzX3Zub3BzLmM6MjgyIDNyZCAweGZmZmZmZDAwMjU0ODI3ZTgNCnVmcyAodWZzKSBAIC9wb29s L3NvdXJjZXMvQ1VSUkVOVC9zcmMvc3lzL2tlcm4vdmZzX3N1YnIuYzoyNTcyIHN0YWNrIGJhY2t0 cmFjZToNCiMwIDB4ZmZmZjAwMDAwMDNkZjMwMCBhdCB3aXRuZXNzX2RlYnVnZ2VyKzB4NjQNCiMx IDB4ZmZmZjAwMDAwMDM1MDA4MCBhdCBsb2NrbWdyX3hsb2NrX2hhcmQrMHg2Yw0KIzIgMHhmZmZm MDAwMDAwMzUwOGZjIGF0IF9fbG9ja21ncl9hcmdzKzB4NGFjDQojMyAweGZmZmYwMDAwMDA2MDA3 YmMgYXQgZmZzX2xvY2srMHg4OA0KIzQgMHhmZmZmMDAwMDAwNmJlNDg0IGF0IFZPUF9MT0NLMV9B UFYrMHhhYw0KIzUgMHhmZmZmMDAwMDAwNDUxYWYwIGF0IF92bl9sb2NrKzB4NjQNCiM2IDB4ZmZm ZjAwMDAwMDQ0MjEzMCBhdCB2Z2V0KzB4NzgNCiM3IDB4ZmZmZjAwMDAwMDQzNGYyNCBhdCB2ZnNf aGFzaF9nZXQrMHhlYw0KIzggMHhmZmZmMDAwMDAwNWZjN2VjIGF0IGZmc192Z2V0ZisweDQ0DQoj OSAweGZmZmYwMDAwMDA1ZjM0MmMgYXQgc29mdGRlcF9zeW5jX2J1ZisweDlmNA0KIzEwIDB4ZmZm ZjAwMDAwMDYwMTRmOCBhdCBmZnNfc3luY3Zub2RlKzB4MjZjDQojMTEgMHhmZmZmMDAwMDAwNWRi NGNjIGF0IGZmc190cnVuY2F0ZSsweDZiNA0KIzEyIDB4ZmZmZjAwMDAwMDYwODBjNCBhdCB1ZnNf ZGlyZW50ZXIrMHg3NzgNCiMxMyAweGZmZmYwMDAwMDA2MTAxZDAgYXQgdWZzX21ha2Vpbm9kZSsw eDRiOA0KIzE0IDB4ZmZmZjAwMDAwMDYwYzhhOCBhdCB1ZnNfY3JlYXRlKzB4MzgNCiMxNSAweGZm ZmYwMDAwMDA2YmI3M2MgYXQgVk9QX0NSRUFURV9BUFYrMHhhYw0KIzE2IDB4ZmZmZjAwMDAwMDQ1 MTQ2NCBhdCB2bl9vcGVuX2NyZWQrMHgyNjQNCiMxNyAweGZmZmYwMDAwMDA0NGE4NzggYXQga2Vy bl9vcGVuYXQrMHgyMDgNCg0KDQotIC0tIA0KTy4gSGFydG1hbm4NCg0KSWNoIHdpZGVyc3ByZWNo ZSBkZXIgTnV0enVuZyBvZGVyINxiZXJtaXR0bHVuZyBtZWluZXIgRGF0ZW4gZvxyDQpXZXJiZXp3 ZWNrZSBvZGVyIGb8ciBkaWUgTWFya3QtIG9kZXIgTWVpbnVuZ3Nmb3JzY2h1bmcgKKcgMjggQWJz LiA0IEJEU0cpLg0KLS0tLS1CRUdJTiBQR1AgU0lHTkFUVVJFLS0tLS0NCg0KaUxVRUFSTUtBQjBX SVFRWlZaTXpBdHdDMlQvODZUclM1MjhmeUZoWWxBVUNXeDBtckFBS0NSRFM1MjhmeUZoWQ0KbEwz aUFmNHUyaDlOT09QS2hSUDM5ZHQxUm1qdHJuamUrRWVmZVRSemIzK21xTFEyb2xFbXdFMHpsOVVG NlhIbw0KNDcxUFArRDZLYzU1NituYkp5YjVuL0NLakwwTUFmOUhPVXlYQ1J6L0ZER3NwU24zNEh5 eVE2VmVxK0xtdHZ1RA0KekJId3F0ZnpwOHYxVHlUVUN5bmh3VnYwSFBJbTNtRjAvR2owNVVJRHVQ ZHNZNWw0dHBtbg0KPUVhT2sNCi0tLS0tRU5EIFBHUCBTSUdOQVRVUkUtLS0tLQ0K From owner-freebsd-arm@freebsd.org Sun Jun 10 19:15: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 6E8DD1016E3F for ; Sun, 10 Jun 2018 19:15:55 +0000 (UTC) (envelope-from usenet@ulrich-grey.de) Received: from mo6-p00-ob.smtp.rzone.de (mo6-p00-ob.smtp.rzone.de [IPv6:2a01:238:20a:202:5300::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.smtp.rzone.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C94E572BEE for ; Sun, 10 Jun 2018 19:15:54 +0000 (UTC) (envelope-from usenet@ulrich-grey.de) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1528658152; s=strato-dkim-0002; d=ulrich-grey.de; h=Message-Id:Subject:Cc:To:From:Date:X-RZG-CLASS-ID:X-RZG-AUTH:From: Subject:Sender; bh=z6Lx0zUkpUyv386hp9LMgU412woGARzC/cLVzt1k3NM=; b=c4yrFeW6Yuh9sYSGiNNQtjikAhCQbtfGs3IOBx7HwkMbotLNwSwFBpR7ycUR3CBOiK mYsY2c5hEAFsOxuhq923DABN0MBC00PkzlphP2E0q7dbNKtiCHVYSmfX75IeI+xjHYE5 ynDzYaMk52EDzgi0O3gZfiwHbg6ejA1b6ptOW3eLyMr/1hN9Xatvhu8ZGIHfq6biEMmX A/hTNnfx9cR6nQULZoP3i9XRECfXIR5CY/JNDC7Sv2ViZZoJFWNH+203DPGH6Rtd54YA a9ff4iGn87pdEY++6XJxsdxzIv7Hnhf8RV6QvQ2vXIYZErd0/B5BXQ2BPEc3Tk3pF5BI oGDw== X-RZG-AUTH: ":OX8Be0W8W+pMC3rDLL/lo2xV/LZTbZkYhPcwkcojh9vB3Wa1dWT+c76f0FX5V4KGCpMzTV5pug==" X-RZG-CLASS-ID: mo00 Received: from ap-fbsd by smtp.strato.de (RZmta 43.10 DYNA|AUTH) with ESMTPSA id x07f60u5AJFqAuo (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (curve secp521r1 with 521 ECDH bits, eq. 15360 bits RSA)) (Client did not present a certificate); Sun, 10 Jun 2018 21:15:52 +0200 (CEST) Date: Sun, 10 Jun 2018 21:15:51 +0200 From: Ulrich Grey To: freebsd-arm@freebsd.org Cc: mail@ulrich-grey.de Subject: Building a PINE64 image on a Wandboard-Quad: Malformed conditional error Message-Id: <20180610211551.4351ff47b55a5326403dad36@ulrich-grey.de> Organization: - X-Mailer: Sylpheed 3.5.1 (GTK+ 2.24.29; i386-portbld-freebsd11.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Jun 2018 19:15:55 -0000 I successfully built a PINE64 image on a Wandboard-Quad (FreeBSD 12.0-CURRENT #0 r333645) using: release.sh -c arm64/PINE64.conf and got some errors "Malformed conditional" (see below). I don't own a PINE64 yet, so I can not test the image. For the complete build log please see: ulrich-grey.de/dl/PINE64_build.log.txt (line 2060 ff.) -------------------------------------------------------------- >>> Kernel build for GENERIC completed on Sun Jun 10 17:37:40 UTC 2018 -------------------------------------------------------------- md0 created md0s1 added active set on md0s1 /dev/md0s1: 110448 sectors in 13806 FAT16 clusters (4096 bytes/cluster) BytesPerSec=512 SecPerClust=8 ResSectors=1 FATs=2 RootDirEnts=512 Media=0xf0 FATsecs=54 SecPerTrack=63 Heads=255 HiddenSecs=0 HugeSectors=110592 md0s2 added md0s2 created md0s2a added Reduced frags per cylinder group from 160280 to 159064 to enlarge last cyl group /dev/md0s2a: 2505.0MB (5130240 sectors) block size 32768, fragment size 4096 using 5 cylinder groups of 621.34MB, 19883 blks, 79616 inodes. with soft updates super-block backups (for fsck_ffs -b #) at: 192, 1272704, 2545216, 3817728, 5090240 make[1]: "/usr/obj/usr/src/arm64.aarch64/compiler-metadata.mk" line 1: Using cached compiler metadata from build at wqtest.intranet on Sat Jun 9 22:08:44 UTC 2018 make[2]: "/usr/src/release/Makefile.ec2" line 8: Malformed conditional (${BRANCH} == "CURRENT" || ${BRANCH} == "STABLE" || ${BRANCH} == "PRERELEASE") make[2]: "/usr/src/release/Makefile.azure" line 19: Malformed conditional (${BRANCH} == "STABLE" || ${BRANCH} == "CURRENT" || ${BRANCH} == "PRERELEASE") make[2]: || "/usr/src/release/Makefile.gce" line 26: Malformed conditional (${BRANCH} == "STABLE" || || ${BRANCH} == "CURRENT" || ${BRANCH} == "PRERELEASE") make[2]: || || "/usr/src/release/Makefile.vagrant" line 31: Malformed conditional (${BRANCH} == || || "STABLE" || ${BRANCH} == "CURRENT" || ${BRANCH} == "PRERELEASE") make[2]: Fatal || || errors encountered -- cannot continuemake[1]: "/usr/src/Makefile.inc1" line 389: || || warning: "make -C /usr/src/release MK_AUTO_OBJ=no -V REVISION" returned non-zero || || status make[2]: "/usr/src/release/Makefile.ec2" line 8: Malformed conditional (${BRANCH} == "CURRENT" || ${BRANCH} == "STABLE" || ${BRANCH} == "PRERELEASE") make[2]: "/usr/src/release/Makefile.azure" line 19: Malformed conditional (${BRANCH} == "STABLE" || ${BRANCH} == "CURRENT" || ${BRANCH} == "PRERELEASE") make[2]: || "/usr/src/release/Makefile.gce" line 26: Malformed conditional (${BRANCH} == "STABLE" || || ${BRANCH} == "CURRENT" || ${BRANCH} == "PRERELEASE") make[2]: || || "/usr/src/release/Makefile.vagrant" line 31: Malformed conditional (${BRANCH} == || || "STABLE" || ${BRANCH} == "CURRENT" || ${BRANCH} == "PRERELEASE") make[2]: Fatal errors encountered -- cannot continuemake[1]: "/usr/src/Makefile.inc1" line 393: warning: "make -C /usr/src/release MK_AUTO_OBJ=no -V BRANCH" returned non-zero status mkdir -p /tmp/install.Os6gUwh3 From owner-freebsd-arm@freebsd.org Sun Jun 10 21:01: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 743421004F68 for ; Sun, 10 Jun 2018 21:01:05 +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 10E0177C90 for ; Sun, 10 Jun 2018 21:01:05 +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 44E1921044 for ; Sun, 10 Jun 2018 21:01:04 +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 w5AL14d8086330 for ; Sun, 10 Jun 2018 21:01:04 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w5AL14t5086327 for freebsd-arm@FreeBSD.org; Sun, 10 Jun 2018 21:01:04 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201806102101.w5AL14t5086327@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, 10 Jun 2018 21:01:04 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Jun 2018 21:01:05 -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 Mon Jun 11 00:24: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 926A010012FF for ; Mon, 11 Jun 2018 00:24:16 +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 0DCD480DF7 for ; Mon, 11 Jun 2018 00:24:15 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id w5B0OMbY011771 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 10 Jun 2018 17:24:23 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w5B0OMcX011770; Sun, 10 Jun 2018 17:24:22 -0700 (PDT) (envelope-from fbsd) Date: Sun, 10 Jun 2018 17:24:22 -0700 From: bob prohaska To: freebsd-arm@freebsd.org Subject: RPI3, panic on warm boot at r334894 Message-ID: <20180611002421.GA11616@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.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jun 2018 00:24:16 -0000 For the first time in months my Pi3 got through a -j4 buildworld/installworld cycle. Make clean was run in /usr/src, but no other cleaning was done and the -DNO_CLEAN option was used in buildworld/buildkernel. However, on reboot using shutdown -r now it panic'd, with (in part) (da0:umass-sim0:0:0:0): Error 5, Retries exhausted g_vfs_done():da0a[READ(offset=163840, length=32768)]error = 5 panic: mount: lost mount cpuid = 3 time = 1528671592 KDB: stack backtrace: [console output is at http://www.zefox.net/~fbsd/rpi3/crashes/20180610/] On a whim, I power-cycled the machine, and it came back up just fine. Sources were updated to 334935 and a new build/install cycle is running, again using -DNO_CLEAN to speed things along, without any cleaning. This is the second occurrence in the last couple of days. Last time the system was rebooted (warm) to the old kernel, this time a complete power cycle cleared the error. Might the -DNO_CLEAN be the culprit? I expected it would cause compile time problems, if any. Thanks for reading, and any guidance. bob prohaska From owner-freebsd-arm@freebsd.org Tue Jun 12 15:47: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 4A1461020B66 for ; Tue, 12 Jun 2018 15:47:06 +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 DE0A36A350 for ; Tue, 12 Jun 2018 15:47:05 +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 3E55E179D4 for ; Tue, 12 Jun 2018 15:47:05 +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 w5CFl59V074763 for ; Tue, 12 Jun 2018 15:47:05 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w5CFl51f074762 for freebsd-arm@FreeBSD.org; Tue, 12 Jun 2018 15:47:05 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 228951] EFI vt code for arm64 Date: Tue, 12 Jun 2018 15:47:05 +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 Many People X-Bugzilla-Who: rgrimes@FreeBSD.org 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.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Jun 2018 15:47:06 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D228951 Bug ID: 228951 Summary: EFI vt code for arm64 Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: arm Assignee: freebsd-arm@FreeBSD.org Reporter: rgrimes@FreeBSD.org EFI vt code for arm64 --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-arm@freebsd.org Tue Jun 12 16:02: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 70C0510007A5 for ; Tue, 12 Jun 2018 16:02:33 +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 0E88F6B172 for ; Tue, 12 Jun 2018 16:02:33 +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 6BE6317C9C for ; Tue, 12 Jun 2018 16:02:32 +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 w5CG2WuO026368 for ; Tue, 12 Jun 2018 16:02:32 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w5CG2WtU026367 for freebsd-arm@FreeBSD.org; Tue, 12 Jun 2018 16:02:32 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 228955] Speculative fixes for speculative execution (specifically ARM for latest round of issues) Date: Tue, 12 Jun 2018 16:02:32 +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 Many People X-Bugzilla-Who: rgrimes@FreeBSD.org 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.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Jun 2018 16:02:33 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D228955 Bug ID: 228955 Summary: Speculative fixes for speculative execution (specifically ARM for latest round of issues) Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: arm Assignee: freebsd-arm@FreeBSD.org Reporter: rgrimes@FreeBSD.org Speculative fixes for speculative execution (specifically ARM for latest ro= und of issues) --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-arm@freebsd.org Tue Jun 12 16:09:10 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 E7DD71001339 for ; Tue, 12 Jun 2018 16:09:09 +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 7FDDD6B5D1 for ; Tue, 12 Jun 2018 16:09:09 +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 C265A17CB3 for ; Tue, 12 Jun 2018 16:09:08 +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 w5CG98kd033248 for ; Tue, 12 Jun 2018 16:09:08 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w5CG98GK033247 for freebsd-arm@FreeBSD.org; Tue, 12 Jun 2018 16:09:08 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 228957] Cull armv6/armv7 boards Date: Tue, 12 Jun 2018 16:09:08 +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 Many People X-Bugzilla-Who: rgrimes@FreeBSD.org 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.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Jun 2018 16:09:10 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D228957 Bug ID: 228957 Summary: Cull armv6/armv7 boards Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: arm Assignee: freebsd-arm@FreeBSD.org Reporter: rgrimes@FreeBSD.org Cull armv6/armv7 boards --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-arm@freebsd.org Tue Jun 12 16:11:01 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 25FE81001593 for ; Tue, 12 Jun 2018 16:11:01 +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 B69BB6B6E0 for ; Tue, 12 Jun 2018 16:11:00 +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 0F18417CC8 for ; Tue, 12 Jun 2018 16:11:00 +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 w5CGAxOj037189 for ; Tue, 12 Jun 2018 16:10:59 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w5CGAxqC037188 for freebsd-arm@FreeBSD.org; Tue, 12 Jun 2018 16:10:59 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 228958] Generic armv7 release image and tool to add uboot to generic image Date: Tue, 12 Jun 2018 16:11: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 Many People X-Bugzilla-Who: rgrimes@FreeBSD.org 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.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Jun 2018 16:11:01 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D228958 Bug ID: 228958 Summary: Generic armv7 release image and tool to add uboot to generic image Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: arm Assignee: freebsd-arm@FreeBSD.org Reporter: rgrimes@FreeBSD.org Generic armv7 release image and tool to add uboot to generic image --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-arm@freebsd.org Tue Jun 12 20:33:01 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 2C676101B8DF for ; Tue, 12 Jun 2018 20:33:01 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id BDCED788CC for ; Tue, 12 Jun 2018 20:33:00 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: by mailman.ysv.freebsd.org (Postfix) id 81176101B8DA; Tue, 12 Jun 2018 20:33:00 +0000 (UTC) Delivered-To: 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 6CFBA101B8D9 for ; Tue, 12 Jun 2018 20:33:00 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.blih.net", Issuer "mail.blih.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id CE7DF788CB for ; Tue, 12 Jun 2018 20:32:56 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) by mail.blih.net (OpenSMTPD) with ESMTP id cd281dff for ; Tue, 12 Jun 2018 22:32:49 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=bidouilliste.com; h=date :from:to:subject:message-id:mime-version:content-type :content-transfer-encoding; s=mail; bh=3sN53YwDnn+Kg0ondhUUzCKV7 +I=; b=WNLbecr+3Gf/aRQa/K60TFCWfrmIjHFZLGfy5zDjm8dRpbaQg5mtR+JTi 7k9snJx7AWzDBbrGIFksWauW1tIPWKXk0Qx2hBgmUL3BNZTQPYdZy2dCRGPy4/Ez Vr5dVxgbnaykRZjww/e26tBuy+nsG2cOxBkUmYbyaWmQDZOUDc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=bidouilliste.com; h=date :from:to:subject:message-id:mime-version:content-type :content-transfer-encoding; q=dns; s=mail; b=ONnGQ6W94D2KsphIKzh KBxAah4/iMf15jI+8wykUVvybjFBf5MgD8os5Oetwan2sLpq4sYi9Fw8Rfwf9Eni KqW7UzFOeFVm1wq/4alC+wM2l1nqhon/9SlRTkqD09iZPtFAPs5vPUVx6dYRk1A3 8br2Mq+3RaowLUGj5arF9Dpg= Received: from skull.home.blih.net (ip-9.net-89-3-105.rev.numericable.fr [89.3.105.9]) by mail.blih.net (OpenSMTPD) with ESMTPSA id 7163bf91 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO for ; Tue, 12 Jun 2018 22:32:49 +0200 (CEST) Date: Tue, 12 Jun 2018 22:32:48 +0200 From: Emmanuel Vadot To: "freebsd-arm@freebsd.org" Subject: De-orbit Allwinner A10/A20/A31 for 12.0 Message-Id: <20180612223248.f95d9ce3961187576e220614@bidouilliste.com> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; amd64-portbld-freebsd12.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Jun 2018 20:33:01 -0000 Hello arm@ I don't like to send this email but ... I want to remove A10/A20/A31 support for FreeBSD 12, here is the reason why : - I don't have time to maintain thoses SoC - For A10/A20 we currently don't boot on it since it requires new clocks binding (handled by aw_ccung) and I have no time to do the switch. - H3 (which is 32bits too) is way better in term of performance and price, you can buy a "good" $10 board while getting an A20 will cost you more for some reason. - My A31 board (BananapiM1) just died today after a long time of being my arm32 reference board. - I don't want the code to stay like the old 32 bits rockchip or amlogic code that can't even boot nowadays. If someone want to step up and convert A10/A20 to ccung I'll be glad to help/review but if no one step up it's unreasonable for me to support those right now and I prefer to remove completely the support. The plan is to remove support in one month (July 12th) if there is no volunteer to update the current code. Cheers, -- Emmanuel Vadot From owner-freebsd-arm@freebsd.org Tue Jun 12 20:43: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 AF37B101C783 for ; Tue, 12 Jun 2018 20:43:55 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 3288C78E2E for ; Tue, 12 Jun 2018 20:43:55 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mailman.ysv.freebsd.org (Postfix) id E21A2101C782; Tue, 12 Jun 2018 20:43:54 +0000 (UTC) Delivered-To: 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 BAA92101C77E for ; Tue, 12 Jun 2018 20:43:54 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x235.google.com (mail-io0-x235.google.com [IPv6:2607:f8b0:4001:c06::235]) (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 35E3878E2C for ; Tue, 12 Jun 2018 20:43:54 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x235.google.com with SMTP id g7-v6so963754ioh.11 for ; Tue, 12 Jun 2018 13:43:54 -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=TzrbTeDE1J+y9ixbLJSPz8vSX+bEUTxrDto+4YnS2JQ=; b=AocLNiqupBBOz37TLna22pqC5S0wNYpiudtpYofEhgnnQh3nP0xGzsP7lQZkFeJ3Nc GcKh9n3dntpJGjlEl1pQOqO1eZLwnrYuQhbgY1GYaClnSHz+bUcG8aI72SEz/hVgXjlo chOfcIF2vy02yAMsSdvwYKhWbRyinV2SB39R8/8i3RNAgVYYm/WhhRmn3J27GuZ7jB3m yMTITXHmyCUicngp6gpz0oIXsQypsc96GsaY34JsZ7+qg0bd2g3WWWrCPPj4uhneTDRo XDMXzhWegpaazxqKTYLEnGf/JTWlHPT1bHdrwCsUUW98lhFJbJNvyE5F7Y54OVocxytP kYWA== 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=TzrbTeDE1J+y9ixbLJSPz8vSX+bEUTxrDto+4YnS2JQ=; b=Cv/kG8jw0blw/jNPo0vOa4xHnu86hFrtEYivlQFyGWpjxHVrjx3FP9vV3KJZrJGMMm bntoM+iJESXlbskFLYREq03HvUOkKtBeQ7e987LB3YELFUGNklhiA5yymvXYUSXOz9Nn sr75uGWtaJfAFFnzm4jTo2c7X8azJFZqZBpxhEFCWzUhkrnFPcKddsMXXXDPtWqw3I57 oRQE2hcdbkqJ+U0bej+6I7yAcCH449+RODr0oKNTPEV/4EYETTk48+m1YI2FFhccWepb rlKuQ1DY5MJ3fwOLgGbuv9xjmFX6SRleN1KKND2jrR0bVqce1PUPpbdwctAcgGl6pqnr /2qw== X-Gm-Message-State: APt69E051E1RuZSIYP4K5E2+NnuUeQ+3PwOkU9qTyOBCujytsStNX9Hf chmzCyXvcakA8bYympgUuA0BOO9Ls3zcviBAmS4veQ== X-Google-Smtp-Source: ADUXVKIGHeBkWnVWOSgurz1ToubN0ROTIq82t8FmMLRWv5giQ8jjSOnVgXYqhGDcC+JQE2XhQAz4dhLIklqXrcjxtrE= X-Received: by 2002:a6b:d40c:: with SMTP id l12-v6mr2112451iog.37.1528836233370; Tue, 12 Jun 2018 13:43:53 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 2002:a4f:d028:0:0:0:0:0 with HTTP; Tue, 12 Jun 2018 13:43:52 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: <20180612223248.f95d9ce3961187576e220614@bidouilliste.com> References: <20180612223248.f95d9ce3961187576e220614@bidouilliste.com> From: Warner Losh Date: Tue, 12 Jun 2018 14:43:52 -0600 X-Google-Sender-Auth: 92UlKaBoxRoO4pL3f0OCg776Lfw Message-ID: Subject: Re: De-orbit Allwinner A10/A20/A31 for 12.0 To: Emmanuel Vadot Cc: "freebsd-arm@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Jun 2018 20:43:55 -0000 I have all these boards... But they are getting old and nearly are unobtanium these days. Were it not for the clocks thing, they'd be fine to run -current (I have a slightly pre new clock version running on a couple of boards). I think I'm with you: we need a maintainer who has done the work to bring them up to date, or they need to go. We likely have other house cleaning that's needed in arm as well, but I'll keep this discussion clean. Warner On Tue, Jun 12, 2018 at 2:32 PM, Emmanuel Vadot wrote: > > Hello arm@ > > I don't like to send this email but ... > > I want to remove A10/A20/A31 support for FreeBSD 12, here is the > reason why : > > - I don't have time to maintain thoses SoC > - For A10/A20 we currently don't boot on it since it requires new > clocks binding (handled by aw_ccung) and I have no time to do the > switch. > - H3 (which is 32bits too) is way better in term of performance and > price, you can buy a "good" $10 board while getting an A20 will cost > you more for some reason. > - My A31 board (BananapiM1) just died today after a long time of being > my arm32 reference board. > - I don't want the code to stay like the old 32 bits rockchip or > amlogic code that can't even boot nowadays. > > If someone want to step up and convert A10/A20 to ccung I'll be > glad to help/review but if no one step up it's unreasonable for me to > support those right now and I prefer to remove completely the support. > > The plan is to remove support in one month (July 12th) if there is no > volunteer to update the current code. > > Cheers, > > -- > Emmanuel Vadot > _______________________________________________ > 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 Jun 12 20:52: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 9AFD5101D3F1 for ; Tue, 12 Jun 2018 20:52:08 +0000 (UTC) (envelope-from rogiel@rogiel.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 2985C79215 for ; Tue, 12 Jun 2018 20:52:08 +0000 (UTC) (envelope-from rogiel@rogiel.com) Received: by mailman.ysv.freebsd.org (Postfix) id D71F8101D3EB; Tue, 12 Jun 2018 20:52:07 +0000 (UTC) Delivered-To: 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 AFB51101D3EA for ; Tue, 12 Jun 2018 20:52:07 +0000 (UTC) (envelope-from rogiel@rogiel.com) Received: from mail-qt0-x22f.google.com (mail-qt0-x22f.google.com [IPv6:2607:f8b0:400d:c0d::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4B17479210 for ; Tue, 12 Jun 2018 20:52:07 +0000 (UTC) (envelope-from rogiel@rogiel.com) Received: by mail-qt0-x22f.google.com with SMTP id d3-v6so406386qto.1 for ; Tue, 12 Jun 2018 13:52:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rogiel.com; s=google; h=date:from:to:message-id:in-reply-to:references:subject:mime-version; bh=sSv53pFMcvkTe+4OH3i0wNIzg7Tm0FKcDyTo2iId1J4=; b=EoH5g9huJWOi6V9R3Zwz6T9BYT7E4aE98pz8JR2RcTAsxfrllRMBxxOo90ZTMLlCif GFIuBQ19iDoSFewCHHrj5wAYMo5tKToStsIEzWIjpTOomn+QuIQQvnIfcXenSOmIWWtb 0fxGq9/UWYSjBxJwq6HS1BMZw8bCuaA0P4+Es= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:message-id:in-reply-to:references :subject:mime-version; bh=sSv53pFMcvkTe+4OH3i0wNIzg7Tm0FKcDyTo2iId1J4=; b=q3wIqhkjqN0yv9nGY+Ppm5QVUrFS/eLw7UV1uihQtMY4oV28ZlzJcimRj1ZW8kUu2o M48TfZjkV5cBPhdlIBjjnzqlX1jiyJZVlzriMxEN8/QpPKOz5FD4vFSB4lpeCPEAsCNT zJ9EqFthknN+P5bWrl7SvWaHJFjOWy4ET/kpl4kZHxQEC/8D/PNcAIEnAnNC0CGDi9rM 1eiHwg04IJTJr68/oCK1JHLbUIa3EEF9R9Pbw0yjw9sbAG8CzZsH70te/AujPSIvc66o 08pQRi1EFHfx2HW3EohTObSOvvLdUzbAIvilhWhnE0mr7HCSMqBtCxLa/bHsOgfbKVsI PvFQ== X-Gm-Message-State: APt69E2sCmxWMe1o/yU/QVJlHuYXNwPdHJhjAMrsaITm6Udt4CdWQVDl jHy6pqVZD5OKl/VTnRQsid7qXJ162j0= X-Google-Smtp-Source: ADUXVKJgj5bGRMX8DC2F5/zh4DlSi617Ii1yCGINZrOAuipI+irOIc6V0QfinGpuY2BR68jSSuhl3Q== X-Received: by 2002:aed:3d7d:: with SMTP id h58-v6mr2039981qtf.405.1528836726644; Tue, 12 Jun 2018 13:52:06 -0700 (PDT) Received: from [192.168.1.178] (131-72-249-143.brasrede.psi.br. [131.72.249.143]) by smtp.gmail.com with ESMTPSA id h126-v6sm719945qke.50.2018.06.12.13.52.04 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 12 Jun 2018 13:52:05 -0700 (PDT) Date: Tue, 12 Jun 2018 17:51:57 -0300 From: Rogiel Sulzbach To: "=?utf-8?Q?freebsd-arm=40freebsd.org?=" , Emmanuel Vadot Message-ID: <1270d2d0-7f10-4454-af30-d5d62ec5bd73@Spark> In-Reply-To: <20180612223248.f95d9ce3961187576e220614@bidouilliste.com> References: <20180612223248.f95d9ce3961187576e220614@bidouilliste.com> Subject: Re: De-orbit Allwinner A10/A20/A31 for 12.0 X-Readdle-Message-ID: 1270d2d0-7f10-4454-af30-d5d62ec5bd73@Spark MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Jun 2018 20:52:09 -0000 Hello Emmanuel, we have recently considered to switching from i.MX6 to a A20 for cost reasons. I have just bought a Banana Pi with an A20 to test performance and compare it to the Wandboard. The problem with H3 (and all other better socs) is the lack of a proper SATA controller. A real controller is only available in A10/A20 SoCs, all others go through a horrible SATA-to-USB adapter that is horribly slow. Anyway, in case we decide to switch, I can keep the A20 running -CURRENT. I might need some help getting started since I do not have a lot of experience in the kernel, other than the AHCI driver for the imx. On Jun 12, 2018, 5:33 PM -0300, Emmanuel Vadot , wrote: > > Hello arm@ > > I don't like to send this email but ... > > I want to remove A10/A20/A31 support for FreeBSD 12, here is the > reason why : > > - I don't have time to maintain thoses SoC > - For A10/A20 we currently don't boot on it since it requires new > clocks binding (handled by aw_ccung) and I have no time to do the > switch. > - H3 (which is 32bits too) is way better in term of performance and > price, you can buy a "good" $10 board while getting an A20 will cost > you more for some reason. > - My A31 board (BananapiM1) just died today after a long time of being > my arm32 reference board. > - I don't want the code to stay like the old 32 bits rockchip or > amlogic code that can't even boot nowadays. > > If someone want to step up and convert A10/A20 to ccung I'll be > glad to help/review but if no one step up it's unreasonable for me to > support those right now and I prefer to remove completely the support. > > The plan is to remove support in one month (July 12th) if there is no > volunteer to update the current code. > > Cheers, > > -- > Emmanuel Vadot > _______________________________________________ > 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 Jun 12 23:20: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 DBEB41008E3A for ; Tue, 12 Jun 2018 23:20:03 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 790E97EFB4 for ; Tue, 12 Jun 2018 23:20:03 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: by mailman.ysv.freebsd.org (Postfix) id 35E571008E31; Tue, 12 Jun 2018 23:20:03 +0000 (UTC) Delivered-To: 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 2305C1008E30 for ; Tue, 12 Jun 2018 23:20:03 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [18.222.6.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.soaustin.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C92087EFB1; Tue, 12 Jun 2018 23:20:02 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from lonesome.com (unknown [18.188.142.31]) by mail.soaustin.net (Postfix) with ESMTPSA id D4EC724937; Tue, 12 Jun 2018 23:20:01 +0000 (UTC) Date: Tue, 12 Jun 2018 23:20:00 +0000 From: Mark Linimon To: Emmanuel Vadot , imp@FreeBSD.org Cc: "freebsd-arm@freebsd.org" Subject: Re: De-orbit Allwinner A10/A20/A31 for 12.0 Message-ID: <20180612231959.GA10643@lonesome.com> References: <20180612223248.f95d9ce3961187576e220614@bidouilliste.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180612223248.f95d9ce3961187576e220614@bidouilliste.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Jun 2018 23:20:04 -0000 fwiw I have now heavily edited the wiki page for Allwinner (which I had been intending to do for some time) to reflect this possible deprecation. Can interested parties please go through this page and see if my changes are correct? Thanks. mcl From owner-freebsd-arm@freebsd.org Tue Jun 12 23:48:24 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 0B33A100B7BF for ; Tue, 12 Jun 2018 23:48:24 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 95A948040A for ; Tue, 12 Jun 2018 23:48:23 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 59233100B7AE; Tue, 12 Jun 2018 23:48:23 +0000 (UTC) Delivered-To: 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 1E53A100B7AD for ; Tue, 12 Jun 2018 23:48:23 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C598380408 for ; Tue, 12 Jun 2018 23:48:22 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from mail-lf0-f45.google.com (mail-lf0-f45.google.com [209.85.215.45]) (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)) (Authenticated sender: kevans) by smtp.freebsd.org (Postfix) with ESMTPSA id 633D4209B8 for ; Tue, 12 Jun 2018 23:48:22 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mail-lf0-f45.google.com with SMTP id q11-v6so1050748lfc.7 for ; Tue, 12 Jun 2018 16:48:22 -0700 (PDT) X-Gm-Message-State: APt69E1AP/2cwHHf58cK9sI9LVWlSYUVCuR6Pon+Bf6gRG6uQVQ98nhn RD+bpNVi3Ddon/W7LzSr+6AODL7osYPogYf7GkU= X-Google-Smtp-Source: ADUXVKJiLyWn1UX6Ya7HSAhKqhlR56aWx1GjtLMJCPSIpVOK91v3bsQOCJFgOdwnUiwl3kP6dqD8FNnqU4Jq8HueWUs= X-Received: by 2002:a2e:575c:: with SMTP id r28-v6mr1456373ljd.51.1528847301013; Tue, 12 Jun 2018 16:48:21 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a2e:8582:0:0:0:0:0 with HTTP; Tue, 12 Jun 2018 16:47:59 -0700 (PDT) In-Reply-To: <1270d2d0-7f10-4454-af30-d5d62ec5bd73@Spark> References: <20180612223248.f95d9ce3961187576e220614@bidouilliste.com> <1270d2d0-7f10-4454-af30-d5d62ec5bd73@Spark> From: Kyle Evans Date: Tue, 12 Jun 2018 18:47:59 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: De-orbit Allwinner A10/A20/A31 for 12.0 To: Rogiel Sulzbach Cc: "freebsd-arm@freebsd.org" , Emmanuel Vadot Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Jun 2018 23:48:24 -0000 On Tue, Jun 12, 2018 at 3:51 PM, Rogiel Sulzbach wrote: > On Jun 12, 2018, 5:33 PM -0300, Emmanuel Vadot , w= rote: >> >> Hello arm@ >> >> I don't like to send this email but ... >> >> I want to remove A10/A20/A31 support for FreeBSD 12, here is the >> reason why : >> >> - I don't have time to maintain thoses SoC >> - For A10/A20 we currently don't boot on it since it requires new >> clocks binding (handled by aw_ccung) and I have no time to do the >> switch. >> - H3 (which is 32bits too) is way better in term of performance and >> price, you can buy a "good" $10 board while getting an A20 will cost >> you more for some reason. >> - My A31 board (BananapiM1) just died today after a long time of being >> my arm32 reference board. >> - I don't want the code to stay like the old 32 bits rockchip or >> amlogic code that can't even boot nowadays. >> >> If someone want to step up and convert A10/A20 to ccung I'll be >> glad to help/review but if no one step up it's unreasonable for me to >> support those right now and I prefer to remove completely the support. >> >> The plan is to remove support in one month (July 12th) if there is no >> volunteer to update the current code. >> >> Cheers, >> >> -- >> Emmanuel Vadot > > Hello Emmanuel, > > we have recently considered to switching from i.MX6 to a A20 for cost rea= sons. > > I have just bought a Banana Pi with an A20 to test performance and compar= e it to the Wandboard. The problem with H3 (and all other better socs) is t= he lack of a proper SATA controller. A real controller is only available in= A10/A20 SoCs, all others go through a horrible SATA-to-USB adapter that is= horribly slow. > > Anyway, in case we decide to switch, I can keep the A20 running -CURRENT.= I might need some help getting started since I do not have a lot of experi= ence in the kernel, other than the AHCI driver for the imx. Hi Rogiel, FWIW- I'm going to go ahead and write the ccung bits for A10/A20 so that I can make use of my Lamobo R1 when the switch driver for that is finished. This is probably not a bad time to pare down the DTS+U-Boot we build for these SoC to what people are actually willing to claim they use with FreeBSD, though. Thanks, Kyle Evans From owner-freebsd-arm@freebsd.org Wed Jun 13 03:32: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 23B24101DA52 for ; Wed, 13 Jun 2018 03:32:11 +0000 (UTC) (envelope-from ganbold@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id AB2B068AB0 for ; Wed, 13 Jun 2018 03:32:10 +0000 (UTC) (envelope-from ganbold@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 6EDCC101DA4E; Wed, 13 Jun 2018 03:32:10 +0000 (UTC) Delivered-To: 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 49CC2101DA4B for ; Wed, 13 Jun 2018 03:32:10 +0000 (UTC) (envelope-from ganbold@gmail.com) Received: from mail-qt0-x22b.google.com (mail-qt0-x22b.google.com [IPv6:2607:f8b0:400d:c0d::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 D6F3C68AAC; Wed, 13 Jun 2018 03:32:09 +0000 (UTC) (envelope-from ganbold@gmail.com) Received: by mail-qt0-x22b.google.com with SMTP id d3-v6so1169583qto.1; Tue, 12 Jun 2018 20:32:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=5X8qzVd23tDVgbEJWDRBv9PjQqi1gLHDjnhXLR237pU=; b=pUmSBGLPgjN7OM8a1oI5XwXiawYgS0JGLTz8QcP/Gk127CjuljUQmj5xlQwwzQ0Z3J g1dSLJc0kh0yGpnxH9awST1JIwVdO5KezL3zy0p2BFICQ/0r3RvX9HezOmIuvH5sHCaU RarbVb5WtJLbjXByqnE9Igizx4qHWyASoBHeB7BAIkQAWWhx+mfTaYPFK9mMg8ABmWW2 fizwez4vzXCFVV5AOashoUqH8PJAY7xHiCzSn6YWjQqjE1nToQBTz1IrwZpTh0xxUq7l OLzEP/7tD2BnkmDPoM5Uz7UBkk7z6QswuhZ0HNa9YX+ObjW1oX9XIeBJtQkkVSVvy0WD qCKg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=5X8qzVd23tDVgbEJWDRBv9PjQqi1gLHDjnhXLR237pU=; b=O21R1q43TZylZjfHisMXHEKTB7PQu1uzwOHAwXyGETpg7RevDiS/O4RRkANMcXYMKR PPh2ikKdrwCt+Dx0/fiklIOgOcrOK9P9IW+VPZUjpRBLVqB4pF/wBxtsCtcQ5CXMP/zr 6PFbFBC7J7of2gs3WFmr1bDfAXeAqiALHjzI+AcnnnTYYXcSg37iFNcBY1E0fLSk+bfo 3UeSpVq7hU+8SyQqFUDJxDPkgV70biZvlH2SvhIc/tLWViTI0NjsW90tvM46jVtuYA7B 4lGMWcUhrazgTmwRvrgq94b8XGA1vuQCcZXFcwG/LCYz/jas7sS0+jcaS1v+lpJsexJI pe+g== X-Gm-Message-State: APt69E0fao4k53sejXIdGf8EmXWS8icC/V2jyr5L1yn979yB0tgEyNC/ cJMDFmMpd9cgUuGqhHxA8+TfXpvqjLndVcW8xOJ2aQ== X-Google-Smtp-Source: ADUXVKJE9skTp4fnVG0bPN2zME/kOKI7NakAuOrnjpvXEAz4qKwt9isgYCeZrjxDkZclhomjtCibfCzLUbcy4nWHqOk= X-Received: by 2002:aed:2459:: with SMTP id s25-v6mr3016701qtc.289.1528860729309; Tue, 12 Jun 2018 20:32:09 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:aed:3a27:0:0:0:0:0 with HTTP; Tue, 12 Jun 2018 20:32:08 -0700 (PDT) In-Reply-To: References: <20180612223248.f95d9ce3961187576e220614@bidouilliste.com> <1270d2d0-7f10-4454-af30-d5d62ec5bd73@Spark> From: Ganbold Tsagaankhuu Date: Wed, 13 Jun 2018 11:32:08 +0800 Message-ID: Subject: Re: De-orbit Allwinner A10/A20/A31 for 12.0 To: Kyle Evans , Emmanuel Vadot Cc: Rogiel Sulzbach , "freebsd-arm@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jun 2018 03:32:11 -0000 Hi, On Wed, Jun 13, 2018 at 7:47 AM, Kyle Evans wrote: > On Tue, Jun 12, 2018 at 3:51 PM, Rogiel Sulzbach > wrote: > > On Jun 12, 2018, 5:33 PM -0300, Emmanuel Vadot , > wrote: > >> > >> Hello arm@ > >> > >> I don't like to send this email but ... > >> > >> I want to remove A10/A20/A31 support for FreeBSD 12, here is the > >> reason why : > >> > >> - I don't have time to maintain thoses SoC > >> - For A10/A20 we currently don't boot on it since it requires new > >> clocks binding (handled by aw_ccung) and I have no time to do the > >> switch. > >> - H3 (which is 32bits too) is way better in term of performance and > >> price, you can buy a "good" $10 board while getting an A20 will cost > >> you more for some reason. > >> - My A31 board (BananapiM1) just died today after a long time of being > >> my arm32 reference board. > >> - I don't want the code to stay like the old 32 bits rockchip or > >> amlogic code that can't even boot nowadays. > >> > >> If someone want to step up and convert A10/A20 to ccung I'll be > >> glad to help/review but if no one step up it's unreasonable for me to > >> support those right now and I prefer to remove completely the support. > >> > >> The plan is to remove support in one month (July 12th) if there is no > >> volunteer to update the current code. > >> > >> Cheers, > >> > >> -- > >> Emmanuel Vadot > > > > Hello Emmanuel, > > > > we have recently considered to switching from i.MX6 to a A20 for cost > reasons. > > > > I have just bought a Banana Pi with an A20 to test performance and > compare it to the Wandboard. The problem with H3 (and all other better > socs) is the lack of a proper SATA controller. A real controller is only > available in A10/A20 SoCs, all others go through a horrible SATA-to-USB > adapter that is horribly slow. > > > > Anyway, in case we decide to switch, I can keep the A20 running > -CURRENT. I might need some help getting started since I do not have a lot > of experience in the kernel, other than the AHCI driver for the imx. > > Hi Rogiel, > > FWIW- I'm going to go ahead and write the ccung bits for A10/A20 so > that I can make use of my Lamobo R1 when the switch driver for that is > finished. > > This is probably not a bad time to pare down the DTS+U-Boot we build > for these SoC to what people are actually willing to claim they use > with FreeBSD, though. > First of all I would like to thank manu@ and kevans@ and other committers who improved the support of Allwinner SoC related codes and maintaining them up to now. I basically agree with manu@, but there could be few points we may have to consider: - It is nice to have the support of a board which has SATA controller, as mentioned Rogiel - According to https://wiki.freebsd.org/FreeBSD/arm/Allwinner most of drivers work on A20 boards (if we add ccung support) and it could be a reference code for attracting new developers, users etc. - If we nuke A10/A20 bits, then we maybe need to obtain some other boards with H3 SoC for gjb@ or anyone who builds official images, I believe those images are tested on those boards. - I know it is time consuming, but I think a developer has to make sure his/her code changes work across boards/SoC family, or at least ask others to test or apply similar changes to their boards/SoCs just to make sure everything works. Correct me if I'm wrong here. - I know I should be blamed for not updating Rockchip RK3188 and Amlogic codes, but I hope some of the bits can be used/referenced later on for boards with SoC like RK3328, RK3399 etc, since I do have the latter one. Kyle, Adding ccung support to A10/A20 is very much appreciated. I will wait for your switch driver, that would be really awesome. I think I have same board too :) thanks a lot for understanding, Ganbold > > Thanks, > > Kyle Evans > _______________________________________________ > 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 Wed Jun 13 06:54:01 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 D6AE8100B087; Wed, 13 Jun 2018 06:54:01 +0000 (UTC) (envelope-from alexandru.elisei@gmail.com) Received: from mail-qt0-x22b.google.com (mail-qt0-x22b.google.com [IPv6:2607:f8b0:400d:c0d::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 677A06FB2A; Wed, 13 Jun 2018 06:54:01 +0000 (UTC) (envelope-from alexandru.elisei@gmail.com) Received: by mail-qt0-x22b.google.com with SMTP id q6-v6so1439136qtn.7; Tue, 12 Jun 2018 23:54:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=Om6vSpYeUARpgjfylh+Y8ISpHAoE2CGctzRoOvQNJ+A=; b=O/panSuM439I5OW33PrBPoNw9jg0oDfumOMgZu5RewjW0m9uiHFvAtg+bDgU1BR3yo 7YDSU/Y3QxmPuuSfHs5IeK6FeluUTn5rFTmRGrtdKhnF3SOOLbT4Vye96EHn7ZyNUsxm qOxnKRXU0P5iPWLMZ5U/g+x48E+xfZZ8irYGfasToSxf8LbIR/2GuVCBrMvGwyGNJcb3 f5+snSNOcAGUyfVH+KOh2MSzrR00d6Tg0IcgpYao5ON4vqpuAiIdqXQ6+bGY9wTOLRqS mtAPxCKfNipKOT2mdYPq3+Kiuk7qdQt6ZqiY8AwqeAWvuDOwYBVRrYTT2JeoqCYl0TuW bjUA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=Om6vSpYeUARpgjfylh+Y8ISpHAoE2CGctzRoOvQNJ+A=; b=hS2Rd7+OjGfT9XhsWNpuZNZSdh3QaopjoFK4/CK1NoADo9+tqWFXcu4BzSeifnrrOa hG6t5librhSF+Hv7tZRlYnOS579VRwhOXSGOR66JNYasZSH352BTZAqLENyqB79qkuhn uJy1rH8UezuLftqH2yjxz2eFfwFIVzXcGuhi0JhluWKh58SqC0IcU+0EIV+0bV0vFlPw x4Fawp4ABhoGPqo2+60VdvNSq2B2vL5uUv16DMHEPoLkcqB1KLWVrLEFPKir59uaN1JX F7zJK10gwOqzwwUpIwjZXSyNPYVqRwxEkd0e3qZGerWf6PwYiuRldLqP44eBdl2LKhPg xQVA== X-Gm-Message-State: APt69E33SjqifVm5YqIE/ZPiO5iIZQvM3JJ2HDMzAGYqYYztUWLdhq4b jnccMEt0haLqw4ll1gf5B6VbbwYPUuM33hkJgcA= X-Google-Smtp-Source: ADUXVKKELUmYsT9P8pXwoo69oAbIOqr1oPQ1eoe3glCdmNQmAlq71YboNB0CJwZL1QDEc+tnynyOyyAEVV1Js+M0JTw= X-Received: by 2002:ac8:2f81:: with SMTP id l1-v6mr3422440qta.90.1528872840694; Tue, 12 Jun 2018 23:54:00 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:aed:2be7:0:0:0:0:0 with HTTP; Tue, 12 Jun 2018 23:54:00 -0700 (PDT) From: Alexandru Elisei Date: Wed, 13 Jun 2018 09:54:00 +0300 Message-ID: Subject: ARMv8 development board with GICv3 To: freebsd-arm@freebsd.org, freebsd-virtualization@freebsd.org Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jun 2018 06:54:02 -0000 Hello, I have been working on porting bhyve to ARMv8 and the hypervisor is able to successfully boot a FreeBSD virtual machine on the Foundation Emulator provided by ARM. I plan to submit the project for review, but before that I need to validate the hypervisor on a hardware platform. Can anyone be so kind as to recommend a development board for testing? The board needs to have an ARMv8 CPU with virtualization extensions implemented (Exception Level 2 needs to be available) and a GIC version 3 compliant interrupt controller. Thank you, Alexandru Elisei From owner-freebsd-arm@freebsd.org Wed Jun 13 07:06: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 BF833100C06C; Wed, 13 Jun 2018 07:06:41 +0000 (UTC) (envelope-from araujobsdport@gmail.com) Received: from mail-lf0-x242.google.com (mail-lf0-x242.google.com [IPv6:2a00:1450:4010:c07::242]) (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 29F3E702EB; Wed, 13 Jun 2018 07:06:41 +0000 (UTC) (envelope-from araujobsdport@gmail.com) Received: by mail-lf0-x242.google.com with SMTP id n3-v6so2206096lfe.12; Wed, 13 Jun 2018 00:06:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:reply-to:in-reply-to:references:from:date:message-id :subject:to:cc; bh=HyrfQX+TaEojxz2lEZJHr2o1MVoPQcno9fAvcrRFEBE=; b=QsUuZJGaPa5/z1nZvEuBorgld7W/gY/AgWc1cencbrA7PAvJlGKmntMly/wK3ENz0K 6DSTLGVtfP4y8JaDARQODucQJuIVoduWJdixSsZMWjml3CmXaCmmBeNFSr7D1InXPqph iUYzwo4Q5DbqX8apoazrUpsJ7i0a7db0+TZ1LmGTT+uM2KKVd1qo50Uc/wakbTP6hIRT esB2wAu8vlfRpV6EuKxVxdqA95adpXv0FMF5ortSOzHsENQ2W7I5NXoF+2Yx7wMlpD7K /M2jOHjnu6CsyzY/LGTjuya7f9mPwSaXt6r9tMy3mcf+AHWcID5DCm/E6Bx9Br1vGPPv 71Mg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to:cc; bh=HyrfQX+TaEojxz2lEZJHr2o1MVoPQcno9fAvcrRFEBE=; b=W9FOt4C9Ggrk68ze0hP2bmP0yTxs2VeYjXOJjt1KA9QLaLiYuqw8IEgSbCI0Qi8ft8 UJ5MAGCn3ax0JbzWKHlfx6LMPKxPuZmoGO8THo6e/M28DaBRoRiYkYbLK/83vqPzxBG8 KqXN1WylfgtbLjEjwjbV0LWpDSMQHLOK2YfpbDf2jStB9egSANfwtT0Ul66gmSqCRsqZ txNSpCw68iGbsrznDr7WRzxo0arTZ+l4WyAxluBflG0B3sbZFu8MD5y7o2nu7XFL2xRf XstYSDcjtPtpXnLr2cfpWUfSW8ps8SrGreo9lkMMocXAl17JWGePI73nknhZuQ/wuRKu QkMg== X-Gm-Message-State: APt69E3uuJwNaEVdYSotg9RzijIWLefZYLqW5jEU4aQGZhkb/UJA2pnG FPNQXMPb3ZV47EiYv0GzUo4WhoZVBkyXeLBHeM0= X-Google-Smtp-Source: ADUXVKJz0MUcryyXflosdEuJQRdOAEwSyfNildeypK0msQFgiE1pnDW+2+/hD7zztZ8NI61nCgjYsMyxWGuPTsYzwYw= X-Received: by 2002:a19:e585:: with SMTP id i5-v6mr2014364lfk.63.1528873599854; Wed, 13 Jun 2018 00:06:39 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a19:1f94:0:0:0:0:0 with HTTP; Wed, 13 Jun 2018 00:06:39 -0700 (PDT) Reply-To: araujo@freebsd.org In-Reply-To: References: From: Marcelo Araujo Date: Wed, 13 Jun 2018 15:06:39 +0800 Message-ID: Subject: Re: ARMv8 development board with GICv3 To: Alexandru Elisei Cc: freebsd-arm@freebsd.org, freebsd-virtualization@freebsd.org, manu@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jun 2018 07:06:42 -0000 2018-06-13 14:54 GMT+08:00 Alexandru Elisei : > Hello, > > I have been working on porting bhyve to ARMv8 and the hypervisor is > able to successfully boot a FreeBSD virtual machine on the Foundation > Emulator provided by ARM. > > I plan to submit the project for review, but before that I need to > validate the hypervisor on a hardware platform. > > Can anyone be so kind as to recommend a development board for testing? > The board needs to have an ARMv8 CPU with virtualization extensions > implemented (Exception Level 2 needs to be available) and a GIC > version 3 compliant interrupt controller. > > Thank you, > Alexandru Elisei > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to "freebsd-virtualization- > unsubscribe@freebsd.org" > Hello Alexandru, Excited to see your work! I have Cc manu@ as I know he works a lot with embedded devices and probably he can give you some suggestions. I'm sure he is on freebsd-arm@ mailing list, but even though I'm Cc'ing him. Best, -- -- Marcelo Araujo (__)araujo@FreeBSD.org \\\'',)http://www.FreeBSD.org \/ \ ^ Power To Server. .\. /_) From owner-freebsd-arm@freebsd.org Wed Jun 13 07:30: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 78DA3100DEAA; Wed, 13 Jun 2018 07:30:26 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.blih.net", Issuer "mail.blih.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 8CCAA715E6; Wed, 13 Jun 2018 07:30:24 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) by mail.blih.net (OpenSMTPD) with ESMTP id 74c1fefd; Wed, 13 Jun 2018 09:30:22 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=bidouilliste.com; h= mime-version:content-type:content-transfer-encoding:date:from:to :cc:subject:in-reply-to:references:message-id; s=mail; bh=vStCgF mWYHhi7LWPZd2AdJ5oJss=; b=SQRn/svoIk4MMZBoEHahUhWZU2DKzaUZmmg/Ch UWostxXlJ+ouXySNOXhF10hSBMoYqw0m1/sBDcCS8I5t3pm1/SqhXW+kIdvK6lNP Qxz6g/WexQHG1MxDW0iiMySXknNdQ1MRxXGxB/EVr01RVkm6T3dkzb0ub4qGadis aF5uA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=bidouilliste.com; h= mime-version:content-type:content-transfer-encoding:date:from:to :cc:subject:in-reply-to:references:message-id; q=dns; s=mail; b= UJWxW1e5Xc9bz4jeydRu9L58JZL1hXeQZdy4edbm8mLAdPnFwBF5RhZPnQxp0dvm 9zkLL05iHwoKULZmHQel4h2cVeYfw5PG5X6iozFUjg2fDX7qntzbeDkDCcMF8Jsp 2+a8to0HEaBJ0qwpgiimilndrVAGU5ohikZzqcPuask= Received: from webmail.megadrive.org (www1.blih.net [212.83.177.180]) by mail.blih.net (OpenSMTPD) with ESMTP id dc35180f; Wed, 13 Jun 2018 09:30:22 +0200 (CEST) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Wed, 13 Jun 2018 09:30:22 +0200 From: Emmanuel Vadot To: araujo@freebsd.org Cc: Alexandru Elisei , manu@freebsd.org, freebsd-arm@freebsd.org, freebsd-virtualization@freebsd.org, owner-freebsd-virtualization@freebsd.org Subject: Re: ARMv8 development board with GICv3 Organization: Bidouilliste In-Reply-To: References: Message-ID: X-Sender: manu@bidouilliste.com User-Agent: Roundcube Webmail/1.1.1 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jun 2018 07:30:26 -0000 On 2018-06-13 09:06, Marcelo Araujo wrote: > 2018-06-13 14:54 GMT+08:00 Alexandru Elisei > : > >> Hello, >> >> I have been working on porting bhyve to ARMv8 and the hypervisor is >> able to successfully boot a FreeBSD virtual machine on the Foundation >> Emulator provided by ARM. >> >> I plan to submit the project for review, but before that I need to >> validate the hypervisor on a hardware platform. >> >> Can anyone be so kind as to recommend a development board for testing? >> The board needs to have an ARMv8 CPU with virtualization extensions >> implemented (Exception Level 2 needs to be available) and a GIC >> version 3 compliant interrupt controller. >> >> Thank you, >> Alexandru Elisei >> _______________________________________________ >> freebsd-virtualization@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization >> To unsubscribe, send any mail to "freebsd-virtualization- >> unsubscribe@freebsd.org" >> > > Hello Alexandru, > > Excited to see your work! > > I have Cc manu@ as I know he works a lot with embedded devices and > probably > he can give you some suggestions. > I'm sure he is on freebsd-arm@ mailing list, but even though I'm Cc'ing > him. > > Best, > -- A quick grep in the linux dts directory for arm64 give me a few SoC where we boot on it : Thunderx and Marvell 37XX. That being said I think you better try with a gic-v2 board as I adviced in AsiaBSDCon this year. Cheers, -- Emmanuel Vadot From owner-freebsd-arm@freebsd.org Wed Jun 13 07:37: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 34B85100E940; Wed, 13 Jun 2018 07:37:20 +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 A767C71BD9; Wed, 13 Jun 2018 07:37:19 +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 w5D7bH7Z038234; Wed, 13 Jun 2018 00:37:17 -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 w5D7bHxX038233; Wed, 13 Jun 2018 00:37:17 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201806130737.w5D7bHxX038233@pdx.rh.CN85.dnsmgr.net> Subject: Re: ARMv8 development board with GICv3 In-Reply-To: To: Alexandru Elisei Date: Wed, 13 Jun 2018 00:37:17 -0700 (PDT) CC: freebsd-arm@freebsd.org, freebsd-virtualization@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.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jun 2018 07:37:20 -0000 > Hello, > > I have been working on porting bhyve to ARMv8 and the hypervisor is > able to successfully boot a FreeBSD virtual machine on the Foundation > Emulator provided by ARM. > > I plan to submit the project for review, but before that I need to > validate the hypervisor on a hardware platform. > > Can anyone be so kind as to recommend a development board for testing? > The board needs to have an ARMv8 CPU with virtualization extensions > implemented (Exception Level 2 needs to be available) and a GIC > version 3 compliant interrupt controller. I believe the Chromebook SNOW meets the criteria, not exactly a "board" but I have one on loan from Michael Dexter that was originally purhased to support ARMv8 bhyve work. Not sure that it has a version 3 GIC either. Actually I am thinking that you have to do the software GIC on this platform. I have booted various versions of FreeBSD on it, the most annoying problem is that the built in keyboard goes into continuous autorepeat as soon as you try to login, but a USB attached keyboard works fine. > Thank you, > Alexandru Elisei -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-arm@freebsd.org Wed Jun 13 07:39: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 AE5E2100EDBD; Wed, 13 Jun 2018 07:39:49 +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 1FADB71DF8; Wed, 13 Jun 2018 07:39:48 +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 w5D7dhgC038253; Wed, 13 Jun 2018 00:39:43 -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 w5D7dh75038252; Wed, 13 Jun 2018 00:39:43 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201806130739.w5D7dh75038252@pdx.rh.CN85.dnsmgr.net> Subject: Re: ARMv8 development board with GICv3 In-Reply-To: To: Emmanuel Vadot Date: Wed, 13 Jun 2018 00:39:43 -0700 (PDT) CC: araujo@freebsd.org, manu@freebsd.org, freebsd-arm@freebsd.org, owner-freebsd-virtualization@freebsd.org, freebsd-virtualization@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.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jun 2018 07:39:49 -0000 > On 2018-06-13 09:06, Marcelo Araujo wrote: > > 2018-06-13 14:54 GMT+08:00 Alexandru Elisei > > : > > > >> Hello, > >> > >> I have been working on porting bhyve to ARMv8 and the hypervisor is > >> able to successfully boot a FreeBSD virtual machine on the Foundation > >> Emulator provided by ARM. > >> > >> I plan to submit the project for review, but before that I need to > >> validate the hypervisor on a hardware platform. > >> > >> Can anyone be so kind as to recommend a development board for testing? > >> The board needs to have an ARMv8 CPU with virtualization extensions > >> implemented (Exception Level 2 needs to be available) and a GIC > >> version 3 compliant interrupt controller. > >> > >> Thank you, > >> Alexandru Elisei > > > > Hello Alexandru, > > > > Excited to see your work! > > > > I have Cc manu@ as I know he works a lot with embedded devices and > > probably > > he can give you some suggestions. > > I'm sure he is on freebsd-arm@ mailing list, but even though I'm Cc'ing > > him. > > > > Best, > > -- > > A quick grep in the linux dts directory for arm64 give me a few SoC > where we boot on it : > > Thunderx and Marvell 37XX. > > That being said I think you better try with a gic-v2 board as I adviced > in AsiaBSDCon this year. Emmanuel, Can you tell me what GIC is in the Samsung Chromebook SNOW? https://www.chromium.org/chromium-os/developer-information-for-chrome-os-devices/samsung-arm-chromebook Thanks, Rod > Emmanuel Vadot -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-arm@freebsd.org Wed Jun 13 07:54:41 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 32722101028F; Wed, 13 Jun 2018 07:54:41 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.blih.net", Issuer "mail.blih.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 52E5272867; Wed, 13 Jun 2018 07:54:40 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) by mail.blih.net (OpenSMTPD) with ESMTP id 3f8778ff; Wed, 13 Jun 2018 09:54:38 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; s=mail; bh=FrkieOfGnuhq+BP/dHtgR1h80QY=; b=dO9unX9+oypx6fvCTWjntdCmJ8Q9 YdJTtOFRQ+vkOEe/Hvce2uFYluwjA78fpXpiX6jewHqhagIM0Pz7ihaiEZlXPYg9 UBeT2LsT/q1MLTaD4wN5LH9Fkd3FxFT7jf2+xCqhnzAypaq85Y2rhpFWJ2N6iP22 tBb9V2R+BSkKOPU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; q=dns; s= mail; b=mxE5Wjw60cCDm795e95x9c49TIs7saMQKv3CdHgOicICESj0KdIA+uPm NN+6JbXk6C2EAXXJBFgqY7vdYby8j9i6Ou37xB/qGhfXg01evwF/rdLz1iXz7uT7 B/Ne+VYs1xZ/do/LrvHn1YiDUnSSRElkqPXYiQsaBXsw/EXFUNw= Received: from skull.home.blih.net (ip-9.net-89-3-105.rev.numericable.fr [89.3.105.9]) by mail.blih.net (OpenSMTPD) with ESMTPSA id ea7b3001 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Wed, 13 Jun 2018 09:54:38 +0200 (CEST) Date: Wed, 13 Jun 2018 09:54:38 +0200 From: Emmanuel Vadot To: "Rodney W. Grimes" Cc: araujo@freebsd.org, manu@freebsd.org, freebsd-arm@freebsd.org, owner-freebsd-virtualization@freebsd.org, freebsd-virtualization@freebsd.org Subject: Re: ARMv8 development board with GICv3 Message-Id: <20180613095438.e7ae85bf86c841277ef0a379@bidouilliste.com> In-Reply-To: <201806130739.w5D7dh75038252@pdx.rh.CN85.dnsmgr.net> References: <201806130739.w5D7dh75038252@pdx.rh.CN85.dnsmgr.net> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; amd64-portbld-freebsd12.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jun 2018 07:54:41 -0000 On Wed, 13 Jun 2018 00:39:43 -0700 (PDT) "Rodney W. Grimes" wrote: > > On 2018-06-13 09:06, Marcelo Araujo wrote: > > > 2018-06-13 14:54 GMT+08:00 Alexandru Elisei > > > : > > > > > >> Hello, > > >> > > >> I have been working on porting bhyve to ARMv8 and the hypervisor is > > >> able to successfully boot a FreeBSD virtual machine on the Foundation > > >> Emulator provided by ARM. > > >> > > >> I plan to submit the project for review, but before that I need to > > >> validate the hypervisor on a hardware platform. > > >> > > >> Can anyone be so kind as to recommend a development board for testing? > > >> The board needs to have an ARMv8 CPU with virtualization extensions > > >> implemented (Exception Level 2 needs to be available) and a GIC > > >> version 3 compliant interrupt controller. > > >> > > >> Thank you, > > >> Alexandru Elisei > > > > > > Hello Alexandru, > > > > > > Excited to see your work! > > > > > > I have Cc manu@ as I know he works a lot with embedded devices and > > > probably > > > he can give you some suggestions. > > > I'm sure he is on freebsd-arm@ mailing list, but even though I'm Cc'ing > > > him. > > > > > > Best, > > > -- > > > > A quick grep in the linux dts directory for arm64 give me a few SoC > > where we boot on it : > > > > Thunderx and Marvell 37XX. > > > > That being said I think you better try with a gic-v2 board as I adviced > > in AsiaBSDCon this year. > > Emmanuel, > > Can you tell me what GIC is in the Samsung Chromebook SNOW? > https://www.chromium.org/chromium-os/developer-information-for-chrome-os-devices/samsung-arm-chromebook > > Thanks, > Rod Well it's cortex a15 so 32 bits so clearly not v3. https://github.com/torvalds/linux/blob/master/arch/arm/boot/dts/exynos5.dtsi#L88 -- Emmanuel Vadot From owner-freebsd-arm@freebsd.org Wed Jun 13 08:01: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 2349A1010C27 for ; Wed, 13 Jun 2018 08:01:36 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id A08F472DEF for ; Wed, 13 Jun 2018 08:01:35 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: by mailman.ysv.freebsd.org (Postfix) id 609DE1010C1D; Wed, 13 Jun 2018 08:01:35 +0000 (UTC) Delivered-To: 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 225531010C19 for ; Wed, 13 Jun 2018 08:01:35 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.blih.net", Issuer "mail.blih.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 80C4C72DEA; Wed, 13 Jun 2018 08:01:34 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) by mail.blih.net (OpenSMTPD) with ESMTP id 7479aa05; Wed, 13 Jun 2018 10:01:33 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; s=mail; bh=gk5EP7JLkDRH3asq2At+JRmJhUk=; b=VkrlLUstzPczqZJ2e7NBeyUwbQsw FO8NIXks8qC5C22sJGU4outIzsBipQJO78FppYl8otwT7Es6i41xna4ruFVVvJWE qN4vBJoQhpiyVMJNknDDCs4CWvS/qxT7Dud1OpjIG6u2weXzhMgY0gj6ZzqsDPV2 1fT9h9QugzZ8zVA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; q=dns; s= mail; b=i33x+1Qf7hEOrHjD2kBo5H5IlcW2R98q4dEW++v4vJtY+1mneJeQg3Gq vro/wKWXHcWf28qFf4eCOznwEeTtHrPtquGAOIrkqeyBC9zS7rlZVA2QOc5IkCII cJdCHClxXec0/aJc6dwBCzk4xkdG+uT328lOn0scvRydKqtPPsc= Received: from skull.home.blih.net (ip-9.net-89-3-105.rev.numericable.fr [89.3.105.9]) by mail.blih.net (OpenSMTPD) with ESMTPSA id a37d8573 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Wed, 13 Jun 2018 10:01:32 +0200 (CEST) Date: Wed, 13 Jun 2018 10:01:32 +0200 From: Emmanuel Vadot To: Ganbold Tsagaankhuu Cc: Kyle Evans , Rogiel Sulzbach , "freebsd-arm@freebsd.org" Subject: Re: De-orbit Allwinner A10/A20/A31 for 12.0 Message-Id: <20180613100132.af9a6fa4e4c9d627ffd28a5a@bidouilliste.com> In-Reply-To: References: <20180612223248.f95d9ce3961187576e220614@bidouilliste.com> <1270d2d0-7f10-4454-af30-d5d62ec5bd73@Spark> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; amd64-portbld-freebsd12.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jun 2018 08:01:36 -0000 On Wed, 13 Jun 2018 11:32:08 +0800 Ganbold Tsagaankhuu wrote: > Hi, > > On Wed, Jun 13, 2018 at 7:47 AM, Kyle Evans wrote: > > > On Tue, Jun 12, 2018 at 3:51 PM, Rogiel Sulzbach > > wrote: > > > On Jun 12, 2018, 5:33 PM -0300, Emmanuel Vadot , > > wrote: > > >> > > >> Hello arm@ > > >> > > >> I don't like to send this email but ... > > >> > > >> I want to remove A10/A20/A31 support for FreeBSD 12, here is the > > >> reason why : > > >> > > >> - I don't have time to maintain thoses SoC > > >> - For A10/A20 we currently don't boot on it since it requires new > > >> clocks binding (handled by aw_ccung) and I have no time to do the > > >> switch. > > >> - H3 (which is 32bits too) is way better in term of performance and > > >> price, you can buy a "good" $10 board while getting an A20 will cost > > >> you more for some reason. > > >> - My A31 board (BananapiM1) just died today after a long time of being > > >> my arm32 reference board. > > >> - I don't want the code to stay like the old 32 bits rockchip or > > >> amlogic code that can't even boot nowadays. > > >> > > >> If someone want to step up and convert A10/A20 to ccung I'll be > > >> glad to help/review but if no one step up it's unreasonable for me to > > >> support those right now and I prefer to remove completely the support. > > >> > > >> The plan is to remove support in one month (July 12th) if there is no > > >> volunteer to update the current code. > > >> > > >> Cheers, > > >> > > >> -- > > >> Emmanuel Vadot > > > > > > Hello Emmanuel, > > > > > > we have recently considered to switching from i.MX6 to a A20 for cost > > reasons. > > > > > > I have just bought a Banana Pi with an A20 to test performance and > > compare it to the Wandboard. The problem with H3 (and all other better > > socs) is the lack of a proper SATA controller. A real controller is only > > available in A10/A20 SoCs, all others go through a horrible SATA-to-USB > > adapter that is horribly slow. > > > > > > Anyway, in case we decide to switch, I can keep the A20 running > > -CURRENT. I might need some help getting started since I do not have a lot > > of experience in the kernel, other than the AHCI driver for the imx. > > > > Hi Rogiel, > > > > FWIW- I'm going to go ahead and write the ccung bits for A10/A20 so > > that I can make use of my Lamobo R1 when the switch driver for that is > > finished. > > > > This is probably not a bad time to pare down the DTS+U-Boot we build > > for these SoC to what people are actually willing to claim they use > > with FreeBSD, though. > > > > > First of all I would like to thank manu@ and kevans@ and other committers > who improved the support of Allwinner SoC related codes and maintaining > them up to now. > I basically agree with manu@, but there could be few points we may have to > consider: > - It is nice to have the support of a board which has SATA controller, as > mentioned Rogiel Yes that's for me the only interesting thing on those SoC nowadays. > - According to https://wiki.freebsd.org/FreeBSD/arm/Allwinner most of > drivers work on A20 boards (if we add ccung support) and it could be a > reference code for attracting new developers, users etc. Correct the only missing thing is ccung (and test/maintainance of course) > - If we nuke A10/A20 bits, then we maybe need to obtain some other boards > with H3 SoC for gjb@ or anyone who builds official images, I believe those > images are tested on those boards. I plan to deorbit some images and make a generic image, now sure how for now that's all :) > - I know it is time consuming, but I think a developer has to make sure > his/her code changes work across boards/SoC family, or at least ask others > to test or apply similar changes to their boards/SoCs just to make sure > everything works. Correct me if I'm wrong here. Sure, that's why I always test on 32bit allwinner (A31/H3) and 64bit (A64/H5) > - I know I should be blamed for not updating Rockchip RK3188 and Amlogic > codes, but I hope some of the bits can be used/referenced later on for > boards with SoC like RK3328, RK3399 etc, since I do have the latter one. Nothing to be blamed for, we all have a life :) I had a quick glance at the rockchip code before starting working on RK3328 and I think that now everything supported before is supported for 64bits SoC (with a few extras) > Kyle, > > Adding ccung support to A10/A20 is very much appreciated. > I will wait for your switch driver, that would be really awesome. > I think I have same board too :) > > thanks a lot for understanding, > > Ganbold > > > > > > > Thanks, > > > > Kyle Evans > > _______________________________________________ > > 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" > > -- Emmanuel Vadot From owner-freebsd-arm@freebsd.org Wed Jun 13 08:02: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 A08101010EE4; Wed, 13 Jun 2018 08:02:33 +0000 (UTC) (envelope-from alexandru.elisei@gmail.com) Received: from mail-qk0-x244.google.com (mail-qk0-x244.google.com [IPv6:2607:f8b0:400d:c09::244]) (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 3BFE472F2A; Wed, 13 Jun 2018 08:02:33 +0000 (UTC) (envelope-from alexandru.elisei@gmail.com) Received: by mail-qk0-x244.google.com with SMTP id g14-v6so983265qkm.6; Wed, 13 Jun 2018 01:02:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=0JHfuVWUVT/9L4yaq0sTd1eljiifxhU5M64+4xbD/TA=; b=IM/LNy6QTaFiDcek8+dn+0sxp/rrq38WIF4M4/RH+yBZPWDvkdQB7NPB49ncj8gY9z yY8mXzJ14DV4A0YyFjAYV40FWP71BmuMIUvVKgD3DazejR0H0qyVkKKRVdHDfZ+exNTh p9CLNnMzYDt+XlwSMD25ypi7m7rVLWsYPdICOojND/63d8tE8kT0D18ySgEOUA2/3i7w IQFmuZzKqa1ndnDt6K0inaBIGYqmXpxVGOyx2Hf/B3mSP01Lvjat2ENjUKsphjsmIDRt Bbfma+hZ2nYP0yNtIZuLfWfqCtG+oCuD3fuLootH6meyPsjcFgCAgNF1+3rP3+//Pc1P zsHA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=0JHfuVWUVT/9L4yaq0sTd1eljiifxhU5M64+4xbD/TA=; b=kTndk4dVrIWfKQLijz0KcK6ZoJcs37u8d61tgS6PiTr0VPTSuLu/pE0I/eu/qI76gV ZqhHCU4n8LoU9+YUYLVyXpOq/pYWC0Wl7MF83fRqxckMsqxrA1hceCkH6kE2x9Hq/rIU XeaGxSPUwkbS7xg8eGSVCCuPdGxbHThChUSV47yPfKuU6pPttB0tmLKBZRuBtUxajN6B +QaVs1XF44S+LquZTT9B9hucfx68tl3zRdNIjQg0VpeYQj8RYWu8TVdfzrx2dp9AmKCC Bf+DOczeBNFaCHRGS25xOpDsRv36yh4q9NpQN8/hUW/Kyi6w82er62evrtw1DsruDlKN LrHw== X-Gm-Message-State: APt69E1aNk/4nJN8kmAaiIIIYHCukH3bjYL+63eDg8xUSAnpCSzZukv0 9dJPmasAVTg0zpKZIjE7hfJ8OG3f2gKChgr3JN8b+H+U X-Google-Smtp-Source: ADUXVKKUse7coZLCf3UJ2qAslBmsJ5+NPMnpO4f3GCyLML1gbDVQNr6jaPzVcXbMNZaTYrGPXyWbogD9GeMF0xoG9l4= X-Received: by 2002:ae9:e118:: with SMTP id g24-v6mr3308789qkm.99.1528876952530; Wed, 13 Jun 2018 01:02:32 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:aed:2be7:0:0:0:0:0 with HTTP; Wed, 13 Jun 2018 01:02:31 -0700 (PDT) In-Reply-To: References: From: Alexandru Elisei Date: Wed, 13 Jun 2018 11:02:31 +0300 Message-ID: Subject: Re: ARMv8 development board with GICv3 To: Emmanuel Vadot Cc: araujo@freebsd.org, manu@freebsd.org, freebsd-arm@freebsd.org, freebsd-virtualization@freebsd.org, owner-freebsd-virtualization@freebsd.org, Alexandru Elisei Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jun 2018 08:02:33 -0000 On Wed, Jun 13, 2018 at 10:30 AM, Emmanuel Vadot wrote: > A quick grep in the linux dts directory for arm64 give me a few SoC where > we boot on it : > > Thunderx and Marvell 37XX. > > That being said I think you better try with a gic-v2 board as I adviced in > AsiaBSDCon this year. I have virtualized the GICv3 controller as it is the newer version and I would like to validate this version on a board. GICv2 virtualization was done for the ARMv7 version of bhyve and the two versions haven't been yet integrated and I am not familiar with the code, as GICv2 is architecturally different from GICv3. > > Cheers, > > > -- > Emmanuel Vadot From owner-freebsd-arm@freebsd.org Wed Jun 13 09:34: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 0D5621019179 for ; Wed, 13 Jun 2018 09:34:40 +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 11D1D779F3 for ; Wed, 13 Jun 2018 09:34:39 +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 8A4B520FD4 for ; Wed, 13 Jun 2018 09:34:37 +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 w5D9Yb8m028997 for ; Wed, 13 Jun 2018 09:34:37 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w5D9YbSV028996 for freebsd-arm@FreeBSD.org; Wed, 13 Jun 2018 09:34:37 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 228977] /etc/devd/devmatch.conf has bad 'action' line Date: Wed, 13 Jun 2018 09:34:37 +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 Many People X-Bugzilla-Who: bobf@mrp3.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.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jun 2018 09:34:40 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D228977 Bug ID: 228977 Summary: /etc/devd/devmatch.conf has bad 'action' line Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: arm Assignee: freebsd-arm@FreeBSD.org Reporter: bobf@mrp3.com The new /etc/devd/devmatch.conf has an action line for 'nomatch' in it that does not work correctly. Instead of passing a single argument containing embedded white space to the /etc/rc.d/devmatch script as parameter 2, the 'service' command strips off = the single quote characters, which causes the parameter to be passed as multiple arguments to the 'devmatch' script, instead. This causes the devmatch program to receive '?' as the parameter following = '-p' which gives you an error message similar to: devmatch: Malformed NOMATCH string: '' A simple workaround can be performed by using the following action string: action "/etc/rc.d/devmatch start '?$_'"; this avoids calling 'service' and invokes the rc script directly. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-arm@freebsd.org Wed Jun 13 15:48: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 78A7A10172BE for ; Wed, 13 Jun 2018 15:48: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 D55226A094 for ; Wed, 13 Jun 2018 15:48: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 w5DFmQ5g024226 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 13 Jun 2018 08:48:27 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w5DFmQ6M024225; Wed, 13 Jun 2018 08:48:26 -0700 (PDT) (envelope-from fbsd) Date: Wed, 13 Jun 2018 08:48:26 -0700 From: bob prohaska To: freebsd-arm@freebsd.org Subject: GPT vs MBR for swap devices Message-ID: <20180613154826.GA24146@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.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jun 2018 15:48:20 -0000 In trying to get a Pi3 at r334939 to run -j4 buildworld it's become clear that a USB flash (Sandisk Extreme) swap device very quickly triggers OOM process kills, while a USB mechanical disk swap devices works perfectly. It's somewhat hard to believe that the Sandisk Extreme is much slower than a mechanical hard drive for small reads and writes if the rated speeds are anywhere close to correct, but it happens that the flash device uses MBR partitioning, while the mechanical hard drive uses GPT. Is there any reason to think that the partitioning scheme matters? Thanks for reading, bob prohaska From owner-freebsd-arm@freebsd.org Wed Jun 13 16:09:22 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 396921019396 for ; Wed, 13 Jun 2018 16:09:22 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x231.google.com (mail-io0-x231.google.com [IPv6:2607:f8b0:4001:c06::231]) (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 BC4D06B360 for ; Wed, 13 Jun 2018 16:09:21 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x231.google.com with SMTP id g7-v6so3993631ioh.11 for ; Wed, 13 Jun 2018 09:09:21 -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=H+iUrrMi7lATmndFPsVim+tG34gkceJ9K4G4j9puzzk=; b=eZz46bAFGcme4VT10Pkano+cV5TqmjUCkSzZiarSe8rJ+4jjizuDBYT7Hr+kEoyZTq 5rDtWeJlCb0H+8H7GB7dCagvC8FAz41eUJC8X43PeAKB5JKD2cE114I6QFtSTlFXUzkQ zx3KpELfslWQB26MY/By7ShWz46YfF1o4KrpnwgLfDSSO7oFvNAJsR4AKmJ9Nvj5me01 XuxWlsg/TWSXiJIN9qxH0/t06VlObHYI42z5uWVtv9xCPu3vVdL5xMJ1ZmcKzFj363b8 S2uxCUN4p7tClubuPKgDpuFGGLfoKTep1uUdVCqoR6S5l1L7MdKHaT7fLb0tzKv1yvlh cvVw== 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=H+iUrrMi7lATmndFPsVim+tG34gkceJ9K4G4j9puzzk=; b=iORgqGJUd3wVBst6SCz1uhSnsGPw8C7/Jfcru+IEhIBF9+jtqh9RJe+B+56ax6ZCMl YRXLQISnPL0BGCxnzMt0wlT2rZq0YxHegP8OokRZO3kLw1A7/agnxrnoVIZdgYUkgRQe pc7/pmliCo0Hb845q9lqO2AcVBnYWBwQBow7DwcVkD6C6735c6uLEdRmssSBtZJE5uaD +2AJZNtuzwOv4opg53g6+aaagBQupPP+lfqhQuoDuMMvdBqbZ4Q90lHg/ze5SeuLjBAF osvPzCmbiOQMUW1DhDPqBoSQxQ4n6tUAlwzz0VMzLgWUv9TA3Sr1tWu6/BHI5s0J2ZTr 9dzQ== X-Gm-Message-State: APt69E3JXPHDJa2k50IccpG1KhYNezuzbWRLvY5e8HUmw2GBMhRrioxv irhdnvZ9phbTsky23mK/tV2WYZf9b1GwiVHov1y6sg== X-Google-Smtp-Source: ADUXVKItyKrqhu1dOJ1mGp0xNj5li9JQJ0dHX3US/ow6/ZfKXHZ0sW5r91tcRKgvh9B+WcCmQAiexEhPNBx3UQQ6bNA= X-Received: by 2002:a6b:29c4:: with SMTP id p187-v6mr5162247iop.299.1528906160857; Wed, 13 Jun 2018 09:09:20 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 2002:a4f:d028:0:0:0:0:0 with HTTP; Wed, 13 Jun 2018 09:09:20 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: <20180613154826.GA24146@www.zefox.net> References: <20180613154826.GA24146@www.zefox.net> From: Warner Losh Date: Wed, 13 Jun 2018 10:09:20 -0600 X-Google-Sender-Auth: _AzAfjDb5M-AT6LtHZC08ZsWPcE Message-ID: Subject: Re: GPT vs MBR for swap devices To: bob prohaska Cc: "freebsd-arm@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jun 2018 16:09:22 -0000 On Wed, Jun 13, 2018 at 9:48 AM, bob prohaska wrote: > In trying to get a Pi3 at r334939 to run -j4 buildworld it's become clear > that a USB flash (Sandisk Extreme) swap device very quickly triggers OOM > process kills, while a USB mechanical disk swap devices works perfectly. > > It's somewhat hard to believe that the Sandisk Extreme is much slower than > a mechanical hard drive for small reads and writes if the rated speeds are > anywhere close to correct, but it happens that the flash device uses MBR > partitioning, while the mechanical hard drive uses GPT. > > Is there any reason to think that the partitioning scheme matters? > Usually, partitioning doesn't matter. USB flash drives are optimized for (a) being big and (b) writing large files, infrequently. Neither of these is good for swap space. So, lots of 'small' writes that the swapper does can often trigger pathological behavior in the drive's FTL (that's a polite way to say performance goes through the floor). I've seen on SSDs, which have better FTLs, that can easily do 500MB/s drop to 10-20MB/s when reads and writes are mixed with the wrong workload. Our swapper is written with the assumption that all writes are equal and small ones are better than larger ones (since they free up the dirty pages faster). However, you can often get better performance out of larger writes and I don't think there's a knob to twist for that. I should have added (c) and sometimes for FAT file systems. That used to be the case. And for that MBR used to be a little better. However, that was 5 years ago or so. With the new Sandisk Extreme drives it isn't so much since they are so large and FAT isn't good enough for most people these days. My experience with them recently has been they are OK drives. The write speed is kinda crappy (maybe 50-60MB/s when streaming a file to them, and 20-3MB/s in a mixed workload), but their read speed is surprisingly good at up to about 200MB/s when there's no flash contention. My main concern, though, was copying a 16GB video to them and making sure it would play back OK. For that they are good. For backing up the video project with all it's little files, not so good, and doing 'du' on it while copying slowed the copying down a lot, even though it wasn't that much traffic to the drive. All of this was on macOS, though. Warner From owner-freebsd-arm@freebsd.org Wed Jun 13 16:55:02 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 6017A101D0C9 for ; Wed, 13 Jun 2018 16:55:02 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x235.google.com (mail-io0-x235.google.com [IPv6:2607:f8b0:4001:c06::235]) (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 E6FE26D792 for ; Wed, 13 Jun 2018 16:55:01 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x235.google.com with SMTP id g22-v6so4166288iob.7 for ; Wed, 13 Jun 2018 09:55:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:from:date:message-id:subject:to; bh=2aKFOs8JpfpEWlQ4BkYEukDvz6TSfUjBH58hlnbY8pY=; b=NgfZPTcTlsyj8A09GewCUdYN7hSVfT/r1p6fwjAh1mlAxMjVDHmecIePNl7MDUPOst CxGX2jIW9SBonKn18WGL1iW7Er9VVfw0pb5VKk07Cjb2uMrrfm+gbSwkCCa+oPL2WJu8 yEJbxwNz8GhUhqq0UQ/NieSWCDQsCF2ycVRHmy+eQHO9abYZDkgXsa6G0wSB+0dmddBQ 3NEHv8FeJDUTQBWFG7NtN1GvzhAV9CxuwrYCqfDjlQL2yD1zaog7Tsh2Qa6jizPQ1wyr afdm2efMJ1VhQEnwZ2QlWVJehtQm5z72+RutK6U8LYc5FJtM+HvVOHR5i7hruA7mrUTQ tFQA== 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:from:date:message-id:subject :to; bh=2aKFOs8JpfpEWlQ4BkYEukDvz6TSfUjBH58hlnbY8pY=; b=c6Qqradb8khR+MSiR802vXjdzZ4VyeJbsKK0WpvYXVJxqhk0UhoEUbtRJAoraEGd92 MuYcx+yakqdwIoLMwiiRZSALYeWRHck0MfSpheT972OqVZ4vQjWcIiIQA+NrLRlNTqH4 msohVCx/R2A6FZCYm5rCTen1rXQDC+YfF/3jv9eql9ip7GQUkEeVxrlL++a39SQZRitl GYc0Jg8bS20krxeQ4C05+LAzI5lumVQNA+O9xzUkYNuuXi1ai7SO40wBf3BoBEQ3Kvbm YAXWfsPJh26itoT1RFD/c6Uky0VhG9cpEUa5DCykpLHFPSgciHmCaR28HtgyI12NBJzQ RhuA== X-Gm-Message-State: APt69E0qsgWCe3n2Aj1unDulJoQfLDDEcLjWsqqo8fN5FwevbnDlaloV s29q+BPBVXb5rk7ZAhNgo/MlrDogtExaZORgI4IxWw== X-Google-Smtp-Source: ADUXVKIB8X4khFyZtvKy77a4MqFjSksaDyPRK7dTL6AYjmKW7J93VDI4kkG4nI8GQBhs4ohThOzFJC6K2ANT4aLRGQA= X-Received: by 2002:a6b:284b:: with SMTP id o72-v6mr5465092ioo.168.1528908901061; Wed, 13 Jun 2018 09:55:01 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 2002:a4f:d028:0:0:0:0:0 with HTTP; Wed, 13 Jun 2018 09:55:00 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] From: Warner Losh Date: Wed, 13 Jun 2018 10:55:00 -0600 X-Google-Sender-Auth: h9Bm_aNWs8qMbqDzpb90_V9u4-Y Message-ID: Subject: 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.26 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jun 2018 16:55:02 -0000 I'd like to remove armeb before 12.0. It's poorly supported today. Nobody has tested the concurrency kit changes on it. And ck is now mandatory. We don't even know if it works or not. Last time we asked, it took quite a while to find users. It maxes out at 256MB of RAM. This is barely large enough for FreeBSD to run in. The hardware was last made almost a decade ago. It uses non-standard non-mainstream boot loaders (boot technology has moved on from redboot). The cost of doing API sweeps, make universe runs, etc exceeds the benefit to the project. So, given all these factors, it sounds like a good candidate for retirement. Therefore, I'd like to remove it on July 15th. Comments? (please keep them on topic to this specific thing: there's other things that may also be past their freshness date, we'll discuss those in a separate thread). Warner From owner-freebsd-arm@freebsd.org Wed Jun 13 17:39: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 6A088102126E; Wed, 13 Jun 2018 17:39:11 +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 E0CFE6FB29; Wed, 13 Jun 2018 17:39:10 +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 w5DHd6Ms040723; Wed, 13 Jun 2018 10:39:06 -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 w5DHd6sl040722; Wed, 13 Jun 2018 10:39:06 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201806131739.w5DHd6sl040722@pdx.rh.CN85.dnsmgr.net> Subject: Re: Armeb removal before 12 In-Reply-To: To: Warner Losh Date: Wed, 13 Jun 2018 10:39:06 -0700 (PDT) CC: "freebsd-arm@freebsd.org" , "freebsd-arch@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.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jun 2018 17:39:11 -0000 > I'd like to remove armeb before 12.0. > > It's poorly supported today. > > Nobody has tested the concurrency kit changes on it. And ck is now > mandatory. We don't even know if it works or not. > > Last time we asked, it took quite a while to find users. > > It maxes out at 256MB of RAM. This is barely large enough for FreeBSD to > run in. 64MB is usable for 32 bit archs, I have many VM's running in that configuration, so this item should not be in this list. > > The hardware was last made almost a decade ago. > > It uses non-standard non-mainstream boot loaders (boot technology has moved > on from redboot). > > The cost of doing API sweeps, make universe runs, etc exceeds the benefit > to the project. > > So, given all these factors, it sounds like a good candidate for retirement. > > Therefore, I'd like to remove it on July 15th. > > Comments? (please keep them on topic to this specific thing: there's other > things that may also be past their freshness date, we'll discuss those in a > separate thread). Given all the other valid reasons, I have no objection to removal of armeb. -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-arm@freebsd.org Wed Jun 13 18:09:10 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 694551001F92 for ; Wed, 13 Jun 2018 18:09:10 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x232.google.com (mail-it0-x232.google.com [IPv6:2607:f8b0:4001:c0b::232]) (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 F173D71364 for ; Wed, 13 Jun 2018 18:09:09 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x232.google.com with SMTP id v83-v6so5140927itc.3 for ; Wed, 13 Jun 2018 11:09:09 -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=muxbzQ1ZTPT+EFm/vHUfyGom5Iz8xaAllgxQTKG9ndM=; b=n4p4/c5s7uH2WJHdQOks0NR2h79pMAY7ZwwiRDVqwAhtOigpDv6B/5mudgMwUUsEDL oblBjo8u7jFqpePoEO9YIz89sElsGuO5fJZF7I2651X78+mSZPU+EZVuSL+b7AapAuXe aMXXUdkYz+iu/enLXOUizy5tD+n3OTWa1J7+UEmU3pL5Xb56UgjrHismy37ZtcXfwWXF a/LSO6ibt7e0ds3gAODgUogHSq5mhMWatVcw709moAGqzhoXWCvNLnBRFLxAlbIrJDpi JQ8OzVKX7SqnjgCQXin0co79aPjLnY4huPbBJUNHGrIfssVgdk9S9alDF+K42qy9W2Np zTmQ== 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=muxbzQ1ZTPT+EFm/vHUfyGom5Iz8xaAllgxQTKG9ndM=; b=WJOGYZQST3Mwx8f7GVJaUEo0vOjmOYNy8Gv1lL5xgxsV8UOnXE2sl+OHud7S/o3oVO 8JXivWc3nZTLHXqniVdftzpQ441qWTN074+n1UOdg0x+EKKTekvEXhdZC19Fsr9UaWbF i8Y771TmMIXxfYE4u6S1mH5rTPWbC4WkXxZ5cbxEPjrCNJC2JlWgnGiUR9uAMRE1otjS XSDdAMIjX4g6X4KSw/Ghab6XJSCnyJDzcgfSaeTZcmRma+5C0tNMJf7vCPjC+jMbJzRP c5FdL5dzoz5mpAkYb/uAio9ttvlebwwZP8jSCPAXZZwRCRzQInl+Kfk2foq1Eyy4nakp ISrA== X-Gm-Message-State: APt69E0RcN5v/shubOlN95o7ShTU0lzOLh4OgFnpUN7DEk+38eidHZvi titrZiukqG/vJYQ/zVUuRkzjMHhmDZw93Y91vt33yg== X-Google-Smtp-Source: ADUXVKLe2k3hwZePxE5LHTLGm/Zovta769QqVl6RW0I6/Oeo1XzFWwm28oRwFMeRryvbW11BrmY703nObJShJJkkZPs= X-Received: by 2002:a02:6348:: with SMTP id j69-v6mr838749jac.45.1528913349277; Wed, 13 Jun 2018 11:09:09 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 2002:a4f:d028:0:0:0:0:0 with HTTP; Wed, 13 Jun 2018 11:09:08 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: <201806131739.w5DHd6sl040722@pdx.rh.CN85.dnsmgr.net> References: <201806131739.w5DHd6sl040722@pdx.rh.CN85.dnsmgr.net> From: Warner Losh Date: Wed, 13 Jun 2018 12:09:08 -0600 X-Google-Sender-Auth: a-642fCUulx0DUc4ohG_ifEMUoU Message-ID: Subject: Re: Armeb removal before 12 To: "Rodney W. Grimes" Cc: "freebsd-arm@freebsd.org" , "freebsd-arch@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jun 2018 18:09:10 -0000 On Wed, Jun 13, 2018 at 11:39 AM, Rodney W. Grimes < freebsd-rwg@pdx.rh.cn85.dnsmgr.net> wrote: > > I'd like to remove armeb before 12.0. > > > > It's poorly supported today. > > > > Nobody has tested the concurrency kit changes on it. And ck is now > > mandatory. We don't even know if it works or not. > > > > Last time we asked, it took quite a while to find users. > > > > It maxes out at 256MB of RAM. This is barely large enough for FreeBSD to > > run in. > > 64MB is usable for 32 bit archs, I have many VM's running in > that configuration, so this item should not be in this list. Yes and no. A VM is a different beast to a real box. arm requires more memory in general, and a little more on real machines. You can run it in 128MB and do useful things, but not very many things. One cannot, for example, run a wifi access point on arm in 128MB, at least on this hardware. Adrian's ultra-stripped down stuff might be possible, but nobody has ported it to this hardware despite it being ported to many weird things. Likewise with the ZRouter project. You could run a simple sshd / dns server on it, but there's lots of other alternatives for that which are dirt cheap. One can, with a lot of effort, do 64MB too, but it's more effort than for i386. Even at 64MB on i386, though, the number of things you can do is quite limited. You can't build anything on that machine. DNS + SSH is possible here as well, as long as the zones are too big. So I'll concede the point it's possible, and I'm not looking to make it not be possible. However, we do need to draw the line somewhere, and this is but one factor of many. Were it the only factor here, we wouldn't be contemplating removal. Most people want to do more ambitious things that can be done in 256MB is all I was trying to say. > The hardware was last made almost a decade ago. > > > > It uses non-standard non-mainstream boot loaders (boot technology has > moved > > on from redboot). > > > > The cost of doing API sweeps, make universe runs, etc exceeds the benefit > > to the project. > > > > So, given all these factors, it sounds like a good candidate for > retirement. > > > > Therefore, I'd like to remove it on July 15th. > > > > Comments? (please keep them on topic to this specific thing: there's > other > > things that may also be past their freshness date, we'll discuss those > in a > > separate thread). > > Given all the other valid reasons, I have no objection to removal of armeb. Excellent. Warner From owner-freebsd-arm@freebsd.org Wed Jun 13 18:23: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 2172910037DE; Wed, 13 Jun 2018 18:23:25 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id B0F4A72109; Wed, 13 Jun 2018 18:23:24 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.55.3]) by phk.freebsd.dk (Postfix) with ESMTP id 015AC14885; Wed, 13 Jun 2018 18:23:21 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.15.2/8.15.2) with ESMTPS id w5DINLOv045576 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 13 Jun 2018 18:23:21 GMT (envelope-from phk@critter.freebsd.dk) Received: (from phk@localhost) by critter.freebsd.dk (8.15.2/8.15.2/Submit) id w5DINKhS045575; Wed, 13 Jun 2018 18:23:20 GMT (envelope-from phk) To: Warner Losh cc: "Rodney W. Grimes" , "freebsd-arch@freebsd.org" , "freebsd-arm@freebsd.org" Subject: Re: Armeb removal before 12 In-reply-to: From: "Poul-Henning Kamp" References: <201806131739.w5DHd6sl040722@pdx.rh.CN85.dnsmgr.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <45573.1528914200.1@critter.freebsd.dk> Content-Transfer-Encoding: quoted-printable Date: Wed, 13 Jun 2018 18:23:20 +0000 Message-ID: <45574.1528914200@critter.freebsd.dk> X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jun 2018 18:23:25 -0000 -------- In message , Warner Losh writes: >One can, with a lot of effort, do 64MB too, but it's more effort than for >i386. Even at 64MB on i386, though, the number of things you can do is >quite limited. You can't build anything on that machine. = Well, we *do* have code for something called "swap-devices", and belive it or not, I actually ran make world in 64MB recently - just to see if it would work. Took most of a week. PS: No opinion on the proposed removal. -- = Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe = Never attribute to malice what can adequately be explained by incompetence= . From owner-freebsd-arm@freebsd.org Wed Jun 13 18:23: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 960051003853 for ; Wed, 13 Jun 2018 18:23:33 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x231.google.com (mail-io0-x231.google.com [IPv6:2607:f8b0:4001:c06::231]) (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 27E4972125 for ; Wed, 13 Jun 2018 18:23:33 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x231.google.com with SMTP id e15-v6so4481560iog.1 for ; Wed, 13 Jun 2018 11:23:33 -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=J3zITzvsvjTdAw/8ifyG8amwcSL2ZhA+8cXwOdVrjcM=; b=Glp6DnNZ7no40uvrmpt6EAzon5nO5NSNHQKnC3ZKqq/4GvE0/4MEEMj/7WsXXAUbZ6 1+6y5+2XO5pt6wRK9lU4pHeiIFgzAe2pEbrGHVRBRTsmtWSXcgvwA0nLkfN/EgVIMJri L76nY4svtH/MBH4Lzz2zJJDbkIOB+IWkd3xowqv4O8rotg0K9UEjS+N8dZUFnUhEHS5z C6X4ai/hRA6MpFvKGNZAChQKeY2b9yBirQFybDBOv7x6vnqZWzQsLP8hz1D81RXNi2uP XFgRjZSteW6vokya4b0g5uefO7xzoRPjUykrtb6KMIBkjPahW/+8aOkokcoUTTrD3O4x c/MQ== 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=J3zITzvsvjTdAw/8ifyG8amwcSL2ZhA+8cXwOdVrjcM=; b=d8Mrf4DZHSqvQXA6Kh5+8tZVSLLDqStnb5xT62vGRZcf3JdBDNnZyc30OVJ0KL3pZ5 mL5VylA0HeHhRJcS4SOmGzf3g/6EroWLKq35agV8Jls5xVn2yOWrrfx1Jl0qcXhFgl1z 0NQkGvDAyUrEG4aLSMIYPokbkXDyWBTUHett3ALYbOCOlaP9z25Ac+84cEvo5+8VsfKc fErtVOWxgecwd3Ry+xp5Kk8iYgCp4cG5iCeYNcnGF5g0cZL68XqDPpKCT8udIueAapHg mmoXU7KAED5ySVA1fuVREYKftU2IFot1zj1LdK0RfHrnr2tRy6CZGE7Zh4jd2rvsiumF /K2Q== X-Gm-Message-State: APt69E2DF+iW/XoxfGXnfkxlmPw+ISfAhxPjvgVZyzmzjPdZeuqEzj88 UQ+/JfkcY4NsHbeL5DJvCrQ0h/iE8gmOaqhCelIK2Q== X-Google-Smtp-Source: ADUXVKI5maW7pHL08UCUyjxShuQPLOhPd9rqkHxITOOK3m8Jag+jPznBCJCBGBbEX8ZWXDajDktOdrTAu5W0Vxc8W48= X-Received: by 2002:a6b:284b:: with SMTP id o72-v6mr5749459ioo.168.1528914212496; Wed, 13 Jun 2018 11:23:32 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 2002:a4f:d028:0:0:0:0:0 with HTTP; Wed, 13 Jun 2018 11:23:31 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: References: <201806131739.w5DHd6sl040722@pdx.rh.CN85.dnsmgr.net> From: Warner Losh Date: Wed, 13 Jun 2018 12:23:31 -0600 X-Google-Sender-Auth: vdCgBYSjz-W0iLJh8Yz1Qz218uA Message-ID: Subject: Re: Armeb removal before 12 To: "Rodney W. Grimes" Cc: "freebsd-arm@freebsd.org" , "freebsd-arch@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jun 2018 18:23:33 -0000 On Wed, Jun 13, 2018 at 12:09 PM, Warner Losh wrote: > > > On Wed, Jun 13, 2018 at 11:39 AM, Rodney W. Grimes < > freebsd-rwg@pdx.rh.cn85.dnsmgr.net> wrote: > >> > I'd like to remove armeb before 12.0. >> > >> > It's poorly supported today. >> > >> > Nobody has tested the concurrency kit changes on it. And ck is now >> > mandatory. We don't even know if it works or not. >> > >> > Last time we asked, it took quite a while to find users. >> > >> > It maxes out at 256MB of RAM. This is barely large enough for FreeBSD to >> > run in. >> >> 64MB is usable for 32 bit archs, I have many VM's running in >> that configuration, so this item should not be in this list. > > > Yes and no. A VM is a different beast to a real box. arm requires more > memory in general, and a little more on real machines. > > You can run it in 128MB and do useful things, but not very many things. > One cannot, for example, run a wifi access point on arm in 128MB, at least > on this hardware. Adrian's ultra-stripped down stuff might be possible, but > nobody has ported it to this hardware despite it being ported to many weird > things. Likewise with the ZRouter project. You could run a simple sshd / > dns server on it, but there's lots of other alternatives for that which are > dirt cheap. > > One can, with a lot of effort, do 64MB too, but it's more effort than for > i386. Even at 64MB on i386, though, the number of things you can do is > quite limited. You can't build anything on that machine. DNS + SSH is > possible here as well, as long as the zones are too big. > > So I'll concede the point it's possible, and I'm not looking to make it > not be possible. However, we do need to draw the line somewhere, and this > is but one factor of many. Were it the only factor here, we wouldn't be > contemplating removal. Most people want to do more ambitious things that > can be done in 256MB is all I was trying to say. > Just to followup... On my 11.0 internal DHCP / DNS server (dnsmasq), I have a Allwinner A20 board with 1GB ram that runs between 100-120MB avm 120-1320MB wired with ~750MB free. That's what I've been basing my 256MB to run comfortably statements on. It's possible to do it with less, but it takes a lot of tuning, custom kernels, and legwork to make it happen. This box has only 14 processes, apart from kernel threads and is pretty minimal. Warner From owner-freebsd-arm@freebsd.org Wed Jun 13 18:37: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 AE6731004DD8 for ; Wed, 13 Jun 2018 18:37:19 +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 2D64372F2B for ; Wed, 13 Jun 2018 18:37:18 +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 w5DIbUIE024737 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 13 Jun 2018 11:37:31 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w5DIbUI4024736; Wed, 13 Jun 2018 11:37:30 -0700 (PDT) (envelope-from fbsd) Date: Wed, 13 Jun 2018 11:37:30 -0700 From: bob prohaska To: Warner Losh Cc: "freebsd-arm@freebsd.org" , bob prohaska Subject: Re: GPT vs MBR for swap devices Message-ID: <20180613183730.GA24526@www.zefox.net> References: <20180613154826.GA24146@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.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jun 2018 18:37:19 -0000 On Wed, Jun 13, 2018 at 10:09:20AM -0600, Warner Losh wrote: > The write speed > is kinda crappy (maybe 50-60MB/s when streaming a file to them, and > 20-3MB/s in a mixed workload)..... That does not seem horrible compared to a mechanical disk with its seek delays. A brief web search suggests 4k random write speeds of 1-3 MB/s for mechanical disks more modern than the one I'm using. Thus far experiements have included swap on microSD (works), swap on mechanical disk (works), swap on USB flash (causes OOM kills even with < 20% swap utilization) and mixed USB flash, microSD flash and/or mechanical swap (causes OOM kills). It seems odd that adding USB flash swap to either microSD or USB mechanical swap seems to make mischief. If a device is slow, I thought the swapper would dis-favor or ignore it. Some of the combinations trigger the warning: warning: total configured swap (1048576 pages) exceeds maximum recommended amount (918256 pages). warning: increase kern.maxswzone or reduce amount of swap. which I've ignored, thinking the system will ignore excess swap space. Is this mistaken? It's pretty clear the system does not need more than about 1.5 GB of swap. Available swap devices are presently sized like so: 3 GB mechanical disk 2 GB microSD flash 1 GB microSD flash 1 GB USB flash The original plan was to use the two 1 GB flash partitions in the hope they'd interleave, but that does not work at all. The microSD flash swap seems to work fine. I was wondering if the USB mechanical swap might point to trouble in the USB side of things, but it does not. Thanks for reading, bob prohaska From owner-freebsd-arm@freebsd.org Wed Jun 13 18:45: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 3DD4A10058B6 for ; Wed, 13 Jun 2018 18:45:05 +0000 (UTC) (envelope-from 4250.10.freebsd-arm=freebsd.org@email-od.com) Received: from s1-b0c6.socketlabs.email-od.com (s1-b0c6.socketlabs.email-od.com [142.0.176.198]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D78FA7343F for ; Wed, 13 Jun 2018 18:45:04 +0000 (UTC) (envelope-from 4250.10.freebsd-arm=freebsd.org@email-od.com) DKIM-Signature: v=1; a=rsa-sha256; d=email-od.com;i=@email-od.com;s=dkim; c=relaxed/relaxed; q=dns/txt; t=1528915505; x=1531507505; h=content-transfer-encoding:content-type:mime-version:references:in-reply-to:message-id:subject:cc:to:from:date:x-thread-info; bh=bTKTdB+lvuQsecWWEU2/0kpGUXHMUgMWUmkCKeT8w3I=; b=RWRx1gpf0Mmbtb+VIDxRQmm+Di8rQ08U0BmTC1Ml/M+9ZfECjuQSkN5Sdl+GX/wMR5q2/R+AfbB9zpIanjpQjr+UYltJyZCcWKEXqyJFUpCb0qCycnINkvC7vqRXyz418lvnZBedTPHWj+HgvRjUN/Z1dyf+UA9dwuPwqVL2D80= X-Thread-Info: NDI1MC4xMi4xOGYwMDAwMDAwOTRkMGUuZnJlZWJzZC1hcm09ZnJlZWJzZC5vcmc= Received: from r5.us-west-2a.aws.in.socketlabs.com (r5.us-west-2a.aws.in.socketlabs.com [52.39.5.146]) by mxsg2.email-od.com with ESMTP(version=Tls12 cipher=Aes256 bits=256); Wed, 13 Jun 2018 14:44:59 -0400 Received: from smtp.lan.sohara.org (EMTPY [89.127.62.20]) by r5.us-west-2a.aws.in.socketlabs.com with ESMTP(version=Tls12 cipher=Aes256 bits=256); Wed, 13 Jun 2018 14:44:57 -0400 Received: from [192.168.63.1] (helo=steve.lan.sohara.org) by smtp.lan.sohara.org with smtp (Exim 4.90_1 (FreeBSD)) (envelope-from ) id 1fTAlK-000Ded-Ar; Wed, 13 Jun 2018 18:44:54 +0000 Date: Wed, 13 Jun 2018 19:44:54 +0100 From: Steve O'Hara-Smith To: "Poul-Henning Kamp" Cc: Warner Losh , "freebsd-arch@freebsd.org" , "freebsd-arm@freebsd.org" , "Rodney W. Grimes" Subject: Re: Armeb removal before 12 Message-Id: <20180613194454.534e9157129d3988c1683972@sohara.org> In-Reply-To: <45574.1528914200@critter.freebsd.dk> References: <201806131739.w5DHd6sl040722@pdx.rh.CN85.dnsmgr.net> <45574.1528914200@critter.freebsd.dk> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; amd64-portbld-freebsd11.1) X-Clacks-Overhead: "GNU Terry Pratchett" Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jun 2018 18:45:05 -0000 On Wed, 13 Jun 2018 18:23:20 +0000 "Poul-Henning Kamp" wrote: > Well, we *do* have code for something called "swap-devices", and > belive it or not, I actually ran make world in 64MB recently - just > to see if it would work. Took most of a week. If memory serves correctly buildworld took a day or two back when 64MB was a fairly generous allocation of memory and there was a lot less world. -- Steve O'Hara-Smith From owner-freebsd-arm@freebsd.org Wed Jun 13 19:13: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 5F81F1008AF1 for ; Wed, 13 Jun 2018 19:13:08 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x233.google.com (mail-it0-x233.google.com [IPv6:2607:f8b0:4001:c0b::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E1BD0752A6 for ; Wed, 13 Jun 2018 19:13:07 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x233.google.com with SMTP id l6-v6so5421340iti.2 for ; Wed, 13 Jun 2018 12:13:07 -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=frAJ/6cptoxcZM8cDzaNIoq2vg9dt1bEuUe62c6bcBM=; b=RTul18l2CaaNgyciBzunQFfOF4/Ycy+Ls7sV0kKAO23VbJz6gaEGUWFVNhyaIFjlmI xvUlTFmEX05tZz2bdHnpIZko/lgqy3aDFkbW5KUU8Yh/UX6WBIrCP3MzLQgDPJomOjL2 L/gN+4X05y0igyOPKLhcOhvPgVjn+3Ql5SZgg5r2iQj/X430zGcoB+plHeL4XtjZwzqh TWZdFxlzEQJhgDM8L+Y8kj4O94UTQd3tqFKLTPbFNU/yKMQdLOoNT58TLdR4/FAfG135 /x+g/upkHqhNc1gGGFzAMUJXKda+HoYjYlH7tFEO3Yn2t+DIacafvt3y49ipKEFJlPxA kQAQ== 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=frAJ/6cptoxcZM8cDzaNIoq2vg9dt1bEuUe62c6bcBM=; b=brAYaO1MXF4gDCsnjelpBtW7esKRjZ89XKH4J+3NHsOSBsQz5XPr09ja31VhFBIkJ5 3G43fpXZB0r8k5TTPMkb2H54auZaGraRs/6a3d7HB2GP9gDU5IbGb3N3hXMU5pXr2nOW OJGJo9DVU5ZwaHrRAMGnb7JN9umQ5XV7B4EIo9YEbnxESjvnwncFoD9E4/pJY7SDNzqJ Tld6idnHIdUwhW3Vhd4t6UI69cSz8npzkMnmxpaAqSJwkJ1ickkGLV5GL7Tw11cjxSzN WgMLbMWDLeJOEpmq2U6+tI4aHpmYnb7egKBYQWsZIChQHJnf+7u8B2QSCVrxTlyDrloE qx8Q== X-Gm-Message-State: APt69E1g4tXH8tte/ZGn21KgjUtakRiJjIxkGOjTxTlBQX7fsxF9wCKz XsFrvJVf6f9cKyiO3PLZp+3yOP70NuYDyl8e5j4P1g== X-Google-Smtp-Source: ADUXVKKTb665ZRjyxiSMqWtk6l3m5dheWaIY/it35QAmMiXg+YasZl8e+HmjFaRAECGi8i3gTcAZ1Q/ny9d31BbBhZs= X-Received: by 2002:a24:7c8d:: with SMTP id a135-v6mr5811319itd.73.1528917187113; Wed, 13 Jun 2018 12:13:07 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 2002:a4f:d028:0:0:0:0:0 with HTTP; Wed, 13 Jun 2018 12:13:06 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: <20180613194454.534e9157129d3988c1683972@sohara.org> References: <201806131739.w5DHd6sl040722@pdx.rh.CN85.dnsmgr.net> <45574.1528914200@critter.freebsd.dk> <20180613194454.534e9157129d3988c1683972@sohara.org> From: Warner Losh Date: Wed, 13 Jun 2018 13:13:06 -0600 X-Google-Sender-Auth: CiRENNPEJPCRPURN_i_a8mPFmeY Message-ID: Subject: Re: Armeb removal before 12 To: "Steve O'Hara-Smith" Cc: Poul-Henning Kamp , "freebsd-arch@freebsd.org" , "freebsd-arm@freebsd.org" , "Rodney W. Grimes" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jun 2018 19:13:08 -0000 On Wed, Jun 13, 2018 at 12:44 PM, Steve O'Hara-Smith wrote: > On Wed, 13 Jun 2018 18:23:20 +0000 > "Poul-Henning Kamp" wrote: > > > Well, we *do* have code for something called "swap-devices", and > > belive it or not, I actually ran make world in 64MB recently - just > > to see if it would work. Took most of a week. > > If memory serves correctly buildworld took a day or two back when > 64MB was a fairly generous allocation of memory and there was a lot less > world. > In the FreeBSD 1.x time frame, my 486DX2-66 with 32MB of RAM built world over night (well, late afternoon start the build, it was done by breakfast the next day so < 15 hours). Warner From owner-freebsd-arm@freebsd.org Wed Jun 13 19:39: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 0F75E100B2A6; Wed, 13 Jun 2018 19:39:11 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id 93AB9765DA; Wed, 13 Jun 2018 19:39:10 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.55.3]) by phk.freebsd.dk (Postfix) with ESMTP id A3F611487A; Wed, 13 Jun 2018 19:39:09 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.15.2/8.15.2) with ESMTPS id w5DJd8mP045780 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 13 Jun 2018 19:39:08 GMT (envelope-from phk@critter.freebsd.dk) Received: (from phk@localhost) by critter.freebsd.dk (8.15.2/8.15.2/Submit) id w5DJd8K4045779; Wed, 13 Jun 2018 19:39:08 GMT (envelope-from phk) To: "Steve O'Hara-Smith" cc: "freebsd-arch@freebsd.org" , "freebsd-arm@freebsd.org" , "Rodney W. Grimes" Subject: Re: Armeb removal before 12 In-reply-to: <20180613194454.534e9157129d3988c1683972@sohara.org> From: "Poul-Henning Kamp" References: <201806131739.w5DHd6sl040722@pdx.rh.CN85.dnsmgr.net> <45574.1528914200@critter.freebsd.dk> <20180613194454.534e9157129d3988c1683972@sohara.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <45777.1528918748.1@critter.freebsd.dk> Content-Transfer-Encoding: quoted-printable Date: Wed, 13 Jun 2018 19:39:08 +0000 Message-ID: <45778.1528918748@critter.freebsd.dk> X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jun 2018 19:39:11 -0000 -------- In message <20180613194454.534e9157129d3988c1683972@sohara.org>, Steve O'H= ara-Smith writes: >On Wed, 13 Jun 2018 18:23:20 +0000 >"Poul-Henning Kamp" wrote: > >> Well, we *do* have code for something called "swap-devices", and >> belive it or not, I actually ran make world in 64MB recently - just >> to see if it would work. Took most of a week. > > If memory serves correctly buildworld took a day or two back when >64MB was a fairly generous allocation of memory and there was a lot less >world. Most of the cpu-time in buildworld is taken up compiling LLVM. -- = Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe = Never attribute to malice what can adequately be explained by incompetence= . From owner-freebsd-arm@freebsd.org Wed Jun 13 21:41: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 AC6A9101A522 for ; Wed, 13 Jun 2018 21:41:48 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic301-4.consmr.mail.bf2.yahoo.com (sonic301-4.consmr.mail.bf2.yahoo.com [74.6.129.43]) (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 5444A7DF8F for ; Wed, 13 Jun 2018 21:41:48 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: Rju9YWoVM1nQRHy1ngIYq_cbS9DdO17ZcA5c1vK0d4EJucApNWTMz0DG7fJj9c7 h.pLAmoyYXbBp8ixzgycvGyxjht0U9t087.McajCJVWv6OK.I6VYMzDmi_W5_tsHqxIiBEjhPxtA 1poFfjGLEFEfbuZ6NMJ57iYWMvMnEN2EV11CkI8Fm7d399v9W9jjr.5IuniNO2_iX9yPr0zg6y5i k92sRZZtUydWPE27RvsDLteNMHBFnovGePV06Gm6IRHuQsvvac6s_D4uh2cmAuDrcUwftPm60QUD TS9KQiitVGDkKGIVQkSYFbqMIYp2asSHswBgdFy6xTtVEAI77vIiOJFwlpHS2m5JAYRJz1.K2I1g OF8fEDNxbHBSYXHKEnk5DepsWMyOEGbmyr8s6KUldO6EfYv_hNBR5vVXuANyyd3ChGeJIlttNOht urjzhAMOrI6ZniF4q_iC5ccJ7vrVDcLxshhJfI2WXfSY1mOP2Xch8KdYK6hSj7ApNvhgTrlOYVNQ WkQS16OtNEbzZQthkzYtkUAZ1FfLrceWQmlAMfoaYWH5kZt7hD3_gy2FfH0DVGkGFt6CCPaJQyAy IKhEPKq4EUHSimVZbOWreYBvOyo7CGHjeR0ykDybCL4snfPzX4YngLCPtMHIsxVdCcUEvvcHXPsF 0d8PlaPB_kg.Pq7iPAD.9Ydsvff4zWgDIIZrsMfO2n6LV9jJoMsZhlc1HX2e4zGr7rf2sTBOBdK6 IKvO.lnSj9mHag.NW2_7Gn_l8fTIU915nHqWfoNnKf.o_ypv6NgmeO4V3NJ8EJi1ToMh0ZaC6ABd vwyFFNc2PNRo3bdQuzYbNljuRnkq_AE3GYb5jXnwWw6SytYdJe7W41RLcV2NMXpnZbn8cGjtKnEG 6a3iXe60jVipSVu140W8Am1qJ4TtalKNFspgQPK.3yoNSe9XnQGOS44g.02NryhIqQHN0YZk3FPD 8aJ1DAuJ7WuDHLhDnk4qEm_2ap4TiRKJIaEQ- Received: from sonic.gate.mail.ne1.yahoo.com by sonic301.consmr.mail.bf2.yahoo.com with HTTP; Wed, 13 Jun 2018 21:41:42 +0000 Received: from ip70-189-131-151.lv.lv.cox.net (EHLO [192.168.0.109]) ([70.189.131.151]) by smtp419.mail.bf1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 9ba3756b48b75b5f6df2ed44313c0ea4; Wed, 13 Jun 2018 21:41:37 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\)) Subject: Re: GPT vs MBR for swap devices From: Mark Millard In-Reply-To: <20180613183730.GA24526@www.zefox.net> Date: Wed, 13 Jun 2018 14:41:35 -0700 Cc: Warner Losh , "freebsd-arm@freebsd.org" Content-Transfer-Encoding: quoted-printable Message-Id: References: <20180613154826.GA24146@www.zefox.net> <20180613183730.GA24526@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.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jun 2018 21:41:48 -0000 On 2018-Jun-13, at 11:37 AM, bob prohaska wrote: . . . > Some of the combinations trigger the warning: >=20 > warning: total configured swap (1048576 pages) exceeds maximum = recommended amount (918256 pages). > warning: increase kern.maxswzone or reduce amount of swap. As I remember, the "increase kern.maxswzone" only applies if one has previously decreased it: the modern default is the maximum recommended as I remember (allowing for for half the theoretical maximum swap). If I remember right the code overrode attempts to set more than the default, only setting less (when requested). (I've not re-validated this claim via a code inspection in some time.) Quoting "man 8 loader" and its kern.maxswzone material, Note that swap metadata can be fragmented, which means = that the system can run out of space before it reaches the theoretical limit. Therefore, care should be taken to = not configure more swap than approximately half of the theoretical maximum. So it will potentially have more fragmentation problems fitting the=20 extra metadata that is involved in the same amount of total RAM. I will note that aarch64 and armv7 for the same amount of RAM use very different "maximum recommended amount"s. (Compare an armv7 rpi2 to an aarch64 rpi3 by adding enough swap to get the notice, for example. The rpi3 allows far more swap space as I remember.) This variability is not obvious from the man page's material. > which I've ignored, thinking the system will ignore excess swap space. Again: It will potentially have more fragmentation problems fitting the=20= extra metadata that is involved in the same amount of total RAM. > Is=20 > this mistaken? I expect so because of the metadata issue. (But some later notes below go in another direction, making this possibly not a unique source of overall behavior differences.) > It's pretty clear the system does not need more than about=20 > 1.5 GB of swap. Available swap devices are presently sized like so: I'd recommend not using a whole lot more than you need, at least small enough (total) for it to not report the warning. One thing I wish FreeBSD had was an (approximate) "Maximum Observed Swap Used" that could be queried or that some built-in tool would monitor and report. At times I've made variants of top that displayed such based on the figures it uses for its swap line. I've made judgements about -jN choices and swaps space sizes based on what I've observed for various contexts that I use/do repeatedly and for "large" things that I do rarely but that can fail in my normal configuration. > 3 GB mechanical disk > 2 GB microSD flash > 1 GB microSD flash > 1 GB USB flash To make your experiments comparable, I'd recommend the same total swap be used across the alternatives being tested and compared. This may be biased to using a smaller swap space that all the contexts can support. Going in another direction: The timing variations between the types of media may mean that the mix of what is happening at the same time changes for -j4 from one context to the next. This could get other issues involved in why there are variations in the overall behavior. Side note: I've used eMMC on an adapter in some microSD slots. I had to "adjust" the Pine64+ 2GB case for the adapter that I used to reach so such is not always an automatically-available option. > The original plan was to use the two 1 GB flash partitions in the hope > they'd interleave, but that does not work at all. The microSD flash > swap seems to work fine. I was wondering if the USB mechanical swap > might point to trouble in the USB side of things, but it does not.=20 . . . Just for completeness for other readers (you may well be using swap partitions) . . . I also recommend swap partitions instead of swap files. See, for example: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D206048 (OOM process kills were not one of the issues for bugzilla 206048. But there were other problems for swap files.) =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-arm@freebsd.org Wed Jun 13 22:28: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 25635101E615 for ; Wed, 13 Jun 2018 22:28:12 +0000 (UTC) (envelope-from yamori813@yahoo.co.jp) Received: from nh603-vm11.bullet.mail.ssk.yahoo.co.jp (nh603-vm11.bullet.mail.ssk.yahoo.co.jp [182.22.90.52]) by mx1.freebsd.org (Postfix) with SMTP id 51DF27FC0D for ; Wed, 13 Jun 2018 22:28:10 +0000 (UTC) (envelope-from yamori813@yahoo.co.jp) Received: from [182.22.66.104] by nh603.bullet.mail.ssk.yahoo.co.jp with NNFMP; 13 Jun 2018 22:25:44 -0000 Received: from [182.22.91.128] by t602.bullet.mail.ssk.yahoo.co.jp with NNFMP; 13 Jun 2018 22:25:44 -0000 Received: from [127.0.0.1] by omp601.mail.ssk.yahoo.co.jp with NNFMP; 13 Jun 2018 22:25:44 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 683572.80780.bm@omp601.mail.ssk.yahoo.co.jp Received: (qmail 52050 invoked by uid 60001); 13 Jun 2018 22:25:44 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.co.jp; s=yj20110701; t=1528928744; bh=B/HLa3bOQXNS53diXkEV6qovaEnZdSWAYQi3feQFsjY=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:X-YMail-JAS:References:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=bg4y455C+Gc8LwuvBO5lPfNrHf9IkeDlB4i80a73a5QKxB7D7Z1hCAzrZ+s/qU7fUruKx+WFR1EjVRSWtdkZOQSMJLgHfAerAMllc4o8dsORDYb+M+T2KlP4T5Dvzk/CaojQxzMPfSSIoETNUUiVnzyQD6w1Ng7ceh/LDdyJt2U= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=yj20110701; d=yahoo.co.jp; h=Message-ID:X-YMail-OSG:Received:X-Mailer:X-YMail-JAS:References:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=JKJIrJb0unvtUCLYRjA6nGG7/H0AMiY4j4wdoGnjBa/PmnZTyDJZzbJrajDJgCKL8bLuEqn7jJ9njgv33Bg3NvQws+czaKNCggzH/Lpj6ooIaUXCHNyEGN40rLTKUh4UFMZTRzV9XAxHvKSyZtTS/YCd8d8N27GwxwcqphC9nBE=; Message-ID: <540973.43848.qm@web101701.mail.ssk.yahoo.co.jp> X-YMail-OSG: 3K28KpsVM1l03toHXstNalsxsnupG4PqLvDzE5CxithSyW4F5pQdsSdroBstCjO6LRUBmka.RaAEbnElen1fjKMWQB3Hh0Zo4OlkL5JJ8jfpQfPnIiJkfoQoToh5Mw6u_gH7NsoEsg2VZxaJ91xahaNvjV1qd2hI4hvt0hcjEILKB21duaoPi0vMhYGBAkln4.AEHRD6vhHrWtHZcnp8huE0TzjklegM1Jt3GqsPScRtUiPXLJTJYRJnMoihp.Ra5Fl6BMoOHUlvtq_xmhKLi3pDK_L1jLehAoGdIIn3zmEF8ddrQaWiuSDJ.NnMpAGdZwWOZmNK50ju6elSB2Fva42Wc5erj9rHo6FfDirp_27R1H8mEXE7hcnQ2EYxLcDgnDtIYrXGb_dddKaWgQTUxNUmX2sOVwGzVICuNDwabKOXkDsCo1vC2tuaL225QzG3rsxfNO2VQbxQa4j_poyetwZA2c5V1EYB8EdRJ21Lzif0uRh7TCP.RXgLzerwygtzNrXFMBpotnUrWdebri2qiQIJVVc0xcuwIEtpwelaGnpNn7v9QHmIusHncnwaJrKiadNM1J5XBnQxORdkOtM5zQngQ_wbvRp0knV_VrJtvLYmshUpbfPyJBDPuxx.dKRK Received: from [203.165.91.75] by web101701.mail.ssk.yahoo.co.jp via HTTP; Thu, 14 Jun 2018 07:25:43 JST X-Mailer: YahooMailWebService/0.8.111_74 X-YMail-JAS: Pq.l_6YVM1k1eiLk1cFy3OP3RmXiLFDgjBgo3t0jMUlVa0ZCOa9zOIBzvxDbF9WepNJfLucits4H3Qj3MFOk9gYhHJXz.nuklYnl18yBXCdtJTWhgPJMBeg6lb1D3LkutBBl References: Date: Thu, 14 Jun 2018 07:25:43 +0900 (JST) From: Mori Hiroki Reply-To: Mori Hiroki Subject: Re: Armeb removal before 12 To: Warner Losh , "freebsd-arm@freebsd.org" , "freebsd-arch@freebsd.org" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jun 2018 22:28:12 -0000 Hi.=0A=0A=0A----- Original Message -----=0A> From: Warner Losh =0A> To: "freebsd-arm@freebsd.org" ; "freebsd-= arch@freebsd.org" =0A> Cc: =0A> Date: 2018/6/14, Thu 01:5= 5=0A> Subject: Armeb removal before 12=0A> =0A> I'd like to remove armeb be= fore 12.0.=0A> =0A> It's poorly supported today.=0A> =0A> Nobody has tested= the concurrency kit changes on it. And ck is now=0A> mandatory. We don't e= ven know if it works or not.=0A> =0A> Last time we asked, it took quite a w= hile to find users.=0A> =0A> It maxes out at 256MB of RAM. This is barely l= arge enough for FreeBSD to=0A> run in.=0A=0Asys/arm/ralink target is only 1= 6M of RAM. I use bridge on this target=0Awork fine.=0A=0AI have FWIXP422BB = target(Planex BRC-14VG) with 32M of RAM. I never build=0AFreeBSD for this= =A0target.=0A=0AI want build for=A0FWIXP422BB but clang cross build is very= slow. It take=0A7 hour on my machine.=0A=0A> =0A> The hardware was last ma= de almost a decade ago.=0A> =0A> It uses non-standard non-mainstream boot l= oaders (boot technology has moved=0A> on from redboot).=0A> =0A> The cost o= f doing API sweeps, make universe runs, etc exceeds the benefit=0A> to the = project.=0A> =0A> So, given all these factors, it sounds like a good candid= ate for retirement.=0A> =0A> Therefore, I'd like to remove it on July 15th.= =0A> =0A> Comments? (please keep=A0 them on topic to this specific thing: t= here's other=0A> things that may also be past their freshness date, we'll d= iscuss those in a=0A> separate thread).=0A> =0A> Warner=0A> _______________= ________________________________=0A> freebsd-arm@freebsd.org mailing list= =0A> https://lists.freebsd.org/mailman/listinfo/freebsd-arm=0A> To unsubscr= ibe, send any mail to "freebsd-arm-unsubscribe@freebsd.org"=0A> From owner-freebsd-arm@freebsd.org Wed Jun 13 22:51: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 DF9C5102066E; Wed, 13 Jun 2018 22:51:48 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (muon.bluestop.org [96.73.9.1]) (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 7BBB3809A9; Wed, 13 Jun 2018 22:51:48 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (localhost [127.0.0.1]) by muon.bluestop.org (Postfix) with ESMTP id 5BC1D4CBA6; Wed, 13 Jun 2018 16:51:16 -0600 (MDT) Received: from muon.bluestop.org ([127.0.0.1]) by muon.bluestop.org (muon.bluestop.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id eWA7X9nxdhDf; Wed, 13 Jun 2018 16:51:15 -0600 (MDT) Received: from [10.0.10.173] (gw.bluestop.org [96.73.9.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by muon.bluestop.org (Postfix) with ESMTPSA; Wed, 13 Jun 2018 16:51:15 -0600 (MDT) Subject: Re: ARMv8 development board with GICv3 To: "Rodney W. Grimes" , Alexandru Elisei Cc: freebsd-arm@freebsd.org, freebsd-virtualization@freebsd.org References: <201806130737.w5D7bHxX038233@pdx.rh.CN85.dnsmgr.net> From: Rebecca Cran Message-ID: Date: Wed, 13 Jun 2018 16:51:03 -0600 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <201806130737.w5D7bHxX038233@pdx.rh.CN85.dnsmgr.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jun 2018 22:51:49 -0000 On 6/13/2018 1:37 AM, Rodney W. Grimes wrote: > > I believe the Chromebook SNOW meets the criteria, not exactly a > "board" but I have one on loan from Michael Dexter that was originally > purhased to support ARMv8 bhyve work. > > Not sure that it has a version 3 GIC either. Actually I am thinking > that you have to do the software GIC on this platform. On a similar note, the SoftIron OverDrive 1000 (https://softiron.com/development-tools/overdrive-1000/) might be suitable? It uses an A57 in an Opteron A1100 SoC. At $600 it's relatively affordable for a complete system. -- Rebecca Cran From owner-freebsd-arm@freebsd.org Wed Jun 13 22:57:04 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 D78621020E13 for ; Wed, 13 Jun 2018 22:57:03 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x22c.google.com (mail-io0-x22c.google.com [IPv6:2607:f8b0:4001:c06::22c]) (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 6D7BD80C76 for ; Wed, 13 Jun 2018 22:57:03 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x22c.google.com with SMTP id l19-v6so5222158ioj.5 for ; Wed, 13 Jun 2018 15:57:03 -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=ZAg9QIw4NwwqcOk7QTThnQrCXaQaZWqs/xTOjF2sOUI=; b=lhK7QvGc5KFURML9LqyXEBNYbyKygHOjrKj7ph0uAB/PH2HNHN/CAxS4rCqQELYEUq 7kiQYoczavBGZ5GjAJOyMrzmmLmGWRDTpqTGDsxp2dpDzGDhd58fg8Hk8aAcfIFTdx8M jkHSJmoHVfRLcLWlYCckWQSBm2SsLch8789Wztz4VwLpgrQn3xT+TdL4fTU1hur0Jcpe sgp49A2v8aUrR4WO+Zbd5yI7ZPZSuNwZ8FDGve3XG1+zP7aIK3YsKK5C6judxTvOM/hL 3wTZ65nDcRvRAKkSi8uVyeIsq5q7genOMnJZ4s0cetWC9rpMyoYQ/JmiJbE/ziBKu8E/ LETw== 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=ZAg9QIw4NwwqcOk7QTThnQrCXaQaZWqs/xTOjF2sOUI=; b=cbCgsvxFDvhTFJwRbKL+xjnkKFKNN7X+Xl2/C7g+VfdrCTJ9d9LpNVUbGTy9whd7r9 YFWU/gJg+UflHvLAF1suN7FBfuaRxD9wCtSlWZoz0V2ZUdq1qOozezKKak2Ba7VWWIxw ribJ3FN5jZ2it5LrualxEVx2cBaJIJapXthZSnSmFVlnKA8hL5t/LNjrm5PEFAjwpMCr 5FsVG4oTdEMk0iHaew+QEPddBvI1JlaGuHSCY0J36vRP1UkHEymPkPNhb/AKWeeiy8nU GW8p6BuFp5xzFtqmj/RikKc7Zm8iQSm0vHNf3syari3L25BXkZanCSz5euOXZhnO2WMW 2N/w== X-Gm-Message-State: APt69E090JyvdTfqWiaSiDwI/x+fk2nAHFwcJR9ouAQSUXS0HV1t5jvy jUQEYMEfmRIpaur0TrzxuqmTAimb8EM1XCQj+/5b2A== X-Google-Smtp-Source: ADUXVKIkWRNWg+5K/DYIhiDL2FwS94AUaniTImnF3zC7u/lqZ8C4D7eJ56pWcTH0wiuxjHX1Dda/nUsKPOq5VmJpCU8= X-Received: by 2002:a6b:d40c:: with SMTP id l12-v6mr124789iog.37.1528930622665; Wed, 13 Jun 2018 15:57:02 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 2002:a4f:d028:0:0:0:0:0 with HTTP; Wed, 13 Jun 2018 15:57:02 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: <540973.43848.qm@web101701.mail.ssk.yahoo.co.jp> References: <540973.43848.qm@web101701.mail.ssk.yahoo.co.jp> From: Warner Losh Date: Wed, 13 Jun 2018 16:57:02 -0600 X-Google-Sender-Auth: 5HUYRbmaDjcSxXO0TItfn25B4fs Message-ID: Subject: Re: Armeb removal before 12 To: Mori Hiroki Cc: "freebsd-arm@freebsd.org" , "freebsd-arch@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jun 2018 22:57:04 -0000 On Wed, Jun 13, 2018 at 4:25 PM, Mori Hiroki wrote: > Hi. > > > ----- Original Message ----- > > From: Warner Losh > > To: "freebsd-arm@freebsd.org" ; " > freebsd-arch@freebsd.org" > > Cc: > > Date: 2018/6/14, Thu 01:55 > > Subject: Armeb removal before 12 > > > > I'd like to remove armeb before 12.0. > > > > It's poorly supported today. > > > > Nobody has tested the concurrency kit changes on it. And ck is now > > mandatory. We don't even know if it works or not. > > > > Last time we asked, it took quite a while to find users. > > > > It maxes out at 256MB of RAM. This is barely large enough for FreeBSD to > > run in. > > sys/arm/ralink target is only 16M of RAM. I use bridge on this target > work fine. > Even with current? It seems to have grown a lot. Even FreeBSD 11 on my atmel boards, the 32MB ones can't really do much of anything (though a custom /etc/rc.d might be usable). The 64MB ones I have troubles logging into without disabling a ton of stuff. And FreeBSD-current is even larger. Are you using a custom rc.d in this setup? > I have FWIXP422BB target(Planex BRC-14VG) with 32M of RAM. I never build > FreeBSD for this target. > > I want build for FWIXP422BB but clang cross build is very slow. It take > 7 hour on my machine. I'm sorry to hear that. Even on my fast machines, it takes long time. Warner > > > > > The hardware was last made almost a decade ago. > > > > It uses non-standard non-mainstream boot loaders (boot technology has > moved > > on from redboot). > > > > The cost of doing API sweeps, make universe runs, etc exceeds the benefit > > to the project. > > > > So, given all these factors, it sounds like a good candidate for > retirement. > > > > Therefore, I'd like to remove it on July 15th. > > > > Comments? (please keep them on topic to this specific thing: there's > other > > things that may also be past their freshness date, we'll discuss those > in a > > separate thread). > > > > Warner > > _______________________________________________ > > 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 Wed Jun 13 23:13:38 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 BDC07102247D for ; Wed, 13 Jun 2018 23:13:38 +0000 (UTC) (envelope-from yamori813@yahoo.co.jp) Received: from nh503-vm12.bullet.mail.kks.yahoo.co.jp (nh503-vm12.bullet.mail.kks.yahoo.co.jp [183.79.56.198]) by mx1.freebsd.org (Postfix) with SMTP id 46ED9817C1 for ; Wed, 13 Jun 2018 23:13:37 +0000 (UTC) (envelope-from yamori813@yahoo.co.jp) Received: from [183.79.100.141] by nh503.bullet.mail.kks.yahoo.co.jp with NNFMP; 13 Jun 2018 23:10:14 -0000 Received: from [183.79.100.137] by t504.bullet.mail.kks.yahoo.co.jp with NNFMP; 13 Jun 2018 23:10:14 -0000 Received: from [127.0.0.1] by omp506.mail.kks.yahoo.co.jp with NNFMP; 13 Jun 2018 23:10:14 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 103228.76270.bm@omp506.mail.kks.yahoo.co.jp Received: (qmail 57827 invoked by uid 60001); 13 Jun 2018 23:10:13 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.co.jp; s=yj20110701; t=1528931413; bh=h1nmF6+dSMhXdTAUALJnMxxrecPJ3Be4OZQPtiaXxnA=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:X-YMail-JAS:References:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=FL+U1vYmVGgUtLRLum+LOnStn9QxeDdCv0ykPcd4cBm+EiBMYBdnhgTLU2o2gIPDNZdcycMcz+qHMQFtW5RBYMADeOWUMn3ONHS9WOFkwvBqw+3VF2ow71Cpi+hXufXYd6DbPuugBHdJpUMMf72ZYjgmj0cwqnG0eEg1lfJlB6M= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=yj20110701; d=yahoo.co.jp; h=Message-ID:X-YMail-OSG:Received:X-Mailer:X-YMail-JAS:References:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=LJgvbbK1g/LnSAKlrZ/Cx4gu9hmz0S0+IOywH6ov0iWZHzhomjQYQtGTFypKQZFoydrExxNPMWufC1esTmIH0ASB8UigFYf81KL1BAZ9Wipm1h6j2g5wcqANF27kBJxqWd+4mrQp96wmR/Mp8ehg+Bc3k5XPoYubuAiIgcvyM8k=; Message-ID: <861063.32056.qm@web101713.mail.ssk.yahoo.co.jp> X-YMail-OSG: 8Swe6woVM1lkyhri6SEJGpR0pOXoYO88EpoJExZ2vqiQuy48sc_9ZU4Ywf329Uzib26WLBzyl.hnm5uLnFRV2vHj0cc3qT0Ry99s2R_5okEkQytftDtiCLt2_wevelYtiCOEb1kj1Syu.eWAA0LfxMCenyisAMlQOPnOZvjQKLodpLQdQx7dy0dgWUO1663PImIcNU22LUizeuQPCk4UMmvYGxBp9Nfc.iXqTQuSYepLptTJUvhhd4s6fA0_Fc4B2yOVneXW.Ij0i8Vs_t8e_gPyxMQ8ER7lxi0ZvSJQMO2a3zAkx5ponsOXh9eRI.ph2kAQRUgFWuP6BRX3zjbNl3xdpF0ogjIJVTNcQZkdmm.1zVTqW9XToqObKKbtdRAWg.XwsmOTBGUhRUvq3eIN.5reYHgX0m4tAwC7Z9R2tT_sBkEYSfmD.OZYYqGgzydQqcKa.WNwytnL5qgzOi71ojOgHZ5kcpOqIl2NnULg9t.iEbtnlI4vFN_QHfKCrdkzvbKep4pP.Wbk3WPDT2ysG1wNQjH0UZbgChI7cb39VkWuz7qWgzfx0IcB8.Vt65Ru94KVF5zn9ZDIIhkNR.8tHkkDvwoYdTn48l6da5XU2HNkMloupzs1z.co9o1VOZ3C Received: from [203.165.91.75] by web101713.mail.ssk.yahoo.co.jp via HTTP; Thu, 14 Jun 2018 08:10:12 JST X-Mailer: YahooMailWebService/0.8.111_74 X-YMail-JAS: lCRctvMVM1lAWZKcdIKBOVMlzUV4IypNvOI1o41ca_b3K8LpSBF_yNyKkD0T4bAHyOzgVXmNfrTreaJXV3vE6sNJujYjqjIT8CnpsJcg8je3bhdHZl2HJTEcvfcL8v5iDh8M References: <540973.43848.qm@web101701.mail.ssk.yahoo.co.jp> Date: Thu, 14 Jun 2018 08:10:12 +0900 (JST) From: Mori Hiroki Reply-To: Mori Hiroki Subject: Re: Armeb removal before 12 To: Warner Losh Cc: "freebsd-arm@freebsd.org" , "freebsd-arch@freebsd.org" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jun 2018 23:13:39 -0000 Hi=0A=0A----- Original Message -----=0A>From: Warner Losh = =0A>To: Mori Hiroki =0A>Cc: "freebsd-arm@freebsd.or= g" ; "freebsd-arch@freebsd.org" = =0A>Date: 2018/6/14, Thu 07:57=0A>Subject: Re: Armeb removal before 12=0A> = =0A>=0A>=0A>=0A>=0A>=0A>On Wed, Jun 13, 2018 at 4:25 PM, Mori Hiroki wrote:=0A>=0A>Hi.=0A>>=0A>>=0A>>----- Original Message --= ---=0A>>> From: Warner Losh =0A>>> To: "freebsd-arm@freebsd= .org" ; "freebsd-arch@freebsd.org" =0A>>> Cc: =0A>>> Date: 2018/6/14, Thu 01:55=0A>>> Subject: Armeb remova= l before 12=0A>>> =0A>>> I'd like to remove armeb before 12.0.=0A>>> =0A>>>= It's poorly supported today.=0A>>> =0A>>> Nobody has tested the concurrenc= y kit changes on it. And ck is now=0A>>> mandatory. We don't even know if i= t works or not.=0A>>> =0A>>> Last time we asked, it took quite a while to f= ind users.=0A>>> =0A>>> It maxes out at 256MB of RAM. This is barely large = enough for FreeBSD to=0A>>> run in.=0A>>=0A>>sys/arm/ralink target is only = 16M of RAM. I use bridge on this target=0A>>work fine.=0A>>=0A>=0A>=0A>Even= with current? It seems to have grown a lot. Even FreeBSD 11 on my atmel bo= ards, the 32MB ones can't really do much of anything (though a custom /etc/= rc.d might be usable). The 64MB ones I have troubles logging into without d= isabling a ton of stuff. And FreeBSD-current is even larger.=0A>=0A>=0A>Are= you using a custom rc.d in this setup?=0A=0A=0AOf course CURRENT.=0A=0Ahtt= ps://gist.github.com/yamori813/88224f1c96c9c592fb611b12a15e4ab5=0A=0A=0AI u= se custom rc.d by ZRouter build system.=0A=0AThanks=0A=0AHiroki Mori=0A=0A>= =A0=0A>I have FWIXP422BB target(Planex BRC-14VG) with 32M of RAM. I never b= uild=0A>>FreeBSD for this=A0target.=0A>>=0A>>I want build for=A0FWIXP422BB = but clang cross build is very slow. It take=0A>>7 hour on my machine.=0A>= =0A>=0A>I'm sorry to hear that. Even on my fast machines, it takes long tim= e.=0A>=0A>=0A>Warner=0A>=0A>=0A>=A0=0A>=0A>>> =0A>>> The hardware was last = made almost a decade ago.=0A>>> =0A>>> It uses non-standard non-mainstream = boot loaders (boot technology has moved=0A>>> on from redboot).=0A>>> =0A>>= > The cost of doing API sweeps, make universe runs, etc exceeds the benefit= =0A>>> to the project.=0A>>> =0A>>> So, given all these factors, it sounds = like a good candidate for retirement.=0A>>> =0A>>> Therefore, I'd like to r= emove it on July 15th.=0A>>> =0A>>> Comments? (please keep=A0 them on topic= to this specific thing: there's other=0A>>> things that may also be past t= heir freshness date, we'll discuss those in a=0A>>> separate thread).=0A>>>= =0A>>> Warner=0A>>=0A>>> ______________________________ _________________= =0A>>> freebsd-arm@freebsd.org mailing list=0A>>> https://lists.freebsd.org= / mailman/listinfo/freebsd-arm=0A>>> To unsubscribe, send any mail to "free= bsd-arm-unsubscribe@ freebsd.org"=0A>>> =0A>>=0A>=0A>=0A> From owner-freebsd-arm@freebsd.org Wed Jun 13 23:24: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 1839A1000255 for ; Wed, 13 Jun 2018 23:24:15 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x22b.google.com (mail-it0-x22b.google.com [IPv6:2607:f8b0:4001:c0b::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 BA0DC81F1D for ; Wed, 13 Jun 2018 23:24:14 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x22b.google.com with SMTP id u4-v6so6003064itg.0 for ; Wed, 13 Jun 2018 16:24:14 -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=zeheL/enFjhTSq+XXwjaIU75eBMw/ePyR23ecLbXufU=; b=J366PIzvOTDKsWBS6IBXpL+bDRPlSGUG9qeHAsX7ww6Af2DePMCqiOA7186mgYlvAJ 8SfKaq/FHCfIkZc4HM8JiUe6A6tHrbatH1AJUdVF2BncHaUMvd9HXahmxMr/W+5MZzUd RBO3R3fwJV4nduaS2pB2I12wRZ8isiJq6BeWO8KkqVoOLrY4Wj6EilTQ/eT8D5u5Zb8J Snur0uYzdHYuGi6OPDQebqdgBe0DblNrl7+KruBQoYNPOnx7ANne8oCgylXhfxjWaG6K 71mo9FmvpkMkZw/dFLr4tAlMDCgsw5HjomQZMUIbrdIDf3Dt5UDpU7ZUpHG4LgfpGu6w 6wEQ== 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=zeheL/enFjhTSq+XXwjaIU75eBMw/ePyR23ecLbXufU=; b=ZyRZdAhbOpjH9dq7VP8T1hCcEd1rCTVY6QHobaqLm9eushpIi/MInCNQFCHpGYnR3q UH3lxflvKb4bpKn6fKkw7gE9BopZIx5G7qClFO7+czYJDvFb3KJLYJ3mPHxLyPbn0mGf fuuC7WUZrjzwi1WQAxTZq1XLbprihlRDnKDLq1lnRR3lMNu9VkDjU4PvTNojc8HkZigQ u88m2qx90iwiIWHD0y1tk+vd5oAvH9EP1XwkaYX5TKGJBizD6XP7dKKbamPGVu+IT3Q6 syn/ql8V4DpxV0P3PSzEvAwnRl1bcmJetS+HFpko6S+EWg2ihjAX7GjoMv1zB6ZYvJpR 9Ltw== X-Gm-Message-State: APt69E1rRO8cKmBgVxue+UPH2B9+NAhDXrbUQJo+mR6sEVbqNI65YZFU iWrSZx1r+awf7+yUHHsk5O8UHaWpAmbT8IagRe6Ehw== X-Google-Smtp-Source: ADUXVKIeqjuHuhtkXQkkXA+k0ne/oMXK2H7wddXK5gDfixRSUQIu39Gr+lPl4qpQzT2CfM+CA+LoVWHfNaA8cI0VLu4= X-Received: by 2002:a24:64ce:: with SMTP id t197-v6mr153106itc.36.1528932254073; Wed, 13 Jun 2018 16:24:14 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 2002:a4f:d028:0:0:0:0:0 with HTTP; Wed, 13 Jun 2018 16:24:13 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: <861063.32056.qm@web101713.mail.ssk.yahoo.co.jp> References: <540973.43848.qm@web101701.mail.ssk.yahoo.co.jp> <861063.32056.qm@web101713.mail.ssk.yahoo.co.jp> From: Warner Losh Date: Wed, 13 Jun 2018 17:24:13 -0600 X-Google-Sender-Auth: ZjLw9CiLa-Jyxq2FQWakPGJtlHQ Message-ID: Subject: Re: Armeb removal before 12 To: Mori Hiroki Cc: "freebsd-arm@freebsd.org" , "freebsd-arch@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jun 2018 23:24:15 -0000 On Wed, Jun 13, 2018 at 5:10 PM, Mori Hiroki wrote: > Hi > > ----- Original Message ----- > >From: Warner Losh > >To: Mori Hiroki > >Cc: "freebsd-arm@freebsd.org" ; " > freebsd-arch@freebsd.org" > >Date: 2018/6/14, Thu 07:57 > >Subject: Re: Armeb removal before 12 > > > > > > > > > > > > > >On Wed, Jun 13, 2018 at 4:25 PM, Mori Hiroki > wrote: > > > >Hi. > >> > >> > >>----- Original Message ----- > >>> From: Warner Losh > >>> To: "freebsd-arm@freebsd.org" ; " > freebsd-arch@freebsd.org" > >>> Cc: > >>> Date: 2018/6/14, Thu 01:55 > >>> Subject: Armeb removal before 12 > >>> > >>> I'd like to remove armeb before 12.0. > >>> > >>> It's poorly supported today. > >>> > >>> Nobody has tested the concurrency kit changes on it. And ck is now > >>> mandatory. We don't even know if it works or not. > >>> > >>> Last time we asked, it took quite a while to find users. > >>> > >>> It maxes out at 256MB of RAM. This is barely large enough for FreeBSD > to > >>> run in. > >> > >>sys/arm/ralink target is only 16M of RAM. I use bridge on this target > >>work fine. > >> > > > > > >Even with current? It seems to have grown a lot. Even FreeBSD 11 on my > atmel boards, the 32MB ones can't really do much of anything (though a > custom /etc/rc.d might be usable). The 64MB ones I have troubles logging > into without disabling a ton of stuff. And FreeBSD-current is even larger. > > > > > >Are you using a custom rc.d in this setup? > > > Of course CURRENT. > > https://gist.github.com/yamori813/88224f1c96c9c592fb611b12a15e4ab5 > > > I use custom rc.d by ZRouter build system. > Cool! You have 10MB available. what all runs in that little space? I didn't see too much starting up Warner > Thanks > > Hiroki Mori > > > > >I have FWIXP422BB target(Planex BRC-14VG) with 32M of RAM. I never build > >>FreeBSD for this target. > >> > >>I want build for FWIXP422BB but clang cross build is very slow. It take > >>7 hour on my machine. > > > > > >I'm sorry to hear that. Even on my fast machines, it takes long time. > > > > > >Warner > > > > > > > > > >>> > >>> The hardware was last made almost a decade ago. > >>> > >>> It uses non-standard non-mainstream boot loaders (boot technology has > moved > >>> on from redboot). > >>> > >>> The cost of doing API sweeps, make universe runs, etc exceeds the > benefit > >>> to the project. > >>> > >>> So, given all these factors, it sounds like a good candidate for > retirement. > >>> > >>> Therefore, I'd like to remove it on July 15th. > >>> > >>> Comments? (please keep them on topic to this specific thing: there's > other > >>> things that may also be past their freshness date, we'll discuss those > in a > >>> separate thread). > >>> > >>> Warner > >> > >>> ______________________________ _________________ > >>> 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 Jun 14 00:04: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 F21F51004576 for ; Thu, 14 Jun 2018 00:04:07 +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 2683E84135 for ; Thu, 14 Jun 2018 00:04:06 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id w5E04IYF032397 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 13 Jun 2018 17:04:19 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w5E04I1n032396; Wed, 13 Jun 2018 17:04:18 -0700 (PDT) (envelope-from fbsd) Date: Wed, 13 Jun 2018 17:04:18 -0700 From: bob prohaska To: Mark Millard Cc: Warner Losh , "freebsd-arm@freebsd.org" , bob prohaska Subject: Re: GPT vs MBR for swap devices Message-ID: <20180614000418.GB24526@www.zefox.net> References: <20180613154826.GA24146@www.zefox.net> <20180613183730.GA24526@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.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Jun 2018 00:04:08 -0000 On Wed, Jun 13, 2018 at 02:41:35PM -0700, Mark Millard wrote: > On 2018-Jun-13, at 11:37 AM, bob prohaska wrote: > > . . . > > Some of the combinations trigger the warning: > > > > warning: total configured swap (1048576 pages) exceeds maximum recommended amount (918256 pages). > > warning: increase kern.maxswzone or reduce amount of swap. > > As I remember, the "increase kern.maxswzone" only applies if one has > previously decreased it: the modern default is the maximum recommended > as I remember (allowing for for half the theoretical maximum swap). If > I remember right the code overrode attempts to set more than the > default, only setting less (when requested). (I've not re-validated > this claim via a code inspection in some time.) > > Quoting "man 8 loader" and its kern.maxswzone material, > > Note that swap metadata can be fragmented, which means that > the system can run out of space before it reaches the > theoretical limit. Therefore, care should be taken to not > configure more swap than approximately half of the > theoretical maximum. > > So it will potentially have more fragmentation problems fitting the > extra metadata that is involved in the same amount of total RAM. > > I will note that aarch64 and armv7 for the same amount of RAM use > very different "maximum recommended amount"s. On boot the RPI3 the system reports warning: total configured swap (1048576 pages) exceeds maximum recommended amount (918256 pages). warning: increase kern.maxswzone or reduce amount of swap. I've turned off the 1 GB of microSD swap, leaving only the 3 GB mechanical disk. On the RPI2 the report is warning: total configured swap (524288 pages) exceeds maximum recommended amount (469280 pages). warning: increase kern.maxswzone or reduce amount of swap A -j4 buildworld completes without trouble, even with the excess swap. > > which I've ignored, thinking the system will ignore excess swap space. > > Again: It will potentially have more fragmentation problems fitting the > extra metadata that is involved in the same amount of total RAM. > > > Is > > this mistaken? > > I expect so because of the metadata issue. (But some later > notes below go in another direction, making this possibly > not a unique source of overall behavior differences.) > > > It's pretty clear the system does not need more than about > > 1.5 GB of swap. Available swap devices are presently sized like so: > > I'd recommend not using a whole lot more than you need, at least > small enough (total) for it to not report the warning. > > One thing I wish FreeBSD had was an (approximate) "Maximum Observed > Swap Used" that could be queried or that some built-in tool would > monitor and report. Indeed. Vmstat will log activity, but finding the peak and relating it to OOM kills or other problems seems difficult without timestamps > There are times when slowly-performing swap is infinitely better than out-of-memory kills. The Raspberry Pi series seem a prime example. > > 3 GB mechanical disk > > 2 GB microSD flash > > 1 GB microSD flash > > 1 GB USB flash > > To make your experiments comparable, I'd recommend the same total > swap be used across the alternatives being tested and compared. > This may be biased to using a smaller swap space that all the > contexts can support. > > Going in another direction: The timing variations between the types > of media may mean that the mix of what is happening at the same time > changes for -j4 from one context to the next. This could get other > issues involved in why there are variations in the overall behavior. > > > Side note: I've used eMMC on an adapter in some microSD slots. I > had to "adjust" the Pine64+ 2GB case for the adapter that I used > to reach so such is not always an automatically-available option. > > . . . > > > Just for completeness for other readers (you may well be using swap > partitions) . . . > All of the swap experiments were with hard partitions. No swap files. The most glaring (to me) oddity is that both the USB flash and microSD flash are the same make and model name, all being Sandisk Extreme. The only obvious difference is the interface to the CPU. There's no hint of filesystem trouble with any media on either interface. On the RPI3 USB does not work for flash swap, but seems fine for mechanical swap. MicroSD flash swap seems to work without issue. Either kind of swap works on the RPI2. That makes no sense to me. Thanks for reading! bob prohaska From owner-freebsd-arm@freebsd.org Thu Jun 14 09:25: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 3A60E101509C for ; Thu, 14 Jun 2018 09:25:03 +0000 (UTC) (envelope-from tvijlbrief@gmail.com) Received: from mail-ua0-x233.google.com (mail-ua0-x233.google.com [IPv6:2607:f8b0:400c:c08::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B2E0C7FAE5 for ; Thu, 14 Jun 2018 09:25:02 +0000 (UTC) (envelope-from tvijlbrief@gmail.com) Received: by mail-ua0-x233.google.com with SMTP id s13-v6so3656500uad.2 for ; Thu, 14 Jun 2018 02:25:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=jiwyRPx4Zk9vKxUzgFfPzgUe8ks4r6aulDCQH7l6Ijg=; b=txS+2RTUi6cVBCpJQhoKaDIPbdJf7pUGTn6TR0232DeJtoJn0avIKs9bytuHVDv+ZD V0NzSUZX97/QyvocXXuLbQ6Dav3MWBGfhWims55RUg1LJnPe7EVU3Sbdnz3CCAf1oErL 9nainIxvmyGbwY5yEIIQV0/bzst+xawjcc/l2iMgP625cu3FzKRLmceKceZbwr/19dAc qY/jU5jGY4HNn7n6kc/Q9mhWQlgLE2iNKeq8rCinvVf8vUcDx5HCr2pDyBH5HX+P3bjf MlP1IEdP0NQ4x7zVFo8d6n17nC/GnX5kcBFZri9oSplRsMpgFsUQdELIbbwUdYuqOtli ETmw== 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:cc; bh=jiwyRPx4Zk9vKxUzgFfPzgUe8ks4r6aulDCQH7l6Ijg=; b=hT7wHGSK6ZkfMyerrnaXdrTTF6fkND8gIExJxNWLlRuFNjZlhxZwYL0hyyeiXGybdK cCxlXmLAkWHkpX1GAvrw1yJhGYkUHmcsQ9x2agdp9ITUS/qmAghSRhrp4jqK/GTk/iON YBwYZ+VeaZIF6URNOp/jDT5AZdXamjZFzRUnMyRl6rkmBImFFliPU/k0sdI8GnOmo6tc z97Q7f7PQjl5mBow2z+C+XCVHta7hmhIllfC25j+A7rTJcqWTTq4qQ8gGHDqdb8HzDw8 LLL8FP+Fy60H0+3rvXzwCENHmpOD3GZ21sxdenV7WuS1CxHUrIN907TgE8xe+sTrlkql wMrQ== X-Gm-Message-State: APt69E1lCRkSHIAxw15Zol1WmcXffHeBhjAqD+MaPdcMPYDQT71ozyzV XWyslSM2Rc04AFzM+/+4FtCgfeN5lrG0CDW6/AkxgQ== X-Google-Smtp-Source: ADUXVKLXrlHxkF50eD8J+R5rHTcn9y13vSqdaaG0rIgGA5ygFhl6AcwO/9oFXFbl4CYeZ0iRVfyvGC2+w2faThhej3E= X-Received: by 2002:ab0:517a:: with SMTP id f55-v6mr1143321uaa.90.1528968302055; Thu, 14 Jun 2018 02:25:02 -0700 (PDT) MIME-Version: 1.0 References: <20180613154826.GA24146@www.zefox.net> <20180613183730.GA24526@www.zefox.net> In-Reply-To: From: Tom Vijlbrief Date: Thu, 14 Jun 2018 11:24:50 +0200 Message-ID: Subject: Re: GPT vs MBR for swap devices 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.26 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Jun 2018 09:25:03 -0000 I am torturing myself by doing build worlds on an original rpi with just 256Mb memory. I used to use an usb hard disk for swap and for /usr/{src,obj} but that disk has died. Currently swapping on an NFS swap file (this Linux server also hosts /usr/{src,obj} ) which works surprisingly well. The user %cpu is much better when swap is heavily used (often > 90%) compared to the old usb disk setup. The latency of the NFS server is quite small, even with the slow 100mbit rpi Ethernet. Op wo 13 jun. 2018 23:42 schreef Mark Millard via freebsd-arm < freebsd-arm@freebsd.org>: > On 2018-Jun-13, at 11:37 AM, bob prohaska wrote: > > . . . > > Some of the combinations trigger the warning: > > > > warning: total configured swap (1048576 pages) exceeds maximum > recommended amount (918256 pages). > > warning: increase kern.maxswzone or reduce amount of swap. > > As I remember, the "increase kern.maxswzone" only applies if one has > previously decreased it: the modern default is the maximum recommended > as I remember (allowing for for half the theoretical maximum swap). If > I remember right the code overrode attempts to set more than the > default, only setting less (when requested). (I've not re-validated > this claim via a code inspection in some time.) > > Quoting "man 8 loader" and its kern.maxswzone material, > > Note that swap metadata can be fragmented, which means > that > the system can run out of space before it reaches the > theoretical limit. Therefore, care should be taken to not > configure more swap than approximately half of the > theoretical maximum. > > So it will potentially have more fragmentation problems fitting the > extra metadata that is involved in the same amount of total RAM. > > I will note that aarch64 and armv7 for the same amount of RAM use > very different "maximum recommended amount"s. (Compare an armv7 rpi2 > to an aarch64 rpi3 by adding enough swap to get the notice, for > example. The rpi3 allows far more swap space as I remember.) This > variability is not obvious from the man page's material. > > > which I've ignored, thinking the system will ignore excess swap space. > > Again: It will potentially have more fragmentation problems fitting the > extra metadata that is involved in the same amount of total RAM. > > > Is > > this mistaken? > > I expect so because of the metadata issue. (But some later > notes below go in another direction, making this possibly > not a unique source of overall behavior differences.) > > > It's pretty clear the system does not need more than about > > 1.5 GB of swap. Available swap devices are presently sized like so: > > I'd recommend not using a whole lot more than you need, at least > small enough (total) for it to not report the warning. > > One thing I wish FreeBSD had was an (approximate) "Maximum Observed > Swap Used" that could be queried or that some built-in tool would > monitor and report. At times I've made variants of top that displayed > such based on the figures it uses for its swap line. I've made > judgements about -jN choices and swaps space sizes based on what I've > observed for various contexts that I use/do repeatedly and for "large" > things that I do rarely but that can fail in my normal configuration. > > > 3 GB mechanical disk > > 2 GB microSD flash > > 1 GB microSD flash > > 1 GB USB flash > > To make your experiments comparable, I'd recommend the same total > swap be used across the alternatives being tested and compared. > This may be biased to using a smaller swap space that all the > contexts can support. > > Going in another direction: The timing variations between the types > of media may mean that the mix of what is happening at the same time > changes for -j4 from one context to the next. This could get other > issues involved in why there are variations in the overall behavior. > > > Side note: I've used eMMC on an adapter in some microSD slots. I > had to "adjust" the Pine64+ 2GB case for the adapter that I used > to reach so such is not always an automatically-available option. > > > The original plan was to use the two 1 GB flash partitions in the hope > > they'd interleave, but that does not work at all. The microSD flash > > swap seems to work fine. I was wondering if the USB mechanical swap > > might point to trouble in the USB side of things, but it does not. > . . . > > > Just for completeness for other readers (you may well be using swap > partitions) . . . > > I also recommend swap partitions instead of swap files. See, for > example: > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206048 > > > (OOM process kills were not one of the issues for bugzilla 206048. > But there were other problems for swap files.) > > === > Mark Millard > marklmi at yahoo.com > ( dsl-only.net went > away in early 2018-Mar) > > _______________________________________________ > 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 Jun 14 09:25: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 7AD6B10150F4 for ; Thu, 14 Jun 2018 09:25:21 +0000 (UTC) (envelope-from yamori813@yahoo.co.jp) Received: from nh605-vm12.bullet.mail.ssk.yahoo.co.jp (nh605-vm12.bullet.mail.ssk.yahoo.co.jp [182.22.90.85]) by mx1.freebsd.org (Postfix) with SMTP id 9B4687FB16 for ; Thu, 14 Jun 2018 09:25:20 +0000 (UTC) (envelope-from yamori813@yahoo.co.jp) Received: from [182.22.66.103] by nh605.bullet.mail.ssk.yahoo.co.jp with NNFMP; 14 Jun 2018 09:22:22 -0000 Received: from [182.22.91.130] by t601.bullet.mail.ssk.yahoo.co.jp with NNFMP; 14 Jun 2018 09:22:22 -0000 Received: from [127.0.0.1] by omp603.mail.ssk.yahoo.co.jp with NNFMP; 14 Jun 2018 09:22:22 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 413788.35633.bm@omp603.mail.ssk.yahoo.co.jp Received: (qmail 94499 invoked by uid 60001); 14 Jun 2018 09:22:22 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.co.jp; s=yj20110701; t=1528968142; bh=pZwod/ryIQq1dR5058q97gkdGOirHIH7hYIVb5AROtY=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:X-YMail-JAS:References:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=KLMXQ04x76485zEtI820umhGS+Gz9qR+56zCsn5v4p8tpQH63Vu7sDyKDOPjdCSm2i2x5F4kLSIad/JeWcf6LAcgnqsyMYt79YU2Dn+YgZaOQkWGJ0O0K/iM+YMIvhEyLWQeRGGEkyD+wiIMEQESDq0fSrxLqs98npmGIZli/8c= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=yj20110701; d=yahoo.co.jp; h=Message-ID:X-YMail-OSG:Received:X-Mailer:X-YMail-JAS:References:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=T1K+cxt41WcWsaVlAbtlinX8uiW3VG5JNqjueg4HxZTAGHMp6neMxNxPrG93swgc7cmfu+oh6AZG88N34Y1jlFI9nkJ5AtJ/YdUvp7M+yr5u+tQV/M4xeT23A+JnwMJmJagg9V3NpdRrZerZ+u2nk0z8vJqxRj3KwyR9JJ1MzNk=; Message-ID: <245966.93741.qm@web101712.mail.ssk.yahoo.co.jp> X-YMail-OSG: 7VbOxXEVM1n94RUfzrTkwOk0VxKfzqE7HWTK4lwBcrksA8F9L4aSeVWIkmWLpyVA5GmbZ9Qa8T3.WQNv8SA0e9Axn3Zm8W6_ARRKcf0vqAiOl.P8i81zeFatqSRnPRS8T4QcK1X5nDFJLbhYc1ETf1Fdyp0UAMw.D64x6WSdiIeDYNhGMS8hoRnGxz0B.Ef4hrq2Ssgf4CJWsnvr6UxDVdC2aSjzUbFH0gdA1ecx1GGwxnysxqFNUd6Q2p4HfehcYHKszIWdW6A2DTQi17FIt8mbOsHrLSQmVwUuLTHThPMrVMKLn1UfOlUg_npcCc938978WFiEG8GNYwm92tvC3sIU_9ZPI71n9npupUctAqOO8KsNPx0ReHbQqAs756I2NVNSbPs63N8v6robHLFU5I3IXSsVmDUg9ffD_RZIrWrjtjUV023Z7eQa5ELQ8uwTYuhQepMdWDXe87ewLihspyCydV391a1nMcg3NLjqXFaF8XOaaQlMCSeST5JLjpqNKfw.eHzaNe9Rf1h2ovBnEEP5BMIceDv1n41O2Ul15us0V2ICxkuWXxXixhKrS2fpIkwrsmPLyRMsR9TZg4u0JiYg8ezRwXWTPVm1RrtUEOAyqzEu365HpmyRnPA7sl53 Received: from [203.165.91.75] by web101712.mail.ssk.yahoo.co.jp via HTTP; Thu, 14 Jun 2018 18:22:20 JST X-Mailer: YahooMailWebService/0.8.111_74 X-YMail-JAS: 6wAesBAVM1k8WNaxRAN9jSi_3eLSHW47SBWMEWLV0dIhbMLEVA9MNuhrZDm_jzaY5GSJ8T68MlkfkBeCzmwlz9GZ0jV.jTmlcJHJm03RZv3Ma59D5wL5ZpPghSkQfhHROco_ References: <787828.4440.qm@web101714.mail.ssk.yahoo.co.jp> Date: Thu, 14 Jun 2018 18:22:20 +0900 (JST) From: Mori Hiroki Reply-To: Mori Hiroki Subject: Re: Flash support patch review To: "freebsd-arm@freebsd.org" , "freebsd-mips@freebsd.org" In-Reply-To: <787828.4440.qm@web101714.mail.ssk.yahoo.co.jp> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Jun 2018 09:25:21 -0000 Hi=0A=0AI want this patch to current. Please check some body.=0A=0ARegards= =0A=0AHiroki Mori=0A=0A----- Original Message -----=0A>From: Mori Hiroki =0A>To: "freebsd-arm@freebsd.org" ; "freebsd-mips@freebsd.org" =0A>Date: 2018= /5/1, Tue 16:59=0A>Subject: Flash support patch review=0A> =0A>Hi.=0A>=0A>I= make two review for flash.=0A>=0A>One is cfi write bug fix on mx flash.=0A= >=0A>https://reviews.freebsd.org/D14279=0A>=0A>=0A>The other is automatic f= ind rootfs at geom_flashmap.=0A>=0A>dts file is set while firmware partitio= n by named "firmware"=0A>=0A>Then find rootfs after u-boot image.=0A>=0A>Th= is dts file is same as linux it.=0A>=0A>https://reviews.freebsd.org/D13648= =0A>=0A>=0A>Please somebody check this review.=0A>=0A>Regards=0A>=0A>Hiroki= Mori=0A>_______________________________________________=0A>freebsd-mips@fr= eebsd.org mailing list=0A>https://lists.freebsd.org/mailman/listinfo/freebs= d-mips=0A>To unsubscribe, send any mail to "freebsd-mips-unsubscribe@freebs= d.org"=0A>=0A>=0A> From owner-freebsd-arm@freebsd.org Thu Jun 14 16:44: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 A1A9B1012D77 for ; Thu, 14 Jun 2018 16:44:30 +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 1EB6B73C07 for ; Thu, 14 Jun 2018 16:44:29 +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 w5EGibvj035488 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 14 Jun 2018 09:44:38 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w5EGiaOJ035487; Thu, 14 Jun 2018 09:44:36 -0700 (PDT) (envelope-from fbsd) Date: Thu, 14 Jun 2018 09:44:36 -0700 From: bob prohaska To: Tom Vijlbrief Cc: Mark Millard , "freebsd-arm@freebsd.org" , bob prohaska Subject: Re: GPT vs MBR for swap devices Message-ID: <20180614164436.GA35161@www.zefox.net> References: <20180613154826.GA24146@www.zefox.net> <20180613183730.GA24526@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.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Jun 2018 16:44:30 -0000 On Thu, Jun 14, 2018 at 11:24:50AM +0200, Tom Vijlbrief wrote: > I am torturing myself by doing build worlds on an original rpi with just > 256Mb memory. I used to use an usb hard disk for swap and for > /usr/{src,obj} but that disk has died. > > Currently swapping on an NFS swap file (this Linux server also hosts > /usr/{src,obj} ) which works surprisingly well. The user %cpu is much > better when swap is heavily used (often > 90%) compared to the old usb disk > setup. The latency of the NFS server is quite small, even with the slow > 100mbit rpi Ethernet. > It's understood that NFS for swap works. It's also a complex and fragile solution for a seemingly-simple problem. Setting aside a little bit of a microSD or USB storage device is cheaper, uses less power, less hardware and has fewer failure points than NFS. I'd submit that it's a better solution for infrequent needs like buildworld. My point is the observation that using USB flash for swap does not seem to work on RPI3, although microSD flash does work, along with USB mechanical drives. The fact the USB flash swap does seem to work on an RPI2 suggests that there's nothing inherently wrong with USB flash as a swap medium. In particular, I'm becoming skeptical of claims that modern USB flash is too slow on write for use as swap. Thanks for reading, bob prohaska > Op wo 13 jun. 2018 23:42 schreef Mark Millard via freebsd-arm < > freebsd-arm@freebsd.org>: > > > On 2018-Jun-13, at 11:37 AM, bob prohaska wrote: > > > > . . . > > > Some of the combinations trigger the warning: > > > > > > warning: total configured swap (1048576 pages) exceeds maximum > > recommended amount (918256 pages). > > > warning: increase kern.maxswzone or reduce amount of swap. > > > > As I remember, the "increase kern.maxswzone" only applies if one has > > previously decreased it: the modern default is the maximum recommended > > as I remember (allowing for for half the theoretical maximum swap). If > > I remember right the code overrode attempts to set more than the > > default, only setting less (when requested). (I've not re-validated > > this claim via a code inspection in some time.) > > > > Quoting "man 8 loader" and its kern.maxswzone material, > > > > Note that swap metadata can be fragmented, which means > > that > > the system can run out of space before it reaches the > > theoretical limit. Therefore, care should be taken to not > > configure more swap than approximately half of the > > theoretical maximum. > > > > So it will potentially have more fragmentation problems fitting the > > extra metadata that is involved in the same amount of total RAM. > > > > I will note that aarch64 and armv7 for the same amount of RAM use > > very different "maximum recommended amount"s. (Compare an armv7 rpi2 > > to an aarch64 rpi3 by adding enough swap to get the notice, for > > example. The rpi3 allows far more swap space as I remember.) This > > variability is not obvious from the man page's material. > > > > > which I've ignored, thinking the system will ignore excess swap space. > > > > Again: It will potentially have more fragmentation problems fitting the > > extra metadata that is involved in the same amount of total RAM. > > > > > Is > > > this mistaken? > > > > I expect so because of the metadata issue. (But some later > > notes below go in another direction, making this possibly > > not a unique source of overall behavior differences.) > > > > > It's pretty clear the system does not need more than about > > > 1.5 GB of swap. Available swap devices are presently sized like so: > > > > I'd recommend not using a whole lot more than you need, at least > > small enough (total) for it to not report the warning. > > > > One thing I wish FreeBSD had was an (approximate) "Maximum Observed > > Swap Used" that could be queried or that some built-in tool would > > monitor and report. At times I've made variants of top that displayed > > such based on the figures it uses for its swap line. I've made > > judgements about -jN choices and swaps space sizes based on what I've > > observed for various contexts that I use/do repeatedly and for "large" > > things that I do rarely but that can fail in my normal configuration. > > > > > 3 GB mechanical disk > > > 2 GB microSD flash > > > 1 GB microSD flash > > > 1 GB USB flash > > > > To make your experiments comparable, I'd recommend the same total > > swap be used across the alternatives being tested and compared. > > This may be biased to using a smaller swap space that all the > > contexts can support. > > > > Going in another direction: The timing variations between the types > > of media may mean that the mix of what is happening at the same time > > changes for -j4 from one context to the next. This could get other > > issues involved in why there are variations in the overall behavior. > > > > > > Side note: I've used eMMC on an adapter in some microSD slots. I > > had to "adjust" the Pine64+ 2GB case for the adapter that I used > > to reach so such is not always an automatically-available option. > > > > > The original plan was to use the two 1 GB flash partitions in the hope > > > they'd interleave, but that does not work at all. The microSD flash > > > swap seems to work fine. I was wondering if the USB mechanical swap > > > might point to trouble in the USB side of things, but it does not. > > . . . > > > > > > Just for completeness for other readers (you may well be using swap > > partitions) . . . > > > > I also recommend swap partitions instead of swap files. See, for > > example: > > > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206048 > > > > > > (OOM process kills were not one of the issues for bugzilla 206048. > > But there were other problems for swap files.) > > > > === > > Mark Millard > > marklmi at yahoo.com > > ( dsl-only.net went > > away in early 2018-Mar) > > > > _______________________________________________ > > 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 Jun 14 16:54: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 37A3F10139CB for ; Thu, 14 Jun 2018 16:54:00 +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 83D20743F3 for ; Thu, 14 Jun 2018 16:53:59 +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 w5EGrvK8045733; Thu, 14 Jun 2018 09:53:57 -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 w5EGrvpR045732; Thu, 14 Jun 2018 09:53:57 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201806141653.w5EGrvpR045732@pdx.rh.CN85.dnsmgr.net> Subject: Re: GPT vs MBR for swap devices In-Reply-To: <20180614164436.GA35161@www.zefox.net> To: bob prohaska Date: Thu, 14 Jun 2018 09:53:57 -0700 (PDT) CC: Tom Vijlbrief , "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.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Jun 2018 16:54:00 -0000 > On Thu, Jun 14, 2018 at 11:24:50AM +0200, Tom Vijlbrief wrote: > > I am torturing myself by doing build worlds on an original rpi with just > > 256Mb memory. I used to use an usb hard disk for swap and for > > /usr/{src,obj} but that disk has died. > > > > Currently swapping on an NFS swap file (this Linux server also hosts > > /usr/{src,obj} ) which works surprisingly well. The user %cpu is much > > better when swap is heavily used (often > 90%) compared to the old usb disk > > setup. The latency of the NFS server is quite small, even with the slow > > 100mbit rpi Ethernet. > > > > It's understood that NFS for swap works. It's also a complex > and fragile solution for a seemingly-simple problem. Setting aside a > little bit of a microSD or USB storage device is cheaper, uses less power, > less hardware and has fewer failure points than NFS. I'd submit that it's > a better solution for infrequent needs like buildworld. > > My point is the observation that using USB flash for swap does not seem > to work on RPI3, although microSD flash does work, along with USB mechanical > drives. > > The fact the USB flash swap does seem to work on an RPI2 suggests that > there's nothing inherently wrong with USB flash as a swap medium. In > particular, I'm becoming skeptical of claims that modern USB flash > is too slow on write for use as swap. > > Thanks for reading, I would be very interested in seeing if resizing the swap partition in the example that greatly exceeds what the system expects as a max total swap helps to bring the OOM issue under control. I think the state of things is such that if you use up the max usable swap space on the first swap device, only that swap device well ever be used. I do not believe there is any attempts what so ever to split the allocation up so that you use the first fraction of each device. > > bob prohaska > > > > Op wo 13 jun. 2018 23:42 schreef Mark Millard via freebsd-arm < > > freebsd-arm@freebsd.org>: > > > > > On 2018-Jun-13, at 11:37 AM, bob prohaska wrote: > > > > > > . . . > > > > Some of the combinations trigger the warning: > > > > > > > > warning: total configured swap (1048576 pages) exceeds maximum > > > recommended amount (918256 pages). > > > > warning: increase kern.maxswzone or reduce amount of swap. > > > > > > As I remember, the "increase kern.maxswzone" only applies if one has > > > previously decreased it: the modern default is the maximum recommended > > > as I remember (allowing for for half the theoretical maximum swap). If > > > I remember right the code overrode attempts to set more than the > > > default, only setting less (when requested). (I've not re-validated > > > this claim via a code inspection in some time.) > > > > > > Quoting "man 8 loader" and its kern.maxswzone material, > > > > > > Note that swap metadata can be fragmented, which means > > > that > > > the system can run out of space before it reaches the > > > theoretical limit. Therefore, care should be taken to not > > > configure more swap than approximately half of the > > > theoretical maximum. > > > > > > So it will potentially have more fragmentation problems fitting the > > > extra metadata that is involved in the same amount of total RAM. > > > > > > I will note that aarch64 and armv7 for the same amount of RAM use > > > very different "maximum recommended amount"s. (Compare an armv7 rpi2 > > > to an aarch64 rpi3 by adding enough swap to get the notice, for > > > example. The rpi3 allows far more swap space as I remember.) This > > > variability is not obvious from the man page's material. > > > > > > > which I've ignored, thinking the system will ignore excess swap space. > > > > > > Again: It will potentially have more fragmentation problems fitting the > > > extra metadata that is involved in the same amount of total RAM. > > > > > > > Is > > > > this mistaken? > > > > > > I expect so because of the metadata issue. (But some later > > > notes below go in another direction, making this possibly > > > not a unique source of overall behavior differences.) > > > > > > > It's pretty clear the system does not need more than about > > > > 1.5 GB of swap. Available swap devices are presently sized like so: > > > > > > I'd recommend not using a whole lot more than you need, at least > > > small enough (total) for it to not report the warning. > > > > > > One thing I wish FreeBSD had was an (approximate) "Maximum Observed > > > Swap Used" that could be queried or that some built-in tool would > > > monitor and report. At times I've made variants of top that displayed > > > such based on the figures it uses for its swap line. I've made > > > judgements about -jN choices and swaps space sizes based on what I've > > > observed for various contexts that I use/do repeatedly and for "large" > > > things that I do rarely but that can fail in my normal configuration. > > > > > > > 3 GB mechanical disk > > > > 2 GB microSD flash > > > > 1 GB microSD flash > > > > 1 GB USB flash > > > > > > To make your experiments comparable, I'd recommend the same total > > > swap be used across the alternatives being tested and compared. > > > This may be biased to using a smaller swap space that all the > > > contexts can support. > > > > > > Going in another direction: The timing variations between the types > > > of media may mean that the mix of what is happening at the same time > > > changes for -j4 from one context to the next. This could get other > > > issues involved in why there are variations in the overall behavior. > > > > > > > > > Side note: I've used eMMC on an adapter in some microSD slots. I > > > had to "adjust" the Pine64+ 2GB case for the adapter that I used > > > to reach so such is not always an automatically-available option. > > > > > > > The original plan was to use the two 1 GB flash partitions in the hope > > > > they'd interleave, but that does not work at all. The microSD flash > > > > swap seems to work fine. I was wondering if the USB mechanical swap > > > > might point to trouble in the USB side of things, but it does not. > > > . . . > > > > > > > > > Just for completeness for other readers (you may well be using swap > > > partitions) . . . > > > > > > I also recommend swap partitions instead of swap files. See, for > > > example: > > > > > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206048 > > > > > > > > > (OOM process kills were not one of the issues for bugzilla 206048. > > > But there were other problems for swap files.) > > > > > > === > > > Mark Millard > > > marklmi at yahoo.com > > > ( dsl-only.net went > > > away in early 2018-Mar) > > > > > > _______________________________________________ > > > 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" > > > > _______________________________________________ > 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 Thu Jun 14 17:56:10 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 8B2D5101861A for ; Thu, 14 Jun 2018 17:56:10 +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 0A5D178114 for ; Thu, 14 Jun 2018 17:56:09 +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 w5EHuMi8035726 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 14 Jun 2018 10:56:23 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w5EHuMln035725; Thu, 14 Jun 2018 10:56:22 -0700 (PDT) (envelope-from fbsd) Date: Thu, 14 Jun 2018 10:56:22 -0700 From: bob prohaska To: "Rodney W. Grimes" Cc: Tom Vijlbrief , "freebsd-arm@freebsd.org" , bob prohaska Subject: Re: GPT vs MBR for swap devices Message-ID: <20180614175622.GC35161@www.zefox.net> References: <20180614164436.GA35161@www.zefox.net> <201806141653.w5EGrvpR045732@pdx.rh.CN85.dnsmgr.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201806141653.w5EGrvpR045732@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.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Jun 2018 17:56:10 -0000 On Thu, Jun 14, 2018 at 09:53:57AM -0700, Rodney W. Grimes wrote: > > I would be very interested in seeing if resizing the swap partition > in the example that greatly exceeds what the system expects as a > max total swap helps to bring the OOM issue under control. > The swap partitions at my immediate disposal are 1 GB USB flash 1 GB microSD flash 2 GB microSD flash 3 GB USB mechanical What combination is apt to be most informative? My original intent was to use 1 GB USB flash plus 1 GB microSD flash in hopes of a speed gain from interleaving, but maybe that's no longer realistic. Anything over 3 GB total causes the "too much swap" warning and I've never observed more than about 1.2 GB of swap in use. > I think the state of things is such that if you use up the > max usable swap space on the first swap device, only that > swap device well ever be used. I do not believe there is > any attempts what so ever to split the allocation up so > that you use the first fraction of each device. > Swap usage seem to be spread among active partitions, though how they're weighted is unclear to me. In days of yore there was a little note about "interleaved" in swapinfo reports, but I don't recall seeing that for a loong time. Maybe that feature has gone away..... Thanks for reading, bob prohaska From owner-freebsd-arm@freebsd.org Thu Jun 14 21:10:24 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 A2CED100723C for ; Thu, 14 Jun 2018 21:10:24 +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 C1B9482821 for ; Thu, 14 Jun 2018 21:10:23 +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 w5ELALDw046841; Thu, 14 Jun 2018 14:10:21 -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 w5ELAL0N046840; Thu, 14 Jun 2018 14:10:21 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201806142110.w5ELAL0N046840@pdx.rh.CN85.dnsmgr.net> Subject: Re: GPT vs MBR for swap devices In-Reply-To: <20180614175622.GC35161@www.zefox.net> To: bob prohaska Date: Thu, 14 Jun 2018 14:10:21 -0700 (PDT) CC: Tom Vijlbrief , "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.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Jun 2018 21:10:24 -0000 > On Thu, Jun 14, 2018 at 09:53:57AM -0700, Rodney W. Grimes wrote: > > > > I would be very interested in seeing if resizing the swap partition > > in the example that greatly exceeds what the system expects as a > > max total swap helps to bring the OOM issue under control. > > > The swap partitions at my immediate disposal are > 1 GB USB flash > 1 GB microSD flash > 2 GB microSD flash > 3 GB USB mechanical > > What combination is apt to be most informative? My original intent > was to use 1 GB USB flash plus 1 GB microSD flash in hopes of a speed > gain from interleaving, but maybe that's no longer realistic. Anything > over 3 GB total causes the "too much swap" warning and I've never observed > more than about 1.2 GB of swap in use. Well if you do a swapon to the 3 GB USB Mechanical that should be all that is usable, so we could infact test the theory by doing that one first and adding anything to it and find out if it started to use the others. Or someone that knows the current code could tell us :-) It might be interesting to do in order the swapon commands to 1G USB flash, 1G SD flash, 2G SD flash, that should if what I think happens yeild a pretty even 1G of each usable, with 1G wasted on the 2G SD flash. > > I think the state of things is such that if you use up the > > max usable swap space on the first swap device, only that > > swap device well ever be used. I do not believe there is > > any attempts what so ever to split the allocation up so > > that you use the first fraction of each device. > > > > Swap usage seem to be spread among active partitions, though > how they're weighted is unclear to me. In days of yore there > was a little note about "interleaved" in swapinfo reports, but > I don't recall seeing that for a loong time. Maybe that feature > has gone away..... > > Thanks for reading, > > bob prohaska > > > > -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-arm@freebsd.org Thu Jun 14 23:02:14 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 40EE210153CC for ; Thu, 14 Jun 2018 23:02:14 +0000 (UTC) (envelope-from editor@callfortesting.org) Received: from mail-ot0-x234.google.com (mail-ot0-x234.google.com [IPv6:2607:f8b0:4003:c0f::234]) (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 CC0EF693E3 for ; Thu, 14 Jun 2018 23:02:13 +0000 (UTC) (envelope-from editor@callfortesting.org) Received: by mail-ot0-x234.google.com with SMTP id a5-v6so8999773otf.12 for ; Thu, 14 Jun 2018 16:02:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=callfortesting-org.20150623.gappssmtp.com; s=20150623; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=bRpKGCrRgxFQeErNpjC48/TBq6l+hLLZRDlqjlOnIgc=; b=bHNf8TM4dueVJn+IyiNdrnpKR4B8fbU2fzww0rCEKms+CPCVcGVOmkcOd4Ur+q4KT5 8oHU5aANPD/ovq1NEhDXnDzush1q+L5x2JkyIxktUVPMCgNetzpAzSrKpDmnAzH6J+k+ +2Bs9deB0z1/ogXvt2XWY7Y7YHaUdRTVQp8ZNn6BPQmimShh6sjjeQr83MJSzRD7GWVO Dl2bBLsESKfm2vGWWeP1/osEIczp7gD4HdCZQckkhtRLc1hvgtpaQmT0RwZHvFub4Ac0 smketix07rYogndzRqESJJK7jNzZotIGyH+j4z0Tu9BxA6Xau8I7oY6+o9dIqZrp7Cgn iGuA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=bRpKGCrRgxFQeErNpjC48/TBq6l+hLLZRDlqjlOnIgc=; b=k3CkRDgOLfczOBGEWt9AtVSyEt0Lfw/6RiVUAprS6a2iV9ZNsm9bReqiSBRCMuMVLe 0ps144ll9nTTiggej5uNkvpLXSsM6okQmjdxME8LAiPaceTjZfwmi/aAlcZbU3riLutJ 6cb7oeGPjyaxzvbnyfOxfmf+RSpRa5teT/GgX8gv2eVBx30a8X5adKLt0Sc8f4TGkBhF AT/5w6ywuTj0bdYvn0tR6rX488IqYi5rvKbKap3+jcB85kHlzf5tGyuewVuKyLipUIPE m2pTV3RpFCxPLciY9+Krh3hlpX/eFFzqCsRz6MyvVofZ8Rs9K2VtA786Pdw7X8VbLmcP xlWA== X-Gm-Message-State: APt69E0J47Fst5++dfa3/DxlDmsHAebbmpAlqbqVPP3rTx38HJnoallN x04hy7PDYRy+6RFMGcbIiC1Fsg== X-Google-Smtp-Source: ADUXVKJxLyCmilY9Xem7xiVvRexE3NujKPqJL7CUhYi9j1ureLtAKyH6b8UYCHJPlmctfc/8899k3Q== X-Received: by 2002:a9d:70d6:: with SMTP id w22-v6mr2779100otj.375.1529017332971; Thu, 14 Jun 2018 16:02:12 -0700 (PDT) Received: from ?IPv6:2600:8802:5100:11f:29e6:10e1:1094:1147? ([2600:8802:5100:11f:29e6:10e1:1094:1147]) by smtp.gmail.com with ESMTPSA id a76-v6sm5801212oii.37.2018.06.14.16.02.09 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 14 Jun 2018 16:02:10 -0700 (PDT) Subject: Re: ARMv8 development board with GICv3 To: "Rodney W. Grimes" , Alexandru Elisei Cc: freebsd-arm@freebsd.org, freebsd-virtualization@freebsd.org References: <201806130737.w5D7bHxX038233@pdx.rh.CN85.dnsmgr.net> From: Michael Dexter Message-ID: <91705d37-7a15-afcd-cadd-c14c6a43eb84@callfortesting.org> Date: Thu, 14 Jun 2018 16:02:09 -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: <201806130737.w5D7bHxX038233@pdx.rh.CN85.dnsmgr.net> 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.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Jun 2018 23:02:14 -0000 On 6/13/18 12:37 AM, Rodney W. Grimes wrote: > I believe the Chromebook SNOW meets the criteria, not exactly a > "board" but I have one on loan from Michael Dexter that was originally > purhased to support ARMv8 bhyve work. Peter Grehan handed one to Ruslan at AsiaBSDCon a few years back which led to basic FreeBSD support. "Spurious interrupts" soon became an issue with later versions of FreeBSD and I don't believe anyone has resolved it. This model was very much the one to get for its virtualization potential at a low price. Michael From owner-freebsd-arm@freebsd.org Fri Jun 15 03:21: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 9F10B100DAD2 for ; Fri, 15 Jun 2018 03:21:19 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic317-28.consmr.mail.bf2.yahoo.com (sonic317-28.consmr.mail.bf2.yahoo.com [74.6.129.83]) (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 4A27473D78 for ; Fri, 15 Jun 2018 03:21:19 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: nB1sREkVM1n25PyNHvW4m5ce5Q4RTwIx1oW7ezxAgmUbgVQgpjzwfgP1vjL_hLM _8NgmQbV_kNPGnoOmNWAN.uvIsMGr5WIoWdHyXGzeuRkW6z4onHolUsmBcsDg4KMV2OVoj_kekjS BPK7AQnDZtijfCKyykx2ivXCvVsVncKJCgArBSzfwsj8UeYNRX5qS_X2wr6KL3q0gH6cdHTWFcSa ITFBOzL.aZbboTp7n804m0HmZGeovdm8_nWZ9B._MghWtqKppqdK38FFPhv4i7990JoCy_IEsBuz pxG9exTbwKgcydcJSGS8xgOfqzftHi43OfW_i4WdZYypn6Vpz8ar5eCl.rAWCiGTefG6izDTRSKf ECaOenRJLhWHIXjOOyegj0P_uqRakXgOB5o4s4.QqB2rij5OUA_F6QcqlQePonMEpj87xeKiJGTy 6L23z9mBU1uVi7R0GZmtiHpptvilJM6KhPbr2IxUM_fCBUJny7uT0rp8DwWrY9HTbg2aWBmT5QhY 8o1rf5O37mxivIUpn2j5qExW3ttegOd6WKMHi7H5v21BSIEGWwDohCXqVCzbqwxYDED_tNCGuZoK hZt5tSmEaSWS2QTIRnNx.dxE8vPAWKRPVYjgOn6V38KKU3BYERqWA_4YiDGeOT4JZcjK8nxnE2xB 0uBOnSMERcaJ4IoeZpYKG8COoB8fE5.VD4JW4L3gSIZx_YRmj8AUhYhTCbWMlK1VN1CDfXXxK.lf _t3TtRldz5Zbs_UdHpmRwuLEmKRZcN6srxL3Vq0L89I2N0qgVYhJXokD05oeeUWu42iAr7P9rAp5 mr8Xvt6bEv_EBGjfsd3f2F9zDyzkD6pCmhxjeaJdVSDM2lwYvsdwLUBxARdiGpRhfVdIh8izd5gC GJzhXuOHadIQBodILtHHZpgTMtJ7IxtMhvQNkZx6D1qs5s_m1CQ5Ti.wJ3bJjoHaQM5.nMUJ1fKw jaJj8zfobn3xMmDjA Received: from sonic.gate.mail.ne1.yahoo.com by sonic317.consmr.mail.bf2.yahoo.com with HTTP; Fri, 15 Jun 2018 03:21:18 +0000 Received: from ip70-189-131-151.lv.lv.cox.net (EHLO [192.168.0.109]) ([70.189.131.151]) by smtp425.mail.bf1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID a74b853e0398a9d77837c25a90100dae; Fri, 15 Jun 2018 03:21:14 +0000 (UTC) From: Mark Millard 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: Re: GPT vs MBR for swap devices Message-Id: <4B9C9E24-9428-4ECE-8551-227792F6957C@yahoo.com> Date: Thu, 14 Jun 2018 20:21:12 -0700 Cc: "Rodney W. Grimes" To: bob prohaska , freebsd-arm@freebsd.org X-Mailer: Apple Mail (2.3445.8.2) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jun 2018 03:21:19 -0000 bob prohaska fbsd at www.zefox.net wrote on Thu Jun 14 17:56:10 UTC 2018 : > On Thu, Jun 14, 2018 at 09:53:57AM -0700, Rodney W. Grimes wrote: > > > > I would be very interested in seeing if resizing the swap partition > > in the example that greatly exceeds what the system expects as a > > max total swap helps to bring the OOM issue under control. > > > > The swap partitions at my immediate disposal are > 1 GB USB flash > 1 GB microSD flash > 2 GB microSD flash > 3 GB USB mechanical > > What combination is apt to be most informative? My original intent > was to use 1 GB USB flash plus 1 GB microSD flash in hopes of a speed > gain from interleaving, but maybe that's no longer realistic. Anything > over 3 GB total causes the "too much swap" warning and I've never observed > more than about 1.2 GB of swap in use. 1.2 GB of swap in-use lets out testing just the USB flash unless one with a larger swap partition were available. Similarly for the 1 GB microSD flash. My prior suggestion could be implemented for the other two by temporarily resizing the 3 GB swap partition to be just 2 GB and then to try "USB mechanical" by itself for comparison to the 2GB swap-partition microSD flash by itself. This does overlap with the Rodney G.'s request for tests that avoid getting the too-much-swap-space warnings and so might well cover both directions of investigation if I interpret Rodney's suggestion correctly. As for use of multiple swap partitions and which are actually used, I think the swapinfo command during the time of heavy use (by size used) should indicate how much is in use for each partition: it has a "used" field in the output. # swapinfo -m Device 1M-blocks Used Avail Capacity /dev/gpt/FBSDUSSDswap 15360 19 15340 0% (The context has only one swap partition but the above does show the "used" being about 19 MBytes.) === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-arm@freebsd.org Fri Jun 15 03:52:14 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 4F13C1011037 for ; Fri, 15 Jun 2018 03:52:14 +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 C2D53754D7 for ; Fri, 15 Jun 2018 03:52:13 +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 w5F3qQms037543 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 14 Jun 2018 20:52:27 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w5F3qQAF037542; Thu, 14 Jun 2018 20:52:26 -0700 (PDT) (envelope-from fbsd) Date: Thu, 14 Jun 2018 20:52:26 -0700 From: bob prohaska To: "Rodney W. Grimes" Cc: Tom Vijlbrief , "freebsd-arm@freebsd.org" , bob prohaska Subject: Re: GPT vs MBR for swap devices Message-ID: <20180615035225.GA37370@www.zefox.net> References: <20180614175622.GC35161@www.zefox.net> <201806142110.w5ELAL0N046840@pdx.rh.CN85.dnsmgr.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201806142110.w5ELAL0N046840@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.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jun 2018 03:52:14 -0000 On Thu, Jun 14, 2018 at 02:10:21PM -0700, Rodney W. Grimes wrote: > > It might be interesting to do in order the swapon > commands to 1G USB flash, 1G SD flash, 2G SD flash, It seems clear that USB flash swap, alone or in any combination, fails early in buildworld. 1 GB of SD flash swap seemed to work consideraby better, but even it slowed greatly when 500 MB swap was in use. 3 GB of USB mechanical swap seems to work. 3 GB of SD flash swap (2 GB plus 1 GB) also seemed to work. These tests were not with the same kernel and sources, which makes the comparisons rather suspect. The machine is now reverting to r334939 using 1 GB + 2 GB of SD flash swap. If that succeeds I will then run buildworld for each case using the same kernel, world and sources. Thanks for reading! bob prohaska From owner-freebsd-arm@freebsd.org Fri Jun 15 04:01:13 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 46E3B1011D47 for ; Fri, 15 Jun 2018 04:01:13 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x235.google.com (mail-io0-x235.google.com [IPv6:2607:f8b0:4001:c06::235]) (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 D7F7275A73 for ; Fri, 15 Jun 2018 04:01:12 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x235.google.com with SMTP id t5-v6so9469121ioa.8 for ; Thu, 14 Jun 2018 21:01:12 -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 :cc; bh=Hh7LB+XxFa3V5RqxK6QXo1qe62hstCQNZMDQARgfOdc=; b=x4fQtDTwJOMxkcIVhtHXXdKeBdajjAN3LnL25xA60dTSo5P4VgjT6XZpipi1boQaKV M3BRIX4hewuAGXdnaZk7Wjs49RAE6TE1av5H4kV2xH9TQxxk+cDMkp5GDAKqO5XZK+80 q9PCrVpB+0wQLBEwsBJoQwGzHaEcNO/fQrHbDctD0inMi+kJ9gQN4lEZ/8jzJox7Q9p3 D6o+yM4ogVKaQyLnXvWktpiKeEd6O3HyvLKKmkKeQVhq9Fihk3xc0UC4NwS21hrTUzzB TTYKJlHOf6iosV8uNx3h9lC0hnhpmDsM7kmJ7gjAt+lU4Jll3lWUWf7W3YKoT7NmbnN1 zfrw== 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:cc; bh=Hh7LB+XxFa3V5RqxK6QXo1qe62hstCQNZMDQARgfOdc=; b=aHDQhCDjZk0Vtj5xcivzPrBWrKbHNsq9Ckbazr4tVyYe15QitspHNC2xq0ER8OHkXW 2ETnuwq9AMHxkZhr+bbI8PYKwPVyAcWCAmEewnDzvlRiEqV/tzauZkpYVWfhKfjqwrSe O5sQIDgqs+5uYHlZbmkRDmohe/0bLHiRaxYmi3V9QZrYNDLtgCDJcsWrmDXxvqTwSykw TRaN7AGPwkUAKB8pzorWGjN+alJpyYz0V+qNPmD7eEzqzVB1r/uqaQZfxZ16s+V9VBwf vtQmvLDu2Zh5uJBzRNq/h8aw8pgbCKYKSNPq1pNy/f68xYO7oN4DFGqjC3DIgp2NPN+K RMow== X-Gm-Message-State: APt69E30ST7jNm8hh5v8S+cVt1cM3ADvMGROgv8YZFEHuIr+ZtsJXmmD x5vJQ9/ASfM2+gWfbv48S9T6xymU6fnz4nHzb3csVw== X-Google-Smtp-Source: ADUXVKKANON3qCgq3+E2TuoWiyZNF6j6g0rtBMntVK0i2AbCgiqfiS9dhIrPaUTLIydatshRNK2VQk52FnsP8j0NwMc= X-Received: by 2002:a6b:284b:: with SMTP id o72-v6mr21472ioo.168.1529035272092; Thu, 14 Jun 2018 21:01:12 -0700 (PDT) MIME-Version: 1.0 References: <20180614175622.GC35161@www.zefox.net> <201806142110.w5ELAL0N046840@pdx.rh.CN85.dnsmgr.net> <20180615035225.GA37370@www.zefox.net> In-Reply-To: <20180615035225.GA37370@www.zefox.net> From: Warner Losh Date: Thu, 14 Jun 2018 22:00:59 -0600 Message-ID: Subject: Re: GPT vs MBR for swap devices To: bob prohaska Cc: "Rodney W. Grimes" , freebsd-arm@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jun 2018 04:01:13 -0000 On Thu, Jun 14, 2018, 9:52 PM bob prohaska wrote: > On Thu, Jun 14, 2018 at 02:10:21PM -0700, Rodney W. Grimes wrote: > > > > It might be interesting to do in order the swapon > > commands to 1G USB flash, 1G SD flash, 2G SD flash, > > It seems clear that USB flash swap, alone or in any > combination, fails early in buildworld. I think that's because USB flash can't swap fast enough to keep up with the page demand. You might be able to confirm this by looking at the write rates to the swap portions for the various other media with gstat. I suspect it's FTL is doing more expensive garbage collection under a swap work load leading to long pauses from time to time that the VM system responds to by starting OOM too soon. Warner 1 GB of SD > flash swap seemed to work consideraby better, but > even it slowed greatly when 500 MB swap was in use. > 3 GB of USB mechanical swap seems to work. 3 GB of SD flash > swap (2 GB plus 1 GB) also seemed to work. > > These tests were not with the same kernel and sources, > which makes the comparisons rather suspect. > > The machine is now reverting to r334939 using 1 GB + 2 GB of > SD flash swap. If that succeeds I will then run buildworld > for each case using the same kernel, world and sources. > > 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" > From owner-freebsd-arm@freebsd.org Fri Jun 15 05:15: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 CCE781019BFB for ; Fri, 15 Jun 2018 05:15:44 +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 4B90878AF2 for ; Fri, 15 Jun 2018 05:15: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 w5F5FXI5037794 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 14 Jun 2018 22:15:35 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w5F5FSgF037792; Thu, 14 Jun 2018 22:15:28 -0700 (PDT) (envelope-from fbsd) Date: Thu, 14 Jun 2018 22:15:27 -0700 From: bob prohaska To: Warner Losh Cc: "Rodney W. Grimes" , freebsd-arm@freebsd.org, bob prohaska Subject: Re: GPT vs MBR for swap devices Message-ID: <20180615051527.GB37370@www.zefox.net> References: <20180614175622.GC35161@www.zefox.net> <201806142110.w5ELAL0N046840@pdx.rh.CN85.dnsmgr.net> <20180615035225.GA37370@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.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jun 2018 05:15:45 -0000 On Thu, Jun 14, 2018 at 10:00:59PM -0600, Warner Losh wrote: > > I think that's because USB flash can't swap fast enough to keep up with the > page demand. You might be able to confirm this by looking at the write > rates to the swap portions for the various other media with gstat. I'll try capturing vmstat -c -w 5 to a file, but will need help interpreting the results. It seems particularly hard to correlate vmstat output with corresponding compilation activity. > I > suspect it's FTL is doing more expensive garbage collection under a swap > work load leading to long pauses from time to time that the VM system > responds to by starting OOM too soon. > Wouldn't flash speed issues equally affect SD flash and USB flash swap? >From what I can see SD flash performs far better than USB flash for swap on the RPI3. Also, using 1 GB USB flash swap together with 1 GB SD flash swap produced worse performance than the 1 GB SD flash swap alone. Are there contention issues between USB traffic and SD traffic? I've always thought they were mostly independent. If they obstruct one another that might help explain what I'm seeing. It would also make clear that my goal of "interleaving" swap devices was badly mistaken. It's worth remembering that USB flash swap (2 GB, in a single partiton) seems to work quite well on an RPI2 running current. If it works on a Pi2 shouldn't it work on a Pi3? Thanks for reading! bob prohaska From owner-freebsd-arm@freebsd.org Fri Jun 15 07:18:22 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 A836E1002213 for ; Fri, 15 Jun 2018 07:18:22 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic314-21.consmr.mail.gq1.yahoo.com (sonic314-21.consmr.mail.gq1.yahoo.com [98.137.69.84]) (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 2EC357D895 for ; Fri, 15 Jun 2018 07:18:22 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: Wu1NSjQVM1lNWFoPfFpm2XLVz4lQ3vTQQZvQwvtK1EwWn7ZO0EIAZgMrw7_hXRo HVt4MTyX1JPJI8kugkssuPYuXgkWJ40Pzfimlm6VoaFReYFo7KB4JHjOD2kYdvjx.5uD1PxaVabD ucZnXby6HPmUpaangx.Hr8LFjk6z43rHmlo9i5bnYMPFW0IGpQLHcIdCeNIKGWXEQG04N9bHZFIa JbBMPQmR9swx07oTop2xFFmBHMh2Dxuk8VOkLZEpsiQPo3QhvbLnatHBSYqUSNfIv5MgUHt9NDGt kTgasvpQY1YSYK4SgNOJutqo8QZ53MQdXFxQ.6l6VUjAm0zynQLe0_3c9qPTC9IocE_s6j9Qo3Pl 5JXVjfYXjwtiStM0Oor9BDHynBk7rBXjjCyGcq6BrB1PQELHZHtWsW8imWpAzGsErxb2WNA9RNLm gTJJvBOxDpV3GU5GAUntOBy.ad37GMIdOw8W1KWbimpHUHA2OKFUed891om4ebO0sI8i_WjC8TX3 5FDy8v6r0WMc1fmKGdVhxwiiOsGrv3tjC90Gq4NapyxAnMIvxhSJxYWwPxLGmwoHSmI0_8_iBM1Z IKnBQT6XfTgfp5bTTCEJSX0jxE.sG_4cyXP31u6r6R6zvJGfO6aAKGG7YRQsK0jUqA8QaMpF8YpT yWM1PGqxW7uqAbblI1WIlG_LzdKTSnBUqW3A5Y8FZd1Y_BcnFw5ypTFc2s7T9pn.ptk6LXzQRTdh vuF2R3_fjkIXLSZd7ByywRfouUZBcab.yK6f6ZmaCtZd5vpyFP58Y9.ywuLEM9wmoXKhHrG07CQI VZ.MAbk9MNXI_EhZPCYFlxiGoUs9UojRI7wsGOW2zJZkPQQ7LXZXMd8N464qwiavPOYbzAfzgW5O FHqJvbYFpnH2zjBl0FxqxsG9.rFA4rU1nCSdeTW8QoJxRDp1xDcJVkJNq3IUUEZtiSjdgqK3Koo0 xfGGN Received: from sonic.gate.mail.ne1.yahoo.com by sonic314.consmr.mail.gq1.yahoo.com with HTTP; Fri, 15 Jun 2018 07:18:20 +0000 Received: from ip70-189-131-151.lv.lv.cox.net (EHLO [192.168.0.109]) ([70.189.131.151]) by smtp422.mail.gq1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 52fb4ad77c201e6280a60c7ca80bd5d0; Fri, 15 Jun 2018 06:37:49 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\)) Subject: Re: GPT vs MBR for swap devices From: Mark Millard In-Reply-To: <20180615051527.GB37370@www.zefox.net> Date: Thu, 14 Jun 2018 23:37:48 -0700 Cc: Warner Losh , freebsd-arm@freebsd.org, "Rodney W. Grimes" Content-Transfer-Encoding: quoted-printable Message-Id: <834EA7A6-B567-436F-96B2-0C75FACA3FF9@yahoo.com> References: <20180614175622.GC35161@www.zefox.net> <201806142110.w5ELAL0N046840@pdx.rh.CN85.dnsmgr.net> <20180615035225.GA37370@www.zefox.net> <20180615051527.GB37370@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.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jun 2018 07:18:22 -0000 # vmstat -c -w 5 procs memory page disks faults cpu r b w avm fre flt re pi po fr sr da0 ad0 in sy cs = us sy id 1 0 0 416M 224M 1647 1 0 0 1856 142 0 0 144 1791 1024 = 4 2 94 0 0 0 416M 224M 9 0 0 0 0 1 0 0 4 85 116 = 0 0 100 0 0 0 416M 224M 12 0 0 0 0 1 0 0 2 93 113 = 0 0 100 0 0 0 416M 224M 9 0 0 0 2 1 1 0 4 64 121 = 0 0 100 On 2018-Jun-14, at 10:15 PM, bob prohaska wrote: > On Thu, Jun 14, 2018 at 10:00:59PM -0600, Warner Losh wrote: >>=20 >> I think that's because USB flash can't swap fast enough to keep up = with the >> page demand. You might be able to confirm this by looking at the = write >> rates to the swap portions for the various other media with gstat.=20 >=20 > I'll try capturing vmstat -c -w 5 to a file, but will need help=20 > interpreting the results. It seems particularly hard to correlate > vmstat output with corresponding compilation activity.=20 >=20 >> . . . When I look at: # vmstat -c -w 5 procs memory page disks faults cpu r b w avm fre flt re pi po fr sr da0 ad0 in sy cs = us sy id 1 0 0 416M 224M 1647 1 0 0 1856 142 0 0 144 1791 1024 = 4 2 94 0 0 0 416M 224M 9 0 0 0 0 1 0 0 4 85 116 = 0 0 100 0 0 0 416M 224M 12 0 0 0 0 1 0 0 2 93 113 = 0 0 100 0 0 0 416M 224M 9 0 0 0 2 1 1 0 4 64 121 = 0 0 100 . . . and "man vmstat" I do not see any column that is the swap space usage (nor any combination of columns to do such a calculation from). I do not expect that vmstat reports what you are likely/primarily looking for. An example is "avm" which for which the man page reports: . . . Note that the entire memory object's size is considered mapped even if only a = subset of the object's pages are currently mapped. This statistic = is not related to the active page queue which is used to track = real memory. The free list size ("fre") is not sufficient either. =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-arm@freebsd.org Fri Jun 15 12:06: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 B5E7B101F696 for ; Fri, 15 Jun 2018 12:06:30 +0000 (UTC) (envelope-from rb743@hermes.cam.ac.uk) Received: from ppsw-32.csi.cam.ac.uk (ppsw-32.csi.cam.ac.uk [131.111.8.132]) (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 5696569C3A for ; Fri, 15 Jun 2018 12:06:30 +0000 (UTC) (envelope-from rb743@hermes.cam.ac.uk) X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://help.uis.cam.ac.uk/email-scanner-virus Received: from sc1.bsdpad.com ([163.172.212.18]:13567) by ppsw-32.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.158]:587) with esmtpsa (LOGIN:rb743) (TLSv1:ECDHE-RSA-AES256-SHA:256) id 1fTnUr-000Z7o-07 (Exim 4.91) (return-path ); Fri, 15 Jun 2018 13:06:29 +0100 Date: Fri, 15 Jun 2018 12:56:02 +0100 From: Ruslan Bukin To: Mark Rutland Cc: Andrea Bolognani , freebsd-arm@freebsd.org, "Robert N. M. Watson" Subject: Re: virtio-net issues on aarch64 QEMU/KVM Message-ID: <20180615115602.GA29619@bsdpad.com> References: <1501165794.4378.8.camel@redhat.com> <20170804132950.GA9477@remoulade> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20170804132950.GA9477@remoulade> User-Agent: Mutt/1.6.1 (2016-04-27) Sender: "R. Bukin" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jun 2018 12:06:30 -0000 Hi Mark, Thanks for the stacktrace -- it was helpful. I found an issue: virtqueues have to be reinitialized any time we reset virtio controller, because QEMU now clears pointers to virtqueue. I have a patch: https://reviews.freebsd.org/D15821 This allows me to use QEMU's virtio-net-device just fine in FreeBSD/RISC-V. Thanks Ruslan On Fri, Aug 04, 2017 at 02:29:51PM +0100, Mark Rutland wrote: > On Thu, Jul 27, 2017 at 04:29:54PM +0200, Andrea Bolognani wrote: > > Hi all, > > Hi, > > > I'm trying 11.1-RELEASE on QEMU/KVM, and I'm having some > > trouble with VirtIO networking. > > Likewise on both counts. > > As a (vaguely-related) heads-up, you will find that 11.1 will not work as an > SMP KVM guest, as it doesn't enable SGIs for the boot CPU in the GIC > distributor, leading to a lockup later in the boot process. I think Andrew > Turner is currently looking at fixing that. > > > I've imported the official qcow2 image into libvirt by > > running > > > >   # virt-install \ > >     --name freebsd \ > >     --arch aarch64 \ > >     --machine virt \ > >     --ram 2048 \ > >     --vcpus 1 \ > >     --accelerate \ > >     --graphics none \ > >     --features acpi=off \ > >     --os-variant freebsd11.0 \ > >     --import \ > >     --disk path=/var/lib/libvirt/images/freebsd.qcow2,bus=virtio,address.type=virtio-mmio \ > >     --network network=default,model=virtio,address.type=virtio-mmio > > > > and the system comes up succesfully; however, when I > > try to activate the network interface by running > > > >   # dhclient vtnet0 > > > > the process seems to pretty much just sit there. ^C > > doesn't help. Needless to say, if I configure vtnet0 to > > be brought up at boot I never get to the prompt. > > I see the same thing with or without KVM using QEMU 2.9.0, upstream EDK2 > (commit ef3d1df77bbd5227), and the same 11.1-RELEASE VM image. I'm not using > libvirt, but I see issues when pasing QEMU: > > -device virtio-net-device,netdev=net0 netdev user,id=net0 > > At boot time, FreeBSD stops making progress after "Feeding entropy: .", and if > I send SIGINFO with ^T, I see: > > load: 1.55 cmd: ifconfig 233 [runnable] 124.01r 0.00u 123.88s 100% 2768k > > I dumped a stacktrace using QEMU's gdbserver; it looks like FreeBSD is polling > the virtio queue waiting for something: > > #0 0xffff000000170294 in VIRTIO_BUS_POLL (dev=0xfffffd00005ab900) at ./virtio_bus_if.h:159 > #1 virtqueue_poll (vq=0xffff00004083e000, len=0x0) at /usr/src/sys/dev/virtio/virtqueue.c:573 > #2 0xffff00000017707c in vtnet_ctrl_mac_cmd (sc=0xfffffd00004fa000, hwaddr=) at /usr/src/sys/dev/virtio/network/if_vtnet.c:3163 > #3 vtnet_set_hwaddr (sc=0xfffffd00004fa000) at /usr/src/sys/dev/virtio/network/if_vtnet.c:3588 > #4 0xffff000000176568 in vtnet_reinit (sc=0xfffffd00004fa000) at /usr/src/sys/dev/virtio/network/if_vtnet.c:3022 > #5 vtnet_init_locked (sc=0xfffffd00004fa000) at /usr/src/sys/dev/virtio/network/if_vtnet.c:3069 > #6 0xffff000000175ff8 in vtnet_ioctl (ifp=0xfffffd000058f000, cmd=, data=) at /usr/src/sys/dev/virtio/network/if_vtnet.c:1107 > #7 0xffff000000373e60 in ifhwioctl (cmd=, ifp=, td=, data=) at /usr/src/sys/net/if.c:2456 > #8 ifioctl (so=, cmd=2149607696, data=0xffff000054ae1888 "vtnet0", td=) at /usr/src/sys/net/if.c:2836 > #9 0xffff0000002f3b14 in fo_ioctl (fp=, com=2149607696, active_cred=, td=, data=) at /usr/src/sys/sys/file.h:323 > #10 kern_ioctl (td=0xfffffd0000a7f000, fd=3, com=2149607696, data=0xffff000054ae1888 "vtnet0") at /usr/src/sys/kern/sys_generic.c:836 > #11 0xffff0000002f377c in sys_ioctl (td=0xfffffd0000a7f000, uap=0xffff000054ae1978) at /usr/src/sys/kern/sys_generic.c:745 > #12 0xffff000000555408 in syscallenter (td=, sa=) at /usr/src/sys/arm64/arm64/../../kern/subr_syscall.c:135 > #13 svc_handler (frame=, td=) at /usr/src/sys/arm64/arm64/trap.c:139 > #14 do_el0_sync (td=0xfffffd0000a7f000, frame=) at /usr/src/sys/arm64/arm64/trap.c:366 > > ... unfortunately I'm not all that familiar with how virtio works, so I'm not > sure which end is doing the wrong thing. > > Thanks, > Mark. > _______________________________________________ > 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 Fri Jun 15 12:40:38 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 A259C1022819; Fri, 15 Jun 2018 12:40:38 +0000 (UTC) (envelope-from alexandru.elisei@gmail.com) Received: from mail-qk0-x242.google.com (mail-qk0-x242.google.com [IPv6:2607:f8b0:400d:c09::242]) (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 44B556B119; Fri, 15 Jun 2018 12:40:38 +0000 (UTC) (envelope-from alexandru.elisei@gmail.com) Received: by mail-qk0-x242.google.com with SMTP id y4-v6so5493181qka.5; Fri, 15 Jun 2018 05:40:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=X2GyeSrHWWK6/Lne4UVyV5J51h56u1ngANCp0RYdAc8=; b=uW+iVsey1o9RIglz7ar/Xs9GYpv9G9YRr98kooGAUtp+2IsN0Re6vYGbLfOSgmjXMp n1OdHrDVvJ4J5GJgcPxbjPzx89o8oOeHBMcBKJVBZ8Xfsh4nWowtq34hX0M2BnkbPDxx Vi9vzsSl+d5dcb728Fm2HaebP6ph40I4jznG3Gk6ujt2nDQoqVOffwp2de9W/P9fyf17 N9LjqROFB8gGP4Ymo4tUXwetc75axOakliWydPyK8dSy5VT/uHV1mS1eUd14wYawp3QJ 0OmXc3ofodfsNCNtT2iM5haI//+vySyxtmDSOawTbVV4LKOaqmJ+D07LZthbmjKDPxML z3KQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=X2GyeSrHWWK6/Lne4UVyV5J51h56u1ngANCp0RYdAc8=; b=pX5LyMRsUfEuLqj0foaNC2JFyCw9jdHh3OB9S4kiNRKQ1ojY2f1jxi8opybalVz9Uj NsPbATTJAwYH48KUXyEZzfx9ugr73mRPODuf+SyGYlqDmY+aZG7d/vwiOAjMb0XhLljo 1qpaLQYSBzHXEYjKcDgxNxsEOES1y6+5x6ExN70qhsPeoMbU65BZnVLS/dYBQf4sIdv1 uIwLbIApf3iEOfcUoyj1MKr+BKZt9TwRKN13Gb6MZORp9K4JQ9PIEA9EPQ/tpBKAUDqU f8sDpyqxBY/JzrKcnhd19G3A0+yfMuAV/SDDdsvC/7QOf+VZzRI1/0fHUvyYH6PghoQh +qTw== X-Gm-Message-State: APt69E1XEpMlHftlI1lHJ9mh9L/Snl1szh66UlqeBpdcseDLKiaNgvaE SYYlHfunAPvOhV3SAW+iy1sS2i98VLpw/ieXZkvUkQ== X-Google-Smtp-Source: ADUXVKKr2kE/CI9FLyyznX8Ue7eTK3MD17jupwzBl9IJTJrLXbZhzF0E7e+GBgGh3qmglxOgzxFKC810b9TWpth1y7w= X-Received: by 2002:a37:cc8e:: with SMTP id n14-v6mr1131281qkl.420.1529066437480; Fri, 15 Jun 2018 05:40:37 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:aed:2be7:0:0:0:0:0 with HTTP; Fri, 15 Jun 2018 05:40:37 -0700 (PDT) In-Reply-To: <91705d37-7a15-afcd-cadd-c14c6a43eb84@callfortesting.org> References: <201806130737.w5D7bHxX038233@pdx.rh.CN85.dnsmgr.net> <91705d37-7a15-afcd-cadd-c14c6a43eb84@callfortesting.org> From: Alexandru Elisei Date: Fri, 15 Jun 2018 15:40:37 +0300 Message-ID: Subject: Re: ARMv8 development board with GICv3 To: Michael Dexter Cc: "Rodney W. Grimes" , freebsd-arm@freebsd.org, freebsd-virtualization@freebsd.org Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jun 2018 12:40:38 -0000 Thank you all for your suggestions. I was considering the espressobin board [1], I only need a disk to boot from and a network controller to connect to the board. It uses a Marvell 3720 SoC (model 88F3720) which according to the specs [2] has all exception levels and it uses a GIC-500 interrupt controller which implementes the GICv3 specification [3]. The board is supported under linux [4], I was wondering if anyone can tell me how well it is supported under FreeBSD. [1] http://espressobin.net/ [2] https://origin-www.marvell.com/documents/qc8hltbjybmpjhx36ckw/ [3] http://infocenter.arm.com/help/topic/com.arm.doc.ddi0516b/DDI0516B_gic5000_r0p0_trm.pdf [4] https://github.com/torvalds/linux/tree/master/arch/arm64/boot/dts/marvell Regards, Alexandru Elisei On Fri, Jun 15, 2018 at 2:02 AM, Michael Dexter wrote: > On 6/13/18 12:37 AM, Rodney W. Grimes wrote: > >> I believe the Chromebook SNOW meets the criteria, not exactly a >> "board" but I have one on loan from Michael Dexter that was originally >> purhased to support ARMv8 bhyve work. > > > Peter Grehan handed one to Ruslan at AsiaBSDCon a few years back which led > to basic FreeBSD support. "Spurious interrupts" soon became an issue with > later versions of FreeBSD and I don't believe anyone has resolved it. This > model was very much the one to get for its virtualization potential at a low > price. > > Michael From owner-freebsd-arm@freebsd.org Fri Jun 15 13:24:24 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 DF68F1003E97; Fri, 15 Jun 2018 13:24:24 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (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 72F106D278; Fri, 15 Jun 2018 13:24:24 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.89 (FreeBSD)) (envelope-from ) id 1fToiH-000EhY-FS; Fri, 15 Jun 2018 15:24:25 +0200 Date: Fri, 15 Jun 2018 15:24:25 +0200 From: Kurt Jaeger To: Rebecca Cran Cc: freebsd-arm@freebsd.org, freebsd-virtualization@freebsd.org Subject: Re: ARMv8 development board with GICv3 Message-ID: <20180615132425.GI4028@home.opsec.eu> References: <201806130737.w5D7bHxX038233@pdx.rh.CN85.dnsmgr.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jun 2018 13:24:25 -0000 Hi! > On a similar note, the SoftIron OverDrive 1000 > (https://softiron.com/development-tools/overdrive-1000/) might be > suitable? It uses an A57 in an Opteron A1100 SoC. At $600 it's > relatively affordable for a complete system. https://wiki.freebsd.org/arm64/OverDrive1000 says that it runs FreeBSD already 8-} -- pi@opsec.eu +49 171 3101372 2 years to go ! From owner-freebsd-arm@freebsd.org Fri Jun 15 13:33: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 D93DE1004C59; Fri, 15 Jun 2018 13:33:11 +0000 (UTC) (envelope-from tuexen@fh-muenster.de) Received: from drew.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.franken.de", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6A6A26D955; Fri, 15 Jun 2018 13:33:11 +0000 (UTC) (envelope-from tuexen@fh-muenster.de) Received: from [IPv6:2003:cd:6f2e:bd00:5f:1e76:426c:ae2a] (p200300CD6F2EBD00005F1E76426CAE2A.dip0.t-ipconnect.de [IPv6:2003:cd:6f2e:bd00:5f:1e76:426c:ae2a]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTPSA id 6DF3B721E2826; Fri, 15 Jun 2018 15:33:07 +0200 (CEST) From: Michael Tuexen Message-Id: <0C56F55F-843C-4175-A9D1-DF97878629D3@fh-muenster.de> Content-Type: multipart/signed; boundary="Apple-Mail=_A81D694A-6A59-4BFC-B538-10096AD1BA04"; protocol="application/pkcs7-signature"; micalg=sha1 Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\)) Subject: Re: ARMv8 development board with GICv3 Date: Fri, 15 Jun 2018 15:33:06 +0200 In-Reply-To: <20180615132425.GI4028@home.opsec.eu> Cc: Rebecca Cran , freebsd-arm@freebsd.org, freebsd-virtualization@freebsd.org To: Kurt Jaeger References: <201806130737.w5D7bHxX038233@pdx.rh.CN85.dnsmgr.net> <20180615132425.GI4028@home.opsec.eu> X-Mailer: Apple Mail (2.3445.8.2) X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=disabled version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail-n.franken.de X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jun 2018 13:33:12 -0000 --Apple-Mail=_A81D694A-6A59-4BFC-B538-10096AD1BA04 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii > On 15. Jun 2018, at 15:24, Kurt Jaeger wrote: > > Hi! > >> On a similar note, the SoftIron OverDrive 1000 >> (https://softiron.com/development-tools/overdrive-1000/) might be >> suitable? It uses an A57 in an Opteron A1100 SoC. At $600 it's >> relatively affordable for a complete system. > > https://wiki.freebsd.org/arm64/OverDrive1000 > says that it runs FreeBSD already 8-} I'm running head on it and it works pretty stable. Just replaced the HDD with an SSD. Best regards Michael > > -- > pi@opsec.eu +49 171 3101372 2 years to go ! > _______________________________________________ > 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" --Apple-Mail=_A81D694A-6A59-4BFC-B538-10096AD1BA04 Content-Disposition: attachment; filename=smime.p7s Content-Type: application/pkcs7-signature; name=smime.p7s Content-Transfer-Encoding: base64 MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIQkDCCBNUw ggO9oAMCAQICCFBOxvU9EbRkMA0GCSqGSIb3DQEBCwUAMHExCzAJBgNVBAYTAkRFMRwwGgYDVQQK ExNEZXV0c2NoZSBUZWxla29tIEFHMR8wHQYDVQQLExZULVRlbGVTZWMgVHJ1c3QgQ2VudGVyMSMw IQYDVQQDExpEZXV0c2NoZSBUZWxla29tIFJvb3QgQ0EgMjAeFw0xNDA3MjIxMjA4MjZaFw0xOTA3 MDkyMzU5MDBaMFoxCzAJBgNVBAYTAkRFMRMwEQYDVQQKEwpERk4tVmVyZWluMRAwDgYDVQQLEwdE Rk4tUEtJMSQwIgYDVQQDExtERk4tVmVyZWluIFBDQSBHbG9iYWwgLSBHMDEwggEiMA0GCSqGSIb3 DQEBAQUAA4IBDwAwggEKAoIBAQDpm8NnhfkNrvWNVMOWUDU9YuluTO2U1wBblSJ01CDrNI/W7MAx BAuZgeKmFNJSoCgjhIt0iQReW+DieMF4yxbLKDU5ey2QRdDtoAB6fL9KDhsAw4bpXCsxEXsM84Ik Q4wcOItqaACa7txPeKvSxhObdq3u3ibo7wGvdA/BCaL2a869080UME/15eOkyGKbghoDJzANAmVg Te3RCSMqljVYJ9N2xnG2kB3E7f81hn1vM7PbD8URwoqDoZRdQWvY0hD1TP3KUazZve+Sg7va64sW VlZDz+HVEz2mHycwzUlU28kTNJpxdcVs6qcLmPkhnSevPqM5OUhqjK3JmfvDEvK9AgMBAAGjggGG MIIBgjAOBgNVHQ8BAf8EBAMCAQYwHQYDVR0OBBYEFEm3xs/oPR9/6kR7Eyn38QpwPt5kMB8GA1Ud IwQYMBaAFDHDeRu69VPXF+CJei0XbAqzK50zMBIGA1UdEwEB/wQIMAYBAf8CAQIwYgYDVR0gBFsw WTARBg8rBgEEAYGtIYIsAQEEAgIwEQYPKwYBBAGBrSGCLAEBBAMAMBEGDysGAQQBga0hgiwBAQQD ATAPBg0rBgEEAYGtIYIsAQEEMA0GCysGAQQBga0hgiweMD4GA1UdHwQ3MDUwM6AxoC+GLWh0dHA6 Ly9wa2kwMzM2LnRlbGVzZWMuZGUvcmwvRFRfUk9PVF9DQV8yLmNybDB4BggrBgEFBQcBAQRsMGow LAYIKwYBBQUHMAGGIGh0dHA6Ly9vY3NwMDMzNi50ZWxlc2VjLmRlL29jc3ByMDoGCCsGAQUFBzAC hi5odHRwOi8vcGtpMDMzNi50ZWxlc2VjLmRlL2NydC9EVF9ST09UX0NBXzIuY2VyMA0GCSqGSIb3 DQEBCwUAA4IBAQBjICj9nCGGcr45Rlk5MiW8qQGbDczKfUGchm0KbiyzE1l1sTOSG2EnFv/DstU1 gvuEKgFJvWa7Zi+ywgZdbj9u4wFaW8pDY1yVtuExpx/VB19N5mWCTjL5w3x6S81NXHTuIfJ1AuxS PtLJatOQI25JZzW+f01WpOzML8+3oZeocj7JvEDWWqQIPda8gsO3tzKOsSyOam23NQIZz/U5RFhj pyQAELC7/E6vbi84u6VXST/YblBvLJeW3B1GmmWJz67M8uXZn1OzPqEvkqnYC8aEHwTG6x7on321 e6UC8STFJGMRNMxakyAqeYg6JUKQqWU7fIbTEhUjKfws2sw5W1QXMIIFojCCBIqgAwIBAgIHF6Qk oQlIMzANBgkqhkiG9w0BAQsFADBaMQswCQYDVQQGEwJERTETMBEGA1UEChMKREZOLVZlcmVpbjEQ MA4GA1UECxMHREZOLVBLSTEkMCIGA1UEAxMbREZOLVZlcmVpbiBQQ0EgR2xvYmFsIC0gRzAxMB4X DTE0MDUyNzE0NTQwOVoXDTE5MDcwOTIzNTkwMFowgcYxCzAJBgNVBAYTAkRFMRwwGgYDVQQIExNO b3JkcmhlaW4tV2VzdGZhbGVuMREwDwYDVQQHEwhNdWVuc3RlcjEgMB4GA1UEChMXRmFjaGhvY2hz Y2h1bGUgTXVlbnN0ZXIxIzAhBgNVBAsTGkRhdGVudmVyYXJiZWl0dW5nc3plbnRyYWxlMR0wGwYD VQQDExRGSCBNdWVuc3RlciBDQSAtIEcwMTEgMB4GCSqGSIb3DQEJARYRY2FAZmgtbXVlbnN0ZXIu ZGUwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC4eWyu8GzsIv0iowf2v/9BT0SmCFNX /eyQe5BncOk1j6XIlY5bnNu1S5uBe3uVgekgTh3gJyVNlaoIfCgAjqCrNJIaNQq5fr/S6L8uFeaU O8IF/C4RH5P7f9Hn2GUueEjmJhg9CI3LBAhrfAmEEtNmuVfDycN2MjngwDNxUNRfuXbWxuhkgDqJ 0ztJeayHGhFDrGx88eyStx40xy+0c0OFWdWxzBFQlBRHnl+zRftj3c9qy6BY+/fGaA2vV1oKr3h5 X6eyU1T8YlpP1NDe4bylqAteX01sM2Qciu8UAPnNc7Sb93TQjhCFRVDIS3CdN6AOpwz5YWEld6ey CdmFZ7pvAgMBAAGjggH+MIIB+jASBgNVHRMBAf8ECDAGAQH/AgEBMA4GA1UdDwEB/wQEAwIBBjAR BgNVHSAECjAIMAYGBFUdIAAwHQYDVR0OBBYEFArzW7zkMYDWNUKJptPDzzfe0d/XMB8GA1UdIwQY MBaAFEm3xs/oPR9/6kR7Eyn38QpwPt5kMBwGA1UdEQQVMBOBEWNhQGZoLW11ZW5zdGVyLmRlMIGI BgNVHR8EgYAwfjA9oDugOYY3aHR0cDovL2NkcDEucGNhLmRmbi5kZS9nbG9iYWwtcm9vdC1jYS9w dWIvY3JsL2NhY3JsLmNybDA9oDugOYY3aHR0cDovL2NkcDIucGNhLmRmbi5kZS9nbG9iYWwtcm9v dC1jYS9wdWIvY3JsL2NhY3JsLmNybDCB1wYIKwYBBQUHAQEEgcowgccwMwYIKwYBBQUHMAGGJ2h0 dHA6Ly9vY3NwLnBjYS5kZm4uZGUvT0NTUC1TZXJ2ZXIvT0NTUDBHBggrBgEFBQcwAoY7aHR0cDov L2NkcDEucGNhLmRmbi5kZS9nbG9iYWwtcm9vdC1jYS9wdWIvY2FjZXJ0L2NhY2VydC5jcnQwRwYI KwYBBQUHMAKGO2h0dHA6Ly9jZHAyLnBjYS5kZm4uZGUvZ2xvYmFsLXJvb3QtY2EvcHViL2NhY2Vy dC9jYWNlcnQuY3J0MA0GCSqGSIb3DQEBCwUAA4IBAQDeRwM11kpvuRIPuzWXLapr/ZBtB76V3cuF l45x/Kx0u03yjB4GaBPcxihn4P1z5KhRYkDBMo8HXkOgbL59aF6VdOlCurEgZvghKvUkKOCyWeYx S9rTGPBkbGiNn2ATVuLXzF8rDf50ynAIu3otstOOv+3Ifqi1pzCva1nO64khQA5Gd5/BNyu+YHbW f8ERAf9leu5a7yVI7cv1gCZAHpWJpkUKmfawyY4sAJ2hbGZRBvdACOxrfbuMdSOzPneT2rlmvH+D 7M6DmzVabLYk6UtAxQhldd/T/qsHkWvaWXHt0Eb9STs2Fl03Ls7M3NyLQLhaeR3ysNURYcaEfaB+ lxN+MIIGDTCCBPWgAwIBAgIHG5mIdDexozANBgkqhkiG9w0BAQsFADCBxjELMAkGA1UEBhMCREUx HDAaBgNVBAgTE05vcmRyaGVpbi1XZXN0ZmFsZW4xETAPBgNVBAcTCE11ZW5zdGVyMSAwHgYDVQQK ExdGYWNoaG9jaHNjaHVsZSBNdWVuc3RlcjEjMCEGA1UECxMaRGF0ZW52ZXJhcmJlaXR1bmdzemVu dHJhbGUxHTAbBgNVBAMTFEZIIE11ZW5zdGVyIENBIC0gRzAxMSAwHgYJKoZIhvcNAQkBFhFjYUBm aC1tdWVuc3Rlci5kZTAeFw0xNjA3MDQwNzA2MTNaFw0xOTA3MDQwNzA2MTNaMHwxCzAJBgNVBAYT AkRFMSAwHgYDVQQKDBdGYWNoaG9jaHNjaHVsZSBNdWVuc3RlcjEyMDAGA1UECwwpRmFjaGJlcmVp Y2ggRWxla3Ryb3RlY2huaWsgdW5kIEluZm9ybWF0aWsxFzAVBgNVBAMMDk1pY2hhZWwgVHVleGVu MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAzJoaUG3Zm24XxA/zNg2sbFcL56w8xqMg +X6G7UsYec3YEncnlkw3jgE5nDefos7UVoCA7wPjFTj8AQt5xfpXElnbM45IPy5Ng7g6dS7biGSM VRACPXe1PrjgApRAwwGmCPvALnZXkmKP6Zlf+3VLfz9YWIIaeKu3jFM2Lk6Y3gr5U1l8bjHSawOo WMlfvSsXXLT38zKW7Uz9jS278j0OqHANBPgsE6/LJoCWFInwlvybxhO3nGU7OteUGaPikqzvjLsL YgpHDi0WjMZfVx/UtUSzZ4EJvmJTBeuVwyKnCbrawnfwYPTQQ6VE1OkAzmsMByBbEwJ996RtG//T XCG06QIDAQABo4ICRzCCAkMwQAYDVR0gBDkwNzARBg8rBgEEAYGtIYIsAQEEAwUwEQYPKwYBBAGB rSGCLAIBBAMBMA8GDSsGAQQBga0hgiwBAQQwCQYDVR0TBAIwADAOBgNVHQ8BAf8EBAMCBeAwHQYD VR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMB0GA1UdDgQWBBTQHa9qhKgSZgCCAPThZkXaEaJ/ dTAfBgNVHSMEGDAWgBQK81u85DGA1jVCiabTw8833tHf1zAgBgNVHREEGTAXgRV0dWV4ZW5AZmgt bXVlbnN0ZXIuZGUwgYgGA1UdHwSBgDB+MD2gO6A5hjdodHRwOi8vY2RwMS5wY2EuZGZuLmRlL2Zo LW11ZW5zdGVyLWNhL3B1Yi9jcmwvY2FjcmwuY3JsMD2gO6A5hjdodHRwOi8vY2RwMi5wY2EuZGZu LmRlL2ZoLW11ZW5zdGVyLWNhL3B1Yi9jcmwvY2FjcmwuY3JsMIHXBggrBgEFBQcBAQSByjCBxzAz BggrBgEFBQcwAYYnaHR0cDovL29jc3AucGNhLmRmbi5kZS9PQ1NQLVNlcnZlci9PQ1NQMEcGCCsG AQUFBzAChjtodHRwOi8vY2RwMS5wY2EuZGZuLmRlL2ZoLW11ZW5zdGVyLWNhL3B1Yi9jYWNlcnQv Y2FjZXJ0LmNydDBHBggrBgEFBQcwAoY7aHR0cDovL2NkcDIucGNhLmRmbi5kZS9maC1tdWVuc3Rl ci1jYS9wdWIvY2FjZXJ0L2NhY2VydC5jcnQwDQYJKoZIhvcNAQELBQADggEBAEj2/6x4kzoCVIiu aaminPrOHxACyoYsmSRjYPQpgW5xRj/FlolO1nG+ZZ11sqTb3TdCGD69ko5/zs8eGKnv/i0VLCHF g1JLfpaxElN5RrR/cqRJrbzKshF9aUkBODF8vlf9BCeimMK3fifjbbWRyxHssfEECffujD7/Yvta NYMO46Roz39lIK2s37IVFq3V5RWzUeTuwpP9t8lOxirOi9eK2OYI/dh0HjR2S5Dr9nMR1dNulrhz jlFxGc+opefGScrRR9Ec0eqTXlbt1Q9UzNIYVS+OGZY8/bBbprwXVTmwSp8dygEULkIaMbLsaTaW 6TehuL8ousPJkL52SOENgSkxggQpMIIEJQIBATCB0jCBxjELMAkGA1UEBhMCREUxHDAaBgNVBAgT E05vcmRyaGVpbi1XZXN0ZmFsZW4xETAPBgNVBAcTCE11ZW5zdGVyMSAwHgYDVQQKExdGYWNoaG9j aHNjaHVsZSBNdWVuc3RlcjEjMCEGA1UECxMaRGF0ZW52ZXJhcmJlaXR1bmdzemVudHJhbGUxHTAb BgNVBAMTFEZIIE11ZW5zdGVyIENBIC0gRzAxMSAwHgYJKoZIhvcNAQkBFhFjYUBmaC1tdWVuc3Rl ci5kZQIHG5mIdDexozAJBgUrDgMCGgUAoIICKzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwG CSqGSIb3DQEJBTEPFw0xODA2MTUxMzMzMDZaMCMGCSqGSIb3DQEJBDEWBBTKcxcZYTPM9aVKSr47 imdzeV1kyjCB4wYJKwYBBAGCNxAEMYHVMIHSMIHGMQswCQYDVQQGEwJERTEcMBoGA1UECBMTTm9y ZHJoZWluLVdlc3RmYWxlbjERMA8GA1UEBxMITXVlbnN0ZXIxIDAeBgNVBAoTF0ZhY2hob2Noc2No dWxlIE11ZW5zdGVyMSMwIQYDVQQLExpEYXRlbnZlcmFyYmVpdHVuZ3N6ZW50cmFsZTEdMBsGA1UE AxMURkggTXVlbnN0ZXIgQ0EgLSBHMDExIDAeBgkqhkiG9w0BCQEWEWNhQGZoLW11ZW5zdGVyLmRl AgcbmYh0N7GjMIHlBgsqhkiG9w0BCRACCzGB1aCB0jCBxjELMAkGA1UEBhMCREUxHDAaBgNVBAgT E05vcmRyaGVpbi1XZXN0ZmFsZW4xETAPBgNVBAcTCE11ZW5zdGVyMSAwHgYDVQQKExdGYWNoaG9j aHNjaHVsZSBNdWVuc3RlcjEjMCEGA1UECxMaRGF0ZW52ZXJhcmJlaXR1bmdzemVudHJhbGUxHTAb BgNVBAMTFEZIIE11ZW5zdGVyIENBIC0gRzAxMSAwHgYJKoZIhvcNAQkBFhFjYUBmaC1tdWVuc3Rl ci5kZQIHG5mIdDexozANBgkqhkiG9w0BAQEFAASCAQBMfYM/IokDFgezHLaqn/TE1rNNZYqLjMth 2UBavd2SBSJLUsFYuo1pMBPXq0ALZKGXf+oaZxcsTE6iSLENszEb1gaZRcdMcat2SakK94s0qTTR 67GX1qWoPYWq/xZ3usESvZlLOJzvsdzyL08wOOHM8qGuQD6U2IZeNdekYOyTFmHeNpl+uH2yEeNc nsy1LeTShl9FEKF+8CX+9Ruc/jZP6qZF6sbhcpfqi1vlTpUDSWQTUaDh8pwgoTa+oubdU3OYsANp DyfYkBG2lfst37iXKC8jMjjXtgJRSKZ+RyjrhE3hieiJlUECTBMKkV/c2qQ5rohAcW0+oUzHZHam yIeQAAAAAAAA --Apple-Mail=_A81D694A-6A59-4BFC-B538-10096AD1BA04-- From owner-freebsd-arm@freebsd.org Fri Jun 15 15:43:24 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 8EE71101024A for ; Fri, 15 Jun 2018 15:43:24 +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 E35B7747A1 for ; Fri, 15 Jun 2018 15:43:23 +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 w5FFhZ4K039870 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 15 Jun 2018 08:43:36 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w5FFhY2m039869; Fri, 15 Jun 2018 08:43:34 -0700 (PDT) (envelope-from fbsd) Date: Fri, 15 Jun 2018 08:43:34 -0700 From: bob prohaska To: Mark Millard Cc: Warner Losh , freebsd-arm@freebsd.org, "Rodney W. Grimes" , bob prohaska Subject: Re: GPT vs MBR for swap devices Message-ID: <20180615154334.GA39777@www.zefox.net> References: <20180614175622.GC35161@www.zefox.net> <201806142110.w5ELAL0N046840@pdx.rh.CN85.dnsmgr.net> <20180615035225.GA37370@www.zefox.net> <20180615051527.GB37370@www.zefox.net> <834EA7A6-B567-436F-96B2-0C75FACA3FF9@yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <834EA7A6-B567-436F-96B2-0C75FACA3FF9@yahoo.com> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jun 2018 15:43:24 -0000 On Thu, Jun 14, 2018 at 11:37:48PM -0700, Mark Millard wrote: > > When I look at: > > # vmstat -c -w 5 > procs memory page disks faults cpu > r b w avm fre flt re pi po fr sr da0 ad0 in sy cs us sy id > 1 0 0 416M 224M 1647 1 0 0 1856 142 0 0 144 1791 1024 4 2 94 > 0 0 0 416M 224M 9 0 0 0 0 1 0 0 4 85 116 0 0 100 > 0 0 0 416M 224M 12 0 0 0 0 1 0 0 2 93 113 0 0 100 > 0 0 0 416M 224M 9 0 0 0 2 1 1 0 4 64 121 0 0 100 > . . . > > and "man vmstat" I do not see any column that is the swap space > usage (nor any combination of columns to do such a calculation > from). > > I do not expect that vmstat reports what you are likely/primarily > looking for. > > An example is "avm" which for which the man page reports: > > . . . Note that the entire > memory object's size is considered mapped even if only a subset > of the object's pages are currently mapped. This statistic is > not related to the active page queue which is used to track real > memory. > > The free list size ("fre") is not sufficient either. > That seems astonishing. I imagined that among those columns _had_ to be reads from and writes to the swap partitions. It looks as if top -d 1000 | grep Swap produces a running list of swap usage, but one must guess how many times to iterate: bob@www:/usr/src % top -d 1000 | grep Swap Swap: 3072M Total, 30M Used, 3041M Free Swap: 3072M Total, 30M Used, 3041M Free Swap: 3072M Total, 30M Used, 3041M Free Swap: 3072M Total, 30M Used, 3041M Free Swap: 3072M Total, 30M Used, 3041M Free ....... Replacing the "1000" with "0" or "infinite" triggers a syntax error. Is there a special parameter that makes top run till it's killed, as in interactive mode? I didn't recognize any hint in the man page. Thanks for reading! bob prohaska From owner-freebsd-arm@freebsd.org Fri Jun 15 15: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 367A8101097C for ; Fri, 15 Jun 2018 15:57:19 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x22e.google.com (mail-io0-x22e.google.com [IPv6:2607:f8b0:4001:c06::22e]) (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 C77D674D26 for ; Fri, 15 Jun 2018 15:57:18 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x22e.google.com with SMTP id f1-v6so11134799ioh.6 for ; Fri, 15 Jun 2018 08:57:18 -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=j+k1J4IIBUaMylVDMa6Id4RqPMv3cH7DQkDPpDne3eo=; b=jZdNPOKWOhS1mv5zUArefdL11ZQ7CtNxUNGcflcrylEDO/JLSo9T7UN+tRGQ/c4vag PVmkVSa0JiMCR6nGY2XtpdLhV9D6Il2H8VfKJyrKbfJW+lm5LKRVGJGEb1q0j5iRIcIm XYvBFJe1mCvzflcNvc4cEM54ULQETPgAdqmkTk6UwLjXDzvkbp6FWqOOlArRDtdbwvX9 4tB+mPtWAGlM/C67/msacs25d5KegvUnJq3ol913UQ8PTh3DiKxwVMuIHBl8crMxkLNo zKQqDt/lc7D4ZhN/XaRtp87F4+hRkta+/huHu6H9XEbBa1DUOnRw7rNeQhMYNsbKN5jo RNJw== 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=j+k1J4IIBUaMylVDMa6Id4RqPMv3cH7DQkDPpDne3eo=; b=NxIMofVi2Hxv4RKOelGLmRp7jSN1MemioEpjzzawZn8BhqLfra4c6KtXjAy8GzdZp2 4VdrDqWIfVhqY36MQ8IrURiH+93V5X2MP2JwujSQOMKZiDjYOjGzne4+J5JB/Zauqvqw S65K4zxUUqHKcCNU7t1J3++KwoxjE33mpOUDvgadH4oOCpnKtNTH7UXHpjgxXMMh+L+c 7NuiFICPgBUrWQottMgNBiF6Gt4CWls3nmXKLg/3Dzoebagi4Q/5kdhqSHjvQfl9/QOR QEI+rf4EuD99YThLsrkVg8kR5gIqu7LIR7q40mDcDVg5w5ha/omLF+9nWXR2CHgQNilt /anQ== X-Gm-Message-State: APt69E2e2qes0bvcmsn6UkdgS0/gQBtqW7pIDaDctMmSeFdTPk2R3Acc RPO1QuAA8pQQNSMQwn4+iBIvxd/c2OFKhNJNrRmcBg== X-Google-Smtp-Source: ADUXVKJfaVH81UQ8qfidplqVf1q0TnAgExaJ4VrqblEKPlWKiGc8gV58r9JpFEktECnAgQC3Ue2R7lNs9jq1AdToDFY= X-Received: by 2002:a6b:d40c:: with SMTP id l12-v6mr2029062iog.37.1529078237844; Fri, 15 Jun 2018 08:57:17 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 2002:a4f:5945:0:0:0:0:0 with HTTP; Fri, 15 Jun 2018 08:57:17 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: <20180615154334.GA39777@www.zefox.net> References: <20180614175622.GC35161@www.zefox.net> <201806142110.w5ELAL0N046840@pdx.rh.CN85.dnsmgr.net> <20180615035225.GA37370@www.zefox.net> <20180615051527.GB37370@www.zefox.net> <834EA7A6-B567-436F-96B2-0C75FACA3FF9@yahoo.com> <20180615154334.GA39777@www.zefox.net> From: Warner Losh Date: Fri, 15 Jun 2018 09:57:17 -0600 X-Google-Sender-Auth: LAROaXZ-X6G4P2OsIxkqc7VlLV4 Message-ID: Subject: Re: GPT vs MBR for swap devices To: bob prohaska Cc: Mark Millard , "freebsd-arm@freebsd.org" , "Rodney W. Grimes" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jun 2018 15:57:19 -0000 On Fri, Jun 15, 2018 at 9:43 AM, bob prohaska wrote: > On Thu, Jun 14, 2018 at 11:37:48PM -0700, Mark Millard wrote: > > > > When I look at: > > > > # vmstat -c -w 5 > > procs memory page disks faults cpu > > r b w avm fre flt re pi po fr sr da0 ad0 in sy cs > us sy id > > 1 0 0 416M 224M 1647 1 0 0 1856 142 0 0 144 1791 1024 > 4 2 94 > > 0 0 0 416M 224M 9 0 0 0 0 1 0 0 4 85 116 > 0 0 100 > > 0 0 0 416M 224M 12 0 0 0 0 1 0 0 2 93 113 > 0 0 100 > > 0 0 0 416M 224M 9 0 0 0 2 1 1 0 4 64 121 > 0 0 100 > > . . . > > > > and "man vmstat" I do not see any column that is the swap space > > usage (nor any combination of columns to do such a calculation > > from). > > > > I do not expect that vmstat reports what you are likely/primarily > > looking for. > > > > An example is "avm" which for which the man page reports: > > > > . . . Note that the entire > > memory object's size is considered mapped even if only a > subset > > of the object's pages are currently mapped. This statistic > is > > not related to the active page queue which is used to track > real > > memory. > > > > The free list size ("fre") is not sufficient either. > > > > That seems astonishing. I imagined that among those columns _had_ to be > reads from and writes to the swap partitions. > > It looks as if > top -d 1000 | grep Swap > produces a running list of swap usage, but one must guess how many > times to iterate: > > bob@www:/usr/src % top -d 1000 | grep Swap > Swap: 3072M Total, 30M Used, 3041M Free > Swap: 3072M Total, 30M Used, 3041M Free > Swap: 3072M Total, 30M Used, 3041M Free > Swap: 3072M Total, 30M Used, 3041M Free > Swap: 3072M Total, 30M Used, 3041M Free > ....... > > Replacing the "1000" with "0" or "infinite" triggers > a syntax error. Is there a special parameter that makes top run till > it's killed, as in interactive mode? I didn't recognize any hint in the > man page. > > Thanks for reading! > Right, this is why I was suggesting gstat. It's a direct measure of the read/write performance of the device with some latency numbers. It will give the kind of data I'm looking for. vmstat won't, top won't. I don't care about used/free swap usage. I care about performance to the swap partition. That's what I'm suspecting in the USB thumb drive FTL. I don't care what the total swap usage is. I suspect that's irrelevant to the issue at hand since the OOM isn't triggering because we're filling swap, but more that it's due to not being able to get enough pages to the swap device fast enough to satisfy the memory shortages, triggering OOM. As for why it would affect the USB drive and not SD cards, I can only say that USB drives tend to be first to market with bigger capacities. This has traditionally made them less well tuned for anything other than large, long sequential reads or writes that aren't mixed. More so than even SD or uSD cards which tend to do better than USB drives at that workload. It's the FTL that's the issue, not the NAND itself. The FTL is the software that translates the log-style device you have to have for flash to work to the LBA style devices that people attach to systems. If it can't cope with a mixed workload, or needs to do too much garbage collection or read/modify/write operations due to it's poor quality / tuning, that will show up as long delays. USB flash also tends to suck more with BIO_DELETE than others, though the swapper doesn't do that, so that's one fewer wildcards we need to look at. gstat -Bd -I 10 -f > gstat-swap-data.dat would be how I'd recommend collecting it. This file may get kinda big depending how long it takes to trigger the weird state. I'm hoping that if you put this on a known good device, we'll power through the issues. We might not get perfect correlation with this, but the data should show all kinds of crazy before the system drives off the cliff if I'm right, so we don't need perfect data. There's some higher fidelity numbers we can get from the I/O scheduler with dynamic scheduling compiled in, but I don't think we'll need those. Warner From owner-freebsd-arm@freebsd.org Fri Jun 15 16:20: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 085C61011B22 for ; Fri, 15 Jun 2018 16:20:52 +0000 (UTC) (envelope-from rb743@hermes.cam.ac.uk) Received: from ppsw-32.csi.cam.ac.uk (ppsw-32.csi.cam.ac.uk [131.111.8.132]) (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 A178C75FEB for ; Fri, 15 Jun 2018 16:20:51 +0000 (UTC) (envelope-from rb743@hermes.cam.ac.uk) X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://help.uis.cam.ac.uk/email-scanner-virus Received: from sc1.bsdpad.com ([163.172.212.18]:37342) by ppsw-32.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.158]:587) with esmtpsa (LOGIN:rb743) (TLSv1:ECDHE-RSA-AES256-SHA:256) id 1fTrSz-000Ntq-2G (Exim 4.91) (return-path ); Fri, 15 Jun 2018 17:20:49 +0100 Date: Fri, 15 Jun 2018 17:10:23 +0100 From: Ruslan Bukin To: Mark Rutland Cc: Andrea Bolognani , freebsd-arm@freebsd.org, "Robert N. M. Watson" Subject: Re: virtio-net issues on aarch64 QEMU/KVM Message-ID: <20180615161023.GA34414@bsdpad.com> References: <1501165794.4378.8.camel@redhat.com> <20170804132950.GA9477@remoulade> <20180615115602.GA29619@bsdpad.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20180615115602.GA29619@bsdpad.com> User-Agent: Mutt/1.6.1 (2016-04-27) Sender: "R. Bukin" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jun 2018 16:20:52 -0000 I committed the fix: https://lists.freebsd.org/pipermail/svn-src-head/2018-June/114969.html Ruslan On Fri, Jun 15, 2018 at 12:56:02PM +0100, Ruslan Bukin wrote: > Hi Mark, > > Thanks for the stacktrace -- it was helpful. > > I found an issue: virtqueues have to be reinitialized any time we reset virtio controller, because QEMU now clears pointers to virtqueue. > > I have a patch: https://reviews.freebsd.org/D15821 > > This allows me to use QEMU's virtio-net-device just fine in FreeBSD/RISC-V. > > Thanks > > Ruslan > > On Fri, Aug 04, 2017 at 02:29:51PM +0100, Mark Rutland wrote: > > On Thu, Jul 27, 2017 at 04:29:54PM +0200, Andrea Bolognani wrote: > > > Hi all, > > > > Hi, > > > > > I'm trying 11.1-RELEASE on QEMU/KVM, and I'm having some > > > trouble with VirtIO networking. > > > > Likewise on both counts. > > > > As a (vaguely-related) heads-up, you will find that 11.1 will not work as an > > SMP KVM guest, as it doesn't enable SGIs for the boot CPU in the GIC > > distributor, leading to a lockup later in the boot process. I think Andrew > > Turner is currently looking at fixing that. > > > > > I've imported the official qcow2 image into libvirt by > > > running > > > > > >   # virt-install \ > > >     --name freebsd \ > > >     --arch aarch64 \ > > >     --machine virt \ > > >     --ram 2048 \ > > >     --vcpus 1 \ > > >     --accelerate \ > > >     --graphics none \ > > >     --features acpi=off \ > > >     --os-variant freebsd11.0 \ > > >     --import \ > > >     --disk path=/var/lib/libvirt/images/freebsd.qcow2,bus=virtio,address.type=virtio-mmio \ > > >     --network network=default,model=virtio,address.type=virtio-mmio > > > > > > and the system comes up succesfully; however, when I > > > try to activate the network interface by running > > > > > >   # dhclient vtnet0 > > > > > > the process seems to pretty much just sit there. ^C > > > doesn't help. Needless to say, if I configure vtnet0 to > > > be brought up at boot I never get to the prompt. > > > > I see the same thing with or without KVM using QEMU 2.9.0, upstream EDK2 > > (commit ef3d1df77bbd5227), and the same 11.1-RELEASE VM image. I'm not using > > libvirt, but I see issues when pasing QEMU: > > > > -device virtio-net-device,netdev=net0 netdev user,id=net0 > > > > At boot time, FreeBSD stops making progress after "Feeding entropy: .", and if > > I send SIGINFO with ^T, I see: > > > > load: 1.55 cmd: ifconfig 233 [runnable] 124.01r 0.00u 123.88s 100% 2768k > > > > I dumped a stacktrace using QEMU's gdbserver; it looks like FreeBSD is polling > > the virtio queue waiting for something: > > > > #0 0xffff000000170294 in VIRTIO_BUS_POLL (dev=0xfffffd00005ab900) at ./virtio_bus_if.h:159 > > #1 virtqueue_poll (vq=0xffff00004083e000, len=0x0) at /usr/src/sys/dev/virtio/virtqueue.c:573 > > #2 0xffff00000017707c in vtnet_ctrl_mac_cmd (sc=0xfffffd00004fa000, hwaddr=) at /usr/src/sys/dev/virtio/network/if_vtnet.c:3163 > > #3 vtnet_set_hwaddr (sc=0xfffffd00004fa000) at /usr/src/sys/dev/virtio/network/if_vtnet.c:3588 > > #4 0xffff000000176568 in vtnet_reinit (sc=0xfffffd00004fa000) at /usr/src/sys/dev/virtio/network/if_vtnet.c:3022 > > #5 vtnet_init_locked (sc=0xfffffd00004fa000) at /usr/src/sys/dev/virtio/network/if_vtnet.c:3069 > > #6 0xffff000000175ff8 in vtnet_ioctl (ifp=0xfffffd000058f000, cmd=, data=) at /usr/src/sys/dev/virtio/network/if_vtnet.c:1107 > > #7 0xffff000000373e60 in ifhwioctl (cmd=, ifp=, td=, data=) at /usr/src/sys/net/if.c:2456 > > #8 ifioctl (so=, cmd=2149607696, data=0xffff000054ae1888 "vtnet0", td=) at /usr/src/sys/net/if.c:2836 > > #9 0xffff0000002f3b14 in fo_ioctl (fp=, com=2149607696, active_cred=, td=, data=) at /usr/src/sys/sys/file.h:323 > > #10 kern_ioctl (td=0xfffffd0000a7f000, fd=3, com=2149607696, data=0xffff000054ae1888 "vtnet0") at /usr/src/sys/kern/sys_generic.c:836 > > #11 0xffff0000002f377c in sys_ioctl (td=0xfffffd0000a7f000, uap=0xffff000054ae1978) at /usr/src/sys/kern/sys_generic.c:745 > > #12 0xffff000000555408 in syscallenter (td=, sa=) at /usr/src/sys/arm64/arm64/../../kern/subr_syscall.c:135 > > #13 svc_handler (frame=, td=) at /usr/src/sys/arm64/arm64/trap.c:139 > > #14 do_el0_sync (td=0xfffffd0000a7f000, frame=) at /usr/src/sys/arm64/arm64/trap.c:366 > > > > ... unfortunately I'm not all that familiar with how virtio works, so I'm not > > sure which end is doing the wrong thing. > > > > Thanks, > > Mark. > > _______________________________________________ > > 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 Fri Jun 15 16:35: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 D0CCB1012C71 for ; Fri, 15 Jun 2018 16:35:23 +0000 (UTC) (envelope-from mark.rutland@arm.com) Received: from foss.arm.com (foss.arm.com [217.140.101.70]) by mx1.freebsd.org (Postfix) with ESMTP id 783F777100 for ; Fri, 15 Jun 2018 16:35:23 +0000 (UTC) (envelope-from mark.rutland@arm.com) Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.72.51.249]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 8EC6B1529; Fri, 15 Jun 2018 09:35:15 -0700 (PDT) Received: from lakrids.cambridge.arm.com (usa-sjc-imap-foss1.foss.arm.com [10.72.51.249]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id A3E603F25D; Fri, 15 Jun 2018 09:35:14 -0700 (PDT) Date: Fri, 15 Jun 2018 17:35:12 +0100 From: Mark Rutland To: Ruslan Bukin Cc: Andrea Bolognani , freebsd-arm@freebsd.org, "Robert N. M. Watson" Subject: Re: virtio-net issues on aarch64 QEMU/KVM Message-ID: <20180615163512.55o5ldr6dwwl5jdl@lakrids.cambridge.arm.com> References: <1501165794.4378.8.camel@redhat.com> <20170804132950.GA9477@remoulade> <20180615115602.GA29619@bsdpad.com> <20180615161023.GA34414@bsdpad.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180615161023.GA34414@bsdpad.com> User-Agent: NeoMutt/20170113 (1.7.2) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jun 2018 16:35:24 -0000 On Fri, Jun 15, 2018 at 05:10:23PM +0100, Ruslan Bukin wrote: > I committed the fix: > https://lists.freebsd.org/pipermail/svn-src-head/2018-June/114969.html Great; thanks for tackling this! Mark. From owner-freebsd-arm@freebsd.org Fri Jun 15 16:41:51 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 8713B1013156 for ; Fri, 15 Jun 2018 16:41: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 032F7776F7 for ; Fri, 15 Jun 2018 16:41:50 +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 w5FGg29b040050 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 15 Jun 2018 09:42: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 w5FGg22X040049; Fri, 15 Jun 2018 09:42:02 -0700 (PDT) (envelope-from fbsd) Date: Fri, 15 Jun 2018 09:42:02 -0700 From: bob prohaska To: Warner Losh Cc: Mark Millard , "freebsd-arm@freebsd.org" , "Rodney W. Grimes" , bob prohaska Subject: Re: GPT vs MBR for swap devices Message-ID: <20180615164202.GB39777@www.zefox.net> References: <20180614175622.GC35161@www.zefox.net> <201806142110.w5ELAL0N046840@pdx.rh.CN85.dnsmgr.net> <20180615035225.GA37370@www.zefox.net> <20180615051527.GB37370@www.zefox.net> <834EA7A6-B567-436F-96B2-0C75FACA3FF9@yahoo.com> <20180615154334.GA39777@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.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jun 2018 16:41:51 -0000 On Fri, Jun 15, 2018 at 09:57:17AM -0600, Warner Losh wrote: > gstat -Bd -I 10 -f > gstat-swap-data.dat > > would be how I'd recommend collecting it. This file may get kinda big > depending how long it takes to trigger the weird state. I'm hoping that if > you put this on a known good device, we'll power through the issues. We > might not get perfect correlation with this, but the data should show all > kinds of crazy before the system drives off the cliff if I'm right, so we > don't need perfect data. > Apologies, we spoke of gstat earlier. I lost the distinction between gstat and vmstat. In the case at hand the possible swap devices are /dev/da0b (this is the one causing trouble) /dev/mmcsd0s3b /dev/mmcsd0s3d what would the correct look like? Is there any indication why problems seen on the RPI3 do not seem apparent on an RPI2? A 2 GB USB flash swap partition seems to work successfully on the Pi2. Thanks very much! bob prohaska From owner-freebsd-arm@freebsd.org Fri Jun 15 17:21:04 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 27FB01014F8E for ; Fri, 15 Jun 2018 17:21:04 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x22e.google.com (mail-io0-x22e.google.com [IPv6:2607:f8b0:4001:c06::22e]) (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 AE283796F7 for ; Fri, 15 Jun 2018 17:21:03 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x22e.google.com with SMTP id e15-v6so11384762iog.1 for ; Fri, 15 Jun 2018 10:21:03 -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=Fry79kZj2bGUYFJ5vds/JZJ8hCxgAddBPPcuaO57+P0=; b=UKDhPax8ahmuZigkoP+ab1ebf5hG0xxXOMefKpFLkFC/rH55BGHTMrCShoHuQwo4Lb IPEvl0/w4RVIE6jS/zejBobTniesQJLgN0o+eh0ayHBQt3Rbc/V4bJLLE+CAttRLhW+6 8Vxctpp5zEGle5IzK3mclEn321oBd2IcHhc3k7osZHmNZwu7bDO/5NdRf4RzqGlfT0+v qAXwaQeIY5+HJJuFicUkrgZaILBts/TAXHCMIlLZR3+c/cZcdwdYzqRX0EUzZrr+5jnZ i2vpAnvqY8r8KUetevjzhJVhU+jYpcgFmSGCRc6VWl5BH5P1ESzdNo3hoNejYyZi/sOP BhAg== 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=Fry79kZj2bGUYFJ5vds/JZJ8hCxgAddBPPcuaO57+P0=; b=P6tY4mcGQaXi932UnTMUJhpR/HYD4TJXBggQRXP0hFSTLSNfSE1dAd1kpJSySa2/t9 JdibkjzKd02ztAMNA//EfFpEuPiBgk3EQwF781PYDCncoctYcELZiUSdwcLk71MjISAl tvFJBQeuoJE+QZnNsSEa7Bim6scwN12jUqPb+YKG8Kp3y7t5Z/n725vlIii4gm3mLg2p 2ev13JhoYDiODMEFIjLkB4Fuod/9kkyNDHmNMz1bLvzQKZELKRJdi0UWQM9oAmwWG1lm hByo1p5uOS7rT8kRH0JAr5SykrRr1HflsqSbiadsEigwIQ1Ai2o9HP8YEP8EyTZAgMOR YZdg== X-Gm-Message-State: APt69E3n7sKienx9ovkDQzk2R6PyyKZbOOrsIBq7z4AsINF43Azr02je HYYoYIP8bAC4AYfYwKN/gmbOk0ZkuEeJ7e0Ahe/rWw== X-Google-Smtp-Source: ADUXVKIKWz1o8ouUPipLZao2qTPM2Z9MDwtoKDEQe2iRVah8jWBFxcbXSrsafdD+T0dtFnVszoru+382tWANx5a/g4o= X-Received: by 2002:a6b:29c4:: with SMTP id p187-v6mr2189625iop.299.1529083263010; Fri, 15 Jun 2018 10:21:03 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 2002:a4f:5945:0:0:0:0:0 with HTTP; Fri, 15 Jun 2018 10:21:01 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: <20180615164202.GB39777@www.zefox.net> References: <20180614175622.GC35161@www.zefox.net> <201806142110.w5ELAL0N046840@pdx.rh.CN85.dnsmgr.net> <20180615035225.GA37370@www.zefox.net> <20180615051527.GB37370@www.zefox.net> <834EA7A6-B567-436F-96B2-0C75FACA3FF9@yahoo.com> <20180615154334.GA39777@www.zefox.net> <20180615164202.GB39777@www.zefox.net> From: Warner Losh Date: Fri, 15 Jun 2018 11:21:01 -0600 X-Google-Sender-Auth: uXS6ZYmB9h0ScNfrfQLgu17Ehtc Message-ID: Subject: Re: GPT vs MBR for swap devices To: bob prohaska Cc: Mark Millard , "freebsd-arm@freebsd.org" , "Rodney W. Grimes" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jun 2018 17:21:04 -0000 On Fri, Jun 15, 2018 at 10:42 AM, bob prohaska wrote: > On Fri, Jun 15, 2018 at 09:57:17AM -0600, Warner Losh wrote: > > > gstat -Bd -I 10 -f > > gstat-swap-data.dat > > > > would be how I'd recommend collecting it. This file may get kinda big > > depending how long it takes to trigger the weird state. I'm hoping that > if > > you put this on a known good device, we'll power through the issues. We > > might not get perfect correlation with this, but the data should show all > > kinds of crazy before the system drives off the cliff if I'm right, so we > > don't need perfect data. > > > > Apologies, we spoke of gstat earlier. I lost the distinction between > gstat and vmstat. In the case at hand the possible swap devices are > > /dev/da0b (this is the one causing trouble) > /dev/mmcsd0s3b > /dev/mmcsd0s3d > > > what would the correct look like? > I'd just use -f '^da0b$' for each of the devices. > Is there any indication why problems seen on the RPI3 do not seem > apparent on an RPI2? A 2 GB USB flash swap partition seems to work > successfully on the Pi2. > Interesting. The only thing I can think of is different OOM tuning levels. But if anything, I'd expect more trouble on the RPi2 than the RPi3. So that might also point to a difference in USB and/or VM things. It would be interesting to see if we see a significant difference in the graphs between the two for the same physical drive. I'd have expected, like you, that this would be reproducible between the two. Warner From owner-freebsd-arm@freebsd.org Fri Jun 15 17:51: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 46DF3101644C for ; Fri, 15 Jun 2018 17:51:49 +0000 (UTC) (envelope-from jim@netgate.com) Received: from mail-oi0-x244.google.com (mail-oi0-x244.google.com [IPv6:2607:f8b0:4003:c06::244]) (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 D21697B2E1 for ; Fri, 15 Jun 2018 17:51:48 +0000 (UTC) (envelope-from jim@netgate.com) Received: by mail-oi0-x244.google.com with SMTP id d5-v6so9530871oib.5 for ; Fri, 15 Jun 2018 10:51:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=netgate.com; s=google; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=EfN/GSZjpZtF30HdJufVDuBMf/aSettg4iDKO2w9OfY=; b=HrRyRvrWxHbXyfgKTPqtZ0+Nqtq+HZqPvTfYVretnKGkjSzodp5jlOuCEVrYNVpJ17 w2taTeb31hwf7PmlqMosU3aB/VxCZKeOvUTMMz5Zxy0uBgicjiXrTRU8hHcXocQg7uW6 V284VxXzzfJcjT4PL2j6StmIjOmz6mXKsEuCU= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=EfN/GSZjpZtF30HdJufVDuBMf/aSettg4iDKO2w9OfY=; b=PZ16lJ9Nd4rLLIgJZ2xF7NhhBjZc8Yrz5bZT87xTNPy8d6VgJelM/b2yuZD0fIgqH+ kt4vD70njujR5BhDPPyPUJPbcPbyqpKY3HNcJn5AeSoFmOJxJ++VLBz+0A/px8QmzHdG lQ5JX+kxExsBqEzLRVWpBvMrxj81I7zZabWiL7vtklEYoysOQU5N+I98cLZ6cwGoJVUi wgJ5SYZAA/mTeKsDSH33LLA3Q707p5jN5CFSFvfOWp8r8wkc/LQ/cw+qJ0QoEeOJDaH0 u1n06F+qhl3hrJ74DSQ1vlpTmLpRhWcLT5HKssn4qKUg1JpQxLMwiG26zA7ir4CY+2XC /zTQ== X-Gm-Message-State: APt69E22BHO3L79c3XkRK4QiSl8IqmGjaCLlI4TLSsNsfNhvYaXpkQsJ UL5CykneFjilwJmt5mpOugBe4Q== X-Google-Smtp-Source: ADUXVKIelc0J/nMd9Z+9Kv++Dsl0+jPY1uzs7YdcwvD+0NwySZ6XO9wQHrJLREUOiDrm21LJ7jJwDw== X-Received: by 2002:aca:d4c1:: with SMTP id l184-v6mr1538793oig.325.1529085107912; Fri, 15 Jun 2018 10:51:47 -0700 (PDT) Received: from [10.10.40.141] ([66.196.5.190]) by smtp.gmail.com with ESMTPSA id k141-v6sm7007128oih.42.2018.06.15.10.51.46 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 15 Jun 2018 10:51:46 -0700 (PDT) From: Jim Thompson Message-Id: Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\)) Subject: Re: ARMv8 development board with GICv3 Date: Fri, 15 Jun 2018 12:51:45 -0500 In-Reply-To: Cc: Michael Dexter , freebsd-arm@freebsd.org, "Rodney W. Grimes" , freebsd-virtualization@freebsd.org To: Alexandru Elisei References: <201806130737.w5D7bHxX038233@pdx.rh.CN85.dnsmgr.net> <91705d37-7a15-afcd-cadd-c14c6a43eb84@callfortesting.org> X-Mailer: Apple Mail (2.3445.6.18) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jun 2018 17:51:49 -0000 > On Jun 15, 2018, at 7:40 AM, Alexandru Elisei = wrote: >=20 > Thank you all for your suggestions. >=20 > I was considering the espressobin board [1], I only need a disk to > boot from and a network controller to connect to the board. >=20 > It uses a Marvell 3720 SoC (model 88F3720) which according to the > specs [2] has all exception levels and it uses a GIC-500 interrupt > controller which implementes the GICv3 specification [3]. >=20 > The board is supported under linux [4], I was wondering if anyone can > tell me how well it is supported under FreeBSD. https://gist.github.com/gonzopancho/760ab9ecee9dfbc1b6033e48647a4b48 = Note: we haven=E2=80=99t upstreamed everything. Yet. macchiato.bin needs interrupts and NIC drivers, and seems a better = target for bhyve machiatto.bin 4C A72 @ 1.6GHz/2.0GHz, 16GB DDR4 espresso.bin 2C A53 @1.0GHz and1/2GB DDR3 (*) Jim (*) Very new espresso.bin has 1.2GHz SoC and DDR4, and you can plug a = SATA drive in, including power. https://i.imgur.com/5fc2vv0.jpg From owner-freebsd-arm@freebsd.org Fri Jun 15 18:40: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 C8FB710178C1; Fri, 15 Jun 2018 18:40:15 +0000 (UTC) (envelope-from alexandru.elisei@gmail.com) Received: from mail-qt0-x244.google.com (mail-qt0-x244.google.com [IPv6:2607:f8b0:400d:c0d::244]) (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 65BDE7D03B; Fri, 15 Jun 2018 18:40:15 +0000 (UTC) (envelope-from alexandru.elisei@gmail.com) Received: by mail-qt0-x244.google.com with SMTP id a18-v6so9946044qtj.4; Fri, 15 Jun 2018 11:40:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=7U/w1hdN6iRWiz0KQ1jqKrwSqG7viklJOiEIRZXcVLU=; b=fRW0KF10PwphvwIKaUutqyedIUWGA9ykRrzQTZ0w9DWC/R1e++ZBKOFNFP4RXvymew BymlvcI/Mc/JeT44GfItD60NeU1UyLRbheJ9QMfyweO3RPXafWkcLoU8jbcbbGSoMShU xDfeIGbpAgcwcYtVCTRUVb80AmC0HC676oZkZmhcdwoFwuG9T6Ey69sfmNDUYYvZLWf8 laU+alU/Ukxdm5byZHGVScp2LqX7cCsoHuwlNEn2OS4Vs39gboZ/n8kdrvcCiFfJd9XC LZQJ1jV8BXzyA4P/+qUXpu25nzPoJaleCxZVxXvCsD4aMuyC6bevIbmFeXy6zBT0fCw7 u+Zw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=7U/w1hdN6iRWiz0KQ1jqKrwSqG7viklJOiEIRZXcVLU=; b=h/3cOBi+/Gadf00LRnKlTxysF2xPykPrKFIt4R71IxoMpTtbAl9SST3cDYeUgVGk7Z mdJ0bfrZ5otHvslrt/3436OMZR4+X6O9iQ+gEjeiQS9x8M+MbM67CUp1XQGVpoCGRQIc Jy/PaVlqqsIdVsttuMdoth0N3drjAPerqcYW8fsUgMs5XN7Gt4h2BxJQ6TuLZ8G1rXsI Tx1elUGGO2Xyf6SiAHACDhpJCYb9RRVwnb95INL5QVIng3bTMeshQcAcLZ0/wrb5YSmW ttnBuh60JJbfcQQZbpPZCaqK98o61BDXsOBO/mjoqmRRVw5HF2LGHQN+KtpVuc6IGnUn qAjw== X-Gm-Message-State: APt69E0anaEHuF4Fp7KnYyS7X0/j/7w/9h7i2mT4oEwHepmRew+sa1B2 MPKH4uhz+yh03pqwu5H0LNGfu3cw9l7f9oI61E0= X-Google-Smtp-Source: ADUXVKJ6qAK6RppMQacqmeWY46w55ke9KEtdXCI37KtmpQ6LiljaGjqCypd3ZcOfbsUh9W99DB1+bkDMcMtrPF9lz9E= X-Received: by 2002:ac8:3fb2:: with SMTP id d47-v6mr2469464qtk.401.1529088014875; Fri, 15 Jun 2018 11:40:14 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:aed:2be7:0:0:0:0:0 with HTTP; Fri, 15 Jun 2018 11:40:14 -0700 (PDT) In-Reply-To: References: <201806130737.w5D7bHxX038233@pdx.rh.CN85.dnsmgr.net> <91705d37-7a15-afcd-cadd-c14c6a43eb84@callfortesting.org> From: Alexandru Elisei Date: Fri, 15 Jun 2018 21:40:14 +0300 Message-ID: Subject: Re: ARMv8 development board with GICv3 To: Jim Thompson Cc: Michael Dexter , freebsd-arm@freebsd.org, "Rodney W. Grimes" , freebsd-virtualization@freebsd.org, Alexandru Elisei Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jun 2018 18:40:16 -0000 On Fri, Jun 15, 2018 at 8:51 PM, Jim Thompson wrote: > > > https://gist.github.com/gonzopancho/760ab9ecee9dfbc1b6033e48647a4b48 > > Note: we haven=E2=80=99t upstreamed everything. Yet. Is FreeBSD bootable on the board and the NIC working? > macchiato.bin needs interrupts and NIC drivers, and seems a better target > for bhyve > > machiatto.bin 4C A72 @ 1.6GHz/2.0GHz, 16GB DDR4 > > espresso.bin 2C A53 @1.0GHz and1/2GB DDR3 (*) > > Jim > > (*) Very new espresso.bin has 1.2GHz SoC and DDR4, and you can plug a SAT= A > drive in, including power. > https://i.imgur.com/5fc2vv0.jpg > From owner-freebsd-arm@freebsd.org Fri Jun 15 20:19:07 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 E55FE101B0BB for ; Fri, 15 Jun 2018 20:19:06 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic309-21.consmr.mail.gq1.yahoo.com (sonic309-21.consmr.mail.gq1.yahoo.com [98.137.65.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 467C58188B for ; Fri, 15 Jun 2018 20:19:06 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: AP3jB7IVM1lWr.GJGGyoGnuyrdYWKc4JO0MWOhJdWVJv_uPA_UuQ1e8lDiyqvv_ 36wy0g8H0vuwz_M0z7rsIzOIZV2VPAXCJdmffe_STu_ll4dMamCIe59yqLRyk_sYLx06uwla499V QPNLH_2W2G4D6VwrGXceVc9wDxTaXCsrcarow.wrI8ghWaDqD1TDdpoe3dZrvW11AbrbViA63iiX 4Os3yCeWBhEEcywVI07kxqzw1EuZ64V.YWxAkvd3o87MCEyr12y8UDAc7Ke22tXk.dvugg0dK1OF UWWSISNYTg82FRGfWG9c8CPz8sC_PtR3XYBTtADr4koYN2kzu8AImFfBZVXKTw1s6Te4af3fa4Vx GZjBMFZ1eRNxnSoJDkA_aTtPr4_po9tKSfuMBUeqhBe.tCrWLTV6mWVXKPLhwnw4TFlzI0IW.8O5 xPTjc23C1nkUnGPdc3rQKDvaNP1PJganpmF8uIMNwCwSQN6c5MyMzWwq3k_StQQhdJGkrZf7qz1y zmy0ctFOyfA37UYFOLCX.0MFIUqKsGKfeUPttMQm6KvpkDZYPEjfuqCBZtE4tA_8f1JCKKGE0FoZ waazJ.UINHl1ijhcsMiEh_u85.Fvq6Fa5ul286QrlDYkPLJinms5_ON0cvGz2ZaDJHu3FVMBPq6C 3Z6JilpFQZf1Idx8M3WokBNOV.xuEABF.BXrKTO_96m8BWtH4eWQroCSWKupyEsDeRGaKq3BM5C. _dBoPjdMkw9eTpeqQohwA4BDH_pOiw3cB5fcEmcwF95NS_C_TBs73KoxPc7Pfy0t98arI2_RpGdU ij5w7R5EDysFpjjsZhJ89XwIPbnHEuXGrkWcKdAzFp5ii.YQii11lshlJhSC8wRJi9IOrL9uUBNw YpTyU.egBxuWLq0uJzEf1_cNq6m7w0Flp08.tb3CokJgdKovZcqIuo9CGwGnQT4wa2JN3ioBpBxB ZpuHDTAY- Received: from sonic.gate.mail.ne1.yahoo.com by sonic309.consmr.mail.gq1.yahoo.com with HTTP; Fri, 15 Jun 2018 20:18:59 +0000 Received: from ip70-189-131-151.lv.lv.cox.net (EHLO [192.168.0.109]) ([70.189.131.151]) by smtp423.mail.gq1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID a0d40ca6ab7332edf6b7fa58ea166bc0; Fri, 15 Jun 2018 20:18:58 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\)) Subject: Re: GPT vs MBR for swap devices From: Mark Millard In-Reply-To: <20180615164202.GB39777@www.zefox.net> Date: Fri, 15 Jun 2018 13:18:56 -0700 Cc: Warner Losh , "freebsd-arm@freebsd.org" , "Rodney W. Grimes" Content-Transfer-Encoding: 7bit Message-Id: <91986169-F9AE-45AA-BA34-332BB89C5439@yahoo.com> References: <20180614175622.GC35161@www.zefox.net> <201806142110.w5ELAL0N046840@pdx.rh.CN85.dnsmgr.net> <20180615035225.GA37370@www.zefox.net> <20180615051527.GB37370@www.zefox.net> <834EA7A6-B567-436F-96B2-0C75FACA3FF9@yahoo.com> <20180615154334.GA39777@www.zefox.net> <20180615164202.GB39777@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.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jun 2018 20:19:07 -0000 On 2018-Jun-15, at 9:42 AM, bob prohaska wrote: > On Fri, Jun 15, 2018 at 09:57:17AM -0600, Warner Losh wrote: > >> gstat -Bd -I 10 -f > gstat-swap-data.dat >> >> would be how I'd recommend collecting it. This file may get kinda big >> depending how long it takes to trigger the weird state. I'm hoping that if >> you put this on a known good device, we'll power through the issues. We >> might not get perfect correlation with this, but the data should show all >> kinds of crazy before the system drives off the cliff if I'm right, so we >> don't need perfect data. >> > > Apologies, we spoke of gstat earlier. I lost the distinction between > gstat and vmstat. In the case at hand the possible swap devices are > > /dev/da0b (this is the one causing trouble) > /dev/mmcsd0s3b > /dev/mmcsd0s3d > > > what would the correct look like? > > Is there any indication why problems seen on the RPI3 do not seem > apparent on an RPI2? A 2 GB USB flash swap partition seems to work > successfully on the Pi2. gstat and top/swapinfo are good for different things: gstat: for various I/O rates and such to the swap partition(s) top: for samples of how much swap space is in use (total). swapinfo: per swap partition swap space usage and the total. (swapinfo requires use of separate looping/sleeping for it to repeatedly report.) (swapinfo is a specialization/limitation of pstat.) There may be times when you want information about both aspects (I/O rates and usage-size figures from similar time frames). === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-arm@freebsd.org Fri Jun 15 23:36: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 765671020F94 for ; Fri, 15 Jun 2018 23:36:21 +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 C1F626883D for ; Fri, 15 Jun 2018 23:36:20 +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 w5FNaQhF041654 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 15 Jun 2018 16:36:27 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w5FNaP0P041653; Fri, 15 Jun 2018 16:36:25 -0700 (PDT) (envelope-from fbsd) Date: Fri, 15 Jun 2018 16:36:25 -0700 From: bob prohaska To: Warner Losh Cc: Mark Millard , "freebsd-arm@freebsd.org" , "Rodney W. Grimes" , bob prohaska Subject: Re: GPT vs MBR for swap devices Message-ID: <20180615233625.GA41147@www.zefox.net> References: <20180614175622.GC35161@www.zefox.net> <201806142110.w5ELAL0N046840@pdx.rh.CN85.dnsmgr.net> <20180615035225.GA37370@www.zefox.net> <20180615051527.GB37370@www.zefox.net> <834EA7A6-B567-436F-96B2-0C75FACA3FF9@yahoo.com> <20180615154334.GA39777@www.zefox.net> <20180615164202.GB39777@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.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jun 2018 23:36:21 -0000 On Fri, Jun 15, 2018 at 11:21:01AM -0600, Warner Losh wrote: > On Fri, Jun 15, 2018 at 10:42 AM, bob prohaska wrote: > > > On Fri, Jun 15, 2018 at 09:57:17AM -0600, Warner Losh wrote: > > > > > gstat -Bd -I 10 -f > > > gstat-swap-data.dat > > > Could a longer interval, maybe one or ten seconds, and perhaps the -a flag to reduce file size produce useful results? Given the way gstat output is formatted it does not look easy to search, except in small amounts by eye. > > > would be how I'd recommend collecting it. This file may get kinda big > > > depending how long it takes to trigger the weird state. I'm hoping that > > if > > > you put this on a known good device, we'll power through the issues. We > > > might not get perfect correlation with this, but the data should show all > > > kinds of crazy before the system drives off the cliff if I'm right, so we > > > don't need perfect data. > > > > > > > Apologies, we spoke of gstat earlier. I lost the distinction between > > gstat and vmstat. In the case at hand the possible swap devices are > > > > /dev/da0b (this is the one causing trouble) > > /dev/mmcsd0s3b > > /dev/mmcsd0s3d > > > > > > what would the correct look like? > > > > I'd just use -f '^da0b$' for each of the devices. > So, ignore the SD flash for now? > > > Is there any indication why problems seen on the RPI3 do not seem > > apparent on an RPI2? A 2 GB USB flash swap partition seems to work > > successfully on the Pi2. > > > > Interesting. The only thing I can think of is different OOM tuning levels. > But if anything, I'd expect more trouble on the RPi2 than the RPi3. So that > might also point to a difference in USB and/or VM things. It would be > interesting to see if we see a significant difference in the graphs between > the two for the same physical drive. I'd have expected, like you, that this > would be reproducible between the two. > The Pi2 vs Pi3 comparison is less fair than I indicated; the Pi2 is running 11.2-PRERELEASE FreeBSD 11.2-PRERELEASE #0 r335072, while the Pi3 is running 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r334939. Both Pi2 and Pi3 are using 64 GB Sandisk Extreme USB flash drives, but the unit on the Pi3 is about a year newer. I'd expect that to help, rather than hurt, but.... I'll try logging gstat output on the Pi2 as-is during a clean-start buildworld and see what happens. Thanks for all your help! bob prohaska From owner-freebsd-arm@freebsd.org Sat Jun 16 09:31: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 2BCEE10102BA for ; Sat, 16 Jun 2018 09:31:40 +0000 (UTC) (envelope-from mw@semihalf.com) Received: from mail-io0-x241.google.com (mail-io0-x241.google.com [IPv6:2607:f8b0:4001:c06::241]) (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 BE32D7B630 for ; Sat, 16 Jun 2018 09:31:39 +0000 (UTC) (envelope-from mw@semihalf.com) Received: by mail-io0-x241.google.com with SMTP id d22-v6so12793562iof.13 for ; Sat, 16 Jun 2018 02:31:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=semihalf-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=ziT5qjswfF/sCh66KgRXpXIuZ5okEZRnfX4dg978C7A=; b=1qvn2rMWuAvGk3ylAINop95GXi9Jlr96rl81LsA1b74zb6MwnKqsMnhqxIwY3VisOh YZ30QdMMNIGCrFarq0Iy4beeNl5+oSiL3QEYv41dIUB4waGX0RBppilBOIRcV8XNvu5o MdZ8Dbxuke/q95VALvTaWQ+KDEVoZmxXBHIDkYEjUobq3RIFelYELcQyINdKSiwBqn2d 2pUnVXRFJwHng3Vd1lOpRi9v/PCKMeErAqrKO1xcIo9Pp/gD3QUoyuw6/nC52sfMfUjj WbN0yQAg1nxCj5hEY/IZ9DDvaLJXEl7H+iBYIIASTL9ZUYSNIsic1HdlpgbV/KM2NC4U tBow== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=ziT5qjswfF/sCh66KgRXpXIuZ5okEZRnfX4dg978C7A=; b=Kgxg1xWGwNBElER34ym2K12HQZhQrb4is6Ef7wYFM+eQbrufPiyO6WxPv86KSlZ2Se 3aYLCJFOOMqe5RArKCHAsbenWb3EahNETxlXSty9H2rJc6BwSF1MqTdA5SX0WHXP6GpK oscq5r06TJu9jN/3BdILkmiwxaJRVRSib3ly7P3+I8d6zwkBwrXGZ3/6wVcHDMC/XLEP aHSrViaDaxxwqx8vm2x7uWqJHHlF301uaHMNH1VYEkboZhEJiiwXjGdScw2Cdb+BZ4PB u//qMJ+v1SrSTgIk9tMiTMZuXi0LKHIfl1e+h5JAHHhVrjRGo8N6qSp86Fn/D5YcmDkA iteA== X-Gm-Message-State: APt69E3mB2bStrYLb344bzdWlgc8YbUg5I1yid22BjbXUDYH43L5Fz5d 9hTQt6hmX8n95cuzkce9hHrgLOc7xzlu19thYX9izq15 X-Google-Smtp-Source: ADUXVKJgcZrEWcRM/Lox9H42PZZqB7gjXdIVmzlqesIzn9aP0pxLKjTwiy97OeNb89+bsykDt7Cps69iiTGYQ881a6c= X-Received: by 2002:a6b:8e96:: with SMTP id q144-v6mr4165077iod.248.1529141499142; Sat, 16 Jun 2018 02:31:39 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a6b:c6cc:0:0:0:0:0 with HTTP; Sat, 16 Jun 2018 02:31:38 -0700 (PDT) In-Reply-To: References: <201806130737.w5D7bHxX038233@pdx.rh.CN85.dnsmgr.net> <91705d37-7a15-afcd-cadd-c14c6a43eb84@callfortesting.org> From: Marcin Wojtas Date: Sat, 16 Jun 2018 11:31:38 +0200 Message-ID: Subject: Re: ARMv8 development board with GICv3 To: Alexandru Elisei Cc: Jim Thompson , freebsd-arm , "Rodney W. Grimes" , freebsd-virtualization@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Jun 2018 09:31:40 -0000 2018-06-15 20:40 GMT+02:00 Alexandru Elisei : > > On Fri, Jun 15, 2018 at 8:51 PM, Jim Thompson wrote: > > > > > > https://gist.github.com/gonzopancho/760ab9ecee9dfbc1b6033e48647a4b48 > > > > Note: we haven=E2=80=99t upstreamed everything. Yet. > > Is FreeBSD bootable on the board and the NIC working? In 2017 I pushed patches and the board was booting with the network, USB and SATA. However I know that loos from Netgate has improved the overall support - as a result we can see the log Jim provided. > > > macchiato.bin needs interrupts and NIC drivers, and seems a better targ= et > > for bhyve > > > > machiatto.bin 4C A72 @ 1.6GHz/2.0GHz, 16GB DDR4 > > > > espresso.bin 2C A53 @1.0GHz and1/2GB DDR3 (*) Just one note - macchiato.bin is using GICv2m and espresso - GICv3. Best regards, Marcin > > > > Jim > > > > (*) Very new espresso.bin has 1.2GHz SoC and DDR4, and you can plug a S= ATA > > drive in, including power. > > https://i.imgur.com/5fc2vv0.jpg From owner-freebsd-arm@freebsd.org Sat Jun 16 19:12: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 E204A101F958 for ; Sat, 16 Jun 2018 19:12:21 +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 458BD6C17A for ; Sat, 16 Jun 2018 19:12:21 +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 w5GJCWmx045677 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 16 Jun 2018 12:12:33 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w5GJCVuI045676; Sat, 16 Jun 2018 12:12:31 -0700 (PDT) (envelope-from fbsd) Date: Sat, 16 Jun 2018 12:12:31 -0700 From: bob prohaska To: Warner Losh Cc: Mark Millard , "freebsd-arm@freebsd.org" , "Rodney W. Grimes" , bob prohaska Subject: Re: GPT vs MBR for swap devices Message-ID: <20180616191231.GA45514@www.zefox.net> References: <20180614175622.GC35161@www.zefox.net> <201806142110.w5ELAL0N046840@pdx.rh.CN85.dnsmgr.net> <20180615035225.GA37370@www.zefox.net> <20180615051527.GB37370@www.zefox.net> <834EA7A6-B567-436F-96B2-0C75FACA3FF9@yahoo.com> <20180615154334.GA39777@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.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Jun 2018 19:12:22 -0000 On Fri, Jun 15, 2018 at 09:57:17AM -0600, Warner Losh wrote: > > Right, this is why I was suggesting gstat. It's a direct measure of the > read/write performance of the device with some latency numbers. It will > give the kind of data I'm looking for. Here is a first cut at recording gstat data on r334939 during two -j4 buildworld sessions. The interesting one uses 2 GB of SD flash swap on the boot device and 1 GB of USB flash on the thumb drive hosting the outboard file systems. The readme and log file are at http://www.zefox.net/~fbsd/rpi3/swaptests/ The logging command was gstat -aBd -I 10s > 2gbsdflash_1gbusbflash.log It looks as if something strange happens when swap is placed on two separate interfaces. In the mixed USB/SD case, it appears that the SD flash swap is ignored and the USB flash swap is never very busy (eyeball scan only). The failed buildworld ended at the bootstrap tools stage, swap was on da0b and mmcsd0s3d. It's already known that having all swap on SD flash in two partitions or all swap on USB mechanical disk in one partition works. There is also an RPI2 case with all swap on USB flash in one partition at http://www.zefox.net/~fbsd/rpi2/swaptests/ in case it's of interest. At this stage I don't know what to try next, suggestions are welcome. It would be easy to sample at 1 second rather than ten. Cutting SD flash swap down to 1 or 2 GB is also easy. Likewise, reducing to 1 GB USB flash swap is easy. I have a powered hub so USB things can be added, but that makes the setup more complicated rather than less. Thanks very much for reading, bob prohaska From owner-freebsd-arm@freebsd.org Sat Jun 16 23:13: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 3F0771001A09 for ; Sat, 16 Jun 2018 23:13:26 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic310-15.consmr.mail.bf2.yahoo.com (sonic310-15.consmr.mail.bf2.yahoo.com [74.6.135.125]) (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 C31D873212 for ; Sat, 16 Jun 2018 23:13:25 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: 9e4QaUgVM1kyEsQ6MjMaDdjBNJwbUxTsC_JsTHss1t6RmJsMvNkDWYeCVcdIlhO plSazYFZzEiUbf74rqD6mNMpTjZ6vfZETtaW8wBQzAAB7MW41rgFBx8kkjXKIPuV3_ra3eTwAQ2n weMC_h6GoitJTfFFvbh7wgEiDseu.qRk2g4nvoECgTt3gYOq_BhzQvVr9U2yd.1AFGy6rres2Hzy eoag7uKWYI4vSla6Hod0wUgd7vlr7zW2N8oWRdcm8cbnc0ukLw4SRv3baCq_Va1nSXXCfq0uRSuY JgqAV4hTJAW0c1YRsbHNwN4ooo0mO_zwtyX.CL03C2hb.t.at9RJOQkYIn880ix.nQ3oO8giX1vD 6W0JkioODr6x5WHYEaETefs5ilS0As5vgc7LHSrkEtObcXFCYAetoCGlogaSppy_WhDaU2lxukNI aTdO_KFYQJ6SYn72u5eg34fH5TPEC3y077HKJyN1pE9K8wXOM74ms7bivh4drpU.bK31_mSA.2gd R52H7Dic068iqwFsfzC8su_Xv7UT.Ibplns6uLYum0Cq.AApbwJT9IHs9ACApnHk2NtbQd8BjAiY RpyRtFk00aQMnC_m3zSMl_9XJSGvOW.9UsTknTT6l1lS.VeCjL.gaxYJHTfYPmVRjxyB4WorIYbK CBywO5h_iTQR3j7TBs8KufxvRHEZFAoqfBuDdEIscjwwJlVgtFt52UgQAYKzXapN9OqVTvC6go3m 2as4AVBlsAK8zBpYWlJxwxuYs9zNKPmbeOhllpu1.ufpmFCWLGslmGoRgEM6.c2uKjLq1DgoMW6v VmU6Axqz.aXFb95qjNpgSTZdgtvzgGcQT5frziF8pX69TpAiCBW_BhdsgsjCyLj9Aw3UNnaAZwKA TdK0aszgzRQs2X_jM2PfoDjWBgFaSbvLO4MAJoXr8BFoi0XQLJNwLpBgAJFlzviF._LbHpomOs2E J_aLjaODp Received: from sonic.gate.mail.ne1.yahoo.com by sonic310.consmr.mail.bf2.yahoo.com with HTTP; Sat, 16 Jun 2018 23:13:19 +0000 Received: from ip70-189-131-151.lv.lv.cox.net (EHLO [192.168.0.105]) ([70.189.131.151]) by smtp429.mail.bf1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 4c74ae9bc7dbb008bf84d29a04978926; Sat, 16 Jun 2018 23:03:08 +0000 (UTC) From: Mark Millard 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: Re: GPT vs MBR for swap devices Message-Id: <7AB401DF-7AE4-409B-8263-719FD3D889E5@yahoo.com> Date: Sat, 16 Jun 2018 16:03:06 -0700 To: bob prohaska , freebsd-arm@freebsd.org X-Mailer: Apple Mail (2.3445.8.2) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Jun 2018 23:13:26 -0000 bob prohaska fbsd at www.zefox.net wrote on Sat Jun 16 19:12:22 UTC 2018 (some by reference to other web pages, which is what I quote from here) : > Presently, the divided swap layout fails during -j4 buildworld with > "out of swap" kills during the more frantic portions of buildworld. > > When all swap is placed on a single 3 GB USB mechanical disk partition > the "out of swap" errors go away. Similarly, when swap is placed entirely > on the microSD card in two partitions, one the original 1 GB partition > plus a second 2 GB partition, the "out of swap" errors dissapear. Since the "multiple swap partitions across multiple devices" context (my description) is what has problems, it would be interesting to see swapinfo information from around the time frame of the failures: how much is used vs. available on each swap partition? Is only one being (significantly) used? The small one (1 GiByte)? A related, additional example to try? . . . Since you report needing around 1.2 GiByte of swap, what happens if you have a split but both devices have, say, 1.5 GiByte of swap space for the partition used? If I read right, you could shrink the 2GiByte microSD card partition and the 3 GiByte USB mechanical disk partition and then use that pair as a test. (This also avoids the message about having too much swap. Also, I'm avoiding having significant size differences between the partitions used.) Technically, without the split, either partition should be sufficient without the other involved. In such a context, does the split still fail? Or does it only fail when one partition is stoo small to be sufficient by itself? These suggestions are going a different direction than the I/O rate investigation but also having I/O rate information would not hurt. But I/O rate information can not substitute for the swapinfo output here. Nor can top cover what I'd be looking for: per partition usage figures are required, not just grand total swap-space usage. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar)