From owner-freebsd-arm@freebsd.org Sun Oct 27 04:35:32 2019 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id DBEFE15D7D5 for ; Sun, 27 Oct 2019 04:35:32 +0000 (UTC) (envelope-from kistapas42@gmail.com) Received: from mail-yb1-xb49.google.com (mail-yb1-xb49.google.com [IPv6:2607:f8b0:4864:20::b49]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4714ll4S7dz4JLJ for ; Sun, 27 Oct 2019 04:35:31 +0000 (UTC) (envelope-from kistapas42@gmail.com) Received: by mail-yb1-xb49.google.com with SMTP id y6so5493454ybm.12 for ; Sat, 26 Oct 2019 21:35:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:reply-to:sender:message-id:date:subject:from:to; bh=6DB3hYsdkXOAtWLqdnM/Yq0+PMXtzSJ84M8V9hDhtLo=; b=hOghmZQMFjL8YJwLQVN+GwHWolJrRIH6G0XJal4TstZq+5P/QWPVMAjQk0n+0cmbXm slQV433T8rtR+pawfzpiMHYw9JJfNb4Kxtv3C8lcMH2vbHo3kCdTDaj9msyB9eIru5qy Kd9AJzPnqCHYmZCDD6R1Di2cdoVEtzBRNyJ9z88Yumxuhw2jYZymV/eYKDMcPywHQaxv 4crXrLOSXJarE911GEzhxegDpLO/nN/aOJiPPvc4oivE8y6/fH/1mc6/YjafDlcZXbi+ h46tYzWlKvqosAngYY+9bKS7aztuDfXtJQydVO9IY82uKgJPeSuwgKhFHNg7QvxOXaIN DH2w== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:reply-to:sender:message-id:date:subject:from:to; bh=6DB3hYsdkXOAtWLqdnM/Yq0+PMXtzSJ84M8V9hDhtLo=; b=qFXkYnFdzdI63c7RpectNNOlE9MusHakAlSI9MvpHdzPA4ZaUF37DTTG5MQbl1IVNr 5d0d6fN5DQKB64UQvZL5wM5ozU4lcgnaNB5s3mDVm8P+ZgOY6WNdGqBrE4fj5Dbcrt8T 84q5Bn31E8dPDon7wkFgRoxaoyTgevsq5ZfP5258hvzlAhH66Cm/V5mQFx6TaucPae42 Nos2EyejbJMGYlYQcbbHx4RIqSczXFXYagMgyd7NOxIvVIFP3bVkeNGBZVUyHECgWjI4 kICfX6Iqt7s7Urzw6mXc9msLEPwWYWM7g7/NVNbjU1f5kWmWFxyJPWEB/ANx+FF9F7EY ZayQ== 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:sender:message-id:date :subject:from:to; bh=6DB3hYsdkXOAtWLqdnM/Yq0+PMXtzSJ84M8V9hDhtLo=; b=cbejE+k8Z5vZp9nmQVxwoIleaQXqrhbvzPhQr1bpT6kdcqgXMfnMeNj0QFsE2YfebE WWvGamHZcusgrB2StbkCiwujNAPr/y/8E2ApVBYgeYlAy7C7fFGUTOXX4l0lDcrLzQJY /a627zJxwG9U6DtbcWrXoORUhRqWGwD5x3itgaTJoszG3J35brU/zbkPHfoP0vlpFG/Z yhA4ceGtEyQ+FTjCjYcQc84f/Fu8frfKT7ybe+deWHTsUM5kRygg2g8ja67ruL28ma6S EjJ5Y9sXJmGV/6rJImBfzWc4lUdYb1nbTfXaanSk+LrlKJ34G3vmBa6q11bQLd8m9RQA k5Eg== X-Gm-Message-State: APjAAAVRrFcyXoZCjHI8463v7keglU2ZmfTAxG7//WKcraPtXHUdqEvN pbpRafPkTVcL2zSLpXIn79hRjZK4oGFLLgN8auuV X-Google-Smtp-Source: APXvYqzKuT/O7+o2UvRwd0q84lOhKuCDXopZVqo2KQObBxaSMYnLlLIgFiLjA7u8rICnOPfYXx137vMOC+YStYxgJyeP MIME-Version: 1.0 X-Received: by 2002:a81:9a83:: with SMTP id r125mr8799996ywg.163.1572150929043; Sat, 26 Oct 2019 21:35:29 -0700 (PDT) Reply-To: kistapas42@gmail.com Sender: Google Calendar Message-ID: <000000000000a8b8290595dce9b9@google.com> Date: Sun, 27 Oct 2019 04:35:29 +0000 Subject: =?UTF-8?B?SW52aXRhdGlvbjog4LmC4LiX4Lij4LiU4LmJ4Lin4LiiIFNreXBlIEAgU3VuIE9jdCAyNw==?= =?UTF-8?B?LCAyMDE5IChmcmVlYnNkLWFybUBmcmVlYnNkLm9yZyk=?= From: kistapas42@gmail.com To: freebsd-arm@freebsd.org X-Rspamd-Queue-Id: 4714ll4S7dz4JLJ X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=pass header.d=google.com header.s=20161025 header.b=hOghmZQM; dkim=pass header.d=gmail.com header.s=20161025 header.b=qFXkYnFd; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of kistapas42@gmail.com designates 2607:f8b0:4864:20::b49 as permitted sender) smtp.mailfrom=kistapas42@gmail.com X-Spamd-Result: default: False [-0.52 / 15.00]; HAS_REPLYTO(0.00)[kistapas42@gmail.com]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; HAS_ATTACHMENT(0.00)[]; TO_DN_NONE(0.00)[]; DKIM_TRACE(0.00)[google.com:+,gmail.com:+]; MIME_BASE64_TEXT(0.10)[]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:+,3:~,4:~,5:~]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; PHISHING(0.72)[skype->google]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[google.com:s=20161025,gmail.com:s=20161025]; REPLYTO_EQ_FROM(0.00)[]; IP_SCORE(0.00)[ip: (-1.88), ipnet: 2607:f8b0::/32(-2.40), asn: 15169(-2.05), country: US(-0.05)]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/mixed,multipart/alternative,text/plain]; FREEMAIL_REPLYTO(0.00)[gmail.com]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; MIME_BAD_ATTACHMENT(1.60)[ics]; RCPT_COUNT_ONE(0.00)[1]; MANY_INVISIBLE_PARTS(0.05)[1]; IP_SCORE_FREEMAIL(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[9.4.b.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; FROM_NO_DN(0.00)[]; HAS_GOOGLE_REDIR(0.01)[]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] Content-Type: text/plain; charset="UTF-8"; format=flowed; delsp=yes Content-Transfer-Encoding: base64 X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Oct 2019 04:35:32 -0000 WW91IGhhdmUgYmVlbiBpbnZpdGVkIHRvIHRoZSBmb2xsb3dpbmcgZXZlbnQuDQoNClRpdGxlOiDg uYLguJfguKPguJTguYnguKfguKIgU2t5cGUNCkJzZA0KDQrguKPguLHguJogT3V0bG9vayBmb3Ig QW5kcm9pZA0KaHR0cHM6Ly9qb2luLnNreXBlLmNvbS9RR2cxUHFjSlRkajgNCg0KDQouLi4uLi4u Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u Li4uLi4uLi4uLi4uLi4uLg0KSm9pbiBvbmxpbmUgbWVldGluZw0KLi4uLi4uLi4uLi4uLi4uLi4u Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u Li4uLi4NCg0KV2hlbjogU3VuIE9jdCAyNywgMjAxOQ0KQ2FsZW5kYXI6IGZyZWVic2QtYXJtQGZy ZWVic2Qub3JnDQpXaG86DQogICAgICoga2lzdGFwYXM0MkBnbWFpbC5jb20gLSBvcmdhbml6ZXIN CiAgICAgKiBmcmVlYnNkLWFybUBmcmVlYnNkLm9yZw0KDQpFdmVudCBkZXRhaWxzOiAgDQpodHRw czovL3d3dy5nb29nbGUuY29tL2NhbGVuZGFyL2V2ZW50P2FjdGlvbj1WSUVXJmVpZD1Yell3Y1RN d1l6Rm5OakJ2TXpCbE1XazJNRzgwWVdNeFp6WXdjbW80WjNCc09EaHlhakpqTVdnNE5ITXpOR2c1 WnpZd2N6TXdZekZuTmpCdk16QmpNV2MyTVRNek1tUTVhVGcxTXpNMlpIRTJOekV4YXpoa09XYzJO Rzh6TUdNeFp6WXdiek13WXpGbk5qQnZNekJqTVdjMk1HOHpNbU14WnpZd2J6TXdZekZuTm5OeU16 Qm5ZVEkyT0hGcU5HZHdiVGc1TVRNNFpIQnJObU56TXpaallUVTRaRE0wTW1Sb2JqaG5jek00WjJo dE9EUnhaeUJtY21WbFluTmtMV0Z5YlVCbWNtVmxZbk5rTG05eVp3JnRvaz1NakFqYTJsemRHRndZ WE0wTWtCbmJXRnBiQzVqYjIxa1pUa3lOVGd4TVRreFltRTJaRGN4WlRZMk1tTXlZMlEwTVdJNVpU TXdaRGhoWVRVek1EUmkmY3R6PVVUQyZobD1lbiZlcz0wDQoNCkludml0YXRpb24gZnJvbSBHb29n bGUgQ2FsZW5kYXI6IGh0dHBzOi8vd3d3Lmdvb2dsZS5jb20vY2FsZW5kYXIvDQoNCllvdSBhcmUg cmVjZWl2aW5nIHRoaXMgY291cnRlc3kgZW1haWwgYXQgdGhlIGFjY291bnQgIA0KZnJlZWJzZC1h cm1AZnJlZWJzZC5vcmcgYmVjYXVzZSB5b3UgYXJlIGFuIGF0dGVuZGVlIG9mIHRoaXMgZXZlbnQu DQoNClRvIHN0b3AgcmVjZWl2aW5nIGZ1dHVyZSB1cGRhdGVzIGZvciB0aGlzIGV2ZW50LCBkZWNs aW5lIHRoaXMgZXZlbnQuICANCkFsdGVybmF0aXZlbHkgeW91IGNhbiBzaWduIHVwIGZvciBhIEdv b2dsZSBhY2NvdW50IGF0ICANCmh0dHBzOi8vd3d3Lmdvb2dsZS5jb20vY2FsZW5kYXIvIGFuZCBj b250cm9sIHlvdXIgbm90aWZpY2F0aW9uIHNldHRpbmdzIGZvciAgDQp5b3VyIGVudGlyZSBjYWxl bmRhci4NCg0KRm9yd2FyZGluZyB0aGlzIGludml0YXRpb24gY291bGQgYWxsb3cgYW55IHJlY2lw aWVudCB0byBzZW5kIGEgcmVzcG9uc2UgdG8gIA0KdGhlIG9yZ2FuaXplciBhbmQgYmUgYWRkZWQg dG8gdGhlIGd1ZXN0IGxpc3QsIG9yIGludml0ZSBvdGhlcnMgcmVnYXJkbGVzcyAgDQpvZiB0aGVp ciBvd24gaW52aXRhdGlvbiBzdGF0dXMsIG9yIHRvIG1vZGlmeSB5b3VyIFJTVlAuIExlYXJuIG1v cmUgYXQgIA0KaHR0cHM6Ly9zdXBwb3J0Lmdvb2dsZS5jb20vY2FsZW5kYXIvYW5zd2VyLzM3MTM1 I2ZvcndhcmRpbmcNCg== From owner-freebsd-arm@freebsd.org Sun Oct 27 21:00:16 2019 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 2B9FE1A6278 for ; Sun, 27 Oct 2019 21:00:16 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 471Vc00NwQz478G for ; Sun, 27 Oct 2019 21:00:16 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id E5F8126E0C for ; Sun, 27 Oct 2019 21:00:15 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x9RL0F4X018344 for ; Sun, 27 Oct 2019 21:00:15 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x9RL0FVV018343 for freebsd-arm@FreeBSD.org; Sun, 27 Oct 2019 21:00:15 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201910272100.x9RL0FVV018343@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, 27 Oct 2019 21:00:15 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Oct 2019 21:00:16 -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 ------------+-----------+--------------------------------------------------- Open | 238576 | Raspberry Pi 3B+ "shutdown -p" does not shut off Open | 239673 | Spurious Interrupt message from /dev/led/led1 2 problems total for which you should take action. From owner-freebsd-arm@freebsd.org Mon Oct 28 00:26:19 2019 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id B385115D601 for ; Mon, 28 Oct 2019 00:26:19 +0000 (UTC) (envelope-from darius@dons.net.au) Received: from ipmail03.adl2.internode.on.net (ipmail03.adl2.internode.on.net [150.101.137.141]) by mx1.freebsd.org (Postfix) with ESMTP id 471b9j3Zhgz4Kb9 for ; Mon, 28 Oct 2019 00:26:16 +0000 (UTC) (envelope-from darius@dons.net.au) Received: from unknown (HELO midget.dons.net.au) ([118.211.86.117]) by ipmail03.adl2.internode.on.net with ESMTP; 28 Oct 2019 10:56:13 +1030 Received: from midget.dons.net.au (localhost [127.0.0.1]) by midget.dons.net.au (8.15.2/8.15.2) with ESMTPS id x9S0Pxv0015523 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Mon, 28 Oct 2019 10:56:06 +1030 (ACDT) (envelope-from darius@dons.net.au) Received: (from mailnull@localhost) by midget.dons.net.au (8.15.2/8.15.2/Submit) id x9S03S6D097446 for ; Mon, 28 Oct 2019 10:33:28 +1030 (ACDT) (envelope-from darius@dons.net.au) X-Authentication-Warning: midget.dons.net.au: mailnull set sender to using -f X-MIMEDefang-Relay-be813b1f1da6d6b27d681222cb70cc4f5b642383: 10.0.2.38 Received: from havok.dons.net.au ([10.0.2.38]) by ns.dons.net.au (envelope-sender ) (MIMEDefang) with ESMTP id x9S03NrA097444; Mon, 28 Oct 2019 10:33:28 +1030 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Subject: Re: Permissions when moving storage devices between hosts From: "O'Connor, Daniel" In-Reply-To: <20191026163920.GA38958@www.zefox.net> Date: Mon, 28 Oct 2019 10:33:23 +1030 Cc: freebsd-arm@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <20191026163920.GA38958@www.zefox.net> To: bob prohaska X-Mailer: Apple Mail (2.3445.104.11) X-Spam-Score: -1 () No, score=-1.0 required=5.0 tests=ALL_TRUSTED autolearn=unavailable autolearn_force=no version=3.4.2 X-Scanned-By: MIMEDefang 2.83 on 10.0.2.1 X-Rspamd-Queue-Id: 471b9j3Zhgz4Kb9 X-Spamd-Bar: +++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of darius@dons.net.au has no SPF policy when checking 150.101.137.141) smtp.mailfrom=darius@dons.net.au X-Spamd-Result: default: False [3.93 / 15.00]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; HAS_XAW(0.00)[]; RWL_MAILSPIKE_GOOD(0.00)[141.137.101.150.rep.mailspike.net : 127.0.0.18]; DMARC_NA(0.00)[dons.net.au]; AUTH_NA(1.00)[]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_SPAM_MEDIUM(0.72)[0.720,0]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[141.137.101.150.list.dnswl.org : 127.0.5.0]; NEURAL_SPAM_LONG(0.94)[0.943,0]; R_SPF_NA(0.00)[]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:4739, ipnet:150.101.0.0/16, country:AU]; MID_RHS_MATCH_FROM(0.00)[]; IP_SCORE(0.77)[ip: (0.05), ipnet: 150.101.0.0/16(2.50), asn: 4739(1.28), country: AU(0.01)] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Oct 2019 00:26:19 -0000 > On 27 Oct 2019, at 03:09, bob prohaska wrote: > The plan was to re-run the bonnie test on the second host to see if = the > choice of host made much difference. Alas, after mounting the card, = all > owners/groups are freebsd/freebsd and I can't get permission to write > any files, at least as a regular user. The usernames are the same on > both hosts and I'm hesitant to try mucking about with ownerships. > It does not seem possible to simply add world-write permissions to the=20= > test directory using chmod +w as root. =20 Is it mounted read/write? ie show the output of 'mount'. Also note that the filesystem only stores user IDs not user names. ie you might have a user called 'freebsd' on two systems but with = different IDs and if you move an FS between them you can have issues. That said, root should be able to change the permissions (or just write = since being root skips permission checks). If it can't then it seems = more like it isn't mounted read/write for whatever reason (write protect = tab on the SD card set by accident?) -- Daniel O'Connor "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum From owner-freebsd-arm@freebsd.org Mon Oct 28 00:45:16 2019 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 6C98A15E182 for ; Mon, 28 Oct 2019 00:45:16 +0000 (UTC) (envelope-from gdotten@gmail.com) Received: from mail-qt1-x836.google.com (mail-qt1-x836.google.com [IPv6:2607:f8b0:4864:20::836]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 471bbZ4t7kz4LKY; Mon, 28 Oct 2019 00:45:14 +0000 (UTC) (envelope-from gdotten@gmail.com) Received: by mail-qt1-x836.google.com with SMTP id u22so12171336qtq.13; Sun, 27 Oct 2019 17:45:14 -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=49OUhmUVvC47RaLnt0W0Ru5E9S3iys1AMgEYnMShs5U=; b=c4ksUqw6Yv1sWqWNAUr1xmaXKT60TYqBo9wMIERNaQBa4No3op5Oa6FSWUnLYe8/EV PLa/89ZSlsROhov6lCIiSdKTcecARgWJIpOplfRG+KuReBAUWs+caLcKbd8HfJ96C/u3 FhQ/Nfc99KgPj85teB5oDiZdFM1Z10HRWz9fxYQ0/fYSoIMr1OAZqPAS9TKdkuc5A1sl ZmyfTTuQ8ZzUbtFDYpL5sVu/2rDM9rH+HEtgS2lw/JlfNwdkf+DFL7xOqNq/KCs7ufuN 4U658lIBiv/DiHbtiDIVmLpPWoDjk9Ittzcrr2oEbIkk9s4k1LJiw/XGKYFU4NOnNHpD AXTw== 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=49OUhmUVvC47RaLnt0W0Ru5E9S3iys1AMgEYnMShs5U=; b=dZDkvJchAQCarPyy9jzBfhkT7L5uJwDT0krXX9qeMHWGmHXDh5aergTMqnNEaeAJuf Tl7C9gZDhSz3pe86xwkJ/39m396GvOuDqxcpy/oyixWbppcpjK2MwViXP02U0r/R+8pn 1/ehVbDrAK861irJJprhgoc7zlfwnmS6SlY2638gGWcOIv6H5Bd1qHlZF2kg2XKVZ4Ty qFXcr5oXpoHBZXnRgGDSAfFpGfs5OKbh/HdtnBfjB8jkMSzMOEwmrb8XySMlX0ZuA3gl oOe9Omb6noKz9KmhtIVM6LOcCiGOSUjpCKdSvhVByXgX/c/y77xzOHiVp0nZWtKwf92Z Bl0Q== X-Gm-Message-State: APjAAAVVfojB9OuftLS0ZtsWSiOqijEnkXohobz6WN1Cae0MuNiMNSdJ jtieNQLuJztPJk26J4Jv7gFlF0MUOJl5T0uW1nR3skRc X-Google-Smtp-Source: APXvYqyT8G41WvzWtV+ka6oqluWL5D6GGH8nPUy3o207uYs0M7SQIxcweuy09+lud5AFJefPw9fmQ+z6KChp8zjcC20= X-Received: by 2002:aed:2357:: with SMTP id i23mr7875971qtc.365.1572223513006; Sun, 27 Oct 2019 17:45:13 -0700 (PDT) MIME-Version: 1.0 References: <20191015131842.370e113b9f494ead760b9b6f@bidouilliste.com> <20191015175901.1d0173f27798f15c25c037de@bidouilliste.com> <20191018133131.3063a80860e4906e0fd67f2c@bidouilliste.com> <20191018134326.dce3f37b8418ea9a2c0095a1@bidouilliste.com> <20191022155716.3ebf30f63e02409aee2a6679@bidouilliste.com> In-Reply-To: <20191022155716.3ebf30f63e02409aee2a6679@bidouilliste.com> From: Gary Otten Date: Sun, 27 Oct 2019 20:36:44 -0400 Message-ID: Subject: Re: GPIO on Olimex A64 board. Bank E not working. To: Emmanuel Vadot Cc: freebsd-arm@freebsd.org, mmel@freebsd.org X-Rspamd-Queue-Id: 471bbZ4t7kz4LKY X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=c4ksUqw6; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of gdotten@gmail.com designates 2607:f8b0:4864:20::836 as permitted sender) smtp.mailfrom=gdotten@gmail.com X-Spamd-Result: default: False [-3.00 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; IP_SCORE(0.00)[ip: (-9.24), ipnet: 2607:f8b0::/32(-2.40), asn: 15169(-2.05), country: US(-0.05)]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TO_DN_SOME(0.00)[]; IP_SCORE_FREEMAIL(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; RCVD_IN_DNSWL_NONE(0.00)[6.3.8.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Oct 2019 00:45:16 -0000 I have set boot-on on aldo1 I didn't have any success in getting the E bank to have voltage. I turned on a few other voltage regulators as well hoping one of those might be powering the E bank instead, but no luck. I do have voltage on the B bank of gpios and the pins that are exposed do function correctly with the gpioctl command. For output see below. Thanks again for everyone's help. root@generic:~ # sysctl hw.regulator hw.regulator.dc1sw.uvolt: 0 hw.regulator.dc1sw.always_on: 0 hw.regulator.dc1sw.boot_on: 0 hw.regulator.dc1sw.enable_cnt: 0 hw.regulator.dc1sw.enable_delay: 0 hw.regulator.dc1sw.ramp_delay: 0 hw.regulator.dc1sw.max_uamp: 0 hw.regulator.dc1sw.min_uamp: 0 hw.regulator.dc1sw.max_uvolt: 0 hw.regulator.dc1sw.min_uvolt: 0 hw.regulator.ldo-io1.always_on: 0 hw.regulator.ldo-io1.boot_on: 0 hw.regulator.ldo-io1.enable_cnt: 0 hw.regulator.ldo-io1.enable_delay: 0 hw.regulator.ldo-io1.ramp_delay: 0 hw.regulator.ldo-io1.max_uamp: 0 hw.regulator.ldo-io1.min_uamp: 0 hw.regulator.ldo-io1.max_uvolt: 3300000 hw.regulator.ldo-io1.min_uvolt: 700000 hw.regulator.ldo-io0.always_on: 0 hw.regulator.ldo-io0.boot_on: 0 hw.regulator.ldo-io0.enable_cnt: 0 hw.regulator.ldo-io0.enable_delay: 0 hw.regulator.ldo-io0.ramp_delay: 0 hw.regulator.ldo-io0.max_uamp: 0 hw.regulator.ldo-io0.min_uamp: 0 hw.regulator.ldo-io0.max_uvolt: 3300000 hw.regulator.ldo-io0.min_uvolt: 700000 hw.regulator.vdd-cpus.uvolt: 1100000 hw.regulator.vdd-cpus.always_on: 1 hw.regulator.vdd-cpus.boot_on: 0 hw.regulator.vdd-cpus.enable_cnt: 0 hw.regulator.vdd-cpus.enable_delay: 0 hw.regulator.vdd-cpus.ramp_delay: 0 hw.regulator.vdd-cpus.max_uamp: 0 hw.regulator.vdd-cpus.min_uamp: 0 hw.regulator.vdd-cpus.max_uvolt: 1100000 hw.regulator.vdd-cpus.min_uvolt: 1100000 hw.regulator.vcc-1v2-hsic.uvolt: 1200000 hw.regulator.vcc-1v2-hsic.always_on: 0 hw.regulator.vcc-1v2-hsic.boot_on: 0 hw.regulator.vcc-1v2-hsic.enable_cnt: 0 hw.regulator.vcc-1v2-hsic.enable_delay: 0 hw.regulator.vcc-1v2-hsic.ramp_delay: 0 hw.regulator.vcc-1v2-hsic.max_uamp: 0 hw.regulator.vcc-1v2-hsic.min_uamp: 0 hw.regulator.vcc-1v2-hsic.max_uvolt: 1200000 hw.regulator.vcc-1v2-hsic.min_uvolt: 1200000 hw.regulator.eldo3.always_on: 0 hw.regulator.eldo3.boot_on: 0 hw.regulator.eldo3.enable_cnt: 0 hw.regulator.eldo3.enable_delay: 0 hw.regulator.eldo3.ramp_delay: 0 hw.regulator.eldo3.max_uamp: 0 hw.regulator.eldo3.min_uamp: 0 hw.regulator.eldo3.max_uvolt: 1900000 hw.regulator.eldo3.min_uvolt: 700000 hw.regulator.vcc-dvdd-csi.uvolt: 1800000 hw.regulator.vcc-dvdd-csi.always_on: 1 hw.regulator.vcc-dvdd-csi.boot_on: 1 hw.regulator.vcc-dvdd-csi.enable_cnt: 0 hw.regulator.vcc-dvdd-csi.enable_delay: 0 hw.regulator.vcc-dvdd-csi.ramp_delay: 0 hw.regulator.vcc-dvdd-csi.max_uamp: 0 hw.regulator.vcc-dvdd-csi.min_uamp: 0 hw.regulator.vcc-dvdd-csi.max_uvolt: 1800000 hw.regulator.vcc-dvdd-csi.min_uvolt: 1800000 hw.regulator.cpvdd.uvolt: 1800000 hw.regulator.cpvdd.always_on: 0 hw.regulator.cpvdd.boot_on: 0 hw.regulator.cpvdd.enable_cnt: 0 hw.regulator.cpvdd.enable_delay: 0 hw.regulator.cpvdd.ramp_delay: 0 hw.regulator.cpvdd.max_uamp: 0 hw.regulator.cpvdd.min_uamp: 0 hw.regulator.cpvdd.max_uvolt: 1800000 hw.regulator.cpvdd.min_uvolt: 1800000 hw.regulator.vcc-pll-avcc.uvolt: 3000000 hw.regulator.vcc-pll-avcc.always_on: 1 hw.regulator.vcc-pll-avcc.boot_on: 1 hw.regulator.vcc-pll-avcc.enable_cnt: 0 hw.regulator.vcc-pll-avcc.enable_delay: 0 hw.regulator.vcc-pll-avcc.ramp_delay: 0 hw.regulator.vcc-pll-avcc.max_uamp: 0 hw.regulator.vcc-pll-avcc.min_uamp: 0 hw.regulator.vcc-pll-avcc.max_uvolt: 3000000 hw.regulator.vcc-pll-avcc.min_uvolt: 3000000 hw.regulator.vcc-pl.uvolt: 3300000 hw.regulator.vcc-pl.always_on: 1 hw.regulator.vcc-pl.boot_on: 1 hw.regulator.vcc-pl.enable_cnt: 0 hw.regulator.vcc-pl.enable_delay: 0 hw.regulator.vcc-pl.ramp_delay: 0 hw.regulator.vcc-pl.max_uamp: 0 hw.regulator.vcc-pl.min_uamp: 0 hw.regulator.vcc-pl.max_uvolt: 3300000 hw.regulator.vcc-pl.min_uvolt: 3300000 hw.regulator.vcc-pe.uvolt: 2800000 hw.regulator.vcc-pe.always_on: 1 hw.regulator.vcc-pe.boot_on: 1 hw.regulator.vcc-pe.enable_cnt: 0 hw.regulator.vcc-pe.enable_delay: 0 hw.regulator.vcc-pe.ramp_delay: 0 hw.regulator.vcc-pe.max_uamp: 0 hw.regulator.vcc-pe.min_uamp: 0 hw.regulator.vcc-pe.max_uvolt: 2800000 hw.regulator.vcc-pe.min_uvolt: 2800000 hw.regulator.vcc-wifi-io.uvolt: 3300000 hw.regulator.vcc-wifi-io.always_on: 0 hw.regulator.vcc-wifi-io.boot_on: 0 hw.regulator.vcc-wifi-io.enable_cnt: 0 hw.regulator.vcc-wifi-io.enable_delay: 0 hw.regulator.vcc-wifi-io.ramp_delay: 0 hw.regulator.vcc-wifi-io.max_uamp: 0 hw.regulator.vcc-wifi-io.min_uamp: 0 hw.regulator.vcc-wifi-io.max_uvolt: 3300000 hw.regulator.vcc-wifi-io.min_uvolt: 3300000 hw.regulator.vcc-avdd-csi.uvolt: 2800000 hw.regulator.vcc-avdd-csi.always_on: 1 hw.regulator.vcc-avdd-csi.boot_on: 1 hw.regulator.vcc-avdd-csi.enable_cnt: 0 hw.regulator.vcc-avdd-csi.enable_delay: 0 hw.regulator.vcc-avdd-csi.ramp_delay: 0 hw.regulator.vcc-avdd-csi.max_uamp: 0 hw.regulator.vcc-avdd-csi.min_uamp: 0 hw.regulator.vcc-avdd-csi.max_uvolt: 2800000 hw.regulator.vcc-avdd-csi.min_uvolt: 2800000 hw.regulator.vcc-mipi.uvolt: 3300000 hw.regulator.vcc-mipi.always_on: 1 hw.regulator.vcc-mipi.boot_on: 1 hw.regulator.vcc-mipi.enable_cnt: 0 hw.regulator.vcc-mipi.enable_delay: 0 hw.regulator.vcc-mipi.ramp_delay: 0 hw.regulator.vcc-mipi.max_uamp: 0 hw.regulator.vcc-mipi.min_uamp: 0 hw.regulator.vcc-mipi.max_uvolt: 3300000 hw.regulator.vcc-mipi.min_uvolt: 3300000 hw.regulator.vcc-hdmi.uvolt: 3300000 hw.regulator.vcc-hdmi.always_on: 0 hw.regulator.vcc-hdmi.boot_on: 0 hw.regulator.vcc-hdmi.enable_cnt: 0 hw.regulator.vcc-hdmi.enable_delay: 0 hw.regulator.vcc-hdmi.ramp_delay: 0 hw.regulator.vcc-hdmi.max_uamp: 0 hw.regulator.vcc-hdmi.min_uamp: 0 hw.regulator.vcc-hdmi.max_uvolt: 3300000 hw.regulator.vcc-hdmi.min_uvolt: 3300000 hw.regulator.vdd-sys.uvolt: 1100000 hw.regulator.vdd-sys.always_on: 1 hw.regulator.vdd-sys.boot_on: 0 hw.regulator.vdd-sys.enable_cnt: 0 hw.regulator.vdd-sys.enable_delay: 0 hw.regulator.vdd-sys.ramp_delay: 0 hw.regulator.vdd-sys.max_uamp: 0 hw.regulator.vdd-sys.min_uamp: 0 hw.regulator.vdd-sys.max_uvolt: 1100000 hw.regulator.vdd-sys.min_uvolt: 1100000 hw.regulator.vcc-ddr3.uvolt: 1360000 hw.regulator.vcc-ddr3.always_on: 1 hw.regulator.vcc-ddr3.boot_on: 0 hw.regulator.vcc-ddr3.enable_cnt: 0 hw.regulator.vcc-ddr3.enable_delay: 0 hw.regulator.vcc-ddr3.ramp_delay: 0 hw.regulator.vcc-ddr3.max_uamp: 0 hw.regulator.vcc-ddr3.min_uamp: 0 hw.regulator.vcc-ddr3.max_uvolt: 1360000 hw.regulator.vcc-ddr3.min_uvolt: 1360000 hw.regulator.dcdc4.uvolt: 1100000 hw.regulator.dcdc4.always_on: 0 hw.regulator.dcdc4.boot_on: 0 hw.regulator.dcdc4.enable_cnt: 0 hw.regulator.dcdc4.enable_delay: 0 hw.regulator.dcdc4.ramp_delay: 0 hw.regulator.dcdc4.max_uamp: 0 hw.regulator.dcdc4.min_uamp: 0 hw.regulator.dcdc4.max_uvolt: 1300000 hw.regulator.dcdc4.min_uvolt: 500000 hw.regulator.dcdc3.uvolt: 1100000 hw.regulator.dcdc3.always_on: 0 hw.regulator.dcdc3.boot_on: 0 hw.regulator.dcdc3.enable_cnt: 0 hw.regulator.dcdc3.enable_delay: 0 hw.regulator.dcdc3.ramp_delay: 0 hw.regulator.dcdc3.max_uamp: 0 hw.regulator.dcdc3.min_uamp: 0 hw.regulator.dcdc3.max_uvolt: 1300000 hw.regulator.dcdc3.min_uvolt: 500000 hw.regulator.vdd-cpux.uvolt: 1100000 hw.regulator.vdd-cpux.always_on: 1 hw.regulator.vdd-cpux.boot_on: 0 hw.regulator.vdd-cpux.enable_cnt: 0 hw.regulator.vdd-cpux.enable_delay: 0 hw.regulator.vdd-cpux.ramp_delay: 0 hw.regulator.vdd-cpux.max_uamp: 0 hw.regulator.vdd-cpux.min_uamp: 0 hw.regulator.vdd-cpux.max_uvolt: 1300000 hw.regulator.vdd-cpux.min_uvolt: 1040000 hw.regulator.vcc-3v3.uvolt: 3300000 hw.regulator.vcc-3v3.always_on: 1 hw.regulator.vcc-3v3.boot_on: 1 hw.regulator.vcc-3v3.enable_cnt: 2 hw.regulator.vcc-3v3.enable_delay: 0 hw.regulator.vcc-3v3.ramp_delay: 0 hw.regulator.vcc-3v3.max_uamp: 0 hw.regulator.vcc-3v3.min_uamp: 0 hw.regulator.vcc-3v3.max_uvolt: 3300000 hw.regulator.vcc-3v3.min_uvolt: 3300000 hw.regulator.usb1-vbus.uvolt: 5000000 hw.regulator.usb1-vbus.always_on: 0 hw.regulator.usb1-vbus.boot_on: 1 hw.regulator.usb1-vbus.enable_cnt: 1 hw.regulator.usb1-vbus.enable_delay: 0 hw.regulator.usb1-vbus.ramp_delay: 0 hw.regulator.usb1-vbus.max_uamp: 0 hw.regulator.usb1-vbus.min_uamp: 0 hw.regulator.usb1-vbus.max_uvolt: 5000000 hw.regulator.usb1-vbus.min_uvolt: 5000000 *************************************************************************************** pin 00: 1 PB0 pin 01: 0 PB1<> pin 02: 0 PB2<> pin 03: 0 PB3<> pin 04: 0 PB4<> pin 05: 0 PB5<> pin 06: 0 PB6<> pin 07: 0 PB7<> pin 08: 0 PB8<> pin 09: 0 PB9 pin 10: 0 PC0<> pin 11: 0 PC1<> pin 12: 0 PC2<> pin 13: 0 PC3 pin 14: 0 PC4 pin 15: 0 PC5 pin 16: 0 PC6 pin 17: 0 PC7 pin 18: 0 PC8 pin 19: 0 PC9 pin 20: 0 PC10 pin 21: 0 PC11 pin 22: 0 PC12 pin 23: 0 PC13 pin 24: 0 PC14 pin 25: 0 PC15 pin 26: 0 PC16 pin 27: 0 PD0<> pin 28: 0 PD1<> pin 29: 0 PD2<> pin 30: 0 PD3<> pin 31: 0 PD4<> pin 32: 0 PD5<> pin 33: 0 PD6<> pin 34: 0 PD7<> pin 35: 0 PD8<> pin 36: 0 PD9<> pin 37: 0 PD10<> pin 38: 0 PD11<> pin 39: 0 PD12<> pin 40: 0 PD13<> pin 41: 0 PD14<> pin 42: 0 PD15<> pin 43: 0 PD16<> pin 44: 0 PD17<> pin 45: 0 PD18<> pin 46: 0 PD19<> pin 47: 0 PD20<> pin 48: 0 PD21<> pin 49: 0 PD22<> pin 50: 0 PD23<> pin 51: 0 PD24<> pin 52: 1 PE0 pin 53: 0 PE1<> pin 54: 0 PE2<> pin 55: 0 PE3<> pin 56: 0 PE4<> pin 57: 0 PE5<> pin 58: 0 PE6<> On Tue, Oct 22, 2019 at 9:57 AM Emmanuel Vadot wrote: > On Fri, 18 Oct 2019 13:43:26 +0200 > Emmanuel Vadot wrote: > > > On Fri, 18 Oct 2019 13:31:31 +0200 > > Emmanuel Vadot wrote: > > > > > On Tue, 15 Oct 2019 13:26:46 -0400 > > > Gary Otten wrote: > > > > > > > Ok, I placed hw.regulator.disable_unused=0 in /boot/loader.conf. > Here is > > > > the results, also still no output on the E bank. > > > > > > > > root@:/dev # sysctl hw.regulator > > > > hw.regulator.dc1sw.uvolt: 0 > > > > hw.regulator.dc1sw.always_on: 0 > > > > hw.regulator.dc1sw.boot_on: 0 > > > > hw.regulator.dc1sw.enable_cnt: 0 > > > > hw.regulator.dc1sw.enable_delay: 0 > > > > hw.regulator.dc1sw.ramp_delay: 0 > > > > hw.regulator.dc1sw.max_uamp: 0 > > > > hw.regulator.dc1sw.min_uamp: 0 > > > > hw.regulator.dc1sw.max_uvolt: 0 > > > > hw.regulator.dc1sw.min_uvolt: 0 > > > > hw.regulator.ldo-io1.always_on: 0 > > > > hw.regulator.ldo-io1.boot_on: 0 > > > > hw.regulator.ldo-io1.enable_cnt: 0 > > > > hw.regulator.ldo-io1.enable_delay: 0 > > > > hw.regulator.ldo-io1.ramp_delay: 0 > > > > hw.regulator.ldo-io1.max_uamp: 0 > > > > hw.regulator.ldo-io1.min_uamp: 0 > > > > hw.regulator.ldo-io1.max_uvolt: 3300000 > > > > hw.regulator.ldo-io1.min_uvolt: 700000 > > > > hw.regulator.ldo-io0.always_on: 0 > > > > hw.regulator.ldo-io0.boot_on: 0 > > > > hw.regulator.ldo-io0.enable_cnt: 0 > > > > hw.regulator.ldo-io0.enable_delay: 0 > > > > hw.regulator.ldo-io0.ramp_delay: 0 > > > > hw.regulator.ldo-io0.max_uamp: 0 > > > > hw.regulator.ldo-io0.min_uamp: 0 > > > > hw.regulator.ldo-io0.max_uvolt: 3300000 > > > > hw.regulator.ldo-io0.min_uvolt: 700000 > > > > hw.regulator.vdd-cpus.uvolt: 1100000 > > > > hw.regulator.vdd-cpus.always_on: 1 > > > > hw.regulator.vdd-cpus.boot_on: 0 > > > > hw.regulator.vdd-cpus.enable_cnt: 0 > > > > hw.regulator.vdd-cpus.enable_delay: 0 > > > > hw.regulator.vdd-cpus.ramp_delay: 0 > > > > hw.regulator.vdd-cpus.max_uamp: 0 > > > > hw.regulator.vdd-cpus.min_uamp: 0 > > > > hw.regulator.vdd-cpus.max_uvolt: 1100000 > > > > hw.regulator.vdd-cpus.min_uvolt: 1100000 > > > > hw.regulator.vcc-1v2-hsic.uvolt: 1200000 > > > > hw.regulator.vcc-1v2-hsic.always_on: 0 > > > > hw.regulator.vcc-1v2-hsic.boot_on: 0 > > > > hw.regulator.vcc-1v2-hsic.enable_cnt: 0 > > > > hw.regulator.vcc-1v2-hsic.enable_delay: 0 > > > > hw.regulator.vcc-1v2-hsic.ramp_delay: 0 > > > > hw.regulator.vcc-1v2-hsic.max_uamp: 0 > > > > hw.regulator.vcc-1v2-hsic.min_uamp: 0 > > > > hw.regulator.vcc-1v2-hsic.max_uvolt: 1200000 > > > > hw.regulator.vcc-1v2-hsic.min_uvolt: 1200000 > > > > hw.regulator.eldo3.always_on: 0 > > > > hw.regulator.eldo3.boot_on: 0 > > > > hw.regulator.eldo3.enable_cnt: 0 > > > > hw.regulator.eldo3.enable_delay: 0 > > > > hw.regulator.eldo3.ramp_delay: 0 > > > > hw.regulator.eldo3.max_uamp: 0 > > > > hw.regulator.eldo3.min_uamp: 0 > > > > hw.regulator.eldo3.max_uvolt: 1900000 > > > > hw.regulator.eldo3.min_uvolt: 700000 > > > > hw.regulator.vcc-dvdd-csi.uvolt: 1800000 > > > > hw.regulator.vcc-dvdd-csi.always_on: 0 > > > > hw.regulator.vcc-dvdd-csi.boot_on: 0 > > > > hw.regulator.vcc-dvdd-csi.enable_cnt: 0 > > > > hw.regulator.vcc-dvdd-csi.enable_delay: 0 > > > > hw.regulator.vcc-dvdd-csi.ramp_delay: 0 > > > > hw.regulator.vcc-dvdd-csi.max_uamp: 0 > > > > hw.regulator.vcc-dvdd-csi.min_uamp: 0 > > > > hw.regulator.vcc-dvdd-csi.max_uvolt: 1800000 > > > > hw.regulator.vcc-dvdd-csi.min_uvolt: 1800000 > > > > hw.regulator.cpvdd.uvolt: 1800000 > > > > hw.regulator.cpvdd.always_on: 0 > > > > hw.regulator.cpvdd.boot_on: 0 > > > > hw.regulator.cpvdd.enable_cnt: 0 > > > > hw.regulator.cpvdd.enable_delay: 0 > > > > hw.regulator.cpvdd.ramp_delay: 0 > > > > hw.regulator.cpvdd.max_uamp: 0 > > > > hw.regulator.cpvdd.min_uamp: 0 > > > > hw.regulator.cpvdd.max_uvolt: 1800000 > > > > hw.regulator.cpvdd.min_uvolt: 1800000 > > > > hw.regulator.vcc-pll-avcc.uvolt: 3000000 > > > > hw.regulator.vcc-pll-avcc.always_on: 1 > > > > hw.regulator.vcc-pll-avcc.boot_on: 0 > > > > hw.regulator.vcc-pll-avcc.enable_cnt: 0 > > > > hw.regulator.vcc-pll-avcc.enable_delay: 0 > > > > hw.regulator.vcc-pll-avcc.ramp_delay: 0 > > > > hw.regulator.vcc-pll-avcc.max_uamp: 0 > > > > hw.regulator.vcc-pll-avcc.min_uamp: 0 > > > > hw.regulator.vcc-pll-avcc.max_uvolt: 3000000 > > > > hw.regulator.vcc-pll-avcc.min_uvolt: 3000000 > > > > hw.regulator.vcc-pl.uvolt: 3300000 > > > > hw.regulator.vcc-pl.always_on: 1 > > > > hw.regulator.vcc-pl.boot_on: 0 > > > > hw.regulator.vcc-pl.enable_cnt: 0 > > > > hw.regulator.vcc-pl.enable_delay: 0 > > > > hw.regulator.vcc-pl.ramp_delay: 0 > > > > hw.regulator.vcc-pl.max_uamp: 0 > > > > hw.regulator.vcc-pl.min_uamp: 0 > > > > hw.regulator.vcc-pl.max_uvolt: 3300000 > > > > hw.regulator.vcc-pl.min_uvolt: 3300000 > > > > hw.regulator.vcc-pe.uvolt: 2800000 > > > > hw.regulator.vcc-pe.always_on: 1 > > > > hw.regulator.vcc-pe.boot_on: 0 > > > > hw.regulator.vcc-pe.enable_cnt: 0 > > > > hw.regulator.vcc-pe.enable_delay: 0 > > > > hw.regulator.vcc-pe.ramp_delay: 0 > > > > hw.regulator.vcc-pe.max_uamp: 0 > > > > hw.regulator.vcc-pe.min_uamp: 0 > > > > hw.regulator.vcc-pe.max_uvolt: 2800000 > > > > hw.regulator.vcc-pe.min_uvolt: 2800000 > > > > > > I've just realized that boot_on isn't 1 so u-boot will not enabled the > > > regulator and we won't too. > > > I guess that Linux (or armbian) hack on this. We are not supposed to > > > enable a regulator if boot-on is set, only the bootloader is supposed > > > to do that. And the always-on property is only there so we don't > > > disable it if no device "claimed" it. > > > > So, after asking on some linux-related irc channel, it seems that > > the Linux kernel enable a regulator if always-on or boot-on is set > > which doesn't reflect what the binding docs says and the regulator > > framework on FreeBSD is based on what the doc says ... I guess we > > should do the same. > > mmel@ what's your view on this ? > > You might want to try https://reviews.freebsd.org/D22106 > > I haven't tested, only compile the code. > > > > The proper patch would be to set the boot-on property in the dts used > > > by u-boot. Easiest way to test that is to : > > > > > > $ cd freebsd-ports/sysutils/u-boot-a64-olinuxino/ > > > $ make patch > > > ... > > > $ edit work/u-boot-2019.07/arch/arm/dts/sun50i-a64-olinuxino.dts and > > > add 'regulator-boot-on;' under the '®_aldo1' node. > > > $ make > > > $ dd the new u-boot > > > > > > > hw.regulator.vcc-wifi-io.uvolt: 3300000 > > > > hw.regulator.vcc-wifi-io.always_on: 0 > > > > hw.regulator.vcc-wifi-io.boot_on: 0 > > > > hw.regulator.vcc-wifi-io.enable_cnt: 0 > > > > hw.regulator.vcc-wifi-io.enable_delay: 0 > > > > hw.regulator.vcc-wifi-io.ramp_delay: 0 > > > > hw.regulator.vcc-wifi-io.max_uamp: 0 > > > > hw.regulator.vcc-wifi-io.min_uamp: 0 > > > > hw.regulator.vcc-wifi-io.max_uvolt: 3300000 > > > > hw.regulator.vcc-wifi-io.min_uvolt: 3300000 > > > > hw.regulator.vcc-avdd-csi.uvolt: 2800000 > > > > hw.regulator.vcc-avdd-csi.always_on: 0 > > > > hw.regulator.vcc-avdd-csi.boot_on: 0 > > > > hw.regulator.vcc-avdd-csi.enable_cnt: 0 > > > > hw.regulator.vcc-avdd-csi.enable_delay: 0 > > > > hw.regulator.vcc-avdd-csi.ramp_delay: 0 > > > > hw.regulator.vcc-avdd-csi.max_uamp: 0 > > > > hw.regulator.vcc-avdd-csi.min_uamp: 0 > > > > hw.regulator.vcc-avdd-csi.max_uvolt: 2800000 > > > > hw.regulator.vcc-avdd-csi.min_uvolt: 2800000 > > > > hw.regulator.vcc-mipi.uvolt: 3300000 > > > > hw.regulator.vcc-mipi.always_on: 0 > > > > hw.regulator.vcc-mipi.boot_on: 0 > > > > hw.regulator.vcc-mipi.enable_cnt: 0 > > > > hw.regulator.vcc-mipi.enable_delay: 0 > > > > hw.regulator.vcc-mipi.ramp_delay: 0 > > > > hw.regulator.vcc-mipi.max_uamp: 0 > > > > hw.regulator.vcc-mipi.min_uamp: 0 > > > > hw.regulator.vcc-mipi.max_uvolt: 3300000 > > > > hw.regulator.vcc-mipi.min_uvolt: 3300000 > > > > hw.regulator.vcc-hdmi.uvolt: 3300000 > > > > hw.regulator.vcc-hdmi.always_on: 0 > > > > hw.regulator.vcc-hdmi.boot_on: 0 > > > > hw.regulator.vcc-hdmi.enable_cnt: 0 > > > > hw.regulator.vcc-hdmi.enable_delay: 0 > > > > hw.regulator.vcc-hdmi.ramp_delay: 0 > > > > hw.regulator.vcc-hdmi.max_uamp: 0 > > > > hw.regulator.vcc-hdmi.min_uamp: 0 > > > > hw.regulator.vcc-hdmi.max_uvolt: 3300000 > > > > hw.regulator.vcc-hdmi.min_uvolt: 3300000 > > > > hw.regulator.vdd-sys.uvolt: 1100000 > > > > hw.regulator.vdd-sys.always_on: 1 > > > > hw.regulator.vdd-sys.boot_on: 0 > > > > hw.regulator.vdd-sys.enable_cnt: 0 > > > > hw.regulator.vdd-sys.enable_delay: 0 > > > > hw.regulator.vdd-sys.ramp_delay: 0 > > > > hw.regulator.vdd-sys.max_uamp: 0 > > > > hw.regulator.vdd-sys.min_uamp: 0 > > > > hw.regulator.vdd-sys.max_uvolt: 1100000 > > > > hw.regulator.vdd-sys.min_uvolt: 1100000 > > > > hw.regulator.vcc-ddr3.uvolt: 1360000 > > > > hw.regulator.vcc-ddr3.always_on: 1 > > > > hw.regulator.vcc-ddr3.boot_on: 0 > > > > hw.regulator.vcc-ddr3.enable_cnt: 0 > > > > hw.regulator.vcc-ddr3.enable_delay: 0 > > > > hw.regulator.vcc-ddr3.ramp_delay: 0 > > > > hw.regulator.vcc-ddr3.max_uamp: 0 > > > > hw.regulator.vcc-ddr3.min_uamp: 0 > > > > hw.regulator.vcc-ddr3.max_uvolt: 1360000 > > > > hw.regulator.vcc-ddr3.min_uvolt: 1360000 > > > > hw.regulator.dcdc4.uvolt: 1100000 > > > > hw.regulator.dcdc4.always_on: 0 > > > > hw.regulator.dcdc4.boot_on: 0 > > > > hw.regulator.dcdc4.enable_cnt: 0 > > > > hw.regulator.dcdc4.enable_delay: 0 > > > > hw.regulator.dcdc4.ramp_delay: 0 > > > > hw.regulator.dcdc4.max_uamp: 0 > > > > hw.regulator.dcdc4.min_uamp: 0 > > > > hw.regulator.dcdc4.max_uvolt: 1300000 > > > > hw.regulator.dcdc4.min_uvolt: 500000 > > > > hw.regulator.dcdc3.uvolt: 1100000 > > > > hw.regulator.dcdc3.always_on: 0 > > > > hw.regulator.dcdc3.boot_on: 0 > > > > hw.regulator.dcdc3.enable_cnt: 0 > > > > hw.regulator.dcdc3.enable_delay: 0 > > > > hw.regulator.dcdc3.ramp_delay: 0 > > > > hw.regulator.dcdc3.max_uamp: 0 > > > > hw.regulator.dcdc3.min_uamp: 0 > > > > hw.regulator.dcdc3.max_uvolt: 1300000 > > > > hw.regulator.dcdc3.min_uvolt: 500000 > > > > hw.regulator.vdd-cpux.uvolt: 1100000 > > > > hw.regulator.vdd-cpux.always_on: 1 > > > > hw.regulator.vdd-cpux.boot_on: 0 > > > > hw.regulator.vdd-cpux.enable_cnt: 0 > > > > hw.regulator.vdd-cpux.enable_delay: 0 > > > > hw.regulator.vdd-cpux.ramp_delay: 0 > > > > hw.regulator.vdd-cpux.max_uamp: 0 > > > > hw.regulator.vdd-cpux.min_uamp: 0 > > > > hw.regulator.vdd-cpux.max_uvolt: 1300000 > > > > hw.regulator.vdd-cpux.min_uvolt: 1040000 > > > > hw.regulator.vcc-3v3.uvolt: 3300000 > > > > hw.regulator.vcc-3v3.always_on: 1 > > > > hw.regulator.vcc-3v3.boot_on: 0 > > > > hw.regulator.vcc-3v3.enable_cnt: 2 > > > > hw.regulator.vcc-3v3.enable_delay: 0 > > > > hw.regulator.vcc-3v3.ramp_delay: 0 > > > > hw.regulator.vcc-3v3.max_uamp: 0 > > > > hw.regulator.vcc-3v3.min_uamp: 0 > > > > hw.regulator.vcc-3v3.max_uvolt: 3300000 > > > > hw.regulator.vcc-3v3.min_uvolt: 3300000 > > > > hw.regulator.usb1-vbus.uvolt: 5000000 > > > > hw.regulator.usb1-vbus.always_on: 0 > > > > hw.regulator.usb1-vbus.boot_on: 1 > > > > hw.regulator.usb1-vbus.enable_cnt: 1 > > > > hw.regulator.usb1-vbus.enable_delay: 0 > > > > hw.regulator.usb1-vbus.ramp_delay: 0 > > > > hw.regulator.usb1-vbus.max_uamp: 0 > > > > hw.regulator.usb1-vbus.min_uamp: 0 > > > > hw.regulator.usb1-vbus.max_uvolt: 5000000 > > > > hw.regulator.usb1-vbus.min_uvolt: 5000000 > > > > > > > > On Tue, Oct 15, 2019 at 11:59 AM Emmanuel Vadot < > manu@bidouilliste.com> > > > > wrote: > > > > > > > > > On Tue, 15 Oct 2019 11:46:14 -0400 > > > > > Gary Otten wrote: > > > > > > > > > > > Thanks for your response. > > > > > > > > > > > > Freebsd Version 12.0-STABLE > > > > > > > > > > > > root@:/dev # sysctl hw.regulator.vcc-pe > > > > > > hw.regulator.vcc-pe.uvolt: 2800000 > > > > > > hw.regulator.vcc-pe.always_on: 1 > > > > > > hw.regulator.vcc-pe.boot_on: 0 > > > > > > hw.regulator.vcc-pe.enable_cnt: 0 > > > > > > > > > > That's the problem. > > > > > Can you try with hw.regulator.disable_unused=0 in > /boot/loader.conf ? > > > > > Something is wrong somewhere as we should enable this regulator > as the > > > > > always-on prop is set. I'll try to have a look this week. > > > > > > > > > > > hw.regulator.vcc-pe.enable_delay: 0 > > > > > > hw.regulator.vcc-pe.ramp_delay: 0 > > > > > > hw.regulator.vcc-pe.max_uamp: 0 > > > > > > hw.regulator.vcc-pe.min_uamp: 0 > > > > > > hw.regulator.vcc-pe.max_uvolt: 2800000 > > > > > > hw.regulator.vcc-pe.min_uvolt: 2800000 > > > > > > > > > > > > Yes I am testing the pins with a multimeter, I am not seeing any > voltage > > > > > > swings at all on Port E. On the external connector I see 5V on > pin 1, > > > > > 3.3 > > > > > > on pin 3 and the correct voltage( software setting) on the other > pins, > > > > > > except bank E. > > > > > > > > > > > > PB0-PB4 voltage corresponds to software setting. > > > > > > PC4,PC7 voltage corresponds to software setting. > > > > > > PE0-PE17 no voltage swings, doesn't work. > > > > > > PL7-PL12 voltage corresponds to software setting. > > > > > > > > > > > > I don't know if it will help, but if I make output on a pin > low, still > > > > > > when I switch the that pin from In to out, , I see a small > voltage swing > > > > > > in the milli volt range, but when I switch the PE pins from in > to out, I > > > > > > don't see that small swing. Its as if they is no software > connection to > > > > > > the PE pins. > > > > > > > > > > > > On Tue, Oct 15, 2019 at 7:18 AM Emmanuel Vadot < > manu@bidouilliste.com> > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > Hi Gary, > > > > > > > > > > > > > > On Mon, 14 Oct 2019 14:46:12 -0400 > > > > > > > Gary Otten wrote: > > > > > > > > > > > > > > > I have successfully booted the FreeBSD on the Olimex board > which has > > > > > the > > > > > > > > Allwinner A64. I have been experimenting with the gpios, > again with > > > > > > > > success. However the 40 pin connector on the Olimex board > exposes > > > > > GPIO > > > > > > > pins > > > > > > > > PB0 - PB4 which function normally (voltage corresponds to > software > > > > > > > setting > > > > > > > > for that pin) and then PE0-PE17 which don't. I have > played with > > > > > most > > > > > > > > of the PE0- PE17 pins with various settings, again nothing > works, no > > > > > > > signs > > > > > > > > of activity. I have successfully lit the LED (PE17) with the > armbian > > > > > > > > (linux) distribution for this board so I know it should work. > > > > > > > > > > > > > > > > Example > > > > > > > > gpioctl -f /dev/gpioc0 -c PB0 OUT > > > > > > > > gpioctl -f /dev/gpioc0 PB0 1 > > > > > > > > > > > > > > > > The pin PB0 then goes high (1) as expected. > > > > > > > > > > > > > > > > gpioctl -f /dev/gpioc0 -c PE17 OUT > > > > > > > > gpioctl -f /dev/gpioc0 PE17 1 > > > > > > > > > > > > > > > > No activity on PE17 > > > > > > > > > > > > > > > > > > > > > > > > I have dug into the the driver code a bit and the files > containing > > > > > the > > > > > > > > settings for this board/processor, but I have had no luck > figuring it > > > > > > > out. > > > > > > > > I have studied the Allwinner a64 manual but I haven't had > luck > > > > > figuring > > > > > > > > out any other settings that might work. I think I am > missing a > > > > > simple > > > > > > > > setting but can't figure it out, does anyone know how to get > pins > > > > > PE0 to > > > > > > > > PE17 to work? Thanks. > > > > > > > > > > > > > > What version of FreeBSD are you booting on this board ? > > > > > > > PE is a bit special on the Olinuxino as it's also used for > MIPI-CSI > > > > > > > and it's drived at 2.8V by default. It's using the regulator > ALDO1 from > > > > > > > the AXP PMIC and you should be able to confirm that it's > enabled by > > > > > > > doing sysctl hw.regulator.vcc-pe > > > > > > > Check for the .enable sysctl > > > > > > > It should be on as there is the always-on property in the DTS. > > > > > > > By default I think that the gpio pins are configured for 20mA > so I > > > > > > > don't know if it would be enough for this led. If you have a > multimeter > > > > > > > it would be good to confirm if you have any voltage on the ext > > > > > > > connector (you can use any PE pins, from what I see from the > schematics > > > > > > > they are all safe to play with). > > > > > > > > > > > > > > -- > > > > > > > Emmanuel Vadot > > > > > > > > > > > > > > > > > > > > > > -- > > > > > Emmanuel Vadot > > > > > > > > > > > > > > -- > > > 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" > > > > > > -- > > Emmanuel Vadot > > > -- > Emmanuel Vadot > From owner-freebsd-arm@freebsd.org Mon Oct 28 00:50:06 2019 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id E7CF315E345 for ; Mon, 28 Oct 2019 00:50:06 +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 471bj96Kh6z4LPP for ; Mon, 28 Oct 2019 00:50:05 +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 x9S0nhkB000973 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 27 Oct 2019 17:49:44 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id x9S0nhpv000972; Sun, 27 Oct 2019 17:49:43 -0700 (PDT) (envelope-from fbsd) Date: Sun, 27 Oct 2019 17:49:42 -0700 From: bob prohaska To: "O'Connor, Daniel" Cc: freebsd-arm@freebsd.org, bob prohaska Subject: Re: Permissions when moving storage devices between hosts Message-ID: <20191028004942.GA932@www.zefox.net> References: <20191026163920.GA38958@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-Rspamd-Queue-Id: 471bj96Kh6z4LPP X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of fbsd@www.zefox.net has no SPF policy when checking 50.1.20.27) smtp.mailfrom=fbsd@www.zefox.net X-Spamd-Result: default: False [0.13 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.88)[-0.879,0]; WWW_DOT_DOMAIN(0.50)[]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; IP_SCORE(0.08)[ip: (0.33), ipnet: 50.1.16.0/20(0.16), asn: 7065(-0.04), country: US(-0.05)]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[zefox.net]; AUTH_NA(1.00)[]; NEURAL_HAM_LONG(-0.97)[-0.969,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US]; MID_RHS_MATCH_FROM(0.00)[]; MID_RHS_WWW(0.50)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Oct 2019 00:50:07 -0000 On Mon, Oct 28, 2019 at 10:33:23AM +1030, O'Connor, Daniel wrote: > > > > On 27 Oct 2019, at 03:09, bob prohaska wrote: > > The plan was to re-run the bonnie test on the second host to see if the > > choice of host made much difference. Alas, after mounting the card, all > > owners/groups are freebsd/freebsd and I can't get permission to write > > any files, at least as a regular user. The usernames are the same on > > both hosts and I'm hesitant to try mucking about with ownerships. > > It does not seem possible to simply add world-write permissions to the > > test directory using chmod +w as root. > > Is it mounted read/write? > ie show the output of 'mount'. > No, I wanted to add write permission, which failed silently even when chmod was run by root. . > Also note that the filesystem only stores user IDs not user names. > > ie you might have a user called 'freebsd' on two systems but with different IDs and if you move an FS between them you can have issues. > That was probably the mistake I made. Like usernames, but unlike IDs. > That said, root should be able to change the permissions (or just write since being root skips permission checks). If it can't then it seems more like it isn't mounted read/write for whatever reason (write protect tab on the SD card set by accident?) > In the end, it was enough to just chown the one directory I needed to write to. I didn't want to run the disk test as root Thanks for writing, bob prohaska From owner-freebsd-arm@freebsd.org Mon Oct 28 04:05:28 2019 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id B169316656C for ; Mon, 28 Oct 2019 04:05:28 +0000 (UTC) (envelope-from sales@feitdz.com) Received: from mail-pg1-x543.google.com (mail-pg1-x543.google.com [IPv6:2607:f8b0:4864:20::543]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 471h2b1nd9z4TBV for ; Mon, 28 Oct 2019 04:05:27 +0000 (UTC) (envelope-from sales@feitdz.com) Received: by mail-pg1-x543.google.com with SMTP id 15so5950416pgt.7 for ; Sun, 27 Oct 2019 21:05:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=feitdz-com.20150623.gappssmtp.com; s=20150623; h=mime-version:date:content-transfer-encoding:content-disposition :from:subject:to:reply-to:message-id:in-reply-to; bh=BEF8EfYfKHe+w/jXd/bjrb5clMwUykCthChF2MXZ7XA=; b=gLcbYfAniqlDo6WHyJHbZ+Pj94dzVA+ycrehLLuPa+wU/TkZHO/SxknE8AD+WlVMlw 79cfwwqa8t6iFEa6k9wNDbmCX+IM0t5Cd2nxw+HZiwv4hLNkkUx5T5RrcPw0UMRXLTL6 FadD7bsaanlmYxfIqiuAdJxzA1/VN58RKyT/OS1XQ4PxtgVDyEkRNlu2L3u0jbRpEx0i j/9fPv8aSidHqiOoSyi9hMywr6nAgFYjK8GyBHqjOHZLJUBnFwytt33hygp1B1IPIGMa gH4Sb8YLaIgHRLBMMsGVE5J5oEHPB5syvE3ZEMVLNy2d96rZBPbgk4eJttIIphVpoV7L zbTg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:date:content-transfer-encoding :content-disposition:from:subject:to:reply-to:message-id:in-reply-to; bh=BEF8EfYfKHe+w/jXd/bjrb5clMwUykCthChF2MXZ7XA=; b=gAepyGta0Ep5SgMGUYAzlM9GIIApMZ5WaG2GFy6OUT+iccDrvMMABLfGWHkBIBvXqF nGaaN88+JgMpAiD57I9veJL8hhefr4jYuT5fcxbbAsEOAoSOHpRknkp/wvExb+TaPuvj bqViQizyyYSpDcKG6V5pI9ZfN4czS2rKGRlBCWiMf45Ra0qtqa1NSAwCi6n0LLtYm2gv KT97O87ZEpn6feShdRKOe9vJ/UYu4wUNptDWRRAVmABzFY2oCBaxr+PJaW9uinDJ4DE9 DytmItHXAT8vlujSm8Q9cagKOij2JPp30Rvj0kvL8vvkk5KArPHlaIQ20BEwb2zgu3+r VBNQ== X-Gm-Message-State: APjAAAUhX+25Ez20t2wiaeEpXLHSqtQiZClarX3oe/HboV3tTs+nDCOJ 6AyD4LJjeHU7OQID5UP1e0A/s01zJxM= X-Google-Smtp-Source: APXvYqzcWvdtdMx0QuYhpCUVynUtn9blz9cTKcgsJXRWQS2jACW7nd8HVUDoGcexXS6xnmCneQV8Fw== X-Received: by 2002:a17:90a:c717:: with SMTP id o23mr19641989pjt.88.1572235525242; Sun, 27 Oct 2019 21:05:25 -0700 (PDT) Received: from YOS-01807191143 (n112120101220.netvigator.com. [112.120.101.220]) by smtp.gmail.com with ESMTPSA id y80sm10095524pfc.30.2019.10.27.21.05.23 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 27 Oct 2019 21:05:24 -0700 (PDT) MIME-Version: 1.0 Date: Mon, 28 Oct 2019 12:05:56 +0800 From: "sales@feitdz.com" Subject: Reliable OEM & ODM USB Flash Drives Supplier To: freebsd-arm@freebsd.org Reply-To: sales@feitdz.com Message-ID: <2019100028120500560901@feitdz.com> X-Mailer: Foxmail 6, 13, 102, 15 [cn] In-Reply-To: <2019100028120500560901@feitdz.com> X-Rspamd-Queue-Id: 471h2b1nd9z4TBV X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=feitdz-com.20150623.gappssmtp.com header.s=20150623 header.b=gLcbYfAn; dmarc=none; spf=pass (mx1.freebsd.org: domain of sales@feitdz.com designates 2607:f8b0:4864:20::543 as permitted sender) smtp.mailfrom=sales@feitdz.com X-Spamd-Result: default: False [-1.47 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; HAS_REPLYTO(0.00)[sales@feitdz.com]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; TO_DN_NONE(0.00)[]; REPLYTO_ADDR_EQ_FROM(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[feitdz-com.20150623.gappssmtp.com:+]; MIME_BASE64_TEXT(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; IP_SCORE(-1.07)[ip: (-0.83), ipnet: 2607:f8b0::/32(-2.40), asn: 15169(-2.05), country: US(-0.05)]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; R_DKIM_ALLOW(-0.20)[feitdz-com.20150623.gappssmtp.com:s=20150623]; FROM_DN_EQ_ADDR(1.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; DMARC_NA(0.00)[feitdz.com]; HTML_SHORT_LINK_IMG_2(1.00)[]; RCPT_COUNT_ONE(0.00)[1]; RCVD_IN_DNSWL_NONE(0.00)[3.4.5.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; RCVD_TLS_ALL(0.00)[] Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: Base64 Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Oct 2019 04:05:28 -0000 SGkgZ29vZCBkYXksDQpIb3BlIGV2ZXJ5dGhpbmcgZ29lcyB3ZWxsIHdpdGggeW91Lg0KSSBhbSBK YXNvbiBMZWUgZnJvbSBGZWl0IERpYW56aSBjb21wYW55Lg0KV2UgYXJlIG9uZSBvZiB0aGUgYmVz dCBwcm9mZXNzaW9uYWwgYW5kIHJlbGlhYmxlIE9FTSAmIE9ETSBVU0IgZmxhc2ggZHJpdmVzIGZh Y3RvcmllcyBpbiBTaGVuemhlbiBzaW5jZSAyMDA2LiBXZSB1c2UgYnJhbmQgYW5kIGdyYWRlIEEg Y2hpcHNldCBhbmQgZ2l2ZSAxIHllYXIgcXVhbGl0eSB3YXJyYW50eS4gDQpUaGUgZm9sbG93aW5n IGRlc2lnbnMgb24gRUMyMS5jb20gYXJlIHBhcnQgb2YgdGhlIG1vZGVscyB3ZSBwcm9kdWNlOiAN CuKXjyBQcm9tb3Rpb25hbCBjbGFzc2ljIFVTQiBkcml2ZXMNCuKXjyBVU0IgcGVuIGRyaXZlcw0K 4pePIExlYXRoZXIgVVNCIGRyaXZlcw0K4pePIFdvb2QvYmFtYm9vIFVTQiBkcml2ZXMNCuKXjyBN ZXRhbCBVU0IgZHJpdmVzDQril48gQ3J5c3RhbCBVU0IgZHJpdmVzDQril48gU2lsaWNvbmUgVVNC IGRyaXZlcw0K4pePIE5ldyBtb2xkaW5nIGN1c3RvbSBzb2Z0IFBWQyBVU0IgZHJpdmVzDQril48g SmV3ZWxyeSBVU0IgZHJpdmVzDQril48gQ2FyZCBzaGFwZWQgVVNCIGRyaXZlcw0K4pePIFdhdGVy cHJvb2YgVVNCIGRyaXZlcw0K4pePIFBhc3N3b3JkIHByb3RlY3Rpb24gVVNCIGRyaXZlcw0K4peP IE1pbmkgVVNCIGRyaXZlcw0K4pePIFJlY3ljbGVkIHBhcGVyIFVTQiBkcml2ZXMNCuKXjyBTbWFy dHBob25lIE9URyAyLWluLTEgVVNCIGRyaXZlcw0K4pePIFNtYXJ0cGhvbmUgT1RHIDMtaW4tMSBV U0IgZHJpdmVzDQril48gU21hcnRwaG9uZSBPVEcgNC1pbi0xIFVTQiBkcml2ZXMNCuKXjyBTcGVj aWFsICBzaGFwZWQgVVNCIGRyaXZlcw0K4pePIFVTQiB3ZWJrZXkNCk91ciB0b2RheSdzIHByaWNl IGxpc3Qgd2lsbCBiZSBzZW50IHRvIHlvdSBpZiB5b3UgaGF2ZSBhbnkgaW50ZXJlc3QgaW4gdGhl c2UuIA0KTG9vayBmb3J3YXJkIHRvIGhlYXJpbmcgZnJvbSB5b3UuIA0KQmVzdCByZWdhcmRzLCAN Ckphc29uIExlZQ0KRmVpdCBEaWFuemkgQ28uLEx0ZA0KRW1haWw6IHNhbGVzQGZlaXRkei5jb20N ClRlbDogKCs4NikgNzU1LTgzMjcgNjA0MA0KRmF4OigrODYpIDc1NS04MzI3IDYwMzUNCk1vYmls ZSAmIFdlY2hhdCBJRDogMDA4NjEzNjMyNzExMzMwDQpBZGRyZXNzOjN0aCBGbG9vciwgQnVpbGRp bmcgNSwgSGVzaGVuZyBJbmR1c3RyeSBab25lLEZ1eW9uZyBUb3duLEJhbydhbiBEaXN0LCBTaGVu emhlbixDaGluYSA1MTgxMjYuDQo= From owner-freebsd-arm@freebsd.org Mon Oct 28 10:58:12 2019 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 8720917DF65 for ; Mon, 28 Oct 2019 10:58:12 +0000 (UTC) (envelope-from s199p.wa1k9r@gmail.com) Received: from mail-lj1-x22f.google.com (mail-lj1-x22f.google.com [IPv6:2a00:1450:4864:20::22f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 471sBp6XlHz3Jjv for ; Mon, 28 Oct 2019 10:58:10 +0000 (UTC) (envelope-from s199p.wa1k9r@gmail.com) Received: by mail-lj1-x22f.google.com with SMTP id l21so10806731lje.4 for ; Mon, 28 Oct 2019 03:58:10 -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=u95mUHJ9U5ZrS6gKInj3vELVzfR2ufHatIVJ/ly9VQo=; b=gLjP3IznVChHYnZ1tiflLWnffMjh6IR3iGD+dmMMWMSd4v5G3ZISgzesuFc1IPoOAX a2k3lAbfiWVuXIgWiBWtbE+NMsY6IP+zU2gELinNPvkbdxtEad4JIW5DsjkUPgI0QkfQ Pd7LXE1+eqiZsBqWIvdi7jUrQvB9PIavraKDvp3BGNuIpxQOSam8q97riABJHiyVweqh h24rHmbgR85+FD6m9HtQAvH/ooYJBxCzjDlk9UOk0KdNvUbI8KD//m52Gu+4V2CF14nh 7ZSIi897Hm7owO7MbR7zgghHo5+pQaBO9Gj1NB5IL10D2WycMZwM98Sr+qkiZn25GL6L jjFQ== 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=u95mUHJ9U5ZrS6gKInj3vELVzfR2ufHatIVJ/ly9VQo=; b=FVf6DexNen0WCVUiU9JVdQgykeHzT9rmijFCq/vt9nBTTqJIVu2KauGRDRJng2Acrr iwrKjNDRdcozHGevKXkSC0jgsEonQO0qNrdIHyajMLSkjiib3CUI+7tnOWEuic6lDXJU xeiCyYPjoX0VJ4EV7IeiG3oR2YArHPRm1P0RTJFWy9bcdVVz76Gp8GqtZyumbchC/fLr XxFvvWgUCXlugCsdTgbMTbyzn1qvFORY0CJjzkJEqy3paVF0/pWBDjMdKHS+Hbkq5iNk CIrFxpTxha38yVWJs7A+3lKE8lMgsR5KegDn5N9R0cqwd7F+Z0AormugxFYfCKRmUeOJ Tuxw== X-Gm-Message-State: APjAAAVZoPiOz3CJbNr8EjPl7bsZDNu/76U+H3C+BJG7+xUu3tL7wySG jUAVrEeOkLAych6056ojZoXOrPi5ghINqykyyLZyFHDd6ss= X-Google-Smtp-Source: APXvYqyOD4GuK4mwc5p8aNFwdrAJfVtN5ba0Mgp3+XV5X+TLZapMSRQJLpxRvlcyTUb7ZHyuefM/JV1OK6J9H4dcoAE= X-Received: by 2002:a2e:207:: with SMTP id 7mr11292841ljc.198.1572260288162; Mon, 28 Oct 2019 03:58:08 -0700 (PDT) MIME-Version: 1.0 From: Sleep Walker Date: Mon, 28 Oct 2019 13:57:57 +0300 Message-ID: Subject: FreeBSD 13-CURRENT download status on RK3399 SBC`s To: freebsd-arm@freebsd.org X-Rspamd-Queue-Id: 471sBp6XlHz3Jjv X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=gLjP3Izn; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of s199pwa1k9r@gmail.com designates 2a00:1450:4864:20::22f as permitted sender) smtp.mailfrom=s199pwa1k9r@gmail.com X-Spamd-Result: default: False [-2.00 / 15.00]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; TO_DN_NONE(0.00)[]; URI_COUNT_ODD(1.00)[3]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; FROM_EQ_ENVFROM(0.00)[]; IP_SCORE(0.00)[ip: (-9.21), ipnet: 2a00:1450::/32(-2.80), asn: 15169(-2.05), country: US(-0.05)]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; TAGGED_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; IP_SCORE_FREEMAIL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; RCVD_IN_DNSWL_NONE(0.00)[f.2.2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Oct 2019 10:58:12 -0000 Hi All! On Khadas-EDGE-V - mainline uboot U-Boot TPL 2019.10-rc3 - bootup from SD - eth OK - uart OK - emmc OK - sd OK - USB 2.0 OK - USB 3.0 OK - USB HID OK - USB DISK OK On Rock Pi4 UEFI booting, very cool. But I can not log into the console. it seems it keeps rebooting. Here is the log: https://pastebin.com/JFX7Ssnz From owner-freebsd-arm@freebsd.org Mon Oct 28 11:10:37 2019 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 7903117E1F7 for ; Mon, 28 Oct 2019 11:10:37 +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 471sT802Qrz3K50; Mon, 28 Oct 2019 11:10:35 +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 6e4e6a73; Mon, 28 Oct 2019 12:10:27 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; s=mail; bh=qGiJUC9bDnXBbTr0BBn9GLdVVjw=; b=gxA77l4CEJHKD5NkmyHEwL337tu1 MgcBvsV7QePPYGgVxGZAZRk9HOa9jJDT3qBz5SLNgFxJLUDCjwgRjmUubZaX/5Wd 9ioKx/72kMJENwuzEPMd4AgcYSRSx7+n8ZEs3Bi5RgGiyA6fP+DxmugdIsZVAjaK ZBeo9Kv8tBrJGPM= 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=bts623GtN77C27ldsk+Enk5yc7DRe2Ytik2/cV6v3OtOUgREKrvjb/Zm EtXKQBtOuUaPpn7/ROWuj3K5BeaxNEl6G2HsyfMFvOHjCSOD334yEz/TvD+MgH54 4j58p6lcqQrjyX1VBrIJnRNrqnuDpPdZJ9v31KrQPQLHs2KKo2A= Received: from sonic.home.blih.net (ip-9.net-89-3-105.rev.numericable.fr [89.3.105.9]) by mail.blih.net (OpenSMTPD) with ESMTPSA id 2be09c19 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Mon, 28 Oct 2019 12:10:27 +0100 (CET) Date: Mon, 28 Oct 2019 12:10:27 +0100 From: Emmanuel Vadot To: Sleep Walker Cc: freebsd-arm@freebsd.org, mmel@freebsd.org Subject: Re: FreeBSD 13-CURRENT download status on RK3399 SBC`s Message-Id: <20191028121027.8c89aef2a2809cd844ccad80@bidouilliste.com> In-Reply-To: References: X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; amd64-portbld-freebsd13.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 471sT802Qrz3K50 X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bidouilliste.com header.s=mail header.b=gxA77l4C; dmarc=none; spf=pass (mx1.freebsd.org: domain of manu@bidouilliste.com designates 212.83.177.182 as permitted sender) smtp.mailfrom=manu@bidouilliste.com X-Spamd-Result: default: False [-1.15 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[bidouilliste.com:s=mail]; NEURAL_HAM_MEDIUM(-0.67)[-0.672,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+ip4:212.83.177.182/32]; MV_CASE(0.50)[]; TAGGED_RCPT(0.00)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[bidouilliste.com]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-0.96)[-0.960,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[bidouilliste.com:+]; FREEMAIL_TO(0.00)[gmail.com]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; IP_SCORE(0.39)[ip: (-0.61), ipnet: 212.83.160.0/19(2.44), asn: 12876(0.10), country: FR(-0.00)]; ASN(0.00)[asn:12876, ipnet:212.83.160.0/19, country:FR]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Oct 2019 11:10:37 -0000 On Mon, 28 Oct 2019 13:57:57 +0300 Sleep Walker wrote: > Hi All! > > On Khadas-EDGE-V > > - mainline uboot U-Boot TPL 2019.10-rc3 > - bootup from SD > - eth OK > - uart OK > - emmc OK > - sd OK > - USB 2.0 OK > - USB 3.0 OK > - USB HID OK > - USB DISK OK Good to know that everything is working on this board too. > > On Rock Pi4 > > UEFI booting, very cool. > > But I can not log into the console. > > it seems it keeps rebooting. > > Here is the log: > https://pastebin.com/JFX7Ssnz This is known. Let me try to describe the problem. So the sd and emmc clock have multiple possible parent, one of them is the usb clock that is generated by the usb controller. The problem is that when we create the clock domain of the CRU (Clock and Reset Unit) the usb controller isn't probed yet because it needs clock from the CRU. When a clock domain is finished (by calling clkdom_finit) we need all the clocks to be present so we cannot add the unknown for now usb clock. So to fix this issue we need a way to create a fake clock when the CRU clock domain is created that will be later replaced by the usb controller. There is multiple approch to this and I'm not yet sure which one will work best. 1) We allow to list non-existing clock as parent and don't throw errors anymore at clkdom_finit but at some SYSINIT. This will work well with a big static kernel but not if the clock is created by a kernel module. 2) We create some fake clock domain where we can add clocks to it so it became a somewhat valid parent (but not usable so you cannot select it with clknode_set_parent for example) and when a clock domain is finished we remove clock from the fake domain that are present in the newly created one (as clock names are unique this should not cause problem). The question is then what should we do when we still have clock in the fake domain ? Maybe mmel@ have more ideas. -- Emmanuel Vadot From owner-freebsd-arm@freebsd.org Mon Oct 28 11:59:35 2019 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 212D017F0AA for ; Mon, 28 Oct 2019 11:59:35 +0000 (UTC) (envelope-from melounmichal@gmail.com) Received: from mail-wr1-x441.google.com (mail-wr1-x441.google.com [IPv6:2a00:1450:4864:20::441]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 471tYf27JWz3Lyq for ; Mon, 28 Oct 2019 11:59:34 +0000 (UTC) (envelope-from melounmichal@gmail.com) Received: by mail-wr1-x441.google.com with SMTP id n1so2114237wra.10 for ; Mon, 28 Oct 2019 04:59:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:from:reply-to:subject:to:cc:references:openpgp:autocrypt :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=3kcnkZ4VM5hNVQ1vK0V7bO4aqr7TufFXW3zOn0oBq9k=; b=LqP6qtAfUpbTzh9zeZOdKrgUEnQMk7hDLuD9Zs/VAl9jC7SeemqVmjUS1Wamiwsnx5 0EW3/yienuP4PN0qVCLSclxAo3iXWBH+EW6+V4sj8rja/8y89shNFZRBeePBdt9VP6jM 8hjJ0J1pRvbdZJ2wanWmyyq+ESpqsxZMuxYoqk2Ov4JZQ4+ozlrvKQcGak2dox91Mpmd IcICsIF7HAZQdsjru7ZZNgk7qghw4DJYFcCFAaTiPIRoHG+lp3l2BN6FriIidGhyLpu1 bw6Z9Frd7h/Vb/S2kOubphkOeRnJqfvY8xccpx0ERHhi6eXjwUwB1XR93XtB6H+mIgQT yoEw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:from:reply-to:subject:to:cc:references :openpgp:autocrypt:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=3kcnkZ4VM5hNVQ1vK0V7bO4aqr7TufFXW3zOn0oBq9k=; b=IDMbMW+Vk80aEdXZVxK0WdTeRWw5iG4+uepS91MVmHR4/IaKwdQRT6fRWjY9sTgRZb 2bJIHNVEspGry0kLUpPz4yw8n+okJpBFXGBSvab9q2PH5rIaCU8PJF+RXfeUs6rMD2hQ HQQmm4m59Eq+MlZbZgCKL2wfwa6jsxjOXfjNNZewtsAig6y5QjCxpgtOqni438bb/zpY xZ6grOnDsKRULCt2ea2dUrxABUkU2y3xepSKVj3y+OUCUTuxIrow22CQFtFDD5r0/TVo uTmJgcJykZKCrtK0TRmaKj3GBujYUh5dDDx+KmOikuI8rfYTw/xFp80iZ4ym/nRK8uGH StYg== X-Gm-Message-State: APjAAAUgdUhBFnvYDD2ZtWYQS6mlMujA2obmZd7Aydrf1uOBuuPPPzCU RRUmFhdlA4WWYndtA6vdIIQjcBoH X-Google-Smtp-Source: APXvYqys+hrFZKqDiGUBm7Mul5jnze/HivZE5W39r9PABz064TTR6XWQa9GoIkNPd4JCPN6BjSGUxw== X-Received: by 2002:adf:e882:: with SMTP id d2mr15226436wrm.132.1572263972692; Mon, 28 Oct 2019 04:59:32 -0700 (PDT) Received: from [88.208.79.100] (halouny.humusoft.cz. [88.208.79.100]) by smtp.gmail.com with ESMTPSA id r11sm8409056wrx.67.2019.10.28.04.59.31 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 28 Oct 2019 04:59:32 -0700 (PDT) Sender: Michal Meloun From: Michal Meloun X-Google-Original-From: Michal Meloun Reply-To: mmel@freebsd.org Subject: Re: FreeBSD 13-CURRENT download status on RK3399 SBC`s To: Emmanuel Vadot , Sleep Walker Cc: freebsd-arm@freebsd.org References: <20191028121027.8c89aef2a2809cd844ccad80@bidouilliste.com> Openpgp: preference=signencrypt Autocrypt: addr=mmel@freebsd.org; prefer-encrypt=mutual; keydata= mQENBFYuVRkBCADZiwLCCne3wG9b9k+R2Neo5zVo2bLaZRfNNY/v9kg283i0sb1Da4EdEiNT 15El5UyozhphUIbIR/zrVpxF1TvvFdoCyzx6a68bNY2d9dBrDcNDZC+XnyDdHQoobN87DWT1 mRVkmbg9LHZ/SVUOkGYuWyE+8UYeDAcUizuXwSK5zFWmeTyIoWNa68ifrWLfQe0p4x5jC/AI VURCi17p360vU4fhgwoMvEEhrRBWCr4DYHToFjIt2WdBy3GR1qoO0+Xkd6G+OoBULo+XDfgu L2WdPvh0K69F9/LgHkMmG5Il7SCe62QGpG2vaCgRV7BQhLX+kxlvM+WrdRatWRml4Y/3ABEB AAG0IE1pY2hhbCBNZWxvdW4gPG1tZWxAZnJlZWJzZC5vcmc+iQFXBBMBCgBBAhsDBQsJCAcD BRUKCQgLBRYDAgEAAh4BAheAAhkBFiEEAN1KEEuAn+Apg413aR6ya17FqqoFAlw3aO8FCQ9v FVYACgkQaR6ya17FqqrIFwf/V/NRuAutw1cZ/HRCwfp00KY+8g730KwOaAMhPYvq8tqf8krD whFRWt9s4DSVTVJUC2dRZa5g1MS77iQL/WWzBUhJj7rW4uMpcKpi7UXi060sKrnE+1ZBvanG 8YCMTHKxQgQDD0cBqsyOAfrSA+Pyya3/HyAh1vvjQZfu5vWxA1X5NX5l5KtonprJ+ybVacwO W34yfWSX+ncx089JpUknenGdI+gVoKfa6uh/8YiCZTI5poxBttrOB8NGfylTsTTTbw2pkire Vkc87qq++I9bBNtTqWOZjB/3KBUd4q1veEUa4MS63TWtAvcEcsxHiBv4AH6npPO/iPycuGGh qldT1LkBDQRWLlUZAQgAuqBGR9LbUP86pYT2Zd+HZsiOun24LxPQwK6KZuysB0so02isa7ac T6t5uBfyfmdgzfvsc6dqU8bI65e8JtDwwVVF1Y4fF6cmNcmJqU10Gw5/bAu9re9JJWx2g/OJ tYMhwmqEE5DcS6GwgvJZI+9hgoSLL3mZ+GsO25NM4BhVH1o1AE4Q3O0HZMMnIzH+pma0augZ Xc3Qep17/Occ+1A7xEbn8VAYx8cwjkYUy7JyvVx4ecuj+i+uoCXhNhX5QdIcn4UMT1233Bcd yVZtZsLTI26ByFmrquGjkmN+/hra/s+nKfcegOKeHWVY/uFgDRk0TEYd6QuddZWo7+XMZLps wQARAQABiQElBBgBCgAPAhsMBQJZjBHDBQkHICOqAAoJEGkesmtexaqquysH/iDgRIrlMvFT GLyktZws/K/C03gWZ/tWwJV5+SFqRoasM+Z+9+cb44XA3rReqieLsYF5qSXTXHBPhEg1+9V9 KEPLpwektLtAv8zynN+6VVffwyRWQ4PIZmHCMT6PJP+Rk0DU6VrDc3ch58erduuyRDsbh32g 96nYMNvDsLhDvq44GPHLfglUHRY6wHo3IxAH2HosaWNC10R13JSrCdFnPMeIa+nSE+11hAdB mWpuPgVX2VNErtrwSBr7LsyCZ4yLO0bN5fKM0/Tavc9EcI9qDBrnts/EfZoCHhDtTMEFnQZM ybsMso20I/nxYPFuWuuFn7uQeoYrwWxt15SkN0RgtV2JATwEGAEKACYCGwwWIQQA3UoQS4Cf 4CmDjXdpHrJrXsWqqgUCXDdpmwUJD28WAgAKCRBpHrJrXsWqqtOrB/9Okk/dm2/mAs3tbA6l lKOZAwfUwBonwG7YhK9dOb5No/bJoY8G9s2IVXqwWKqCDv1qKC4M8pMXPD9fVsfNPG8GA1GZ rpZoZxHFteXZHoE1grpWypE0T3hp1W0hQNWXKv0MSuEMRVKU1m/iyLa10X7q8BaKtEDs35Xf DCh7eVg1vqiKtWyFn1u+y9Gy1Ztc/SKTs8mQvMYNUdBZuV6vN0VSz3I6wD9HVfo6Eo3M7cVp qqQ+KhrrGiCCYQPfZwpFAJSSgV3bR5O0BlNaGKJOoVTV1yexRbVEStswiFP8JFQp6U+S3nqE FFob7daQBLxi80oUVRn6eEdzR8tBhIy7sbeD Message-ID: <150c9db3-26f9-bd3b-eb16-c2801d6944f6@freebsd.org> Date: Mon, 28 Oct 2019 12:59:30 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0 MIME-Version: 1.0 In-Reply-To: <20191028121027.8c89aef2a2809cd844ccad80@bidouilliste.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 471tYf27JWz3Lyq X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=LqP6qtAf; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of melounmichal@gmail.com designates 2a00:1450:4864:20::441 as permitted sender) smtp.mailfrom=melounmichal@gmail.com X-Spamd-Result: default: False [-3.00 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; HAS_REPLYTO(0.00)[mmel@freebsd.org]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; TAGGED_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TAGGED_RCPT(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; REPLYTO_DOM_NEQ_FROM_DOM(0.00)[]; MIME_GOOD(-0.10)[text/plain]; IP_SCORE_FREEMAIL(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[1.4.4.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; IP_SCORE(0.00)[ip: (2.73), ipnet: 2a00:1450::/32(-2.80), asn: 15169(-2.05), country: US(-0.05)]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Oct 2019 11:59:35 -0000 On 28.10.2019 12:10, Emmanuel Vadot wrote: > On Mon, 28 Oct 2019 13:57:57 +0300 > Sleep Walker wrote: > >> Hi All! >> >> On Khadas-EDGE-V >> >> - mainline uboot U-Boot TPL 2019.10-rc3 >> - bootup from SD >> - eth OK >> - uart OK >> - emmc OK >> - sd OK >> - USB 2.0 OK >> - USB 3.0 OK >> - USB HID OK >> - USB DISK OK > > Good to know that everything is working on this board too. > >> >> On Rock Pi4 >> >> UEFI booting, very cool. >> >> But I can not log into the console. >> >> it seems it keeps rebooting. >> >> Here is the log: >> https://pastebin.com/JFX7Ssnz > > This is known. Let me try to describe the problem. > So the sd and panic: clknode_init_parent_idx: Invalid parent index 5 for clock sclk_sdmmc have multiple possible parent, one of them is > the usb clock that is generated by the usb controller. The problem is > that when we create the clock domain of the CRU (Clock and Reset > Unit) the usb controller isn't probed yet because it needs clock from > the CRU. When a clock domain is finished (by calling clkdom_finit) we > need all the clocks to be present so we cannot add the unknown for now > usb clock. > So to fix this issue we need a way to create a fake clock when the CRU > clock domain is created that will be later replaced by the usb > controller. There is multiple approch to this and I'm not yet sure > which one will work best. > > 1) We allow to list non-existing clock as parent and don't throw > errors anymore at clkdom_finit but at some SYSINIT. > This will work well with a big static kernel but not if the clock is > created by a kernel module. > 2) We create some fake clock domain where we can add clocks to it so > it became a somewhat valid parent (but not usable so you cannot select > it with clknode_set_parent for example) and when a clock domain is > finished we remove clock from the fake domain that are present in the > newly created one (as clock names are unique this should not cause > problem). The question is then what should we do when we still have > clock in the fake domain ? > > Maybe mmel@ have more ideas. > All above is right but is not related to this panic "panic: clknode_init_parent_idx: Invalid parent index 5 for clock sclk_sdmmc". In this case, the parent clock at index 5 for sclk_sdmmc (named "clk_sdmmc in TRM) is CLK_24M (at least in my TRM). Problem (for me) is that rockchip clock code is slightly incomplete and it uses different nomenclature (naming) that is in TRM. Unfortunately, putting right clock for this index doesn't helps much, my RockPRo64 still fails with another (not yet identified)problem. I currently working on proper (i hope) solution for this problem -> something like soft-link clock node - a pure pass-throw node, which can link clock between domains used for cross-domain clock linking. Michal From owner-freebsd-arm@freebsd.org Mon Oct 28 12:24:01 2019 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id B2A021A139D for ; Mon, 28 Oct 2019 12:24:01 +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 471v5s233Nz3NYV; Mon, 28 Oct 2019 12:24:00 +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 ca3e20f4; Mon, 28 Oct 2019 13:23:58 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; s=mail; bh=eYgQlaMbTJu9Ot6MGfqtvNWxUFU=; b=CnPcCrKFwhl5Fwutx9PnVVnEcZoQ UVO8CXTC1c/Rxl+ZAbkc3WTEC34LLnvz9de/Y821C853IQ4OKJfPG5Ua/Gl8zDZW udLBWbLXowcCSocog/3H9Fsa8Xhd4jAwxf+erF/xOyqFSV2aVyaJ2pN9civUrKJ8 MAVp4YVUnbNu3sg= 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=joq0JkPgOCVX2dcozH+5e6TWoeh8ysTBIFo0Atp6ynH+UCrneaBpU+Z7 kb8jgIMr+avrfx9OsHbK4X24Lo9+G0otbl3qpSh2d5tMQ1qhv7sHp5Q13KdlOcZV W3Z+ZpTLC3BYoltwcPGe3nudnDNRbJ8Z+E/3ro6DWtk1NMGWO8c= Received: from sonic.home.blih.net (ip-9.net-89-3-105.rev.numericable.fr [89.3.105.9]) by mail.blih.net (OpenSMTPD) with ESMTPSA id 58b739b8 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Mon, 28 Oct 2019 13:23:58 +0100 (CET) Date: Mon, 28 Oct 2019 13:23:58 +0100 From: Emmanuel Vadot To: mmel@freebsd.org Cc: Michal Meloun , Sleep Walker , freebsd-arm@freebsd.org Subject: Re: FreeBSD 13-CURRENT download status on RK3399 SBC`s Message-Id: <20191028132358.cd225b5127fb7396c11c4585@bidouilliste.com> In-Reply-To: <150c9db3-26f9-bd3b-eb16-c2801d6944f6@freebsd.org> References: <20191028121027.8c89aef2a2809cd844ccad80@bidouilliste.com> <150c9db3-26f9-bd3b-eb16-c2801d6944f6@freebsd.org> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; amd64-portbld-freebsd13.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 471v5s233Nz3NYV X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-5.99 / 15.00]; NEURAL_HAM_MEDIUM(-0.99)[-0.993,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TAGGED_RCPT(0.00)[]; REPLY(-4.00)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Oct 2019 12:24:01 -0000 On Mon, 28 Oct 2019 12:59:30 +0100 Michal Meloun wrote: > > > On 28.10.2019 12:10, Emmanuel Vadot wrote: > > On Mon, 28 Oct 2019 13:57:57 +0300 > > Sleep Walker wrote: > > > >> Hi All! > >> > >> On Khadas-EDGE-V > >> > >> - mainline uboot U-Boot TPL 2019.10-rc3 > >> - bootup from SD > >> - eth OK > >> - uart OK > >> - emmc OK > >> - sd OK > >> - USB 2.0 OK > >> - USB 3.0 OK > >> - USB HID OK > >> - USB DISK OK > > > > Good to know that everything is working on this board too. > > > >> > >> On Rock Pi4 > >> > >> UEFI booting, very cool. > >> > >> But I can not log into the console. > >> > >> it seems it keeps rebooting. > >> > >> Here is the log: > >> https://pastebin.com/JFX7Ssnz > > > > This is known. Let me try to describe the problem. > > So the sd and panic: clknode_init_parent_idx: Invalid parent index 5 for clock sclk_sdmmc have multiple possible parent, one of them is > > the usb clock that is generated by the usb controller. The problem is > > that when we create the clock domain of the CRU (Clock and Reset > > Unit) the usb controller isn't probed yet because it needs clock from > > the CRU. When a clock domain is finished (by calling clkdom_finit) we > > need all the clocks to be present so we cannot add the unknown for now > > usb clock. > > So to fix this issue we need a way to create a fake clock when the CRU > > clock domain is created that will be later replaced by the usb > > controller. There is multiple approch to this and I'm not yet sure > > which one will work best. > > > > 1) We allow to list non-existing clock as parent and don't throw > > errors anymore at clkdom_finit but at some SYSINIT. > > This will work well with a big static kernel but not if the clock is > > created by a kernel module. > > 2) We create some fake clock domain where we can add clocks to it so > > it became a somewhat valid parent (but not usable so you cannot select > > it with clknode_set_parent for example) and when a clock domain is > > finished we remove clock from the fake domain that are present in the > > newly created one (as clock names are unique this should not cause > > problem). The question is then what should we do when we still have > > clock in the fake domain ? > > > > Maybe mmel@ have more ideas. > > > All above is right but is not related to this panic > "panic: clknode_init_parent_idx: Invalid parent index 5 for clock > sclk_sdmmc". In this case, the parent clock at index 5 for sclk_sdmmc > (named "clk_sdmmc in TRM) is CLK_24M (at least in my TRM). Mhm right, it's the clock parent id 4 ("upll" in the TRM) the one I was talking about. So I guess that puttin parent 4 = NULL and xin24m for parent 5 should work. > Problem (for me) is that rockchip clock code is slightly incomplete and it uses > different nomenclature (naming) that is in TRM. > Unfortunately, putting > right clock for this index doesn't helps much, my RockPRo64 still fails > with another (not yet identified)problem. What are the symptoms ? > I currently working on proper (i hope) solution for this problem -> > something like soft-link clock node - a pure pass-throw node, which can > link clock between domains used for cross-domain clock linking. > > Michal -- Emmanuel Vadot From owner-freebsd-arm@freebsd.org Mon Oct 28 13:10:36 2019 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 5F1281A2642 for ; Mon, 28 Oct 2019 13:10:36 +0000 (UTC) (envelope-from melounmichal@gmail.com) Received: from mail-wm1-x344.google.com (mail-wm1-x344.google.com [IPv6:2a00:1450:4864:20::344]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 471w7b38kvz3R02 for ; Mon, 28 Oct 2019 13:10:35 +0000 (UTC) (envelope-from melounmichal@gmail.com) Received: by mail-wm1-x344.google.com with SMTP id 22so8946724wms.3 for ; Mon, 28 Oct 2019 06:10:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:from:reply-to:subject:to:cc:references:openpgp:autocrypt :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=uJ3hKfPbRKkpGG5S4sKXl9AECSz5I13KGZg/WUjW4ro=; b=GxzCQx3mmh0pq56XbN7ilRu3H6CZoxOlRz9uWAFJixkQYCPoUMuNOEmEmubquc9Z+F whDdRBnnM9/UWy+/QbUtzeZdN84kXXVgpMcQuEuDX0gefEM+TJcVtXdQLdTqH+GrfNX9 NTE+zpkH2RnokrA9z4ThvMZNxQVgCFPIARSiT4VsYCmeUIlh6wAL3h/KbZ7XRAZ+TNNb Oxwpi86A2Qxj67ZflfRD9u2uQzftXHZ+XmwN2QFfS0SON/i13cl2+y9KNhZxco73uBXc lfr+Wkp5wDtUqMdNq1uuZSzd8PYqHR9wEU7XNyFYKZPEHqptA/u1UrdWvAQfiG2fK0dM k+kw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:from:reply-to:subject:to:cc:references :openpgp:autocrypt:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=uJ3hKfPbRKkpGG5S4sKXl9AECSz5I13KGZg/WUjW4ro=; b=L18DG5crTZERgexJdUYUEB2ox1c5QnuEEvvp1GnvG7YRtyqzfxR2xyWYPB+WjrSCxN VfkUPjWnNH4jldzzu1YcH0X7O8SQ4fc7Z31KHi/hkHL9/kERQF0U8SPLi8BO7jWEuEB9 OxaqQVlCBKJSJohZlaAlOqWkOfCVOIMOQAfIKls+IDEU9VPJgFFY3+SElJP4feU9wF9G c0IvtoEXBktTSe0OJV6gxE/UhX8tb3d+/9qEc8mk+Qz7TH0Zmqo0isWWkzL+sJu8jbNG SmOMWSHkqaub8XY6rBuTqxmo/FTXbBX/BMPX0JfY3NKyHIl6wdA5wV8a9Nktq1Vfw0bo mdjA== X-Gm-Message-State: APjAAAX2FJR4r5Xew7eCyzzJaSlYMzKcU0HvCWOnW55RdpS/VScB9vhA iz01mGp5gl9QH2ASkv8THV4TGV76 X-Google-Smtp-Source: APXvYqwPY8jHhYMCyVxxZS4u/qGbfG5h/hyAeOryJT3c54I9Qy3QWZHBgLCwCqDzM2ilJ5tJLTX5nA== X-Received: by 2002:a1c:7305:: with SMTP id d5mr15305119wmb.84.1572268233511; Mon, 28 Oct 2019 06:10:33 -0700 (PDT) Received: from [88.208.79.100] (halouny.humusoft.cz. [88.208.79.100]) by smtp.gmail.com with ESMTPSA id r188sm11813118wmr.17.2019.10.28.06.10.32 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 28 Oct 2019 06:10:32 -0700 (PDT) Sender: Michal Meloun From: Michal Meloun X-Google-Original-From: Michal Meloun Reply-To: mmel@freebsd.org Subject: Re: FreeBSD 13-CURRENT download status on RK3399 SBC`s To: Emmanuel Vadot Cc: Michal Meloun , Sleep Walker , freebsd-arm@freebsd.org References: <20191028121027.8c89aef2a2809cd844ccad80@bidouilliste.com> <150c9db3-26f9-bd3b-eb16-c2801d6944f6@freebsd.org> <20191028132358.cd225b5127fb7396c11c4585@bidouilliste.com> Openpgp: preference=signencrypt Autocrypt: addr=mmel@freebsd.org; prefer-encrypt=mutual; keydata= mQENBFYuVRkBCADZiwLCCne3wG9b9k+R2Neo5zVo2bLaZRfNNY/v9kg283i0sb1Da4EdEiNT 15El5UyozhphUIbIR/zrVpxF1TvvFdoCyzx6a68bNY2d9dBrDcNDZC+XnyDdHQoobN87DWT1 mRVkmbg9LHZ/SVUOkGYuWyE+8UYeDAcUizuXwSK5zFWmeTyIoWNa68ifrWLfQe0p4x5jC/AI VURCi17p360vU4fhgwoMvEEhrRBWCr4DYHToFjIt2WdBy3GR1qoO0+Xkd6G+OoBULo+XDfgu L2WdPvh0K69F9/LgHkMmG5Il7SCe62QGpG2vaCgRV7BQhLX+kxlvM+WrdRatWRml4Y/3ABEB AAG0IE1pY2hhbCBNZWxvdW4gPG1tZWxAZnJlZWJzZC5vcmc+iQFXBBMBCgBBAhsDBQsJCAcD BRUKCQgLBRYDAgEAAh4BAheAAhkBFiEEAN1KEEuAn+Apg413aR6ya17FqqoFAlw3aO8FCQ9v FVYACgkQaR6ya17FqqrIFwf/V/NRuAutw1cZ/HRCwfp00KY+8g730KwOaAMhPYvq8tqf8krD whFRWt9s4DSVTVJUC2dRZa5g1MS77iQL/WWzBUhJj7rW4uMpcKpi7UXi060sKrnE+1ZBvanG 8YCMTHKxQgQDD0cBqsyOAfrSA+Pyya3/HyAh1vvjQZfu5vWxA1X5NX5l5KtonprJ+ybVacwO W34yfWSX+ncx089JpUknenGdI+gVoKfa6uh/8YiCZTI5poxBttrOB8NGfylTsTTTbw2pkire Vkc87qq++I9bBNtTqWOZjB/3KBUd4q1veEUa4MS63TWtAvcEcsxHiBv4AH6npPO/iPycuGGh qldT1LkBDQRWLlUZAQgAuqBGR9LbUP86pYT2Zd+HZsiOun24LxPQwK6KZuysB0so02isa7ac T6t5uBfyfmdgzfvsc6dqU8bI65e8JtDwwVVF1Y4fF6cmNcmJqU10Gw5/bAu9re9JJWx2g/OJ tYMhwmqEE5DcS6GwgvJZI+9hgoSLL3mZ+GsO25NM4BhVH1o1AE4Q3O0HZMMnIzH+pma0augZ Xc3Qep17/Occ+1A7xEbn8VAYx8cwjkYUy7JyvVx4ecuj+i+uoCXhNhX5QdIcn4UMT1233Bcd yVZtZsLTI26ByFmrquGjkmN+/hra/s+nKfcegOKeHWVY/uFgDRk0TEYd6QuddZWo7+XMZLps wQARAQABiQElBBgBCgAPAhsMBQJZjBHDBQkHICOqAAoJEGkesmtexaqquysH/iDgRIrlMvFT GLyktZws/K/C03gWZ/tWwJV5+SFqRoasM+Z+9+cb44XA3rReqieLsYF5qSXTXHBPhEg1+9V9 KEPLpwektLtAv8zynN+6VVffwyRWQ4PIZmHCMT6PJP+Rk0DU6VrDc3ch58erduuyRDsbh32g 96nYMNvDsLhDvq44GPHLfglUHRY6wHo3IxAH2HosaWNC10R13JSrCdFnPMeIa+nSE+11hAdB mWpuPgVX2VNErtrwSBr7LsyCZ4yLO0bN5fKM0/Tavc9EcI9qDBrnts/EfZoCHhDtTMEFnQZM ybsMso20I/nxYPFuWuuFn7uQeoYrwWxt15SkN0RgtV2JATwEGAEKACYCGwwWIQQA3UoQS4Cf 4CmDjXdpHrJrXsWqqgUCXDdpmwUJD28WAgAKCRBpHrJrXsWqqtOrB/9Okk/dm2/mAs3tbA6l lKOZAwfUwBonwG7YhK9dOb5No/bJoY8G9s2IVXqwWKqCDv1qKC4M8pMXPD9fVsfNPG8GA1GZ rpZoZxHFteXZHoE1grpWypE0T3hp1W0hQNWXKv0MSuEMRVKU1m/iyLa10X7q8BaKtEDs35Xf DCh7eVg1vqiKtWyFn1u+y9Gy1Ztc/SKTs8mQvMYNUdBZuV6vN0VSz3I6wD9HVfo6Eo3M7cVp qqQ+KhrrGiCCYQPfZwpFAJSSgV3bR5O0BlNaGKJOoVTV1yexRbVEStswiFP8JFQp6U+S3nqE FFob7daQBLxi80oUVRn6eEdzR8tBhIy7sbeD Message-ID: Date: Mon, 28 Oct 2019 14:10:32 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0 MIME-Version: 1.0 In-Reply-To: <20191028132358.cd225b5127fb7396c11c4585@bidouilliste.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 471w7b38kvz3R02 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=GxzCQx3m; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of melounmichal@gmail.com designates 2a00:1450:4864:20::344 as permitted sender) smtp.mailfrom=melounmichal@gmail.com X-Spamd-Result: default: False [-3.00 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; HAS_REPLYTO(0.00)[mmel@freebsd.org]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; TAGGED_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TAGGED_RCPT(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; REPLYTO_DOM_NEQ_FROM_DOM(0.00)[]; MIME_GOOD(-0.10)[text/plain]; IP_SCORE_FREEMAIL(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[4.4.3.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; IP_SCORE(0.00)[ip: (2.80), ipnet: 2a00:1450::/32(-2.80), asn: 15169(-2.05), country: US(-0.05)]; FREEMAIL_CC(0.00)[gmail.com]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Oct 2019 13:10:36 -0000 On 28.10.2019 13:23, Emmanuel Vadot wrote: > On Mon, 28 Oct 2019 12:59:30 +0100 > Michal Meloun wrote: > >> >> >> On 28.10.2019 12:10, Emmanuel Vadot wrote: >>> On Mon, 28 Oct 2019 13:57:57 +0300 >>> Sleep Walker wrote: >>> >>>> Hi All! >>>> >>>> On Khadas-EDGE-V >>>> >>>> - mainline uboot U-Boot TPL 2019.10-rc3 >>>> - bootup from SD >>>> - eth OK >>>> - uart OK >>>> - emmc OK >>>> - sd OK >>>> - USB 2.0 OK >>>> - USB 3.0 OK >>>> - USB HID OK >>>> - USB DISK OK >>> >>> Good to know that everything is working on this board too. >>> >>>> >>>> On Rock Pi4 >>>> >>>> UEFI booting, very cool. >>>> >>>> But I can not log into the console. >>>> >>>> it seems it keeps rebooting. >>>> >>>> Here is the log: >>>> https://pastebin.com/JFX7Ssnz >>> >>> This is known. Let me try to describe the problem. >>> So the sd and panic: clknode_init_parent_idx: Invalid parent index 5 for clock sclk_sdmmc have multiple possible parent, one of them is >>> the usb clock that is generated by the usb controller. The problem is >>> that when we create the clock domain of the CRU (Clock and Reset >>> Unit) the usb controller isn't probed yet because it needs clock from >>> the CRU. When a clock domain is finished (by calling clkdom_finit) we >>> need all the clocks to be present so we cannot add the unknown for now >>> usb clock. >>> So to fix this issue we need a way to create a fake clock when the CRU >>> clock domain is created that will be later replaced by the usb >>> controller. There is multiple approch to this and I'm not yet sure >>> which one will work best. >>> >>> 1) We allow to list non-existing clock as parent and don't throw >>> errors anymore at clkdom_finit but at some SYSINIT. >>> This will work well with a big static kernel but not if the clock is >>> created by a kernel module. >>> 2) We create some fake clock domain where we can add clocks to it so >>> it became a somewhat valid parent (but not usable so you cannot select >>> it with clknode_set_parent for example) and when a clock domain is >>> finished we remove clock from the fake domain that are present in the >>> newly created one (as clock names are unique this should not cause >>> problem). The question is then what should we do when we still have >>> clock in the fake domain ? >>> >>> Maybe mmel@ have more ideas. >>> >> All above is right but is not related to this panic >> "panic: clknode_init_parent_idx: Invalid parent index 5 for clock >> sclk_sdmmc". In this case, the parent clock at index 5 for sclk_sdmmc >> (named "clk_sdmmc in TRM) is CLK_24M (at least in my TRM). > > Mhm right, it's the clock parent id 4 ("upll" in the TRM) the one I > was talking about. So I guess that puttin parent 4 = NULL and xin24m > for parent 5 should work. > >> Problem (for me) is that rockchip clock code is slightly incomplete and it uses >> different nomenclature (naming) that is in TRM. >> Unfortunately, putting >> right clock for this index doesn't helps much, my RockPRo64 still fails >> with another (not yet identified)problem. > > What are the symptoms ? > See attached log. It occurs on every second hard reboot (by pressing reset button) reboot, only if both clusters are enabled. And, please, don't ask me why :) Michal ---------------------------------------------------------------------- ... WARNING: WITNESS option enabled, expect reduced performance. uhub2: 1 port with 1 removable, self powered uhub4: 1 port with 1 removable, self powered uhub3: 2 ports with 2 removable, self powered Root mount waiting for: usbus4 usbus2 usbus0 uhub0: 1 port with 1 removable, self powered uhub1: 1 port with 1 removable, self powered Root mount waiting for: usbus4 usbus0 ugen4.2: at usbus4 umass0 on uhub3 umass0: on usbus4 umass0: SCSI over Bulk-Only; quirks = 0x8100 umass0:0:0: Attached to scbus0 da0 at umass-sim0 bus 0 scbus0 target 0 lun 0 da0: Removable Direct Access SPC-2 SCSI device da0: Serial Number 02UIG9DQD7J9880G da0: 40.000MB/s transfers da0: 3764MB (7708672 512 byte sectors) da0: quirks=0x12 ugen0.2: at usbus0 umass1 on uhub0 umass1: on usbus0 umass1: SCSI over Bulk-Only; quirks = 0x8100 umass1:1:1: Attached to scbus1 Kernel page fault with the following non-sleepable locks held: exclusive sleep mutex CAM bus lock (CAM bus lock) r = 0 (0xfffffd0003fe7260) locked @ /usr2/Meloun/git/pmap/sys/cam/cam_xpt.c:1039 exclusive sleep mutex XPT topology lock (XPT topology lock) r = 0 (0xffff000000d0dee8) locked @ /usr2/Meloun/git/pmap/sys/cam/cam_xpt.c:5367 exclusive sleep mutex CAM device lock (CAM device lock) r = 0 (0xfffffd000e02d4d0) locked @ /usr2/Meloun/git/pmap/sys/cam/cam_xpt.c:5494 stack backtrace: #0 0xffff0000005b3ae0 at witness_checkorder+0xd04 #1 0xffff0000005b4afc at witness_warn+0x3f8 #2 0xffff000000899c6c at do_el1h_sync+0x318 #3 0xffff000000899a78 at do_el1h_sync+0x124 #4 0xffff000000880874 at handle_el1h_sync+0x74 #5 0xffff0000000161f0 at xpt_remove_periph+0x38 #6 0xffff000000012674 at cam_periph_release_locked_buses+0x158 #7 0xffff00000001284c at cam_periph_release_locked+0x1c #8 0xffff00000002de74 at nvme_get_identify_ns+0x6d18 #9 0xffff00000001b474 at xpt_done_direct+0x3b4 #10 0xffff00000001d26c at xpt_register_async+0x13fc #11 0xffff00000050b040 at fork_exit+0x7c x0: fffffd0003fe7260 From owner-freebsd-arm@freebsd.org Mon Oct 28 13:21:54 2019 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 942D71A2A60 for ; Mon, 28 Oct 2019 13:21:54 +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 471wNf05xhz3xCM; Mon, 28 Oct 2019 13:21:53 +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 a5363971; Mon, 28 Oct 2019 14:21:52 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; s=mail; bh=ndg5CY8OQ/ElZ25ododdYmM43Ag=; b=q+P4mPBXW7pWfz/Yg/tdEHdQnNvS zDVdK/DaMvUs57PXkAlzUU2301Tt8XKaCdgNzL330nqCmgv8p0Vf4BN2qsO5H9Jq gfCvOxDYRtZGRlijqsTC/8NvaB9y73vdFpfNw18w4gDzhQBismKEuoGmY03Av7aI v85Ci54rJWalhbk= 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=BIpv9u7ItjEJ3APTJbR8OX4A6QmKQdgHTSgy1WcDIjoZ01JryhfzJ4WD TULT997QXmGJgg0vdfxoC5Kp9ID0xhc0RnspiJ0p4oYZKKL5ZfFj+AMH5khnn1+R 9DZQxyt0ShwUP+Q5J8zZLV58HdDFusliPu0XKGWOtanOuiyeyYU= Received: from sonic.home.blih.net (ip-9.net-89-3-105.rev.numericable.fr [89.3.105.9]) by mail.blih.net (OpenSMTPD) with ESMTPSA id 1daaf2f5 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Mon, 28 Oct 2019 14:21:52 +0100 (CET) Date: Mon, 28 Oct 2019 14:21:52 +0100 From: Emmanuel Vadot To: mmel@freebsd.org Cc: Michal Meloun , Sleep Walker , freebsd-arm@freebsd.org Subject: Re: FreeBSD 13-CURRENT download status on RK3399 SBC`s Message-Id: <20191028142152.a3147e5b4f7ef2a84a2502df@bidouilliste.com> In-Reply-To: References: <20191028121027.8c89aef2a2809cd844ccad80@bidouilliste.com> <150c9db3-26f9-bd3b-eb16-c2801d6944f6@freebsd.org> <20191028132358.cd225b5127fb7396c11c4585@bidouilliste.com> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; amd64-portbld-freebsd13.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 471wNf05xhz3xCM X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-5.99 / 15.00]; TAGGED_RCPT(0.00)[]; NEURAL_HAM_MEDIUM(-0.99)[-0.993,0]; REPLY(-4.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Oct 2019 13:21:54 -0000 On Mon, 28 Oct 2019 14:10:32 +0100 Michal Meloun wrote: > > > On 28.10.2019 13:23, Emmanuel Vadot wrote: > > On Mon, 28 Oct 2019 12:59:30 +0100 > > Michal Meloun wrote: > > > >> > >> > >> On 28.10.2019 12:10, Emmanuel Vadot wrote: > >>> On Mon, 28 Oct 2019 13:57:57 +0300 > >>> Sleep Walker wrote: > >>> > >>>> Hi All! > >>>> > >>>> On Khadas-EDGE-V > >>>> > >>>> - mainline uboot U-Boot TPL 2019.10-rc3 > >>>> - bootup from SD > >>>> - eth OK > >>>> - uart OK > >>>> - emmc OK > >>>> - sd OK > >>>> - USB 2.0 OK > >>>> - USB 3.0 OK > >>>> - USB HID OK > >>>> - USB DISK OK > >>> > >>> Good to know that everything is working on this board too. > >>> > >>>> > >>>> On Rock Pi4 > >>>> > >>>> UEFI booting, very cool. > >>>> > >>>> But I can not log into the console. > >>>> > >>>> it seems it keeps rebooting. > >>>> > >>>> Here is the log: > >>>> https://pastebin.com/JFX7Ssnz > >>> > >>> This is known. Let me try to describe the problem. > >>> So the sd and panic: clknode_init_parent_idx: Invalid parent index 5 for clock sclk_sdmmc have multiple possible parent, one of them is > >>> the usb clock that is generated by the usb controller. The problem is > >>> that when we create the clock domain of the CRU (Clock and Reset > >>> Unit) the usb controller isn't probed yet because it needs clock from > >>> the CRU. When a clock domain is finished (by calling clkdom_finit) we > >>> need all the clocks to be present so we cannot add the unknown for now > >>> usb clock. > >>> So to fix this issue we need a way to create a fake clock when the CRU > >>> clock domain is created that will be later replaced by the usb > >>> controller. There is multiple approch to this and I'm not yet sure > >>> which one will work best. > >>> > >>> 1) We allow to list non-existing clock as parent and don't throw > >>> errors anymore at clkdom_finit but at some SYSINIT. > >>> This will work well with a big static kernel but not if the clock is > >>> created by a kernel module. > >>> 2) We create some fake clock domain where we can add clocks to it so > >>> it became a somewhat valid parent (but not usable so you cannot select > >>> it with clknode_set_parent for example) and when a clock domain is > >>> finished we remove clock from the fake domain that are present in the > >>> newly created one (as clock names are unique this should not cause > >>> problem). The question is then what should we do when we still have > >>> clock in the fake domain ? > >>> > >>> Maybe mmel@ have more ideas. > >>> > >> All above is right but is not related to this panic > >> "panic: clknode_init_parent_idx: Invalid parent index 5 for clock > >> sclk_sdmmc". In this case, the parent clock at index 5 for sclk_sdmmc > >> (named "clk_sdmmc in TRM) is CLK_24M (at least in my TRM). > > > > Mhm right, it's the clock parent id 4 ("upll" in the TRM) the one I > > was talking about. So I guess that puttin parent 4 = NULL and xin24m > > for parent 5 should work. > > > >> Problem (for me) is that rockchip clock code is slightly incomplete and it uses > >> different nomenclature (naming) that is in TRM. > >> Unfortunately, putting > >> right clock for this index doesn't helps much, my RockPRo64 still fails > >> with another (not yet identified)problem. > > > > What are the symptoms ? > > > > See attached log. It occurs on every second hard reboot (by pressing > reset button) reboot, only if both clusters are enabled. And, please, > don't ask me why :) > Michal > > ---------------------------------------------------------------------- > ... > WARNING: WITNESS option enabled, expect reduced performance. > uhub2: 1 port with 1 removable, self powered > uhub4: 1 port with 1 removable, self powered > uhub3: 2 ports with 2 removable, self powered > Root mount waiting for: usbus4 usbus2 usbus0 > uhub0: 1 port with 1 removable, self powered > uhub1: 1 port with 1 removable, self powered > Root mount waiting for: usbus4 usbus0 > ugen4.2: at usbus4 > umass0 on uhub3 > umass0: 1> on usbus4 > umass0: SCSI over Bulk-Only; quirks = 0x8100 > umass0:0:0: Attached to scbus0 > da0 at umass-sim0 bus 0 scbus0 target 0 lun 0 > da0: Removable Direct Access SPC-2 SCSI device > da0: Serial Number 02UIG9DQD7J9880G > da0: 40.000MB/s transfers > da0: 3764MB (7708672 512 byte sectors) > da0: quirks=0x12 > ugen0.2: at usbus0 > umass1 on uhub0 > umass1: 2> on usbus0 > umass1: SCSI over Bulk-Only; quirks = 0x8100 > umass1:1:1: Attached to scbus1 > Kernel page fault with the following non-sleepable locks held: > exclusive sleep mutex CAM bus lock (CAM bus lock) r = 0 > (0xfffffd0003fe7260) locked @ /usr2/Meloun/git/pmap/sys/cam/cam_xpt.c:1039 > exclusive sleep mutex XPT topology lock (XPT topology lock) r = 0 > (0xffff000000d0dee8) locked @ /usr2/Meloun/git/pmap/sys/cam/cam_xpt.c:5367 > exclusive sleep mutex CAM device lock (CAM device lock) r = 0 > (0xfffffd000e02d4d0) locked @ /usr2/Meloun/git/pmap/sys/cam/cam_xpt.c:5494 > stack backtrace: > #0 0xffff0000005b3ae0 at witness_checkorder+0xd04 > #1 0xffff0000005b4afc at witness_warn+0x3f8 > #2 0xffff000000899c6c at do_el1h_sync+0x318 > #3 0xffff000000899a78 at do_el1h_sync+0x124 > #4 0xffff000000880874 at handle_el1h_sync+0x74 > #5 0xffff0000000161f0 at xpt_remove_periph+0x38 > #6 0xffff000000012674 at cam_periph_release_locked_buses+0x158 > #7 0xffff00000001284c at cam_periph_release_locked+0x1c > #8 0xffff00000002de74 at nvme_get_identify_ns+0x6d18 > #9 0xffff00000001b474 at xpt_done_direct+0x3b4 > #10 0xffff00000001d26c at xpt_register_async+0x13fc > #11 0xffff00000050b040 at fork_exit+0x7c > x0: fffffd0003fe7260 Ah yes this is known too, I only use the small cluster. I've presume a mutex problem between the clusters but I'm not sure. Not that this only shows up if you use a usb disk (well anything CAM I guess). -- Emmanuel Vadot From owner-freebsd-arm@freebsd.org Mon Oct 28 13:28:13 2019 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 042C61A2E0B for ; Mon, 28 Oct 2019 13:28:13 +0000 (UTC) (envelope-from s199p.wa1k9r@gmail.com) Received: from mail-lj1-x244.google.com (mail-lj1-x244.google.com [IPv6:2a00:1450:4864:20::244]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 471wWw26d8z3xYh; Mon, 28 Oct 2019 13:28:11 +0000 (UTC) (envelope-from s199p.wa1k9r@gmail.com) Received: by mail-lj1-x244.google.com with SMTP id w8so6833744lji.13; Mon, 28 Oct 2019 06:28:11 -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; bh=oOFiFlsSv+8ZL6awQ7UNJoRuF3JHPLU8WzH98DEqyao=; b=beEg1cusvumYN7FAO3AQTyMt960IKoK5wL4L+uucujqQqjIi/pko4gJxr/n/0cyTZJ EdxF8AZzfyWSMYZguGHcOsAAT5hQ+U5c7mEKe31Jx+Mrj0AW+4esT9lxq+meM3BPL+Al OppVXc+3I2agREe8Gj47U0HBnqRE+4+rkAreOcgCDI3K3ijZqNMwW3jlgfklYFZnW08a pkfgeVHw601JSWdiolnL9d7IuESy21FOygTpK8Yw0Ej8dUOS5fXWqxfnebKg4FCT+i2q zz0+cyE79g/Sjip1Q8XqqXUCYNkqoa3Kp9duZzZaaBPqiCJCqsqy6SxSnAyepqH0bLWq An3Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=oOFiFlsSv+8ZL6awQ7UNJoRuF3JHPLU8WzH98DEqyao=; b=TzWv4JoWq2hi97aRZmZ4g2Io7yUebkkW0Ju6/X6cQA2SpGoNkVg1vjL0v7jc5Ki1d6 m+xMfTLsh2U2Py9e5VGO+sKhG94kJDceuKm7GcG5LuCTknjmoSw8+mVXzsnlCol/1OtC dBw7ckiNZeG2rWMkWYcrcUYnLqQOUgTqWsU6vpn3Ota+pVbRXhwUTTu+PBhjSfDCQL/v GLIYg57xpoULcO+iHEqeiTbyR61XyUgS2NqEmKAMyBMnU1iofI7ja/5kHyp39bueqTvD VYs8MgINsGzxOHWHVqktb1GeFoAOUrISMDgyJsbY+7SB3XgmkomMyp0uyN399AtV1bxa meOA== X-Gm-Message-State: APjAAAWp8GG4wCtTJ+iq8H3XeHCUTXcEzlI+igJ45sJvRS6D8GVQq6yu MYtycOHVyIC1dgYzQ5oWsD+mUNXiJfYfxR5Go7vkdD8phMY= X-Google-Smtp-Source: APXvYqzAevKmZ6NapxfvJLt9Rd2bmH6IBPZnFJweTcAMrUxCpK2n1sSfFf6/d80MjR15p0I4sDhBHL9BwLoPy2i/oIA= X-Received: by 2002:a2e:5b82:: with SMTP id m2mr12121448lje.184.1572269289450; Mon, 28 Oct 2019 06:28:09 -0700 (PDT) MIME-Version: 1.0 References: <20191028121027.8c89aef2a2809cd844ccad80@bidouilliste.com> <150c9db3-26f9-bd3b-eb16-c2801d6944f6@freebsd.org> <20191028132358.cd225b5127fb7396c11c4585@bidouilliste.com> <20191028142152.a3147e5b4f7ef2a84a2502df@bidouilliste.com> In-Reply-To: <20191028142152.a3147e5b4f7ef2a84a2502df@bidouilliste.com> From: Sleep Walker Date: Mon, 28 Oct 2019 16:27:58 +0300 Message-ID: Subject: Re: FreeBSD 13-CURRENT download status on RK3399 SBC`s To: Emmanuel Vadot , "mmel@freebsd.org" , freebsd-arm@freebsd.org X-Rspamd-Queue-Id: 471wWw26d8z3xYh X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=beEg1cus; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of s199pwa1k9r@gmail.com designates 2a00:1450:4864:20::244 as permitted sender) smtp.mailfrom=s199pwa1k9r@gmail.com X-Spamd-Result: default: False [-2.00 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; URI_COUNT_ODD(1.00)[3]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; FROM_EQ_ENVFROM(0.00)[]; IP_SCORE(0.00)[ip: (2.90), ipnet: 2a00:1450::/32(-2.80), asn: 15169(-2.05), country: US(-0.05)]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; TAGGED_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; IP_SCORE_FREEMAIL(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[4.4.2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Oct 2019 13:28:13 -0000 Will there be any recommendations on how to avoid a mistake clknode_init_parent_idx: Invalid parent index 5 for clock sclk_sdmmc You will offer some patches. I am ready to try them. =D0=BF=D0=BD, 28 =D0=BE=D0=BA=D1=82. 2019 =D0=B3. =D0=B2 16:21, Emmanuel Va= dot : > On Mon, 28 Oct 2019 14:10:32 +0100 > Michal Meloun wrote: > > > > > > > On 28.10.2019 13:23, Emmanuel Vadot wrote: > > > On Mon, 28 Oct 2019 12:59:30 +0100 > > > Michal Meloun wrote: > > > > > >> > > >> > > >> On 28.10.2019 12:10, Emmanuel Vadot wrote: > > >>> On Mon, 28 Oct 2019 13:57:57 +0300 > > >>> Sleep Walker wrote: > > >>> > > >>>> Hi All! > > >>>> > > >>>> On Khadas-EDGE-V > > >>>> > > >>>> - mainline uboot U-Boot TPL 2019.10-rc3 > > >>>> - bootup from SD > > >>>> - eth OK > > >>>> - uart OK > > >>>> - emmc OK > > >>>> - sd OK > > >>>> - USB 2.0 OK > > >>>> - USB 3.0 OK > > >>>> - USB HID OK > > >>>> - USB DISK OK > > >>> > > >>> Good to know that everything is working on this board too. > > >>> > > >>>> > > >>>> On Rock Pi4 > > >>>> > > >>>> UEFI booting, very cool. > > >>>> > > >>>> But I can not log into the console. > > >>>> > > >>>> it seems it keeps rebooting. > > >>>> > > >>>> Here is the log: > > >>>> https://pastebin.com/JFX7Ssnz > > >>> > > >>> This is known. Let me try to describe the problem. > > >>> So the sd and panic: clknode_init_parent_idx: Invalid parent index > 5 for clock sclk_sdmmc have multiple possible parent, one of them is > > >>> the usb clock that is generated by the usb controller. The problem = is > > >>> that when we create the clock domain of the CRU (Clock and Reset > > >>> Unit) the usb controller isn't probed yet because it needs clock fr= om > > >>> the CRU. When a clock domain is finished (by calling clkdom_finit) = we > > >>> need all the clocks to be present so we cannot add the unknown for > now > > >>> usb clock. > > >>> So to fix this issue we need a way to create a fake clock when the > CRU > > >>> clock domain is created that will be later replaced by the usb > > >>> controller. There is multiple approch to this and I'm not yet sure > > >>> which one will work best. > > >>> > > >>> 1) We allow to list non-existing clock as parent and don't throw > > >>> errors anymore at clkdom_finit but at some SYSINIT. > > >>> This will work well with a big static kernel but not if the clock = is > > >>> created by a kernel module. > > >>> 2) We create some fake clock domain where we can add clocks to it = so > > >>> it became a somewhat valid parent (but not usable so you cannot > select > > >>> it with clknode_set_parent for example) and when a clock domain is > > >>> finished we remove clock from the fake domain that are present in t= he > > >>> newly created one (as clock names are unique this should not cause > > >>> problem). The question is then what should we do when we still have > > >>> clock in the fake domain ? > > >>> > > >>> Maybe mmel@ have more ideas. > > >>> > > >> All above is right but is not related to this panic > > >> "panic: clknode_init_parent_idx: Invalid parent index 5 for clock > > >> sclk_sdmmc". In this case, the parent clock at index 5 for sclk_sdmm= c > > >> (named "clk_sdmmc in TRM) is CLK_24M (at least in my TRM). > > > > > > Mhm right, it's the clock parent id 4 ("upll" in the TRM) the one I > > > was talking about. So I guess that puttin parent 4 =3D NULL and xin24= m > > > for parent 5 should work. > > > > > >> Problem (for me) is that rockchip clock code is slightly incomplete > and it uses > > >> different nomenclature (naming) that is in TRM. > > >> Unfortunately, putting > > >> right clock for this index doesn't helps much, my RockPRo64 still > fails > > >> with another (not yet identified)problem. > > > > > > What are the symptoms ? > > > > > > > See attached log. It occurs on every second hard reboot (by pressing > > reset button) reboot, only if both clusters are enabled. And, please, > > don't ask me why :) > > Michal > > > > ---------------------------------------------------------------------- > > ... > > WARNING: WITNESS option enabled, expect reduced performance. > > uhub2: 1 port with 1 removable, self powered > > uhub4: 1 port with 1 removable, self powered > > uhub3: 2 ports with 2 removable, self powered > > Root mount waiting for: usbus4 usbus2 usbus0 > > uhub0: 1 port with 1 removable, self powered > > uhub1: 1 port with 1 removable, self powered > > Root mount waiting for: usbus4 usbus0 > > ugen4.2: at usbus4 > > umass0 on uhub3 > > umass0: > 1> on usbus4 > > umass0: SCSI over Bulk-Only; quirks =3D 0x8100 > > umass0:0:0: Attached to scbus0 > > da0 at umass-sim0 bus 0 scbus0 target 0 lun 0 > > da0: Removable Direct Access SPC-2 SCSI > device > > da0: Serial Number 02UIG9DQD7J9880G > > da0: 40.000MB/s transfers > > da0: 3764MB (7708672 512 byte sectors) > > da0: quirks=3D0x12 > > ugen0.2: at usbus0 > > umass1 on uhub0 > > umass1: > 2> on usbus0 > > umass1: SCSI over Bulk-Only; quirks =3D 0x8100 > > umass1:1:1: Attached to scbus1 > > Kernel page fault with the following non-sleepable locks held: > > exclusive sleep mutex CAM bus lock (CAM bus lock) r =3D 0 > > (0xfffffd0003fe7260) locked @ > /usr2/Meloun/git/pmap/sys/cam/cam_xpt.c:1039 > > exclusive sleep mutex XPT topology lock (XPT topology lock) r =3D 0 > > (0xffff000000d0dee8) locked @ > /usr2/Meloun/git/pmap/sys/cam/cam_xpt.c:5367 > > exclusive sleep mutex CAM device lock (CAM device lock) r =3D 0 > > (0xfffffd000e02d4d0) locked @ > /usr2/Meloun/git/pmap/sys/cam/cam_xpt.c:5494 > > stack backtrace: > > #0 0xffff0000005b3ae0 at witness_checkorder+0xd04 > > #1 0xffff0000005b4afc at witness_warn+0x3f8 > > #2 0xffff000000899c6c at do_el1h_sync+0x318 > > #3 0xffff000000899a78 at do_el1h_sync+0x124 > > #4 0xffff000000880874 at handle_el1h_sync+0x74 > > #5 0xffff0000000161f0 at xpt_remove_periph+0x38 > > #6 0xffff000000012674 at cam_periph_release_locked_buses+0x158 > > #7 0xffff00000001284c at cam_periph_release_locked+0x1c > > #8 0xffff00000002de74 at nvme_get_identify_ns+0x6d18 > > #9 0xffff00000001b474 at xpt_done_direct+0x3b4 > > #10 0xffff00000001d26c at xpt_register_async+0x13fc > > #11 0xffff00000050b040 at fork_exit+0x7c > > x0: fffffd0003fe7260 > > Ah yes this is known too, I only use the small cluster. I've presume a > mutex problem between the clusters but I'm not sure. Not that this only > shows up if you use a usb disk (well anything CAM I guess). > > -- > Emmanuel Vadot > From owner-freebsd-arm@freebsd.org Mon Oct 28 14:00:44 2019 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 92E451A38C1 for ; Mon, 28 Oct 2019 14:00:44 +0000 (UTC) (envelope-from melounmichal@gmail.com) Received: from mail-wm1-x342.google.com (mail-wm1-x342.google.com [IPv6:2a00:1450:4864:20::342]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 471xFR6W7yz40yL for ; Mon, 28 Oct 2019 14:00:43 +0000 (UTC) (envelope-from melounmichal@gmail.com) Received: by mail-wm1-x342.google.com with SMTP id g24so9572697wmh.5 for ; Mon, 28 Oct 2019 07:00:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:from:reply-to:subject:to:references:openpgp:autocrypt :message-id:date:user-agent:mime-version:in-reply-to :content-language; bh=rqgoDqrWeIPNcnjZgB+3zOH96Mjn54lvmXEVl6u9BCM=; b=mZ/YEUFtlYPp+LovfhruJfTlcFSIN9f2dnMW0GAmRNYPpahv9nlj+T/fb4NtNDYVzO Mxq1QVOEtX89ex1kuw1qO0lk479dAo0K0OHLtZlgoqaVpopKtqhKBVTLRUJT8mE6aSMi vncwQVIAjYP9L6tr4m8y4vwp+f1pPqnNeBBiNVMi5W01JzlOTep643E8Jc/wL7U9xlTj B/nCv5J8shsu17epXSHkoOM3b1NHR3S9NYJqWsM8iuLk1ht3dwSKi8lYaTBX0GrhIk9u 0e2oh3PRdJ2D0XY2UqDsIj/RsQjHSoudyOc/S0naKsi0m/FT0QXbJINfTislBN217+TI el2g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:from:reply-to:subject:to:references :openpgp:autocrypt:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=rqgoDqrWeIPNcnjZgB+3zOH96Mjn54lvmXEVl6u9BCM=; b=faJO0tslXz4tUH/c1CUE/RAxGlcicsJyETTRVnhdUIfrOopjf6G5Ll5KJSABVc5/3L //ZIxFWaST5m2/uw4lxpyBYOEUUlFKgD2Ai0b2QNJOVJDCUGnM6ylS1jMPFNa4uBKs3y tiNwFGCBiuYQcA2vu0nW2dQHgPcFbwR+cow48IcON169kCG6L3k3W+t0MaykIf6To/CI xLbt3Fy+S4aIT0/r+mBYuwooqdME4fGp0GGYdhDvg2wYtF0fvKK6mODufaGYBGoKW9m6 qWjWIFo8urTDyn88rX0NdDBaX8/AXUNDB0Co+zcXVWrsvZ4mdKJTXZjCZIQX/bBFNZic KPcg== X-Gm-Message-State: APjAAAUKRm2ERA+6t8Yd8cCvlPfDgfRBgCg2QtpyGH6C+NT4L/EsbKDf XZ49f2xreQ9eZeYM6r7TDVoe3aIt X-Google-Smtp-Source: APXvYqy2J1tWriI1sg+xYtynLnXAvl5g7oljOlLe8iH16HhM8lQnOPsb22enyDEj6IQ9kKiXmOdLJQ== X-Received: by 2002:a1c:c28a:: with SMTP id s132mr120471wmf.162.1572271241648; Mon, 28 Oct 2019 07:00:41 -0700 (PDT) Received: from [88.208.79.100] (halouny.humusoft.cz. [88.208.79.100]) by smtp.gmail.com with ESMTPSA id c16sm12785426wrw.32.2019.10.28.07.00.40 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 28 Oct 2019 07:00:40 -0700 (PDT) Sender: Michal Meloun From: Michal Meloun X-Google-Original-From: Michal Meloun Reply-To: mmel@freebsd.org Subject: Re: FreeBSD 13-CURRENT download status on RK3399 SBC`s To: Sleep Walker , Emmanuel Vadot , freebsd-arm@freebsd.org References: <20191028121027.8c89aef2a2809cd844ccad80@bidouilliste.com> <150c9db3-26f9-bd3b-eb16-c2801d6944f6@freebsd.org> <20191028132358.cd225b5127fb7396c11c4585@bidouilliste.com> <20191028142152.a3147e5b4f7ef2a84a2502df@bidouilliste.com> Openpgp: preference=signencrypt Autocrypt: addr=mmel@freebsd.org; prefer-encrypt=mutual; keydata= mQENBFYuVRkBCADZiwLCCne3wG9b9k+R2Neo5zVo2bLaZRfNNY/v9kg283i0sb1Da4EdEiNT 15El5UyozhphUIbIR/zrVpxF1TvvFdoCyzx6a68bNY2d9dBrDcNDZC+XnyDdHQoobN87DWT1 mRVkmbg9LHZ/SVUOkGYuWyE+8UYeDAcUizuXwSK5zFWmeTyIoWNa68ifrWLfQe0p4x5jC/AI VURCi17p360vU4fhgwoMvEEhrRBWCr4DYHToFjIt2WdBy3GR1qoO0+Xkd6G+OoBULo+XDfgu L2WdPvh0K69F9/LgHkMmG5Il7SCe62QGpG2vaCgRV7BQhLX+kxlvM+WrdRatWRml4Y/3ABEB AAG0IE1pY2hhbCBNZWxvdW4gPG1tZWxAZnJlZWJzZC5vcmc+iQFXBBMBCgBBAhsDBQsJCAcD BRUKCQgLBRYDAgEAAh4BAheAAhkBFiEEAN1KEEuAn+Apg413aR6ya17FqqoFAlw3aO8FCQ9v FVYACgkQaR6ya17FqqrIFwf/V/NRuAutw1cZ/HRCwfp00KY+8g730KwOaAMhPYvq8tqf8krD whFRWt9s4DSVTVJUC2dRZa5g1MS77iQL/WWzBUhJj7rW4uMpcKpi7UXi060sKrnE+1ZBvanG 8YCMTHKxQgQDD0cBqsyOAfrSA+Pyya3/HyAh1vvjQZfu5vWxA1X5NX5l5KtonprJ+ybVacwO W34yfWSX+ncx089JpUknenGdI+gVoKfa6uh/8YiCZTI5poxBttrOB8NGfylTsTTTbw2pkire Vkc87qq++I9bBNtTqWOZjB/3KBUd4q1veEUa4MS63TWtAvcEcsxHiBv4AH6npPO/iPycuGGh qldT1LkBDQRWLlUZAQgAuqBGR9LbUP86pYT2Zd+HZsiOun24LxPQwK6KZuysB0so02isa7ac T6t5uBfyfmdgzfvsc6dqU8bI65e8JtDwwVVF1Y4fF6cmNcmJqU10Gw5/bAu9re9JJWx2g/OJ tYMhwmqEE5DcS6GwgvJZI+9hgoSLL3mZ+GsO25NM4BhVH1o1AE4Q3O0HZMMnIzH+pma0augZ Xc3Qep17/Occ+1A7xEbn8VAYx8cwjkYUy7JyvVx4ecuj+i+uoCXhNhX5QdIcn4UMT1233Bcd yVZtZsLTI26ByFmrquGjkmN+/hra/s+nKfcegOKeHWVY/uFgDRk0TEYd6QuddZWo7+XMZLps wQARAQABiQElBBgBCgAPAhsMBQJZjBHDBQkHICOqAAoJEGkesmtexaqquysH/iDgRIrlMvFT GLyktZws/K/C03gWZ/tWwJV5+SFqRoasM+Z+9+cb44XA3rReqieLsYF5qSXTXHBPhEg1+9V9 KEPLpwektLtAv8zynN+6VVffwyRWQ4PIZmHCMT6PJP+Rk0DU6VrDc3ch58erduuyRDsbh32g 96nYMNvDsLhDvq44GPHLfglUHRY6wHo3IxAH2HosaWNC10R13JSrCdFnPMeIa+nSE+11hAdB mWpuPgVX2VNErtrwSBr7LsyCZ4yLO0bN5fKM0/Tavc9EcI9qDBrnts/EfZoCHhDtTMEFnQZM ybsMso20I/nxYPFuWuuFn7uQeoYrwWxt15SkN0RgtV2JATwEGAEKACYCGwwWIQQA3UoQS4Cf 4CmDjXdpHrJrXsWqqgUCXDdpmwUJD28WAgAKCRBpHrJrXsWqqtOrB/9Okk/dm2/mAs3tbA6l lKOZAwfUwBonwG7YhK9dOb5No/bJoY8G9s2IVXqwWKqCDv1qKC4M8pMXPD9fVsfNPG8GA1GZ rpZoZxHFteXZHoE1grpWypE0T3hp1W0hQNWXKv0MSuEMRVKU1m/iyLa10X7q8BaKtEDs35Xf DCh7eVg1vqiKtWyFn1u+y9Gy1Ztc/SKTs8mQvMYNUdBZuV6vN0VSz3I6wD9HVfo6Eo3M7cVp qqQ+KhrrGiCCYQPfZwpFAJSSgV3bR5O0BlNaGKJOoVTV1yexRbVEStswiFP8JFQp6U+S3nqE FFob7daQBLxi80oUVRn6eEdzR8tBhIy7sbeD Message-ID: <6a757be7-79ec-3b95-f3d4-373cdc519836@freebsd.org> Date: Mon, 28 Oct 2019 15:00:40 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/mixed; boundary="------------472F11F4BA34F8B3CFD02AC3" Content-Language: en-US X-Rspamd-Queue-Id: 471xFR6W7yz40yL X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=mZ/YEUFt; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of melounmichal@gmail.com designates 2a00:1450:4864:20::342 as permitted sender) smtp.mailfrom=melounmichal@gmail.com X-Spamd-Result: default: False [-1.90 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; HAS_REPLYTO(0.00)[mmel@freebsd.org]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; HAS_ATTACHMENT(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[gmail.com:+]; CTYPE_MIXED_BOGUS(1.00)[]; MIME_BASE64_TEXT(0.10)[]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; TAGGED_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TAGGED_RCPT(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; REPLYTO_DOM_NEQ_FROM_DOM(0.00)[]; MIME_GOOD(-0.10)[multipart/mixed,text/plain]; IP_SCORE_FREEMAIL(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2.4.3.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; IP_SCORE(0.00)[ip: (2.83), ipnet: 2a00:1450::/32(-2.80), asn: 15169(-2.05), country: US(-0.05)]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Oct 2019 14:00:44 -0000 This is a multi-part message in MIME format. --------------472F11F4BA34F8B3CFD02AC3 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit On 28.10.2019 14:27, Sleep Walker wrote: > Will there be any recommendations on how to avoid a mistake > clknode_init_parent_idx: Invalid parent index 5 for clock sclk_sdmmc > You will offer some patches. > I am ready to try them. Only gross hack, nothing which can be committed. (added clock at index 4 is wrong (it should be 'upll'. But we don't have this branch defined at all, and rk_clk_composite don't likes sparse clock arrays...) Michal > пн, 28 окт. 2019 г. в 16:21, Emmanuel Vadot : > >> On Mon, 28 Oct 2019 14:10:32 +0100 >> Michal Meloun wrote: >> >>> >>> >>> On 28.10.2019 13:23, Emmanuel Vadot wrote: >>>> On Mon, 28 Oct 2019 12:59:30 +0100 >>>> Michal Meloun wrote: >>>> >>>>> >>>>> >>>>> On 28.10.2019 12:10, Emmanuel Vadot wrote: >>>>>> On Mon, 28 Oct 2019 13:57:57 +0300 >>>>>> Sleep Walker wrote: >>>>>> >>>>>>> Hi All! >>>>>>> >>>>>>> On Khadas-EDGE-V >>>>>>> >>>>>>> - mainline uboot U-Boot TPL 2019.10-rc3 >>>>>>> - bootup from SD >>>>>>> - eth OK >>>>>>> - uart OK >>>>>>> - emmc OK >>>>>>> - sd OK >>>>>>> - USB 2.0 OK >>>>>>> - USB 3.0 OK >>>>>>> - USB HID OK >>>>>>> - USB DISK OK >>>>>> >>>>>> Good to know that everything is working on this board too. >>>>>> >>>>>>> >>>>>>> On Rock Pi4 >>>>>>> >>>>>>> UEFI booting, very cool. >>>>>>> >>>>>>> But I can not log into the console. >>>>>>> >>>>>>> it seems it keeps rebooting. >>>>>>> >>>>>>> Here is the log: >>>>>>> https://pastebin.com/JFX7Ssnz >>>>>> >>>>>> This is known. Let me try to describe the problem. >>>>>> So the sd and panic: clknode_init_parent_idx: Invalid parent index >> 5 for clock sclk_sdmmc have multiple possible parent, one of them is >>>>>> the usb clock that is generated by the usb controller. The problem is >>>>>> that when we create the clock domain of the CRU (Clock and Reset >>>>>> Unit) the usb controller isn't probed yet because it needs clock from >>>>>> the CRU. When a clock domain is finished (by calling clkdom_finit) we >>>>>> need all the clocks to be present so we cannot add the unknown for >> now >>>>>> usb clock. >>>>>> So to fix this issue we need a way to create a fake clock when the >> CRU >>>>>> clock domain is created that will be later replaced by the usb >>>>>> controller. There is multiple approch to this and I'm not yet sure >>>>>> which one will work best. >>>>>> >>>>>> 1) We allow to list non-existing clock as parent and don't throw >>>>>> errors anymore at clkdom_finit but at some SYSINIT. >>>>>> This will work well with a big static kernel but not if the clock is >>>>>> created by a kernel module. >>>>>> 2) We create some fake clock domain where we can add clocks to it so >>>>>> it became a somewhat valid parent (but not usable so you cannot >> select >>>>>> it with clknode_set_parent for example) and when a clock domain is >>>>>> finished we remove clock from the fake domain that are present in the >>>>>> newly created one (as clock names are unique this should not cause >>>>>> problem). The question is then what should we do when we still have >>>>>> clock in the fake domain ? >>>>>> >>>>>> Maybe mmel@ have more ideas. >>>>>> >>>>> All above is right but is not related to this panic >>>>> "panic: clknode_init_parent_idx: Invalid parent index 5 for clock >>>>> sclk_sdmmc". In this case, the parent clock at index 5 for sclk_sdmmc >>>>> (named "clk_sdmmc in TRM) is CLK_24M (at least in my TRM). >>>> >>>> Mhm right, it's the clock parent id 4 ("upll" in the TRM) the one I >>>> was talking about. So I guess that puttin parent 4 = NULL and xin24m >>>> for parent 5 should work. >>>> >>>>> Problem (for me) is that rockchip clock code is slightly incomplete >> and it uses >>>>> different nomenclature (naming) that is in TRM. >>>>> Unfortunately, putting >>>>> right clock for this index doesn't helps much, my RockPRo64 still >> fails >>>>> with another (not yet identified)problem. >>>> >>>> What are the symptoms ? >>>> >>> >>> See attached log. It occurs on every second hard reboot (by pressing >>> reset button) reboot, only if both clusters are enabled. And, please, >>> don't ask me why :) >>> Michal >>> >>> ---------------------------------------------------------------------- >>> ... >>> WARNING: WITNESS option enabled, expect reduced performance. >>> uhub2: 1 port with 1 removable, self powered >>> uhub4: 1 port with 1 removable, self powered >>> uhub3: 2 ports with 2 removable, self powered >>> Root mount waiting for: usbus4 usbus2 usbus0 >>> uhub0: 1 port with 1 removable, self powered >>> uhub1: 1 port with 1 removable, self powered >>> Root mount waiting for: usbus4 usbus0 >>> ugen4.2: at usbus4 >>> umass0 on uhub3 >>> umass0: >> 1> on usbus4 >>> umass0: SCSI over Bulk-Only; quirks = 0x8100 >>> umass0:0:0: Attached to scbus0 >>> da0 at umass-sim0 bus 0 scbus0 target 0 lun 0 >>> da0: Removable Direct Access SPC-2 SCSI >> device >>> da0: Serial Number 02UIG9DQD7J9880G >>> da0: 40.000MB/s transfers >>> da0: 3764MB (7708672 512 byte sectors) >>> da0: quirks=0x12 >>> ugen0.2: at usbus0 >>> umass1 on uhub0 >>> umass1: >> 2> on usbus0 >>> umass1: SCSI over Bulk-Only; quirks = 0x8100 >>> umass1:1:1: Attached to scbus1 >>> Kernel page fault with the following non-sleepable locks held: >>> exclusive sleep mutex CAM bus lock (CAM bus lock) r = 0 >>> (0xfffffd0003fe7260) locked @ >> /usr2/Meloun/git/pmap/sys/cam/cam_xpt.c:1039 >>> exclusive sleep mutex XPT topology lock (XPT topology lock) r = 0 >>> (0xffff000000d0dee8) locked @ >> /usr2/Meloun/git/pmap/sys/cam/cam_xpt.c:5367 >>> exclusive sleep mutex CAM device lock (CAM device lock) r = 0 >>> (0xfffffd000e02d4d0) locked @ >> /usr2/Meloun/git/pmap/sys/cam/cam_xpt.c:5494 >>> stack backtrace: >>> #0 0xffff0000005b3ae0 at witness_checkorder+0xd04 >>> #1 0xffff0000005b4afc at witness_warn+0x3f8 >>> #2 0xffff000000899c6c at do_el1h_sync+0x318 >>> #3 0xffff000000899a78 at do_el1h_sync+0x124 >>> #4 0xffff000000880874 at handle_el1h_sync+0x74 >>> #5 0xffff0000000161f0 at xpt_remove_periph+0x38 >>> #6 0xffff000000012674 at cam_periph_release_locked_buses+0x158 >>> #7 0xffff00000001284c at cam_periph_release_locked+0x1c >>> #8 0xffff00000002de74 at nvme_get_identify_ns+0x6d18 >>> #9 0xffff00000001b474 at xpt_done_direct+0x3b4 >>> #10 0xffff00000001d26c at xpt_register_async+0x13fc >>> #11 0xffff00000050b040 at fork_exit+0x7c >>> x0: fffffd0003fe7260 >> >> Ah yes this is known too, I only use the small cluster. I've presume a >> mutex problem between the clusters but I'm not sure. Not that this only >> shows up if you use a usb disk (well anything CAM I guess). >> >> -- >> Emmanuel Vadot >> > --------------472F11F4BA34F8B3CFD02AC3 Content-Type: text/plain; charset=UTF-8; name="temp.diff" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="temp.diff" ZGlmZiAtLWdpdCBhL3N5cy9hcm02NC9yb2NrY2hpcC9jbGsvcmszMzk5X2NydS5jIGIvc3lz L2FybTY0L3JvY2tjaGlwL2Nsay9yazMzOTlfY3J1LmMKaW5kZXggMzE2ZWZlZGYzZTIuLmEx OWM4YThmYjllIDEwMDY0NAotLS0gYS9zeXMvYXJtNjQvcm9ja2NoaXAvY2xrL3JrMzM5OV9j cnUuYworKysgYi9zeXMvYXJtNjQvcm9ja2NoaXAvY2xrL3JrMzM5OV9jcnUuYwpAQCAtMTcz OSw3ICsxNzM5LDcgQEAgc3RhdGljIHN0cnVjdCBya19jbGtfY29tcG9zaXRlX2RlZiBoY2xr X3NkID0gewogCiAjZGVmaW5lCVNDTEtfU0RNTUMJCTc2CiAKLXN0YXRpYyBjb25zdCBjaGFy ICpzY2xrX3NkbW1jX3BhcmVudHNbXSA9IHsiY3BsbCIsICJncGxsIiwgIm5wbGwiLCAicHBs bCJ9Oworc3RhdGljIGNvbnN0IGNoYXIgKnNjbGtfc2RtbWNfcGFyZW50c1tdID0geyJjcGxs IiwgImdwbGwiLCAibnBsbCIsICJwcGxsIiwgInhpbjI0bSIsICJ4aW4yNG0ifTsKIAogc3Rh dGljIHN0cnVjdCBya19jbGtfY29tcG9zaXRlX2RlZiBzY2xrX3NkbW1jID0gewogCS5jbGtk ZWYgPSB7Cg== --------------472F11F4BA34F8B3CFD02AC3-- From owner-freebsd-arm@freebsd.org Mon Oct 28 15:12:07 2019 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 401101A5616 for ; Mon, 28 Oct 2019 15:12:07 +0000 (UTC) (envelope-from warlock@phouka1.phouka.net) Received: from phouka1.phouka.net (phouka1.phouka.net [107.170.196.116]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "phouka.net", Issuer "Go Daddy Secure Certificate Authority - G2" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 471yqp1gJFz4B32 for ; Mon, 28 Oct 2019 15:12:05 +0000 (UTC) (envelope-from warlock@phouka1.phouka.net) Received: from phouka1.phouka.net (localhost [127.0.0.1]) by phouka1.phouka.net (8.15.2/8.15.2) with ESMTPS id x9SFAhZp004536 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Mon, 28 Oct 2019 08:10:43 -0700 (PDT) (envelope-from warlock@phouka1.phouka.net) Received: (from warlock@localhost) by phouka1.phouka.net (8.15.2/8.15.2/Submit) id x9SFAhdG004535; Mon, 28 Oct 2019 08:10:43 -0700 (PDT) (envelope-from warlock) Date: Mon, 28 Oct 2019 08:10:43 -0700 From: John Kennedy To: ro Ze Cc: freebsd-arm@freebsd.org Subject: Re: Is it possible to build a ZFS Raspberry Pi 3B/3B+/4 image? with other questions. Message-ID: <20191028151043.GA2664@phouka1.phouka.net> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.12.2 (2019-09-21) X-Rspamd-Queue-Id: 471yqp1gJFz4B32 X-Spamd-Bar: +++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of warlock@phouka1.phouka.net has no SPF policy when checking 107.170.196.116) smtp.mailfrom=warlock@phouka1.phouka.net X-Spamd-Result: default: False [3.29 / 15.00]; ARC_NA(0.00)[]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; IP_SCORE(0.40)[ipnet: 107.170.192.0/18(0.13), asn: 14061(1.93), country: US(-0.05)]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[phouka.net]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.90)[0.900,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_SPAM_LONG(0.79)[0.791,0]; R_SPF_NA(0.00)[]; FORGED_SENDER(0.30)[warlock@phouka.net,warlock@phouka1.phouka.net]; FREEMAIL_TO(0.00)[gmail.com]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:14061, ipnet:107.170.192.0/18, country:US]; FROM_NEQ_ENVFROM(0.00)[warlock@phouka.net,warlock@phouka1.phouka.net]; SUBJECT_HAS_QUESTION(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Oct 2019 15:12:07 -0000 On Sat, Oct 26, 2019 at 07:58:37PM +0900, ro Ze wrote: > Hi everyone, it is my first FreeBSD post. I am using FreeBSD 12.1-RC2 RPI3 > image in my Raspberry Pi 3B+. ... > > I have a few experience on FreeNAS and I know the two system are not the > same. On FreeNAS, there is a tool named iocage which is a FreeBSD Jail > manager. Using the iocage, I am allowed to pass a dedicated network > interface to the Jail via the vnet feature which is default supported in > FreeBSD 12.0. With that feature, I have a idea of using FreeBSD Jail in my > Raspberry Pi and I start to do this. FYI, the only jails I use on my RPI is for poudriere. It's a very memory constrained platform, obviously. > Before flashing the image to SD card, I had downloaded x86 DVD and > installed as a VM to learn the basic command in FreeBSD. Since the > installation process allowed me to use ZFS as the root file system, I only > had few trouble in installing the iocage and using the Jail with vnet. > However, I found that the root file system of FreeBSD RPI3 image is UFS, > which is not supported by iocage. This means that I will have to use > another storage device to create a new zpool for iocage. > > Since Raspberry Pi doesn't have native SATA port and all it's USB ports are > come from USB Hub, I believe that using iocage inside the USB will have a > huge performance drop. However, to try the feature, I adopt this situation, > create a USB zpool for iocage. I have build a zpool for Jail storage in > another USB stick in my FreeNAS and I am now import the pool to my > Raspberry Pi, and mount to the Jail. I've het to find a good enough SD card that I thought it IO-overpowered my USB-attached drive, probably made worse by throwing ZFS on top of it with my workloads (I'm specifically thinking about available RAM for disk cache). > Question part. > So, is there a way to build a ZFS image (zroot) so that I could use iocage > natively in my SD card? ... So... yes. Paraphrasing from my original notes when 12.0 was CURRENT which was apparently 2018/8/2 so you'll have to adapt. In short, I took the image FreeBSD distributed, repartitioned with ZFS and copied their files into it. It may be enough to keep iocage happy. o Grab the image to base your stuff on o Mount it via mdconfig mdconfig -a -t vnode -o readonly -f something.img -u 0 o Get your new SD card somewhere where you can write to it (I had a little USB-adapter) o Nuke all partitions on your new disk; set up partitioning gpart create -s MBR ${DISK} o Build the first partition to keep uboot happy. Note that I align my 2nd partition to 4M to try and optimize things. That \!12 is a funky way to specify the fat32lba type that I had to use at that point in time: gpart add -t freebsd -b51m -a4m -i2 ${DISK} gpart add -t \!12 -a4m -i1 ${DISK} gpart set -i1 -a active ${DISK} So now my disk looked something like this: # gpart show $DISK => 63 124735425 da0 MBR (59G) 63 8129 - free - (4.0M) 8192 98304 1 fat32lba [active] (48M) 106496 124624896 2 freebsd (59G) 124731392 4096 - free - (2.0M) o Give us a filesystem for uboot: newfs_msdos -F16 -L uboot /dev/${DISK}s1 o Set up our mountpoints for copying data: (md0s1 should be the uboot dos partition from the image) mkdir -p /mnt/src /mnt/dst /mnt/zfs mount -v -t msdosfs -o ro /dev/md0s1 /mnt/src mount -v -t msdosfs -o rw /dev/${DISK}s1 /mnt/dst sh -c "cd /mnt/src && tar cf - *" | sh -c "cd /mnt/dst && tar fvx -" umount -v /mnt/src && umount -v /mnt/dst o Now work on the BSD. As I recall here, I needed the UFS partition here for /boot since uboot couldn't handle ZFS directly. I can't say that I'm too impressed with my layout. In real life, I'd probably want to make the ZFS partition last since it's the most likely to want to get expanded. IMHO, you REALLY, REALLY want a native swap partition that's decently (if not max) sized: gpart create -s BSD ${DISK}s2 gpart add -t freebsd-zfs -a4m -s 40g ${DISK}s2 gpart add -t freebsd-ufs -a4m -s 12g ${DISK}s2 gpart add -t freebsd-swap -a4m ${DISK}s2 So the layout looked like this afterwards: # gpart show ${DISK}s2 => 0 124624896 da0s2 BSD (59G) 0 83886080 1 freebsd-zfs (40G) 83886080 25165824 2 freebsd-ufs (12G) 109051904 15572992 4 freebsd-swap (7.4G) o Rebuild UFS partition, copy data in: newfs -L uroot /dev/${DISK}s2b mount -v -t ufs -o ro /dev/md0s2a /mnt/src mount -v -t ufs -o rw /dev/${DISK}s2b /mnt/dst sh -c "cd /mnt/src && tar cf - ." | sh -c "cd /mnt/dst && tar fvx -" o Rebuild ZFS parition: zpool create -f -m none -o altroot=/mnt/zfs ${POOL} ${DISK}s2a zfs set compression=lz4 atime=off ${POOL} zfs create -o mountpoint=none ${POOL}/ROOT zfs create ${POOL}/ROOT/default zfs set mountpoint=/ canmount=noauto ${POOL}/ROOT/default zpool set bootfs=${POOL}/ROOT/default ${POOL} o Create ZFS file system hierarchy. I think I based this a bit on an old wiki article, partly my own preference (specifically obj & ports): (https://wiki.freebsd.org/RootOnZFS/GPTZFSBoot) zpool create -o altroot=/mnt zroot ada0p3 zfs set compress=on zroot zfs create -o mountpoint=none zroot/ROOT zfs create -o mountpoint=/ -o canmount=noauto zroot/ROOT/default mount -t zfs zroot/ROOT/default /mnt zfs create -o mountpoint=/tmp -o exec=on -o setuid=off zroot/tmp zfs create -o canmount=off -o mountpoint=/usr zroot/usr zfs create zroot/usr/home zfs create -o exec=on -o setuid=off zroot/usr/src zfs create zroot/usr/obj zfs create -o mountpoint=/usr/ports -o setuid=off zroot/usr/ports zfs create -o exec=off -o setuid=off zroot/usr/ports/distfiles zfs create -o exec=off -o setuid=off zroot/usr/ports/packages zfs create -o canmount=off -o mountpoint=/var zroot/var zfs create -o exec=off -o setuid=off zroot/var/audit zfs create -o exec=off -o setuid=off zroot/var/crash zfs create -o exec=off -o setuid=off zroot/var/log zfs create -o atime=on -o exec=off -o setuid=off zroot/var/mail zfs create -o exec=on -o setuid=off zroot/var/tmp o Copy the files in.... mount -vt zfs ${POOL}/ROOT/default /mnt/zfs zfs set mountpoint=/${POOL} ${POOL} sh -c "cd /mnt/src && tar cf - ." | sh -c "cd /mnt/zfs && tar fvx -" ... and customize. Make sure the various files have some ZFS things enabled: Make sure ZFS is enabled, don't allow more automatic growth: /etc/rc.conf: zfs_enable="YES" # growfs_enable="YES" /boot/loader.conf hw.usb.template=3 umodem_load="YES" opensolaris_load="YES" zfs_load="YES" Don't remember why I had the USB template. I think umodem was RPI specific. Those might have come from the original distribution and I kept them in. The ZFS stuff was obvious (I think the opensolaris may not be needed now, but at the time it was a dependency that didn't auto-load). /etc/fstab # Device Mountpoint FStype Options Dump Pass# /dev/ufs/uroot / ufs rw 1 1 /dev/msdosfs/UBOOT /boot/msdos msdosfs rw,noatime 0 0 tmpfs /tmp tmpfs rw,mode=1777,size=50m 0 0 #/dev/mmcsd0s2b none swap sw 0 0 The ZFS should auto-mount in the positions we set up when we created it. Not sure why I commented-out the swap here. From owner-freebsd-arm@freebsd.org Tue Oct 29 00:50:00 2019 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 5CA70161DBD for ; Tue, 29 Oct 2019 00:50:00 +0000 (UTC) (envelope-from mjsisan@gmail.com) Received: from mail-wm1-x329.google.com (mail-wm1-x329.google.com [IPv6:2a00:1450:4864:20::329]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 472Cfb2J9Mz3DRc for ; Tue, 29 Oct 2019 00:49:59 +0000 (UTC) (envelope-from mjsisan@gmail.com) Received: by mail-wm1-x329.google.com with SMTP id w9so719881wmm.5 for ; Mon, 28 Oct 2019 17:49:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:subject:message-id:mime-version :content-transfer-encoding; bh=FbtVHm30ipinsk5jWtqg+SQurVm/rdYuSZycTmJe6hY=; b=kiLD6i9pt/Lgtca8cMXKB7yd7k3O442vcWHscrx8MPl+pUBO7msCGQa5FTU/y2vL3i sNVZSH7JgVJMiCUWQo3NXU2irztAcPkRhyYQpUB/lXMcL3ajfx5Kr3/b3ZQEG8KSJKjd lIPxfIY4desqsKY3Xld/PSpeNdqDo7BAb/CIuIjvd3EtXTA9DV0OYhN3mbckvQZbjY1H DYd0EGurvNW9Wafx+CFKTWCRZVgfbaiQgicd5n6O+UQdsiM7Wc1O+qOyovq0zGvsIInj akTkMnj4cDNdbdkQQmnlj5ncCX6i7PNhFx/h+SdCUsRu2P2oMesv9jPwbdS+h3L8iYlN ZljQ== 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:subject:message-id:mime-version :content-transfer-encoding; bh=FbtVHm30ipinsk5jWtqg+SQurVm/rdYuSZycTmJe6hY=; b=Hwwd1kiULTdIkrwUgDR9bZyzqbd9W10vcQQm/B3vGhaSUjPAFghb/NnkoTjUMDP/cL d4mvnfXvkyzkej25NCRLwYcYrAISnrBXmWb7tQMfVFS2waUo8hohkstnJrQoczPkkBeM IIpuQTYAmy26Rjmfj40BOn7/C4M51SG5IL+7mYqis1sZdNLhiLdWqYkO3IDYr/rZy/6e 8DgFdLZaln3Qd5eaS0FWnWH/jo7Xs+JnhuQiTQk7UN0v3nkNOZNwCZkZMg9CRG4Xioet YLllLRcW76RUAECj4cK6s/TddZxgrL34E4+6OBbIG5aaMaqHPyu5mS9PfI5/xwqwHw7v RJkA== X-Gm-Message-State: APjAAAWTL1IQ5u3M3JNEPNgVVqu/qBDNycp8cCdJHgTS5oJbuS1NUQvJ yyxyvy111vcp6RdMcw+l3TYOtO8Q X-Google-Smtp-Source: APXvYqzIml710JvspUBIpKPznuap9ULbcKDq0Cd+S/6rN1vIO+SxCqdzfGMZBwYq5WH4Y7mY/NsdUA== X-Received: by 2002:a05:600c:22cd:: with SMTP id 13mr1784105wmg.52.1572310196870; Mon, 28 Oct 2019 17:49:56 -0700 (PDT) Received: from lucero (179.red-193-153-59.dynamicip.rima-tde.net. [193.153.59.179]) by smtp.gmail.com with ESMTPSA id l22sm25524628wrb.45.2019.10.28.17.49.55 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 28 Oct 2019 17:49:56 -0700 (PDT) Date: Tue, 29 Oct 2019 01:49:53 +0100 From: Miguel To: freebsd-arm@freebsd.org Subject: How to powerd in FREEBSD 12.1 STABLE over RPI-B Message-ID: <20191029014953.30d6d593@lucero> X-Mailer: Claws Mail 3.17.4 (GTK+ 2.24.32; amd64-portbld-freebsd12.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 472Cfb2J9Mz3DRc X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=kiLD6i9p; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of mjsisan@gmail.com designates 2a00:1450:4864:20::329 as permitted sender) smtp.mailfrom=mjsisan@gmail.com X-Spamd-Result: default: False [-2.50 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; TO_DN_NONE(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; RECEIVED_SPAMHAUS_PBL(0.00)[179.59.153.193.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.11]; FROM_EQ_ENVFROM(0.00)[]; IP_SCORE(0.00)[ip: (-9.30), ipnet: 2a00:1450::/32(-2.80), asn: 15169(-2.05), country: US(-0.05)]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; IP_SCORE_FREEMAIL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+]; RCVD_IN_DNSWL_NONE(0.00)[9.2.3.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; MID_RHS_NOT_FQDN(0.50)[]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Oct 2019 00:50:00 -0000 Hi all, I hope you can help me with this I have used powerd since FREEBSD 10.2 on my RPI-B, but when upgrading to FREEBSD 12 I can't get it to work. If i run: powerd powerd: no cpufreq (4) support - aborting: No such file or directory it seems that this feature is not enabled by default I also can't find any CPU when running dmesg | grep cpu (show nothing) however if I run these same commands under FreeBSD 11.2 I get different results: dmesg | grep cpu cpulist0: on ofwbus0 cpu0: on cpulist0 bcm2835_cpufreq0: on cpu0 bcm2835_cpufreq0: ARM 700MHz, Core 250MHz, SDRAM 400MHz, Turbo OFF and the powerd daemon works powerd powerd: powerd already running, pid: 789 Maybe something missing in dts? regards, Miguel From owner-freebsd-arm@freebsd.org Tue Oct 29 09:34:08 2019 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id A82E91A1A1E for ; Tue, 29 Oct 2019 09:34:08 +0000 (UTC) (envelope-from yamori813@yahoo.co.jp) Received: from nh603-vm7.bullet.mail.ssk.yahoo.co.jp (nh603-vm7.bullet.mail.ssk.yahoo.co.jp [182.22.90.48]) by mx1.freebsd.org (Postfix) with SMTP id 472RHL0ZDZz4JTT for ; Tue, 29 Oct 2019 09:34:05 +0000 (UTC) (envelope-from yamori813@yahoo.co.jp) Received: from [182.22.66.103] by nh603.bullet.mail.ssk.yahoo.co.jp with NNFMP; 29 Oct 2019 09:34:00 -0000 Received: from [182.22.91.204] by t601.bullet.mail.ssk.yahoo.co.jp with NNFMP; 29 Oct 2019 09:34:00 -0000 Received: from [127.0.0.1] by omp607.mail.ssk.yahoo.co.jp with NNFMP; 29 Oct 2019 09:34:00 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 754751.85910.bm@omp607.mail.ssk.yahoo.co.jp X-YMail-OSG: ccvSZJoVM1lIRNYE2lHq2k3uazlgNuyx8lHorv38y70MeOCsk209s8u9ZjbdkPP gw4bEbasDPN_07H.tsqHNFgl56QHI6BHBtmT7dUPVrvV2N5bOeaylMg7zNBOUAcVOAujT5gm8Pbh t6qsfqvEfLoaixCpXuXW7m2aCRl7H.qbf8UAxUc6yWUSpTjj_.2lVNqU6AHJWeArR.ieWOCZJPEG OmG0gLfoY4eO.y.j3F6jNM8B6mrYMPo3iSki3eMEnEP.tBAv1BxButfQmza5zx4oyx.j4QVuBR0o Og0EVX9tj1UUsEn0_upHOlvSYEh785SyBs46HO8Ia8wtd_z4nmBWwKG0DNPg1HlGtzY9WuOP9bI0 yh.bgpSTt5ffU3s.oUhGrXo2WoqsbPXTvhaA0.TsrJ86NwKKdieiY4QQqvnsev1Rd1JS1_3XhL3t ploz.ENb5FcqnI7McexxS4uqQi7G78XMqD_Q_50uS_jT5PTXjAAOctv7LqC2AfUdkP2UC56JsyEy YBUKHZCN3AzePYkPgnyK7krIXEaSWjObSNZb7P8RU5ucPHMN56MVmXJw8944uCXiOs1VqEH0dBjU dr50Cq.1G3MnmMl89kHT5.pZKcvuW3gywIgRSFNZup00fPSWq0yo_Tr8qfMzhzIeYopHlSeS7J7U d7.q21KISaqER_lIfutckh6bXKJQvYEiKJGucIEzBf7nQBg-- Received: from jws704108.mail.ssk.yahoo.co.jp by sendmailws614.mail.ssk.yahoo.co.jp; Tue, 29 Oct 2019 18:34:00 +0000; 1572341640.203 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1572341640; s=yj20110701; d=yahoo.co.jp; h=Date:From:Reply-To:To:Message-ID:In-Reply-To:References:Subject:MIME-Version:Content-Type:Content-Transfer-Encoding; bh=XaZbizPYCRC1wY3uF+JoSj6JwlUVv1dZDhnoWZyc1Mc=; b=E5zutL/oahPb9V/yagyxxw1uem/eKD0uP2ellbyPQl53llXyqhDxypnPiYRljU3e itE3uv3fBXfWgwzWgN6W3dkzvrn9pZr4TdO5eK1o5VmZekSZgVYhczM93PF5q9vgtNF 6zFBtFONKSBB5HLBLjSH2wN4/j90N05ejwxncA2c= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=yj20110701; d=yahoo.co.jp; h=Date:From:Reply-To:Message-ID:In-Reply-To:References:MIME-Version:Content-Type:Content-Transfer-Encoding; b=ZxhqKTBfY9w297ykllttoH6y388xgesw/eOlpjCECTaZz2SlPaSliGU/tJus4MlJ kiMpO2cwEBmm0YW6pHr7UjA7dUfi47IGi4Q18SzD5c3uf5nkPMkq4+hqXMq8SPTqoL3 fCE8Zl+WNyDairhblWZGvQL70jKrV2Ca+Yj9VPcI=; Date: Tue, 29 Oct 2019 18:33:59 +0900 (JST) From: Mori Hiroki Reply-To: Mori Hiroki To: Ian Lepore , "freebsd-arm@freebsd.org" Message-ID: <2092111865.1312240.1572341639200.JavaMail.yahoo@mail.yahoo.co.jp> In-Reply-To: <4f2516e031ce09d161afc63986b54237b5f6d3a6.camel@freebsd.org> References: <256784304.3333098.1570612921981.JavaMail.yahoo.ref@jws701102.mail.ssk.yahoo.co.jp> <256784304.3333098.1570612921981.JavaMail.yahoo@jws701102.mail.ssk.yahoo.co.jp> <4f2516e031ce09d161afc63986b54237b5f6d3a6.camel@freebsd.org> Subject: Re: arm1136 support on CURRENT MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 472RHL0ZDZz4JTT X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=yahoo.co.jp header.s=yj20110701 header.b=E5zutL/o; dmarc=pass (policy=none) header.from=yahoo.co.jp; spf=pass (mx1.freebsd.org: domain of yamori813@yahoo.co.jp designates 182.22.90.48 as permitted sender) smtp.mailfrom=yamori813@yahoo.co.jp X-Spamd-Result: default: False [-2.79 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; HAS_REPLYTO(0.00)[yamori813@yahoo.co.jp]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:182.22.90.0/23]; FREEMAIL_FROM(0.00)[yahoo.co.jp]; DKIM_TRACE(0.00)[yahoo.co.jp:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[yahoo.co.jp,none]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; IP_SCORE(0.00)[ip: (-0.16), ipnet: 182.22.0.0/17(1.88), asn: 23816(1.50), country: JP(0.00)]; FREEMAIL_ENVFROM(0.00)[yahoo.co.jp]; ASN(0.00)[asn:23816, ipnet:182.22.0.0/17, country:JP]; MIME_TRACE(0.00)[0:+]; DWL_DNSWL_NONE(0.00)[yahoo.co.jp.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.89)[-0.888,0]; R_DKIM_ALLOW(-0.20)[yahoo.co.jp:s=yj20110701]; RCVD_COUNT_FIVE(0.00)[5]; FROM_HAS_DN(0.00)[]; REPLYTO_EQ_FROM(0.00)[]; NEURAL_HAM_LONG(-1.00)[-0.998,0]; MIME_GOOD(-0.10)[text/plain]; FREEMAIL_REPLYTO(0.00)[yahoo.co.jp]; IP_SCORE_FREEMAIL(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[48.90.22.182.list.dnswl.org : 127.0.5.0]; RWL_MAILSPIKE_POSSIBLE(0.00)[48.90.22.182.rep.mailspike.net : 127.0.0.17] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Oct 2019 09:34:08 -0000 Hi I seem this is VFP issue. Comcerto 1000 is arm1136J-S. It's don't have VFP. I don't set VFP option in kernel build. Then kernel is work fine. But user land use VFP. I try to CPUTYPE=3Darmv6-soft, then build is fail. I want build arm1136J-S user land same as armv5t. Thanks Hiroki Mori ----- Original Message ----- > From: Ian Lepore > To: Mori Hiroki ; "freebsd-arm@freebsd.org" > Cc:=20 > Date: 2019/10/9, Wed 23:43 > Subject: Re: arm1136 support on CURRENT >=20 > On Wed, 2019-10-09 at 18:22 +0900, Mori Hiroki wrote: >> Hi >>=20 >> I try to Mindspeed Comcerto 1000 on CURRENT. >>=20 >> Comcerto 1000 is arm1136. >>=20 >> I write timer and pic code in kernel. >>=20 >> http://dmesgd.nycbug.org/index.cgi?do=3Dview&id=3D5136=20 >>=20 >>=20 >> Now single user sh is crash. >>=20 >> arm.armv6 clang default is 1176. But I want >> comple on 1136. >>=20 >> How to comple on 1136 on arm.armv6 ? >>=20 >> Regards >>=20 >>=20 >=20 > I don't speak officially for the freebsd project when saying this, but > I don't believe we will ever support compiling for the 1136 or any > other armv6 platform besides the original RPi.=C2=A0 There have been > increasing calls for dropping current support for armv6 and the 1176 > chip completely.=C2=A0 (Full disclosure: I am one of the people constantl= y > pushing to drop armv6 support.) >=20 > As a practical matter:=C2=A0 Already, nobody is willing to work on > continuing support for armv6 and the 1176 chip, so it's almost certain > that nobody is going to put any effort into supporting different v6 > chips. >=20 > -- Ian >=20 From owner-freebsd-arm@freebsd.org Tue Oct 29 12:59:59 2019 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id E70F21A6431 for ; Tue, 29 Oct 2019 12:59:59 +0000 (UTC) (envelope-from mjsisan@gmail.com) Received: from mail-wm1-x341.google.com (mail-wm1-x341.google.com [IPv6:2a00:1450:4864:20::341]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 472Wrv13F1z4VBD for ; Tue, 29 Oct 2019 12:59:58 +0000 (UTC) (envelope-from mjsisan@gmail.com) Received: by mail-wm1-x341.google.com with SMTP id g24so2464030wmh.5 for ; Tue, 29 Oct 2019 05:59:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:subject:message-id:in-reply-to:references:mime-version :content-transfer-encoding; bh=1bID0X2JfJEw3+duL/z2toA6+zvrRWSiZ/KZ8ekD9gc=; b=Kgr+bYp5iJXXI9oY7ZVixM2TOeyh41b6wf6bE/8R425gBkwKWqkgvcXNjApmYcxghA TFd+vTgyBV/N+qwZfkHzitdzxqXae4YOhfmvg7a+yVa9h49gT0DGHrnvghMfcdoq5T7l lgVc11wqnLOU0jbz5N1XcsQt5kt1tgc8Qq4ygP8TpYS90cVSznk9VRbnWvMakgWdqIBS EgRR3/3s2Bk1EEgcr6aSeWWVco18B1Yhxsk+y0OJASlqb8kawDuBcyh5Y/W947LtCB9T TgnINEfIaB+5rSOzbNoDvb0GSrR8vOCWpWlT1POJv62AyrXtSfLdHwiIMdLh8AcoMsgj 2pFg== 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:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=1bID0X2JfJEw3+duL/z2toA6+zvrRWSiZ/KZ8ekD9gc=; b=YxT9FNl2m4jIL3B0A5vgHuWz9K7xSbcBvyjLScqz861GtuJszShcoORGSyORYQ5Fno vDoHM23kj2fhBnlYmbpu/yh8GBdcZJilD4MtfpgYjuv4b345w9WoJdj8ovpuT8Id+wA6 NFqynqPHMYQdrkyK9zn2aEHvKvsS3sQicdss6GdUAtVykgBwUavceOH4+X27ubX0PEPC ojPZKjvy4kdRxWDX0gF/SAXl7a9Y1ZZpAWFIGAxld2UdqVBBAJg+g1guRTH15hstHy0Z dJcNP18qPXHx/ZQH3XdXC1a1H3oC5FFw2juezJMp4qVlC74FfuKBXvDSKjOks525+aSM tj0w== X-Gm-Message-State: APjAAAXZjPPgjfA007lnq++UDCckc4QaYdQgObMk+5YQ6UEXSD5K105w cbvB+zF3VVx9i/EuzNGIpZkX8sq8 X-Google-Smtp-Source: APXvYqz/BkJI+SIor/G4IDKzVlUN7MFRu09JheArehIjRB0SDoqYwVu1Ly9A5p0duduwdoPcQ66GoQ== X-Received: by 2002:a1c:1d48:: with SMTP id d69mr3797419wmd.160.1572353997550; Tue, 29 Oct 2019 05:59:57 -0700 (PDT) Received: from lucero (179.red-193-153-59.dynamicip.rima-tde.net. [193.153.59.179]) by smtp.gmail.com with ESMTPSA id o25sm18035916wro.21.2019.10.29.05.59.56 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 29 Oct 2019 05:59:56 -0700 (PDT) Date: Tue, 29 Oct 2019 13:59:55 +0100 From: Miguel To: freebsd-arm@freebsd.org Subject: Re: How to powerd in FREEBSD 12.1 STABLE over RPI-B Message-ID: <20191029135955.764b67b7@lucero> In-Reply-To: <20191029014953.30d6d593@lucero> References: <20191029014953.30d6d593@lucero> X-Mailer: Claws Mail 3.17.4 (GTK+ 2.24.32; amd64-portbld-freebsd12.0) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 472Wrv13F1z4VBD X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=Kgr+bYp5; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of mjsisan@gmail.com designates 2a00:1450:4864:20::341 as permitted sender) smtp.mailfrom=mjsisan@gmail.com X-Spamd-Result: default: False [-2.50 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; TO_DN_NONE(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; RECEIVED_SPAMHAUS_PBL(0.00)[179.59.153.193.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.11]; FROM_EQ_ENVFROM(0.00)[]; IP_SCORE(0.00)[ip: (3.13), ipnet: 2a00:1450::/32(-2.79), asn: 15169(-2.04), country: US(-0.05)]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; IP_SCORE_FREEMAIL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+]; RCVD_IN_DNSWL_NONE(0.00)[1.4.3.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; MID_RHS_NOT_FQDN(0.50)[]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Oct 2019 13:00:00 -0000 El Tue, 29 Oct 2019 01:49:53 +0100 Miguel escribi=F3: > Hi all, I hope you can help me with this >=20 > I have used powerd since FREEBSD 10.2 on my RPI-B, but when > upgrading to FREEBSD 12 I can't get it to work. If i run: > powerd > powerd: no cpufreq (4) support - aborting: No such file or > directory >=20 > it seems that this feature is not enabled by default > I also can't find any CPU when running >=20 > dmesg | grep cpu > (show nothing) >=20 > however if I run these same commands under FreeBSD 11.2 I get > different results: >=20 > dmesg | grep cpu >=20 > cpulist0: on ofwbus0 > cpu0: on cpulist0 > bcm2835_cpufreq0: on cpu0 > bcm2835_cpufreq0: ARM 700MHz, Core 250MHz, SDRAM 400MHz, Turbo OFF=20 >=20 >=20 > and the powerd daemon works >=20 > powerd > powerd: powerd already running, pid: 789 >=20 > Maybe something missing in dts? >=20 > regards, >=20 > Miguel This issue has been solved; please see https://forums.freebsd.org/threads/how-to-make-powerd-works-in-freebsd-12-1= -stable-over-rpi-b.72799/ regards, Miguel From owner-freebsd-arm@freebsd.org Tue Oct 29 13:33:30 2019 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 2777D1A6F88 for ; Tue, 29 Oct 2019 13:33:30 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 472XbZ0Km5z4WcG for ; Tue, 29 Oct 2019 13:33:30 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id E43DB22A95 for ; Tue, 29 Oct 2019 13:33:29 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x9TDXTOr099718 for ; Tue, 29 Oct 2019 13:33:29 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x9TDXT9Z099717 for freebsd-arm@FreeBSD.org; Tue, 29 Oct 2019 13:33:29 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 241388] The snapshot images of CURRENT for RPi-B do not boot till login-prompt any more Date: Tue, 29 Oct 2019 13:33:29 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: arm X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: iz-rpi03@hs-karlsruhe.de X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-arm@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Oct 2019 13:33:30 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D241388 iz-rpi03@hs-karlsruhe.de changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Open |Closed Resolution|--- |FIXED --- Comment #4 from iz-rpi03@hs-karlsruhe.de --- After updating cross-compilation system and the RPi-B to base r354130 (a li= ttle bit newer than base r354097, which contains the related llvm/clang fixes), I can announce that the issue is gone. Thank you. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-arm@freebsd.org Tue Oct 29 15:12:03 2019 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 6A3B415990F for ; Tue, 29 Oct 2019 15:12:03 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [195.149.99.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "raven.bwct.de", Issuer "raven.bwct.de" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 472ZnG1zJfz4cXT for ; Tue, 29 Oct 2019 15:12:01 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.15.2/8.15.2) with ESMTPS id x9TFCgSJ015432 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 29 Oct 2019 16:12:43 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cicely.de; s=default; t=1572361963; bh=bWiIaF0IHyIu04SkDi57oBAoQI7888thDZ6vLx4OWqw=; h=Date:From:To:Cc:Subject:Reply-To:References:In-Reply-To; b=tRbuK9sqP8QbvxiShl2j7mNpfT7/9FAEANDORBiQivMgkUjbPMiuRvEFf4cj2gWt/ BPPRiUevfkyItJ6+2QJrLkVviei8VsAHVjqpBG1G2AVEa23BfHaliFtTqpvf8pT0uj frwuw47bFKz+VHFsVsQJL4jFhvUKRDlWM74Mu4u0= Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.5/8.14.4) with ESMTP id x9TFBmDW008829 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 29 Oct 2019 16:11:48 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.15.2/8.15.2) with ESMTP id x9TFBm4V096231; Tue, 29 Oct 2019 16:11:48 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.15.2/8.15.2/Submit) id x9TFBkfa096230; Tue, 29 Oct 2019 16:11:46 +0100 (CET) (envelope-from ticso) Date: Tue, 29 Oct 2019 16:11:46 +0100 From: Bernd Walter To: John Kennedy Cc: ro Ze , freebsd-arm@freebsd.org Subject: Re: Is it possible to build a ZFS Raspberry Pi 3B/3B+/4 image? with other questions. Message-ID: <20191029151126.GV321@cicely7.cicely.de> Reply-To: ticso@cicely.de References: <20191028151043.GA2664@phouka1.phouka.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20191028151043.GA2664@phouka1.phouka.net> X-Operating-System: FreeBSD cicely7.cicely.de 12.0-STABLE amd64 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-2.9 required=4.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9 autolearn=ham version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de X-Rspamd-Queue-Id: 472ZnG1zJfz4cXT X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=cicely.de header.s=default header.b=tRbuK9sq; dmarc=none; spf=none (mx1.freebsd.org: domain of ticso@cicely7.cicely.de has no SPF policy when checking 195.149.99.3) smtp.mailfrom=ticso@cicely7.cicely.de X-Spamd-Result: default: False [-1.78 / 15.00]; ARC_NA(0.00)[]; HAS_REPLYTO(0.00)[ticso@cicely.de]; R_DKIM_ALLOW(-0.20)[cicely.de:s=default]; NEURAL_HAM_MEDIUM(-0.99)[-0.985,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[cicely.de]; REPLYTO_DOM_NEQ_FROM_DOM(0.00)[]; NEURAL_HAM_LONG(-1.00)[-0.997,0]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[cicely.de:+]; RCVD_IN_DNSWL_NONE(0.00)[3.99.149.195.list.dnswl.org : 127.0.20.0]; IP_SCORE(-0.00)[country: DE(-0.01)]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:21461, ipnet:195.149.99.0/24, country:DE]; MID_RHS_MATCH_FROM(0.00)[]; SUBJECT_HAS_QUESTION(0.00)[]; FREEMAIL_CC(0.00)[gmail.com] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Oct 2019 15:12:03 -0000 On Mon, Oct 28, 2019 at 08:10:43AM -0700, John Kennedy wrote: > On Sat, Oct 26, 2019 at 07:58:37PM +0900, ro Ze wrote: > > Hi everyone, it is my first FreeBSD post. I am using FreeBSD 12.1-RC2 RPI3 > > image in my Raspberry Pi 3B+. ... > > > > I have a few experience on FreeNAS and I know the two system are not the > > same. On FreeNAS, there is a tool named iocage which is a FreeBSD Jail > > manager. Using the iocage, I am allowed to pass a dedicated network > > interface to the Jail via the vnet feature which is default supported in > > FreeBSD 12.0. With that feature, I have a idea of using FreeBSD Jail in my > > Raspberry Pi and I start to do this. > > FYI, the only jails I use on my RPI is for poudriere. It's a very memory > constrained platform, obviously. > > > Before flashing the image to SD card, I had downloaded x86 DVD and > > installed as a VM to learn the basic command in FreeBSD. Since the > > installation process allowed me to use ZFS as the root file system, I only > > had few trouble in installing the iocage and using the Jail with vnet. > > However, I found that the root file system of FreeBSD RPI3 image is UFS, > > which is not supported by iocage. This means that I will have to use > > another storage device to create a new zpool for iocage. > > > > Since Raspberry Pi doesn't have native SATA port and all it's USB ports are > > come from USB Hub, I believe that using iocage inside the USB will have a > > huge performance drop. However, to try the feature, I adopt this situation, > > create a USB zpool for iocage. I have build a zpool for Jail storage in > > another USB stick in my FreeNAS and I am now import the pool to my > > Raspberry Pi, and mount to the Jail. > > I've het to find a good enough SD card that I thought it IO-overpowered my > USB-attached drive, probably made worse by throwing ZFS on top of it with > my workloads (I'm specifically thinking about available RAM for disk cache). SanDisk extreme cards work perfect for me. I use them for ZFS root in a mirrored setup, one card in slot and if the board has no second uSD slot, then I use an SD reader. 1GB RAM works fine for that. Compiling llvm is my RAM issue these days, even on 2GB boards a buildworld is problematic. I really like to have a system with more memory, just to compile. I've just ordered some RockPro64-4GB for that reason. Unfortunately AFAIK we don't support the RPI4 yet. I'm open for other suggestions on affordable boards with 4-8GB RAM. So far I have an iMX6 system with 4GB, but havn't tried FreeBSD on it yet and it is 32bit. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-arm@freebsd.org Tue Oct 29 18:24:57 2019 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 04B2A1602FB for ; Tue, 29 Oct 2019 18:24:57 +0000 (UTC) (envelope-from warlock@phouka1.phouka.net) Received: from phouka1.phouka.net (phouka1.phouka.net [107.170.196.116]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "phouka.net", Issuer "Go Daddy Secure Certificate Authority - G2" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 472g3r0xrBz3Pvg for ; Tue, 29 Oct 2019 18:24:55 +0000 (UTC) (envelope-from warlock@phouka1.phouka.net) Received: from phouka1.phouka.net (localhost [127.0.0.1]) by phouka1.phouka.net (8.15.2/8.15.2) with ESMTPS id x9TIMG38008499 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Tue, 29 Oct 2019 11:22:16 -0700 (PDT) (envelope-from warlock@phouka1.phouka.net) Received: (from warlock@localhost) by phouka1.phouka.net (8.15.2/8.15.2/Submit) id x9TIMFIG008498; Tue, 29 Oct 2019 11:22:15 -0700 (PDT) (envelope-from warlock) Date: Tue, 29 Oct 2019 11:22:15 -0700 From: John Kennedy To: ticso@cicely.de Cc: ro Ze , freebsd-arm@freebsd.org Subject: Re: Is it possible to build a ZFS Raspberry Pi 3B/3B+/4 image? with other questions. Message-ID: <20191029182215.GA4642@phouka1.phouka.net> References: <20191028151043.GA2664@phouka1.phouka.net> <20191029151126.GV321@cicely7.cicely.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20191029151126.GV321@cicely7.cicely.de> User-Agent: Mutt/1.12.2 (2019-09-21) X-Rspamd-Queue-Id: 472g3r0xrBz3Pvg X-Spamd-Bar: ++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of warlock@phouka1.phouka.net has no SPF policy when checking 107.170.196.116) smtp.mailfrom=warlock@phouka1.phouka.net X-Spamd-Result: default: False [2.64 / 15.00]; ARC_NA(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; IP_SCORE(0.40)[ipnet: 107.170.192.0/18(0.12), asn: 14061(1.93), country: US(-0.05)]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[phouka.net]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.69)[0.687,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_SPAM_LONG(0.35)[0.355,0]; R_SPF_NA(0.00)[]; FORGED_SENDER(0.30)[warlock@phouka.net,warlock@phouka1.phouka.net]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:14061, ipnet:107.170.192.0/18, country:US]; FROM_NEQ_ENVFROM(0.00)[warlock@phouka.net,warlock@phouka1.phouka.net]; SUBJECT_HAS_QUESTION(0.00)[]; FREEMAIL_CC(0.00)[gmail.com] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Oct 2019 18:24:57 -0000 On Tue, Oct 29, 2019 at 04:11:46PM +0100, Bernd Walter wrote: > SanDisk extreme cards work perfect for me. > I use them for ZFS root in a mirrored setup, one card in slot and if the > board has no second uSD slot, then I use an SD reader. > 1GB RAM works fine for that. > Compiling llvm is my RAM issue these days, even on 2GB boards a buildworld > is problematic. > I really like to have a system with more memory, just to compile. > I've just ordered some RockPro64-4GB for that reason. > Unfortunately AFAIK we don't support the RPI4 yet. > I'm open for other suggestions on affordable boards with 4-8GB RAM. > So far I have an iMX6 system with 4GB, but havn't tried FreeBSD on it yet > and it is 32bit. SanDisk extremes (I picked the ones rated for good video with the idea that that needs more high-speed block writes than photos) are what I use. I just haven't tried to do something like a bonnie test with that vs a USB drive, or decided if that really mattered when your workload is a big obscene compile. [I have issues doing parallel builds without fails because you never know when two things are going to fight for memory and fail (it's basically unrepeatable random luck of the draw), and if you go into OOM-failure all kinds of random things get killed off. Having 48+ hour builds get wacked just sucks.] The llvm builds are bad, rust is bad. llvm is like 48 hours, and you end up with two of those these days if you're trying to compile firefox and then add rust which is even longer (~72 hours? I forget). RPI4 should be nice. The guy who was working on it on this list had made some good progress but doesn't look like he's had a lot of time past what he's done so far. I've been eyeing the pine64 boards myself. I think I could get into their product line. That particular board has what I was looking forward to in the RPI4. It looks like FreeBSD is trying to stick mainstream (64-bit vs 32) from some of the ARM support discussions I think I remember (admittedly they were trying to cut off some old ARM chips that happened to be 32-bit, so maybe just 32-bit isn't unforgivable, but 4+G of RAM on 32-bit would be an issue unless ARM has some kind of PAE. From owner-freebsd-arm@freebsd.org Wed Oct 30 09:19:20 2019 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id BFB4B17ED02 for ; Wed, 30 Oct 2019 09:19:20 +0000 (UTC) (envelope-from yamori813@yahoo.co.jp) Received: from nh501-vm10.bullet.mail.kks.yahoo.co.jp (nh501-vm10.bullet.mail.kks.yahoo.co.jp [183.79.56.140]) by mx1.freebsd.org (Postfix) with SMTP id 4732vp1Brhz4dK7 for ; Wed, 30 Oct 2019 09:19:17 +0000 (UTC) (envelope-from yamori813@yahoo.co.jp) Received: from [183.79.100.141] by nh501.bullet.mail.kks.yahoo.co.jp with NNFMP; 30 Oct 2019 09:19:13 -0000 Received: from [183.79.100.136] by t504.bullet.mail.kks.yahoo.co.jp with NNFMP; 30 Oct 2019 09:19:13 -0000 Received: from [127.0.0.1] by omp505.mail.kks.yahoo.co.jp with NNFMP; 30 Oct 2019 09:19:13 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 99314.68855.bm@omp505.mail.kks.yahoo.co.jp X-YMail-OSG: 8C3lgOgVM1lDPfx7qNGYAqZuJqKeNLX9gJBE3VLnaJjqS2KIJEEsCGaxp3shZw4 wfw99EtWEz5yvSSq4vFymZfV1EN5Hz4SIloAUIKY16d9IsvjPlNjXhP4qk7HponKi405UphZ5y9Y i2ea0gtRfwHjB0D.j8ki2TgdGl8bejpR6tASMJl8zfubKz1TazML6aHKUmJJSBrnBgrCm8dJPFU2 ssqzaXLWc6TRhRWHF62ctbFiLTOQ2jHTpd.u30LTG5fMp3G4Z.VpBZxWPYTSYmUcOuv3MXLGx2Ua OnWNbeFEguZFjTvqa7NByMSrqiy3wOarKMcm1GDgudpY04KC8xkJ1VY1M1MVb5OAD9uNt.OBTO0A zLdm.D4xUl_yMNC_v6xMFBKaBXWjEwV1lXF.LKB9GFphoa._FYvumzpV5cWu4NdUu0aX_zAQOlfy yOgOHS1T8Nq4bA2wpRfuavrov4JMioUFm9.j0Hy.CYN5yBZrcTInfz1Nm.Q9cZlNxgSoYQJV3iZm TaDIIaLXIPW8awDAK6p2.Zz4n6swsthPUnphFOKBRK9zRLmwOagu1VywdnVN.R.QNZqrQ6fKojU_ pIXIHVyoJCmHSY2Ht9lf3yr73u1TX4iVSGVl.yf_vkcxs2HIZLO8HDiY.56GIO6qwCfNAEhrwcxX r0RHH0kQ4eWRvhyFznpEwGq04DsMXG7bA9KIQ2s30VsBL Received: from jws703102.mail.ssk.yahoo.co.jp by sendmailws613.mail.ssk.yahoo.co.jp; Wed, 30 Oct 2019 18:19:12 +0000; 1572427152.462 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1572427152; s=yj20110701; d=yahoo.co.jp; h=Date:From:Reply-To:To:Message-ID:In-Reply-To:References:Subject:MIME-Version:Content-Type:Content-Transfer-Encoding; bh=4K83ENY/jw4pUb5Y3hzHMlvEgKDoFENVRXv3hwirbCk=; b=XDnOHIr++/bK07iU/bTiPO8Zuk1ScGq1eUsRfve9VL/VRGqwEpHhC70m8H9W6xu3 AaviM1V3O88Rvp78LoVYQeSeGokXUhMkSvvfgfJzNL3dThWYhBtE0kGcxAgseN7WPjR 3APulsu2XHhiC24JP5Z9ZkVpobiDNkJ6hliPAw3M= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=yj20110701; d=yahoo.co.jp; h=Date:From:Reply-To:Message-ID:In-Reply-To:References:MIME-Version:Content-Type:Content-Transfer-Encoding; b=hdnIkMleodcVcprAh0Ve8dgkd+cl8tdkDRa7aBoAmdmIM+N0/+E1TDRh9/sPGYQo EjTbHQborz5GL7rvSuM4P736ZkDO5P7/1pCOoyn/DNSs2zIYhPXA24CrOXjauAT1lvX GCLBdQvjuaygMh6iEpBMMNWvsRKIgs1HVlhkLb4Q=; Date: Wed, 30 Oct 2019 18:19:11 +0900 (JST) From: Mori Hiroki Reply-To: Mori Hiroki To: "freebsd-arm@freebsd.org" Message-ID: <494125213.44147.1572427151682.JavaMail.yahoo@mail.yahoo.co.jp> In-Reply-To: <2092111865.1312240.1572341639200.JavaMail.yahoo@mail.yahoo.co.jp> References: <256784304.3333098.1570612921981.JavaMail.yahoo.ref@jws701102.mail.ssk.yahoo.co.jp> <256784304.3333098.1570612921981.JavaMail.yahoo@jws701102.mail.ssk.yahoo.co.jp> <4f2516e031ce09d161afc63986b54237b5f6d3a6.camel@freebsd.org> <2092111865.1312240.1572341639200.JavaMail.yahoo@mail.yahoo.co.jp> Subject: Re: arm1136 support on CURRENT MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4732vp1Brhz4dK7 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=yahoo.co.jp header.s=yj20110701 header.b=XDnOHIr+; dmarc=pass (policy=none) header.from=yahoo.co.jp; spf=pass (mx1.freebsd.org: domain of yamori813@yahoo.co.jp designates 183.79.56.140 as permitted sender) smtp.mailfrom=yamori813@yahoo.co.jp X-Spamd-Result: default: False [-2.28 / 15.00]; HAS_REPLYTO(0.00)[yamori813@yahoo.co.jp]; R_SPF_ALLOW(-0.20)[+ip4:183.79.0.0/16]; FREEMAIL_FROM(0.00)[yahoo.co.jp]; DKIM_TRACE(0.00)[yahoo.co.jp:+]; DMARC_POLICY_ALLOW(-0.50)[yahoo.co.jp,none]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[yahoo.co.jp]; ASN(0.00)[asn:24572, ipnet:183.79.0.0/16, country:JP]; IP_SCORE(0.00)[ip: (5.03), ipnet: 183.79.0.0/16(1.85), asn: 24572(1.48), country: JP(0.00)]; DWL_DNSWL_NONE(0.00)[yahoo.co.jp.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.53)[-0.529,0]; R_DKIM_ALLOW(-0.20)[yahoo.co.jp:s=yj20110701]; RCVD_COUNT_FIVE(0.00)[5]; FROM_HAS_DN(0.00)[]; REPLYTO_EQ_FROM(0.00)[]; NEURAL_HAM_LONG(-0.85)[-0.855,0]; MIME_GOOD(-0.10)[text/plain]; FREEMAIL_REPLYTO(0.00)[yahoo.co.jp]; IP_SCORE_FREEMAIL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[140.56.79.183.list.dnswl.org : 127.0.5.0]; TO_DN_EQ_ADDR_ALL(0.00)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Oct 2019 09:19:20 -0000 Hi This is error message. Why use VFP by armv6-soft ? cc -target armv6-gnueabi-freebsd13.0 --sysroot=3D/usr/home/hiroki/zobj/usr/= home/hi roki/ZRouter/tmp/usr/home/hiroki/freebsd/arm.armv6/tmp -B/usr/home/hiroki/z= obj/u sr/home/hiroki/ZRouter/tmp/usr/home/hiroki/freebsd/arm.armv6/tmp/usr/bin -O= 2 -pi pe -mfloat-abi=3Dsoftfp -mfloat-abi=3Dsoftfp -DNDEBUG -g -std=3Dgnu99 -Wno-= format-zero -length -Wsystem-headers -Wall -Wno-format-y2k -W -Wno-unused-parameter -Ws= trict -prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual = -Wwri te-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscri= pts - Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-poin= ter-s ign -Wmissing-variable-declarations -Wthread-safety -Wno-empty-body -Wno-st= ring- plus-int -Wno-unused-const-variable -Qunused-arguments=C2=A0=C2=A0=C2=A0 -o= cat.full cat.o=C2=A0=20 /usr/home/hiroki/zobj/usr/home/hiroki/ZRouter/tmp/usr/home/hiroki/freebsd/a= rm.ar mv6/tmp/lib/libc.so.7: undefined reference to `__aeabi_dcmpun_vfp' /usr/home/hiroki/zobj/usr/home/hiroki/ZRouter/tmp/usr/home/hiroki/freebsd/a= rm.ar mv6/tmp/lib/libc.so.7: undefined reference to `__aeabi_dmul_vfp' /usr/home/hiroki/zobj/usr/home/hiroki/ZRouter/tmp/usr/home/hiroki/freebsd/a= rm.ar mv6/tmp/lib/libc.so.7: undefined reference to `__aeabi_dcmplt_vfp' /usr/home/hiroki/zobj/usr/home/hiroki/ZRouter/tmp/usr/home/hiroki/freebsd/a= rm.ar mv6/tmp/lib/libc.so.7: undefined reference to `__aeabi_f2iz_vfp' /usr/home/hiroki/zobj/usr/home/hiroki/ZRouter/tmp/usr/home/hiroki/freebsd/a= rm.ar mv6/tmp/lib/libc.so.7: undefined reference to `__aeabi_dcmpge_vfp' /usr/home/hiroki/zobj/usr/home/hiroki/ZRouter/tmp/usr/home/hiroki/freebsd/a= rm.ar mv6/tmp/lib/libc.so.7: undefined reference to `__aeabi_fdiv_vfp' /usr/home/hiroki/zobj/usr/home/hiroki/ZRouter/tmp/usr/home/hiroki/freebsd/a= rm.ar mv6/tmp/lib/libc.so.7: undefined reference to `__aeabi_i2d_vfp' /usr/home/hiroki/zobj/usr/home/hiroki/ZRouter/tmp/usr/home/hiroki/freebsd/a= rm.ar mv6/tmp/lib/libc.so.7: undefined reference to `__aeabi_fcmpun_vfp' /usr/home/hiroki/zobj/usr/home/hiroki/ZRouter/tmp/usr/home/hiroki/freebsd/a= rm.ar mv6/tmp/lib/libc.so.7: undefined reference to `__aeabi_i2f_vfp' /usr/home/hiroki/zobj/usr/home/hiroki/ZRouter/tmp/usr/home/hiroki/freebsd/a= rm.ar mv6/tmp/lib/libc.so.7: undefined reference to `__aeabi_fcmple_vfp' /usr/home/hiroki/zobj/usr/home/hiroki/ZRouter/tmp/usr/home/hiroki/freebsd/a= rm.ar mv6/tmp/lib/libc.so.7: undefined reference to `__aeabi_fcmpgt_vfp' /usr/home/hiroki/zobj/usr/home/hiroki/ZRouter/tmp/usr/home/hiroki/freebsd/a= rm.ar mv6/tmp/lib/libc.so.7: undefined reference to `__aeabi_fmul_vfp' /usr/home/hiroki/zobj/usr/home/hiroki/ZRouter/tmp/usr/home/hiroki/freebsd/a= rm.ar mv6/tmp/lib/libc.so.7: undefined reference to `__aeabi_fsub_vfp' /usr/home/hiroki/zobj/usr/home/hiroki/ZRouter/tmp/usr/home/hiroki/freebsd/a= rm.ar mv6/tmp/lib/libc.so.7: undefined reference to `__aeabi_dcmple_vfp' /usr/home/hiroki/zobj/usr/home/hiroki/ZRouter/tmp/usr/home/hiroki/freebsd/a= rm.ar mv6/tmp/lib/libc.so.7: undefined reference to `__aeabi_dcmpeq_vfp' /usr/home/hiroki/zobj/usr/home/hiroki/ZRouter/tmp/usr/home/hiroki/freebsd/a= rm.ar mv6/tmp/lib/libc.so.7: undefined reference to `__aeabi_dadd_vfp' /usr/home/hiroki/zobj/usr/home/hiroki/ZRouter/tmp/usr/home/hiroki/freebsd/a= rm.ar mv6/tmp/lib/libc.so.7: undefined reference to `__aeabi_f2d_vfp' /usr/home/hiroki/zobj/usr/home/hiroki/ZRouter/tmp/usr/home/hiroki/freebsd/a= rm.ar mv6/tmp/lib/libc.so.7: undefined reference to `__aeabi_dcmpgt_vfp' /usr/home/hiroki/zobj/usr/home/hiroki/ZRouter/tmp/usr/home/hiroki/freebsd/a= rm.ar mv6/tmp/lib/libc.so.7: undefined reference to `__aeabi_fadd_vfp' /usr/home/hiroki/zobj/usr/home/hiroki/ZRouter/tmp/usr/home/hiroki/freebsd/a= rm.ar mv6/tmp/lib/libc.so.7: undefined reference to `__aeabi_fcmpeq_vfp' /usr/home/hiroki/zobj/usr/home/hiroki/ZRouter/tmp/usr/home/hiroki/freebsd/a= rm.ar mv6/tmp/lib/libc.so.7: undefined reference to `__aeabi_d2iz_vfp' /usr/home/hiroki/zobj/usr/home/hiroki/ZRouter/tmp/usr/home/hiroki/freebsd/a= rm.ar mv6/tmp/lib/libc.so.7: undefined reference to `__aeabi_dsub_vfp' /usr/home/hiroki/zobj/usr/home/hiroki/ZRouter/tmp/usr/home/hiroki/freebsd/a= rm.ar mv6/tmp/lib/libc.so.7: undefined reference to `__aeabi_fcmplt_vfp' /usr/home/hiroki/zobj/usr/home/hiroki/ZRouter/tmp/usr/home/hiroki/freebsd/a= rm.ar mv6/tmp/lib/libc.so.7: undefined reference to `__aeabi_ddiv_vfp' /usr/home/hiroki/zobj/usr/home/hiroki/ZRouter/tmp/usr/home/hiroki/freebsd/a= rm.ar mv6/tmp/lib/libc.so.7: undefined reference to `__aeabi_d2f_vfp' /usr/home/hiroki/zobj/usr/home/hiroki/ZRouter/tmp/usr/home/hiroki/freebsd/a= rm.ar mv6/tmp/lib/libc.so.7: undefined reference to `__aeabi_fcmpge_vfp' cc: error: linker command failed with exit code 1 (use -v to see invocation= ) *** Error code 1 ----- Original Message ----- > From: Mori Hiroki > To: Ian Lepore ; "freebsd-arm@freebsd.org" > Cc:=20 > Date: 2019/10/29, Tue 18:33 > Subject: Re: arm1136 support on CURRENT >=20 > Hi >=20 > I seem this is VFP issue. >=20 > Comcerto 1000 is arm1136J-S. It's don't have VFP. >=20 >=20 > I don't set VFP option in kernel build. Then kernel is work fine. >=20 > But user land use VFP. >=20 > I try to CPUTYPE=3Darmv6-soft, then build is fail. >=20 > I want build arm1136J-S user land same as armv5t. >=20 > Thanks >=20 > Hiroki Mori >=20 >=20 > ----- Original Message ----- >> From: Ian Lepore >> To: Mori Hiroki ;=20 > "freebsd-arm@freebsd.org" >> Cc:=20 >> Date: 2019/10/9, Wed 23:43 >> Subject: Re: arm1136 support on CURRENT >>=20 >> On Wed, 2019-10-09 at 18:22 +0900, Mori Hiroki wrote: >>> =C2=A0 Hi >>>=20 >>> =C2=A0 I try to Mindspeed Comcerto 1000 on CURRENT. >>>=20 >>> =C2=A0 Comcerto 1000 is arm1136. >>>=20 >>> =C2=A0 I write timer and pic code in kernel. >>>=20 >>> =C2=A0 http://dmesgd.nycbug.org/index.cgi?do=3Dview&id=3D5136=20 >>>=20 >>>=20 >>> =C2=A0 Now single user sh is crash. >>>=20 >>> =C2=A0 arm.armv6 clang default is 1176. But I want >>> =C2=A0 comple on 1136. >>>=20 >>> =C2=A0 How to comple on 1136 on arm.armv6 ? >>>=20 >>> =C2=A0 Regards >>>=20 >>>=20 >>=20 >> I don't speak officially for the freebsd project when saying this, but >> I don't believe we will ever support compiling for the 1136 or any >> other armv6 platform besides the original RPi.=C2=A0 There have been >> increasing calls for dropping current support for armv6 and the 1176 >> chip completely.=C2=A0 (Full disclosure: I am one of the people constan= tly >> pushing to drop armv6 support.) >>=20 >> As a practical matter:=C2=A0 Already, nobody is willing to work on >> continuing support for armv6 and the 1176 chip, so it's almost certain >> that nobody is going to put any effort into supporting different v6 >> chips. >>=20 >> -- Ian >>=20 >=20 > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm=20 > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" >=20 From owner-freebsd-arm@freebsd.org Wed Oct 30 23:43:10 2019 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 92B8B1658F3 for ; Wed, 30 Oct 2019 23:43:10 +0000 (UTC) (envelope-from yamori813@yahoo.co.jp) Received: from nh601-vm10.bullet.mail.ssk.yahoo.co.jp (nh601-vm10.bullet.mail.ssk.yahoo.co.jp [182.22.90.19]) by mx1.freebsd.org (Postfix) with SMTP id 473Q4W27ySz4kSf for ; Wed, 30 Oct 2019 23:43:06 +0000 (UTC) (envelope-from yamori813@yahoo.co.jp) Received: from [182.22.66.106] by nh601.bullet.mail.ssk.yahoo.co.jp with NNFMP; 30 Oct 2019 23:43:03 -0000 Received: from [182.22.91.128] by t604.bullet.mail.ssk.yahoo.co.jp with NNFMP; 30 Oct 2019 23:43:03 -0000 Received: from [127.0.0.1] by omp601.mail.ssk.yahoo.co.jp with NNFMP; 30 Oct 2019 23:43:03 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 244864.7771.bm@omp601.mail.ssk.yahoo.co.jp X-YMail-OSG: 95uUrgQVM1lPgAt0avdTcbhANXr4TvaVlo41QmSXhEw6tctXC_aqVQFZklPBrmk TLXqYPJzG7xTqXbKAsVvc_qqaQYE8nYyT4s7VPCLNbUkEkMjKn.sD49Ago8aoaW1FHuiuvSYHtXs KtZvZBtVmU1YUlrAvPlyuTVlJzHuIWT490E8PASXILm8zXZ3m7doq5y87IZ2rjt57pddZb.1R0H8 WMRZFebaVbBPAJEkNqXiW5hawEYYX8RYZ76uA.OoqrI_yfKFLfRKvM8ZXdRF3ZCwH_GIsL8.d.By .R4oRS.vPkcv8DDnLzet1rCzwd_4rKF99alvkMOTVRWrXXXB.sRD0_sIbmR1L3qcRohNxYNqxGBh 9D17qKArDR7g2ZYpzqarKGMhY3pS3SIrfdXd2XyUKNUYN77QGRgcGvujC.A3glsX_P5FfgO2Nfol RmF.ZhUqVkE7B5YjgpX3MUV7m_zdgYaZ3hFmRuEs.I9pjIbFofj1gWQfj_rYL9TdiK8CHnh2hOen OFX.RGMrEiuAV9GnIrqcHBAyWPCIQSSYXa4moWOvrROovkihN4ym.7flrrhnfZDZIpDeVz3a5OBO y1HnFKADm9cJxpR7tvwKx3O8_.6S1sKgZhIDDZHdE00PQcgFPJ6n63xeqvRPBbs6bAymQsn0Vg__ 9DLHR2akyGb8hG8LcEumCpLGX0WG0TBs_uoFBAOCzBd8n Received: from jws703006.mail.kks.yahoo.co.jp by sendmailws502.mail.kks.yahoo.co.jp; Thu, 31 Oct 2019 08:43:02 +0000; 1572478982.632 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1572478983; s=yj20110701; d=yahoo.co.jp; h=Date:From:Reply-To:To:Message-ID:In-Reply-To:References:Subject:MIME-Version:Content-Type:Content-Transfer-Encoding; bh=P/S9CVbLr6LweJ7EQ3t90yKBcsPyvO3dMJ96qJPSkWo=; b=gMjDgbupJ+F0SUt3yTt72ZwMl78h1H0DnwVEqFi8WyWMyjkLo1Tdk9yKoPh7wQCZ r1OfH8SDZlOP6V6I+uX2fPHmLlZd+hbxdz7FiFjIoz699aKVEKkh46zrkj84RMfTdVj Oe7MokmygW5DsGHkWql3M7IyhWH78U+ANUw6/bHI= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=yj20110701; d=yahoo.co.jp; h=Date:From:Reply-To:Message-ID:In-Reply-To:References:MIME-Version:Content-Type:Content-Transfer-Encoding; b=l3lAbCKJqirh1VoIN1yALvobQS5YU3I9/UOHNWArv7J6Af3DeuKwYZcTL1OzCY3p nP7E7LzAXOlZ8lagKs09VMXaV53fTF8EKbk+ygDXVgou+POqbxB0uEX0W4zOP/qnDlf 2evjI8y5ovc3dU18oMAX6AeGH1gjtvtMw7sqaH84=; Date: Thu, 31 Oct 2019 08:43:02 +0900 (JST) From: Mori Hiroki Reply-To: Mori Hiroki To: "freebsd-arm@freebsd.org" Message-ID: <71150875.1218169.1572478982147.JavaMail.yahoo@mail.yahoo.co.jp> In-Reply-To: <494125213.44147.1572427151682.JavaMail.yahoo@mail.yahoo.co.jp> References: <256784304.3333098.1570612921981.JavaMail.yahoo.ref@jws701102.mail.ssk.yahoo.co.jp> <256784304.3333098.1570612921981.JavaMail.yahoo@jws701102.mail.ssk.yahoo.co.jp> <4f2516e031ce09d161afc63986b54237b5f6d3a6.camel@freebsd.org> <2092111865.1312240.1572341639200.JavaMail.yahoo@mail.yahoo.co.jp> <494125213.44147.1572427151682.JavaMail.yahoo@mail.yahoo.co.jp> Subject: Re: arm1136 support on CURRENT MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 473Q4W27ySz4kSf X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=yahoo.co.jp header.s=yj20110701 header.b=gMjDgbup; dmarc=pass (policy=none) header.from=yahoo.co.jp; spf=pass (mx1.freebsd.org: domain of yamori813@yahoo.co.jp designates 182.22.90.19 as permitted sender) smtp.mailfrom=yamori813@yahoo.co.jp X-Spamd-Result: default: False [-2.13 / 15.00]; HAS_REPLYTO(0.00)[yamori813@yahoo.co.jp]; R_SPF_ALLOW(-0.20)[+ip4:182.22.90.0/23]; FREEMAIL_FROM(0.00)[yahoo.co.jp]; DKIM_TRACE(0.00)[yahoo.co.jp:+]; DMARC_POLICY_ALLOW(-0.50)[yahoo.co.jp,none]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; IP_SCORE(0.00)[ip: (4.10), ipnet: 182.22.0.0/17(1.88), asn: 23816(1.50), country: JP(0.00)]; FREEMAIL_ENVFROM(0.00)[yahoo.co.jp]; ASN(0.00)[asn:23816, ipnet:182.22.0.0/17, country:JP]; MIME_TRACE(0.00)[0:+]; DWL_DNSWL_NONE(0.00)[yahoo.co.jp.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.43)[-0.433,0]; R_DKIM_ALLOW(-0.20)[yahoo.co.jp:s=yj20110701]; RCVD_COUNT_FIVE(0.00)[5]; FROM_HAS_DN(0.00)[]; REPLYTO_EQ_FROM(0.00)[]; NEURAL_HAM_LONG(-0.79)[-0.793,0]; MIME_GOOD(-0.10)[text/plain]; FREEMAIL_REPLYTO(0.00)[yahoo.co.jp]; IP_SCORE_FREEMAIL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[19.90.22.182.list.dnswl.org : 127.0.5.0]; TO_DN_EQ_ADDR_ALL(0.00)[]; RWL_MAILSPIKE_POSSIBLE(0.00)[19.90.22.182.rep.mailspike.net : 127.0.0.17] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Oct 2019 23:43:10 -0000 Hi This is fix. diff --git a/lib/libc/arm/aeabi/aeabi_vfp.h b/lib/libc/arm/aeabi/aeabi_vfp.= h index 927652f193c..a7b6b7b5461 100644 --- a/lib/libc/arm/aeabi/aeabi_vfp.h +++ b/lib/libc/arm/aeabi/aeabi_vfp.h @@ -67,7 +67,7 @@ =C2=A0 * C Helper macros =C2=A0 */ =C2=A0 -#if __ARM_ARCH >=3D 6 +#if __ARM_ARCH >=3D 6 && !defined(SOFTFLOAT_FOR_GCC) =C2=A0/* =C2=A0 * Generate a function that will either call into the VFP implementat= ion, =C2=A0 * or the soft float version for a given __aeabi_* helper. The functi= on Now build is complete but I have still problem. ----- Original Message ----- > From: Mori Hiroki > To: "freebsd-arm@freebsd.org" > Cc:=20 > Date: 2019/10/30, Wed 18:19 > Subject: Re: arm1136 support on CURRENT >=20 > Hi >=20 > This is error message. >=20 > Why use VFP by armv6-soft ? >=20 > cc -target armv6-gnueabi-freebsd13.0 --sysroot=3D/usr/home/hiroki/zobj/us= r/home/hi >=20 > roki/ZRouter/tmp/usr/home/hiroki/freebsd/arm.armv6/tmp -B/usr/home/hiroki= /zobj/u > sr/home/hiroki/ZRouter/tmp/usr/home/hiroki/freebsd/arm.armv6/tmp/usr/bin = -O2 -pi > pe -mfloat-abi=3Dsoftfp -mfloat-abi=3Dsoftfp -DNDEBUG -g -std=3Dgnu99 -Wn= o-format-zero > -length -Wsystem-headers -Wall -Wno-format-y2k -W -Wno-unused-parameter -= Wstrict > -prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qua= l -Wwri > te-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subsc= ripts - > Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-po= inter-s > ign -Wmissing-variable-declarations -Wthread-safety -Wno-empty-body -Wno-= string- > plus-int -Wno-unused-const-variable -Qunused-arguments=C2=A0=C2=A0=C2=A0 = -o cat.full cat.o=C2=A0=20 > /usr/home/hiroki/zobj/usr/home/hiroki/ZRouter/tmp/usr/home/hiroki/freebsd= /arm.ar > mv6/tmp/lib/libc.so.7: undefined reference to `__aeabi_dcmpun_vfp' > /usr/home/hiroki/zobj/usr/home/hiroki/ZRouter/tmp/usr/home/hiroki/freebsd= /arm.ar > mv6/tmp/lib/libc.so.7: undefined reference to `__aeabi_dmul_vfp' > /usr/home/hiroki/zobj/usr/home/hiroki/ZRouter/tmp/usr/home/hiroki/freebsd= /arm.ar > mv6/tmp/lib/libc.so.7: undefined reference to `__aeabi_dcmplt_vfp' > /usr/home/hiroki/zobj/usr/home/hiroki/ZRouter/tmp/usr/home/hiroki/freebsd= /arm.ar > mv6/tmp/lib/libc.so.7: undefined reference to `__aeabi_f2iz_vfp' > /usr/home/hiroki/zobj/usr/home/hiroki/ZRouter/tmp/usr/home/hiroki/freebsd= /arm.ar > mv6/tmp/lib/libc.so.7: undefined reference to `__aeabi_dcmpge_vfp' > /usr/home/hiroki/zobj/usr/home/hiroki/ZRouter/tmp/usr/home/hiroki/freebsd= /arm.ar > mv6/tmp/lib/libc.so.7: undefined reference to `__aeabi_fdiv_vfp' > /usr/home/hiroki/zobj/usr/home/hiroki/ZRouter/tmp/usr/home/hiroki/freebsd= /arm.ar > mv6/tmp/lib/libc.so.7: undefined reference to `__aeabi_i2d_vfp' > /usr/home/hiroki/zobj/usr/home/hiroki/ZRouter/tmp/usr/home/hiroki/freebsd= /arm.ar > mv6/tmp/lib/libc.so.7: undefined reference to `__aeabi_fcmpun_vfp' > /usr/home/hiroki/zobj/usr/home/hiroki/ZRouter/tmp/usr/home/hiroki/freebsd= /arm.ar > mv6/tmp/lib/libc.so.7: undefined reference to `__aeabi_i2f_vfp' > /usr/home/hiroki/zobj/usr/home/hiroki/ZRouter/tmp/usr/home/hiroki/freebsd= /arm.ar > mv6/tmp/lib/libc.so.7: undefined reference to `__aeabi_fcmple_vfp' > /usr/home/hiroki/zobj/usr/home/hiroki/ZRouter/tmp/usr/home/hiroki/freebsd= /arm.ar > mv6/tmp/lib/libc.so.7: undefined reference to `__aeabi_fcmpgt_vfp' > /usr/home/hiroki/zobj/usr/home/hiroki/ZRouter/tmp/usr/home/hiroki/freebsd= /arm.ar > mv6/tmp/lib/libc.so.7: undefined reference to `__aeabi_fmul_vfp' > /usr/home/hiroki/zobj/usr/home/hiroki/ZRouter/tmp/usr/home/hiroki/freebsd= /arm.ar > mv6/tmp/lib/libc.so.7: undefined reference to `__aeabi_fsub_vfp' > /usr/home/hiroki/zobj/usr/home/hiroki/ZRouter/tmp/usr/home/hiroki/freebsd= /arm.ar > mv6/tmp/lib/libc.so.7: undefined reference to `__aeabi_dcmple_vfp' > /usr/home/hiroki/zobj/usr/home/hiroki/ZRouter/tmp/usr/home/hiroki/freebsd= /arm.ar > mv6/tmp/lib/libc.so.7: undefined reference to `__aeabi_dcmpeq_vfp' > /usr/home/hiroki/zobj/usr/home/hiroki/ZRouter/tmp/usr/home/hiroki/freebsd= /arm.ar > mv6/tmp/lib/libc.so.7: undefined reference to `__aeabi_dadd_vfp' > /usr/home/hiroki/zobj/usr/home/hiroki/ZRouter/tmp/usr/home/hiroki/freebsd= /arm.ar > mv6/tmp/lib/libc.so.7: undefined reference to `__aeabi_f2d_vfp' > /usr/home/hiroki/zobj/usr/home/hiroki/ZRouter/tmp/usr/home/hiroki/freebsd= /arm.ar > mv6/tmp/lib/libc.so.7: undefined reference to `__aeabi_dcmpgt_vfp' > /usr/home/hiroki/zobj/usr/home/hiroki/ZRouter/tmp/usr/home/hiroki/freebsd= /arm.ar > mv6/tmp/lib/libc.so.7: undefined reference to `__aeabi_fadd_vfp' > /usr/home/hiroki/zobj/usr/home/hiroki/ZRouter/tmp/usr/home/hiroki/freebsd= /arm.ar > mv6/tmp/lib/libc.so.7: undefined reference to `__aeabi_fcmpeq_vfp' > /usr/home/hiroki/zobj/usr/home/hiroki/ZRouter/tmp/usr/home/hiroki/freebsd= /arm.ar > mv6/tmp/lib/libc.so.7: undefined reference to `__aeabi_d2iz_vfp' > /usr/home/hiroki/zobj/usr/home/hiroki/ZRouter/tmp/usr/home/hiroki/freebsd= /arm.ar > mv6/tmp/lib/libc.so.7: undefined reference to `__aeabi_dsub_vfp' > /usr/home/hiroki/zobj/usr/home/hiroki/ZRouter/tmp/usr/home/hiroki/freebsd= /arm.ar > mv6/tmp/lib/libc.so.7: undefined reference to `__aeabi_fcmplt_vfp' > /usr/home/hiroki/zobj/usr/home/hiroki/ZRouter/tmp/usr/home/hiroki/freebsd= /arm.ar > mv6/tmp/lib/libc.so.7: undefined reference to `__aeabi_ddiv_vfp' > /usr/home/hiroki/zobj/usr/home/hiroki/ZRouter/tmp/usr/home/hiroki/freebsd= /arm.ar > mv6/tmp/lib/libc.so.7: undefined reference to `__aeabi_d2f_vfp' > /usr/home/hiroki/zobj/usr/home/hiroki/ZRouter/tmp/usr/home/hiroki/freebsd= /arm.ar > mv6/tmp/lib/libc.so.7: undefined reference to `__aeabi_fcmpge_vfp' > cc: error: linker command failed with exit code 1 (use -v to see invocati= on) > *** Error code 1 >=20 >=20 > ----- Original Message ----- >> From: Mori Hiroki >> To: Ian Lepore ; "freebsd-arm@freebsd.org"=20 > >> Cc:=20 >> Date: 2019/10/29, Tue 18:33 >> Subject: Re: arm1136 support on CURRENT >>=20 >> Hi >>=20 >> I seem this is VFP issue. >>=20 >> Comcerto 1000 is arm1136J-S. It's don't have VFP. >>=20 >>=20 >> I don't set VFP option in kernel build. Then kernel is work fine. >>=20 >> But user land use VFP. >>=20 >> I try to CPUTYPE=3Darmv6-soft, then build is fail. >>=20 >> I want build arm1136J-S user land same as armv5t. >>=20 >> Thanks >>=20 >> Hiroki Mori >>=20 >>=20 >> ----- Original Message ----- >>> =C2=A0 From: Ian Lepore >>> =C2=A0 To: Mori Hiroki ;=20 >> "freebsd-arm@freebsd.org" >>> =C2=A0 Cc:=20 >>> =C2=A0 Date: 2019/10/9, Wed 23:43 >>> =C2=A0 Subject: Re: arm1136 support on CURRENT >>>=20 >>> =C2=A0 On Wed, 2019-10-09 at 18:22 +0900, Mori Hiroki wrote: >>>> =C2=A0 Hi >>>>=20 >>>> =C2=A0 I try to Mindspeed Comcerto 1000 on CURRENT. >>>>=20 >>>> =C2=A0 Comcerto 1000 is arm1136. >>>>=20 >>>> =C2=A0 I write timer and pic code in kernel. >>>>=20 >>>> =C2=A0 http://dmesgd.nycbug.org/index.cgi?do=3Dview&id=3D5136=20 >>>>=20 >>>>=20 >>>> =C2=A0 Now single user sh is crash. >>>>=20 >>>> =C2=A0 arm.armv6 clang default is 1176. But I want >>>> =C2=A0 comple on 1136. >>>>=20 >>>> =C2=A0 How to comple on 1136 on arm.armv6 ? >>>>=20 >>>> =C2=A0 Regards >>>>=20 >>>>=20 >>>=20 >>> =C2=A0 I don't speak officially for the freebsd project when saying thi= s,=20 > but >>> =C2=A0 I don't believe we will ever support compiling for the 1136 or a= ny >>> =C2=A0 other armv6 platform besides the original RPi.=C2=A0 There have = been >>> =C2=A0 increasing calls for dropping current support for armv6 and the = 1176 >>> =C2=A0 chip completely.=C2=A0 (Full disclosure: I am one of the people = constantly >>> =C2=A0 pushing to drop armv6 support.) >>>=20 >>> =C2=A0 As a practical matter:=C2=A0 Already, nobody is willing to work = on >>> =C2=A0 continuing support for armv6 and the 1176 chip, so it's almost= =20 > certain >>> =C2=A0 that nobody is going to put any effort into supporting different= v6 >>> =C2=A0 chips. >>>=20 >>> =C2=A0 -- Ian >>>=20 >>=20 >> _______________________________________________ >> freebsd-arm@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-arm=20 >> To unsubscribe, send any mail to=20 > "freebsd-arm-unsubscribe@freebsd.org" >>=20 >=20 > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm=20 > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" >=20