From owner-freebsd-arm@freebsd.org Sun Nov 17 10:02: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 5DE0E1BC506 for ; Sun, 17 Nov 2019 10:02:59 +0000 (UTC) (envelope-from markm@FreeBSD.org) Received: from gromit.grondar.org (gromit.grondar.org [IPv6:2a01:348:e::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 47G71t3ykCz3MKf; Sun, 17 Nov 2019 10:02:58 +0000 (UTC) (envelope-from markm@FreeBSD.org) Received: from [2a02:8011:300b:42:8c9f:f575:e3e5:42c1] by gromit.grondar.org with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92.3 (FreeBSD)) (envelope-from ) id 1iWHOM-0005lt-0d; Sun, 17 Nov 2019 10:02:50 +0000 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\)) Subject: Re: Initial support for bcm2838 RNG From: Mark Murray In-Reply-To: Date: Sun, 17 Nov 2019 10:02:49 +0000 Cc: Robert Crowston , "freebsd-arm@freebsd.org" Content-Transfer-Encoding: quoted-printable Message-Id: <2F178D6A-300B-4683-84D6-CDB6924877E5@FreeBSD.org> References: To: Kyle Evans X-Mailer: Apple Mail (2.3601.0.10) X-Rspamd-Queue-Id: 47G71t3ykCz3MKf X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-1.83 / 15.00]; local_wl_from(0.00)[FreeBSD.org]; NEURAL_HAM_MEDIUM(-0.83)[-0.828,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; ASN(0.00)[asn:39326, ipnet:2a01:348::/32, country:GB] 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, 17 Nov 2019 10:02:59 -0000 Hi, > On 16 Nov 2019, at 18:59, Kyle Evans wrote: >=20 > On Sat, Nov 16, 2019 at 12:48 PM Robert Crowston via freebsd-arm > wrote: >>=20 >> I have made a first cut at supporting the Broadcom 2838 hardware = random number generator, as found on the Raspberry Pi 4. >>=20 >> Diff: = https://github.com/freebsd/freebsd/compare/master...RobCrowston:pi4-hwrng >>=20 >> This extends the existing bcm2835_rng.c driver to function on the = Pi4. Unfortunately I do not have a Raspberry Pi 3 board to confirm it = still works there, but on my Pi4, it generates (apparently) random = numbers. >>=20 >=20 > Hi, >=20 > No worries- I've got access to a Pi 3 for regression testing. Can you > throw what you've got into Phabricator [0] and add me as a reviewer? > We can iterate/review from there. Please also add markm@ and cem@ (or csprng@). You'll need one of us to = OK the commit. M --=20 Mark R V Murray From owner-freebsd-arm@freebsd.org Sun Nov 17 11:58:17 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 86D681BE5A5 for ; Sun, 17 Nov 2019 11:58:17 +0000 (UTC) (envelope-from sparvu@kronometrix.org) Received: from mail.kronometrix.org (mail.kronometrix.org [95.85.46.90]) (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 "mail.kronometrix.org", Issuer "mail.kronometrix.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 47G9Zv2Zhvz4MZK for ; Sun, 17 Nov 2019 11:58:14 +0000 (UTC) (envelope-from sparvu@kronometrix.org) Received: from [192.168.1.172] (84-253-221-177.bb.dnainternet.fi [84.253.221.177]) (authenticated bits=0) by mail.kronometrix.org (8.15.2/8.15.2) with ESMTPSA id xAHBvvE1016331 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Sun, 17 Nov 2019 11:58:05 GMT (envelope-from sparvu@kronometrix.org) X-Authentication-Warning: mail.kronometrix.org: Host 84-253-221-177.bb.dnainternet.fi [84.253.221.177] claimed to be [192.168.1.172] From: Stefan Parvu Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\)) Subject: FreeBSD/NetBSD bluetooth stack Message-Id: Date: Sun, 17 Nov 2019 13:57:52 +0200 To: freebsd-arm@freebsd.org X-Mailer: Apple Mail (2.3601.0.10) X-Rspamd-Queue-Id: 47G9Zv2Zhvz4MZK X-Spamd-Bar: ++++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of sparvu@kronometrix.org designates 95.85.46.90 as permitted sender) smtp.mailfrom=sparvu@kronometrix.org X-Spamd-Result: default: False [4.21 / 15.00]; ARC_NA(0.00)[]; SUBJECT_ENDS_SPACES(0.50)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; HAS_XAW(0.00)[]; NEURAL_SPAM_MEDIUM(0.88)[0.882,0]; URI_COUNT_ODD(1.00)[3]; RCPT_COUNT_ONE(0.00)[1]; TO_DN_NONE(0.00)[]; MV_CASE(0.50)[]; NEURAL_SPAM_LONG(0.98)[0.984,0]; DMARC_NA(0.00)[kronometrix.org]; IP_SCORE(0.64)[ip: (0.40), ipnet: 95.85.0.0/18(0.94), asn: 14061(1.92), country: US(-0.05)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:14061, ipnet:95.85.0.0/18, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset=us-ascii 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: Sun, 17 Nov 2019 11:58:17 -0000 Hi, FreeBSD ARM is a perfect solution for all sort of IoT projects. But = without a decent bluetooth stack implementation which could offer access to low energy sensors this = is hard to achieve. Is anyone from FreeBSD ARM group testing or experimenting with BLE ? Has = anyone looked over NetBSD project on their own Bluetooth implementation and see if it = would benefit FreeBSD community ? They (NetBSD) claim that the future NetBSD 9.0 would support = the Raspberry PI internal bluetooth device. https://wiki.netbsd.org/ports/evbarm/raspberry_pi/=20 Stefan Parvu sparvu@kronometrix.org From owner-freebsd-arm@freebsd.org Sun Nov 17 12:45:05 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 B32211BFF50 for ; Sun, 17 Nov 2019 12:45:05 +0000 (UTC) (envelope-from soren.schmidt@gmail.com) Received: from mail-lf1-x143.google.com (mail-lf1-x143.google.com [IPv6:2a00:1450:4864:20::143]) (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 47GBcw1wG9z3C4m for ; Sun, 17 Nov 2019 12:45:04 +0000 (UTC) (envelope-from soren.schmidt@gmail.com) Received: by mail-lf1-x143.google.com with SMTP id z12so11548134lfj.9 for ; Sun, 17 Nov 2019 04:45:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=bbxkERsNGmeLinZVsTIPqHJdbMrml2ZcKMp2VqdkjGk=; b=uKSvSHFdSBS0jpL/p5DukqEaCbAFkzEJbmjws32wM6m2pqr7K66m+AeHoVW36WPA/8 4wQtswG4vsW1T7GYeLYBA2WBeHCoFulsMPJrTnDlQX3neZKK03vlfNFb3Hh8Mi6ESJ1K 63/XRA1VtiAV18o++pIHR7oJ0jDxaoFEb0Ye8JC+Rbomgh5s99/RGZKyxLnQ2iCYZ35q MVpkUO3UjgiVaVDKYwc2bAsG/jLily4hMO2a7+b7XV0q3KXbQnlc6JACH7629zgxvud9 KbAH+JiLOsYQs9EjJJQNwNx/KHulU1siTZkKFdhEoCYcaDaEMFuXX8tsdsU6fiPD6RqB Pz4A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=bbxkERsNGmeLinZVsTIPqHJdbMrml2ZcKMp2VqdkjGk=; b=Q1u3JM0oKzlckvybGSSWJKP7rfCLcCJhabAO+2xYIAmgwTyxFzMO8UKTbfjyHbIE1j vJM4pAJaQ4ElYT4gN112fL5S30XGZLBnqDNOnHdtY9FuuhOp3M+BmVa0WfV99mdyVwPw wiQDIBLAIEh2xSmyu0CM4j1wdlYaWbtBIf9NzN494cU1WEbmYXLu//h23nQTVfRrOOww TKxDiwJDawLVY4LcFEoG5paYi73umrIIYi16muTbWIZeqda6zzEOi1LT+anxitXHwjDC o7PbsFZ5SH6Cb7DhZ1tIPmry7ZgRr+gOyZLPQCSaYHqjRPn/1BOavvyWLStvxfQ6KUEu aHdA== X-Gm-Message-State: APjAAAWA4MrtgpthXnsw8TzD6DkGwNpBAqLJ1xpoZ1XO0czU4vewt5WT EBdVu/wY+cLXWcJnVjWvowH+XAhS X-Google-Smtp-Source: APXvYqx+e26u/hrVEUc8J4skBxNe4yfkw+I9+MvOyzG0rxYq0+tZmTWeKxqT+scj8ft2Zoga66NLew== X-Received: by 2002:ac2:488e:: with SMTP id x14mr7914068lfc.81.1573994701872; Sun, 17 Nov 2019 04:45:01 -0800 (PST) Received: from mac.deepcore.dk ([85.27.186.9]) by smtp.gmail.com with ESMTPSA id d5sm7463341lfl.2.2019.11.17.04.45.00 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 17 Nov 2019 04:45:01 -0800 (PST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\)) Subject: Re: FreeBSD/NetBSD bluetooth stack From: =?utf-8?Q?S=C3=B8ren_Schmidt?= In-Reply-To: Date: Sun, 17 Nov 2019 13:45:00 +0100 Cc: freebsd-arm@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <0B74BF99-9028-4CE1-8893-2CB08822342A@gmail.com> References: To: Stefan Parvu X-Mailer: Apple Mail (2.3601.0.10) X-Rspamd-Queue-Id: 47GBcw1wG9z3C4m X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=uKSvSHFd; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of sorenschmidt@gmail.com designates 2a00:1450:4864:20::143 as permitted sender) smtp.mailfrom=sorenschmidt@gmail.com X-Spamd-Result: default: False [-2.50 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; MV_CASE(0.50)[]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; FROM_EQ_ENVFROM(0.00)[]; IP_SCORE(0.00)[ip: (2.73), ipnet: 2a00:1450::/32(-2.72), asn: 15169(-1.98), country: US(-0.05)]; 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]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(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)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[3.4.1.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_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: Sun, 17 Nov 2019 12:45:05 -0000 Hi I think you overread that page a bit :) =46rom what I have gleaned their bluetooth stack is just as much = abandonware as ours :) =46rom what I found out working on the banana-m2-berry that has one of = those =E2=80=9CSD enabled=E2=80=9D wifi/bt chips, the bt part can be = accessed as a serial device, so the current code could potentially = =E2=80=9Cjust work=E2=80=9D YMMW. But I agree 100% that we need to get our act together and get on with a = a working modern BT stack, and by all means a self-contained one. -S=C3=B8ren > On 17 Nov 2019, at 12.57, Stefan Parvu wrote: >=20 > Hi, >=20 > FreeBSD ARM is a perfect solution for all sort of IoT projects. But = without a decent bluetooth > stack implementation which could offer access to low energy sensors = this is hard to achieve. >=20 > Is anyone from FreeBSD ARM group testing or experimenting with BLE ? = Has anyone looked > over NetBSD project on their own Bluetooth implementation and see if = it would benefit FreeBSD > community ? They (NetBSD) claim that the future NetBSD 9.0 would = support the Raspberry PI > internal bluetooth device. >=20 > https://wiki.netbsd.org/ports/evbarm/raspberry_pi/=20 >=20 > Stefan Parvu > sparvu@kronometrix.org >=20 >=20 >=20 > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" From owner-freebsd-arm@freebsd.org Sun Nov 17 14:26:21 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 463A31C1A60 for ; Sun, 17 Nov 2019 14:26:21 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qk1-x729.google.com (mail-qk1-x729.google.com [IPv6:2607:f8b0:4864:20::729]) (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 47GDsl3YWKz4DCb for ; Sun, 17 Nov 2019 14:26:19 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-qk1-x729.google.com with SMTP id m16so12168168qki.11 for ; Sun, 17 Nov 2019 06:26:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=pxhB0sRMRVjcgRqGhqyw4d5KOyM1Z5MK6irRF4vNcG8=; b=dMpN+MSU3YcM7W/DuIEEQTUO06s8uyBWHbDFLsvzxPdZ1E5dMyS/64AyD4dQfInCg3 0xkaUHoHsiOLfrJuJtP4bamAgobq66G2DaWcUvQrRAyBGcrCZ/wnTZ9msjN1ml/1bsMD fQI0BuW4/nR+KOOOeR76ZuLRXWw+tR6r7vy6RTC3NiTI1/RrB+4NMOP/Vtt+OD8TeZrt uCjMRKneyQea8r31NFmmq7wvIzK3kByC37N3kMjjso/t27C7tKOZsaVUyo3nf3wJ7OV3 45gaVLg0w6JpYbybgyxLXy2S/klaP0ipoPYHQbzmvY63U2qLRp2ri0XA7RhUJWO9D+l1 /EqQ== 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=pxhB0sRMRVjcgRqGhqyw4d5KOyM1Z5MK6irRF4vNcG8=; b=AoXAFAdvXjC9ofvh7tbNVbZNBmvW0cBMFrTu/kFCtvrm2vXXHPiIoHIndyG3HO13hF BKcoYVRq9CThruBcLg356egcwsN9+XOI97Ag3EHnUXVXWUFErmFVUuGljbfyu8OScaFZ 8IvX0nFOVigdkjZ+2hxXnWcWU90/jS8KcH4+ELtQJ55ldD4MertyBqfKc8s0pr+wwuBB ZvoUWMsOgM8Zgl2OQdjNh37C9EfqSeSrBY+4zKVtjNp3DAdfdfDNHIY9FeCncqGljF4I 3AC+CklsfRrlrW9EL/+cX4FHYkdYfpw2yui+WNUJ0DQZ4wL7AR8G0g3b5NqbCliuHxit ZaIA== X-Gm-Message-State: APjAAAX96YnWBQXvYKK+sSh37/H0vgKOY9N0Zsn9fMzN/8CpYHYC5JT/ ABb1URMvj9GmYMO6FLeXTud2jHuCpHGjk8jxg5Xd6Ouz X-Google-Smtp-Source: APXvYqwHvv2U3baJd7nTlySz6WoAmi7nNKOiZoKE3aruoRUF42NiTVFDMOFE2SxxwcxMNauwNwo+ynM4nJacvF24g64= X-Received: by 2002:a37:4716:: with SMTP id u22mr20821819qka.495.1574000777564; Sun, 17 Nov 2019 06:26:17 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Warner Losh Date: Sun, 17 Nov 2019 07:26:05 -0700 Message-ID: Subject: Re: FreeBSD/NetBSD bluetooth stack To: Stefan Parvu Cc: freebsd-arm@freebsd.org X-Rspamd-Queue-Id: 47GDsl3YWKz4DCb X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bsdimp-com.20150623.gappssmtp.com header.s=20150623 header.b=dMpN+MSU; dmarc=none; spf=none (mx1.freebsd.org: domain of wlosh@bsdimp.com has no SPF policy when checking 2607:f8b0:4864:20::729) smtp.mailfrom=wlosh@bsdimp.com X-Spamd-Result: default: False [-4.71 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[bsdimp-com.20150623.gappssmtp.com:s=20150623]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(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)[bsdimp.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[bsdimp-com.20150623.gappssmtp.com:+]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[9.2.7.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]; R_SPF_NA(0.00)[]; FORGED_SENDER(0.30)[imp@bsdimp.com,wlosh@bsdimp.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; IP_SCORE(-2.71)[ip: (-9.22), ipnet: 2607:f8b0::/32(-2.31), asn: 15169(-1.98), country: US(-0.05)]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] 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, 17 Nov 2019 14:26:21 -0000 On Sun, Nov 17, 2019, 4:58 AM Stefan Parvu wrote: > Hi, > > FreeBSD ARM is a perfect solution for all sort of IoT projects. But > without a decent bluetooth > stack implementation which could offer access to low energy sensors this > is hard to achieve. > > Is anyone from FreeBSD ARM group testing or experimenting with BLE ? Has > anyone looked > over NetBSD project on their own Bluetooth implementation and see if it > would benefit FreeBSD > community ? They (NetBSD) claim that the future NetBSD 9.0 would support > the Raspberry PI > internal bluetooth device. > > https://wiki.netbsd.org/ports/evbarm/raspberry_pi/ > The NetBSD bluetooth stack is a slightly older version of FreeBSD's stack ported without netgraph. Max fixed a couple of bugs for me in his stack recently. What we need for the RPI is to support its side card. Warner Stefan Parvu > sparvu@kronometrix.org > > > > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" > From owner-freebsd-arm@freebsd.org Sun Nov 17 14:29: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 397BB1C1B08 for ; Sun, 17 Nov 2019 14:29:36 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (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 "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47GDxX0JKDz4MH4; Sun, 17 Nov 2019 14:29:36 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from mail-qv1-f53.google.com (mail-qv1-f53.google.com [209.85.219.53]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) (Authenticated sender: kevans) by smtp.freebsd.org (Postfix) with ESMTPSA id D444F1DFC9; Sun, 17 Nov 2019 14:29:35 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mail-qv1-f53.google.com with SMTP id x14so5517363qvu.0; Sun, 17 Nov 2019 06:29:35 -0800 (PST) X-Gm-Message-State: APjAAAWEdcr59JoFMPrnYqus6VMWDZh3H/ltmhaHoRLtp3CJm7FZGu/R GvIalEhWKamfEDh9jwtGz+OtUPNBFFZZguTNSu8= X-Google-Smtp-Source: APXvYqzcwJ3kVFnn6yAWyhj3ofbr5IEACbxkBtR9o5DR6JKWpnClZJYpnzTs5Td55jHj/0bVu+lJql9URcogCuTCJB4= X-Received: by 2002:a0c:d2b3:: with SMTP id q48mr16035535qvh.5.1574000975300; Sun, 17 Nov 2019 06:29:35 -0800 (PST) MIME-Version: 1.0 References: <2F178D6A-300B-4683-84D6-CDB6924877E5@FreeBSD.org> In-Reply-To: <2F178D6A-300B-4683-84D6-CDB6924877E5@FreeBSD.org> From: Kyle Evans Date: Sun, 17 Nov 2019 08:29:24 -0600 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Initial support for bcm2838 RNG To: Mark Murray Cc: Robert Crowston , "freebsd-arm@freebsd.org" , Conrad Meyer Content-Type: text/plain; charset="UTF-8" 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, 17 Nov 2019 14:29:36 -0000 On Sun, Nov 17, 2019 at 4:03 AM Mark Murray wrote: > > Hi, > > > On 16 Nov 2019, at 18:59, Kyle Evans wrote: > > > > On Sat, Nov 16, 2019 at 12:48 PM Robert Crowston via freebsd-arm > > wrote: > >> > >> I have made a first cut at supporting the Broadcom 2838 hardware random number generator, as found on the Raspberry Pi 4. > >> > >> Diff: https://github.com/freebsd/freebsd/compare/master...RobCrowston:pi4-hwrng > >> > >> This extends the existing bcm2835_rng.c driver to function on the Pi4. Unfortunately I do not have a Raspberry Pi 3 board to confirm it still works there, but on my Pi4, it generates (apparently) random numbers. > >> > > > > Hi, > > > > No worries- I've got access to a Pi 3 for regression testing. Can you > > throw what you've got into Phabricator [0] and add me as a reviewer? > > We can iterate/review from there. > > Please also add markm@ and cem@ (or csprng@). You'll need one of us to OK the commit. > Hi, (adding cem@ to CC list) Is there a document or something outlining what csprng@ wants to accomplish? I definitely don't object to adding you guys on this one (both because of the csprng@ origin story and this touches just enough actual RNG code path to warrant it, at a glance), but going forward- is csprng@ wanting to audit pre-existing stuff as it gets touched in any way (e.g. existing driver, just adding compatibility bits to make it probe/attach on new board), or just any new code actually affecting RNG? Thanks, Kyle Evans From owner-freebsd-arm@freebsd.org Sun Nov 17 16:02: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 69F861C3770 for ; Sun, 17 Nov 2019 16:02:01 +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 47GH076yGbz4dXm for ; Sun, 17 Nov 2019 16:01:59 +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 xAHG1rKx087672 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 17 Nov 2019 08:01:54 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id xAHG1rcf087671; Sun, 17 Nov 2019 08:01:53 -0800 (PST) (envelope-from fbsd) Date: Sun, 17 Nov 2019 08:01:53 -0800 From: bob prohaska To: Alan Cox Cc: freebsd-arm@freebsd.org, bob prohaska Subject: Re: "Invalid ASID" Patch Message-ID: <20191117160153.GA84903@www.zefox.net> References: <3ef09b7e-f7cf-bb10-1a14-a01b0c86b486@rice.edu> <20191116035936.GA80744@www.zefox.net> <5b390364-3a33-cc8e-ff88-a8b415510120@rice.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5b390364-3a33-cc8e-ff88-a8b415510120@rice.edu> User-Agent: Mutt/1.5.24 (2015-08-30) X-Rspamd-Queue-Id: 47GH076yGbz4dXm 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.22 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.79)[-0.785,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.32), 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: Sun, 17 Nov 2019 16:02:01 -0000 On Fri, Nov 15, 2019 at 10:19:33PM -0600, Alan Cox wrote: > > I've attached the patch to this email.?? Apply it to your source tree, > recompile and reinstall a new kernel, and then retry your "buildworld". > > The patched kernel compiled and booted without apparent difficulty. Uname -a reports FreeBSD 13.0-CURRENT #0 r354722M The Pi3 is now compiling www/chromium. With my thanks! bob prohaska From owner-freebsd-arm@freebsd.org Sun Nov 17 18:02:26 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 C36901C5C4A for ; Sun, 17 Nov 2019 18:02:26 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: from mail-ot1-f65.google.com (mail-ot1-f65.google.com [209.85.210.65]) (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 47GKg52LhNz4WlT; Sun, 17 Nov 2019 18:02:25 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: by mail-ot1-f65.google.com with SMTP id c14so5507505oth.2; Sun, 17 Nov 2019 10:02:25 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:reply-to :from:date:message-id:subject:to:cc; bh=DQJfUtkxLrinY87dwhqKa1m2V4KWpY9vzWv4v9Ss5Oc=; b=gst5ig4B4ItjhgZMUBF8rvuEx+3MP5dV+dV8ITJ8/4ThlFDyzGXa/9+t0ahYUWZfk4 dPy/YfUenRd3Dun5O9yJGPAiRJ1eWx+JOgiAPzAcw7V+6oHdoiafw5+2JBYAPvCAG/L5 s+/eMcOcwaVp3GyQrQdgGaJTHhMyULF3I1PmYFunlrFcfk+BMbVZnwGkOPsO9hsjlacF dVGybK/QWxbwEZGZgG6XDkaCLWqQHaIQVDCQL2yXwsd2WdYqncwq7knZWZLTzxxbJTZO TgX9HrdXHtaq9JTdB09VPoEhZ7CN22bIMUgge2DDt4WX0B5vktQmV7nQeiyvpALtYUnx dGdA== X-Gm-Message-State: APjAAAUGCRaE9Ma51NpdGIHL1jFBThH00VDWDIVsmfw+co+VW1snQXAf c+8ePuq9+I604LOz7mJbWTDFSJb3 X-Google-Smtp-Source: APXvYqzL4mXXoyBNePlP/jm8uSUGVQcqRTsMyhm5aYAiyoKJHbx9GVZNrXZ2FL90UPPiQkzlj7uEOA== X-Received: by 2002:a05:6830:1f1a:: with SMTP id u26mr17516301otg.75.1574013743798; Sun, 17 Nov 2019 10:02:23 -0800 (PST) Received: from mail-oi1-f179.google.com (mail-oi1-f179.google.com. [209.85.167.179]) by smtp.gmail.com with ESMTPSA id d5sm5047149oic.23.2019.11.17.10.02.22 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 17 Nov 2019 10:02:23 -0800 (PST) Received: by mail-oi1-f179.google.com with SMTP id n14so13172993oie.13; Sun, 17 Nov 2019 10:02:22 -0800 (PST) X-Received: by 2002:aca:1e02:: with SMTP id m2mr17105285oic.81.1574013742703; Sun, 17 Nov 2019 10:02:22 -0800 (PST) MIME-Version: 1.0 References: <2F178D6A-300B-4683-84D6-CDB6924877E5@FreeBSD.org> In-Reply-To: Reply-To: cem@freebsd.org From: Conrad Meyer Date: Sun, 17 Nov 2019 10:02:11 -0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Initial support for bcm2838 RNG To: Kyle Evans Cc: Conrad Meyer , Mark Murray , Robert Crowston , "freebsd-arm@freebsd.org" X-Rspamd-Queue-Id: 47GKg52LhNz4WlT X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of csecem@gmail.com designates 209.85.210.65 as permitted sender) smtp.mailfrom=csecem@gmail.com X-Spamd-Result: default: False [-2.03 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; HAS_REPLYTO(0.00)[cem@freebsd.org]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17:c]; RWL_MAILSPIKE_GOOD(0.00)[65.210.85.209.rep.mailspike.net : 127.0.0.18]; REPLYTO_ADDR_EQ_FROM(0.00)[]; URI_COUNT_ODD(1.00)[3]; RCPT_COUNT_FIVE(0.00)[5]; RCVD_COUNT_THREE(0.00)[4]; FORGED_SENDER(0.30)[cem@freebsd.org,csecem@gmail.com]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; TAGGED_FROM(0.00)[]; FROM_NEQ_ENVFROM(0.00)[cem@freebsd.org,csecem@gmail.com]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.99)[-0.988,0]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; DMARC_NA(0.00)[freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[65.210.85.209.list.dnswl.org : 127.0.5.0]; IP_SCORE(-1.04)[ipnet: 209.85.128.0/17(-3.18), asn: 15169(-1.98), country: US(-0.05)]; 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: Sun, 17 Nov 2019 18:02:26 -0000 I don=E2=80=99t think csprng=E2=80=99s blocker level review requirement ext= ends to individual drivers, but I might be mistaken. The kind of things we care about (imo) are, in order: the core randomdev device, the Fortuna implementation, the generic entropy gathering, and that entropy data can only be used once =E2=80=94 don=E2=80=99t expose it to a user and also feed= it to randomdev. Also, arc4random et al. Personally, I don=E2=80=99t have the expertise with this particular hardwar= e to find anything objectionable about this change. The actual change to the harvest function in this driver is de minimis. As far as I=E2=80=99m concer= ned, it looks good to me; ship it! On Sun, Nov 17, 2019 at 06:29 Kyle Evans wrote: > On Sun, Nov 17, 2019 at 4:03 AM Mark Murray wrote: > > > > Hi, > > > > > On 16 Nov 2019, at 18:59, Kyle Evans wrote: > > > > > > On Sat, Nov 16, 2019 at 12:48 PM Robert Crowston via freebsd-arm > > > wrote: > > >> > > >> I have made a first cut at supporting the Broadcom 2838 hardware > random number generator, as found on the Raspberry Pi 4. > > >> > > >> Diff: > https://github.com/freebsd/freebsd/compare/master...RobCrowston:pi4-hwrng > > >> > > >> This extends the existing bcm2835_rng.c driver to function on the > Pi4. Unfortunately I do not have a Raspberry Pi 3 board to confirm it sti= ll > works there, but on my Pi4, it generates (apparently) random numbers. > > >> > > > > > > Hi, > > > > > > No worries- I've got access to a Pi 3 for regression testing. Can you > > > throw what you've got into Phabricator [0] and add me as a reviewer? > > > We can iterate/review from there. > > > > Please also add markm@ and cem@ (or csprng@). You'll need one of us to > OK the commit. > > > > Hi, (adding cem@ to CC list) > > Is there a document or something outlining what csprng@ wants to > accomplish? I definitely don't object to adding you guys on this one > (both because of the csprng@ origin story and this touches just enough > actual RNG code path to warrant it, at a glance), but going forward- > is csprng@ wanting to audit pre-existing stuff as it gets touched in > any way (e.g. existing driver, just adding compatibility bits to make > it probe/attach on new board), or just any new code actually affecting > RNG? > > Thanks, > > Kyle Evans > From owner-freebsd-arm@freebsd.org Sun Nov 17 18:04: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 5FD591C5D06 for ; Sun, 17 Nov 2019 18:04:44 +0000 (UTC) (envelope-from sparvu@kronometrix.org) Received: from mail.kronometrix.org (mail.kronometrix.org [95.85.46.90]) (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 "mail.kronometrix.org", Issuer "mail.kronometrix.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 47GKjl1gsKz4Xk0 for ; Sun, 17 Nov 2019 18:04:43 +0000 (UTC) (envelope-from sparvu@kronometrix.org) Received: from [192.168.1.172] (84-253-221-177.bb.dnainternet.fi [84.253.221.177]) (authenticated bits=0) by mail.kronometrix.org (8.15.2/8.15.2) with ESMTPSA id xAHI4XFK018742 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Sun, 17 Nov 2019 18:04:39 GMT (envelope-from sparvu@kronometrix.org) X-Authentication-Warning: mail.kronometrix.org: Host 84-253-221-177.bb.dnainternet.fi [84.253.221.177] claimed to be [192.168.1.172] From: Stefan Parvu Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\)) Subject: Re: FreeBSD/NetBSD bluetooth stack Date: Sun, 17 Nov 2019 20:04:22 +0200 References: To: freebsd-arm@freebsd.org In-Reply-To: Message-Id: <65508BDC-9BDB-4E7B-9473-45EDA6DFDE63@kronometrix.org> X-Mailer: Apple Mail (2.3601.0.10) X-Rspamd-Queue-Id: 47GKjl1gsKz4Xk0 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of sparvu@kronometrix.org designates 95.85.46.90 as permitted sender) smtp.mailfrom=sparvu@kronometrix.org X-Spamd-Result: default: False [0.29 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-0.44)[-0.442,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; HAS_XAW(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-0.11)[-0.111,0]; TO_DN_NONE(0.00)[]; MV_CASE(0.50)[]; DMARC_NA(0.00)[kronometrix.org]; IP_SCORE(0.64)[ip: (0.40), ipnet: 95.85.0.0/18(0.94), asn: 14061(1.92), country: US(-0.05)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:14061, ipnet:95.85.0.0/18, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(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: Sun, 17 Nov 2019 18:04:44 -0000 >=20 > The NetBSD bluetooth stack is a slightly older version of FreeBSD's = stack ported without netgraph. Max fixed a couple of bugs for me in his = stack recently. What we need for the RPI is to support its side card. thanks for all pointers. So FreeBSD BLE stack could be improved.=20 Currently as 12.1 ARM image for RBPI3+ I have tried many things with no = success 1. No support for internal bluetooth device 2. Tried several BLE USB dongles, but without success to pair or see = some data from=20 BLE air quality sensors. Im expecting 2 new USB dongle models to arrive = soon.=20 Everything documented here: = https://github.com/takawata/FreeBSD-BLE/issues/1=20 I hope FreeBSD leadership can see the benefit to bring improvements = around BLE 4.x and 5.0 if we want to be able to compete and offer products and services for IoT = around FreeBSD. Thanks for listening. Stefan= From owner-freebsd-arm@freebsd.org Sun Nov 17 18:06:40 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 BC15A1C5D87 for ; Sun, 17 Nov 2019 18:06:40 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [IPv6:2a01:4f8:c17:6c4b::2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 47GKlz13cGz4YQP for ; Sun, 17 Nov 2019 18:06:38 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.129.235]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 452ED260246; Sun, 17 Nov 2019 19:06:31 +0100 (CET) Subject: Re: FreeBSD/NetBSD bluetooth stack To: Stefan Parvu , freebsd-arm@freebsd.org References: <65508BDC-9BDB-4E7B-9473-45EDA6DFDE63@kronometrix.org> From: Hans Petter Selasky Message-ID: Date: Sun, 17 Nov 2019 19:05:29 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.1.2 MIME-Version: 1.0 In-Reply-To: <65508BDC-9BDB-4E7B-9473-45EDA6DFDE63@kronometrix.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 47GKlz13cGz4YQP X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of hps@selasky.org designates 2a01:4f8:c17:6c4b::2 as permitted sender) smtp.mailfrom=hps@selasky.org X-Spamd-Result: default: False [-4.92 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+a:mail.turbocat.net]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[selasky.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; IP_SCORE(-2.62)[ip: (-9.17), ipnet: 2a01:4f8::/29(-2.29), asn: 24940(-1.64), country: DE(-0.01)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:24940, ipnet:2a01:4f8::/29, country:DE]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(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: Sun, 17 Nov 2019 18:06:40 -0000 On 2019-11-17 19:04, Stefan Parvu wrote: > 2. Tried several BLE USB dongles, but without success to pair or see some data from > BLE air quality sensors. Im expecting 2 new USB dongle models to arrive soon. > Everything documented here:https://github.com/takawata/FreeBSD-BLE/issues/1 Did you try to set: Write_Authentication_Enable to 1 using hccontrol, before trying to pair? --HPS From owner-freebsd-arm@freebsd.org Sun Nov 17 19:13:22 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 171451C77B7 for ; Sun, 17 Nov 2019 19:13:22 +0000 (UTC) (envelope-from sparvu@kronometrix.org) Received: from mail.kronometrix.org (mail.kronometrix.org [95.85.46.90]) (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 "mail.kronometrix.org", Issuer "mail.kronometrix.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 47GMDw4vGhz3Gbv for ; Sun, 17 Nov 2019 19:13:20 +0000 (UTC) (envelope-from sparvu@kronometrix.org) Received: from [192.168.1.172] (84-253-221-177.bb.dnainternet.fi [84.253.221.177]) (authenticated bits=0) by mail.kronometrix.org (8.15.2/8.15.2) with ESMTPSA id xAHJD3Tp019234 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 17 Nov 2019 19:13:16 GMT (envelope-from sparvu@kronometrix.org) X-Authentication-Warning: mail.kronometrix.org: Host 84-253-221-177.bb.dnainternet.fi [84.253.221.177] claimed to be [192.168.1.172] Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\)) Subject: Re: FreeBSD/NetBSD bluetooth stack From: Stefan Parvu In-Reply-To: Date: Sun, 17 Nov 2019 21:12:58 +0200 Cc: freebsd-arm@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <89F9D660-724D-43D4-A842-79A9A4319838@kronometrix.org> References: <65508BDC-9BDB-4E7B-9473-45EDA6DFDE63@kronometrix.org> To: Hans Petter Selasky X-Mailer: Apple Mail (2.3601.0.10) X-Rspamd-Queue-Id: 47GMDw4vGhz3Gbv X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of sparvu@kronometrix.org designates 95.85.46.90 as permitted sender) smtp.mailfrom=sparvu@kronometrix.org X-Spamd-Result: default: False [-0.55 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-0.63)[-0.629,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; HAS_XAW(0.00)[]; DMARC_NA(0.00)[kronometrix.org]; NEURAL_HAM_LONG(-0.76)[-0.759,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; IP_SCORE(0.64)[ip: (0.40), ipnet: 95.85.0.0/18(0.93), asn: 14061(1.92), country: US(-0.05)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:14061, ipnet:95.85.0.0/18, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(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: Sun, 17 Nov 2019 19:13:22 -0000 > Write_Authentication_Enable >=20 > to 1 using hccontrol, before trying to pair? I did not. I will have a look. but I think my experiments failed even = before that.=20 For example using this USB device: http://bit.ly/352J3uO I was able to = run: hccontrol read_neighbor_cache=20 but I never been able to run and get anything from:=20 hccontrol -n ubt0hci inquiry Thanks, Stefan= From owner-freebsd-arm@freebsd.org Sun Nov 17 21:01:05 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 E56091AAF8E for ; Sun, 17 Nov 2019 21:01:05 +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 47GPdF3jKrz44Bb for ; Sun, 17 Nov 2019 21:01:05 +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 5CCB81F8C5 for ; Sun, 17 Nov 2019 21:01:05 +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 xAHL15Mv091551 for ; Sun, 17 Nov 2019 21:01:05 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id xAHL152X091543 for freebsd-arm@FreeBSD.org; Sun, 17 Nov 2019 21:01:05 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201911172101.xAHL152X091543@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, 17 Nov 2019 21:01:05 +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, 17 Nov 2019 21:01:06 -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 Nov 18 15:27: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 F13531C2464 for ; Mon, 18 Nov 2019 15:27:00 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-io1-f48.google.com (mail-io1-f48.google.com [209.85.166.48]) (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 47Gt9H65ssz3Kdv; Mon, 18 Nov 2019 15:26:59 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mail-io1-f48.google.com with SMTP id s3so19211378ioe.3; Mon, 18 Nov 2019 07:26:59 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=VhaHWEo9wApg0FTVlnf/7PcnKm7WLvnVS+U9xEliG9U=; b=paSHeYfhOxNZJQrw2v5yg4rJ3pvMU2Emmgjqs0HbDv28JDcoCJZZL1bKH/fVtBo/UW VlBf3wUMvJm3CV6ltkEPCFSAcwH5Ctqlnu6dLLNm6iNsU9mypZrwjmGqyy2uceBv9jIS OSzScuDuB8GU41IMT/rFbhmoMRWn+WQCJtsHlTPAMsDHYtBNdJ1q/XLHug63QtUrv7VK B8cK9KDyR4sQ9G//lfTzSJNhtO7aY4EGMU7818GwK4wplhOJiYMM2iiHl6Sss983QnTN 8duXwXTAaTnKx3DkZhe4Go12yZEeRFuIc7Yx6/eT7l+UOdoHZx0xxqGdRLnf+9CnXBVd ythQ== X-Gm-Message-State: APjAAAUEZvX+CZH6kt/g9Nu/8oXWzSWh7QUyWJy3GFHllucbMMMqKnHn zL3syFSargozqlBB2aZD9uZFPAdcnfHs8YzfOpt3S8OE X-Google-Smtp-Source: APXvYqxhBR2adQV7RzswqSCUECrjYVxMEDnxq2r1iPbxJksA33RVXnn9+jwJd3ymbu8vKIXFzXTVBJ3XKg5CzAYouzQ= X-Received: by 2002:a02:6657:: with SMTP id l23mr13690918jaf.129.1574090817935; Mon, 18 Nov 2019 07:26:57 -0800 (PST) MIME-Version: 1.0 References: <3ef09b7e-f7cf-bb10-1a14-a01b0c86b486@rice.edu> <20191116035936.GA80744@www.zefox.net> <6ef989c5bcf052cda46f96546b445656dd062a26.camel@freebsd.org> <20191116235548.GA84297@www.zefox.net> In-Reply-To: <20191116235548.GA84297@www.zefox.net> From: Ed Maste Date: Mon, 18 Nov 2019 06:40:17 -0500 Message-ID: Subject: Re: "Invalid ASID" Patch To: bob prohaska Cc: Ian Lepore , "freebsd-arm@freebsd.org" , Alan Cox Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 47Gt9H65ssz3Kdv X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of carpeddiem@gmail.com designates 209.85.166.48 as permitted sender) smtp.mailfrom=carpeddiem@gmail.com X-Spamd-Result: default: False [-4.44 / 15.00]; ARC_NA(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; TO_DN_SOME(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[48.166.85.209.list.dnswl.org : 127.0.5.0]; IP_SCORE(-2.44)[ip: (-7.01), ipnet: 209.85.128.0/17(-3.18), asn: 15169(-1.98), country: US(-0.05)]; FORGED_SENDER(0.30)[emaste@freebsd.org,carpeddiem@gmail.com]; RWL_MAILSPIKE_POSSIBLE(0.00)[48.166.85.209.rep.mailspike.net : 127.0.0.17]; MIME_TRACE(0.00)[0:+]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; FROM_NEQ_ENVFROM(0.00)[emaste@freebsd.org,carpeddiem@gmail.com]; 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, 18 Nov 2019 15:27:01 -0000 On Sat, 16 Nov 2019 at 18:55, bob prohaska wrote: > > I should have explictly asked what was meant by "accepted" and "land", > ie, what must happen for the patch to make it into the source repository? This is terminology from other open source communities, adopted by the Phabricator code-review tool that we use. Accepted: The patch has received a positive review from one or more of the listed reviewers - specifically, someone has chosen "Accept Revision." Land: Commit the patch to the source repository. Alan "landed" the patch in SVN revision r354792. From owner-freebsd-arm@freebsd.org Tue Nov 19 00:12: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 01FB81CD6D4 for ; Tue, 19 Nov 2019 00:12:20 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 47H5qQ5cK9z3Fw3 for ; Tue, 19 Nov 2019 00:12:18 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id xAJ0CD1p093153 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 18 Nov 2019 16:12:14 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id xAJ0CD2l093152; Mon, 18 Nov 2019 16:12:13 -0800 (PST) (envelope-from fbsd) Date: Mon, 18 Nov 2019 16:12:13 -0800 From: bob prohaska To: freebsd-arm@freebsd.org Subject: Another "invalid ASID" panic on an rpi3 running r354796 Message-ID: <20191119001213.GA93097@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.24 (2015-08-30) X-Rspamd-Queue-Id: 47H5qQ5cK9z3Fw3 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.35 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.91)[-0.913,0]; WWW_DOT_DOMAIN(0.50)[]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; IP_SCORE(0.08)[ip: (0.31), 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.72)[-0.717,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; 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: Tue, 19 Nov 2019 00:12:20 -0000 The "invalid ASID" patch seemed to apply without error and caused no visible problems on a Pi3 running r354796. An attempt to crash the machine by running stress2's misc/all.sh test for perhaps an hour failed. However, after stopping stress2 I started an old build of www/chromium, and the machine promptly panic'd: panic: invalid ASID cpuid = 0 time = 1574121393 KDB: stack backtrace: db_trace_self() at db_trace_self_wrapper+0x28 pc = 0xffff00000072947c lr = 0xffff0000001064f0 sp = 0xffff000051927310 fp = 0xffff000051927520 db_trace_self_wrapper() at vpanic+0x18c pc = 0xffff0000001064f0 lr = 0xffff000000400b5c sp = 0xffff000051927530 fp = 0xffff0000519275e0 vpanic() at panic+0x44 pc = 0xffff000000400b5c lr = 0xffff00000040090c sp = 0xffff0000519275f0 fp = 0xffff000051927670 panic() at pmap_remove_write+0x564 pc = 0xffff00000040090c lr = 0xffff000000740e9c sp = 0xffff000051927680 fp = 0xffff0000519276e0 pmap_remove_write() at vfs_busy_pages+0xe8 pc = 0xffff000000740e9c lr = 0xffff0000004accec sp = 0xffff0000519276f0 fp = 0xffff000051927730 vfs_busy_pages() at bufwrite+0x10c pc = 0xffff0000004accec lr = 0xffff0000004aa628 sp = 0xffff000051927740 fp = 0xffff000051927770 bufwrite() at cluster_wbuild+0x624 pc = 0xffff0000004aa628 lr = 0xffff0000004bb360 sp = 0xffff000051927780 fp = 0xffff000051927820 cluster_wbuild() at flushbufqueues+0x4c0 pc = 0xffff0000004bb360 lr = 0xffff0000004b2610 sp = 0xffff000051927830 fp = 0xffff0000519278e0 flushbufqueues() at buf_daemon+0x228 pc = 0xffff0000004b2610 lr = 0xffff0000004b1d20 sp = 0xffff0000519278f0 fp = 0xffff000051927940 buf_daemon() at fork_exit+0x7c pc = 0xffff0000004b1d20 lr = 0xffff0000003c0eb0 sp = 0xffff000051927950 fp = 0xffff000051927980 fork_exit() at fork_trampoline+0x10 pc = 0xffff0000003c0eb0 lr = 0xffff0000007458bc sp = 0xffff000051927990 fp = 0x0000000000000000 KDB: enter: panic [ thread pid 23 tid 100068 ] Stopped at 0 db> bt Tracing pid 23 tid 100068 td 0xfffffd0000d7e560 db_trace_self() at db_stack_trace+0xf8 pc = 0xffff00000072947c lr = 0xffff000000103934 sp = 0xffff000051926ee0 fp = 0xffff000051926f10 db_stack_trace() at db_command+0x228 pc = 0xffff000000103934 lr = 0xffff0000001035ac sp = 0xffff000051926f20 fp = 0xffff000051927000 db_command() at db_command_loop+0x58 pc = 0xffff0000001035ac lr = 0xffff000000103354 sp = 0xffff000051927010 fp = 0xffff000051927030 db_command_loop() at db_trap+0xf4 pc = 0xffff000000103354 lr = 0xffff000000106658 sp = 0xffff000051927040 fp = 0xffff000051927260 db_trap() at kdb_trap+0x1d8 pc = 0xffff000000106658 lr = 0xffff0000004490f4 sp = 0xffff000051927270 fp = 0xffff000051927320 kdb_trap() at do_el1h_sync+0xf4 pc = 0xffff0000004490f4 lr = 0xffff000000745b30 sp = 0xffff000051927330 fp = 0xffff000051927360 do_el1h_sync() at handle_el1h_sync+0x78 pc = 0xffff000000745b30 lr = 0xffff00000072b878 sp = 0xffff000051927370 fp = 0xffff000051927480 handle_el1h_sync() at kdb_enter+0x34 pc = 0xffff00000072b878 lr = 0xffff000000448740 sp = 0xffff000051927490 fp = 0xffff000051927520 kdb_enter() at vpanic+0x1a8 pc = 0xffff000000448740 lr = 0xffff000000400b78 sp = 0xffff000051927530 fp = 0xffff0000519275e0 vpanic() at panic+0x44 pc = 0xffff000000400b78 lr = 0xffff00000040090c sp = 0xffff0000519275f0 fp = 0xffff000051927670 panic() at pmap_remove_write+0x564 pc = 0xffff00000040090c lr = 0xffff000000740e9c sp = 0xffff000051927680 fp = 0xffff0000519276e0 pmap_remove_write() at vfs_busy_pages+0xe8 pc = 0xffff000000740e9c lr = 0xffff0000004accec sp = 0xffff0000519276f0 fp = 0xffff000051927730 vfs_busy_pages() at bufwrite+0x10c pc = 0xffff0000004accec lr = 0xffff0000004aa628 sp = 0xffff000051927740 fp = 0xffff000051927770 bufwrite() at cluster_wbuild+0x624 pc = 0xffff0000004aa628 lr = 0xffff0000004bb360 sp = 0xffff000051927780 fp = 0xffff000051927820 cluster_wbuild() at flushbufqueues+0x4c0 pc = 0xffff0000004bb360 lr = 0xffff0000004b2610 sp = 0xffff000051927830 fp = 0xffff0000519278e0 flushbufqueues() at buf_daemon+0x228 pc = 0xffff0000004b2610 lr = 0xffff0000004b1d20 sp = 0xffff0000519278f0 fp = 0xffff000051927940 buf_daemon() at fork_exit+0x7c pc = 0xffff0000004b1d20 lr = 0xffff0000003c0eb0 sp = 0xffff000051927950 fp = 0xffff000051927980 fork_exit() at fork_trampoline+0x10 pc = 0xffff0000003c0eb0 lr = 0xffff0000007458bc sp = 0xffff000051927990 fp = 0x0000000000000000 db> Please let me know if there's anything I can do to gather more useful information. Thanks for reading, bob prohaska From owner-freebsd-arm@freebsd.org Tue Nov 19 04:07:22 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 DA5C317B8C3 for ; Tue, 19 Nov 2019 04:07:22 +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 47HC2d213pz3xxb for ; Tue, 19 Nov 2019 04:07:20 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id xAJ47L48093777 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 18 Nov 2019 20:07:22 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id xAJ47LdQ093776; Mon, 18 Nov 2019 20:07:21 -0800 (PST) (envelope-from fbsd) Date: Mon, 18 Nov 2019 20:07:20 -0800 From: bob prohaska To: freebsd-arm@freebsd.org Subject: Re: Another "invalid ASID" panic on an rpi3 running r354796 Message-ID: <20191119040720.GB93097@www.zefox.net> References: <20191119001213.GA93097@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20191119001213.GA93097@www.zefox.net> User-Agent: Mutt/1.5.24 (2015-08-30) X-Rspamd-Queue-Id: 47HC2d213pz3xxb 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.26 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.97)[-0.974,0]; WWW_DOT_DOMAIN(0.50)[]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; IP_SCORE(0.07)[ip: (0.31), 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.74)[-0.744,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; 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: Tue, 19 Nov 2019 04:07:22 -0000 Not sure this is useful, but another panic was provoked by first starting www/chromium and then starting stress2/misc/all.sh..... 20191118 19:59:45 all (1/526): mmap21.sh panic: invalid ASID cpuid = 3 time = 1574136018 KDB: stack backtrace: db_trace_self() at db_trace_self_wrapper+0x28 pc = 0xffff00000072947c lr = 0xffff0000001064f0 sp = 0xffff00005191d0f0 fp = 0xffff00005191d300 db_trace_self_wrapper() at vpanic+0x18c pc = 0xffff0000001064f0 lr = 0xffff000000400b5c sp = 0xffff00005191d310 fp = 0xffff00005191d3c0 vpanic() at panic+0x44 pc = 0xffff000000400b5c lr = 0xffff00000040090c sp = 0xffff00005191d3d0 fp = 0xffff00005191d450 panic() at pmap_ts_referenced+0x820 pc = 0xffff00000040090c lr = 0xffff000000741714 sp = 0xffff00005191d460 fp = 0xffff00005191d4f0 pmap_ts_referenced() at vm_pageout_worker+0xe2c pc = 0xffff000000741714 lr = 0xffff0000006e46d4 sp = 0xffff00005191d500 fp = 0xffff00005191d8d0 vm_pageout_worker() at vm_pageout+0x1b0 pc = 0xffff0000006e46d4 lr = 0xffff0000006e3894 sp = 0xffff00005191d8e0 fp = 0xffff00005191d940 vm_pageout() at fork_exit+0x7c pc = 0xffff0000006e3894 lr = 0xffff0000003c0eb0 sp = 0xffff00005191d950 fp = 0xffff00005191d980 fork_exit() at fork_trampoline+0x10 pc = 0xffff0000003c0eb0 lr = 0xffff0000007458bc sp = 0xffff00005191d990 fp = 0x0000000000000000 KDB: enter: panic [ thread pid 21 tid 100066 ] Stopped at 0 db> bt Tracing pid 21 tid 100066 td 0xfffffd0000d7f560 db_trace_self() at db_stack_trace+0xf8 pc = 0xffff00000072947c lr = 0xffff000000103934 sp = 0xffff00005191ccc0 fp = 0xffff00005191ccf0 db_stack_trace() at db_command+0x228 pc = 0xffff000000103934 lr = 0xffff0000001035ac sp = 0xffff00005191cd00 fp = 0xffff00005191cde0 db_command() at db_command_loop+0x58 pc = 0xffff0000001035ac lr = 0xffff000000103354 sp = 0xffff00005191cdf0 fp = 0xffff00005191ce10 db_command_loop() at db_trap+0xf4 pc = 0xffff000000103354 lr = 0xffff000000106658 sp = 0xffff00005191ce20 fp = 0xffff00005191d040 db_trap() at kdb_trap+0x1d8 pc = 0xffff000000106658 lr = 0xffff0000004490f4 sp = 0xffff00005191d050 fp = 0xffff00005191d100 kdb_trap() at do_el1h_sync+0xf4 pc = 0xffff0000004490f4 lr = 0xffff000000745b30 sp = 0xffff00005191d110 fp = 0xffff00005191d140 do_el1h_sync() at handle_el1h_sync+0x78 pc = 0xffff000000745b30 lr = 0xffff00000072b878 sp = 0xffff00005191d150 fp = 0xffff00005191d260 handle_el1h_sync() at kdb_enter+0x34 pc = 0xffff00000072b878 lr = 0xffff000000448740 sp = 0xffff00005191d270 fp = 0xffff00005191d300 kdb_enter() at vpanic+0x1a8 pc = 0xffff000000448740 lr = 0xffff000000400b78 sp = 0xffff00005191d310 fp = 0xffff00005191d3c0 vpanic() at panic+0x44 pc = 0xffff000000400b78 lr = 0xffff00000040090c sp = 0xffff00005191d3d0 fp = 0xffff00005191d450 panic() at pmap_ts_referenced+0x820 pc = 0xffff00000040090c lr = 0xffff000000741714 sp = 0xffff00005191d460 fp = 0xffff00005191d4f0 pmap_ts_referenced() at vm_pageout_worker+0xe2c pc = 0xffff000000741714 lr = 0xffff0000006e46d4 sp = 0xffff00005191d500 fp = 0xffff00005191d8d0 vm_pageout_worker() at vm_pageout+0x1b0 pc = 0xffff0000006e46d4 lr = 0xffff0000006e3894 sp = 0xffff00005191d8e0 fp = 0xffff00005191d940 vm_pageout() at fork_exit+0x7c pc = 0xffff0000006e3894 lr = 0xffff0000003c0eb0 sp = 0xffff00005191d950 fp = 0xffff00005191d980 fork_exit() at fork_trampoline+0x10 pc = 0xffff0000003c0eb0 lr = 0xffff0000007458bc sp = 0xffff00005191d990 fp = 0x0000000000000000 db> www/chromium ran for over an hour with no panic. Starting stress2/misc/all.sh resulted in a panic in tens of seconds. Thanks for reading, bob prohaska From owner-freebsd-arm@freebsd.org Tue Nov 19 19:34:33 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 33B411BC0FE for ; Tue, 19 Nov 2019 19:34:33 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-il1-f170.google.com (mail-il1-f170.google.com [209.85.166.170]) (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 47HbcS2yRWz3MNT for ; Tue, 19 Nov 2019 19:34:32 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mail-il1-f170.google.com with SMTP id o18so20792310ils.12 for ; Tue, 19 Nov 2019 11:34:32 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=0rJkGun9RWGWQmNK7PyJHxbdeBzY060b63i0Vc32o38=; b=r0mivJ0F7tbtfAe034Ic/3t3R8KgN2lIFH5tVBqYvT9SAQAVXcDhBI5KD8czSTeI/b SXCkt+wSzKcrsVJXP1Q+BSEO7atm+afmnBb3i8T3HeQlrCmr1+oPxKv4sZbplF2LHUET 9bWV5Kn4Yws+qZCkAnH84xcOdsZwif2Lv/siWjFB1sz1t6QLVuVTpAaMVCU86z19vTQQ 81b2URwglVwvw1iK3Rg3TRMafFugn9H/UdTpM0BrvGe0XqFw0s7hfs/WQPj4jJOWPABR M0poqVQ3l/d9XR9dbLvoCnOocEHqOwAjlYtjhRVTBgXEC6QNhTJe30qyVKMcNKRR+mwE Sd9w== X-Gm-Message-State: APjAAAVMjSnxEiYYy3GNyoKshy2YMG3DAfjvmTrQkcAKdLcYzolAlyW4 EHzKJ2JOZC+DBgk1vbSNKgdbxDFfOrOytn/DiabazA== X-Google-Smtp-Source: APXvYqxV47oK3ocPdNGm54YU2S9Y2WKDHTtHghVjpO3J6QXR0j1o5DZ5iZ/gwv2CEPvVNCVIyXtSYKh04me4/8SiF/E= X-Received: by 2002:a92:2450:: with SMTP id k77mr23501442ilk.120.1574192071032; Tue, 19 Nov 2019 11:34:31 -0800 (PST) MIME-Version: 1.0 References: <20191119001213.GA93097@www.zefox.net> In-Reply-To: <20191119001213.GA93097@www.zefox.net> From: Ed Maste Date: Tue, 19 Nov 2019 10:47:51 -0500 Message-ID: Subject: Re: Another "invalid ASID" panic on an rpi3 running r354796 To: bob prohaska Cc: "freebsd-arm@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 47HbcS2yRWz3MNT X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of carpeddiem@gmail.com designates 209.85.166.170 as permitted sender) smtp.mailfrom=carpeddiem@gmail.com X-Spamd-Result: default: False [-4.03 / 15.00]; ARC_NA(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; DMARC_NA(0.00)[freebsd.org]; MIME_TRACE(0.00)[0:+]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[170.166.85.209.list.dnswl.org : 127.0.5.0]; IP_SCORE(-2.03)[ip: (-4.92), ipnet: 209.85.128.0/17(-3.18), asn: 15169(-1.97), country: US(-0.05)]; FORGED_SENDER(0.30)[emaste@freebsd.org,carpeddiem@gmail.com]; RWL_MAILSPIKE_POSSIBLE(0.00)[170.166.85.209.rep.mailspike.net : 127.0.0.17]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; FROM_NEQ_ENVFROM(0.00)[emaste@freebsd.org,carpeddiem@gmail.com]; RCVD_TLS_ALL(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: Tue, 19 Nov 2019 19:34:33 -0000 On Mon, 18 Nov 2019 at 19:12, bob prohaska wrote: > > However, after stopping stress2 I started an old build of www/chromium, > and the machine promptly panic'd: > > panic: invalid ASID I see another ASID fix just went in - r354860. Would you update and try again? From owner-freebsd-arm@freebsd.org Tue Nov 19 22:31:24 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 04FE21C0104 for ; Tue, 19 Nov 2019 22:31:24 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 47HgXW5Pzpz42M6; Tue, 19 Nov 2019 22:31:23 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id xAJMVNbs096868 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 19 Nov 2019 14:31:24 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id xAJMVNtv096867; Tue, 19 Nov 2019 14:31:23 -0800 (PST) (envelope-from fbsd) Date: Tue, 19 Nov 2019 14:31:23 -0800 From: bob prohaska To: Ed Maste Cc: "freebsd-arm@freebsd.org" , bob prohaska Subject: Re: Another "invalid ASID" panic on an rpi3 running r354796 Message-ID: <20191119223123.GA96279@www.zefox.net> References: <20191119001213.GA93097@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: 47HgXW5Pzpz42M6 X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-5.99 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-0.996,0]; REPLY(-4.00)[]; NEURAL_HAM_LONG(-0.99)[-0.994,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, 19 Nov 2019 22:31:24 -0000 On Tue, Nov 19, 2019 at 10:47:51AM -0500, Ed Maste wrote: > On Mon, 18 Nov 2019 at 19:12, bob prohaska wrote: > > > > However, after stopping stress2 I started an old build of www/chromium, > > and the machine promptly panic'd: > > > > panic: invalid ASID > > I see another ASID fix just went in - r354860. Would you update and try again? Yes, soon as the present build/install cycle finishes, unless there's a way to update on the fly (which seems risky). Thanks for the headsup! bob prohaska From owner-freebsd-arm@freebsd.org Wed Nov 20 09:49:05 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 F10E21B085C for ; Wed, 20 Nov 2019 09:49:05 +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 47HyZT66zMz4ZXq for ; Wed, 20 Nov 2019 09:49:05 +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 B5ABF20DE0 for ; Wed, 20 Nov 2019 09:49:05 +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 xAK9n56C036465 for ; Wed, 20 Nov 2019 09:49:05 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id xAK9n5Yl036464 for freebsd-arm@FreeBSD.org; Wed, 20 Nov 2019 09:49:05 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-arm@FreeBSD.org Subject: [Bug 242101] sdhci-bcm0-slot0 controller timeouts with r354850 Date: Wed, 20 Nov 2019 09:49:05 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: arm X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: iz-rpi03@hs-karlsruhe.de X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-arm@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter attachments.created Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.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, 20 Nov 2019 09:49:06 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D242101 Bug ID: 242101 Summary: sdhci-bcm0-slot0 controller timeouts with r354850 Product: Base System Version: CURRENT Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: arm Assignee: freebsd-arm@FreeBSD.org Reporter: iz-rpi03@hs-karlsruhe.de Created attachment 209272 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D209272&action= =3Dedit Serial console output from first occurence and verification. Hello, after updating from base r354795 to base r354850 I get sdhci-bcm0-slot controller timeouts while doing zsf send on a RPi 3 B+. The timeouts do not happen when a r354795 or older kernel is used. I think this shows up because of the changes which happend to bcm2835_sdhci between r354795 and r354850. Ralf --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-arm@freebsd.org Wed Nov 20 22:42:50 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 074A01C41BB for ; Wed, 20 Nov 2019 22:42:50 +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 47JHlD5sTKz4Skl for ; Wed, 20 Nov 2019 22:42:48 +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 xAKMhZeW046719 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Wed, 20 Nov 2019 23:43:36 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cicely.de; s=default; t=1574289816; bh=MplAiBZCQQSowNRrR+jrElDZkJ4xTOLzN8UwEcZL7ww=; h=Date:From:To:Cc:Subject:Reply-To; b=BQPdavptI+8cduzrcoIvbi+j9Z7CfmIM0VW6A0v23pZVDaO2rgQqYfxwVQ7hv2Cnw eZMb06O1WzCRlNRr9kRn9xwGZfY6kgxHJIhnPYTvr6CmsG6zeOHhzw97dV5/V2+hWW +qomZo7UtoEfkuQiWrWtbcNec0qz3GyAlPR2YUQg= 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 xAKMgdC7086468 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 20 Nov 2019 23:42:39 +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 xAKMgdFQ034802; Wed, 20 Nov 2019 23:42:39 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.15.2/8.15.2/Submit) id xAKMgduZ034801; Wed, 20 Nov 2019 23:42:39 +0100 (CET) (envelope-from ticso) Date: Wed, 20 Nov 2019 23:42:39 +0100 From: Bernd Walter To: freebsd-arm@freebsd.org Cc: Bernd Walter Subject: 20h offset with DS3231 RTC Message-ID: <20191120224239.GA34719@cicely7.cicely.de> Reply-To: ticso@cicely.de Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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: 47JHlD5sTKz4Skl X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=cicely.de header.s=default header.b=BQPdavpt; 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.76 / 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.98)[-0.979,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; MV_CASE(0.50)[]; NEURAL_HAM_LONG(-0.98)[-0.980,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; DMARC_NA(0.00)[cicely.de]; REPLYTO_DOM_NEQ_FROM_DOM(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[cicely.de:+]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[3.99.149.195.list.dnswl.org : 127.0.20.0]; 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)[]; IP_SCORE(-0.00)[country: DE(-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: Wed, 20 Nov 2019 22:42:50 -0000 I just added an RTC to a Pi3B with FreeBSD 12.1-RELEASE: ds32310: at addr 0xd0 on iicbus0 ... Setting date via ntp. 20 Nov 22:55:48 ntpdate[760]: step time server 46.165.221.137 offset 71999.728041 sec This was the 3rd reboot. The first boot had no actual time as expected and the RTC wasn't even running. The second already showed the offset. To verify I checked another systemm, wqhich I've added such an RTC before. dmesg said that it booted 9 days ago with 1s offset, but with another reboot: 20 Nov 23:31:44 ntpdate[826]: step time server 80.67.16.8 offset 72000.160415 sec It seems that the error depends on the actual date/time. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-arm@freebsd.org Thu Nov 21 02:12:05 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 04B0A1A9ADE for ; Thu, 21 Nov 2019 02:12:05 +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 47JNNg4jrwz3Chw for ; Thu, 21 Nov 2019 02:12:03 +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 xAL2C3wF001939 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 20 Nov 2019 18:12:04 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id xAL2C3eK001938; Wed, 20 Nov 2019 18:12:03 -0800 (PST) (envelope-from fbsd) Date: Wed, 20 Nov 2019 18:12:03 -0800 From: bob prohaska To: freebsd-arm@freebsd.org Subject: rpi3 panic: data pending interrupt pushed through SDHCI framework Message-ID: <20191121021203.GA1837@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.24 (2015-08-30) X-Rspamd-Queue-Id: 47JNNg4jrwz3Chw 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 [2.35 / 15.00]; ARC_NA(0.00)[]; WWW_DOT_DOMAIN(0.50)[]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; IP_SCORE(0.07)[ip: (0.30), ipnet: 50.1.16.0/20(0.15), 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_SPAM_MEDIUM(0.13)[0.131,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_SPAM_LONG(0.25)[0.248,0]; 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: Thu, 21 Nov 2019 02:12:05 -0000 While trying to compile www/chromium on a Pi3 running r354909 the system reported a panic which is new, at least to me: panic: data pending interrupt pushed through SDHCI framework cpuid = 3 time = 1574299870 KDB: stack backtrace: db_trace_self() at db_trace_self_wrapper+0x28 pc = 0xffff00000072978c lr = 0xffff000000106548 sp = 0xffff00004026b4c0 fp = 0xffff00004026b6d0 db_trace_self_wrapper() at vpanic+0x18c pc = 0xffff000000106548 lr = 0xffff000000400c58 sp = 0xffff00004026b6e0 fp = 0xffff00004026b790 vpanic() at panic+0x44 pc = 0xffff000000400c58 lr = 0xffff000000400a08 sp = 0xffff00004026b7a0 fp = 0xffff00004026b820 panic() at bcm_sdhci_will_handle_transfer+0x64 pc = 0xffff000000400a08 lr = 0xffff00000071a48c sp = 0xffff00004026b830 fp = 0xffff00004026b840 bcm_sdhci_will_handle_transfer() at sdhci_generic_intr+0x69c pc = 0xffff00000071a48c lr = 0xffff00000022f44c sp = 0xffff00004026b850 fp = 0xffff00004026b8b0 sdhci_generic_intr() at ithread_loop+0x1e8 pc = 0xffff00000022f44c lr = 0xffff0000003c44e8 sp = 0xffff00004026b8c0 fp = 0xffff00004026b940 ithread_loop() at fork_exit+0x7c pc = 0xffff0000003c44e8 lr = 0xffff0000003c0fac sp = 0xffff00004026b950 fp = 0xffff00004026b980 fork_exit() at fork_trampoline+0x10 pc = 0xffff0000003c0fac lr = 0xffff000000746994 sp = 0xffff00004026b990 fp = 0x0000000000000000 KDB: enter: panic [ thread pid 12 tid 100051 ] Stopped at 0 db> bt Tracing pid 12 tid 100051 td 0xfffffd0000b9d000 db_trace_self() at db_stack_trace+0xf8 pc = 0xffff00000072978c lr = 0xffff00000010398c sp = 0xffff00004026b090 fp = 0xffff00004026b0c0 db_stack_trace() at db_command+0x228 pc = 0xffff00000010398c lr = 0xffff000000103604 sp = 0xffff00004026b0d0 fp = 0xffff00004026b1b0 db_command() at db_command_loop+0x58 pc = 0xffff000000103604 lr = 0xffff0000001033ac sp = 0xffff00004026b1c0 fp = 0xffff00004026b1e0 db_command_loop() at db_trap+0xf4 pc = 0xffff0000001033ac lr = 0xffff0000001066b0 sp = 0xffff00004026b1f0 fp = 0xffff00004026b410 db_trap() at kdb_trap+0x1d8 pc = 0xffff0000001066b0 lr = 0xffff0000004491f0 sp = 0xffff00004026b420 fp = 0xffff00004026b4d0 kdb_trap() at do_el1h_sync+0xf4 pc = 0xffff0000004491f0 lr = 0xffff000000746c08 sp = 0xffff00004026b4e0 fp = 0xffff00004026b510 do_el1h_sync() at handle_el1h_sync+0x78 pc = 0xffff000000746c08 lr = 0xffff00000072c078 sp = 0xffff00004026b520 fp = 0xffff00004026b630 handle_el1h_sync() at kdb_enter+0x34 pc = 0xffff00000072c078 lr = 0xffff00000044883c sp = 0xffff00004026b640 fp = 0xffff00004026b6d0 kdb_enter() at vpanic+0x1a8 pc = 0xffff00000044883c lr = 0xffff000000400c74 sp = 0xffff00004026b6e0 fp = 0xffff00004026b790 vpanic() at panic+0x44 pc = 0xffff000000400c74 lr = 0xffff000000400a08 sp = 0xffff00004026b7a0 fp = 0xffff00004026b820 panic() at bcm_sdhci_will_handle_transfer+0x64 pc = 0xffff000000400a08 lr = 0xffff00000071a48c sp = 0xffff00004026b830 fp = 0xffff00004026b840 bcm_sdhci_will_handle_transfer() at sdhci_generic_intr+0x69c pc = 0xffff00000071a48c lr = 0xffff00000022f44c sp = 0xffff00004026b850 fp = 0xffff00004026b8b0 sdhci_generic_intr() at ithread_loop+0x1e8 pc = 0xffff00000022f44c lr = 0xffff0000003c44e8 sp = 0xffff00004026b8c0 fp = 0xffff00004026b940 ithread_loop() at fork_exit+0x7c pc = 0xffff0000003c44e8 lr = 0xffff0000003c0fac sp = 0xffff00004026b950 fp = 0xffff00004026b980 fork_exit() at fork_trampoline+0x10 pc = 0xffff0000003c0fac lr = 0xffff000000746994 sp = 0xffff00004026b990 fp = 0x0000000000000000 db> The last top window contains last pid: 45350; load averages: 1.98, 2.87, 4.04 up 0+02:41:58 17:31:08 45 processes: 2 running, 43 sleeping CPU: 13.0% user, 0.0% nice, 7.3% system, 9.0% interrupt, 70.7% idle Mem: 417M Active, 72M Inact, 220M Laundry, 170M Wired, 97M Buf, 20M Free Swap: 7194M Total, 410M Used, 6784M Free, 5% Inuse, 12M In, 18M Out PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND 45134 root 1 47 0 320M 36M CPU0 0 0:19 47.44% c++ 45136 root 1 21 0 308M 28M swread 2 0:12 3.15% c++ 45135 root 1 21 0 304M 27M swread 2 0:11 3.34% c++ 45148 root 1 21 0 308M 26M swread 3 0:12 3.32% c++ 45350 bob 1 52 0 12M 2392K nanslp 3 0:00 0.00% gstat 1049 bob 1 20 0 19M 2020K select 1 0:03 0.03% sshd 1554 bob 1 20 0 13M 1912K CPU1 1 0:25 0.23% top 1058 bob 1 20 0 19M 1900K select 2 0:00 0.00% sshd 1059 bob 1 20 0 13M 1816K ttyin 0 0:01 0.00% tcsh 958 root 1 20 0 16M 1804K select 1 0:01 0.02% sendmail 1055 root 1 21 0 19M 1796K select 2 0:00 0.00% sshd 1046 root 1 24 0 19M 1788K select 2 0:00 0.00% sshd 1028 bob 1 20 0 19M 1744K select 2 0:00 0.00% sshd 1066 bob 1 20 0 19M 1744K select 1 0:00 0.00% sshd The last of the I/O activity log contains procs memory page disks faults cpu r b w avm fre flt re pi po fr sr mm0 da0 in sy cs us sy id 1 0 12 1410224 5316 902 2 1 0 1176 638 0 0 14925 2704 6210 21 7 72 dT: 1.050s w: 1.000s L(q) ops/s r/s kBps ms/r w/s kBps ms/w d/s kBps ms/d %busy Name 0 91 3 65 328.1 89 6459 33.6 0 0 0.0 88.3 mmcsd0 0 91 3 65 328.2 89 6459 33.7 0 0 0.0 88.3 mmcsd0s2 0 2 2 61 484.6 0 0 0.0 0 0 0.0 92.3 mmcsd0s2a 0 90 1 4 15.5 89 6459 33.7 0 0 0.0 88.2 mmcsd0s2b 0 2 2 61 484.6 0 0 0.0 0 0 0.0 92.3 ufs/rootfs 7 126 0 0 0.0 126 6021 3.8 0 0 0.0 30.1 da0 5 83 0 0 0.0 83 6021 4.0 0 0 0.0 30.4 da0p6 Wed Nov 20 17:30:44 PST 2019 Device 1K-blocks Used Avail Capacity /dev/mmcsd0s2b 4404252 138100 4266152 3% /dev/da0p6 5242880 139496 5103384 3% Total 9647132 277596 9369536 3% Nov 20 17:27:25 www sshd[44294]: error: PAM: Authentication error for illegal user support from 103.133.104.114 Nov 20 17:27:26 www sshd[44294]: error: Received disconnect from 103.133.104.114 port 52227:14: No more user authentication methods available. [preauth] procs memory page suggesting the panic happened while vmstat was writing to the log. For the moment I'll update /usr/src and rebuild. Please indicate if more useful observations can be gathered. Thanks for reading, bob prohaska From owner-freebsd-arm@freebsd.org Thu Nov 21 02:32: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 C0BCE1AA203 for ; Thu, 21 Nov 2019 02:32:00 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (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 "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47JNqh4jNhz3DXc for ; Thu, 21 Nov 2019 02:32:00 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from mail-qt1-f180.google.com (mail-qt1-f180.google.com [209.85.160.180]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) (Authenticated sender: kevans) by smtp.freebsd.org (Postfix) with ESMTPSA id 764C22EC8 for ; Thu, 21 Nov 2019 02:32:00 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mail-qt1-f180.google.com with SMTP id g50so1987682qtb.4 for ; Wed, 20 Nov 2019 18:32:00 -0800 (PST) X-Gm-Message-State: APjAAAW0lpwXBoWFrDNGpbhzydka14yzOuA8iH+WXlVKfx5w8AwCkrf1 PQdmrKnr/yCObU9KaGsol8DJcVhPlU06i0xqFzk= X-Google-Smtp-Source: APXvYqz8eI0oNO5Q+Zwysd2s+CSqVuxePUkqNpQpKetLpbQKuBI53lQLIiZzqP43cesRCTp9N/PSejCU0ECcc8I5x8o= X-Received: by 2002:ac8:66d7:: with SMTP id m23mr828662qtp.53.1574303519802; Wed, 20 Nov 2019 18:31:59 -0800 (PST) MIME-Version: 1.0 References: <20191121021203.GA1837@www.zefox.net> In-Reply-To: <20191121021203.GA1837@www.zefox.net> From: Kyle Evans Date: Wed, 20 Nov 2019 20:31:48 -0600 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: rpi3 panic: data pending interrupt pushed through SDHCI framework To: bob prohaska Cc: "freebsd-arm@freebsd.org" Content-Type: text/plain; charset="UTF-8" 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: Thu, 21 Nov 2019 02:32:00 -0000 On Wed, Nov 20, 2019 at 8:12 PM bob prohaska wrote: > > While trying to compile www/chromium on a Pi3 running r354909 > the system reported a panic which is new, at least to me: > > panic: data pending interrupt pushed through SDHCI framework > cpuid = 3 > time = 1574299870 > KDB: stack backtrace: > db_trace_self() at db_trace_self_wrapper+0x28 > pc = 0xffff00000072978c lr = 0xffff000000106548 > sp = 0xffff00004026b4c0 fp = 0xffff00004026b6d0 > > db_trace_self_wrapper() at vpanic+0x18c > pc = 0xffff000000106548 lr = 0xffff000000400c58 > sp = 0xffff00004026b6e0 fp = 0xffff00004026b790 > > vpanic() at panic+0x44 > pc = 0xffff000000400c58 lr = 0xffff000000400a08 > sp = 0xffff00004026b7a0 fp = 0xffff00004026b820 > > panic() at bcm_sdhci_will_handle_transfer+0x64 > pc = 0xffff000000400a08 lr = 0xffff00000071a48c > sp = 0xffff00004026b830 fp = 0xffff00004026b840 > > bcm_sdhci_will_handle_transfer() at sdhci_generic_intr+0x69c > pc = 0xffff00000071a48c lr = 0xffff00000022f44c > sp = 0xffff00004026b850 fp = 0xffff00004026b8b0 > > sdhci_generic_intr() at ithread_loop+0x1e8 > pc = 0xffff00000022f44c lr = 0xffff0000003c44e8 > sp = 0xffff00004026b8c0 fp = 0xffff00004026b940 > > ithread_loop() at fork_exit+0x7c > pc = 0xffff0000003c44e8 lr = 0xffff0000003c0fac > sp = 0xffff00004026b950 fp = 0xffff00004026b980 > > fork_exit() at fork_trampoline+0x10 > pc = 0xffff0000003c0fac lr = 0xffff000000746994 > sp = 0xffff00004026b990 fp = 0x0000000000000000 > > KDB: enter: panic > [ thread pid 12 tid 100051 ] > Stopped at 0 > db> bt > Tracing pid 12 tid 100051 td 0xfffffd0000b9d000 > db_trace_self() at db_stack_trace+0xf8 > pc = 0xffff00000072978c lr = 0xffff00000010398c > sp = 0xffff00004026b090 fp = 0xffff00004026b0c0 > > db_stack_trace() at db_command+0x228 > pc = 0xffff00000010398c lr = 0xffff000000103604 > sp = 0xffff00004026b0d0 fp = 0xffff00004026b1b0 > > db_command() at db_command_loop+0x58 > pc = 0xffff000000103604 lr = 0xffff0000001033ac > sp = 0xffff00004026b1c0 fp = 0xffff00004026b1e0 > > db_command_loop() at db_trap+0xf4 > pc = 0xffff0000001033ac lr = 0xffff0000001066b0 > sp = 0xffff00004026b1f0 fp = 0xffff00004026b410 > > db_trap() at kdb_trap+0x1d8 > pc = 0xffff0000001066b0 lr = 0xffff0000004491f0 > sp = 0xffff00004026b420 fp = 0xffff00004026b4d0 > > kdb_trap() at do_el1h_sync+0xf4 > pc = 0xffff0000004491f0 lr = 0xffff000000746c08 > sp = 0xffff00004026b4e0 fp = 0xffff00004026b510 > > do_el1h_sync() at handle_el1h_sync+0x78 > pc = 0xffff000000746c08 lr = 0xffff00000072c078 > sp = 0xffff00004026b520 fp = 0xffff00004026b630 > > handle_el1h_sync() at kdb_enter+0x34 > pc = 0xffff00000072c078 lr = 0xffff00000044883c > sp = 0xffff00004026b640 fp = 0xffff00004026b6d0 > > kdb_enter() at vpanic+0x1a8 > pc = 0xffff00000044883c lr = 0xffff000000400c74 > sp = 0xffff00004026b6e0 fp = 0xffff00004026b790 > > vpanic() at panic+0x44 > pc = 0xffff000000400c74 lr = 0xffff000000400a08 > sp = 0xffff00004026b7a0 fp = 0xffff00004026b820 > > panic() at bcm_sdhci_will_handle_transfer+0x64 > pc = 0xffff000000400a08 lr = 0xffff00000071a48c > sp = 0xffff00004026b830 fp = 0xffff00004026b840 > > bcm_sdhci_will_handle_transfer() at sdhci_generic_intr+0x69c > pc = 0xffff00000071a48c lr = 0xffff00000022f44c > sp = 0xffff00004026b850 fp = 0xffff00004026b8b0 > > sdhci_generic_intr() at ithread_loop+0x1e8 > pc = 0xffff00000022f44c lr = 0xffff0000003c44e8 > sp = 0xffff00004026b8c0 fp = 0xffff00004026b940 > > ithread_loop() at fork_exit+0x7c > pc = 0xffff0000003c44e8 lr = 0xffff0000003c0fac > sp = 0xffff00004026b950 fp = 0xffff00004026b980 > > fork_exit() at fork_trampoline+0x10 > pc = 0xffff0000003c0fac lr = 0xffff000000746994 > sp = 0xffff00004026b990 fp = 0x0000000000000000 > Hi, This one is also mine, added in r354868: https://svnweb.freebsd.org/base/?revision=354868&view=revision --> this specific check is that we don't have any DMA segments at play during SDHCI_PLATFORM_WILL_HANDLE_TRANSFER, because this is indicative of something less-than-stellar -- it will be invoked only if the generic interrupt handler is handling DATA_AVAIL | SPACE_AVAIL. The way this is supposed to work, the driver starts DMA and disables DATA_AVAIL | SPACE_AVAIL interrupts. DMA interrupts then drive the transfer until we're out of DMA segments, at which point we check if we can go ahead and start up another transfer or if we need to just re-enable interrupts and wait for the controller to act. We should never be coming back in from the SDHCI interrupt path with loaded segments, which is what this one was trying to address: https://reviews.freebsd.org/D22430 That being said, I can see one path where we don't clean up after ourselves -- if we fail to load DMA segments mid-transfer, we set a command error and re-enable interrupts. it's not clear to me if SDHCI_PLATFORM_FINISH_TRANSFER will be invoked before that becomes a problem, but I suspect it should -- you would see some errors that make it sound like there's memory issues. I'll clean that up anyways. Thanks, Kyle Evans From owner-freebsd-arm@freebsd.org Thu Nov 21 03:06:40 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 384451AB0E3 for ; Thu, 21 Nov 2019 03:06:40 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (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 "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47JPbh0dz6z3GgR for ; Thu, 21 Nov 2019 03:06:40 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from mail-qk1-f173.google.com (mail-qk1-f173.google.com [209.85.222.173]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) (Authenticated sender: kevans) by smtp.freebsd.org (Postfix) with ESMTPSA id DABBA3360 for ; Thu, 21 Nov 2019 03:06:39 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mail-qk1-f173.google.com with SMTP id i19so1860886qki.2 for ; Wed, 20 Nov 2019 19:06:39 -0800 (PST) X-Gm-Message-State: APjAAAV56te9oYMuKtaJfaCiRmEvqe2Iz5pvcaJSdV1BSjYlgPIer5QD /B80++6UXzADSuuxjMO//A+x227t/iYJUkU4XSE= X-Received: by 2002:a05:620a:139a:: with SMTP id k26mt5240006qki.34.1574305599064; Wed, 20 Nov 2019 19:06:39 -0800 (PST) MIME-Version: 1.0 References: <20191121021203.GA1837@www.zefox.net> In-Reply-To: From: Kyle Evans Date: Wed, 20 Nov 2019 21:06:27 -0600 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: rpi3 panic: data pending interrupt pushed through SDHCI framework Cc: bob prohaska , "freebsd-arm@freebsd.org" Content-Type: text/plain; charset="UTF-8" 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: Thu, 21 Nov 2019 03:06:40 -0000 On Wed, Nov 20, 2019 at 8:31 PM Kyle Evans wrote: > > On Wed, Nov 20, 2019 at 8:12 PM bob prohaska wrote: > > > > While trying to compile www/chromium on a Pi3 running r354909 > > the system reported a panic which is new, at least to me: > > > > panic: data pending interrupt pushed through SDHCI framework > > cpuid = 3 > > time = 1574299870 > > KDB: stack backtrace: > > db_trace_self() at db_trace_self_wrapper+0x28 > > pc = 0xffff00000072978c lr = 0xffff000000106548 > > sp = 0xffff00004026b4c0 fp = 0xffff00004026b6d0 > > > > db_trace_self_wrapper() at vpanic+0x18c > > pc = 0xffff000000106548 lr = 0xffff000000400c58 > > sp = 0xffff00004026b6e0 fp = 0xffff00004026b790 > > > > vpanic() at panic+0x44 > > pc = 0xffff000000400c58 lr = 0xffff000000400a08 > > sp = 0xffff00004026b7a0 fp = 0xffff00004026b820 > > > > panic() at bcm_sdhci_will_handle_transfer+0x64 > > pc = 0xffff000000400a08 lr = 0xffff00000071a48c > > sp = 0xffff00004026b830 fp = 0xffff00004026b840 > > > > bcm_sdhci_will_handle_transfer() at sdhci_generic_intr+0x69c > > pc = 0xffff00000071a48c lr = 0xffff00000022f44c > > sp = 0xffff00004026b850 fp = 0xffff00004026b8b0 > > > > sdhci_generic_intr() at ithread_loop+0x1e8 > > pc = 0xffff00000022f44c lr = 0xffff0000003c44e8 > > sp = 0xffff00004026b8c0 fp = 0xffff00004026b940 > > > > ithread_loop() at fork_exit+0x7c > > pc = 0xffff0000003c44e8 lr = 0xffff0000003c0fac > > sp = 0xffff00004026b950 fp = 0xffff00004026b980 > > > > fork_exit() at fork_trampoline+0x10 > > pc = 0xffff0000003c0fac lr = 0xffff000000746994 > > sp = 0xffff00004026b990 fp = 0x0000000000000000 > > > > KDB: enter: panic > > [ thread pid 12 tid 100051 ] > > Stopped at 0 > > db> bt > > Tracing pid 12 tid 100051 td 0xfffffd0000b9d000 > > db_trace_self() at db_stack_trace+0xf8 > > pc = 0xffff00000072978c lr = 0xffff00000010398c > > sp = 0xffff00004026b090 fp = 0xffff00004026b0c0 > > > > db_stack_trace() at db_command+0x228 > > pc = 0xffff00000010398c lr = 0xffff000000103604 > > sp = 0xffff00004026b0d0 fp = 0xffff00004026b1b0 > > > > db_command() at db_command_loop+0x58 > > pc = 0xffff000000103604 lr = 0xffff0000001033ac > > sp = 0xffff00004026b1c0 fp = 0xffff00004026b1e0 > > > > db_command_loop() at db_trap+0xf4 > > pc = 0xffff0000001033ac lr = 0xffff0000001066b0 > > sp = 0xffff00004026b1f0 fp = 0xffff00004026b410 > > > > db_trap() at kdb_trap+0x1d8 > > pc = 0xffff0000001066b0 lr = 0xffff0000004491f0 > > sp = 0xffff00004026b420 fp = 0xffff00004026b4d0 > > > > kdb_trap() at do_el1h_sync+0xf4 > > pc = 0xffff0000004491f0 lr = 0xffff000000746c08 > > sp = 0xffff00004026b4e0 fp = 0xffff00004026b510 > > > > do_el1h_sync() at handle_el1h_sync+0x78 > > pc = 0xffff000000746c08 lr = 0xffff00000072c078 > > sp = 0xffff00004026b520 fp = 0xffff00004026b630 > > > > handle_el1h_sync() at kdb_enter+0x34 > > pc = 0xffff00000072c078 lr = 0xffff00000044883c > > sp = 0xffff00004026b640 fp = 0xffff00004026b6d0 > > > > kdb_enter() at vpanic+0x1a8 > > pc = 0xffff00000044883c lr = 0xffff000000400c74 > > sp = 0xffff00004026b6e0 fp = 0xffff00004026b790 > > > > vpanic() at panic+0x44 > > pc = 0xffff000000400c74 lr = 0xffff000000400a08 > > sp = 0xffff00004026b7a0 fp = 0xffff00004026b820 > > > > panic() at bcm_sdhci_will_handle_transfer+0x64 > > pc = 0xffff000000400a08 lr = 0xffff00000071a48c > > sp = 0xffff00004026b830 fp = 0xffff00004026b840 > > > > bcm_sdhci_will_handle_transfer() at sdhci_generic_intr+0x69c > > pc = 0xffff00000071a48c lr = 0xffff00000022f44c > > sp = 0xffff00004026b850 fp = 0xffff00004026b8b0 > > > > sdhci_generic_intr() at ithread_loop+0x1e8 > > pc = 0xffff00000022f44c lr = 0xffff0000003c44e8 > > sp = 0xffff00004026b8c0 fp = 0xffff00004026b940 > > > > ithread_loop() at fork_exit+0x7c > > pc = 0xffff0000003c44e8 lr = 0xffff0000003c0fac > > sp = 0xffff00004026b950 fp = 0xffff00004026b980 > > > > fork_exit() at fork_trampoline+0x10 > > pc = 0xffff0000003c0fac lr = 0xffff000000746994 > > sp = 0xffff00004026b990 fp = 0x0000000000000000 > > > > Hi, > > This one is also mine, added in r354868: > https://svnweb.freebsd.org/base/?revision=354868&view=revision --> > this specific check is that we don't have any DMA segments at play > during SDHCI_PLATFORM_WILL_HANDLE_TRANSFER, because this is indicative > of something less-than-stellar -- it will be invoked only if the > generic interrupt handler is handling DATA_AVAIL | SPACE_AVAIL. The > way this is supposed to work, the driver starts DMA and disables > DATA_AVAIL | SPACE_AVAIL interrupts. DMA interrupts then drive the > transfer until we're out of DMA segments, at which point we check if > we can go ahead and start up another transfer or if we need to just > re-enable interrupts and wait for the controller to act. We should > never be coming back in from the SDHCI interrupt path with loaded > segments, which is what this one was trying to address: > https://reviews.freebsd.org/D22430 > > That being said, I can see one path where we don't clean up after > ourselves -- if we fail to load DMA segments mid-transfer, we set a > command error and re-enable interrupts. it's not clear to me if > SDHCI_PLATFORM_FINISH_TRANSFER will be invoked before that becomes a > problem, but I suspect it should -- you would see some errors that > make it sound like there's memory issues. I'll clean that up anyways. > I rolled back the suspicious change in question from the range in your previous post that also fit the bill for a bugzilla PR that came in last night -- r354933 should have the latest hotness. From owner-freebsd-arm@freebsd.org Thu Nov 21 03:32:23 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 799E31AB890 for ; Thu, 21 Nov 2019 03:32:23 +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 47JQ9M1vmTz3HnS; Thu, 21 Nov 2019 03:32:22 +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 xAL3WOjA002144 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 20 Nov 2019 19:32:25 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id xAL3WNWT002143; Wed, 20 Nov 2019 19:32:23 -0800 (PST) (envelope-from fbsd) Date: Wed, 20 Nov 2019 19:32:23 -0800 From: bob prohaska To: Kyle Evans Cc: "freebsd-arm@freebsd.org" Subject: Re: rpi3 panic: data pending interrupt pushed through SDHCI framework Message-ID: <20191121033223.GC1837@www.zefox.net> References: <20191121021203.GA1837@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: 47JQ9M1vmTz3HnS X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-5.98 / 15.00]; NEURAL_HAM_MEDIUM(-0.99)[-0.991,0]; REPLY(-4.00)[]; NEURAL_HAM_LONG(-0.99)[-0.993,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: Thu, 21 Nov 2019 03:32:23 -0000 On Wed, Nov 20, 2019 at 09:06:27PM -0600, Kyle Evans wrote: > > I rolled back the suspicious change in question from the range in your > previous post that also fit the bill for a bugzilla PR that came in > last night -- r354933 should have the latest hotness. As I write this r354933 is building. Thanks very much for your attention and reply! bob prohaska From owner-freebsd-arm@freebsd.org Thu Nov 21 05:56: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 AE2DA1AF691 for ; Thu, 21 Nov 2019 05:56:30 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound3d.ore.mailhop.org (outbound3d.ore.mailhop.org [54.186.57.195]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 47JTMf1vzLz3Pjw for ; Thu, 21 Nov 2019 05:56:30 +0000 (UTC) (envelope-from ian@freebsd.org) ARC-Seal: i=1; a=rsa-sha256; t=1574315789; cv=none; d=outbound.mailhop.org; s=arc-outbound20181012; b=o1RQtCimxsJY5kZjgP7BOr4V0g9LqsRQKPN8Nri/pxx/pojWdhIDmwtUA/0+2226O1c4qihlcbuwZ AYA2blYoREwmErKSbLcNUxM78Pru60joH/pJcbCNGW+q+wq41j4XOy7hJ9HsuEir2A9W8fxcszxZXN ssZUrjtaykGdlb3s1PjcHBC8liSq9nnkH/tX7nnYxs214EE6/H76olNX7XpoQeXsLG2DdzlLewj2aU JxmbAx6dbYkvmna98FL6zTnh16vvOfVcZE7nTP99W//8AMcr7ejGaqhmCtKSTKZMi8d55lRt1PEoNF 4HPOGHkfYHl9IZngOp73bn+CesaTVig== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=arc-outbound20181012; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:cc:to:from:subject:message-id:dkim-signature:from; bh=RMIVVroCR0UUFEoYIKxskL1Ydr+FqrV/wy93LftvJ48=; b=UMNWqqRKmC/LuuyOl0iyWqGEjAvwrv5q2WRVbzPGtcAHUQtxp/62d+zosf5IA6vy9MpK7tzXeneXq SFKoG5L4DUaEaaxaLP0L2ryJ3xLTE5X2YGhT2sbIpusMeA94+d2HfaNmyMkGLZ+mTcoPpS3l9lNild qnbgG+3U4d6xY/EZQt+arfwxhdtv7tMbvMfkWlyT/poZlA6dCCy9E2ebBlzPrsvx0FA10zeNekvPQK 1rkPVvAeypKm3iGOsdisuHhNp60OIebRuGICS/kocqfBWh0cL2zBaWFYmtjl+qC4WuZCwDQNaIWtMT Qz0lRl4DW3TIqnXbjDbuTIf2z7Nzw+A== ARC-Authentication-Results: i=1; outbound3.ore.mailhop.org; spf=softfail smtp.mailfrom=freebsd.org smtp.remote-ip=67.177.211.60; dmarc=none header.from=freebsd.org; arc=none header.oldest-pass=0; DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=dkim-high; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:cc:to:from:subject:message-id:from; bh=RMIVVroCR0UUFEoYIKxskL1Ydr+FqrV/wy93LftvJ48=; b=Gr2ljQ/cn//G0K0tTKCrPUZa9G5YR++Gjokpnx7Rg/QTxvws9Wrpznqkv4edvkSzWApa0MllryKdk rAyhxqa+7tJP/2i8/l2XziAc3RX5yZq3DaUiKejaluXzzLnD99T+fveGMLGYQRLmbdbGzv+VN2Re5D tRTeH2qo0uWBDnKugTdaNFrzviv0i8oU4Za/5bZNHZdl3lGpCUnHUPg+CHGEfzkRSEtoUAYZC+P2v8 s6SVrHZ2+aVUTTB5eLXWaPx6EeMUhpJBsPyBslaVSBn2qDED1DP0pHC5zbiAFoGIX7uEMSfHLDicmp xODVjuMO2c4jqnjgU3FWjW/vibtfjCg== X-MHO-RoutePath: aGlwcGll X-MHO-User: a70e18d1-0c23-11ea-b80c-052b4a66b6b2 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound3.ore.mailhop.org (Halon) with ESMTPSA id a70e18d1-0c23-11ea-b80c-052b4a66b6b2; Thu, 21 Nov 2019 05:56:27 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id xAL5uPoc052808; Wed, 20 Nov 2019 22:56:25 -0700 (MST) (envelope-from ian@freebsd.org) Message-ID: Subject: Re: 20h offset with DS3231 RTC From: Ian Lepore To: ticso@cicely.de, freebsd-arm@freebsd.org Cc: Bernd Walter Date: Wed, 20 Nov 2019 22:56:24 -0700 In-Reply-To: <20191120224239.GA34719@cicely7.cicely.de> References: <20191120224239.GA34719@cicely7.cicely.de> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.5 FreeBSD GNOME Team Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 47JTMf1vzLz3Pjw X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-1.90 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-0.93)[-0.929,0]; NEURAL_HAM_LONG(-0.97)[-0.974,0]; ASN(0.00)[asn:16509, ipnet:54.186.0.0/15, country:US] 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: Thu, 21 Nov 2019 05:56:30 -0000 On Wed, 2019-11-20 at 23:42 +0100, Bernd Walter wrote: > I just added an RTC to a Pi3B with FreeBSD 12.1-RELEASE: > ds32310: at addr 0xd0 on iicbus0 > ... > Setting date via ntp. > 20 Nov 22:55:48 ntpdate[760]: step time server 46.165.221.137 offset > 71999.728041 sec > > This was the 3rd reboot. > The first boot had no actual time as expected and the RTC wasn't even > running. > The second already showed the offset. > > To verify I checked another systemm, wqhich I've added such an RTC > before. > dmesg said that it booted 9 days ago with 1s offset, but with another > reboot: > 20 Nov 23:31:44 ntpdate[826]: step time server 80.67.16.8 offset > 72000.160415 sec > > It seems that the error depends on the actual date/time. > I think this is because of a bug/lack-of-capability in the rpi i2c driver and/or hardware, and it affects all i2c devices that use some common driver routines to read and write slave device "registers". I'll look into fixing it, hopefully within a day. -- Ian From owner-freebsd-arm@freebsd.org Thu Nov 21 19:15:14 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 1AE401C860A for ; Thu, 21 Nov 2019 19:15:14 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound3d.ore.mailhop.org (outbound3d.ore.mailhop.org [54.186.57.195]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 47Jq5F4tWHz3K7J for ; Thu, 21 Nov 2019 19:15:13 +0000 (UTC) (envelope-from ian@freebsd.org) ARC-Seal: i=1; a=rsa-sha256; t=1574363711; cv=none; d=outbound.mailhop.org; s=arc-outbound20181012; b=B1QWJwk4s5X0NKK01Om1pecFQMjZHmgYZzrf8tKmc5Blerwj5q2vCaSC2aE01eU/EVft5NVkGLgrK tiKx609dqS7a0Ii22s+6kxZtGHii+sI8NKDESnzaPogEI0U7rSPVZKUAJUBY6i/EI0u2YkLljdr7kv Cl2EJA9NJvEhplTV8TZRSwsAt8NaM7UdRen+dyE+pRbXE00hxVulaOLo9DDoLFcyoMPTShHY7Y2xI1 Qp9G+JdOEKid27vGi+LDZdP8UEkjrCi5cr4qyvup6UpL5N1No6lJtkcT2UQKP8dTwxG/+cM9zIMRWW xjYlCSb6Mkp3wMQUAqQ/dDHKQjuCAtw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=arc-outbound20181012; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:cc:to:from:subject:message-id:dkim-signature:from; bh=RvYiKo46F9tArBrYQIcDBuziJg1rqhXbHbIDaWoPGaM=; b=QoYu9pnCGl4UzxVVrTzYx+r1ELzP/ERRCmFrCQF/eNMaIqlheL0nAdubw759eTyWsMNs5Vdhjc6Py hRJzDA02rCkkrmiXDvSBjlbsj9UE4UBQm4FTzqeV6D2l2GG9BvfIv2ifPFYsIabhi8f+hTdO+07Giw RndYUHc1s/2jdW8rP0AJrWago2/W0r33qPd2MGNt7WuF/Yt+M5tHfXCmb6cC+PtveCS6iwS7INob6l pQm3Fz2FxNKQj5KWOnVfvE1nPkzXVHxjlEzEpZRUoprZluztHY1N7iV/ti34mXh4GLASIxM8ZchCbA kB+lC7KFhqVziY/KKqRH8LC04nEozWg== ARC-Authentication-Results: i=1; outbound3.ore.mailhop.org; spf=softfail smtp.mailfrom=freebsd.org smtp.remote-ip=67.177.211.60; dmarc=none header.from=freebsd.org; arc=none header.oldest-pass=0; DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=dkim-high; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:cc:to:from:subject:message-id:from; bh=RvYiKo46F9tArBrYQIcDBuziJg1rqhXbHbIDaWoPGaM=; b=wFY5eDprPQF1emWJ/iBAjc4wPGQhLhyrMYWFanGz0wenj8U4HVShdBFCv9trsSbCrOvDCOOkMXhi5 EzN0Ol6Nt6OOHmJFucBeSUdCBGr9ogKERvdLKmtCok3a0/8Ogz5oPXcDozWS7C389KYnRq30DXcb2R RLe5WEtUHqIqUHtWW2g45iRz44M9cN/egS5AVgDfqK7EtYCZFXeQKvIaGO789rxIN01y2/4lQk3cj6 /xaXa5Qn4x+nNosg5dcmP4PMSL3Y3U0XKEBpUH39CFjVSnmOFer630Jgs8TZs/nH40sHyySnIk/E59 zSgteuymkQ5ddizrR8fcjjh4LFmSOWw== X-MHO-RoutePath: aGlwcGll X-MHO-User: 3aca7654-0c93-11ea-b80c-052b4a66b6b2 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound3.ore.mailhop.org (Halon) with ESMTPSA id 3aca7654-0c93-11ea-b80c-052b4a66b6b2; Thu, 21 Nov 2019 19:15:10 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id xALJF691055198; Thu, 21 Nov 2019 12:15:07 -0700 (MST) (envelope-from ian@freebsd.org) Message-ID: Subject: Re: 20h offset with DS3231 RTC From: Ian Lepore To: ticso@cicely.de, freebsd-arm@freebsd.org Cc: Bernd Walter Date: Thu, 21 Nov 2019 12:15:06 -0700 In-Reply-To: <20191120224239.GA34719@cicely7.cicely.de> References: <20191120224239.GA34719@cicely7.cicely.de> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.5 FreeBSD GNOME Team Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 47Jq5F4tWHz3K7J X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-1.93 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-0.96)[-0.963,0]; NEURAL_HAM_LONG(-0.97)[-0.970,0]; ASN(0.00)[asn:16509, ipnet:54.186.0.0/15, country:US] 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: Thu, 21 Nov 2019 19:15:14 -0000 On Wed, 2019-11-20 at 23:42 +0100, Bernd Walter wrote: > I just added an RTC to a Pi3B with FreeBSD 12.1-RELEASE: > ds32310: at addr 0xd0 on iicbus0 > ... > Setting date via ntp. > 20 Nov 22:55:48 ntpdate[760]: step time server 46.165.221.137 offset 71999.728041 sec > > This was the 3rd reboot. > The first boot had no actual time as expected and the RTC wasn't even running. > The second already showed the offset. > > To verify I checked another systemm, wqhich I've added such an RTC before. > dmesg said that it booted 9 days ago with 1s offset, but with another reboot: > 20 Nov 23:31:44 ntpdate[826]: step time server 80.67.16.8 offset 72000.160415 sec > > It seems that the error depends on the actual date/time. > This should be fixed in r354973. -- Ian From owner-freebsd-arm@freebsd.org Thu Nov 21 19:26:51 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 12ADE1C89B5 for ; Thu, 21 Nov 2019 19:26:51 +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 47JqLf6FmXz3KXB; Thu, 21 Nov 2019 19:26:50 +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 xALJRdR3016237 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 21 Nov 2019 20:27:40 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cicely.de; s=default; t=1574364460; bh=Yeb6J8n7wv0TYrZHXoj0MxSN1kJ6szn2mlqcIB1PUJI=; h=Date:From:To:Cc:Subject:Reply-To:References:In-Reply-To; b=sDuXmM2f3tvYaPFKHeACaPeh9U3kxOKcOcZuveXS33kAOxwGTpNR3I/Sas16EkWQs jWsOgV2vfryNdcE5Cv7mzSwMujoswoyGvdwpPjLMIJKMei/ZXNRWWKTNhbAxMtifhO qwAlVB3i5Mlv2GU/DdQUNMjNZx3pHM7yKskE9YfE= 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 xALJQiQV033873 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 21 Nov 2019 20:26:44 +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 xALJQhhc042681; Thu, 21 Nov 2019 20:26:43 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.15.2/8.15.2/Submit) id xALJQhtY042680; Thu, 21 Nov 2019 20:26:43 +0100 (CET) (envelope-from ticso) Date: Thu, 21 Nov 2019 20:26:43 +0100 From: Bernd Walter To: Ian Lepore Cc: ticso@cicely.de, freebsd-arm@freebsd.org, Bernd Walter Subject: Re: 20h offset with DS3231 RTC Message-ID: <20191121192643.GD41336@cicely7.cicely.de> Reply-To: ticso@cicely.de References: <20191120224239.GA34719@cicely7.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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: 47JqLf6FmXz3KXB X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-5.99 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-0.997,0]; NEURAL_HAM_LONG(-1.00)[-0.995,0]; 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: Thu, 21 Nov 2019 19:26:51 -0000 On Thu, Nov 21, 2019 at 12:15:06PM -0700, Ian Lepore wrote: > On Wed, 2019-11-20 at 23:42 +0100, Bernd Walter wrote: > > I just added an RTC to a Pi3B with FreeBSD 12.1-RELEASE: > > ds32310: at addr 0xd0 on iicbus0 > > ... > > Setting date via ntp. > > 20 Nov 22:55:48 ntpdate[760]: step time server 46.165.221.137 offset 71999.728041 sec > > > > This was the 3rd reboot. > > The first boot had no actual time as expected and the RTC wasn't even running. > > The second already showed the offset. > > > > To verify I checked another systemm, wqhich I've added such an RTC before. > > dmesg said that it booted 9 days ago with 1s offset, but with another reboot: > > 20 Nov 23:31:44 ntpdate[826]: step time server 80.67.16.8 offset 72000.160415 sec > > > > It seems that the error depends on the actual date/time. > > > > This should be fixed in r354973. Wow - amazing. I'll give it a try. Thank you very much. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-arm@freebsd.org Fri Nov 22 00:15: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 08F5B1CEFE8 for ; Fri, 22 Nov 2019 00:15:28 +0000 (UTC) (envelope-from crowston@protonmail.com) Received: from mail-40132.protonmail.ch (mail-40132.protonmail.ch [185.70.40.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "protonmail.com", Issuer "SwissSign Server Gold CA 2014 - G22" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47Jxlf5M0Kz47fd; Fri, 22 Nov 2019 00:15:25 +0000 (UTC) (envelope-from crowston@protonmail.com) Date: Fri, 22 Nov 2019 00:15:14 +0000 To: "freebsd-arm@freebsd.org" From: Robert Crowston Cc: Kyle Evans , Conrad Meyer , Mark Murray Reply-To: Robert Crowston Subject: Re: Initial support for bcm2838 RNG Message-ID: In-Reply-To: References: <2F178D6A-300B-4683-84D6-CDB6924877E5@FreeBSD.org> Feedback-ID: 2OVbcR1yHYpdkD8cgQllkFwcuMVZg_LiVMMPvptooFDfHD_03MuQO4ZaF626jWHZYFEhNR2cmIbZ53j4QGWMBQ==:Ext:ProtonMail MIME-Version: 1.0 X-Spam-Status: No, score=-1.2 required=7.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,HTML_MESSAGE autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on mail.protonmail.ch X-Rspamd-Queue-Id: 47Jxlf5M0Kz47fd X-Spamd-Bar: -- X-Spamd-Result: default: False [-3.00 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; HAS_REPLYTO(0.00)[crowston@protonmail.com]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:185.70.40.0/24]; FREEMAIL_FROM(0.00)[protonmail.com]; DKIM_TRACE(0.00)[protonmail.com:+]; MIME_BASE64_TEXT(0.10)[]; DMARC_POLICY_ALLOW(-0.50)[protonmail.com,quarantine]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; IP_SCORE(0.00)[ip: (-9.74), ipnet: 185.70.40.0/24(-4.89), asn: 62371(-3.89), country: CH(0.02)]; RCVD_IN_DNSWL_LOW(-0.10)[132.40.70.185.list.dnswl.org : 127.0.5.1]; ASN(0.00)[asn:62371, ipnet:185.70.40.0/24, country:CH]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[protonmail.com]; R_DKIM_ALLOW(-0.20)[protonmail.com:s=default]; REPLYTO_EQ_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; FREEMAIL_REPLYTO(0.00)[protonmail.com]; HAS_PHPMAILER_SIG(0.00)[]; IP_SCORE_FREEMAIL(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[] Content-Type: text/plain; charset=UTF-8 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: Fri, 22 Nov 2019 00:15:28 -0000 UmV2aWV3IGNyZWF0ZWQgaGVyZTogaHR0cHM6Ly9yZXZpZXdzLmZyZWVic2Qub3JnL0QyMjQ5MwoK 4oCQ4oCQ4oCQ4oCQ4oCQ4oCQ4oCQIE9yaWdpbmFsIE1lc3NhZ2Ug4oCQ4oCQ4oCQ4oCQ4oCQ4oCQ 4oCQCk9uIFN1bmRheSwgMTcgTm92ZW1iZXIgMjAxOSAxODowMiwgQ29ucmFkIE1leWVyIDxjZW1A ZnJlZWJzZC5vcmc+IHdyb3RlOgoKPiBJIGRvbuKAmXQgdGhpbmsgY3Nwcm5n4oCZcyBibG9ja2Vy IGxldmVsIHJldmlldyByZXF1aXJlbWVudCBleHRlbmRzIHRvIGluZGl2aWR1YWwgZHJpdmVycywg YnV0IEkgbWlnaHQgYmUgbWlzdGFrZW4uIFRoZSBraW5kIG9mIHRoaW5ncyB3ZSBjYXJlIGFib3V0 IChpbW8pIGFyZSwgaW4gb3JkZXI6IHRoZSBjb3JlIHJhbmRvbWRldiBkZXZpY2UsIHRoZSBGb3J0 dW5hIGltcGxlbWVudGF0aW9uLCB0aGUgZ2VuZXJpYyBlbnRyb3B5IGdhdGhlcmluZywgYW5kIHRo YXQgZW50cm9weSAgZGF0YSBjYW4gb25seSBiZSB1c2VkIG9uY2Ug4oCUIGRvbuKAmXQgZXhwb3Nl IGl0IHRvIGEgdXNlciBhbmQgYWxzbyBmZWVkIGl0IHRvIHJhbmRvbWRldi4gQWxzbywgYXJjNHJh bmRvbSBldCBhbC4KPgo+IFBlcnNvbmFsbHksIEkgZG9u4oCZdCBoYXZlIHRoZSBleHBlcnRpc2Ug d2l0aCB0aGlzIHBhcnRpY3VsYXIgaGFyZHdhcmUgdG8gZmluZCBhbnl0aGluZyBvYmplY3Rpb25h YmxlIGFib3V0IHRoaXMgY2hhbmdlLiBUaGUgYWN0dWFsIGNoYW5nZSB0byB0aGUgaGFydmVzdCBm dW5jdGlvbiBpbiB0aGlzIGRyaXZlciBpcyBkZSBtaW5pbWlzLiBBcyBmYXIgYXMgSeKAmW0gY29u Y2VybmVkLCBpdCBsb29rcyBnb29kIHRvIG1lOyBzaGlwIGl0IQo+Cj4gT24gU3VuLCBOb3YgMTcs IDIwMTkgYXQgMDY6MjkgS3lsZSBFdmFucyA8a2V2YW5zQGZyZWVic2Qub3JnPiB3cm90ZToKPgo+ PiBPbiBTdW4sIE5vdiAxNywgMjAxOSBhdCA0OjAzIEFNIE1hcmsgTXVycmF5IDxtYXJrbUBmcmVl YnNkLm9yZz4gd3JvdGU6Cj4+Pgo+Pj4gSGksCj4+Pgo+Pj4gPiBPbiAxNiBOb3YgMjAxOSwgYXQg MTg6NTksIEt5bGUgRXZhbnMgPGtldmFuc0BGcmVlQlNELm9yZz4gd3JvdGU6Cj4+PiA+Cj4+PiA+ IE9uIFNhdCwgTm92IDE2LCAyMDE5IGF0IDEyOjQ4IFBNIFJvYmVydCBDcm93c3RvbiB2aWEgZnJl ZWJzZC1hcm0KPj4+ID4gPGZyZWVic2QtYXJtQGZyZWVic2Qub3JnPiB3cm90ZToKPj4+ID4+Cj4+ PiA+PiBJIGhhdmUgbWFkZSBhIGZpcnN0IGN1dCBhdCBzdXBwb3J0aW5nIHRoZSBCcm9hZGNvbSAy ODM4IGhhcmR3YXJlIHJhbmRvbSBudW1iZXIgZ2VuZXJhdG9yLCBhcyBmb3VuZCBvbiB0aGUgUmFz cGJlcnJ5IFBpIDQuCj4+PiA+Pgo+Pj4gPj4gRGlmZjogaHR0cHM6Ly9naXRodWIuY29tL2ZyZWVi c2QvZnJlZWJzZC9jb21wYXJlL21hc3Rlci4uLlJvYkNyb3dzdG9uOnBpNC1od3JuZwo+Pj4gPj4K Pj4+ID4+IFRoaXMgZXh0ZW5kcyB0aGUgZXhpc3RpbmcgYmNtMjgzNV9ybmcuYyBkcml2ZXIgdG8g ZnVuY3Rpb24gb24gdGhlIFBpNC4gVW5mb3J0dW5hdGVseSBJIGRvIG5vdCBoYXZlIGEgUmFzcGJl cnJ5IFBpIDMgYm9hcmQgdG8gY29uZmlybSBpdCBzdGlsbCB3b3JrcyB0aGVyZSwgYnV0IG9uIG15 IFBpNCwgaXQgZ2VuZXJhdGVzIChhcHBhcmVudGx5KSByYW5kb20gbnVtYmVycy4KPj4+ID4+Cj4+ PiA+Cj4+PiA+IEhpLAo+Pj4gPgo+Pj4gPiBObyB3b3JyaWVzLSBJJ3ZlIGdvdCBhY2Nlc3MgdG8g YSBQaSAzIGZvciByZWdyZXNzaW9uIHRlc3RpbmcuIENhbiB5b3UKPj4+ID4gdGhyb3cgd2hhdCB5 b3UndmUgZ290IGludG8gUGhhYnJpY2F0b3IgWzBdIGFuZCBhZGQgbWUgYXMgYSByZXZpZXdlcj8K Pj4+ID4gV2UgY2FuIGl0ZXJhdGUvcmV2aWV3IGZyb20gdGhlcmUuCj4+Pgo+Pj4gUGxlYXNlIGFs c28gYWRkIG1hcmttQCBhbmQgY2VtQCAob3IgY3Nwcm5nQCkuIFlvdSdsbCBuZWVkIG9uZSBvZiB1 cyB0byBPSyB0aGUgY29tbWl0Lgo+Pj4KPj4KPj4gSGksIChhZGRpbmcgY2VtQCB0byBDQyBsaXN0 KQo+Pgo+PiBJcyB0aGVyZSBhIGRvY3VtZW50IG9yIHNvbWV0aGluZyBvdXRsaW5pbmcgd2hhdCBj c3BybmdAIHdhbnRzIHRvCj4+IGFjY29tcGxpc2g/IEkgZGVmaW5pdGVseSBkb24ndCBvYmplY3Qg dG8gYWRkaW5nIHlvdSBndXlzIG9uIHRoaXMgb25lCj4+IChib3RoIGJlY2F1c2Ugb2YgdGhlIGNz cHJuZ0Agb3JpZ2luIHN0b3J5IGFuZCB0aGlzIHRvdWNoZXMganVzdCBlbm91Z2gKPj4gYWN0dWFs IFJORyBjb2RlIHBhdGggdG8gd2FycmFudCBpdCwgYXQgYSBnbGFuY2UpLCBidXQgZ29pbmcgZm9y d2FyZC0KPj4gaXMgY3Nwcm5nQCB3YW50aW5nIHRvIGF1ZGl0IHByZS1leGlzdGluZyBzdHVmZiBh cyBpdCBnZXRzIHRvdWNoZWQgaW4KPj4gYW55IHdheSAoZS5nLiBleGlzdGluZyBkcml2ZXIsIGp1 c3QgYWRkaW5nIGNvbXBhdGliaWxpdHkgYml0cyB0byBtYWtlCj4+IGl0IHByb2JlL2F0dGFjaCBv biBuZXcgYm9hcmQpLCBvciBqdXN0IGFueSBuZXcgY29kZSBhY3R1YWxseSBhZmZlY3RpbmcKPj4g Uk5HPwo+Pgo+PiBUaGFua3MsCj4+Cj4+IEt5bGUgRXZhbnM= From owner-freebsd-arm@freebsd.org Sat Nov 23 10:15:17 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 46D541B1520 for ; Sat, 23 Nov 2019 10:15:17 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic313-19.consmr.mail.gq1.yahoo.com (sonic313-19.consmr.mail.gq1.yahoo.com [98.137.65.82]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 47Kq1H10Qrz3PYv for ; Sat, 23 Nov 2019 10:15:14 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: L40p3OkVM1lFH4pkCjZsB0EJo97fyKRy2TWMUHuHCDjHC2qpKDUkDZS75gG42xI kaXUVKkopzwczznlawc42NQvhjYqB6g91t71BCyU6vG4w1mcwQlEIL9x0QeQsZEF60FecDk5af5G stoxwxUqXm3Lt1tEbm5fl9O4TzfGBhQgrdIuBznGo6p83AF7CmillPqSS_mydow_mTMV22SMrCvw IeqTyUI9aJQZHaJxJCo6IUY1v_lCqGA_gU33ghYC13kXN8oqhc_cYvR_Pjkp8UMIr5lBM0iNuocJ 45gL_57l9SWjbnqi74ybLe.zhWnB6XeHEroYAevQZ0TYb9ce9pARN8_UH.Pbjz5vfd0Q6qsQicTk bmLYnasjS7Eu45myQ7NJxdo2eF6lu9kNsBndwxP_Qqr6ENolxeYE..3fzo2kdL9DDEMrDR_s4h0F b0SvelIOQtXv2IZUksQN1g1yIaDCK2UJIZYoMbcWgx1I_9FNgFNaEl5kApEKDRRM4xcjA6lt2GIF 0vzglG99DoRVscOfAzswmPbX7OtfBCYOX1sGH0Z_d2c5mnH6x6MJS.OGKZFZ0mOULSmbqbHWZAAf lIhJf6NTVq9Zwb6qZKZhg6X0MhI9O4ApT5ZkN5XfmQ6iThWBeR1cRnEvSIKLMscD0H9AtzthYTCw Bid61y2xWZF4fGqVqibibZed5TEJE8Hbr3Y6RNY7XQmX.RAVUwLcUuM7QBlQl54fEQA.yd5iPCAO 5amcRlUjsPjTZS.ZzKBuO5TMd8kC5D4.wVo0XEemFlxHirGtYiXASmxOhBOaVB8eXwFTjXk7_1dc mZIxCM_9EQeE13W8GpPE9YtojolveVbWnMvOEEaVnjFC.7ay1kL5ffIfYaLS_h2jxGL_B9YZRZfX h9rUKfLWRXsTHx0T9HMGX02f.VE_AkHJga1UGPAyY9Sfgfkfg3fYyxYQetpn3oGh5kV_T6dgYW4T cy3DmeBiz_pt4OC0flsSDPrSY2mcUuU5kIo7q_hcqE0uZnkMECdpke4A1vVOwIIwbh9HvkTuGn9i JCsrnHA2f1o2bHP6FASw9XJ7we3ihoyIAjJhVn01fbhsFuITBZTKpyLDnXLpsE6TChGAEmE1uIqC hLcKnximGotplw1P5Etw7Lwd9M8yesBrqMO9_uMi0HZfmuZgkwb7gZPmv1xsu_Xr9nhBqPWp5roh 24LQwZZaFi9ekp_aSHg6yLYxd4lTaYtNIJBJ7djh5VnZKfdbwZXEGjnDvfdEAiZTFG.mGJ1dWKuj EJztDgXslUy1qgkH84YLyuHW8nh9cphlLLlIA4YTy3XI1DYOk5Wnv2JkEh_xcPanKigSd_Vyts2w 0yDiyEO4GZw5fiXklNgHyf_jztBbXN6.klOMRi8nEv9xxtkB5H1.1MxJttgz.RMd8FQkA2jpbMYx f84_srum2jO0rtB5HbbC_Hw-- Received: from sonic.gate.mail.ne1.yahoo.com by sonic313.consmr.mail.gq1.yahoo.com with HTTP; Sat, 23 Nov 2019 10:15:12 +0000 Received: by smtp404.mail.bf1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 4301ba94c85afa74d84256b2348d79a2; Sat, 23 Nov 2019 10:15:08 +0000 (UTC) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\)) Subject: head r355027M : Rock64 4GB booted from 128GB emmc (no sdcard plugged in and no jumper to force sdcard slot use) Message-Id: <87A31A90-774A-4EF7-8428-8F8FEBFD5406@yahoo.com> Date: Sat, 23 Nov 2019 02:15:06 -0800 To: freebsd-arm@freebsd.org X-Mailer: Apple Mail (2.3601.0.10) References: <87A31A90-774A-4EF7-8428-8F8FEBFD5406.ref@yahoo.com> X-Rspamd-Queue-Id: 47Kq1H10Qrz3PYv X-Spamd-Bar: + X-Spamd-Result: default: False [1.43 / 15.00]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[yahoo.com:s=s2048]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ptr:yahoo.com]; FREEMAIL_FROM(0.00)[yahoo.com]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_SPAM_MEDIUM(0.95)[0.950,0]; RCVD_TLS_LAST(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DKIM_TRACE(0.00)[yahoo.com:+]; DMARC_POLICY_ALLOW(-0.50)[yahoo.com,reject]; RCVD_IN_DNSWL_NONE(0.00)[82.65.137.98.list.dnswl.org : 127.0.5.0]; MV_CASE(0.50)[]; IP_SCORE(0.00)[ip: (5.22), ipnet: 98.137.64.0/21(0.88), asn: 36647(0.70), country: US(-0.05)]; IP_SCORE_FREEMAIL(0.00)[]; NEURAL_SPAM_LONG(0.98)[0.976,0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[yahoo.com]; ASN(0.00)[asn:36647, ipnet:98.137.64.0/21, country:US]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[yahoo.com.dwl.dnswl.org : 127.0.5.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: Sat, 23 Nov 2019 10:15:17 -0000 # uname -apKU FreeBSD Rock64OrRPI3 13.0-CURRENT FreeBSD 13.0-CURRENT #24 r355027M: Sat = Nov 23 00:41:05 PST 2019 = markmi@FBSDFHUGE:/usr/obj/cortexA53_clang/arm64.aarch64/usr/src/arm64.aarc= h64/sys/GENERIC-NODBG arm64 aarch64 1300061 1300061 A few notes about what was done . . . The more modern FreeBSD source replaced some of my old hacks that allowed booting the Pine64+ 2GB via emmc on a conversion card. (I've not tried replacing the u-boot material with the Pine64+ 2GB material to see if that would still work.) Since I built a non-debug head r355027, I had to work around one build failure: a variable only used in a KASSERT that stopped the build. I used: # more /usr/local/share/u-boot/u-boot-rock64/README U-Boot loader and related files for the Pine64 Rock64. To install this bootloader on an sdcard just do: dd if=3D/usr/local/share/u-boot/u-boot-rock64/idbloader.img = of=3D/path/to/sdcarddevice seek=3D64 bs=3D512 conv=3Dsync dd if=3D/usr/local/share/u-boot/u-boot-rock64/u-boot.itb = of=3D/path/to/sdcarddevice seek=3D16384 bs=3D512 conv=3Dsync (In the cross build/install environment at the time /dev/da13 was the /path/to/sdcarddevice .) # ls -la /usr/local/share/u-boot/u-boot-rock64/ total 1124 drwxr-xr-x 2 root wheel 512 Oct 26 20:56 . drwxr-xr-x 8 root wheel 512 Sep 15 16:02 .. -rw-r--r-- 1 root wheel 358 Oct 26 19:28 README -rw-r--r-- 1 root wheel 351560 Oct 26 19:28 idbloader.img -rw-r--r-- 1 root wheel 724148 Oct 26 19:28 u-boot.itb The emmc was set up with (shown on the Rock64 after installation, not as seen on the cross build/install environment): # gpart show =3D> 63 244277185 mmcsd0 MBR (116G) 63 32705 - free - (16M) 32768 102312 1 fat32lba [active] (50M) 135080 28760 - free - (14M) 163840 241172480 2 freebsd (115G) 241336320 2940928 - free - (1.4G) =3D> 0 241172480 mmcsd0s2 BSD (115G) 0 230686720 1 freebsd-ufs (110G) 230686720 7340032 2 freebsd-swap (3.5G) 238026752 2097152 4 freebsd-swap (1.0G) 240123904 1048576 - free - (512M) I got the 32768 for fat32lba from what Arch Linux ARM has one start with for installing Arch on a Rock64. (I've not found FreeBSD material about that choice, implicitly leaving it to the u-boot.itb size and seek position for what to avoid in this case.) (Things are set up to allow less total swap space for smaller memory machines by just not adding the other swap space.) The media is an updated variant of my old Pine64+ 2GB setup, which explains some naming that I've left alone. Historically I could boot either the Pine64+ 2GB or the RPi3 with that media. (No u-boot conflicts or such. I've not dealt with the RPI3 material yet.) # df -m Filesystem 1M-blocks Used Avail Capacity Mounted on /dev/label/PINE64P2Groot 109101 37794 62578 38% / devfs 0 0 0 100% /dev /dev/label/PINE642GAboot 49 15 34 31% /boot/efi # ls -la /boot/efi/EFI/BOOT/ total 1336 drwxr-xr-x 1 root wheel 4096 Sep 27 2018 . drwxr-xr-x 1 root wheel 4096 Sep 27 2018 .. -rwxr-xr-x 1 root wheel 679256 Nov 22 16:45 bootaa64.efi -rwxr-xr-x 1 root wheel 679256 Nov 22 16:45 loader.efi Both of the *.efi files are copies of: # ls -ld /boot/loader.efi=20 -r-xr-xr-x 2 root wheel 679256 Nov 23 00:45 /boot/loader.efi (The cross-build/install environment had an odd, 8 hour earlier time for a while for some reason.) Before there was just the bootaa64.efi but I decided to also have a copy under the FreeBSD name. (The source file was /mnt/boot/loader.efi during the cross-install activity. I had mounted the msdosfs file sytsem to /media there as well, making for /media/EFI/BOOT/ for the target directory the copy.) Other that some of the above detail, the install was essentially normal for my context. For reference: # ls -ld /dev/mmcsd* crw-r----- 1 root operator 0x4f Nov 23 00:56 /dev/mmcsd0 crw-r----- 1 root operator 0x50 Nov 23 00:56 /dev/mmcsd0boot0 crw-r----- 1 root operator 0x51 Nov 23 00:56 /dev/mmcsd0boot1 crw-r----- 1 root operator 0x49 Nov 23 00:56 /dev/mmcsd0rpmb crw-r----- 1 root operator 0x52 Nov 23 00:54 /dev/mmcsd0s1 crw-r----- 1 root operator 0x53 Nov 23 00:54 /dev/mmcsd0s2 crw-r----- 1 root operator 0x56 Nov 23 00:54 /dev/mmcsd0s2a crw-r----- 1 root operator 0x57 Nov 23 00:54 /dev/mmcsd0s2b crw-r----- 1 root operator 0x59 Nov 23 01:06 /dev/mmcsd0s2d =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-arm@freebsd.org Sat Nov 23 22:26:26 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 B489E1C11AB for ; Sat, 23 Nov 2019 22:26:26 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic316-55.consmr.mail.gq1.yahoo.com (sonic316-55.consmr.mail.gq1.yahoo.com [98.137.69.31]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 47L7Dw4GdRz4X4k for ; Sat, 23 Nov 2019 22:26:24 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: tKRAXbgVM1nZ3fPUvc35FJgX5c2Rc0u.UHUqXEhlEyjy7kRhKbFDmRf8ao7iPNt _FBm1plj5sQeP6OgP.h4lyV_mf5l6UsF7cRiKlvUos281Wee1ty7MRSMkosDakTTPVBD5lpyQl8G a3Ho_6zgg3CNY7Nd7JrIb31OlntO8Oo.sJ3psuifWO.wsbwkHSXxDpz6DJ7BwTc001EObkgy2HGT OrEcpKxbcc.4NNYlisU3K_K5VH3Q6nf0qO11eHVV9v9O53_oyq.LJZHruXoDKwsGg1dedtK8r_.Z d13jx869.M0wvHKhQc9H0..na5RhXUiWLGde94mC7GfeEe_TiBMg3zS02p5JCWoKTbo4BDIZ5WPh EN.rXzRdEPLvy_okhqfvVEIiNnQ1.7Pnr7OcOcKIa5e0obbQ8FM82YZ.Wry5uj0iEXPoWjWYhsOw gVL5nSUmTIQ0dkrQsQwd7RcxFk3TGJVQb6kPPJMh1ARtTI.rUX3tdNGzVx82rk5cwh3nVc1t4YuK TOxS.AYEGF7mE4CPuELRkb61GO6vyvC4l.Fwc.xwNMTQI6.AIE6pvRO0MhSqxvMtB7CqSG59sLl7 XBgIk5dRe8MigsOjvSRFI0G.Z3Up6er_jllQ3.CvE3F4xeXfiIiui85cZ8mQ50D1UuibKF7G8eUY LVtW5UDPNxfjqk8ubqMzvv2Chlz2VHOPZHLRjV1Mp4ofI2XE5zUjL60QHK_ST0mloPaujzY.t0wd _dEjfoRPqFk82bb0lvF6p38ai8DvWJ8WDGAMpQ2VS7WGkcqGlkx_Fq7Ho9k6hewkgkW4e8rvQW_x v6DPC2GEd3.IM43QuXDgPSVTDkKHzTADYRwkiLOxkQiVSQNMTiBZ3_hzUNfSKcLRkrgVcC253TFO p4kwhu1CHflLEpZpjizoORGNtl2pKJK1hAL_oLX7eg9IuSN3Sgu7G3BsmgzeSVsvP69Rew99USPH M2VrhldlbOALXVlefbahpTXr.5wd56AXufzKuNRkOWXNtRaVQvlPh1jU7WJLHyFJm541RzCEWz7Y IPL.9CfgLbAakfEgv2Q_2fVoKOBqo60X4AMrTCdVx2SkxPaTRkahUFmIJ9wcHcfHOhjPP8k_nVQ9 wREFjeJNGYGGW3WY15nEwxn2XMq.S97EbJF3yW4ruia5DUmlZBW.vKqbDJ5d_F1YKJ4fGZABUcc0 LI.0f_QVvLOV_fo8ovR.Dcgeu2Sr1MKtpYPimpiJW0nv.WQ5NxUzB2QKwS.i8j1ESJCr2hmYm9bw QBynBFFk3c_B2CDUDzMx5ZqvT.fxgRaF7ykm43djE.Dep9BsFWw5SOZeUGZLw.nDHIobTqpX6Uky CD4qV4Ug.xbM54VvKxYabQuss9kxqtHfR3H0Nn_h5mSrvpBDmThRVnRiAlpAu9UCIFBKkZPD3Mh0 a_h6FUZQ6HpWSPYJt_fQ- Received: from sonic.gate.mail.ne1.yahoo.com by sonic316.consmr.mail.gq1.yahoo.com with HTTP; Sat, 23 Nov 2019 22:26:22 +0000 Received: by smtp428.mail.gq1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 94861fd2677e4505aef4e0f3d9aab373; Sat, 23 Nov 2019 22:26:18 +0000 (UTC) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\)) Subject: head -r355027 on Rock64: CPU staying at 600 MHz? (based on ArchLinuxARM benchmark comparison) Message-Id: Date: Sat, 23 Nov 2019 14:26:17 -0800 To: freebsd-arm@freebsd.org X-Mailer: Apple Mail (2.3601.0.10) References: X-Rspamd-Queue-Id: 47L7Dw4GdRz4X4k X-Spamd-Bar: + X-Spamd-Result: default: False [1.44 / 15.00]; R_SPF_ALLOW(-0.20)[+ptr:yahoo.com]; FREEMAIL_FROM(0.00)[yahoo.com]; TO_DN_NONE(0.00)[]; MV_CASE(0.50)[]; DKIM_TRACE(0.00)[yahoo.com:+]; DMARC_POLICY_ALLOW(-0.50)[yahoo.com,reject]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[yahoo.com]; ASN(0.00)[asn:36647, ipnet:98.137.64.0/21, country:US]; MID_RHS_MATCH_FROM(0.00)[]; SUBJECT_HAS_QUESTION(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[yahoo.com:s=s2048]; FROM_HAS_DN(0.00)[]; DWL_DNSWL_NONE(0.00)[yahoo.com.dwl.dnswl.org : 127.0.5.0]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; IP_SCORE(0.00)[ip: (5.99), ipnet: 98.137.64.0/21(0.88), asn: 36647(0.70), country: US(-0.05)]; NEURAL_SPAM_MEDIUM(0.96)[0.963,0]; RCPT_COUNT_ONE(0.00)[1]; IP_SCORE_FREEMAIL(0.00)[]; NEURAL_SPAM_LONG(0.98)[0.982,0]; RCVD_IN_DNSWL_NONE(0.00)[31.69.137.98.list.dnswl.org : 127.0.5.0]; 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: Sat, 23 Nov 2019 22:26:26 -0000 I ran my C++ variation on the old HINT serial/threads benchmark on ArchLinuxARM (5.3.12 kernel) and FreeBSD -r355027 and got a surprise for the CPU/memory-cache dominated range. The benchmark explores from small problems dependent primarily on CPU speed (and memory cache speed) to sizes/patterns dominated by RAM speed (the access pattern makes caches far less effective). (I do not normally use it to explore sizes that would involve paging and have not done so here.) The RAM-speed dominated part is ball park similar, as expected. BUT: For the CPU/cache-speed dominated part FreeBSD is near a factor of 2 slower than for ArchLinuxARM. My guess is that the FreeBSD CPU frequency is staying at 600 MHz instead of going to the 1200MHz or 1296MHz that is listed as possible: dev.cpufreq_dt.3.freq_settings: 408/-1 600/-1 816/-1 1008/-1 1200/-1 1296/-1 dev.cpufreq_dt.3.%parent: cpu3 dev.cpufreq_dt.3.%pnpinfo: dev.cpufreq_dt.3.%location: dev.cpufreq_dt.3.%driver: cpufreq_dt dev.cpufreq_dt.3.%desc: Generic cpufreq driver dev.cpufreq_dt.2.freq_settings: 408/-1 600/-1 816/-1 1008/-1 1200/-1 1296/-1 dev.cpufreq_dt.2.%parent: cpu2 dev.cpufreq_dt.2.%pnpinfo: dev.cpufreq_dt.2.%location: dev.cpufreq_dt.2.%driver: cpufreq_dt dev.cpufreq_dt.2.%desc: Generic cpufreq driver dev.cpufreq_dt.1.freq_settings: 408/-1 600/-1 816/-1 1008/-1 1200/-1 1296/-1 dev.cpufreq_dt.1.%parent: cpu1 dev.cpufreq_dt.1.%pnpinfo: dev.cpufreq_dt.1.%location: dev.cpufreq_dt.1.%driver: cpufreq_dt dev.cpufreq_dt.1.%desc: Generic cpufreq driver dev.cpufreq_dt.0.freq_settings: 408/-1 600/-1 816/-1 1008/-1 1200/-1 1296/-1 dev.cpufreq_dt.0.%parent: cpu0 dev.cpufreq_dt.0.%pnpinfo: dev.cpufreq_dt.0.%location: dev.cpufreq_dt.0.%driver: cpufreq_dt dev.cpufreq_dt.0.%desc: Generic cpufreq driver dev.cpufreq_dt.%parent: dev.cpu.0.freq_levels: 1296/-1 1200/-1 1008/-1 816/-1 600/-1 408/-1 dev.cpu.0.freq: 600 (The above was not from during a benchmark run: just showing the default and the alternatives listed.) Is the reversal of ordering of freq_settings vs. freq_levels also interesting? === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar)