From owner-freebsd-arm@FreeBSD.ORG Sun Mar 8 01:52:11 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CB5644F2 for ; Sun, 8 Mar 2015 01:52:11 +0000 (UTC) Received: from wa3yre.wynn.com (wa3yre.wynn.com [199.89.147.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 86866348 for ; Sun, 8 Mar 2015 01:52:11 +0000 (UTC) Received: from ivory.wynn.com (mail.wynn.com [199.89.147.3]) (authenticated bits=0) by wa3yre.wynn.com (8.14.3/8.12.6) with ESMTP id t281q58E052854; Sat, 7 Mar 2015 20:52:05 -0500 (EST) (envelope-from freebsd-arm@wynn.com) Date: Sat, 7 Mar 2015 20:52:04 -0500 From: Brett Wynkoop To: Peter Garshtja , freebsd-arm@freebsd.org Subject: Re: svn server problems Message-ID: <20150307205204.0fbc6d6d@ivory.wynn.com> In-Reply-To: <54FB8A24.5070207@ambient-md.com> References: <20150307155310.55d0e19b@ivory.wynn.com> <45ef370cb6c.33c874ef@mail.schwarzes.net> <20150307182602.3886f89b@ivory.wynn.com> <54FB8A24.5070207@ambient-md.com> X-Mailer: Claws Mail 3.10.1 (GTK+ 2.24.25; x86_64-apple-darwin10.8.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Mar 2015 01:52:11 -0000 On Sat, 07 Mar 2015 18:30:44 -0500 Peter Garshtja wrote: > hi, > > My issue was that my corporate router/firewall didnt allow me to svn > then i tried svn+http/svn+https/svn+http over http proxy and every > time i had similar problems. > I changed the gateway and i could to download the src. > > I think it could be your local problem. Well there is no firewall between me and the internet, but I just started an svnlite up on both the BBone and my x86 box at the same time. If the BBone again fails and the x86 works then I think we need to start looking at the arm network stack. -Brett -- wynkoop@wynn.com http://prd4.wynn.com/wynkoop/pgp-keys.txt 917-642-6925 929-272-0000 "The strongest reason for the people to retain the right to keep and bear arms is, as a last resort, to protect themselves against tyranny in government" - Thomas Jefferson. From owner-freebsd-arm@FreeBSD.ORG Sun Mar 8 02:56:46 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E86A8C6A for ; Sun, 8 Mar 2015 02:56:46 +0000 (UTC) Received: from wa3yre.wynn.com (wa3yre.wynn.com [199.89.147.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 87D43B39 for ; Sun, 8 Mar 2015 02:56:46 +0000 (UTC) Received: from ivory.wynn.com (mail.wynn.com [199.89.147.3]) (authenticated bits=0) by wa3yre.wynn.com (8.14.3/8.12.6) with ESMTP id t282uh1n058674; Sat, 7 Mar 2015 21:56:44 -0500 (EST) (envelope-from wynkoop@wynn.com) Date: Sat, 7 Mar 2015 21:56:42 -0500 From: Brett Wynkoop To: Brett Wynkoop Subject: Re: svn server problems Message-ID: <20150307215642.008b41a8@ivory.wynn.com> In-Reply-To: <20150307182602.3886f89b@ivory.wynn.com> References: <20150307155310.55d0e19b@ivory.wynn.com> <45ef370cb6c.33c874ef@mail.schwarzes.net> <20150307182602.3886f89b@ivory.wynn.com> X-Mailer: Claws Mail 3.10.1 (GTK+ 2.24.25; x86_64-apple-darwin10.8.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: base64 Cc: freebsd-arm@freebsd.org, Andreas Schwarz X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Mar 2015 02:56:47 -0000 LS0tLS1CRUdJTiBQR1AgU0lHTkVEIE1FU1NBR0UtLS0tLQ0KSGFzaDogU0hBMQ0KDQpHcmVldGlu Zy0NCg0KV2VsbCBhZnRlciBJIHN0YXJ0ZWQgYm90aCB0aGUgc3ZuIHVwIG9uIHRoZSB4ODYgYW5k IGFybSBhdCB0aGUgc2FtZQ0KdGltZSB0aGV5IGJvdGggY29tcGxldGVkLiAgSSBzdXNwZWN0IHRo ZXJlIHdhcyBhIHNlcnZlciBzaWRlIHByb2JsZW0NCnRoYXQgd2FzIGNvcnJlY3RlZC4NCg0KQSAg ICBzeXMvZGV2L3BjaS9wY2lfaW92X3ByaXZhdGUuaA0KVSAgICBzeXMvZGV2L3BjaS9wY2lfaWYu bQ0KVSAgICBzeXMvZGV2L2l4Z2JlL2l4Z2JlLmgNClUgICAgc3lzL2NhbS9jYW1fcGVyaXBoLmMN CiBVICAgc3lzDQogVSAgIC4NClVwZGF0ZWQgdG8gcmV2aXNpb24gMjc5NzYxLg0KW3Jvb3RAYmVh Z2xlYm9uZSAvdXNyL3NyY10jIA0KDQpVICAgIHNiaW4vZ2VvbS9jbGFzcy9wYXJ0L2dlb21fcGFy dC5jDQpVICAgIHNiaW4vaWZjb25maWcvYWZfbmQ2LmMNClUgICAgc2Jpbi9pZmNvbmZpZy9hZl9p bmV0Ni5jDQpVICAgIGdudS91c3IuYmluL2RpZmYvTWFrZWZpbGUNClUgICAgc2Jpbi9pZmNvbmZp Zy9pZmNvbmZpZy44DQpVICAgIGdhbWVzL01ha2VmaWxlDQpVcGRhdGVkIHRvIHJldmlzaW9uIDI3 OTc2MS4NCltyb290QHByZDIgL3Byb2ovd3lua29vcC9hcm1zcmNdIyANCg0KTm93IHRvIHNlZSB3 aGF0IGhhcHBlbnMgd2l0aCB0aGUgbmV4dCBrZXJuZWwgYnVpbGQgYW5kIG15IFVTQiBpc3N1ZXMu DQoNCi0gLUJyZXR0DQotIC0tIA0KDQp3eW5rb29wQHd5bm4uY29tICAgICAgICAgICAgICAgaHR0 cDovL3ByZDQud3lubi5jb20vd3lua29vcC9wZ3Ata2V5cy50eHQNCjkxNy02NDItNjkyNQ0KOTI5 LTI3Mi0wMDAwDQoNCkFtZW5kbWVudCBJSQ0KDQpBIHdlbGwgcmVndWxhdGVkIG1pbGl0aWEsIGJl aW5nIG5lY2Vzc2FyeSB0byB0aGUgc2VjdXJpdHkgb2YgYSBmcmVlDQpzdGF0ZSwgdGhlIHJpZ2h0 IG9mIHRoZSBwZW9wbGUgdG8ga2VlcCBhbmQgYmVhciBhcm1zLCBzaGFsbCBub3QgYmUNCmluZnJp bmdlZC4NCg0KLS0tLS1CRUdJTiBQR1AgU0lHTkFUVVJFLS0tLS0NClZlcnNpb246IEdudVBHIHYy DQoNCmlRRWNCQUVCQWdBR0JRSlUrN3ByQUFvSkVLNkszeXJjK1J1RFdSMEgvQXlSUFY1cDZRWDBj R1FSUTF3a2hCREENClY0M1BZeE1JeG9rOEdDMWt1NkI3MGhYa0NsS21hUzJKa09aM3Z5b3BuYSt2 UGp5T2pQZzBDZFZtOEt3MDJ4WVMNCkJoZzYyWDZrdE80WS9adUlDcE0zdmp4bW5jcDVOYXVvdUVF ZHFHRHU3bU5vWmpYdmJjRmMzSGM5NmdDNFc0OVoNClh6eHI0enZQNDZFVXprODQyZW1IMFBkdERL Q2Fkd0I0dThFYTRRMzRMWDZ0ajRiMUtiTWwrUVFLVEZsSGl6UDINClJHM0JUbEFadEpuMys4dmxG ZVRWRUhaRzAwRzQ1MzVRdTBBVEJveFFNZ0Y4WktqU0N2aWx4Qlg3V1prTVZ3WU4NCmM2TzlUdXlp QlF3NmtZVUxrOW51SVMxdWdVVFRoZDNqcjlyeWhEc0pmcktzcklkak8yYStMQTlMTCtORXcvRT0N Cj05anBGDQotLS0tLUVORCBQR1AgU0lHTkFUVVJFLS0tLS0NCg== From owner-freebsd-arm@FreeBSD.ORG Sun Mar 8 05:44:41 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B7E632A8 for ; Sun, 8 Mar 2015 05:44:41 +0000 (UTC) Received: from monday.kientzle.com (99-115-135-74.uvs.sntcca.sbcglobal.net [99.115.135.74]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9289DDA8 for ; Sun, 8 Mar 2015 05:44:40 +0000 (UTC) Received: (from root@localhost) by monday.kientzle.com (8.14.4/8.14.4) id t285iWLw024795; Sun, 8 Mar 2015 05:44:32 GMT (envelope-from tim@kientzle.com) Received: from [192.168.2.102] (gateway.kientzle.com [192.168.1.65]) by kientzle.com with SMTP id ud4ef8yfi3vptumwaudtaiei4a; Sun, 08 Mar 2015 05:44:32 +0000 (UTC) (envelope-from tim@kientzle.com) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) Subject: Re: svn server problems From: Tim Kientzle In-Reply-To: <20150307155310.55d0e19b@ivory.wynn.com> Date: Sat, 7 Mar 2015 21:44:32 -0800 Content-Transfer-Encoding: 7bit Message-Id: References: <20150307155310.55d0e19b@ivory.wynn.com> To: Brett Wynkoop X-Mailer: Apple Mail (2.2070.6) Cc: freebsd-arm X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Mar 2015 05:44:41 -0000 > On Mar 7, 2015, at 12:53 PM, Brett Wynkoop wrote: > > Greeting- > > So I have been trying since last night to svn up my source tree on the > BBone with no luck. It seems to never complete and instead produces > the following error: > > A sys/gnu/dts/arm/zynq-zc702.dts > A sys/gnu/dts/arm/imx31-bug.dts > A sys/gnu/dts/arm/ste-href-ab8500.dtsi > svn: E120108: Error retrieving REPORT: The server unexpectedly closed > the connection. > > Is anyone else seeing this issue? Back when I did regular native build worlds, I saw this quite regularly. I was always able to eventually complete an update, but it sometimes took many many iterations of: svnlite cleanup && svnlite up before it could complete. I suspect this is an artifact of SD performance: SVN tries to keep a network connection open while its updating files locally and this leads to server timeouts. I had better luck using git. I think its update strategy does not require keeping a network connection open for such long periods of time. Tim From owner-freebsd-arm@FreeBSD.ORG Sun Mar 8 16:02:51 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4BB889AB for ; Sun, 8 Mar 2015 16:02:51 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [IPv6:2001:4f8:3:ffe0:406a:0:50:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2A7A3E81 for ; Sun, 8 Mar 2015 16:02:51 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [127.0.1.5]) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9) with ESMTP id t28G2oYF077268 for ; Sun, 8 Mar 2015 16:02:50 GMT (envelope-from root@phabric-backend.isc.freebsd.org) Received: (from root@localhost) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9/Submit) id t28G2oev077267; Sun, 8 Mar 2015 16:02:50 GMT (envelope-from root) Date: Sun, 8 Mar 2015 16:02:50 +0000 To: freebsd-arm@freebsd.org From: "ian (Ian Lepore)" Subject: [Differential] [Updated] D2017: Allow to disable alignment faults in the kernel configuration file Message-ID: X-Priority: 3 Thread-Topic: D2017: Allow to disable alignment faults in the kernel configuration file X-Herald-Rules: none X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: In-Reply-To: References: Thread-Index: M2IwYjY0ZDAxMWY3ZTNlM2Y4OWM0M2JjYjUzIFT8cqo= X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: , MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Mar 2015 16:02:51 -0000 ian added a comment. Where is the rest of this change? Just defining an option won't make it so. I've been wondering for a while why we still enforce alignment on armv6+ platforms that don't require it in hardware. I've been assuming that it's because we need extra support code or to change/remove some existing code, but I haven't had time to investigate it yet. REVISION DETAIL https://reviews.freebsd.org/D2017 To: zbb, imp, andrew, ian Cc: freebsd-arm From owner-freebsd-arm@FreeBSD.ORG Sun Mar 8 16:10:30 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E2419AAC for ; Sun, 8 Mar 2015 16:10:30 +0000 (UTC) Received: from pmta2.delivery1.ore.mailhop.org (pmta2.delivery1.ore.mailhop.org [54.149.155.156]) by mx1.freebsd.org (Postfix) with ESMTP id BF145EB7 for ; Sun, 8 Mar 2015 16:10:30 +0000 (UTC) Received: from smtp3.ore.mailhop.org (172.31.18.134) by pmta2.delivery1.ore.mailhop.org id hvhq9820u50t for ; Sun, 8 Mar 2015 15:40:41 +0000 (envelope-from ) Received: from c-73-34-117-227.hsd1.co.comcast.net ([73.34.117.227] helo=ilsoft.org) by smtp3.ore.mailhop.org with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.82) (envelope-from ) id 1YUdJL-0001ty-PV; Sun, 08 Mar 2015 15:40:11 +0000 Received: from revolution.hippie.lan (revolution.hippie.lan [172.22.42.240]) by ilsoft.org (8.14.9/8.14.9) with ESMTP id t28Fe9xV005378; Sun, 8 Mar 2015 09:40:10 -0600 (MDT) (envelope-from ian@freebsd.org) X-Mail-Handler: DuoCircle Outbound SMTP X-Originating-IP: 73.34.117.227 X-Report-Abuse-To: abuse@duocircle.com (see https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information for abuse reporting information) X-MHO-User: U2FsdGVkX19SVDXkgNeBw8LquxoGoLu3 Message-ID: <1425829209.73796.16.camel@freebsd.org> Subject: Re: svn server problems From: Ian Lepore To: Tim Kientzle Date: Sun, 08 Mar 2015 09:40:09 -0600 In-Reply-To: References: <20150307155310.55d0e19b@ivory.wynn.com> Content-Type: text/plain; charset="us-ascii" X-Mailer: Evolution 3.12.10 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Cc: freebsd-arm X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Mar 2015 16:10:31 -0000 On Sat, 2015-03-07 at 21:44 -0800, Tim Kientzle wrote: > > On Mar 7, 2015, at 12:53 PM, Brett Wynkoop wrote: > > > > Greeting- > > > > So I have been trying since last night to svn up my source tree on the > > BBone with no luck. It seems to never complete and instead produces > > the following error: > > > > A sys/gnu/dts/arm/zynq-zc702.dts > > A sys/gnu/dts/arm/imx31-bug.dts > > A sys/gnu/dts/arm/ste-href-ab8500.dtsi > > svn: E120108: Error retrieving REPORT: The server unexpectedly closed > > the connection. > > > > Is anyone else seeing this issue? > > Back when I did regular native build worlds, I saw this > quite regularly. I was always able to eventually complete > an update, but it sometimes took many many iterations of: > > svnlite cleanup && svnlite up > > before it could complete. > > I suspect this is an artifact of SD performance: SVN > tries to keep a network connection open while its updating > files locally and this leads to server timeouts. > > I had better luck using git. I think its update strategy > does not require keeping a network connection open > for such long periods of time. > > Tim I was able to checkout via svnlite to both a super-slow usb stick and to a reasonably fast sdcard last night. No hint of trouble. -- Ian From owner-freebsd-arm@FreeBSD.ORG Sun Mar 8 16:41:28 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BE4EAC62 for ; Sun, 8 Mar 2015 16:41:28 +0000 (UTC) Received: from mail-wi0-f182.google.com (mail-wi0-f182.google.com [209.85.212.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 56CD4232 for ; Sun, 8 Mar 2015 16:41:27 +0000 (UTC) Received: by wiwh11 with SMTP id h11so4191906wiw.1 for ; Sun, 08 Mar 2015 09:41:20 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=W5fJRGB4LxlZLdvsnCtCNwibdrdEZvnA3UZRGZ5XoJE=; b=SW/1Qak3OaxdD5IaFfKLuhWIbHsDNOAzHBp7QfNeJHOSjqqd/xD9adxNoczKEw5Ezw x3i2G+BlfDInA0IZ6MDr0v9W7KTKKS/3fT14d7xY8+txtc7jdCHXLfMntAA4SaWm2sZA SuOIp8MfozQr4CyvUuXdHXJBbrAbG3PqD2DFMqvjKER9U9vxNrC8hjHZLE1dCqV2x8W+ pVGGtA7NFNCX4g0xYSzco1WvYp6sQIZdvXnY7PhXRYpfSmwlCYnQ0BdbSPVIbZ+0EPgh +6NJscPPDUKhIVDAm6u64vNzxjZUoANJTp1L7xFn6y7kc4ymvragklSiZONx1+pq0psz xZNA== X-Gm-Message-State: ALoCoQmjSw60Rw58unP+uAkkI/OP3OELa0usrz0XA9xKa/lKpDBUqj1t5lL/3hj/XYqMflLwb0i/ MIME-Version: 1.0 X-Received: by 10.180.39.139 with SMTP id p11mr1923707wik.61.1425832880354; Sun, 08 Mar 2015 09:41:20 -0700 (PDT) Received: by 10.27.198.6 with HTTP; Sun, 8 Mar 2015 09:41:20 -0700 (PDT) X-Originating-IP: [184.151.114.98] In-Reply-To: <1425829209.73796.16.camel@freebsd.org> References: <20150307155310.55d0e19b@ivory.wynn.com> <1425829209.73796.16.camel@freebsd.org> Date: Sun, 8 Mar 2015 12:41:20 -0400 Message-ID: Subject: Re: svn server problems From: peter garshtja To: Ian Lepore Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: Tim Kientzle , freebsd-arm X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Mar 2015 16:41:28 -0000 This morning svn+https failed, I switched to svn+http. I don't whether it worked because I have had to leave. On Sunday, March 8, 2015, Ian Lepore wrote: > On Sat, 2015-03-07 at 21:44 -0800, Tim Kientzle wrote: >> > On Mar 7, 2015, at 12:53 PM, Brett Wynkoop wrote: >> > >> > Greeting- >> > >> > So I have been trying since last night to svn up my source tree on the >> > BBone with no luck. It seems to never complete and instead produces >> > the following error: >> > >> > A sys/gnu/dts/arm/zynq-zc702.dts >> > A sys/gnu/dts/arm/imx31-bug.dts >> > A sys/gnu/dts/arm/ste-href-ab8500.dtsi >> > svn: E120108: Error retrieving REPORT: The server unexpectedly closed >> > the connection. >> > >> > Is anyone else seeing this issue? >> >> Back when I did regular native build worlds, I saw this >> quite regularly. I was always able to eventually complete >> an update, but it sometimes took many many iterations of: >> >> svnlite cleanup && svnlite up >> >> before it could complete. >> >> I suspect this is an artifact of SD performance: SVN >> tries to keep a network connection open while its updating >> files locally and this leads to server timeouts. >> >> I had better luck using git. I think its update strategy >> does not require keeping a network connection open >> for such long periods of time. >> >> Tim > > I was able to checkout via svnlite to both a super-slow usb stick and to > a reasonably fast sdcard last night. No hint of trouble. > > -- Ian > > > _______________________________________________ > freebsd-arm@freebsd.org mailing list > http://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 Mar 8 16:57:46 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0ABE92F1 for ; Sun, 8 Mar 2015 16:57:46 +0000 (UTC) Received: from mail-qg0-f43.google.com (mail-qg0-f43.google.com [209.85.192.43]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B4D3036D for ; Sun, 8 Mar 2015 16:57:45 +0000 (UTC) Received: by qgef51 with SMTP id f51so23557704qge.0 for ; Sun, 08 Mar 2015 09:57:38 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type; bh=7MdmiYMzjrit5ybD/o5xjt3sUMUy6Y7EoTeHDasZvPA=; b=ZWz6fUvtOgtYdghu46ib1u4AxYt9D2WYGWsFypyRE8KdYT+KX2ukXRx8lQgid4Yicr 4aSt9ASFSXlVmvo7nb/rUdHhXxM1LmDush6wU5nGbLr8e9WXTaymxwxrKBRr+i5I65w2 BkHPUz0yhvRIT+QdsKygLD9hVooF5lFmP1hovS2Thr0Kd6JXQJKpoRhzt8aF3m/ygHfJ yeA97m4qh8m16Sy6Rxh10rF2dfZVTTRWVOV7BfoKGeV3fGfJrezEmj0o/pIY3rjWvV57 eG+sO614RQZoS8AhvZ4XByCCfyWFF+9QX3GaS1Pc4iBK0vrzTCjq+LacfWnCrZSMOQNx g4Rg== X-Gm-Message-State: ALoCoQlUeUk2uFVAjFboCqmjXv/TyV8lazlesq6HCcFH+wFKPc8lLIxD7YsghdS0AxWPdrL1MDeT X-Received: by 10.140.130.71 with SMTP id 68mr31737201qhc.12.1425833857962; Sun, 08 Mar 2015 09:57:37 -0700 (PDT) Received: from [172.26.26.1] (ip69-17-247-231.vif.net. [69.17.247.231]) by mx.google.com with ESMTPSA id j92sm3190759qkh.16.2015.03.08.09.57.35 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 08 Mar 2015 09:57:36 -0700 (PDT) Message-ID: <54FC7F85.9070900@ambient-md.com> Date: Sun, 08 Mar 2015 12:57:41 -0400 From: Peter Garshtja User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: Ian Lepore Subject: Re: svn server problems References: <20150307155310.55d0e19b@ivory.wynn.com> <1425829209.73796.16.camel@freebsd.org> In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: Tim Kientzle , freebsd-arm X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Mar 2015 16:57:46 -0000 confirming that svn+http worked. On 3/8/2015 12:41 PM, peter garshtja wrote: > This morning svn+https failed, I switched to svn+http. I don't whether > it worked because I have had to leave. > > On Sunday, March 8, 2015, Ian Lepore > wrote: > > On Sat, 2015-03-07 at 21:44 -0800, Tim Kientzle wrote: > >> > On Mar 7, 2015, at 12:53 PM, Brett Wynkoop > wrote: > >> > > >> > Greeting- > >> > > >> > So I have been trying since last night to svn up my source tree > on the > >> > BBone with no luck. It seems to never complete and instead produces > >> > the following error: > >> > > >> > A sys/gnu/dts/arm/zynq-zc702.dts > >> > A sys/gnu/dts/arm/imx31-bug.dts > >> > A sys/gnu/dts/arm/ste-href-ab8500.dtsi > >> > svn: E120108: Error retrieving REPORT: The server unexpectedly closed > >> > the connection. > >> > > >> > Is anyone else seeing this issue? > >> > >> Back when I did regular native build worlds, I saw this > >> quite regularly. I was always able to eventually complete > >> an update, but it sometimes took many many iterations of: > >> > >> svnlite cleanup && svnlite up > >> > >> before it could complete. > >> > >> I suspect this is an artifact of SD performance: SVN > >> tries to keep a network connection open while its updating > >> files locally and this leads to server timeouts. > >> > >> I had better luck using git. I think its update strategy > >> does not require keeping a network connection open > >> for such long periods of time. > >> > >> Tim > > > > I was able to checkout via svnlite to both a super-slow usb stick and to > > a reasonably fast sdcard last night. No hint of trouble. > > > > -- Ian > > > > > > _______________________________________________ > > freebsd-arm@freebsd.org mailing list > > http://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 Mar 8 17:10:19 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DBD76582 for ; Sun, 8 Mar 2015 17:10:19 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [IPv6:2001:4f8:3:ffe0:406a:0:50:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BAD89667 for ; Sun, 8 Mar 2015 17:10:19 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [127.0.1.5]) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9) with ESMTP id t28HAJp4059718 for ; Sun, 8 Mar 2015 17:10:19 GMT (envelope-from root@phabric-backend.isc.freebsd.org) Received: (from root@localhost) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9/Submit) id t28HAJ83059717; Sun, 8 Mar 2015 17:10:19 GMT (envelope-from root) Date: Sun, 8 Mar 2015 17:10:19 +0000 To: freebsd-arm@freebsd.org From: "zbb (Zbigniew Bodek)" Subject: [Differential] [Commented On] D2017: Allow to disable alignment faults in the kernel configuration file Message-ID: X-Priority: 3 Thread-Topic: D2017: Allow to disable alignment faults in the kernel configuration file X-Herald-Rules: none X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: In-Reply-To: References: Thread-Index: M2IwYjY0ZDAxMWY3ZTNlM2Y4OWM0M2JjYjUzIFT8gns= X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Mar 2015 17:10:19 -0000 zbb added a comment. There is no other change required. All the code is already there (cpufunc.c). It was simply not possible to enable it through the option in kernel configuration file. REVISION DETAIL https://reviews.freebsd.org/D2017 To: zbb, imp, andrew, ian Cc: freebsd-arm From owner-freebsd-arm@FreeBSD.ORG Sun Mar 8 17:19:52 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 65169626 for ; Sun, 8 Mar 2015 17:19:52 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [IPv6:2001:4f8:3:ffe0:406a:0:50:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3D38178B for ; Sun, 8 Mar 2015 17:19:52 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [127.0.1.5]) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9) with ESMTP id t28HJpDH069520 for ; Sun, 8 Mar 2015 17:19:51 GMT (envelope-from root@phabric-backend.isc.freebsd.org) Received: (from root@localhost) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9/Submit) id t28HJpKN069519; Sun, 8 Mar 2015 17:19:51 GMT (envelope-from root) Date: Sun, 8 Mar 2015 17:19:51 +0000 To: freebsd-arm@freebsd.org From: "ian (Ian Lepore)" Subject: [Differential] [Commented On] D2017: Allow to disable alignment faults in the kernel configuration file Message-ID: <47037bb55056f3c7e7f9340b3e1a6954@localhost.localdomain> X-Priority: 3 Thread-Topic: D2017: Allow to disable alignment faults in the kernel configuration file X-Herald-Rules: none X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: In-Reply-To: References: Thread-Index: M2IwYjY0ZDAxMWY3ZTNlM2Y4OWM0M2JjYjUzIFT8hLc= X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Mar 2015 17:19:52 -0000 ian added a comment. I think if this option is set we may need to notice that and set __NO_STRICT_ALIGNMENT accordingly (I'm not sure how/where that gets set). REVISION DETAIL https://reviews.freebsd.org/D2017 To: zbb, imp, andrew, ian Cc: freebsd-arm From owner-freebsd-arm@FreeBSD.ORG Sun Mar 8 17:31:56 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 237E4927 for ; Sun, 8 Mar 2015 17:31:56 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [IPv6:2001:4f8:3:ffe0:406a:0:50:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EFB7291A for ; Sun, 8 Mar 2015 17:31:55 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [127.0.1.5]) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9) with ESMTP id t28HVrkw084159 for ; Sun, 8 Mar 2015 17:31:53 GMT (envelope-from root@phabric-backend.isc.freebsd.org) Received: (from root@localhost) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9/Submit) id t28HVrWl084158; Sun, 8 Mar 2015 17:31:53 GMT (envelope-from root) Date: Sun, 8 Mar 2015 17:31:53 +0000 To: freebsd-arm@freebsd.org From: "andrew (Andrew Turner)" Subject: [Differential] [Updated] D2017: Allow to disable alignment faults in the kernel configuration file Message-ID: <57e6b3912966d4269762164a5300cafa@localhost.localdomain> X-Priority: 3 Thread-Topic: D2017: Allow to disable alignment faults in the kernel configuration file X-Herald-Rules: none X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: In-Reply-To: References: Thread-Index: M2IwYjY0ZDAxMWY3ZTNlM2Y4OWM0M2JjYjUzIFT8h4k= X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: , MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Mar 2015 17:31:56 -0000 andrew added a comment. I would prefer it, if we do enable this, we do it on all armv6 kernels so we can rely on this in userland. If it's only enabled on some we could see issues where a binaries may or may not work under some kernels depending on if it has unaligned access enabled. REVISION DETAIL https://reviews.freebsd.org/D2017 To: zbb, imp, ian, andrew Cc: freebsd-arm From owner-freebsd-arm@FreeBSD.ORG Sun Mar 8 17:55:31 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A007045B for ; Sun, 8 Mar 2015 17:55:31 +0000 (UTC) Received: from wa3yre.wynn.com (wa3yre.wynn.com [199.89.147.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5A853BF8 for ; Sun, 8 Mar 2015 17:55:31 +0000 (UTC) Received: from ivory.wynn.com (mail.wynn.com [199.89.147.3]) (authenticated bits=0) by wa3yre.wynn.com (8.14.3/8.12.6) with ESMTP id t28HtHNA026684; Sun, 8 Mar 2015 13:55:20 -0400 (EDT) (envelope-from freebsd-arm@wynn.com) Date: Sun, 8 Mar 2015 13:54:51 -0400 From: Brett Wynkoop To: freebsd-arm@freebsd.org Subject: Re: crash on writing usbstick Message-ID: <20150308135451.5b904aba@ivory.wynn.com> In-Reply-To: <1DC8221F-64EA-418C-8CE5-5FFA4F3DBC64@bsdimp.com> References: <20150301041855.5352663e@ivory.wynn.com> <20150301144653.63b38cdf@ivory.wynn.com> <20150301184456.7b5e6487@ivory.wynn.com> <1DC8221F-64EA-418C-8CE5-5FFA4F3DBC64@bsdimp.com> X-Mailer: Claws Mail 3.10.1 (GTK+ 2.24.25; x86_64-apple-darwin10.8.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Mar 2015 17:55:31 -0000 Greeting- Oh what a difference a couple of weeks makes. Last night I rebuilt my kernel to: root@beaglebone /usr/ports 135$ uname -a FreeBSD beaglebone.wynn.com 11.0-CURRENT FreeBSD 11.0-CURRENT #4 r279761: Sat Mar 7 23:14:30 EST 2015 wynkoop@beaglebone.wynn.com:/usr/src/sys/arm/compile/BB-BEW arm root@beaglebone /usr/ports 136$ This morning when I checked the BeagleBone I discovered that my copy of /usr/ports to /export/ports completed! Somewhere the driver issue must have been fixed in the last couple of weeks of commits! I did still bet a bunch of: aintc0: Spurious interrupt detected (0xffffffff) during the operation. A second thing I have noticed with r279671 is that the system seems a bit more responsive during heavy load and sshd seems to respond faster. Now for me to try to break something else! I think the next step will be a USB HUB and checking out USB flash and 802.11 connected at the same time. -Brett -- wynkoop@wynn.com http://prd4.wynn.com/wynkoop/pgp-keys.txt 917-642-6925 The Second Amendment extends, prima facie, to all instruments that constitute bearable arms, even those that were not in existence at the time of the founding. ~ Justice Scalia From owner-freebsd-arm@FreeBSD.ORG Sun Mar 8 19:44:50 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0576D554 for ; Sun, 8 Mar 2015 19:44:50 +0000 (UTC) Received: from mailhost.netlabit.sk (mailhost.netlabit.sk [84.245.65.72]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 91C4FBC2 for ; Sun, 8 Mar 2015 19:44:48 +0000 (UTC) Received: from zeta.dino.sk (fw1.dino.sk [84.245.95.252]) (AUTH: LOGIN milan) by mailhost.netlabit.sk with ESMTPA; Sun, 08 Mar 2015 20:44:38 +0100 id 00DCAA26.54FCA6A6.00000A44 Date: Sun, 8 Mar 2015 20:44:38 +0100 From: Milan Obuch To: freebsd-arm@freebsd.org Subject: Raspberry Pi and PiTFT display - problem with driver Message-ID: <20150308204438.18f403a1@zeta.dino.sk> X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.25; i386-portbld-freebsd10.1) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Mar 2015 19:44:50 -0000 Hi, I am trying to write a driver for PiTFT display, small 320x240 pixel panel with touch screen. From software perspective, there are two devices, touch screen controller with GPIO expander, STMPE610, and TFT display controller/driver, ILI9341. Both are connected via SPI bus, with one GPIO pin for the later. This is where a problem is - I found a way how to use SPI bus to program STMPE610, how to read and write to its register, at present, read chip identification and set/reset GPIO used to control LED backlight. I did it a bit hackish for now, using sysctl, but it is simple to use and works. Definitive aproach should be to create a child device, gpioc, possibly, but it is much more complicated and takes more time to do. ILI9341, on the other side, uses SPI with GPIO, so there is a question how to do this - and, because this GPIO pin is used as 'command byte flag', it is quite vital for proper function. So, first, how can I describe this requirement in FDT? Currently, I just put there simple fragment: spi0 { ili0 { compatible = "st,ili"; spi-chipselect = <0>; }; tsc0 { compatible = "st,stmpe_tc"; spi-chipselect = <1>; }; }; but this does not descibe fact ILI9341 uses one GPIO pin, in case of PiTFT, GPIO 25. It is in some way similar to what gpioiic does, but there is only one parent device, while I have two, spi bus and gpio pin... I need some hint... Second, I need some way to 'acquire' this pin in driver, so it is not possible to change its status with gpioctl, and obtain correct values for use in GPIOBUS_PIN_* calls to set pin's value. Third, it is not yet clear to me how would be the best way to implement this. According the docs, ILI9341 is programmed with series of short data exchanges, with exactly one command byte send to device, being flagged with active DC pin (connected to GPIO 25), followed with short series of bytes being written to device or, in case of status read and similar, being read from device, all with DC pin being inactive. DC is short for 'data/command'. Anybody out there with some hint? I will try to write something working first, which will be surely not nice at the beginning, but it is much easier to change something you know a bit about already... Regards, Milan From owner-freebsd-arm@FreeBSD.ORG Sun Mar 8 20:22:00 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B2F884E7 for ; Sun, 8 Mar 2015 20:22:00 +0000 (UTC) Received: from pmta1.delivery6.ore.mailhop.org (pmta1.delivery6.ore.mailhop.org [54.149.206.185]) by mx1.freebsd.org (Postfix) with ESMTP id 8F091AC for ; Sun, 8 Mar 2015 20:22:00 +0000 (UTC) Received: from smtp4.ore.mailhop.org (172.31.36.112) by pmta1.delivery1.ore.mailhop.org id hvinl020r84b for ; Sun, 8 Mar 2015 20:14:44 +0000 (envelope-from ) Received: from c-73-34-117-227.hsd1.co.comcast.net ([73.34.117.227] helo=ilsoft.org) by smtp4.ore.mailhop.org with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.82) (envelope-from ) id 1YUhbO-0005La-JZ; Sun, 08 Mar 2015 20:15:06 +0000 Received: from revolution.hippie.lan (revolution.hippie.lan [172.22.42.240]) by ilsoft.org (8.14.9/8.14.9) with ESMTP id t28KF52A005729; Sun, 8 Mar 2015 14:15:05 -0600 (MDT) (envelope-from ian@freebsd.org) X-Mail-Handler: DuoCircle Outbound SMTP X-Originating-IP: 73.34.117.227 X-Report-Abuse-To: abuse@duocircle.com (see https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information for abuse reporting information) X-MHO-User: U2FsdGVkX19s79278CGs8KREvLQvJhz1 Message-ID: <1425845705.73796.18.camel@freebsd.org> Subject: Re: crash on writing usbstick From: Ian Lepore To: Brett Wynkoop Date: Sun, 08 Mar 2015 14:15:05 -0600 In-Reply-To: <20150308135451.5b904aba@ivory.wynn.com> References: <20150301041855.5352663e@ivory.wynn.com> <20150301144653.63b38cdf@ivory.wynn.com> <20150301184456.7b5e6487@ivory.wynn.com> <1DC8221F-64EA-418C-8CE5-5FFA4F3DBC64@bsdimp.com> <20150308135451.5b904aba@ivory.wynn.com> Content-Type: text/plain; charset="us-ascii" X-Mailer: Evolution 3.12.10 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Cc: freebsd-arm@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Mar 2015 20:22:00 -0000 On Sun, 2015-03-08 at 13:54 -0400, Brett Wynkoop wrote: > Greeting- > > Oh what a difference a couple of weeks makes. Last night I rebuilt my > kernel to: > > root@beaglebone /usr/ports 135$ uname -a > FreeBSD beaglebone.wynn.com 11.0-CURRENT FreeBSD 11.0-CURRENT #4 > r279761: Sat Mar 7 23:14:30 EST 2015 > wynkoop@beaglebone.wynn.com:/usr/src/sys/arm/compile/BB-BEW arm > root@beaglebone /usr/ports 136$ > > This morning when I checked the BeagleBone I discovered that my copy > of /usr/ports to /export/ports completed! Somewhere the driver issue > must have been fixed in the last couple of weeks of commits! > > I did still bet a bunch of: > > aintc0: Spurious interrupt detected (0xffffffff) > > during the operation. > > A second thing I have noticed with r279671 is that the system seems a > bit more responsive during heavy load and sshd seems to respond faster. > > Now for me to try to break something else! I think the next step will > be a USB HUB and checking out USB flash and 802.11 connected at the same > time. I didn't check in the spurious interrupt fix until late last night. Update your kernel to r279766 to get rid of the messages. (You may still very rarely see one, but it should be on the order of 1 or 2 per day, not hundreds of them.) -- Ian From owner-freebsd-arm@FreeBSD.ORG Sun Mar 8 20:31:14 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AB509815 for ; Sun, 8 Mar 2015 20:31:14 +0000 (UTC) Received: from wa3yre.wynn.com (wa3yre.wynn.com [199.89.147.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 48E411ED for ; Sun, 8 Mar 2015 20:31:13 +0000 (UTC) Received: from ivory.wynn.com (mail.wynn.com [199.89.147.3]) (authenticated bits=0) by wa3yre.wynn.com (8.14.3/8.12.6) with ESMTP id t28KVAwW039408; Sun, 8 Mar 2015 16:31:10 -0400 (EDT) (envelope-from freebsd-arm@wynn.com) Date: Sun, 8 Mar 2015 16:31:09 -0400 From: Brett Wynkoop To: Warner Losh , freebsd-arm@freebsd.org Subject: Re: crash on writing usbstick Message-ID: <20150308163109.43414e47@ivory.wynn.com> In-Reply-To: <42ACB215-0C41-4B7D-A259-D65892515BE2@bsdimp.com> References: <20150301041855.5352663e@ivory.wynn.com> <20150301144653.63b38cdf@ivory.wynn.com> <20150301184456.7b5e6487@ivory.wynn.com> <1DC8221F-64EA-418C-8CE5-5FFA4F3DBC64@bsdimp.com> <20150301203244.55578413@ivory.wynn.com> <20150302214352.5143d72e@ivory.wynn.com> <42ACB215-0C41-4B7D-A259-D65892515BE2@bsdimp.com> X-Mailer: Claws Mail 3.10.1 (GTK+ 2.24.25; x86_64-apple-darwin10.8.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Mar 2015 20:31:14 -0000 Greeting- Looks like I spoke too soon. BeagleBone crashed again on USB Flash I/O. This time I was doing a make package-recursive for tinc after I moved /usr/ports to the flash drive. Backtrace below: db> tr Tracing pid 35864 tid 100094 td 0xc26ef330 db_trace_self() at db_trace_self pc = 0xc0606d90 lr = 0xc0231fb8 (db_stack_trace+0x108) sp = 0xd486e620 fp = 0xd486e638 r10 = 0xc07ebb24 db_stack_trace() at db_stack_trace+0x108 pc = 0xc0231fb8 lr = 0xc0231928 (db_command+0x294) sp = 0xd486e640 fp = 0xd486e6e0 r4 = 0x00000000 r5 = 0x00000000 r6 = 0x00000000 r10 = 0xc07ebb24 db_command() at db_command+0x294 pc = 0xc0231928 lr = 0xc0231684 (db_command_loop+0x74) sp = 0xd486e6e8 fp = 0xd486e6f8 r4 = 0xc0653c6f r5 = 0xc06751b8 r6 = 0xc07ebb10 r7 = 0xc072ba84 r8 = 0xc07861c0 r9 = 0xc07861c4 r10 = 0xd486e8c8 db_command_loop() at db_command_loop+0x74 pc = 0xc0231684 lr = 0xc0234168 (db_trap+0x108) sp = 0xd486e700 fp = 0xd486e820 --More-- r4 = 0x00000000 r5 = 0xc07ebb1c r6 = 0xc07861e8 r10 = 0xd486e8c8 db_trap() at db_trap+0x108 pc = 0xc0234168 lr = 0xc03ddf0c (kdb_trap+0xd4) sp = 0xd486e828 fp = 0xd486e848 r4 = 0x00000000 r5 = 0x00000001 r6 = 0xc07861e8 r7 = 0xc072ba84 kdb_trap() at kdb_trap+0xd4 pc = 0xc03ddf0c lr = 0xc061be78 (undefinedinstruction+0x2c8) sp = 0xd486e850 fp = 0xd486e8c0 r4 = 0x00000000 r5 = 0x00000000 r6 = 0xc061bb00 r7 = 0xe7ffffff r8 = 0xc26ef330 r9 = 0xc03dd7cc r10 = 0xd486e8c8 undefinedinstruction() at undefinedinstruction+0x2c8 pc = 0xc061be78 lr = 0xc06084b0 (exception_exit) sp = 0xd486e8c8 fp = 0xd486e960 r4 = 0xc067520d r5 = 0xd486e9a4 r6 = 0xc0695b73 r7 = 0xc0778718 r8 = 0xc26ef330 r9 = 0xc07edc18 --More-- r10 = 0xc0778580 exception_exit() at exception_exit pc = 0xc06084b0 lr = 0xc03dd7bc (kdb_enter+0x48) sp = 0xd486e958 fp = 0xd486e960 r0 = 0xc07861d4 r1 = 0x00000000 r2 = 0xc0678ec1 r3 = 0x000000aa r4 = 0xc067520d r5 = 0xd486e9a4 r6 = 0xc0695b73 r7 = 0xc0778718 r8 = 0xc26ef330 r9 = 0xc07edc18 r10 = 0xc0778580 r12 = 0x00000000 $a.8() at $a.8 pc = 0xc03dd7d0 lr = 0xc03a31c8 (vpanic+0xd0) sp = 0xd486e968 fp = 0xd486e988 r4 = 0x00000100 r10 = 0xc0778580 vpanic() at vpanic+0xd0 pc = 0xc03a31c8 lr = 0xc03a321c (kproc_shutdown) sp = 0xd486e990 fp = 0xd486e998 r4 = 0xc2449000 r5 = 0xd486eb84 r6 = 0x000528cc r7 = 0xc29a3980 r8 = 0x00000000 r9 = 0x000041ed --More-- r10 = 0xc2449000 kproc_shutdown() at kproc_shutdown pc = 0xc03a321c lr = 0xc0588118 (ffs_nodealloccg) sp = 0xd486e9a0 fp = 0xd486ea30 r4 = 0xd486e9a4 r5 = 0xc2449000 ffs_nodealloccg() at ffs_nodealloccg pc = 0xc0588118 lr = 0xc05cbdf4 (ufs_mkdir+0x6c) sp = 0xd486ea38 fp = 0xd486ebc0 r4 = 0x000041ed r5 = 0xc23f76c0 r6 = 0xd486ed48 r7 = 0xc0587918 r8 = 0x00000000 r9 = 0xc34be880 r10 = 0xd486ec80 ufs_mkdir() at ufs_mkdir+0x6c pc = 0xc05cbdf4 lr = 0xc0633768 (VOP_MKDIR_APV+0x12c) sp = 0xd486ebc8 fp = 0xd486ebe0 r4 = 0xd486ed48 r5 = 0xc075d194 r6 = 0x00000000 r7 = 0x00020594 r8 = 0x00000000 r9 = 0x00000000 r10 = 0xd486ec88 VOP_MKDIR_APV() at VOP_MKDIR_APV+0x12c --More-- pc = 0xc0633768 lr = 0xc045d4a4 (kern_mkdirat+0x194) sp = 0xd486ebe8 fp = 0xd486ed80 r4 = 0xd486ec18 r5 = 0xd486ecb0 r6 = 0xd486ed44 r10 = 0xd486ec88 kern_mkdirat() at kern_mkdirat+0x194 pc = 0xc045d4a4 lr = 0xc045d308 (sys_mkdir+0x24) sp = 0xd486ed88 fp = 0xd486ed90 r4 = 0xc26ef330 r5 = 0x00000000 r6 = 0xc07ed900 r7 = 0x00000000 r8 = 0xd486edf8 r9 = 0xc26d5000 r10 = 0x00013738 sys_mkdir() at sys_mkdir+0x24 pc = 0xc045d308 lr = 0xc061ab00 (swi_handler+0x2e4) sp = 0xd486ed98 fp = 0xd486ee48 swi_handler() at swi_handler+0x2e4 pc = 0xc061ab00 lr = 0xc0608440 (swi_exit) sp = 0xd486ee50 fp = 0xbffff3d0 r4 = 0x0001302a r5 = 0x20854600 r6 = 0x00020de4 r7 = 0x00000088 r8 = 0x00000001 r9 = 0x00020594 --More-- r10 = 0x00013738 swi_exit() at swi_exit pc = 0xc0608440 lr = 0xc0608440 (swi_exit) sp = 0xd486ee50 fp = 0xbffff3d0 db> cont Uptime: 13h20m40s # uname -a FreeBSD 11.0-CURRENT FreeBSD 11.0-CURRENT #4 r279761: Sat Mar 7 23:14:30 EST 2015 wynkoop@beaglebone.wynn.com:/usr/src/sys/arm/compile/BB-BEW arm # So I guess this mystery is not solved yet. -Brett -- wynkoop@wynn.com http://prd4.wynn.com/wynkoop/pgp-keys.txt 917-642-6925 929-272-0000 Amendment I Congress shall make no law respecting an establishment of religion, or prohibiting the free exercise thereof; or abridging the freedom of speech, or of the press; or the right of the people peaceably to assemble, and to petition the government for a redress of grievances. From owner-freebsd-arm@FreeBSD.ORG Sun Mar 8 21:09:09 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A4D26EF1 for ; Sun, 8 Mar 2015 21:09:09 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [IPv6:2001:4f8:3:ffe0:406a:0:50:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7CDC9836 for ; Sun, 8 Mar 2015 21:09:09 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [127.0.1.5]) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9) with ESMTP id t28L99Cr013036 for ; Sun, 8 Mar 2015 21:09:09 GMT (envelope-from root@phabric-backend.isc.freebsd.org) Received: (from root@localhost) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9/Submit) id t28L99L2013035; Sun, 8 Mar 2015 21:09:09 GMT (envelope-from root) Date: Sun, 8 Mar 2015 21:09:09 +0000 To: freebsd-arm@freebsd.org From: "imp (Warner Losh)" Subject: [Differential] [Updated] D2017: Allow to disable alignment faults in the kernel configuration file Message-ID: <3cec6b9b22f43a47f04341ad94bed44c@localhost.localdomain> X-Priority: 3 Thread-Topic: D2017: Allow to disable alignment faults in the kernel configuration file X-Herald-Rules: none X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: In-Reply-To: References: Thread-Index: M2IwYjY0ZDAxMWY3ZTNlM2Y4OWM0M2JjYjUzIFT8unU= X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: , MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Mar 2015 21:09:09 -0000 imp added a comment. >>! In D2017#6, @ian wrote: > I think if this option is set we may need to notice that and set __NO_STRICT_ALIGNMENT accordingly (I'm not sure how/where that gets set). __NO_STRICT_ALIGNMENT gets set in machine/_types.h right now. However, it can not be set based on kernel options because it is shared with user land. It is supposed to describe all users of the architecture. Since we have no clue what kernel will be used, we'd have to assume all or nothing based on, say, the architecture level. I'm not familiar enough with all the implications at the hardware level to know what ARM32_DISABLE_ALIGNMENT_FAULTS would really do, so I can't say if making it default is a good idea or not. REVISION DETAIL https://reviews.freebsd.org/D2017 To: zbb, ian, andrew, imp Cc: freebsd-arm From owner-freebsd-arm@FreeBSD.ORG Mon Mar 9 02:11:45 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1FA8EC65 for ; Mon, 9 Mar 2015 02:11:45 +0000 (UTC) Received: from wa3yre.wynn.com (wa3yre.wynn.com [199.89.147.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B4E989B5 for ; Mon, 9 Mar 2015 02:11:44 +0000 (UTC) Received: from ivory.wynn.com (mail.wynn.com [199.89.147.3]) (authenticated bits=0) by wa3yre.wynn.com (8.14.3/8.12.6) with ESMTP id t292BeRM060802 for ; Sun, 8 Mar 2015 22:11:41 -0400 (EDT) (envelope-from freebsd-arm@wynn.com) Date: Sun, 8 Mar 2015 22:11:39 -0400 From: Brett Wynkoop To: freebsd-arm@freebsd.org Subject: Oddness with GPT labels on boot Message-ID: <20150308221139.687c8f3a@ivory.wynn.com> X-Mailer: Claws Mail 3.10.1 (GTK+ 2.24.25; x86_64-apple-darwin10.8.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Mar 2015 02:11:45 -0000 Greeting- So just updated my kernel sources and now I have this oddness happening: No suitable dump device was found. Starting file system checks: /dev/mmcsd0s2a: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/mmcsd0s2a: clean, 560326 free (12950 frags, 68422 blocks, 0.7% fragmentation) ugen1.2: at usbus1 umass0: on usbus1 umass0: SCSI over Bulk-Only; quirks = 0xc100 umass0:0:0: Attached to scbus0 da0 at umass-sim0 bus 0 scbus0 target 0 lun 0 da0: Removable Direct Access SCSI-5 device da0: Serial Number 4C532000071129119192 da0: 40.000MB/s transfers da0: 15267MB (31266816 512 byte sectors: 255H 63S/T 1946C) da0: quirks=0x2 Can't stat /dev/gpt/bbexport: No such file or directory Can't stat /dev/gpt/bbexport: No such file or directory THE FOLLOWING FILE SYSTEM HAD AN UNEXPECTED INCONSISTENCY: ufs: /dev/gpt/bbexport (/export) Unknown error; help! ERROR: ABORTING BOOT (sending SIGTERM to parent)! Mar 8 22:04:47 init: /bin/sh on /etc/rc terminated abnormally, going to single user mode Enter full pathname of shell or RETURN for /bin/sh: # fsck -p /dev/mmcsd0s2a: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/mmcsd0s2a: clean, 560326 free (12950 frags, 68422 blocks, 0.7% fragmentation) /dev/gpt/bbexport: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/gpt/bbexport: clean, 3375570 free (114 frags, 421932 blocks, 0.0% fragmentation) # Note I did nothing more than run fsck -p as soon as I was at the /bin/sh prompt. # uname -a FreeBSD 11.0-CURRENT FreeBSD 11.0-CURRENT #6 r279797: Sun Mar 8 21:22:04 EDT 2015 wynkoop@beaglebone.wynn.com:/usr/src/sys/arm/compile/BB-BEW arm # Before this kernel I had no problem with the filesystem being checked and mounting at boot. I have not rebuilt world, but I am at a loss as to how that could be the problem. Note above that it said it could not find /dev/gpt/bbexport. I have even put the late param in /etc/fstab for /dev/gpt/bbexport to see if that would help. -Brett -- wynkoop@wynn.com http://prd4.wynn.com/wynkoop/pgp-keys.txt 917-642-6925 929-272-0000 "The strongest reason for the people to retain the right to keep and bear arms is, as a last resort, to protect themselves against tyranny in government" - Thomas Jefferson. From owner-freebsd-arm@FreeBSD.ORG Mon Mar 9 03:24:36 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6872C7E8 for ; Mon, 9 Mar 2015 03:24:36 +0000 (UTC) Received: from mail.egr.msu.edu (boomhauer.egr.msu.edu [35.9.37.167]) by mx1.freebsd.org (Postfix) with ESMTP id 40A491A5 for ; Mon, 9 Mar 2015 03:24:35 +0000 (UTC) Received: from boomhauer (localhost [127.0.0.1]) by mail.egr.msu.edu (Postfix) with ESMTP id 177432B5A1 for ; Sun, 8 Mar 2015 23:14:51 -0400 (EDT) X-Virus-Scanned: amavisd-new at egr.msu.edu Received: from mail.egr.msu.edu ([127.0.0.1]) by boomhauer (boomhauer.egr.msu.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1AC1pDQF6rPt for ; Sun, 8 Mar 2015 23:14:50 -0400 (EDT) Received: from EGR authenticated sender Message-ID: <54FD1029.60500@egr.msu.edu> Date: Sun, 08 Mar 2015 23:14:49 -0400 From: Adam McDougall User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: freebsd-arm@freebsd.org Subject: Re: Oddness with GPT labels on boot References: <20150308221139.687c8f3a@ivory.wynn.com> In-Reply-To: <20150308221139.687c8f3a@ivory.wynn.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Mar 2015 03:24:36 -0000 On 03/08/2015 22:11, Brett Wynkoop wrote: > Greeting- > > So just updated my kernel sources and now I have this oddness happening: > > No suitable dump device was found. > Starting file system checks: > /dev/mmcsd0s2a: FILE SYSTEM CLEAN; SKIPPING CHECKS > /dev/mmcsd0s2a: clean, 560326 free (12950 frags, 68422 blocks, 0.7% > fragmentation) ugen1.2: at usbus1 > umass0: on > usbus1 umass0: SCSI over Bulk-Only; quirks = 0xc100 > umass0:0:0: Attached to scbus0 > da0 at umass-sim0 bus 0 scbus0 target 0 lun 0 > da0: Removable Direct Access SCSI-5 device > da0: Serial Number 4C532000071129119192 > da0: 40.000MB/s transfers > da0: 15267MB (31266816 512 byte sectors: 255H 63S/T 1946C) > da0: quirks=0x2 > Can't stat /dev/gpt/bbexport: No such file or directory > Can't stat /dev/gpt/bbexport: No such file or directory > I have even put the late param in /etc/fstab for /dev/gpt/bbexport to > see if that would help. > > -Brett > I've read all the past emails and wanted to ask about some data points to see if I have any ideas or if someone else will notice something. Apologies if any of these were covered but I tried to look. Can you post the output of: gpart show gpart list cat /etc/fstab mount -v (while /export is mounted) sysctl hw.usb.no_boot_wait cat /var/run/dmesg.boot maybe even sysctl kern.geom.confxml Also I know you probably don't have very much ram at all, but in interest of testing with another filesystem you might try zfs if available. I'm sure it would be unrealistic for production and it might crash if it runs out of ram, but that isn't worse than what you already have and the zfs checksumming might reveal something. Thanks. From owner-freebsd-arm@FreeBSD.ORG Mon Mar 9 04:40:50 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 987A147F for ; Mon, 9 Mar 2015 04:40:50 +0000 (UTC) Received: from wa3yre.wynn.com (wa3yre.wynn.com [199.89.147.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9DBA7A22 for ; Mon, 9 Mar 2015 04:40:49 +0000 (UTC) Received: from ivory.wynn.com (mail.wynn.com [199.89.147.3]) (authenticated bits=0) by wa3yre.wynn.com (8.14.3/8.12.6) with ESMTP id t294ehaG071304; Mon, 9 Mar 2015 00:40:43 -0400 (EDT) (envelope-from freebsd-arm@wynn.com) Date: Mon, 9 Mar 2015 00:40:41 -0400 From: Brett Wynkoop To: Adam McDougall Subject: Re: Oddness with GPT labels on boot Message-ID: <20150309004041.2aa40702@ivory.wynn.com> In-Reply-To: <54FD1029.60500@egr.msu.edu> References: <20150308221139.687c8f3a@ivory.wynn.com> <54FD1029.60500@egr.msu.edu> X-Mailer: Claws Mail 3.10.1 (GTK+ 2.24.25; x86_64-apple-darwin10.8.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-arm@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Mar 2015 04:40:50 -0000 Adam- Here is all you asked for. Can we actually run zfs on ARM? The least ram I have ever used for ZFS without crashing is 512MB but I am willing to try ZFS in my 256MB if it actually builds on ARM. I do not have it linked into my kernel at the moment. I am at the moment doing a make package-recursive of something. When that is done I will try to build a zfs capable kernel. -Brett ---------------------cut here-------------------------------------- => 1 15564799 mmcsd0 MBR (7.4G) 1 62 - free - (31K) 63 4095 1 !12 [active] (2.0M) 4158 15560642 2 freebsd (7.4G) => 0 15560642 mmcsd0s2 BSD (7.4G) 0 66 - free - (33K) 66 15560576 1 freebsd-ufs (7.4G) => 40 31266736 da0 GPT (15G) 40 1048576 1 freebsd-swap (512M) 1048616 30218160 2 freebsd-ufs (14G) Geom name: mmcsd0 modified: false state: OK fwheads: 95 fwsectors: 8192 last: 15564799 first: 1 entries: 4 scheme: MBR Providers: 1. Name: mmcsd0s1 Mediasize: 2096640 (2.0M) Sectorsize: 512 Stripesize: 4194304 Stripeoffset: 32256 Mode: r0w0e0 attrib: active rawtype: 12 length: 2096640 offset: 32256 type: !12 index: 1 end: 4157 start: 63 2. Name: mmcsd0s2 Mediasize: 7967048704 (7.4G) Sectorsize: 512 Stripesize: 4194304 Stripeoffset: 2128896 Mode: r1w1e2 rawtype: 165 length: 7967048704 offset: 2128896 type: freebsd index: 2 end: 15564799 start: 4158 Consumers: 1. Name: mmcsd0 Mediasize: 7969177600 (7.4G) Sectorsize: 512 Stripesize: 4194304 Stripeoffset: 0 Mode: r1w1e3 Geom name: mmcsd0s2 modified: false state: OK fwheads: 95 fwsectors: 8192 last: 15560641 first: 0 entries: 8 scheme: BSD Providers: 1. Name: mmcsd0s2a Mediasize: 7967014912 (7.4G) Sectorsize: 512 Stripesize: 4194304 Stripeoffset: 2162688 Mode: r1w1e1 rawtype: 7 length: 7967014912 offset: 33792 type: freebsd-ufs index: 1 end: 15560641 start: 66 Consumers: 1. Name: mmcsd0s2 Mediasize: 7967048704 (7.4G) Sectorsize: 512 Stripesize: 4194304 Stripeoffset: 2128896 Mode: r1w1e2 Geom name: da0 modified: false state: OK fwheads: 255 fwsectors: 63 last: 31266775 first: 40 entries: 152 scheme: GPT Providers: 1. Name: da0p1 Mediasize: 536870912 (512M) Sectorsize: 512 Stripesize: 0 Stripeoffset: 20480 Mode: r1w1e1 rawuuid: 5ffc3b07-bfd2-11e4-89fc-0018318ca522 rawtype: 516e7cb5-6ecf-11d6-8ff8-00022d09712b label: gpswap length: 536870912 offset: 20480 type: freebsd-swap index: 1 end: 1048615 start: 40 2. Name: da0p2 Mediasize: 15471697920 (14G) Sectorsize: 512 Stripesize: 0 Stripeoffset: 536891392 Mode: r1w1e2 rawuuid: a490c34f-bfd2-11e4-89fc-0018318ca522 rawtype: 516e7cb6-6ecf-11d6-8ff8-00022d09712b label: bbexport length: 15471697920 offset: 536891392 type: freebsd-ufs index: 2 end: 31266775 start: 1048616 Consumers: 1. Name: da0 Mediasize: 16008609792 (15G) Sectorsize: 512 Mode: r2w2e5 /dev/mmcsd0s1 /boot/msdos msdosfs rw,noatime,noauto 0 0 /dev/mmcsd0s2a / ufs rw,noatime 1 1 /dev/gpt/bbexport /export ufs rw,noatime,late 2 2 /dev/gpt/gpswap none swap sw,late 0 0 md /tmp mfs rw,noatime,-s50m 0 0 md /var/log mfs rw,noatime,-s15m 0 0 md /var/tmp mfs rw,noatime,-s12m 0 0 #md none swap sw,file=/usr/swap/0,late 0 0 /dev/mmcsd0s2a on / (ufs, local, noatime, journaled soft-updates, nfsv4acls, writes: sync 6 async 104, reads: sync 3358 async 111, fsid 052cdf5426b39751) devfs on /dev (devfs, local, fsid 00ff007171000000) /dev/md0 on /tmp (ufs, local, noatime, soft-updates, writes: sync 2 async 904, reads: sync 9 async 0, fsid 7804fd5444fdca47) /dev/md1 on /var/log (ufs, local, noatime, soft-updates, writes: sync 6 async 131, reads: sync 10 async 0, fsid 7804fd54cace4448) /dev/md2 on /var/tmp (ufs, local, noatime, soft-updates, writes: sync 17 async 79, reads: sync 9 async 0, fsid 7804fd547c03b487) pid568@beaglebone:/host on /host (nfs, fsid 01ff003a3a000000) pid568@beaglebone:/net on /net (nfs, fsid 02ff003a3a000000) /dev/gpt/bbexport on /export (ufs, local, noatime, writes: sync 67667 async 18545, reads: sync 3713 async 384, fsid 746af5541d2c6cd5) hw.usb.no_boot_wait: 0 KDB: debugger backends: ddb KDB: current backend: ddb Copyright (c) 1992-2015 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 11.0-CURRENT #6 r279797: Sun Mar 8 21:22:04 EDT 2015 wynkoop@beaglebone.wynn.com:/usr/src/sys/arm/compile/BB-BEW arm FreeBSD clang version 3.5.1 (tags/RELEASE_351/final 225668) 20150115 WARNING: WITNESS option enabled, expect reduced performance. CPU: Cortex A8-r3 rev 2 (Cortex-A core) Supported features: ARM_ISA THUMB2 JAZELLE THUMBEE ARMv4 Security_Ext WB disabled EABT branch prediction enabled LoUU:2 LoC:3 LoUIS:1 Cache level 1: 32KB/64B 4-way data cache WT WB Read-Alloc 32KB/64B 4-way instruction cache Read-Alloc Cache level 2: 256KB/64B 8-way unified cache WT WB Read-Alloc Write-Alloc real memory = 268435456 (256 MB) avail memory = 249716736 (238 MB) Texas Instruments AM3358 Processor, Revision ES1.0 random: entropy device infrastructure driver random: selecting highest priority adaptor random: SOFT: yarrow init() random: selecting highest priority adaptor ofwbus0: simplebus0: on ofwbus0 aintc0: mem 0x48200000-0x48200fff on simplebus0 aintc0: Revision 5.0 ti_scm0: mem 0x44e10000-0x44e11fff on simplebus0 am335x_prcm0: mem 0x44e00000-0x44e012ff on simplebus0 am335x_prcm0: Clocks: System 24.0 MHz, CPU 720 MHz am335x_dmtimer0: mem 0x44e05000-0x44e05fff,0x44e31000-0x44e31fff,0x48040000-0x48040fff,0x48042000-0x48042fff,0x48044000-0x48044fff,0x48046000-0x48046fff,0x48048000-0x48048fff,0x4804a000-0x4804afff irq 66,67,68,69,92,93,94,95 on simplebus0 Timecounter "AM335x Timecounter" frequency 24000000 Hz quality 1000 Event timer "AM335x Eventtimer" frequency 24000000 Hz quality 1000 am335x_rtc0: mem 0x44e3e000-0x44e3efff irq 75,76 on simplebus0 am335x_rtc0: AM335X RTC v1.0.6 ti_adc0: mem 0x44e0d000-0x44e0efff irq 16 on simplebus0 ti_adc0: scheme: 0x1 func: 0x730 rtl: 0 rev: 0.1 custom rev: 0 ti_wdt0: mem 0x44e35000-0x44e35fff irq 91 on simplebus0 gpio0: mem 0x44e07000-0x44e07fff,0x4804c000-0x4804cfff,0x481ac000-0x481acfff,0x481ae000-0x481aefff irq 96,97,98,99,32,33,62,63 on simplebus0 gpiobus0: on gpio0 gpioc0: on gpio0 uart0: mem 0x44e09000-0x44e09fff irq 72 on simplebus0 uart0: console (115384,n,8,1) ti_edma30: mem 0x49000000-0x490fffff,0x49800000-0x498fffff,0x49900000-0x499fffff,0x49a00000-0x49afffff irq 12,13,14 on simplebus0 ti_edma30: EDMA revision 40014c00 sdhci_ti0: mem 0x48060000-0x48060fff irq 64 on simplebus0 mmc0: on sdhci_ti0 cpsw0: <3-port Switch Ethernet Subsystem> mem 0x4a100000-0x4a103fff irq 40,41,42,43 on simplebus0 cpsw0: CPSW SS Version 1.12 (0) cpsw0: Initial queue size TX=128 RX=384 miibus0: on cpsw0 smscphy0: PHY 0 on miibus0 smscphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto cpsw0: Ethernet address: 00:18:31:8c:a5:22 iichb0: mem 0x44e0b000-0x44e0bfff irq 70 on simplebus0 iichb0: I2C revision 4.0 FIFO size: 32 bytes iicbus0: on iichb0 iic0: on iicbus0 am335x_pmic0: at addr 0x48 on iicbus0 iichb1: mem 0x4802a000-0x4802afff irq 71 on simplebus0 iichb1: I2C revision 4.0 FIFO size: 32 bytes iicbus1: on iichb1 iic1: on iicbus1 iichb2: mem 0x4819c000-0x4819cfff irq 30 on simplebus0 iichb2: I2C revision 4.0 FIFO size: 32 bytes iicbus2: on iichb2 iic2: on iicbus2 am335x_pwm0: mem 0x48300000-0x483000ff,0x48300100-0x4830017f,0x48300180-0x483001ff,0x48300200-0x4830025f irq 86,58 on simplebus0 am335x_pwm1: mem 0x48302000-0x483020ff,0x48302100-0x4830217f,0x48302180-0x483021ff,0x48302200-0x4830225f irq 87,59 on simplebus0 am335x_pwm2: mem 0x48304000-0x483040ff,0x48304100-0x4830417f,0x48304180-0x483041ff,0x48304200-0x4830425f irq 88,60 on simplebus0 musbotg0: mem 0x47400000-0x47400fff,0x47401000-0x474012ff,0x47401300-0x474013ff,0x47401400-0x474017ff,0x47401800-0x47401aff,0x47401b00-0x47401bff,0x47401c00-0x47401fff irq 17,18,19 on simplebus0 musbotg0: TI AM335X USBSS v0.0.13 usbus0: Dynamic FIFO sizing detected, assuming 16Kbytes of FIFO RAM usbus0 on musbotg0 usbus1: Dynamic FIFO sizing detected, assuming 16Kbytes of FIFO RAM usbus1 on musbotg0 ti_pruss0: mem 0x4a300000-0x4a37ffff irq 20,21,22,23,24,25,26,27 on simplebus0 ti_pruss0: AM33xx PRU-ICSS Timecounters tick every 10.000 msec usbus0: 480Mbps High Speed USB v2.0 usbus1: 480Mbps High Speed USB v2.0 ugen0.1: at usbus0 uhub0: on usbus0 ugen1.1: at usbus1 uhub1: on usbus1 mmcsd0: 8GB at mmc0 48.0MHz/4bit/65535-block am335x_pmic0: TPS65217B ver 1.1 powered by USB and AC random: unblocking device. WARNING: WITNESS option enabled, expect reduced performance. Root mount waiting for: usbus1 usbus0 uhub0: 1 port with 1 removable, self powered uhub1: 1 port with 1 removable, self powered Trying to mount root from ufs:/dev/mmcsd0s2a [rw,noatime]... warning: no time-of-day clock registered, system time will not be set accurately ugen0.2: at usbus0 ustorage_fs0: on usbus0 ugen1.2: at usbus1 umass0: on usbus1 umass0: SCSI over Bulk-Only; quirks = 0xc100 umass0:0:0: Attached to scbus0 da0 at umass-sim0 bus 0 scbus0 target 0 lun 0 da0: Removable Direct Access SCSI-5 device da0: Serial Number 4C532000071129119192 da0: 40.000MB/s transfers da0: 15267MB (31266816 512 byte sectors: 255H 63S/T 1946C) da0: quirks=0x2 lock order reversal: 1st 0xc1e96934 ufs (ufs) @ kern/vfs_subr.c:2176 2nd 0xc102fbe0 bufwait (bufwait) @ ufs/ffs/ffs_vnops.c:263 3rd 0xc25446f4 ufs (ufs) @ kern/vfs_subr.c:2176 KDB: stack backtrace: lock order reversal: (sleepable after non-sleepable) 1st 0xc2544714 vnode interlock (vnode interlock) @ kern/vfs_hash.c:87 2nd 0xc0776e70 kernel linker (kernel linker) @ kern/kern_linker.c:552 KDB: stack backtrace: db_trace_self() at db_trace_self pc = 0xc0606d90 lr = 0xc0234004 (db_trace_self_wrapper+0x30) sp = 0xd51b0118 fp = 0xd51b0230 r10 = 0xc0665575 db_trace_self_wrapper() at db_trace_self_wrapper+0x30 pc = 0xc0234004 lr = 0xc03fe194 (witness_checkorder+0xf4c) sp = 0xd51b0238 fp = 0xd51b0288 r4 = 0xc0670ee2 r5 = 0xc0776e70 r6 = 0xc0670afe r7 = 0xc0670afb witness_checkorder() at witness_checkorder+0xf4c pc = 0xc03fe194 lr = 0xc03aab38 (_sx_xlock+0x80) sp = 0xd51b0290 fp = 0xd51b02c0 r4 = 0x00000228 r5 = 0xc0670af2 r6 = 0xc0776e80 r7 = 0xc0776e70 r8 = 0x00000000 r9 = 0xc06a23a1 r10 = 0xc0665575 _sx_xlock() at _sx_xlock+0x80 pc = 0xc03aab38 lr = 0xc03810e8 (linker_file_foreach+0x34) sp = 0xd51b02c8 fp = 0xd51b02e0 r4 = 0xc0776e50 r5 = 0xd51b02e8 r6 = 0xc061c378 r7 = 0xc0606d90 r8 = 0xc0776e70 r10 = 0xc0665575 linker_file_foreach() at linker_file_foreach+0x34 pc = 0xc03810e8 lr = 0xc061bf88 (unwind_stack_one+0x5c) sp = 0xd51b02e8 fp = 0xd51b0310 r4 = 0xd51b0350 r5 = 0xd51b02e8 r6 = 0x00000000 r7 = 0xc0606d90 r8 = 0xc0725120 r10 = 0xc0665575 unwind_stack_one() at unwind_stack_one+0x5c pc = 0xc061bf88 lr = 0xc0606c28 (db_stack_trace_cmd+0x38) sp = 0xd51b0318 fp = 0xd51b0348 r4 = 0xd51b0350 r5 = 0xc068509e r6 = 0x00000000 r7 = 0xc06751c8 r8 = 0xc07b812c r9 = 0xc06a23a1 r10 = 0xc0665575 db_stack_trace_cmd() at db_stack_trace_cmd+0x38 pc = 0xc0606c28 lr = 0xc0606dc0 (db_trace_self+0x30) sp = 0xd51b0350 fp = 0xd51b03a8 r4 = 0x00000000 r5 = 0xd51b03b0 r6 = 0xc06851de r7 = 0xc0665575 r8 = 0xc07b812c r9 = 0xc102fbe0 r10 = 0xc0665575 db_trace_self() at db_trace_self+0x30 pc = 0xc0606dc0 lr = 0xc0234004 (db_trace_self_wrapper+0x30) sp = 0xd51b03b0 fp = 0xd51b04c8 r10 = 0xc0665575 db_trace_self_wrapper() at db_trace_self_wrapper+0x30 pc = 0xc0234004 lr = 0xc03fe194 (witness_checkorder+0xf4c) sp = 0xd51b04d0 fp = 0xd51b0520 r4 = 0xc0665c93 r5 = 0xc25446f4 r6 = 0xc06851de r7 = 0xc0665575 witness_checkorder() at witness_checkorder+0xf4c pc = 0xc03fe194 lr = 0xc0384ba4 (__lockmgr_args+0x838) sp = 0xd51b0528 fp = 0xd51b0590 r4 = 0xc06851d2 r5 = 0xc0665c93 r6 = 0xc25446f4 r7 = 0x00000100 r8 = 0xc2544714 r9 = 0x00080100 r10 = 0x00080000 __lockmgr_args() at __lockmgr_args+0x838 pc = 0xc0384ba4 lr = 0xc05bb050 (ffs_lock+0x80) sp = 0xd51b0598 fp = 0xd51b05c8 r4 = 0xd51b05f0 r5 = 0x00080100 r6 = 0xc25446c0 r7 = 0xc25446f4 r8 = 0xc2544714 r9 = 0x00000000 r10 = 0x00000008 ffs_lock() at ffs_lock+0x80 pc = 0xc05bb050 lr = 0xc06342ac (VOP_LOCK1_APV+0x128) sp = 0xd51b05d0 fp = 0xd51b05e8 r4 = 0xd51b05f0 r5 = 0xc075cc30 r6 = 0x00000000 r7 = 0x00080100 r8 = 0xd51b05f0 r9 = 0x00000000 r10 = 0x00000880 VOP_LOCK1_APV() at VOP_LOCK1_APV+0x128 pc = 0xc06342ac lr = 0xc0460604 (_vn_lock+0x48) sp = 0xd51b05f0 fp = 0xd51b0620 r4 = 0xc25446c0 r5 = 0x00007535 r6 = 0xc06851d2 r10 = 0x00000880 _vn_lock() at _vn_lock+0x48 pc = 0xc0460604 lr = 0xc04511b4 (vget+0x60) sp = 0xd51b0628 fp = 0xd51b0648 r4 = 0xc25446c0 r5 = 0x00007535 r6 = 0x00080100 r7 = 0xc07e335c r8 = 0xc1f56330 r9 = 0x00000000 r10 = 0xc07e3340 vget() at vget+0x60 pc = 0xc04511b4 lr = 0xc0445294 (vfs_hash_get+0xe0) sp = 0xd51b0650 fp = 0xd51b0680 r4 = 0xc0684424 r5 = 0x00007535 r6 = 0xc1f742b0 r7 = 0xc07e335c r8 = 0xc25446c0 r10 = 0xc07e3340 vfs_hash_get() at vfs_hash_get+0xe0 pc = 0xc0445294 lr = 0xc05b6224 (ffs_vgetf+0x38) sp = 0xd51b0688 fp = 0xd51b06d8 r4 = 0x00007535 r5 = 0x00080000 r6 = 0xc1f742b0 r7 = 0x00007535 r8 = 0xc1e49c00 r9 = 0xc240b130 r10 = 0xd51b0738 ffs_vgetf() at ffs_vgetf+0x38 pc = 0xc05b6224 lr = 0xc05ad454 (softdep_sync_buf+0x970) sp = 0xd51b06e0 fp = 0xd51b0758 r4 = 0x00007535 r5 = 0xc1042d60 r6 = 0x00000000 r7 = 0xc1f7f900 r8 = 0xc1e49c00 r9 = 0xc240b130 r10 = 0xc0696daa softdep_sync_buf() at softdep_sync_buf+0x970 pc = 0xc05ad454 lr = 0xc05bbd3c (ffs_syncvnode+0x2f4) sp = 0xd51b0760 fp = 0xd51b07b0 r4 = 0xc069ab7b r5 = 0xc1e96900 r6 = 0x00000000 r7 = 0x00000001 r8 = 0xc102fbe0 r9 = 0xc102fb90 r10 = 0x00000010 ffs_syncvnode() at ffs_syncvnode+0x2f4 pc = 0xc05bbd3c lr = 0xc0590984 (ffs_truncate+0x754) sp = 0xd51b07b8 fp = 0xd51b0968 r4 = 0xc1e96900 r5 = 0x00000200 r6 = 0xc1f85780 r7 = 0x00000000 r8 = 0xc1f857d8 r9 = 0x00000000 r10 = 0xc1f81000 ffs_truncate() at ffs_truncate+0x754 pc = 0xc0590984 lr = 0xc05c38e4 (ufs_direnter+0x82c) sp = 0xd51b0970 fp = 0xd51b09d8 r4 = 0xc1e96900 r5 = 0xc1e96900 r6 = 0xc1f85780 r7 = 0xc25446c0 r8 = 0x00000000 r9 = 0x00000014 r10 = 0xd51b0a00 ufs_direnter() at ufs_direnter+0x82c pc = 0xc05c38e4 lr = 0xc05cd2a8 (ufs_makeinode+0x498) sp = 0xd51b09e0 fp = 0xd51b0b40 r4 = 0xc1e96900 r5 = 0xd51b0a00 r6 = 0x000081a4 r7 = 0x00000000 r8 = 0xd51b0d08 r9 = 0xc2495e00 r10 = 0xd51b0d20 ufs_makeinode() at ufs_makeinode+0x498 pc = 0xc05cd2a8 lr = 0xc05c9214 (ufs_create+0x34) sp = 0xd51b0b48 fp = 0xd51b0b58 r4 = 0xd51b0c38 r5 = 0x00008000 r6 = 0x00000000 r7 = 0x00000602 r8 = 0x00000000 r9 = 0x00000000 r10 = 0xd51b0d28 ufs_create() at ufs_create+0x34 pc = 0xc05c9214 lr = 0xc0631700 (VOP_CREATE_APV+0x12c) sp = 0xd51b0b60 fp = 0xd51b0b78 r4 = 0xd51b0c38 r5 = 0xc075d194 VOP_CREATE_APV() at VOP_CREATE_APV+0x12c pc = 0xc0631700 lr = 0xc045fee0 (vn_open_cred+0x234) sp = 0xd51b0b80 fp = 0xd51b0c68 r4 = 0xd51b0cb8 r5 = 0xd51b0d08 r6 = 0x00000000 r10 = 0xd51b0d28 vn_open_cred() at vn_open_cred+0x234 pc = 0xc045fee0 lr = 0xc045fca4 (vn_open+0x24) sp = 0xd51b0c70 fp = 0xd51b0c78 r4 = 0xc1f56330 r5 = 0x000500cf r6 = 0x00000012 r7 = 0xd51b0cb8 r8 = 0x00000000 r9 = 0x2082c810 r10 = 0x000001b6 vn_open() at vn_open+0x24 pc = 0xc045fca4 lr = 0xc045930c (kern_openat+0x248) sp = 0xd51b0c80 fp = 0xd51b0d80 kern_openat() at kern_openat+0x248 pc = 0xc045930c lr = 0xc04595d4 (sys_openat+0x2c) sp = 0xd51b0d88 fp = 0xd51b0d90 r4 = 0xc1f56330 r5 = 0x00000000 r6 = 0xc07ed900 r7 = 0x00000000 r8 = 0xd51b0df8 r9 = 0xc1f5d378 r10 = 0x00000001 sys_openat() at sys_openat+0x2c pc = 0xc04595d4 lr = 0xc061ab00 (swi_handler+0x2e4) sp = 0xd51b0d98 fp = 0xd51b0e48 swi_handler() at swi_handler+0x2e4 pc = 0xc061ab00 lr = 0xc0608440 (swi_exit) sp = 0xd51b0e50 fp = 0xbfffe738 r4 = 0x2083c584 r5 = 0x2080f3d0 r6 = 0x2082c810 r7 = 0x000001f3 r8 = 0xbfffe754 r9 = 0x000319e8 r10 = 0x00000001 swi_exit() at swi_exit pc = 0xc0608440 lr = 0xc0608440 (swi_exit) sp = 0xd51b0e50 fp = 0xbfffe738 db_trace_self() at db_trace_self pc = 0xc0606d90 lr = 0xc0234004 (db_trace_self_wrapper+0x30) sp = 0xd51b03b0 fp = 0xd51b04c8 r10 = 0xc0665575 db_trace_self_wrapper() at db_trace_self_wrapper+0x30 pc = 0xc0234004 lr = 0xc03fe194 (witness_checkorder+0xf4c) sp = 0xd51b04d0 fp = 0xd51b0520 r4 = 0xc0665c93 r5 = 0xc25446f4 r6 = 0xc06851de r7 = 0xc0665575 witness_checkorder() at witness_checkorder+0xf4c pc = 0xc03fe194 lr = 0xc0384ba4 (__lockmgr_args+0x838) sp = 0xd51b0528 fp = 0xd51b0590 r4 = 0xc06851d2 r5 = 0xc0665c93 r6 = 0xc25446f4 r7 = 0x00000100 r8 = 0xc2544714 r9 = 0x00080100 r10 = 0x00080000 __lockmgr_args() at __lockmgr_args+0x838 pc = 0xc0384ba4 lr = 0xc05bb050 (ffs_lock+0x80) sp = 0xd51b0598 fp = 0xd51b05c8 r4 = 0xd51b05f0 r5 = 0x00080100 r6 = 0xc25446c0 r7 = 0xc25446f4 r8 = 0xc2544714 r9 = 0x00000000 r10 = 0x00000008 ffs_lock() at ffs_lock+0x80 pc = 0xc05bb050 lr = 0xc06342ac (VOP_LOCK1_APV+0x128) sp = 0xd51b05d0 fp = 0xd51b05e8 r4 = 0xd51b05f0 r5 = 0xc075cc30 r6 = 0x00000000 r7 = 0x00080100 r8 = 0xd51b05f0 r9 = 0x00000000 r10 = 0x00000880 VOP_LOCK1_APV() at VOP_LOCK1_APV+0x128 pc = 0xc06342ac lr = 0xc0460604 (_vn_lock+0x48) sp = 0xd51b05f0 fp = 0xd51b0620 r4 = 0xc25446c0 r5 = 0x00007535 r6 = 0xc06851d2 r10 = 0x00000880 _vn_lock() at _vn_lock+0x48 pc = 0xc0460604 lr = 0xc04511b4 (vget+0x60) sp = 0xd51b0628 fp = 0xd51b0648 r4 = 0xc25446c0 r5 = 0x00007535 r6 = 0x00080100 r7 = 0xc07e335c r8 = 0xc1f56330 r9 = 0x00000000 r10 = 0xc07e3340 vget() at vget+0x60 pc = 0xc04511b4 lr = 0xc0445294 (vfs_hash_get+0xe0) sp = 0xd51b0650 fp = 0xd51b0680 r4 = 0xc0684424 r5 = 0x00007535 r6 = 0xc1f742b0 r7 = 0xc07e335c r8 = 0xc25446c0 r10 = 0xc07e3340 vfs_hash_get() at vfs_hash_get+0xe0 pc = 0xc0445294 lr = 0xc05b6224 (ffs_vgetf+0x38) sp = 0xd51b0688 fp = 0xd51b06d8 r4 = 0x00007535 r5 = 0x00080000 r6 = 0xc1f742b0 r7 = 0x00007535 r8 = 0xc1e49c00 r9 = 0xc240b130 r10 = 0xd51b0738 ffs_vgetf() at ffs_vgetf+0x38 pc = 0xc05b6224 lr = 0xc05ad454 (softdep_sync_buf+0x970) sp = 0xd51b06e0 fp = 0xd51b0758 r4 = 0x00007535 r5 = 0xc1042d60 r6 = 0x00000000 r7 = 0xc1f7f900 r8 = 0xc1e49c00 r9 = 0xc240b130 r10 = 0xc0696daa softdep_sync_buf() at softdep_sync_buf+0x970 pc = 0xc05ad454 lr = 0xc05bbd3c (ffs_syncvnode+0x2f4) sp = 0xd51b0760 fp = 0xd51b07b0 r4 = 0xc069ab7b r5 = 0xc1e96900 r6 = 0x00000000 r7 = 0x00000001 r8 = 0xc102fbe0 r9 = 0xc102fb90 r10 = 0x00000010 ffs_syncvnode() at ffs_syncvnode+0x2f4 pc = 0xc05bbd3c lr = 0xc0590984 (ffs_truncate+0x754) sp = 0xd51b07b8 fp = 0xd51b0968 r4 = 0xc1e96900 r5 = 0x00000200 r6 = 0xc1f85780 r7 = 0x00000000 r8 = 0xc1f857d8 r9 = 0x00000000 r10 = 0xc1f81000 ffs_truncate() at ffs_truncate+0x754 pc = 0xc0590984 lr = 0xc05c38e4 (ufs_direnter+0x82c) sp = 0xd51b0970 fp = 0xd51b09d8 r4 = 0xc1e96900 r5 = 0xc1e96900 r6 = 0xc1f85780 r7 = 0xc25446c0 r8 = 0x00000000 r9 = 0x00000014 r10 = 0xd51b0a00 ufs_direnter() at ufs_direnter+0x82c pc = 0xc05c38e4 lr = 0xc05cd2a8 (ufs_makeinode+0x498) sp = 0xd51b09e0 fp = 0xd51b0b40 r4 = 0xc1e96900 r5 = 0xd51b0a00 r6 = 0x000081a4 r7 = 0x00000000 r8 = 0xd51b0d08 r9 = 0xc2495e00 r10 = 0xd51b0d20 ufs_makeinode() at ufs_makeinode+0x498 pc = 0xc05cd2a8 lr = 0xc05c9214 (ufs_create+0x34) sp = 0xd51b0b48 fp = 0xd51b0b58 r4 = 0xd51b0c38 r5 = 0x00008000 r6 = 0x00000000 r7 = 0x00000602 r8 = 0x00000000 r9 = 0x00000000 r10 = 0xd51b0d28 ufs_create() at ufs_create+0x34 pc = 0xc05c9214 lr = 0xc0631700 (VOP_CREATE_APV+0x12c) sp = 0xd51b0b60 fp = 0xd51b0b78 r4 = 0xd51b0c38 r5 = 0xc075d194 VOP_CREATE_APV() at VOP_CREATE_APV+0x12c pc = 0xc0631700 lr = 0xc045fee0 (vn_open_cred+0x234) sp = 0xd51b0b80 fp = 0xd51b0c68 r4 = 0xd51b0cb8 r5 = 0xd51b0d08 r6 = 0x00000000 r10 = 0xd51b0d28 vn_open_cred() at vn_open_cred+0x234 pc = 0xc045fee0 lr = 0xc045fca4 (vn_open+0x24) sp = 0xd51b0c70 fp = 0xd51b0c78 r4 = 0xc1f56330 r5 = 0x000500cf r6 = 0x00000012 r7 = 0xd51b0cb8 r8 = 0x00000000 r9 = 0x2082c810 r10 = 0x000001b6 vn_open() at vn_open+0x24 pc = 0xc045fca4 lr = 0xc045930c (kern_openat+0x248) sp = 0xd51b0c80 fp = 0xd51b0d80 kern_openat() at kern_openat+0x248 pc = 0xc045930c lr = 0xc04595d4 (sys_openat+0x2c) sp = 0xd51b0d88 fp = 0xd51b0d90 r4 = 0xc1f56330 r5 = 0x00000000 r6 = 0xc07ed900 r7 = 0x00000000 r8 = 0xd51b0df8 r9 = 0xc1f5d378 r10 = 0x00000001 sys_openat() at sys_openat+0x2c pc = 0xc04595d4 lr = 0xc061ab00 (swi_handler+0x2e4) sp = 0xd51b0d98 fp = 0xd51b0e48 swi_handler() at swi_handler+0x2e4 pc = 0xc061ab00 lr = 0xc0608440 (swi_exit) sp = 0xd51b0e50 fp = 0xbfffe738 r4 = 0x2083c584 r5 = 0x2080f3d0 r6 = 0x2082c810 r7 = 0x000001f3 r8 = 0xbfffe754 r9 = 0x000319e8 r10 = 0x00000001 swi_exit() at swi_exit pc = 0xc0608440 lr = 0xc0608440 (swi_exit) sp = 0xd51b0e50 fp = 0xbfffe738 kern.geom.confxml: RAID PART da0 2 GPT 152 40 31266775 63 255 OK false r2w2e5 r1w1e2 da0p2 15471697920 512 0 536891392 1048616 31266775 2 freebsd-ufs 536891392 15471697920 516e7cb6-6ecf-11d6-8ff8-00022d09712b a490c34f-bfd2-11e4-89fc-0018318ca522 r1w1e1 da0p1 536870912 512 0 20480 40 1048615 1 freebsd-swap 20480 536870912 516e7cb5-6ecf-11d6-8ff8-00022d09712b 5ffc3b07-bfd2-11e4-89fc-0018318ca522 mmcsd0s2 3 BSD 8 0 15560641 8192 95 OK false r1w1e2 r1w1e1 mmcsd0s2a 7967014912 512 4194304 2162688 66 15560641 1 freebsd-ufs 33792 7967014912 7 mmcsd0 2 MBR 4 1 15564799 8192 95 OK false r1w1e3 r1w1e2 mmcsd0s2 7967048704 512 4194304 2128896 4158 15564799 2 freebsd 2128896 7967048704 165 r0w0e0 mmcsd0s1 2096640 512 4194304 32256 63 4157 1 !12 32256 2096640 12 active SWAP swap 4 r1w1e0 LABEL da0p2 3 r1w1e2 r1w1e1 gpt/bbexport 15471697920 512 0 536891392 0 15471697920 30218160 0 0 da0p1 3 r1w1e1 r1w1e0 gpt/gpswap 536870912 512 0 20480 0 536870912 1048576 0 0 mmcsd0s1 3 r0w0e0 r0w0e0 msdosfs/BOOT 2096640 512 4194304 32256 0 2096640 4095 0 0 VFS ffs.gpt/bbexport 4 r1w1e1 ffs.md2 2 r1w1e1 ffs.md1 2 r1w1e1 ffs.md0 2 r1w1e1 ffs.mmcsd0s2a 4 r1w1e1 DISK da0 1 r2w2e5 da0 16008609792 512 0 0 255 63 4C532000071129119192 Staples 4C532000071129119192 Staples 4C532000071129119192 Staples mmcsd0 1 r1w1e3 mmcsd0 7969177600 512 4194304 0 95 8192 DA4A6E0B SDHC SD08G 3.0 SN DA4A6E0B MFG 09/2013 by 39 PH DEV md2 2 r0w0e0 md1 2 r0w0e0 md0 2 r0w0e0 gpt/bbexport 4 r0w0e0 gpt/gpswap 4 r0w0e0 da0p2 3 r0w0e0 da0p1 3 r0w0e0 da0 2 r0w0e0 mmcsd0s2a 4 r0w0e0 msdosfs/BOOT 4 r0w0e0 mmcsd0s2 3 r0w0e0 mmcsd0s1 3 r0w0e0 mmcsd0 2 r0w0e0 MD md2 1 r1w1e1 md2 12582912 512 0 0 2 512 0 0 12582912 off read-write swap md1 1 r1w1e1 md1 15728640 512 0 0 1 512 0 0 15728640 off read-write swap md0 1 r1w1e1 md0 52428800 512 0 0 0 512 0 0 52428800 off read-write swap ----------------------------cut here------------------ -- wynkoop@wynn.com http://prd4.wynn.com/wynkoop/pgp-keys.txt 917-642-6925 929-272-0000 A free people ought to be armed. - George Washington From owner-freebsd-arm@FreeBSD.ORG Mon Mar 9 09:57:47 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4485FB18 for ; Mon, 9 Mar 2015 09:57:47 +0000 (UTC) Received: from nm21-vm3.bullet.mail.ne1.yahoo.com (nm21-vm3.bullet.mail.ne1.yahoo.com [98.138.91.151]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id F3D01E21 for ; Mon, 9 Mar 2015 09:57:46 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1425894949; bh=bNf/Akt2DS2iAbRtvKAup5phz0FH6RDtJ8bqA5iVUd0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject; b=GBcq65fzB9lWQrDze6koLPqXkR3r7fJnkseWAV+7FGSq031Tgp+CruZL6HH10tTLxAhlB8W0uXFhswxf1Aq6NoeuYRwqrK5KTbKCO6mA2JMbobtaXrq4w93cBy4idP9NZzU8so4E8X2RuJQegNpIoHn7oCwbm905zdPQpGLOAeM/Q+DAwxvUkswh+sBH1aKunzb7urMaEe6JM1pm+03CCnfDuNK33STkzAp/ugmBr2fERolGSZtuZT0Vj8ySy8pmIFuUOXPO5OFakMFYDCuXXcQrz8FC+z4lnCtwlG42F6BVypSJMfP2B9/n5ziuLZcZKbAG66RzF+B1pY2AaFFV5w== Received: from [98.138.226.177] by nm21.bullet.mail.ne1.yahoo.com with NNFMP; 09 Mar 2015 09:55:49 -0000 Received: from [98.138.89.171] by tm12.bullet.mail.ne1.yahoo.com with NNFMP; 09 Mar 2015 09:55:49 -0000 Received: from [127.0.0.1] by omp1027.mail.ne1.yahoo.com with NNFMP; 09 Mar 2015 09:55:49 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 355840.55809.bm@omp1027.mail.ne1.yahoo.com X-YMail-OSG: lv5vA8IVM1kIqy25YIpIqIdh8TZoVELTGaHmhdOQKJjp8jwgEbsQnat1AqVQgOf 5EtjZi0KITSNsaW2XNYpz9CCF2gcDEFRYqvTmjJZgey_PvRpoP1qzzpIo76cxbFjjeW84dTqUd_x 2I51mUIqq07zwrpJx29lsWRSO7Q1xNy4IZcoq97uKSt7EZGe8tic0BzTGKZ.HHI_pFBxfs9IS.1k QyE556S9COY4s74tXnsT.fExgOAAn1y.y52LKxSGNLyJL.y8kbNKHRFkh3JrYj7qkhYLnNU882P4 DxgXbIZmRgsMB_DoEAmmYS4fPVRGCL5pCRYcruizfYmvZ4Jm9GM7faJRcc2OpzkpeC3Ubmmq5_XM FHRSdT57PxBQnvOpcYuviuutgcgwh5nTnRVFNAdL2E3oGWVdQ1XbVH6KcVFt2cV9izTNLIp.qHjx 7sSVzkw2OXMNM1gTrfmLbLj_K.oIVHH_fwj9HPhHCf7eLTOL_IHKsAaH22Yoeb8xcF9sIxg5S3tu PQPQD Received: by 98.138.105.197; Mon, 09 Mar 2015 09:55:48 +0000 Date: Mon, 9 Mar 2015 09:55:48 +0000 (UTC) From: Ji-Haw Foo Reply-To: Ji-Haw Foo To: =?UTF-8?Q?Mika=C3=ABl_Urankar?= Message-ID: <686713608.847728.1425894948596.JavaMail.yahoo@mail.yahoo.com> In-Reply-To: References: Subject: Re: porting node to Pi MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-arm@freebsd.org" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Mar 2015 09:57:47 -0000 Sorry for the delay. Love to unblock node for FreeB+Pi!=20 On Monday, March 2, 2015 1:36 AM, Mika=C3=ABl Urankar wrote: =20 2015-03-02 10:14 GMT+01:00 Ji-Haw Foo : > Would you know what's missing in FreeBSD that stops 0.12.x from working? = I > have 0.12.x on Debian on Pi. Ok, I've made a mistake in my previous statement. I will have a look at www/node later today, do you want to help? From owner-freebsd-arm@FreeBSD.ORG Mon Mar 9 09:58:21 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1D703B63 for ; Mon, 9 Mar 2015 09:58:21 +0000 (UTC) Received: from nm5-vm4.bullet.mail.gq1.yahoo.com (nm5-vm4.bullet.mail.gq1.yahoo.com [98.136.218.179]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DC48DE29 for ; Mon, 9 Mar 2015 09:58:20 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1425894999; bh=2HQvEcQhM2nHJJXdfdx7CZPsUpBUNz/7csKD6Ngni+Q=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject; b=H93ORkVZI61d9b+wmt13RO/+N819rOZ4IoF9i2pK88/Zrx48SvzXe4m5+LuzprA+gy/I1H2aS4IflnfOFCYNZ9+zRtQSz9PNeGYx3jFW8kY5bA3/EPUlzAfxi9MkzWdZRxQUmt85Uv0hFUSGfVq+dZiCFqqfPCmh7zIlcKOqtj3YICu4DSULVNKuefmqsOU8GK1W5ge060Bxfsr/Rgfd1w98PmiD/U+wd5p+Vd0JQthYhVsllW7p5SF+9cquXc7+0k2x2YfCQOvLjDTwf+1LpmPjpZ4d+XHTlZPEupa/k2sQ92WRhWOyiASIfBaEV1AK97gk1wgcQdHC4qhd8Hq+KA== Received: from [216.39.60.182] by nm5.bullet.mail.gq1.yahoo.com with NNFMP; 09 Mar 2015 09:56:39 -0000 Received: from [98.138.87.4] by tm18.bullet.mail.gq1.yahoo.com with NNFMP; 09 Mar 2015 09:56:39 -0000 Received: from [127.0.0.1] by omp1004.mail.ne1.yahoo.com with NNFMP; 09 Mar 2015 09:56:39 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 217760.52476.bm@omp1004.mail.ne1.yahoo.com X-YMail-OSG: Hc3glscVM1mcWmAMdOvt1._PDM0NmxfCLUkeU4EndnNblJ1cmRUz_cxPRnU6eYV NeQ717KeK3V_tKrz0g3Z5mCvfYzA6okoD6CGPrn0mSgZ.nv4tEjk7njvr8U7bzeY4.UHII65Ltdq Ct99kzvW9LPsxRXHDxGd6MfEZ2rzp5qkXhmNUuuEE0NWRfrm6olYvNzTInZcCF.jvbTqjf1dm3b3 VuGGOMmo8CjIC9lXF6BhASqKKTZJZfwUxZ9Dg3B5m63ExMd4zNMgXpTL9Cl1Vpr99.p8A.jRoFHp btU_rXT8NegBGikbp6E5Lmliz0WUx9FPN3Nv2KemuaIXCf5Ez9Jav5H3V76y0zXHQQDA2PYRCeeu ISZsn5ZSdRKBoh9dFcsR36sj_2Pc7OsNYvlWepqZ4_c_PfkWjlSAR7NYU7F54iwixYyLnhf6fhpV mHhhGmroL7J6jr_X_pKrgSE6j0PDVZkbYsza6aFrhGcpbixi46Gx8NIlts5GjFXcsBX5_8Sjbe4h w8oAu Received: by 98.138.105.192; Mon, 09 Mar 2015 09:56:38 +0000 Date: Mon, 9 Mar 2015 09:56:38 +0000 (UTC) From: Ji-Haw Foo Reply-To: Ji-Haw Foo To: =?UTF-8?Q?Mika=C3=ABl_Urankar?= Message-ID: <855488081.872463.1425894998201.JavaMail.yahoo@mail.yahoo.com> In-Reply-To: <686713608.847728.1425894948596.JavaMail.yahoo@mail.yahoo.com> References: <686713608.847728.1425894948596.JavaMail.yahoo@mail.yahoo.com> Subject: Re: porting node to Pi MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-arm@freebsd.org" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Mar 2015 09:58:21 -0000 How can I help?=20 On Monday, March 9, 2015 2:55 AM, Ji-Haw Foo wrot= e: =20 Sorry for the delay. Love to unblock node for FreeB+Pi!=20 On Monday, March 2, 2015 1:36 AM, Mika=C3=ABl Urankar wrote: =20 2015-03-02 10:14 GMT+01:00 Ji-Haw Foo : > Would you know what's missing in FreeBSD that stops 0.12.x from working? = I > have 0.12.x on Debian on Pi. Ok, I've made a mistake in my previous statement. I will have a look at www/node later today, do you want to help? =20 From owner-freebsd-arm@FreeBSD.ORG Mon Mar 9 12:16:41 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A8610414 for ; Mon, 9 Mar 2015 12:16:41 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [IPv6:2001:4f8:3:ffe0:406a:0:50:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 805C5F24 for ; Mon, 9 Mar 2015 12:16:41 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [127.0.1.5]) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9) with ESMTP id t29CGf7p061153 for ; Mon, 9 Mar 2015 12:16:41 GMT (envelope-from root@phabric-backend.isc.freebsd.org) Received: (from root@localhost) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9/Submit) id t29CGfjq061152; Mon, 9 Mar 2015 12:16:41 GMT (envelope-from root) Date: Mon, 9 Mar 2015 12:16:41 +0000 To: freebsd-arm@freebsd.org From: "zbb (Zbigniew Bodek)" Subject: [Differential] [Commented On] D2017: Allow to disable alignment faults in the kernel configuration file Message-ID: <6b28e766f7f035248a4bda92ee642e02@localhost.localdomain> X-Priority: 3 Thread-Topic: D2017: Allow to disable alignment faults in the kernel configuration file X-Herald-Rules: none X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: In-Reply-To: References: Thread-Index: M2IwYjY0ZDAxMWY3ZTNlM2Y4OWM0M2JjYjUzIFT9jyk= X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Mar 2015 12:16:41 -0000 zbb added a comment. **Jakub Palider wrote:** (NOTE) Unaligned access is controlled by two bits in SCTRL register on ARMv6+ architectures, the U bit for unaligned support (on ARMv7+ always set) and the A bit. This patch refers to bit A only, so we can just tell the processor not to raise exception when such situation happens, but rather silently perform additional fetches etc. I believe that has nothing to do with userspace, unless someone aims at fine-tuning their application and wants notification on unaligned accesses just to eventually get rid of them, but that is another story. In kernel we do have unaligned accesses, so extra handling results in unnecessary overhead and performance degradation. REVISION DETAIL https://reviews.freebsd.org/D2017 To: zbb, ian, andrew, imp Cc: freebsd-arm From owner-freebsd-arm@FreeBSD.ORG Mon Mar 9 13:05:21 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 28014D71 for ; Mon, 9 Mar 2015 13:05:21 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [IPv6:2001:4f8:3:ffe0:406a:0:50:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 060B2672 for ; Mon, 9 Mar 2015 13:05:21 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [127.0.1.5]) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9) with ESMTP id t29D5KZ7011938 for ; Mon, 9 Mar 2015 13:05:20 GMT (envelope-from root@phabric-backend.isc.freebsd.org) Received: (from root@localhost) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9/Submit) id t29D5Keb011928; Mon, 9 Mar 2015 13:05:20 GMT (envelope-from root) Date: Mon, 9 Mar 2015 13:05:20 +0000 To: freebsd-arm@freebsd.org From: "meloun-miracle-cz (Michal Meloun)" Subject: [Differential] [Changed Subscribers] D2017: Allow to disable alignment faults in the kernel configuration file Message-ID: <5b814859c841d006aa8bfa8da5e67ed5@localhost.localdomain> X-Priority: 3 Thread-Topic: D2017: Allow to disable alignment faults in the kernel configuration file X-Herald-Rules: none X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: X-Phabricator-Cc: In-Reply-To: References: Thread-Index: M2IwYjY0ZDAxMWY3ZTNlM2Y4OWM0M2JjYjUzIFT9mpA= X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: , MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Mar 2015 13:05:21 -0000 meloun-miracle-cz added a subscriber: meloun-miracle-cz. meloun-miracle-cz added a comment. I don't think it's that simple. The "unaligned access" term on ARM consist of two things. First is "A" bit in SCTRL and second is option for compiler "-mno-unaligned-access / -munaligned-access". Unfortunately, because CPU allows unaligned accesses only for some instruction, the compiler must still know if accesses aligned or unaligned data. Therefore, properly written code compiled **cannot cause** unaligned abort if is compiled with with -mno-unaligned-access and runs on CPU that have CTRL.A bit set. And in opposite, bad code **can cause** unaligned abort even if is complied with -munaligned-access and runs on CPU that have CTRL.A bit cleared. Please see ARM ARM, section "A3.2.1 Unaligned data access" for details. REVISION DETAIL https://reviews.freebsd.org/D2017 To: zbb, ian, andrew, imp Cc: meloun-miracle-cz, freebsd-arm From owner-freebsd-arm@FreeBSD.ORG Mon Mar 9 14:38:38 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 87876575 for ; Mon, 9 Mar 2015 14:38:38 +0000 (UTC) Received: from gromit.dlib.vt.edu (gromit.dlib.vt.edu [128.173.126.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gromit.dlib.vt.edu", Issuer "Chumby Certificate Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 5B89614C for ; Mon, 9 Mar 2015 14:38:38 +0000 (UTC) Received: from pmather.lib.vt.edu (pmather.lib.vt.edu [128.173.126.193]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gromit.dlib.vt.edu (Postfix) with ESMTPSA id 99830BB9; Mon, 9 Mar 2015 10:31:57 -0400 (EDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: Oddness with GPT labels on boot From: Paul Mather In-Reply-To: <20150308221139.687c8f3a@ivory.wynn.com> Date: Mon, 9 Mar 2015 10:31:57 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: <70014E4C-FB67-427C-876E-B646EA0B1AA7@gromit.dlib.vt.edu> References: <20150308221139.687c8f3a@ivory.wynn.com> To: Brett Wynkoop X-Mailer: Apple Mail (2.1878.6) Cc: freebsd-arm@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Mar 2015 14:38:38 -0000 On Mar 8, 2015, at 10:11 PM, Brett Wynkoop wrote: > Greeting- >=20 > So just updated my kernel sources and now I have this oddness = happening: >=20 > No suitable dump device was found. > Starting file system checks: > /dev/mmcsd0s2a: FILE SYSTEM CLEAN; SKIPPING CHECKS > /dev/mmcsd0s2a: clean, 560326 free (12950 frags, 68422 blocks, 0.7% > fragmentation) ugen1.2: at usbus1 > umass0: on > usbus1 umass0: SCSI over Bulk-Only; quirks =3D 0xc100 > umass0:0:0: Attached to scbus0 > da0 at umass-sim0 bus 0 scbus0 target 0 lun 0 > da0: Removable Direct Access SCSI-5 device=20 > da0: Serial Number 4C532000071129119192 > da0: 40.000MB/s transfers > da0: 15267MB (31266816 512 byte sectors: 255H 63S/T 1946C) > da0: quirks=3D0x2 > Can't stat /dev/gpt/bbexport: No such file or directory > Can't stat /dev/gpt/bbexport: No such file or directory > THE FOLLOWING FILE SYSTEM HAD AN UNEXPECTED INCONSISTENCY: > ufs: /dev/gpt/bbexport (/export) > Unknown error; help! > ERROR: ABORTING BOOT (sending SIGTERM to parent)! > Mar 8 22:04:47 init: /bin/sh on /etc/rc terminated abnormally, going > to single user mode Enter full pathname of shell or RETURN for = /bin/sh:=20 > # fsck -p > /dev/mmcsd0s2a: FILE SYSTEM CLEAN; SKIPPING CHECKS > /dev/mmcsd0s2a: clean, 560326 free (12950 frags, 68422 blocks, 0.7% > fragmentation) /dev/gpt/bbexport: FILE SYSTEM CLEAN; SKIPPING CHECKS > /dev/gpt/bbexport: clean, 3375570 free (114 frags, 421932 blocks, 0.0% > fragmentation)=20 > #=20 >=20 > Note I did nothing more than run fsck -p as soon as I was at > the /bin/sh prompt.=20 >=20 > # uname -a > FreeBSD 11.0-CURRENT FreeBSD 11.0-CURRENT #6 r279797: Sun Mar 8 > 21:22:04 EDT 2015 > wynkoop@beaglebone.wynn.com:/usr/src/sys/arm/compile/BB-BEW arm=20 > #=20 >=20 > Before this kernel I had no problem with the filesystem being checked > and mounting at boot. >=20 > I have not rebuilt world, but I am at a loss as to how that could be > the problem. Note above that it said it could not > find /dev/gpt/bbexport.=20 >=20 > I have even put the late param in /etc/fstab for /dev/gpt/bbexport to > see if that would help. One thing that caught me very recently is that when the DTrace code went = in, the BEAGLEBONE kernel config file also grew this line: makeoptions MODULES_OVERRIDE=3D"opensolaris dtrace dtrace/lockstat = dtrace/profile dtrace/fbt" That has the effect of only building those modules. If, like me, you = were using GEOM labels (which, from the above, it looks like you are = using GPT labels), via the geom_label module, then you'd get some = breakage with any new kernel, as the /dev/gpt devices would not appear = and your file systems would not be mountable. :-( If you rely on the vanilla BEAGLEBONE kernel then this might be your = problem. So, I suggest you either comment that out (and revert to building all = modules) or add a nomakeoptions somewhere. (I use another kernel config = file that includes BEAGLEBONE and then disables some things via = nooptions and nomakeoptions.) Cheers, Paul. From owner-freebsd-arm@FreeBSD.ORG Mon Mar 9 15:44:59 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 86012131 for ; Mon, 9 Mar 2015 15:44:59 +0000 (UTC) Received: from mail-pd0-f180.google.com (mail-pd0-f180.google.com [209.85.192.180]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5194BB90 for ; Mon, 9 Mar 2015 15:44:59 +0000 (UTC) Received: by pdbnh10 with SMTP id nh10so69915721pdb.4 for ; Mon, 09 Mar 2015 08:44:52 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; bh=f5cczlCEEiMEL33lABXy2AbNyGq48oOw48CueVFoeLU=; b=QzH9+8mK7AveGF4PVb/gTxfEXvcyYz6IbQ9QPoU8CwI6OHNtKrHDRqENRvZHSvRgXM t3RejRQ6MRD7tvzhk+RqUDEJyNIaG5Lq68au7ba8Nps9+WHTyhl5lp98pQzJKe2dcQHh VPWlvrWKguy/91LEGlacIXWdVq6KTLYlNCt2WyzAzvuWqBZG6d9p5bDP31yuTQEGKqpl /yuBjd51RLO8mFbLzjy1s52UIcBM6jPAdQu1OqmqGFXbkRUg3nYvl4fuOOYrzWOc34A/ JD3H5TUWuznu2/w1xcwv92VCB6e3bGvBq9ccc11XYK+4vAjIOIqXEtsy3OhLBsbXrB1c c+2A== X-Gm-Message-State: ALoCoQlYNsbE9Z//2qPf5/NIhh36RIPmRokeHepl85eaEoQeEgF5fq2PZKw2PcdYZKRaKpnMBzHg X-Received: by 10.66.140.39 with SMTP id rd7mr54393068pab.25.1425915892522; Mon, 09 Mar 2015 08:44:52 -0700 (PDT) Received: from [10.64.24.161] ([69.53.236.236]) by mx.google.com with ESMTPSA id ci17sm19799310pdb.70.2015.03.09.08.44.50 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 09 Mar 2015 08:44:51 -0700 (PDT) Sender: Warner Losh Subject: Re: Oddness with GPT labels on boot Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) Content-Type: multipart/signed; boundary="Apple-Mail=_3C53E8B7-C77B-4C4D-966C-D45F19643195"; protocol="application/pgp-signature"; micalg=pgp-sha512 X-Pgp-Agent: GPGMail 2.5b5 From: Warner Losh In-Reply-To: <70014E4C-FB67-427C-876E-B646EA0B1AA7@gromit.dlib.vt.edu> Date: Mon, 9 Mar 2015 09:44:48 -0600 Message-Id: <4BA1E952-1CD6-4060-8EC5-6EF6272ACDEE@bsdimp.com> References: <20150308221139.687c8f3a@ivory.wynn.com> <70014E4C-FB67-427C-876E-B646EA0B1AA7@gromit.dlib.vt.edu> To: Paul Mather X-Mailer: Apple Mail (2.2070.6) Cc: freebsd-arm@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Mar 2015 15:44:59 -0000 --Apple-Mail=_3C53E8B7-C77B-4C4D-966C-D45F19643195 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii > On Mar 9, 2015, at 8:31 AM, Paul Mather = wrote: >=20 > On Mar 8, 2015, at 10:11 PM, Brett Wynkoop = wrote: >=20 >> Greeting- >>=20 >> So just updated my kernel sources and now I have this oddness = happening: >>=20 >> No suitable dump device was found. >> Starting file system checks: >> /dev/mmcsd0s2a: FILE SYSTEM CLEAN; SKIPPING CHECKS >> /dev/mmcsd0s2a: clean, 560326 free (12950 frags, 68422 blocks, 0.7% >> fragmentation) ugen1.2: at usbus1 >> umass0: on >> usbus1 umass0: SCSI over Bulk-Only; quirks =3D 0xc100 >> umass0:0:0: Attached to scbus0 >> da0 at umass-sim0 bus 0 scbus0 target 0 lun 0 >> da0: Removable Direct Access SCSI-5 device >> da0: Serial Number 4C532000071129119192 >> da0: 40.000MB/s transfers >> da0: 15267MB (31266816 512 byte sectors: 255H 63S/T 1946C) >> da0: quirks=3D0x2 >> Can't stat /dev/gpt/bbexport: No such file or directory >> Can't stat /dev/gpt/bbexport: No such file or directory >> THE FOLLOWING FILE SYSTEM HAD AN UNEXPECTED INCONSISTENCY: >> ufs: /dev/gpt/bbexport (/export) >> Unknown error; help! >> ERROR: ABORTING BOOT (sending SIGTERM to parent)! >> Mar 8 22:04:47 init: /bin/sh on /etc/rc terminated abnormally, going >> to single user mode Enter full pathname of shell or RETURN for = /bin/sh: >> # fsck -p >> /dev/mmcsd0s2a: FILE SYSTEM CLEAN; SKIPPING CHECKS >> /dev/mmcsd0s2a: clean, 560326 free (12950 frags, 68422 blocks, 0.7% >> fragmentation) /dev/gpt/bbexport: FILE SYSTEM CLEAN; SKIPPING CHECKS >> /dev/gpt/bbexport: clean, 3375570 free (114 frags, 421932 blocks, = 0.0% >> fragmentation) >> # >>=20 >> Note I did nothing more than run fsck -p as soon as I was at >> the /bin/sh prompt. >>=20 >> # uname -a >> FreeBSD 11.0-CURRENT FreeBSD 11.0-CURRENT #6 r279797: Sun Mar 8 >> 21:22:04 EDT 2015 >> wynkoop@beaglebone.wynn.com:/usr/src/sys/arm/compile/BB-BEW arm >> # >>=20 >> Before this kernel I had no problem with the filesystem being checked >> and mounting at boot. >>=20 >> I have not rebuilt world, but I am at a loss as to how that could be >> the problem. Note above that it said it could not >> find /dev/gpt/bbexport. >>=20 >> I have even put the late param in /etc/fstab for /dev/gpt/bbexport to >> see if that would help. >=20 >=20 > One thing that caught me very recently is that when the DTrace code = went in, the BEAGLEBONE kernel config file also grew this line: >=20 > makeoptions MODULES_OVERRIDE=3D"opensolaris dtrace dtrace/lockstat = dtrace/profile dtrace/fbt" >=20 >=20 > That has the effect of only building those modules. If, like me, you = were using GEOM labels (which, from the above, it looks like you are = using GPT labels), via the geom_label module, then you'd get some = breakage with any new kernel, as the /dev/gpt devices would not appear = and your file systems would not be mountable. :-( >=20 > If you rely on the vanilla BEAGLEBONE kernel then this might be your = problem. >=20 > So, I suggest you either comment that out (and revert to building all = modules) or add a nomakeoptions somewhere. (I use another kernel config = file that includes BEAGLEBONE and then disables some things via = nooptions and nomakeoptions.) Or grab r279814 where I change the bogus MODULES_OVERRIDE to the correct = MODULES_EXTRA. We want to add dtrace to BEAGLEBONE, not only build = dtrace. Warner --Apple-Mail=_3C53E8B7-C77B-4C4D-966C-D45F19643195 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJU/b/wAAoJEGwc0Sh9sBEALxoQAL+mpYHN7E5qY8kUKG5BUsey te7UvBlB2Iq3w6Fu3MlmgWFpn00qTcOeILbfX02uVQoTYKhtEiobv0hx/GtNKZ8J WdWbtkE23ULtBkApNU6pARC+B09yhTmuYttN0QG5sPfzX/gO+uOrvj8U8nKnT9or vJ9SOX+nix9HfwqVPZiqma1MvGhCyvlaUqHGNWBkaJ5OKwYdY2L+C86aLCbQK8RK 48y7jgjnStFfjt8WhEHcLeBDjz4aniMzCyvi5RWo35ZEkQTt3MGIJ1hNLT8IqbFd 5GcXAoV8qJ4N4j4LmLlxo20Mm6UdvbHGPXK5VlIUlXzgi64Gs0rtIs8YWWnMFVS7 8e40fm0Yb/B4B4/kutSQv7Lll1KHnbBz1+JvnKiI7XINxJdNRdMCZlXXuU3vga0h kiXDvf093BybOx0n3WClKdtBpy8q7dsjY55p5A8dHaLjgLEohjrOyL66bLSoiWsv 0uMFHf2/cE5nLJ+Cw72PayIzosPmvW4IpvfRJ2rZT102eyTUHL22xOf+SzDZbiZn 57g5lbpe1ir0NN4/aM2xYoghHDpZIcRuqFQ+rkcQaUAMAUAKTYnmckCuDblNti1C o9xfRZpWbqh2UWguBz63WKKVnQRb4cbpbDZau+atscLi+qPgUjBvCHjW5wb1ndf5 /nPuqVy+bpbWj2CcKoiJ =C3GM -----END PGP SIGNATURE----- --Apple-Mail=_3C53E8B7-C77B-4C4D-966C-D45F19643195-- From owner-freebsd-arm@FreeBSD.ORG Mon Mar 9 16:49:20 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 23916C9A for ; Mon, 9 Mar 2015 16:49:20 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [IPv6:2001:4f8:3:ffe0:406a:0:50:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DCDCF35A for ; Mon, 9 Mar 2015 16:49:19 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [127.0.1.5]) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9) with ESMTP id t29GnJjT054096 for ; Mon, 9 Mar 2015 16:49:19 GMT (envelope-from root@phabric-backend.isc.freebsd.org) Received: (from root@localhost) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9/Submit) id t29GnJRV054095; Mon, 9 Mar 2015 16:49:19 GMT (envelope-from root) Date: Mon, 9 Mar 2015 16:49:19 +0000 To: freebsd-arm@freebsd.org From: "zbb (Zbigniew Bodek)" Subject: [Differential] [Commented On] D2017: Allow to disable alignment faults in the kernel configuration file Message-ID: X-Priority: 3 Thread-Topic: D2017: Allow to disable alignment faults in the kernel configuration file X-Herald-Rules: none X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: X-Phabricator-Cc: In-Reply-To: References: Thread-Index: M2IwYjY0ZDAxMWY3ZTNlM2Y4OWM0M2JjYjUzIFT9zw8= X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Mar 2015 16:49:20 -0000 zbb added a comment. **Jakub Palider wrote:** >Yes, I think I understand your reasoning, but you refer to a more >generic problem, related to CPU settings vs compiler code generation. >Let me show a more concrete example. Below is an extract from fault when >there is no ARM32_DISABLE_ALIGNMENT_FAULTS set. > >r7=a5b60b36a >Stopped at tcp_input+0x738: ldr r0, [r7, #0x004] > >Here, we can see instruction (LDR) which *does* operate on unaligned >addresses, so I assume compiler was clever enough not to use any of >those "forbidden" instructions (e.g. LDMIA/STMIA). Nevertheless the bit >SCTRL.A set still causes that fault happen and handled in the kernel. >As for alignment correctness in network code... well, I know it is >theoretically possible, but ensuring that would come with an >unacceptable performance cost. > >Summing up, I think that the option ought to be exported - especially >that this patch does no more than just changing feature visibility. >Feature which had been added to cpufunc.c already - not without a >reason. I personally don't understand about what is this discussion because from my point of view we have some portion of code that depends on an option that cannot be set in the configuration file. In this patch we just want to add the possibility to enable it. REVISION DETAIL https://reviews.freebsd.org/D2017 To: zbb, ian, andrew, imp Cc: meloun-miracle-cz, freebsd-arm From owner-freebsd-arm@FreeBSD.ORG Mon Mar 9 17:01:26 2015 Return-Path: Delivered-To: freebsd-arm@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E65E914B for ; Mon, 9 Mar 2015 17:01:26 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CCF9D7A6 for ; Mon, 9 Mar 2015 17:01:26 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t29H1Qji094968 for ; Mon, 9 Mar 2015 17:01:26 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-arm@FreeBSD.org Subject: [Bug 198460] [PATCH] Remove static DTB for BEAGLEBONE Date: Mon, 09 Mar 2015 17:01:26 +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: 11.0-CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: elbarto@bocal.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-arm@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status keywords bug_severity priority component assigned_to reporter attachments.created Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit 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.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Mar 2015 17:01:27 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198460 Bug ID: 198460 Summary: [PATCH] Remove static DTB for BEAGLEBONE Product: Base System Version: 11.0-CURRENT Hardware: arm OS: Any Status: New Keywords: patch Severity: Affects Many People Priority: --- Component: arm Assignee: freebsd-arm@FreeBSD.org Reporter: elbarto@bocal.org Keywords: patch Created attachment 154093 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=154093&action=edit remove static dtb This patch remove the static dtb compiled in the kernel for BEAGLEBONE and BEAGLEBONE BLACK. The same kernel config can be used for the two boards. dtb files are installed in /boot/dtb/ and loaded automatically by u-boot when using the sysutils/u-boot-beaglebone ports. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-arm@FreeBSD.ORG Mon Mar 9 17:21:32 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AAF1BABA for ; Mon, 9 Mar 2015 17:21:32 +0000 (UTC) Received: from wa3yre.wynn.com (wa3yre.wynn.com [199.89.147.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 637CEA6F for ; Mon, 9 Mar 2015 17:21:31 +0000 (UTC) Received: from ivory.wynn.com (mail.wynn.com [199.89.147.3]) (authenticated bits=0) by wa3yre.wynn.com (8.14.3/8.12.6) with ESMTP id t29HLO1J008738; Mon, 9 Mar 2015 13:21:26 -0400 (EDT) (envelope-from freebsd-arm@wynn.com) Date: Mon, 9 Mar 2015 13:21:14 -0400 From: Brett Wynkoop To: Warner Losh , freebsd-arm@freebsd.org Subject: Re: Oddness with GPT labels on boot Message-ID: <20150309132114.175e7263@ivory.wynn.com> In-Reply-To: <4BA1E952-1CD6-4060-8EC5-6EF6272ACDEE@bsdimp.com> References: <20150308221139.687c8f3a@ivory.wynn.com> <70014E4C-FB67-427C-876E-B646EA0B1AA7@gromit.dlib.vt.edu> <4BA1E952-1CD6-4060-8EC5-6EF6272ACDEE@bsdimp.com> X-Mailer: Claws Mail 3.10.1 (GTK+ 2.24.25; x86_64-apple-darwin10.8.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Mar 2015 17:21:32 -0000 Well my overnight make buildworld failed..... 0. Program arguments: tblgen -gen-disassembler -I /usr/src/lib/clang/libllvmx86disassembler/../../../contrib/llvm/include -I /usr/src/lib/clang/libllvmx86disassembler/../../../contrib/llvm/lib/Target/X86 -d X86GenDisassemblerTables.inc.d -o X86GenDisassemblerTables.inc.h /usr/src/lib/clang/libllvmx86disassembler/../../../contrib/llvm/lib/Target/X86/X86.td *** Signal 10 Stop. make[4]: stopped in /usr/src/lib/clang/libllvmx86disassembler *** Error code 1 Stop. make[3]: stopped in /usr/src/lib/clang *** Error code 1 Stop. make[2]: stopped in /usr/src *** Error code 1 Stop. make[1]: stopped in /usr/src *** Error code 1 Stop. make: stopped in /usr/src Maybe time to try and svn up again. I built the geom/gpt stuff into the kernel static. So that is why it is so odd that it is telling me no /dev/gpt/bbexport at boot, but it sees it later. Maybe the /dev stuff is slow to populate? -Brett -- wynkoop@wynn.com http://prd4.wynn.com/wynkoop/pgp-keys.txt 917-642-6925 929-272-0000 "If ever a time should come, when vain and aspiring men shall possess the highest seats in Government, our country will stand in need of its experienced patriots to prevent its ruin." -- Samuel Adams, letter to James Warren (24 October 1780) From owner-freebsd-arm@FreeBSD.ORG Mon Mar 9 17:46:49 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 74B8546D for ; Mon, 9 Mar 2015 17:46:49 +0000 (UTC) Received: from mout0.freenet.de (mout0.freenet.de [IPv6:2001:748:100:40::2:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.freenet.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2E53DD3D for ; Mon, 9 Mar 2015 17:46:49 +0000 (UTC) Received: from [195.4.92.140] (helo=mjail0.freenet.de) by mout0.freenet.de with esmtpa (ID freebsdnewbie@freenet.de) (port 25) (Exim 4.82 #2) id 1YV1lN-0000XV-CI for freebsd-arm@freebsd.org; Mon, 09 Mar 2015 18:46:45 +0100 Received: from localhost ([::1]:52692 helo=mjail0.freenet.de) by mjail0.freenet.de with esmtpa (ID freebsdnewbie@freenet.de) (Exim 4.82 #2) id 1YV1lN-0000d9-2Z for freebsd-arm@freebsd.org; Mon, 09 Mar 2015 18:46:45 +0100 Received: from mx13.freenet.de ([195.4.92.23]:58685) by mjail0.freenet.de with esmtpa (ID freebsdnewbie@freenet.de) (Exim 4.82 #2) id 1YV1iD-0007eP-7e for freebsd-arm@freebsd.org; Mon, 09 Mar 2015 18:43:29 +0100 Received: from p5ddd5082.dip0.t-ipconnect.de ([93.221.80.130]:50506 helo=[127.0.0.1]) by mx13.freenet.de with esmtpsa (ID freebsdnewbie@freenet.de) (TLSv1.2:DHE-RSA-AES128-SHA:128) (port 587) (Exim 4.82 #2) id 1YV1iD-000875-4g for freebsd-arm@freebsd.org; Mon, 09 Mar 2015 18:43:29 +0100 Message-ID: <54FDDBB6.8000101@freenet.de> Date: Mon, 09 Mar 2015 18:43:18 +0100 From: =?UTF-8?B?TWFudWVsIFN0w7xobg==?= User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: freebsd-arm@freebsd.org Subject: GPIO-INTR Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 150309-0, 09.03.2015), Outbound message X-Antivirus-Status: Clean X-Originated-At: 93.221.80.130!50506 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Mar 2015 17:46:49 -0000 Hi, i'm trying to get gpio-events signalled into userspace-applications on a RPi-B. I found some pieces about gpio-interrupts in conjunction with kqueue in the web, but nothing that makes me able to get some notification from gpio. There is an example "gpio-intr-kqueue.c", which compiles smoothly, but gives me only something like: ./gpio-intr-kqueue 23 Awaiting interrupts on pin: 23 error: Operation not supported by device How do i configure a gpio-pin as an interrupt? From owner-freebsd-arm@FreeBSD.ORG Mon Mar 9 18:05:59 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6BA568A8 for ; Mon, 9 Mar 2015 18:05:59 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [IPv6:2001:4f8:3:ffe0:406a:0:50:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4ABE4F69 for ; Mon, 9 Mar 2015 18:05:59 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [127.0.1.5]) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9) with ESMTP id t29I5x1r037229 for ; Mon, 9 Mar 2015 18:05:59 GMT (envelope-from root@phabric-backend.isc.freebsd.org) Received: (from root@localhost) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9/Submit) id t29I5xL9037228; Mon, 9 Mar 2015 18:05:59 GMT (envelope-from root) Date: Mon, 9 Mar 2015 18:05:59 +0000 To: freebsd-arm@freebsd.org From: "imp (Warner Losh)" Subject: [Differential] [Commented On] D2017: Allow to disable alignment faults in the kernel configuration file Message-ID: <5bf303a88cb2f13c93c85f2c9e54b606@localhost.localdomain> X-Priority: 3 Thread-Topic: D2017: Allow to disable alignment faults in the kernel configuration file X-Herald-Rules: none X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: X-Phabricator-Cc: In-Reply-To: References: Thread-Index: M2IwYjY0ZDAxMWY3ZTNlM2Y4OWM0M2JjYjUzIFT94Qc= X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Mar 2015 18:05:59 -0000 imp added a comment. >>! In D2017#12, @zbb wrote: > I personally don't understand about what is this discussion because from my point of view we have some portion of code that depends on an option that cannot be set in the configuration file. In this patch we just want to add the possibility to enable it. Adding this config option isn't a big deal. However, switching the architecture from one that advises that it can't do alignment fixups in hardware to one that can is, and this review has been hijacked to discuss that possibility. REVISION DETAIL https://reviews.freebsd.org/D2017 To: zbb, ian, andrew, imp Cc: meloun-miracle-cz, freebsd-arm From owner-freebsd-arm@FreeBSD.ORG Mon Mar 9 18:22:59 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B52F0D10; Mon, 9 Mar 2015 18:22:59 +0000 (UTC) Received: from wa3yre.wynn.com (wa3yre.wynn.com [199.89.147.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6F9E825D; Mon, 9 Mar 2015 18:22:58 +0000 (UTC) Received: from ivory.wynn.com (mail.wynn.com [199.89.147.3]) (authenticated bits=0) by wa3yre.wynn.com (8.14.3/8.12.6) with ESMTP id t29IMpbN011314; Mon, 9 Mar 2015 14:22:51 -0400 (EDT) (envelope-from freebsd-arm@wynn.com) Date: Mon, 9 Mar 2015 14:22:50 -0400 From: Brett Wynkoop To: bugzilla-noreply@freebsd.org, freebsd-arm@freebsd.org Subject: Re: [Bug 198460] [PATCH] Remove static DTB for BEAGLEBONE Message-ID: <20150309142250.4940ce5e@ivory.wynn.com> In-Reply-To: References: X-Mailer: Claws Mail 3.10.1 (GTK+ 2.24.25; x86_64-apple-darwin10.8.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Mar 2015 18:22:59 -0000 On Mon, 09 Mar 2015 17:01:26 +0000 bugzilla-noreply@freebsd.org wrote: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198460 > > Bug ID: 198460 > Summary: [PATCH] Remove static DTB for BEAGLEBONE > Product: Base System > Version: 11.0-CURRENT > Hardware: arm > OS: Any > Status: New > Keywords: patch > Severity: Affects Many People > Priority: --- > Component: arm > Assignee: freebsd-arm@FreeBSD.org > Reporter: elbarto@bocal.org > Keywords: patch > > Created attachment 154093 > --> > https://bugs.freebsd.org/bugzilla/attachment.cgi?id=154093&action=edit > remove static dtb > > This patch remove the static dtb compiled in the kernel for > BEAGLEBONE and BEAGLEBONE BLACK. > The same kernel config can be used for the two boards. > dtb files are installed in /boot/dtb/ and loaded automatically by > u-boot when using the sysutils/u-boot-beaglebone ports. > So does this mean if I svn up I am going to have to muck around in my ms-dos boot partition before I install a new kernel? -Brett -- wynkoop@wynn.com http://prd4.wynn.com/wynkoop/pgp-keys.txt 917-642-6925 The Second Amendment extends, prima facie, to all instruments that constitute bearable arms, even those that were not in existence at the time of the founding. ~ Justice Scalia From owner-freebsd-arm@FreeBSD.ORG Mon Mar 9 18:31:25 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 94D55150; Mon, 9 Mar 2015 18:31:25 +0000 (UTC) Received: from pmta1.delivery8.ore.mailhop.org (pmta1.delivery8.ore.mailhop.org [54.191.158.99]) by mx1.freebsd.org (Postfix) with ESMTP id 737BE3E0; Mon, 9 Mar 2015 18:31:25 +0000 (UTC) Received: from smtp5.ore.mailhop.org (172.31.18.134) by pmta1.delivery1.ore.mailhop.org id hvnje6216h0m; Mon, 9 Mar 2015 18:30:53 +0000 (envelope-from ) Received: from c-73-34-117-227.hsd1.co.comcast.net ([73.34.117.227] helo=ilsoft.org) by smtp5.ore.mailhop.org with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.82) (envelope-from ) id 1YV2SU-00082j-02; Mon, 09 Mar 2015 18:31:18 +0000 Received: from revolution.hippie.lan (revolution.hippie.lan [172.22.42.240]) by ilsoft.org (8.14.9/8.14.9) with ESMTP id t29IVFPE007672; Mon, 9 Mar 2015 12:31:15 -0600 (MDT) (envelope-from ian@freebsd.org) X-Mail-Handler: DuoCircle Outbound SMTP X-Originating-IP: 73.34.117.227 X-Report-Abuse-To: abuse@duocircle.com (see https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information for abuse reporting information) X-MHO-User: U2FsdGVkX1+zJFVuJFifq3oteyN6FhKI Message-ID: <1425925875.49563.3.camel@freebsd.org> Subject: Re: [Bug 198460] [PATCH] Remove static DTB for BEAGLEBONE From: Ian Lepore To: Brett Wynkoop Date: Mon, 09 Mar 2015 12:31:15 -0600 In-Reply-To: <20150309142250.4940ce5e@ivory.wynn.com> References: <20150309142250.4940ce5e@ivory.wynn.com> Content-Type: text/plain; charset="us-ascii" X-Mailer: Evolution 3.12.10 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Cc: freebsd-arm@freebsd.org, bugzilla-noreply@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Mar 2015 18:31:25 -0000 On Mon, 2015-03-09 at 14:22 -0400, Brett Wynkoop wrote: > On Mon, 09 Mar 2015 17:01:26 +0000 > bugzilla-noreply@freebsd.org wrote: > > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198460 > > > > Bug ID: 198460 > > Summary: [PATCH] Remove static DTB for BEAGLEBONE > > Product: Base System > > Version: 11.0-CURRENT > > Hardware: arm > > OS: Any > > Status: New > > Keywords: patch > > Severity: Affects Many People > > Priority: --- > > Component: arm > > Assignee: freebsd-arm@FreeBSD.org > > Reporter: elbarto@bocal.org > > Keywords: patch > > > > Created attachment 154093 > > --> > > https://bugs.freebsd.org/bugzilla/attachment.cgi?id=154093&action=edit > > remove static dtb > > > > This patch remove the static dtb compiled in the kernel for > > BEAGLEBONE and BEAGLEBONE BLACK. > > The same kernel config can be used for the two boards. > > dtb files are installed in /boot/dtb/ and loaded automatically by > > u-boot when using the sysutils/u-boot-beaglebone ports. > > > > So does this mean if I svn up I am going to have to muck around in my > ms-dos boot partition before I install a new kernel? > > -Brett > No, dtb files are installed along with the kernel in /boot/dtb, they don't go on the fat partition anymore. -- Ian From owner-freebsd-arm@FreeBSD.ORG Mon Mar 9 18:32:54 2015 Return-Path: Delivered-To: freebsd-arm@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B7EEA239 for ; Mon, 9 Mar 2015 18:32:54 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9E436613 for ; Mon, 9 Mar 2015 18:32:54 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t29IWsYu067089 for ; Mon, 9 Mar 2015 18:32:54 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-arm@FreeBSD.org Subject: [Bug 198460] [PATCH] Remove static DTB for BEAGLEBONE Date: Mon, 09 Mar 2015 18:32:54 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: arm X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: ian@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: ian@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc bug_status assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit 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.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Mar 2015 18:32:54 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198460 Ian Lepore changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ian@FreeBSD.org Status|New |In Progress Assignee|freebsd-arm@FreeBSD.org |ian@FreeBSD.org --- Comment #1 from Ian Lepore --- I have work in progress on this that includes changes essentially identical to the submitted patch; I'll take this one. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-arm@FreeBSD.ORG Mon Mar 9 18:42:29 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C7F87446 for ; Mon, 9 Mar 2015 18:42:29 +0000 (UTC) Received: from mx1.bocal.org (mx1.bocal.org [163.5.69.209]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3DAF7765 for ; Mon, 9 Mar 2015 18:42:28 +0000 (UTC) Received: from atlantis.staff.bocal.org (163.5.251.198 [163.5.251.198]); by mx1.bocal.org (OpenSMTPD) with ESMTPSA id bba6f6bc; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Mon, 9 Mar 2015 19:35:46 +0100 (CET) Date: Mon, 9 Mar 2015 19:35:46 +0100 From: Emmanuel Vadot To: Brett Wynkoop Subject: Re: [Bug 198460] [PATCH] Remove static DTB for BEAGLEBONE Message-Id: <20150309193546.90cbdce22fe3212e37aa9926@bocal.org> In-Reply-To: <20150309142250.4940ce5e@ivory.wynn.com> References: <20150309142250.4940ce5e@ivory.wynn.com> X-Mailer: Sylpheed 3.4.2 (GTK+ 2.24.25; amd64-portbld-freebsd10.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-arm@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Mar 2015 18:42:29 -0000 On Mon, 9 Mar 2015 14:22:50 -0400 Brett Wynkoop wrote: > On Mon, 09 Mar 2015 17:01:26 +0000 > bugzilla-noreply@freebsd.org wrote: > > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198460 > > > > Bug ID: 198460 > > Summary: [PATCH] Remove static DTB for BEAGLEBONE > > Product: Base System > > Version: 11.0-CURRENT > > Hardware: arm > > OS: Any > > Status: New > > Keywords: patch > > Severity: Affects Many People > > Priority: --- > > Component: arm > > Assignee: freebsd-arm@FreeBSD.org > > Reporter: elbarto@bocal.org > > Keywords: patch > > > > Created attachment 154093 > > --> > > https://bugs.freebsd.org/bugzilla/attachment.cgi?id=154093&action=edit > > remove static dtb > > > > This patch remove the static dtb compiled in the kernel for > > BEAGLEBONE and BEAGLEBONE BLACK. > > The same kernel config can be used for the two boards. > > dtb files are installed in /boot/dtb/ and loaded automatically by > > u-boot when using the sysutils/u-boot-beaglebone ports. > > > > So does this mean if I svn up I am going to have to muck around in my > ms-dos boot partition before I install a new kernel? > > -Brett > > -- > > wynkoop@wynn.com http://prd4.wynn.com/wynkoop/pgp-keys.txt > 917-642-6925 > > The Second Amendment extends, prima facie, to all instruments that > constitute bearable arms, even those that were not in existence > at the time of the founding. ~ Justice Scalia No the dtb files are located in the ufs partition. In your msdos partition you just have ubldr, MLO and u-boot.img as usual. -- Emmanuel Vadot From owner-freebsd-arm@FreeBSD.ORG Mon Mar 9 20:25:56 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6A8F91E6 for ; Mon, 9 Mar 2015 20:25:56 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [IPv6:2001:4f8:3:ffe0:406a:0:50:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 47C56752 for ; Mon, 9 Mar 2015 20:25:56 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [127.0.1.5]) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9) with ESMTP id t29KPtal081511 for ; Mon, 9 Mar 2015 20:25:55 GMT (envelope-from root@phabric-backend.isc.freebsd.org) Received: (from root@localhost) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9/Submit) id t29KPtIj081509; Mon, 9 Mar 2015 20:25:55 GMT (envelope-from root) Date: Mon, 9 Mar 2015 20:25:55 +0000 To: freebsd-arm@freebsd.org From: "ian (Ian Lepore)" Subject: [Differential] [Commented On] D2017: Allow to disable alignment faults in the kernel configuration file Message-ID: X-Priority: 3 Thread-Topic: D2017: Allow to disable alignment faults in the kernel configuration file X-Herald-Rules: none X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: X-Phabricator-Cc: In-Reply-To: References: Thread-Index: M2IwYjY0ZDAxMWY3ZTNlM2Y4OWM0M2JjYjUzIFT+AdM= X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Mar 2015 20:25:56 -0000 ian added a comment. I disagree, adding this IS a big deal. As soon as we have a kernel out there that can support unaligned accesses, people will build userland apps that rely on that being true, and at that point we can't change it back without effectively breaking the ABI. Having the discussion about the implications of doing this is definitely something we should do up-front, because changing our minds will be somewhere between painful and impossible. (Look at the other things we've done without much thought, such as labeling an architecture "armv6" even though it's really armv7, then spending years trying to explain that armv6 means something different in FreeBSD.) REVISION DETAIL https://reviews.freebsd.org/D2017 To: zbb, ian, andrew, imp Cc: meloun-miracle-cz, freebsd-arm From owner-freebsd-arm@FreeBSD.ORG Mon Mar 9 22:51:55 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 47B3BBF9 for ; Mon, 9 Mar 2015 22:51:55 +0000 (UTC) Received: from mail-oi0-x22a.google.com (mail-oi0-x22a.google.com [IPv6:2607:f8b0:4003:c06::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0D7B0F4F for ; Mon, 9 Mar 2015 22:51:55 +0000 (UTC) Received: by oiba3 with SMTP id a3so32306766oib.7 for ; Mon, 09 Mar 2015 15:51:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=Y7jV8f9QSwSItUSyZF4Ir5SxfnDRTab7m+kYEovIkkY=; b=nwlfHOIHSpP6dx3Inw6r/ROvBstMIOyBtW/LfW2rFiAZJ5wudHGXjQXfTjgG90Rq8D L4Vu1zKR+Lng0LkH7pzHgWoQVs/E2Fa3W7Y6uWtPUsQ93ok3zHrDv3wSKsEMuLAFF6ff HDdGuSifEF+FZdvEHAa0KgPLEsmPaWDZkbxO5J1uy1sBtx0E7aU0G5hfzRtl9OqcnzVI qVqOfUlrvesfjQFu1O+iAFdGEqTgfpb80/3JU4WmjbFON8QvM1UU6DI/3CFrsBvt04nG EgzRVUp5plZVZTZzlhOCRO6qsicQS9sSGx5kOXhcSLqmrbQA76eDd2ODCiWs+VlWP8Sv ew8Q== MIME-Version: 1.0 X-Received: by 10.182.128.199 with SMTP id nq7mr874355obb.47.1425941513750; Mon, 09 Mar 2015 15:51:53 -0700 (PDT) Received: by 10.76.86.42 with HTTP; Mon, 9 Mar 2015 15:51:53 -0700 (PDT) Date: Mon, 9 Mar 2015 22:51:53 +0000 Message-ID: Subject: UFS support in uboot From: "Sevan / Venture37" To: freebsd-arm Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Mar 2015 22:51:55 -0000 Hi, I remember a while back there was talk of getting patches resubmitted to uboot so that it would support uboot natively, did anything come of it? Sevan / Venture37 From owner-freebsd-arm@FreeBSD.ORG Tue Mar 10 00:27:19 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3C0E4885 for ; Tue, 10 Mar 2015 00:27:19 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [IPv6:2001:4f8:3:ffe0:406a:0:50:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 00620AEA for ; Tue, 10 Mar 2015 00:27:18 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [127.0.1.5]) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9) with ESMTP id t2A0RI35040550 for ; Tue, 10 Mar 2015 00:27:18 GMT (envelope-from root@phabric-backend.isc.freebsd.org) Received: (from root@localhost) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9/Submit) id t2A0RImk040549; Tue, 10 Mar 2015 00:27:18 GMT (envelope-from root) Date: Tue, 10 Mar 2015 00:27:18 +0000 To: freebsd-arm@freebsd.org From: "meloun-miracle-cz (Michal Meloun)" Subject: [Differential] [Commented On] D2017: Allow to disable alignment faults in the kernel configuration file Message-ID: X-Priority: 3 Thread-Topic: D2017: Allow to disable alignment faults in the kernel configuration file X-Herald-Rules: none X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: X-Phabricator-Cc: In-Reply-To: References: Thread-Index: M2IwYjY0ZDAxMWY3ZTNlM2Y4OWM0M2JjYjUzIFT+OmY= X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Mar 2015 00:27:19 -0000 meloun-miracle-cz added a comment. > **Jakub Palider wrote:** >Yes, I think I understand your reasoning, but you refer to a more >generic problem, related to CPU settings vs compiler code generation. >Let me show a more concrete example. Below is an extract from fault when >there is no ARM32_DISABLE_ALIGNMENT_FAULTS set. > >r7=a5b60b36a >Stopped at tcp_input+0x738: ldr r0, [r7, #0x004] > >Here, we can see instruction (LDR) which *does* operate on unaligned >addresses, so I assume compiler was clever enough not to use any of >those "forbidden" instructions (e.g. LDMIA/STMIA). This resolution is invalid, imho. The kernel is compiled with “-mno-unaligned-access”, and if everything is in order, the compiler cannot generate any unaligned access. The fault in tcp_input() indicates problem in code, compiler evidently assumes aligned address here. Due to this (incorrect) assumption compiler is free to generate any instruction (LDM/STM including). Or I miss something? Enabling of unaligned access is big win for network code. But this case is evident papering over real problem. And this problem must be solved first. REVISION DETAIL https://reviews.freebsd.org/D2017 To: zbb, ian, andrew, imp Cc: meloun-miracle-cz, freebsd-arm From owner-freebsd-arm@FreeBSD.ORG Tue Mar 10 03:25:05 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 60710C38 for ; Tue, 10 Mar 2015 03:25:05 +0000 (UTC) Received: from mail-wg0-x231.google.com (mail-wg0-x231.google.com [IPv6:2a00:1450:400c:c00::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E7DBA232 for ; Tue, 10 Mar 2015 03:25:04 +0000 (UTC) Received: by wghk14 with SMTP id k14so25900254wgh.3 for ; Mon, 09 Mar 2015 20:25:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=tmUpvpeeGxlgpfpkP7V0AJHG1Vucn5gZoxoH1g5klOk=; b=ZLARBN4puPvzFb77s18CTCAfcKRK0meeVS9Br2fYKfZ5gdrPNg19LoITxN/SUvJCvy TMax0k+FDMw5DMA41raUQBxE4Ylz7utIKYQ35aO+jM55bLMT0YWGg8yuxbzZoS/lmErv tKW+vnd84s4El2n8OuQ5tfYQDOn2wzjZpnoNANnX1hKQ66ONmN/JHBV3F/tyLJmpILcO UFlMc+H85GvOnBsHAVRRIEGJAPTaAU0M1B0tHpnHOKYUX9KenAFiYj2awSaTv39RG4f2 fXNXFfLR68Q/CI+X5k3aLxWIRCO00TdZMVrL+cD6HbrIbmeOqQa0sXn280BXmnqoTuFO x8eg== MIME-Version: 1.0 X-Received: by 10.194.24.35 with SMTP id r3mr4119771wjf.125.1425957903061; Mon, 09 Mar 2015 20:25:03 -0700 (PDT) Received: by 10.180.195.99 with HTTP; Mon, 9 Mar 2015 20:25:02 -0700 (PDT) In-Reply-To: <20150308204438.18f403a1@zeta.dino.sk> References: <20150308204438.18f403a1@zeta.dino.sk> Date: Tue, 10 Mar 2015 00:25:02 -0300 Message-ID: Subject: Re: Raspberry Pi and PiTFT display - problem with driver From: Luiz Otavio O Souza To: Milan Obuch Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-arm@freebsd.org" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Mar 2015 03:25:05 -0000 On 8 March 2015 at 16:44, Milan Obuch wrote: > Hi, > > I am trying to write a driver for PiTFT display, small 320x240 pixel > panel with touch screen. From software perspective, there are two > devices, touch screen controller with GPIO expander, STMPE610, and TFT > display controller/driver, ILI9341. Both are connected via SPI bus, > with one GPIO pin for the later. > > This is where a problem is - I found a way how to use SPI bus to > program STMPE610, how to read and write to its register, at present, > read chip identification and set/reset GPIO used to control LED > backlight. I did it a bit hackish for now, using sysctl, but it is > simple to use and works. Definitive aproach should be to create a child > device, gpioc, possibly, but it is much more complicated and takes more > time to do. > > ILI9341, on the other side, uses SPI with GPIO, so there is a question > how to do this - and, because this GPIO pin is used as 'command byte > flag', it is quite vital for proper function. > > So, first, how can I describe this requirement in FDT? Currently, I > just put there simple fragment: > > spi0 { > ili0 { > compatible = "st,ili"; > spi-chipselect = <0>; > }; > > tsc0 { > compatible = "st,stmpe_tc"; > spi-chipselect = <1>; > }; > }; > > but this does not descibe fact ILI9341 uses one GPIO pin, in case of > PiTFT, GPIO 25. It is in some way similar to what gpioiic does, but > there is only one parent device, while I have two, spi bus and gpio > pin... I need some hint... > > Second, I need some way to 'acquire' this pin in driver, so it is not > possible to change its status with gpioctl, and obtain correct values > for use in GPIOBUS_PIN_* calls to set pin's value. > > Third, it is not yet clear to me how would be the best way to implement > this. According the docs, ILI9341 is programmed with series of short > data exchanges, with exactly one command byte send to device, being > flagged with active DC pin (connected to GPIO 25), followed with short > series of bytes being written to device or, in case of status read and > similar, being read from device, all with DC pin being inactive. DC is > short for 'data/command'. > > Anybody out there with some hint? I will try to write something working > first, which will be surely not nice at the beginning, but it is much > easier to change something you know a bit about already... > > Regards, > Milan Hi, If you need help with the GPIO expander on STMPE610, let me know. Whenever is possible, we should try to use the default/vendor DTS for device. I think this is the one used by PiTFT: https://github.com/notro/fbtft/blob/master/dts/rpi.dts [...] &spi0 { pitft@0{ compatible = "ilitek,ili9340"; reg = <0>; status = "disabled"; spi-max-frequency = <32000000>; rotate = <90>; bgr; buswidth = <8>; dc-gpios = <&gpio 25 0>; [...] In this case you can make use of ofw_gpiobus_parse_gpios() to parse the 'dc-gpios' property, here is an usage example: http://pastebin.com/4mbZFuv1 The struct gpiobus_pin contains everything you need to manipulate the GPIO pin (as in the example). Luiz From owner-freebsd-arm@FreeBSD.ORG Tue Mar 10 04:00:39 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 21B60FB4 for ; Tue, 10 Mar 2015 04:00:39 +0000 (UTC) Received: from mail-we0-x22d.google.com (mail-we0-x22d.google.com [IPv6:2a00:1450:400c:c03::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A48D9750 for ; Tue, 10 Mar 2015 04:00:38 +0000 (UTC) Received: by wesu56 with SMTP id u56so12851035wes.12 for ; Mon, 09 Mar 2015 21:00:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=p+16iq3ehxb8PpK3oFA7KcqZRED3aaKvp1FMyiijcFA=; b=V8ywXCeb3VPYh33eG3Q8x6JA+TwQJis+vuGhtPCWKT2dC/rnKGLrHK0JZGyUjEKNb/ 1WfG/yi4cwF5o1NFbqeRutZKyiR2O1gA79XBdrBD+MW0qZghuo3OyqPVaBr0vbaeaV1e dhXQcvx5btpMe5L0oRBA6N0w7L76HQVVjXHAdDRIdFtxikx90Lrycw0BgwJaHeTMussC /9MmBt9y7/4gvFdR1/T+4VEhJdqjMyYw4nsLAdh/NSFYw6HIwRywv2T0FXVggtL4WlHA ikXMAVMEsQZa88bae12YscVRzkRbzA7QC0vKVUC3PpudesxBwXxOe475a0ErY9fjO7eG J0nQ== MIME-Version: 1.0 X-Received: by 10.194.120.230 with SMTP id lf6mr63291856wjb.78.1425960037101; Mon, 09 Mar 2015 21:00:37 -0700 (PDT) Received: by 10.180.195.99 with HTTP; Mon, 9 Mar 2015 21:00:37 -0700 (PDT) In-Reply-To: <20150306191957.0603e0f3@zeta.dino.sk> References: <20150216093418.3d1be83b@zeta.dino.sk> <20150219075342.7d2e7eec@zeta.dino.sk> <20150302124103.689135d3@zeta.dino.sk> <20150303215040.13f8439f@zeta.dino.sk> <20150305123903.1050694f@zeta.dino.sk> <20150306191957.0603e0f3@zeta.dino.sk> Date: Tue, 10 Mar 2015 01:00:37 -0300 Message-ID: Subject: Re: Raspberry Pi SPI device example? From: Luiz Otavio O Souza To: Milan Obuch Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-arm@freebsd.org" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Mar 2015 04:00:39 -0000 On 6 March 2015 at 15:19, Milan Obuch wrote: > Now there is another problem to solve - there are two devices on the > spibus0, ILI9341 and STMPE610, on chip selects 0 and 1 respectively. > In the end, there will be 'ili' driver for the former and 'tsc' driver > for the later. Both will use SPIBUS_TRANSFER to transfer their > respective bytes, but could they interfere as they are on the same bus? > Is it necessary to use some kind of protection against that or does spi > bus driver ensure transfers cound not interfere? The SPI support is very simple at moment, there is no bus serialization and neither userland access. At least on RPi, each SPI transfer is serialized by the driver, so once a thread start a transfer, any other transfers will be put to sleep until the first one finishes. The problem is only if you need to guarantee that consecutive transfers to the same device won't be interrupted by another threads (e.g. in a read-modify-write cycle). I hope to eventually fix this (unless someone make it first). Luiz From owner-freebsd-arm@FreeBSD.ORG Tue Mar 10 06:15:27 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2D696A6 for ; Tue, 10 Mar 2015 06:15:27 +0000 (UTC) Received: from mailhost.netlabit.sk (mailhost.netlabit.sk [84.245.65.72]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C6CE634F for ; Tue, 10 Mar 2015 06:15:26 +0000 (UTC) Received: from zeta.dino.sk (fw1.dino.sk [84.245.95.252]) (AUTH: LOGIN milan) by mailhost.netlabit.sk with ESMTPA; Tue, 10 Mar 2015 07:15:17 +0100 id 00DCA895.54FE8BF5.00012277 Date: Tue, 10 Mar 2015 07:15:16 +0100 From: Milan Obuch To: Luiz Otavio O Souza Subject: Re: Raspberry Pi and PiTFT display - problem with driver Message-ID: <20150310071516.54d5b8d1@zeta.dino.sk> In-Reply-To: References: <20150308204438.18f403a1@zeta.dino.sk> X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.25; i386-portbld-freebsd10.1) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-arm@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Mar 2015 06:15:27 -0000 On Tue, 10 Mar 2015 00:25:02 -0300 Luiz Otavio O Souza wrote: > On 8 March 2015 at 16:44, Milan Obuch wrote: > > Hi, > > > > I am trying to write a driver for PiTFT display, small 320x240 pixel > > panel with touch screen. From software perspective, there are two > > devices, touch screen controller with GPIO expander, STMPE610, and > > TFT display controller/driver, ILI9341. Both are connected via SPI > > bus, with one GPIO pin for the later. > > > > This is where a problem is - I found a way how to use SPI bus to > > program STMPE610, how to read and write to its register, at present, > > read chip identification and set/reset GPIO used to control LED > > backlight. I did it a bit hackish for now, using sysctl, but it is > > simple to use and works. Definitive aproach should be to create a > > child device, gpioc, possibly, but it is much more complicated and > > takes more time to do. > > > > ILI9341, on the other side, uses SPI with GPIO, so there is a > > question how to do this - and, because this GPIO pin is used as > > 'command byte flag', it is quite vital for proper function. > > > > So, first, how can I describe this requirement in FDT? Currently, I > > just put there simple fragment: > > > > spi0 { > > ili0 { > > compatible = "st,ili"; > > spi-chipselect = <0>; > > }; > > > > tsc0 { > > compatible = "st,stmpe_tc"; > > spi-chipselect = <1>; > > }; > > }; > > > > but this does not descibe fact ILI9341 uses one GPIO pin, in case of > > PiTFT, GPIO 25. It is in some way similar to what gpioiic does, but > > there is only one parent device, while I have two, spi bus and gpio > > pin... I need some hint... > > > > Second, I need some way to 'acquire' this pin in driver, so it is > > not possible to change its status with gpioctl, and obtain correct > > values for use in GPIOBUS_PIN_* calls to set pin's value. > > > > Third, it is not yet clear to me how would be the best way to > > implement this. According the docs, ILI9341 is programmed with > > series of short data exchanges, with exactly one command byte send > > to device, being flagged with active DC pin (connected to GPIO 25), > > followed with short series of bytes being written to device or, in > > case of status read and similar, being read from device, all with > > DC pin being inactive. DC is short for 'data/command'. > > > > Anybody out there with some hint? I will try to write something > > working first, which will be surely not nice at the beginning, but > > it is much easier to change something you know a bit about > > already... > > > > Regards, > > Milan > > Hi, > > If you need help with the GPIO expander on STMPE610, let me know. > Thanks, I will write when necessary, but my immediate need is fullfilled, there is just one pin used for backlight controll and my sysctl is functional. No other pins are available for testing, so there is no need to do it any other way. Also, touchscreen component is useless without display beeing done, so I am trying to work on that one now. > Whenever is possible, we should try to use the default/vendor DTS for > device. > > I think this is the one used by PiTFT: > https://github.com/notro/fbtft/blob/master/dts/rpi.dts > > [...] > &spi0 { > pitft@0{ > compatible = "ilitek,ili9340"; > reg = <0>; > status = "disabled"; > spi-max-frequency = <32000000>; > rotate = <90>; > bgr; > buswidth = <8>; > dc-gpios = <&gpio 25 0>; > [...] > Yes, looks so. I tried to find compiled dtb in my linux image used for functional test, but it is not in boot partition here as is the case with FreeBSD, so they must have different boot sequence regarding FDT use. Also, it looks like here is 'reg' property used in place of my 'spi-chipselect', no idea if it means the same or not. Some other differences - in Adafruit's docs Ilitek's ILI9341 is mentioned, here is ILI9340, no idea about the difference, either. > In this case you can make use of ofw_gpiobus_parse_gpios() to parse > the 'dc-gpios' property, here is an usage example: > http://pastebin.com/4mbZFuv1 > > The struct gpiobus_pin contains everything you need to manipulate the > GPIO pin (as in the example). > Thanks, will use this as reference. Regards, Milan From owner-freebsd-arm@FreeBSD.ORG Tue Mar 10 06:21:21 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3D1B7397 for ; Tue, 10 Mar 2015 06:21:21 +0000 (UTC) Received: from mailhost.netlabit.sk (mailhost.netlabit.sk [84.245.65.72]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BDCBC392 for ; Tue, 10 Mar 2015 06:21:19 +0000 (UTC) Received: from zeta.dino.sk (fw1.dino.sk [84.245.95.252]) (AUTH: LOGIN milan) by mailhost.netlabit.sk with ESMTPA; Tue, 10 Mar 2015 07:21:17 +0100 id 00DCA895.54FE8D5D.00012324 Date: Tue, 10 Mar 2015 07:21:17 +0100 From: Milan Obuch To: Luiz Otavio O Souza Subject: Re: Raspberry Pi SPI device example? Message-ID: <20150310072117.2cf020de@zeta.dino.sk> In-Reply-To: References: <20150216093418.3d1be83b@zeta.dino.sk> <20150219075342.7d2e7eec@zeta.dino.sk> <20150302124103.689135d3@zeta.dino.sk> <20150303215040.13f8439f@zeta.dino.sk> <20150305123903.1050694f@zeta.dino.sk> <20150306191957.0603e0f3@zeta.dino.sk> X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.25; i386-portbld-freebsd10.1) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-arm@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Mar 2015 06:21:21 -0000 On Tue, 10 Mar 2015 01:00:37 -0300 Luiz Otavio O Souza wrote: > On 6 March 2015 at 15:19, Milan Obuch wrote: > > Now there is another problem to solve - there are two devices on the > > spibus0, ILI9341 and STMPE610, on chip selects 0 and 1 respectively. > > In the end, there will be 'ili' driver for the former and 'tsc' > > driver for the later. Both will use SPIBUS_TRANSFER to transfer > > their respective bytes, but could they interfere as they are on the > > same bus? Is it necessary to use some kind of protection against > > that or does spi bus driver ensure transfers cound not interfere? > > The SPI support is very simple at moment, there is no bus > serialization and neither userland access. > > At least on RPi, each SPI transfer is serialized by the driver, so > once a thread start a transfer, any other transfers will be put to > sleep until the first one finishes. The problem is only if you need > to guarantee that consecutive transfers to the same device won't be > interrupted by another threads (e.g. in a read-modify-write cycle). > > I hope to eventually fix this (unless someone make it first). > > Luiz Thanks, that's enough for me now - if driver makes serialization this way, nothing to worry about, collision probability is low I think, anyway, as transfers are short and touchscreen controller will do one only when touch event is detected, but I need to make sure. Regards, Milan From owner-freebsd-arm@FreeBSD.ORG Tue Mar 10 09:43:45 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6839B3F1 for ; Tue, 10 Mar 2015 09:43:45 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [IPv6:2001:4f8:3:ffe0:406a:0:50:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 41D10C65 for ; Tue, 10 Mar 2015 09:43:45 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [127.0.1.5]) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9) with ESMTP id t2A9hieA023826 for ; Tue, 10 Mar 2015 09:43:44 GMT (envelope-from root@phabric-backend.isc.freebsd.org) Received: (from root@localhost) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9/Submit) id t2A9hi2K023824; Tue, 10 Mar 2015 09:43:44 GMT (envelope-from root) Date: Tue, 10 Mar 2015 09:43:44 +0000 To: freebsd-arm@freebsd.org From: "zbb (Zbigniew Bodek)" Subject: [Differential] [Commented On] D2018: Introduce Annapurna Labs AHCI support Message-ID: <38935d9dcdd27e9ecc0913ae481a01d1@localhost.localdomain> X-Priority: 3 Thread-Topic: D2018: Introduce Annapurna Labs AHCI support X-Herald-Rules: none X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: In-Reply-To: References: Thread-Index: ZGMxZTcyZjQyYTA3MjQzZjU5NjlmODc0YTQ5IFT+vNA= X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Mar 2015 09:43:45 -0000 zbb added inline comments. INLINE COMMENTS sys/dev/ahci/ahci.c:150-153 **Jakub Palider wrote:** > Yes, actually this is how things are expected to look like in general, I > mean restore caps. But we have no way to check it on other platforms at > the moment. If you think this does not mess up other configurations it > would be fine to perform the operation on a normal basis. sys/dev/ahci/ahci.c:199-201 **Jakub Palider wrote:** > This is something bootloaders may set up or not. This way we run > independently and make SATAs operational. This also allows to fiddle > around if someone feels like experimenting... REVISION DETAIL https://reviews.freebsd.org/D2018 To: zbb, mav, imp, smh Cc: freebsd-arm From owner-freebsd-arm@FreeBSD.ORG Tue Mar 10 11:11:39 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1A104E02 for ; Tue, 10 Mar 2015 11:11:39 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [IPv6:2001:4f8:3:ffe0:406a:0:50:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EE341978 for ; Tue, 10 Mar 2015 11:11:38 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [127.0.1.5]) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9) with ESMTP id t2ABBcLt016410 for ; Tue, 10 Mar 2015 11:11:38 GMT (envelope-from root@phabric-backend.isc.freebsd.org) Received: (from root@localhost) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9/Submit) id t2ABBcBr016409; Tue, 10 Mar 2015 11:11:38 GMT (envelope-from root) Date: Tue, 10 Mar 2015 11:11:38 +0000 To: freebsd-arm@freebsd.org From: "mav (Alexnder Motin)" Subject: [Differential] [Commented On] D2018: Introduce Annapurna Labs AHCI support Message-ID: X-Priority: 3 Thread-Topic: D2018: Introduce Annapurna Labs AHCI support X-Herald-Rules: none X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: In-Reply-To: References: Thread-Index: ZGMxZTcyZjQyYTA3MjQzZjU5NjlmODc0YTQ5IFT+0Wo= X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Mar 2015 11:11:39 -0000 mav added inline comments. INLINE COMMENTS sys/dev/ahci/ahci.c:150-153 AHCI specification defines this register as read-only. It tells nothing about "restoring" this register. I don't like idea of writing to read-only registers. sys/dev/ahci/ahci.c:199-201 According to specification, this is something that platform/BIOS must set. I know that Linux sets it always, but I believe that this is spec violation. If there is some BROKEN hardware that require it to be set by the driver, I can accept hardware-specific quirk or some tunable, but not global. REVISION DETAIL https://reviews.freebsd.org/D2018 To: zbb, mav, imp, smh Cc: freebsd-arm From owner-freebsd-arm@FreeBSD.ORG Tue Mar 10 16:19:56 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 35D89966 for ; Tue, 10 Mar 2015 16:19:56 +0000 (UTC) Received: from wa3yre.wynn.com (wa3yre.wynn.com [199.89.147.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D1A33774 for ; Tue, 10 Mar 2015 16:19:55 +0000 (UTC) Received: from ivory.wynn.com (mail.wynn.com [199.89.147.3]) (authenticated bits=0) by wa3yre.wynn.com (8.14.3/8.12.6) with ESMTP id t2AGJqA2007346 for ; Tue, 10 Mar 2015 12:19:52 -0400 (EDT) (envelope-from freebsd-arm@wynn.com) Date: Tue, 10 Mar 2015 12:19:46 -0400 From: Brett Wynkoop To: freebsd-arm Subject: Native Buildworld fails on BeagleBone Message-ID: <20150310121946.13c75571@ivory.wynn.com> X-Mailer: Claws Mail 3.10.1 (GTK+ 2.24.25; x86_64-apple-darwin10.8.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Mar 2015 16:19:56 -0000 Greeting- Well as part of my testing of the usb flash disk issues I updated my kernel to r279797 a few days ago, and I have been trying since to build world with no luck. The first run it ran out of memory with 256M of real memory and 512M swap. I kicked the swap to 1024M and it still failed: 0. Program arguments: tblgen -gen-disassembler -I /usr/src/lib/clang/libllvmx86disassembler/../../../contrib/llvm/include -I /usr/src/lib/clang/libllvmx86disassembler/../../../contrib/llvm/lib/Target/X86 -d X86GenDisassemblerTables.inc.d -o X86GenDisassemblerTables.inc.h /usr/src/lib/clang/libllvmx86disassembler/../../../contrib/llvm/lib/Target/X86/X86.td *** Signal 11 Stop. make[4]: stopped in /usr/src/lib/clang/libllvmx86disassembler *** Error code 1 Stop. make[3]: stopped in /usr/src/lib/clang *** Error code 1 Stop. make[2]: stopped in /usr/src *** Error code 1 Stop. make[1]: stopped in /usr/src *** Error code 1 Stop. make: stopped in /usr/src This was in /var/log/messages: Mar 10 08:27:35 beaglebone kernel: pid 50237 (tblgen), uid 0: exited on signal 11 (core dumped) Considering that I can build world on an old 4.6.2 x86 box with 48M real and 96M swap I am starting to think some bug has been introduced. In addition just 4 weeks ago I build world with no issues directly on the BeagleBone. Thoughts? -Brett -- wynkoop@wynn.com http://prd4.wynn.com/wynkoop/pgp-keys.txt 917-642-6925 929-272-0000 If cowardly and dishonorable men sometimes shoot unarmed men with army pistols or guns, the evil must be prevented by the penitentiary and gallows, and not by a general deprivation of a constitutional privilege. -Honorable J. A. Williams, Circuit Judge - Wilson v. State, 33 Ark. 557, 34 Am. Rep. 52 (1878). From owner-freebsd-arm@FreeBSD.ORG Tue Mar 10 19:54:18 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7A7DA285 for ; Tue, 10 Mar 2015 19:54:18 +0000 (UTC) Received: from wa3yre.wynn.com (wa3yre.wynn.com [199.89.147.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E94E767A for ; Tue, 10 Mar 2015 19:54:16 +0000 (UTC) Received: from ivory.wynn.com (mail.wynn.com [199.89.147.3]) (authenticated bits=0) by wa3yre.wynn.com (8.14.3/8.12.6) with ESMTP id t2AJs5Ua020919; Tue, 10 Mar 2015 15:54:06 -0400 (EDT) (envelope-from freebsd-arm@wynn.com) Date: Tue, 10 Mar 2015 15:54:05 -0400 From: Brett Wynkoop To: Warner Losh , freebsd-arm@freebsd.org Subject: Re: crash on writing usbstick Message-ID: <20150310155405.47f2f085@ivory.wynn.com> In-Reply-To: <1DC8221F-64EA-418C-8CE5-5FFA4F3DBC64@bsdimp.com> References: <20150301041855.5352663e@ivory.wynn.com> <20150301144653.63b38cdf@ivory.wynn.com> <20150301184456.7b5e6487@ivory.wynn.com> <1DC8221F-64EA-418C-8CE5-5FFA4F3DBC64@bsdimp.com> X-Mailer: Claws Mail 3.10.1 (GTK+ 2.24.25; x86_64-apple-darwin10.8.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Mar 2015 19:54:18 -0000 Greeting- Since my buildworld failed I decided to copy /usr/src to /export/src (/export is the usb flash drive) to free up some room just in case my problem with the build was lack of space. Well while doing: tar cpf - . | (cd /export/src ; tar xpvf -) I got another crash. For your amusement here is the information. root@beaglebone:/tmp # free Mem: 44M Active, 121M Inact, 73M Wired, 2296K Cache, 34M Buf Swap: 1024M Total, 26M Used, 998M Free, 2% Inuse root@beaglebone:/tmp # panic: ufs_dirbad: /export: bad dir ino 1513 at offset 0: mangled entry KDB: enter: panic [ thread pid 54337 tid 100115 ] Stopped at $d.7: ldrb r15, [r15, r15, ror r15]! db> tr Tracing pid 54337 tid 100115 td 0xc3207330 db_trace_self() at db_trace_self pc = 0xc0606d90 lr = 0xc0231fb8 (db_stack_trace+0x108) sp = 0xe02596d8 fp = 0xe02596f0 r10 = 0xc07ebb24 db_stack_trace() at db_stack_trace+0x108 pc = 0xc0231fb8 lr = 0xc0231928 (db_command+0x294) sp = 0xe02596f8 fp = 0xe0259798 r4 = 0x00000000 r5 = 0x00000000 r6 = 0x00000000 r10 = 0xc07ebb24 db_command() at db_command+0x294 pc = 0xc0231928 lr = 0xc0231684 (db_command_loop+0x74) sp = 0xe02597a0 fp = 0xe02597b0 r4 = 0xc0653c7f r5 = 0xc06751c8 r6 = 0xc07ebb10 r7 = 0xc072ba84 r8 = 0xc07861c0 r9 = 0xc07861c4 r10 = 0xe0259980 db_command_loop() at db_command_loop+0x74 pc = 0xc0231684 lr = 0xc0234168 (db_trap+0x108) sp = 0xe02597b8 fp = 0xe02598d8 --More-- r4 = 0x00000000 r5 = 0xc07ebb1c r6 = 0xc07861e8 r10 = 0xe0259980 db_trap() at db_trap+0x108 pc = 0xc0234168 lr = 0xc03ddf0c (kdb_trap+0xd4) sp = 0xe02598e0 fp = 0xe0259900 r4 = 0x00000000 r5 = 0x00000001 r6 = 0xc07861e8 r7 = 0xc072ba84 kdb_trap() at kdb_trap+0xd4 pc = 0xc03ddf0c lr = 0xc061be78 (undefinedinstruction+0x2c8) sp = 0xe0259908 fp = 0xe0259978 r4 = 0x00000000 r5 = 0x00000000 r6 = 0xc061bb00 r7 = 0xe7ffffff r8 = 0xc3207330 r9 = 0xc03dd7cc r10 = 0xe0259980 undefinedinstruction() at undefinedinstruction+0x2c8 pc = 0xc061be78 lr = 0xc06084b0 (exception_exit) sp = 0xe0259980 fp = 0xe0259a18 r4 = 0xc067521d r5 = 0xe0259a5c r6 = 0xc069b669 r7 = 0xc0778718 r8 = 0xc3207330 r9 = 0xc07edc18 --More-- r10 = 0xc0778580 exception_exit() at exception_exit pc = 0xc06084b0 lr = 0xc03dd7bc (kdb_enter+0x48) sp = 0xe0259a10 fp = 0xe0259a18 r0 = 0xc07861d4 r1 = 0x00000000 r2 = 0xc0678ed1 r3 = 0x000000aa r4 = 0xc067521d r5 = 0xe0259a5c r6 = 0xc069b669 r7 = 0xc0778718 r8 = 0xc3207330 r9 = 0xc07edc18 r10 = 0xc0778580 r12 = 0x00000000 $a.8() at $a.8 pc = 0xc03dd7d0 lr = 0xc03a31c8 (vpanic+0xd0) sp = 0xe0259a20 fp = 0xe0259a40 r4 = 0x00000100 r10 = 0xc0778580 vpanic() at vpanic+0xd0 pc = 0xc03a31c8 lr = 0xc03a321c (kproc_shutdown) sp = 0xe0259a48 fp = 0xe0259a50 r4 = 0xc2ff7b00 r5 = 0x00000000 r6 = 0x00000000 r7 = 0xd2c08004 r8 = 0x00000000 r9 = 0x00000200 --More-- r10 = 0xd2c08000 kproc_shutdown() at kproc_shutdown pc = 0xc03a321c lr = 0xc05c2d58 (ufs_lookup_ino+0xef0) sp = 0xe0259a58 fp = 0xe0259b20 r4 = 0xe0259a5c r5 = 0x00000000 ufs_lookup_ino() at ufs_lookup_ino+0xef0 pc = 0xc05c2d58 lr = 0xc063156c (VOP_CACHEDLOOKUP_APV+0x12c) sp = 0xe0259b28 fp = 0xe0259b40 r4 = 0xe0259b50 r5 = 0xc075d194 r6 = 0x00000000 r7 = 0x00000000 r8 = 0xe0259d00 r9 = 0x00000002 r10 = 0xe0259ce0 VOP_CACHEDLOOKUP_APV() at VOP_CACHEDLOOKUP_APV+0x12c pc = 0xc063156c lr = 0xc043eb80 (vfs_cache_lookup+0xf0) sp = 0xe0259b48 fp = 0xe0259b78 r4 = 0xe0259ce0 r5 = 0xe0259cf8 r6 = 0xc358f6c0 r10 = 0xe0259ce0 vfs_cache_lookup() at vfs_cache_lookup+0xf0 pc = 0xc043eb80 lr = 0xc06313d8 (VOP_LOOKUP_APV+0x12c) sp = 0xe0259b80 fp = 0xe0259b98 --More-- r4 = 0xe0259bb8 r5 = 0xc075d194 r6 = 0x00000000 r7 = 0x00000000 VOP_LOOKUP_APV() at VOP_LOOKUP_APV+0x12c pc = 0xc06313d8 lr = 0xc0446ac4 (lookup+0x548) sp = 0xe0259ba0 fp = 0xe0259be8 r4 = 0xc358f6c0 r5 = 0xe0259c90 r6 = 0x00200000 r10 = 0xe0259ce0 lookup() at lookup+0x548 pc = 0xc0446ac4 lr = 0xc0446240 (namei+0x398) sp = 0xe0259bf0 fp = 0xe0259c70 r4 = 0xe0259c90 r5 = 0xc297d000 r6 = 0xe0259ce8 r7 = 0x00000000 r8 = 0xe0259c18 r9 = 0x00000000 r10 = 0xe0259d00 namei() at namei+0x398 pc = 0xc0446240 lr = 0xc045c524 (kern_lutimes+0xf8) sp = 0xe0259c78 fp = 0xe0259d80 r4 = 0x00000000 r5 = 0xbffff658 r6 = 0xe0259c90 r7 = 0x20d5d640 r8 = 0xc3207330 r9 = 0x00000000 --More-- r10 = 0x00000000 kern_lutimes() at kern_lutimes+0xf8 pc = 0xc045c524 lr = 0xc045c424 (sys_lutimes+0x24) sp = 0xe0259d88 fp = 0xe0259d90 r4 = 0xc3207330 r5 = 0x00000000 r6 = 0xc07ed900 r7 = 0x00000000 r8 = 0xe0259df8 r9 = 0xc39af378 sys_lutimes() at sys_lutimes+0x24 pc = 0xc045c424 lr = 0xc061ab00 (swi_handler+0x2e4) sp = 0xe0259d98 fp = 0xe0259e48 swi_handler() at swi_handler+0x2e4 pc = 0xc061ab00 lr = 0xc0608440 (swi_exit) sp = 0xe0259e50 fp = 0xbffff698 r4 = 0x20c13200 r5 = 0xbffff668 r6 = 0xbffff658 r7 = 0x00000114 r8 = 0x20d65270 r9 = 0x00000000 r10 = 0x00000000 swi_exit() at swi_exit pc = 0xc0608440 lr = 0xc0608440 (swi_exit) sp = 0xe0259e50 fp = 0xbffff698 --More-- db> I wish we could figure out why FreeBSD ARM crashes against UFS on usb flash. I built the zfs kernel module the other day. I may reformat that partition as a zfs pool and see what happens to rule out UFS issues, but I am not sure I can actually get zfs going in 256M of memory. -Brett -- wynkoop@wynn.com http://prd4.wynn.com/wynkoop/pgp-keys.txt 917-642-6925 929-272-0000 If cowardly and dishonorable men sometimes shoot unarmed men with army pistols or guns, the evil must be prevented by the penitentiary and gallows, and not by a general deprivation of a constitutional privilege. -Honorable J. A. Williams, Circuit Judge - Wilson v. State, 33 Ark. 557, 34 Am. Rep. 52 (1878). From owner-freebsd-arm@FreeBSD.ORG Wed Mar 11 00:35:57 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AA1CE66A for ; Wed, 11 Mar 2015 00:35:57 +0000 (UTC) Received: from mail-ob0-x22f.google.com (mail-ob0-x22f.google.com [IPv6:2607:f8b0:4003:c01::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6E792CB9 for ; Wed, 11 Mar 2015 00:35:57 +0000 (UTC) Received: by obcuz6 with SMTP id uz6so5575024obc.7 for ; Tue, 10 Mar 2015 17:35:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=6zB5Wm2sXK6J/ZjU56LuhToKm/XRe7zmdIEXpdWyPxc=; b=W72xrG7jWUq5URHuusRLPtMgIcs02d5FMfy9fknCSP00oato1LpC6YRk3u0/iTtK7Y j+Syqu5szja2b5gnSBA1uVEJ27Z2CWQ6WCr/5g4duUV5wZN1bnnblav9pML4tB2K9KjR u11+58Hqrod1CA/mfSdqzD9f+FRzfbQ5Wb4R2kOnd/qJfoVKtiaS6tzB4Q4ynRRlRYAB y7SI3rUKdZ9BpwmYlWqNdK6/79E7bQZ9DPbOs0AKoOyFDDKl44/aLYwumfzswGIffbIW RCb27qFR9EHO4fevfe9DzCQ4ptIZERUi/hF4hcS7WvNgA1Eh0ukzjtmp2lHEQ/GqyIMq m5aw== MIME-Version: 1.0 X-Received: by 10.182.60.197 with SMTP id j5mr28038254obr.85.1426034156661; Tue, 10 Mar 2015 17:35:56 -0700 (PDT) Received: by 10.182.247.74 with HTTP; Tue, 10 Mar 2015 17:35:56 -0700 (PDT) Date: Tue, 10 Mar 2015 17:35:56 -0700 Message-ID: Subject: BBB freebsd-current backtrace. why? From: jungle Boogie To: "freebsd-arm@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Mar 2015 00:35:57 -0000 Hello All, Brand new download and install of -current on my beagle bone black and getting below backtrace, but the portsnap extract is continuing. If this is how it was on last weeks image, the backtrace will randomly print something similar to what's below even when the BBB is inactive. Downloaded from: ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/arm/armv6/ISO-IMAGES/11.0/ Is this expected? root@beaglebone:~ # portsnap fetch extract update Looking up portsnap.FreeBSD.org mirrors... 7 mirrors found. Fetching public key from isc.portsnap.freebsd.org... done. Fetching snapshot tag from isc.portsnap.freebsd.org... done. Fetching snapshot metadata... done. Fetching snapshot generated at Tue Mar 10 00:05:13 UTC 2015: 248798a3bfb5e11c4a642a6254d9ec1573982894936270100% of 71 MB 2297 kBps 00m32s Extracting snapshot... lock order reversal: 1st 0xcd228ba0 bufwait (bufwait) @ /usr/src/sys/kern/vfs_bio.c:3097 2nd 0xc2fa0e00 dirhash (dirhash) @ /usr/src/sys/ufs/ufs/ufs_dirhash.c:285 KDB: stack backtrace: db_trace_self() at db_trace_self pc = 0xc05cf998 lr = 0xc0233e70 (db_trace_self_wrapper+0x30) sp = 0xde6ee798 fp = 0xde6ee8b0 r10 = 0xc06270b5 db_trace_self_wrapper() at db_trace_self_wrapper+0x30 pc = 0xc0233e70 lr = 0xc03c73a4 (witness_checkorder+0xf4c) sp = 0xde6ee8b8 fp = 0xde6ee908 r4 = 0xc065da14 r5 = 0xc2fa0e00 r6 = 0xc065d662 r7 = 0xc065d65f witness_checkorder() at witness_checkorder+0xf4c pc = 0xc03c73a4 lr = 0xc0379d88 (_sx_xlock+0x80) sp = 0xde6ee910 fp = 0xde6ee940 r4 = 0x0000011d r5 = 0xc065d65f r6 = 0xc2fa0e10 r7 = 0xc2fa0e00 r8 = 0x00000000 r9 = 0x0000004c r10 = 0xde6eea00 _sx_xlock() at _sx_xlock+0x80 pc = 0xc0379d88 lr = 0xc0589558 (ufsdirhash_add+0x3c) sp = 0xde6ee948 fp = 0xde6ee968 r4 = 0xc2fa0e00 r5 = 0x0000084c r6 = 0xc3135900 r7 = 0x0000004c r8 = 0xde6eea00 r10 = 0xde6eea00 ufsdirhash_add() at ufsdirhash_add+0x3c pc = 0xc0589558 lr = 0xc058c1cc (ufs_direnter+0x46c) sp = 0xde6ee970 fp = 0xde6ee9d8 r4 = 0xc3135900 r5 = 0xc30ce6c0 r6 = 0xcd30c84c r7 = 0x0000004c r8 = 0x00000000 r9 = 0x0000004c r10 = 0xde6eea00 ufs_direnter() at ufs_direnter+0x46c pc = 0xc058c1cc lr = 0xc0595f50 (ufs_makeinode+0x498) sp = 0xde6ee9e0 fp = 0xde6eeb40 r4 = 0xc30ce6c0 r5 = 0xde6eea00 r6 = 0x000081a4 r7 = 0x00000000 r8 = 0xde6eed08 r9 = 0xc3134b80 r10 = 0xde6eed20 ufs_makeinode() at ufs_makeinode+0x498 pc = 0xc0595f50 lr = 0xc0591ebc (ufs_create+0x34) sp = 0xde6eeb48 fp = 0xde6eeb58 r4 = 0xde6eec38 r5 = 0x00008000 r6 = 0x00000000 r7 = 0x00100a02 r8 = 0x00000000 r9 = 0x00000000 r10 = 0xde6eed28 ufs_create() at ufs_create+0x34 pc = 0xc0591ebc lr = 0xc05fa2a0 (VOP_CREATE_APV+0x12c) sp = 0xde6eeb60 fp = 0xde6eeb78 r4 = 0xde6eec38 r5 = 0xc0719914 VOP_CREATE_APV() at VOP_CREATE_APV+0x12c pc = 0xc05fa2a0 lr = 0xc04290dc (vn_open_cred+0x234) sp = 0xde6eeb80 fp = 0xde6eec68 r4 = 0xde6eecb8 r5 = 0xde6eed08 r6 = 0x00000800 r10 = 0xde6eed28 vn_open_cred() at vn_open_cred+0x234 pc = 0xc04290dc lr = 0xc0428ea0 (vn_open+0x24) sp = 0xde6eec70 fp = 0xde6eec78 r4 = 0xc333d990 r5 = 0x000500cf r6 = 0x00000012 r7 = 0xde6eecb8 r8 = 0x00000000 r9 = 0x20cca150 r10 = 0x000001a4 vn_open() at vn_open+0x24 pc = 0xc0428ea0 lr = 0xc0422508 (kern_openat+0x248) sp = 0xde6eec80 fp = 0xde6eed80 kern_openat() at kern_openat+0x248 pc = 0xc0422508 lr = 0xc04227d0 (sys_openat+0x2c) sp = 0xde6eed88 fp = 0xde6eed90 r4 = 0xc333d990 r5 = 0x00000000 r6 = 0xc07a9840 r7 = 0x00000000 r8 = 0xde6eedf8 r9 = 0xc2d47a68 r10 = 0x20c14200 sys_openat() at sys_openat+0x2c pc = 0xc04227d0 lr = 0xc05e3780 (swi_handler+0x2e4) sp = 0xde6eed98 fp = 0xde6eee48 swi_handler() at swi_handler+0x2e4 pc = 0xc05e3780 lr = 0xc05d1048 (swi_exit) sp = 0xde6eee50 fp = 0xbffff930 r4 = 0x20c03300 r5 = 0x00100a01 r6 = 0x000001a4 r7 = 0x000001f3 r8 = 0x20cca150 r9 = 0xffffffe2 r10 = 0x20c14200 swi_exit() at swi_exit pc = 0xc05d1048 lr = 0xc05d1048 (swi_exit) sp = 0xde6eee50 fp = 0xbffff930 lock order reversal: 1st 0xc30ce6f4 ufs (ufs) @ /usr/src/sys/kern/vfs_subr.c:2176 2nd 0xcd228ba0 bufwait (bufwait) @ /usr/src/sys/ufs/ffs/ffs_vnops.c:263 3rd 0xc30eb6f4 ufs (ufs) @ /usr/src/sys/kern/vfs_subr.c:2176 KDB: stack backtrace: db_trace_self() at db_trace_self pc = 0xc05cf998 lr = 0xc0233e70 (db_trace_self_wrapper+0x30) sp = 0xde6ee530 fp = 0xde6ee648 r10 = 0xc06270b5 db_trace_self_wrapper() at db_trace_self_wrapper+0x30 pc = 0xc0233e70 lr = 0xc03c73a4 (witness_checkorder+0xf4c) sp = 0xde6ee650 fp = 0xde6ee6a0 r4 = 0xc062d9e4 r5 = 0xc30eb6f4 r6 = 0xc0647733 r7 = 0xc06270b5 witness_checkorder() at witness_checkorder+0xf4c pc = 0xc03c73a4 lr = 0xc0353e2c (__lockmgr_args+0x838) sp = 0xde6ee6a8 fp = 0xde6ee710 r4 = 0xc0647730 r5 = 0xc062d9e4 r6 = 0xc30eb6f4 r7 = 0x00000100 r8 = 0xc30eb714 r9 = 0x00080100 r10 = 0x00080000 __lockmgr_args() at __lockmgr_args+0x838 pc = 0xc0353e2c lr = 0xc0583cf8 (ffs_lock+0x80) sp = 0xde6ee718 fp = 0xde6ee748 r4 = 0xde6ee770 r5 = 0x00080100 r6 = 0xc30eb6c0 r7 = 0xc30eb6f4 r8 = 0xc30eb714 r9 = 0x00000000 r10 = 0x00000008 ffs_lock() at ffs_lock+0x80 pc = 0xc0583cf8 lr = 0xc05fce4c (VOP_LOCK1_APV+0x128) sp = 0xde6ee750 fp = 0xde6ee768 r4 = 0xde6ee770 r5 = 0xc07193b0 r6 = 0x00000000 r7 = 0x00080100 r8 = 0xde6ee770 r9 = 0x00000000 r10 = 0x00000880 VOP_LOCK1_APV() at VOP_LOCK1_APV+0x128 pc = 0xc05fce4c lr = 0xc0429800 (_vn_lock+0x48) sp = 0xde6ee770 fp = 0xde6ee7a0 r4 = 0xc30eb6c0 r5 = 0x0004307f r6 = 0xc0647730 r10 = 0x00000880 _vn_lock() at _vn_lock+0x48 pc = 0xc0429800 lr = 0xc041a3c4 (vget+0x60) sp = 0xde6ee7a8 fp = 0xde6ee7c8 r4 = 0xc30eb6c0 r5 = 0x0004307f r6 = 0x00080100 r7 = 0xc079f29c r8 = 0xc333d990 r9 = 0x00000000 r10 = 0xc079f280 vget() at vget+0x60 pc = 0xc041a3c4 lr = 0xc040e4a4 (vfs_hash_get+0xe0) sp = 0xde6ee7d0 fp = 0xde6ee800 r4 = 0xc064696e r5 = 0x0004307f r6 = 0xc2d592b0 r7 = 0xc079f29c r8 = 0xc30eb6c0 r10 = 0xc079f280 vfs_hash_get() at vfs_hash_get+0xe0 pc = 0xc040e4a4 lr = 0xc057eecc (ffs_vgetf+0x38) sp = 0xde6ee808 fp = 0xde6ee858 r4 = 0x0004307f r5 = 0x00080000 r6 = 0xc2d592b0 r7 = 0x0004307f r8 = 0xc2beaa80 r9 = 0xc3300bb0 r10 = 0xde6ee8b8 ffs_vgetf() at ffs_vgetf+0x38 pc = 0xc057eecc lr = 0xc05760fc (softdep_sync_buf+0x970) sp = 0xde6ee860 fp = 0xde6ee8d8 r4 = 0x0004307f r5 = 0xc2d65c00 r6 = 0xc2beaa80 r7 = 0xc2d65c00 r8 = 0xc2beaa80 r9 = 0xc3300bb0 r10 = 0xc0659363 softdep_sync_buf() at softdep_sync_buf+0x970 pc = 0xc05760fc lr = 0xc05849e4 (ffs_syncvnode+0x2f4) sp = 0xde6ee8e0 fp = 0xde6ee930 r4 = 0xc065d13c r5 = 0xc30ce6c0 r6 = 0xcd206950 r7 = 0x00000001 r8 = 0xcd228ba0 r9 = 0xcd228b50 r10 = 0x00000010 ffs_syncvnode() at ffs_syncvnode+0x2f4 pc = 0xc05849e4 lr = 0xc0583bb4 (ffs_fsync+0x20) sp = 0xde6ee938 fp = 0xde6ee948 r4 = 0xde6ee9a8 r5 = 0xc30ce6c0 r6 = 0x00000000 r7 = 0x00000000 r8 = 0xc333d990 r9 = 0xc3845480 r10 = 0xc30ce6c0 ffs_fsync() at ffs_fsync+0x20 pc = 0xc0583bb4 lr = 0xc05fbcb0 (VOP_FSYNC_APV+0x12c) sp = 0xde6ee950 fp = 0xde6ee968 r4 = 0xde6ee9a8 r5 = 0xc07193b0 r6 = 0x00000000 r7 = 0x00000000 VOP_FSYNC_APV() at VOP_FSYNC_APV+0x12c pc = 0xc05fbcb0 lr = 0xc058c4a8 (ufs_direnter+0x748) sp = 0xde6ee970 fp = 0xde6ee9d8 r4 = 0xc30ce6c0 r5 = 0xc3135900 r6 = 0x00000000 r10 = 0xc30ce6c0 ufs_direnter() at ufs_direnter+0x748 pc = 0xc058c4a8 lr = 0xc0595f50 (ufs_makeinode+0x498) sp = 0xde6ee9e0 fp = 0xde6eeb40 r4 = 0xc30ce6c0 r5 = 0xde6eea00 r6 = 0x000081a4 r7 = 0x00000000 r8 = 0xde6eed08 r9 = 0xc3986480 r10 = 0xde6eed20 ufs_makeinode() at ufs_makeinode+0x498 pc = 0xc0595f50 lr = 0xc0591ebc (ufs_create+0x34) sp = 0xde6eeb48 fp = 0xde6eeb58 r4 = 0xde6eec38 r5 = 0x00008000 r6 = 0x00000000 r7 = 0x00100a02 r8 = 0x00000000 r9 = 0x00000000 r10 = 0xde6eed28 ufs_create() at ufs_create+0x34 pc = 0xc0591ebc lr = 0xc05fa2a0 (VOP_CREATE_APV+0x12c) sp = 0xde6eeb60 fp = 0xde6eeb78 r4 = 0xde6eec38 r5 = 0xc0719914 VOP_CREATE_APV() at VOP_CREATE_APV+0x12c pc = 0xc05fa2a0 lr = 0xc04290dc (vn_open_cred+0x234) sp = 0xde6eeb80 fp = 0xde6eec68 r4 = 0xde6eecb8 r5 = 0xde6eed08 r6 = 0x00000800 r10 = 0xde6eed28 vn_open_cred() at vn_open_cred+0x234 pc = 0xc04290dc lr = 0xc0428ea0 (vn_open+0x24) sp = 0xde6eec70 fp = 0xde6eec78 r4 = 0xc333d990 r5 = 0x000500cf r6 = 0x00000012 r7 = 0xde6eecb8 r8 = 0x00000000 r9 = 0x20cca150 r10 = 0x000001a4 vn_open() at vn_open+0x24 pc = 0xc0428ea0 lr = 0xc0422508 (kern_openat+0x248) sp = 0xde6eec80 fp = 0xde6eed80 kern_openat() at kern_openat+0x248 pc = 0xc0422508 lr = 0xc04227d0 (sys_openat+0x2c) sp = 0xde6eed88 fp = 0xde6eed90 r4 = 0xc333d990 r5 = 0x00000000 r6 = 0xc07a9840 r7 = 0x00000000 r8 = 0xde6eedf8 r9 = 0xc2d47a68 r10 = 0x20c14200 sys_openat() at sys_openat+0x2c pc = 0xc04227d0 lr = 0xc05e3780 (swi_handler+0x2e4) sp = 0xde6eed98 fp = 0xde6eee48 swi_handler() at swi_handler+0x2e4 pc = 0xc05e3780 lr = 0xc05d1048 (swi_exit) sp = 0xde6eee50 fp = 0xbffff930 r4 = 0x20c03300 r5 = 0x00100a01 r6 = 0x000001a4 r7 = 0x000001f3 r8 = 0x20cca150 r9 = 0xffffffe2 r10 = 0x20c14200 swi_exit() at swi_exit pc = 0xc05d1048 lr = 0xc05d1048 (swi_exit) sp = 0xde6eee50 fp = 0xbffff930 -- ------- inum: 883510009027723 sip: jungleboogie@sip2sip.info xmpp: jungle-boogie@jit.si From owner-freebsd-arm@FreeBSD.ORG Wed Mar 11 02:05:00 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E8B59A91 for ; Wed, 11 Mar 2015 02:05:00 +0000 (UTC) Received: from wa3yre.wynn.com (wa3yre.wynn.com [199.89.147.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A7C51907 for ; Wed, 11 Mar 2015 02:05:00 +0000 (UTC) Received: from ivory.wynn.com (mail.wynn.com [199.89.147.3]) (authenticated bits=0) by wa3yre.wynn.com (8.14.3/8.12.6) with ESMTP id t2B24w9k043839; Tue, 10 Mar 2015 22:04:58 -0400 (EDT) (envelope-from freebsd-arm@wynn.com) Date: Tue, 10 Mar 2015 22:04:58 -0400 From: Brett Wynkoop To: jungle Boogie Subject: Re: BBB freebsd-current backtrace. why? Message-ID: <20150310220458.7a0f3995@ivory.wynn.com> In-Reply-To: References: X-Mailer: Claws Mail 3.10.1 (GTK+ 2.24.25; x86_64-apple-darwin10.8.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: "freebsd-arm@freebsd.org" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Mar 2015 02:05:01 -0000 Greeting- What media and device is /usr/ports on? I have had similar issues with writed to a usb flash drive. -Brett -- wynkoop@wynn.com http://prd4.wynn.com/wynkoop/pgp-keys.txt 917-642-6925 929-272-0000 If cowardly and dishonorable men sometimes shoot unarmed men with army pistols or guns, the evil must be prevented by the penitentiary and gallows, and not by a general deprivation of a constitutional privilege. -Honorable J. A. Williams, Circuit Judge - Wilson v. State, 33 Ark. 557, 34 Am. Rep. 52 (1878). From owner-freebsd-arm@FreeBSD.ORG Wed Mar 11 02:05:26 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id F25BCAD0 for ; Wed, 11 Mar 2015 02:05:25 +0000 (UTC) Received: from mail-ob0-f169.google.com (mail-ob0-f169.google.com [209.85.214.169]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B9B8C909 for ; Wed, 11 Mar 2015 02:05:25 +0000 (UTC) Received: by obcvb8 with SMTP id vb8so5988612obc.0 for ; Tue, 10 Mar 2015 19:05:19 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=48dEbeH24H3SPhidC7iVdiB32yAkvsx3nYzK62vojnw=; b=dW0BDLIr9d2aOXDxdn234sP8KinO9LQYsXf1s72FxqH2Q65sI3ZrQXSf9JfoUJm6wX ZsqhcCnQ6T6parS3tzwi0SvzMOs4WO31vdaYmx3Yte7HEtb6L2PEmlgfzOD3lYq5IhuE yU1mmKZiTBfszT0olrdT3aJjW7yB1sNUWNa5mZh97ZlEeXvIVLzcCEYtkFkjzTyeWjDH 9xEaM6amnZCQThATrefWTDFnKhs7UzJDRj4OwcqxXWlXH8Os03LjLIul+NZ8u7kjEHry UFkCa/gnCB7Rl3VHpkIDcqCoLBZ5vYkvnu5BmvFJBBTb6sT5fXryIPsmZKwpUjYgh4+C buJw== X-Gm-Message-State: ALoCoQlFHH/EYziwemUSotEQm1nDf6rzNOk3Cfn7DuvGXyvexcAscOxRdIMDnsBH04nIoeyJhE+M MIME-Version: 1.0 X-Received: by 10.182.88.136 with SMTP id bg8mr13273036obb.86.1426039518911; Tue, 10 Mar 2015 19:05:18 -0700 (PDT) Received: by 10.182.60.226 with HTTP; Tue, 10 Mar 2015 19:05:18 -0700 (PDT) X-Originating-IP: [59.167.133.100] In-Reply-To: References: Date: Wed, 11 Mar 2015 13:05:18 +1100 Message-ID: Subject: Re: BBB freebsd-current backtrace. why? From: Jason Birch To: jungle Boogie Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-arm@freebsd.org" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Mar 2015 02:05:26 -0000 On Wed, Mar 11, 2015 at 11:35 AM, jungle Boogie wrote: > Hello All, > > Brand new download and install of -current on my beagle bone black and > getting below backtrace, but the portsnap extract is continuing. If > this is how it was on last weeks image, the backtrace will randomly > print something similar to what's below even when the BBB is inactive. > > Downloaded from: > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/arm/armv6/ISO-IMAGES/11.0/ > > Is this expected? > > root@beaglebone:~ # portsnap fetch extract update > Looking up portsnap.FreeBSD.org mirrors... 7 mirrors found. > Fetching public key from isc.portsnap.freebsd.org... done. > Fetching snapshot tag from isc.portsnap.freebsd.org... done. > Fetching snapshot metadata... done. > Fetching snapshot generated at Tue Mar 10 00:05:13 UTC 2015: > 248798a3bfb5e11c4a642a6254d9ec1573982894936270100% of 71 MB 2297 kBps > 00m32s > Extracting snapshot... lock order reversal: > 1st 0xcd228ba0 bufwait (bufwait) @ /usr/src/sys/kern/vfs_bio.c:3097 > 2nd 0xc2fa0e00 dirhash (dirhash) @ /usr/src/sys/ufs/ufs/ufs_dirhash.c:285 > KDB: stack backtrace: > They're lock order reversals, as enabled by the WITNESS kernel option. You probably don't need to worry, but it's helpful to check if they've been reported and, if not, report them. You might be running into this one: http://sources.zabbadoz.net/freebsd/lor/261.html Quick Googling turns up these resources: lock order reversals - what do they mean?: https://lists.freebsd.org/pipermail/freebsd-current/2003-December/016617.html Glossary of Kernel Options for Debugging: https://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-options.html FreeBSD LOR(lock order reversal)s seen and comments: http://sources.zabbadoz.net/freebsd/lor.html From owner-freebsd-arm@FreeBSD.ORG Wed Mar 11 03:11:14 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 08C92620 for ; Wed, 11 Mar 2015 03:11:14 +0000 (UTC) Received: from relay.mailchannels.net (tkt-001-i373.relay.mailchannels.net [174.136.5.175]) by mx1.freebsd.org (Postfix) with ESMTP id 2F252EE for ; Wed, 11 Mar 2015 03:11:12 +0000 (UTC) X-Sender-Id: duocircle|x-authuser|hippie Received: from smtp7.ore.mailhop.org (ip-10-213-14-133.us-west-2.compute.internal [10.213.14.133]) by relay.mailchannels.net (Postfix) with ESMTPA id 781F960167; Wed, 11 Mar 2015 02:52:21 +0000 (UTC) X-Sender-Id: duocircle|x-authuser|hippie Received: from smtp7.ore.mailhop.org (smtp7.ore.mailhop.org [10.21.145.197]) (using TLSv1 with cipher DHE-RSA-AES256-SHA) by 0.0.0.0:2500 (trex/5.4.8); Wed, 11 Mar 2015 02:52:21 +0000 X-MC-Relay: Neutral X-MailChannels-SenderId: duocircle|x-authuser|hippie X-MailChannels-Auth-Id: duocircle X-MC-Loop-Signature: 1426042341566:4219252017 X-MC-Ingress-Time: 1426042341566 Received: from c-73-34-117-227.hsd1.co.comcast.net ([73.34.117.227] helo=ilsoft.org) by smtp7.ore.mailhop.org with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.82) (envelope-from ) id 1YVWku-0004QZ-SD; Wed, 11 Mar 2015 02:52:21 +0000 Received: from revolution.hippie.lan (revolution.hippie.lan [172.22.42.240]) by ilsoft.org (8.14.9/8.14.9) with ESMTP id t2B2qGrd010669; Tue, 10 Mar 2015 20:52:16 -0600 (MDT) (envelope-from ian@freebsd.org) X-Mail-Handler: DuoCircle Outbound SMTP X-Originating-IP: 73.34.117.227 X-Report-Abuse-To: abuse@duocircle.com (see https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information for abuse reporting information) X-MHO-User: U2FsdGVkX18gxxrfTfPRIge1CxpmkQXE Message-ID: <1426042336.33324.32.camel@freebsd.org> Subject: Re: BBB freebsd-current backtrace. why? From: Ian Lepore To: Jason Birch Date: Tue, 10 Mar 2015 20:52:16 -0600 In-Reply-To: References: Content-Type: text/plain; charset="us-ascii" X-Mailer: Evolution 3.12.10 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-AuthUser: hippie Cc: "freebsd-arm@freebsd.org" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Mar 2015 03:11:14 -0000 On Wed, 2015-03-11 at 13:05 +1100, Jason Birch wrote: > On Wed, Mar 11, 2015 at 11:35 AM, jungle Boogie > wrote: > > > Hello All, > > > > Brand new download and install of -current on my beagle bone black and > > getting below backtrace, but the portsnap extract is continuing. If > > this is how it was on last weeks image, the backtrace will randomly > > print something similar to what's below even when the BBB is inactive. > > > > Downloaded from: > > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/arm/armv6/ISO-IMAGES/11.0/ > > > > Is this expected? > > > > root@beaglebone:~ # portsnap fetch extract update > > Looking up portsnap.FreeBSD.org mirrors... 7 mirrors found. > > Fetching public key from isc.portsnap.freebsd.org... done. > > Fetching snapshot tag from isc.portsnap.freebsd.org... done. > > Fetching snapshot metadata... done. > > Fetching snapshot generated at Tue Mar 10 00:05:13 UTC 2015: > > 248798a3bfb5e11c4a642a6254d9ec1573982894936270100% of 71 MB 2297 kBps > > 00m32s > > Extracting snapshot... lock order reversal: > > 1st 0xcd228ba0 bufwait (bufwait) @ /usr/src/sys/kern/vfs_bio.c:3097 > > 2nd 0xc2fa0e00 dirhash (dirhash) @ /usr/src/sys/ufs/ufs/ufs_dirhash.c:285 > > KDB: stack backtrace: > > > > They're lock order reversals, as enabled by the WITNESS kernel option. You > probably don't need to worry, but it's helpful to check if they've been > reported and, if not, report them. > > You might be running into this one: > http://sources.zabbadoz.net/freebsd/lor/261.html That website hasn't been updated for years. The sad truth is that you can report LORs all day long and nobody seems to care anymore. But if you try to turn it off by default in the kernel configs you get yelled at about how important it is. Bah. -- Ian From owner-freebsd-arm@FreeBSD.ORG Wed Mar 11 04:07:08 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6B60CBEC for ; Wed, 11 Mar 2015 04:07:08 +0000 (UTC) Received: from mail-oi0-x234.google.com (mail-oi0-x234.google.com [IPv6:2607:f8b0:4003:c06::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2DA0680A for ; Wed, 11 Mar 2015 04:07:08 +0000 (UTC) Received: by oifz81 with SMTP id z81so5655711oif.2 for ; Tue, 10 Mar 2015 21:07:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=wrLq5CZjjqmpoyj73cCRrk2nwrCy3LqzsJMadY8pduc=; b=TMixcb1xmWeQbqlqOA8xjmyfT4QHfiu562JOZPgQn2GRxMlkBLgpqpmPxcx+3GlyeU l00gvIGGPvx4z65HDbGZBns2RDUV7qcnWg89WX9RxyFumHtwDjqX19GSd87AgeX+UEWJ N6zp5XJzjEdEqXRJ2nq8SiLXdhNjqLoyjY3m0Mk4AIBpBG3NolyjfLnGVsICwlC0ovar uh27SKfvHumYyVN9UMYLYeQKYHq8bwPMhEu9dM4b+O9AZLAtvJA1uAHgcVAgccI8MnCF i1RjcZRttZLqcfZSoGfYJMjDBabPZdyTV4XZHDxYuj/YlIqLzQdDlGkWCE+yEq69P0Kp FKgQ== MIME-Version: 1.0 X-Received: by 10.182.121.162 with SMTP id ll2mr28371626obb.71.1426046827589; Tue, 10 Mar 2015 21:07:07 -0700 (PDT) Received: by 10.182.247.74 with HTTP; Tue, 10 Mar 2015 21:07:07 -0700 (PDT) In-Reply-To: <20150310220458.7a0f3995@ivory.wynn.com> References: <20150310220458.7a0f3995@ivory.wynn.com> Date: Tue, 10 Mar 2015 21:07:07 -0700 Message-ID: Subject: Re: BBB freebsd-current backtrace. why? From: jungle Boogie To: Brett Wynkoop Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-arm@freebsd.org" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Mar 2015 04:07:08 -0000 Hi Brett, On 10 March 2015 at 19:04, Brett Wynkoop wrote: > Greeting- > > What media and device is /usr/ports on? I have had similar issues with > writed to a usb flash drive. > Its all on the same media as freeBSD..some sandisk microSD card. I didn't have the problem with previous current images so I'm inclined to think it was something in last week's image. Tonight, it happened once and not again. I'm building tmux right now and after that, I'll leave it idle all night to see if any additional backtraces occur. Thanks for writing! > -Brett Best, jungle > > -- > > wynkoop@wynn.com http://prd4.wynn.com/wynkoop/pgp-keys.txt > 917-642-6925 > 929-272-0000 > > If cowardly and dishonorable men sometimes shoot unarmed men with army > pistols or guns, the evil must be prevented by the penitentiary and > gallows, and not by a general deprivation of a constitutional privilege. > > -Honorable J. A. Williams, Circuit Judge - > Wilson v. State, 33 Ark. 557, 34 Am. Rep. 52 (1878). > -- ------- inum: 883510009027723 sip: jungleboogie@sip2sip.info xmpp: jungle-boogie@jit.si From owner-freebsd-arm@FreeBSD.ORG Wed Mar 11 04:09:41 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 91A31C56 for ; Wed, 11 Mar 2015 04:09:41 +0000 (UTC) Received: from mail-oi0-x22d.google.com (mail-oi0-x22d.google.com [IPv6:2607:f8b0:4003:c06::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 532F4824 for ; Wed, 11 Mar 2015 04:09:41 +0000 (UTC) Received: by oifu20 with SMTP id u20so5588901oif.12 for ; Tue, 10 Mar 2015 21:09:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=y9pGMg+bsccnP+87npkBPoCqtHIsfRRkONjil+R1rJA=; b=o72PyZbu/p0r3pMUo4LR0L3crayUWUm7WEGY0ldv1a7V5SKDPDsS+0CM4rKsJSmjer V1TglNxm37p95wBMdUE6PqiEyK00/pJ3m3+oo2G6QHkjcTpsMb28aoP6V8UM0rSPPOh/ uG/5vuJcwZdnQeIHlCeEaE0m4+5itqREEMnStsSER6VirH0+k9I2KC//WZUU3GUIUiA2 mvj//vqiLhCmrpl8ndI8qRvEdW4JR1kEdTfAOPWL1AJkaco/BWuT6hO+cUPZTIulXyf7 vLXtfRNxV7DDz348SkaEPwIPP3cZHN2bfx6mNq52KNzcO85jWnZvOl4Mqkb3TPsR9O+z vIsQ== MIME-Version: 1.0 X-Received: by 10.202.59.131 with SMTP id i125mr26889051oia.125.1426046980644; Tue, 10 Mar 2015 21:09:40 -0700 (PDT) Received: by 10.182.247.74 with HTTP; Tue, 10 Mar 2015 21:09:40 -0700 (PDT) In-Reply-To: References: Date: Tue, 10 Mar 2015 21:09:40 -0700 Message-ID: Subject: Re: BBB freebsd-current backtrace. why? From: jungle Boogie To: Jason Birch Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-arm@freebsd.org" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Mar 2015 04:09:41 -0000 Hi Jason, On 10 March 2015 at 19:05, Jason Birch wrote: > > They're lock order reversals, as enabled by the WITNESS kernel option. You > probably don't need to worry, but it's helpful to check if they've been > reported and, if not, report them. > > You might be running into this one: > http://sources.zabbadoz.net/freebsd/lor/261.html > > Quick Googling turns up these resources: > > lock order reversals - what do they mean?: > https://lists.freebsd.org/pipermail/freebsd-current/2003-December/016617.html > Glossary of Kernel Options for Debugging: > https://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-options.html > FreeBSD LOR(lock order reversal)s seen and comments: > http://sources.zabbadoz.net/freebsd/lor.html Based on what Ian says, I hope these BT don't continue. Those threads are very likely before the BBB was made...much less had freeBSD running, so hopefully some progress has been made with freeBSD. Best, jungle -- ------- inum: 883510009027723 sip: jungleboogie@sip2sip.info xmpp: jungle-boogie@jit.si From owner-freebsd-arm@FreeBSD.ORG Wed Mar 11 04:59:10 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 77F4346F for ; Wed, 11 Mar 2015 04:59:10 +0000 (UTC) Received: from feith1.FEITH.COM (feith1.FEITH.COM [192.251.93.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3C82ECAA for ; Wed, 11 Mar 2015 04:59:09 +0000 (UTC) Received: from jwlab.FEITH.COM (jwlab.FEITH.COM [192.251.93.16]) by feith1.FEITH.COM (8.14.9+Sun/8.12.9) with ESMTP id t2B4vPBX022151; Wed, 11 Mar 2015 00:57:25 -0400 (EDT) (envelope-from john@jwlab.FEITH.COM) Received: from jwlab.FEITH.COM (localhost [127.0.0.1]) by jwlab.FEITH.COM (8.14.9+Sun/8.14.9) with ESMTP id t2B4vPUS003068; Wed, 11 Mar 2015 00:57:25 -0400 (EDT) Received: (from john@localhost) by jwlab.FEITH.COM (8.14.9+Sun/8.14.9/Submit) id t2B4vLK5003067; Wed, 11 Mar 2015 00:57:21 -0400 (EDT) Date: Wed, 11 Mar 2015 00:57:21 -0400 (EDT) From: John Wehle Message-Id: <201503110457.t2B4vLK5003067@jwlab.FEITH.COM> To: ganbold@gmail.com Subject: Updated Amlogic aml8726-m6 and aml8726-m8 support files MIME-Version: 1.0 Content-Type: text/plain X-DCC-Etherboy-Metrics: feith1; whitelist X-Scanned-By: MIMEDefang 2.67 on 192.251.93.1 Cc: freebsd-arm@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Mar 2015 04:59:10 -0000 Here's a link to the updated support files for Amlogic ARM SoC devices: http://www.cybersashi.com/~john/FreeBSD-amlogic-20150311.shar Currently FreeBSD successfully boots to the login prompt on an aml8726-m6 board (the box seems to be some type of Visson ATV-102) as well as on an aml8726-m8b board (a Hardkernel ODROID-C1) using a SD card and a serial console. Unshar into your FreeBSD 11.0-current source tree, review the README, apply the patch, and have fun. Recent Changes: clock control (aka gate) driver has been added pinctrl driver has been added i2c driver has been added mmc driver minor tweaks rtc now survives a reboot sdxc driver has been added uart driver now supports rts/cts -- John ------------------------------------------------------------------------- | Feith Systems | Voice: 1-215-646-8000 | Email: john@feith.com | | John Wehle | Fax: 1-215-540-5495 | | ------------------------------------------------------------------------- From owner-freebsd-arm@FreeBSD.ORG Wed Mar 11 07:27:49 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1A28AE98 for ; Wed, 11 Mar 2015 07:27:49 +0000 (UTC) Received: from mail.agsec.de (mail.agsec.de [194.55.156.222]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C8A1FD33 for ; Wed, 11 Mar 2015 07:27:48 +0000 (UTC) Received: from hh01.agsec.de (localhost [127.0.0.1]) by mail.agsec.de (Postfix) with ESMTP id 381428929D for ; Wed, 11 Mar 2015 08:27:38 +0100 (CET) X-Virus-Scanned-AGSEC: MailMurkxDeScraCxler at agsec.de Received: from mail.agsec.de ([194.55.156.222]) by hh01.agsec.de (hh01.agsec.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4aciR3Vwu_tu for ; Wed, 11 Mar 2015 08:27:22 +0100 (CET) Received: from ernie.int.kts.org (ernie.int.kts.org [IPv6:2001:6f8:1c56:42::1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.agsec.de (Postfix) with ESMTPS id D8EE58929C for ; Wed, 11 Mar 2015 08:27:22 +0100 (CET) X-Virus-Scanned-KTS: Mail-UnWroks-U-Laksler at KTS.ORG Received: from frazzle.int.kts.org (frazzle.int.kts.org [IPv6:2001:6f8:1c56:42::11]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ernie.int.kts.org (Postfix) with ESMTPSA id BE842E042E for ; Wed, 11 Mar 2015 08:27:11 +0100 (CET) From: Hellmuth Michaelis Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: beaglebone boot from eMMC Message-Id: <3DF08C65-20E3-4524-B0E1-C5C096AA0FE8@hellmuth-michaelis.de> Date: Wed, 11 Mar 2015 08:27:11 +0100 To: freebsd-arm@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Mar 2015 07:27:49 -0000 Hi, i=E2=80=99m running a recent current on a beaglebone black and i=E2=80=99m= using crochet to build stuff. I=E2=80=99ve seen the copy to eMMC script = in root and tried that. After running it, i checked the MSDOS and UFS = partitions and it seems they are OK. But, after removing the SD card and = trying to boot from the internal eMMC i just see =E2=80=9EC=E2=80=9C=E2=80= =99s coming out slowly of the serial console, nothing else is happening. = Putting in the SD card and all runs well again. Has someone a hint what to look for to get it working ? hellmuth --=20 Hellmuth Michaelis Hallstra=C3=9Fe 20 25462 Rellingen Mobil: +49-160-96455696 Telefon: +49-4101-85299-20 Telefax: +49-4101-85299-21 web: www.hellmuth-michaelis.de mail: hm@hellmuth-michaelis.de From owner-freebsd-arm@FreeBSD.ORG Wed Mar 11 07:32:07 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 53655F32 for ; Wed, 11 Mar 2015 07:32:07 +0000 (UTC) Received: from mx1.bocal.org (mx1.bocal.org [163.5.69.209]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BECECDE6 for ; Wed, 11 Mar 2015 07:32:06 +0000 (UTC) Received: from [10.164.143.207] (37.163.216.32 [37.163.216.32]); by mx1.bocal.org (OpenSMTPD) with ESMTPSA id 350f36f9; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Wed, 11 Mar 2015 08:31:57 +0100 (CET) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (1.0) Subject: Re: beaglebone boot from eMMC From: Emmanuel Vadot X-Mailer: iPhone Mail (12B466) In-Reply-To: <3DF08C65-20E3-4524-B0E1-C5C096AA0FE8@hellmuth-michaelis.de> Date: Wed, 11 Mar 2015 08:31:57 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <54BA6DB9-DC61-4A6F-B948-777BB9800F54@bocal.org> References: <3DF08C65-20E3-4524-B0E1-C5C096AA0FE8@hellmuth-michaelis.de> To: Hellmuth Michaelis Cc: "freebsd-arm@freebsd.org" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Mar 2015 07:32:07 -0000 If you have all C it means that the SoC can't find the MLO or that the MLO c= an't find u-boot.img I don't remember which one. --=20 Emmanuel Vadot > On 11 Mar 2015, at 08:27, Hellmuth Michaelis wr= ote: >=20 > Hi, >=20 > i=E2=80=99m running a recent current on a beaglebone black and i=E2=80=99m= using crochet to build stuff. I=E2=80=99ve seen the copy to eMMC script in r= oot and tried that. After running it, i checked the MSDOS and UFS partitions= and it seems they are OK. But, after removing the SD card and trying to boo= t from the internal eMMC i just see =E2=80=9EC=E2=80=9C=E2=80=99s coming out= slowly of the serial console, nothing else is happening. Putting in the SD c= ard and all runs well again. >=20 > Has someone a hint what to look for to get it working ? >=20 > hellmuth > --=20 > Hellmuth Michaelis > Hallstra=C3=9Fe 20 > 25462 Rellingen >=20 > Mobil: +49-160-96455696 > Telefon: +49-4101-85299-20 > Telefax: +49-4101-85299-21 >=20 > web: www.hellmuth-michaelis.de > mail: hm@hellmuth-michaelis.de >=20 >=20 >=20 > _______________________________________________ > freebsd-arm@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" From owner-freebsd-arm@FreeBSD.ORG Wed Mar 11 09:39:15 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 72A8F8AC for ; Wed, 11 Mar 2015 09:39:15 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [IPv6:2001:4f8:3:ffe0:406a:0:50:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 52E21D59 for ; Wed, 11 Mar 2015 09:39:15 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [127.0.1.5]) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9) with ESMTP id t2B9dFti014160 for ; Wed, 11 Mar 2015 09:39:15 GMT (envelope-from root@phabric-backend.isc.freebsd.org) Received: (from root@localhost) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9/Submit) id t2B9dFQH014159; Wed, 11 Mar 2015 09:39:15 GMT (envelope-from root) Date: Wed, 11 Mar 2015 09:39:15 +0000 To: freebsd-arm@freebsd.org From: "zbb (Zbigniew Bodek)" Subject: [Differential] [Commented On] D2018: Introduce Annapurna Labs AHCI support Message-ID: X-Priority: 3 Thread-Topic: D2018: Introduce Annapurna Labs AHCI support X-Herald-Rules: none X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: In-Reply-To: References: Thread-Index: ZGMxZTcyZjQyYTA3MjQzZjU5NjlmODc0YTQ5IFUADUM= X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Mar 2015 09:39:15 -0000 zbb added inline comments. INLINE COMMENTS sys/dev/ahci/ahci.c:150-153 **Jakub Palider wrote:** >I have overlooked it in the specs and took the CAP register RW for >granted. You are right, writing to RO registers doesn't sound fine, and >we don't like it either. But we have little choice but to perform the >writes to make it operational. >You say adding it to quirks is not proper place? Where then? sys/dev/ahci/ahci.c:199-201 **Jakub Palider wrote:** >I'd prefer read MAY/SHOULD/MUST but the spec simply says that it is >loaded by the BIOS. However in reality that does not always happen and >higher level stuff suffers from broken implementations. Linux does it >and although it is not our reference it shows a way to just make things >work. Again - is adding platform quirks wrong way? REVISION DETAIL https://reviews.freebsd.org/D2018 To: zbb, mav, imp, smh Cc: freebsd-arm From owner-freebsd-arm@FreeBSD.ORG Wed Mar 11 09:44:16 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A4C53972 for ; Wed, 11 Mar 2015 09:44:16 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [IPv6:2001:4f8:3:ffe0:406a:0:50:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 84F9FE0C for ; Wed, 11 Mar 2015 09:44:16 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [127.0.1.5]) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9) with ESMTP id t2B9iGo1020580 for ; Wed, 11 Mar 2015 09:44:16 GMT (envelope-from root@phabric-backend.isc.freebsd.org) Received: (from root@localhost) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9/Submit) id t2B9iGMJ020577; Wed, 11 Mar 2015 09:44:16 GMT (envelope-from root) Date: Wed, 11 Mar 2015 09:44:16 +0000 To: freebsd-arm@freebsd.org From: "mav (Alexnder Motin)" Subject: [Differential] [Commented On] D2018: Introduce Annapurna Labs AHCI support Message-ID: X-Priority: 3 Thread-Topic: D2018: Introduce Annapurna Labs AHCI support X-Herald-Rules: none X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: In-Reply-To: References: Thread-Index: ZGMxZTcyZjQyYTA3MjQzZjU5NjlmODc0YTQ5IFUADnA= X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Mar 2015 09:44:16 -0000 mav added inline comments. INLINE COMMENTS sys/dev/ahci/ahci.c:199-201 I haven't told that something is wrong with the quirk. It is fine to me, if it is really needed, that is I am not sure about. REVISION DETAIL https://reviews.freebsd.org/D2018 To: zbb, mav, imp, smh Cc: freebsd-arm From owner-freebsd-arm@FreeBSD.ORG Wed Mar 11 10:39:13 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 28FBFA5B for ; Wed, 11 Mar 2015 10:39:13 +0000 (UTC) Received: from mail.agsec.de (mail.agsec.de [194.55.156.222]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D4D9863F for ; Wed, 11 Mar 2015 10:39:11 +0000 (UTC) Received: from hh01.agsec.de (localhost [127.0.0.1]) by mail.agsec.de (Postfix) with ESMTP id C91D58929D for ; Wed, 11 Mar 2015 11:39:06 +0100 (CET) X-Virus-Scanned-AGSEC: MailMurkxDeScraCxler at agsec.de Received: from mail.agsec.de ([194.55.156.222]) by hh01.agsec.de (hh01.agsec.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Hps2Ylx_Mdzm for ; Wed, 11 Mar 2015 11:38:51 +0100 (CET) Received: from ernie.int.kts.org (www.hallstr.kts.org [IPv6:2001:6f8:1c56:42::1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.agsec.de (Postfix) with ESMTPS id 61F3F8929C for ; Wed, 11 Mar 2015 11:38:51 +0100 (CET) X-Virus-Scanned-KTS: Mail-UnWroks-U-Laksler at KTS.ORG Received: from frazzle.int.kts.org (frazzle.int.kts.org [IPv6:2001:6f8:1c56:42::11]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ernie.int.kts.org (Postfix) with ESMTPSA id E0157E042E for ; Wed, 11 Mar 2015 11:38:39 +0100 (CET) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) Subject: Re: beaglebone boot from eMMC From: Hellmuth Michaelis In-Reply-To: <54BA6DB9-DC61-4A6F-B948-777BB9800F54@bocal.org> Date: Wed, 11 Mar 2015 11:38:39 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: References: <3DF08C65-20E3-4524-B0E1-C5C096AA0FE8@hellmuth-michaelis.de> <54BA6DB9-DC61-4A6F-B948-777BB9800F54@bocal.org> To: "freebsd-arm@freebsd.org" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Mar 2015 10:39:13 -0000 Further investigation shows, if i dd the local image from /dev/mmcsd0 or = a fresh image from remote to /dev/mmcsd1 i get sooner or later=20 GEOM_PART: integrity check failed (mmcsd1, MBR) GEOM_PART: integrity check failed (diskid/DISK-5F817AAF, MBR) on the serial console. Is the internal SD broken ? I got similar messages when i used the copy script and during probing = while start of the kernel. hellmuth --=20 Hellmuth Michaelis Hallstra=C3=9Fe 20 25462 Rellingen Mobil: +49-160-96455696 Telefon: +49-4101-85299-20 Telefax: +49-4101-85299-21 web: www.hellmuth-michaelis.de mail: hm@hellmuth-michaelis.de > Am 11.03.2015 um 08:31 schrieb Emmanuel Vadot : >=20 > If you have all C it means that the SoC can't find the MLO or that = the MLO can't find u-boot.img I don't remember which one. >=20 > --=20 > Emmanuel Vadot >=20 >> On 11 Mar 2015, at 08:27, Hellmuth Michaelis = wrote: >>=20 >> Hi, >>=20 >> i=E2=80=99m running a recent current on a beaglebone black and i=E2=80=99= m using crochet to build stuff. I=E2=80=99ve seen the copy to eMMC = script in root and tried that. After running it, i checked the MSDOS and = UFS partitions and it seems they are OK. But, after removing the SD card = and trying to boot from the internal eMMC i just see =E2=80=9EC=E2=80=9C=E2= =80=99s coming out slowly of the serial console, nothing else is = happening. Putting in the SD card and all runs well again. >>=20 >> Has someone a hint what to look for to get it working ? >>=20 >> hellmuth >> --=20 >> Hellmuth Michaelis >> Hallstra=C3=9Fe 20 >> 25462 Rellingen >>=20 >> Mobil: +49-160-96455696 >> Telefon: +49-4101-85299-20 >> Telefax: +49-4101-85299-21 >>=20 >> web: www.hellmuth-michaelis.de >> mail: hm@hellmuth-michaelis.de >>=20 >>=20 >>=20 >> _______________________________________________ >> freebsd-arm@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-arm >> To unsubscribe, send any mail to = "freebsd-arm-unsubscribe@freebsd.org" > _______________________________________________ > freebsd-arm@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" From owner-freebsd-arm@FreeBSD.ORG Wed Mar 11 11:28:41 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 533346A3 for ; Wed, 11 Mar 2015 11:28:41 +0000 (UTC) Received: from mailsec119.isp.belgacom.be (mailsec119.isp.belgacom.be [195.238.20.115]) by mx1.freebsd.org (Postfix) with ESMTP id E9A70BD5 for ; Wed, 11 Mar 2015 11:28:40 +0000 (UTC) X-Cloudmark-SP-Filtered: true X-Cloudmark-SP-Result: v=1.1 cv=wisUSL2q+2X910teRg2xg/30tBFW7lBMAi45pEFXNHU= c=1 sm=2 a=1oJP67jkp3AA:10 a=H1YVN86-igj4Lzrrnt4A:9 a=QEXdDO2ut3YA:10 a=1KCJa2O9tLIA:10 a=GMJpgf_DBfwA:10 a=SSmOFEACAAAA:8 a=Uj-3PbXrKgkKKspFDngA:9 a=_W_S_7VecoQA:10 a=p403mkujtbAA:10 a=1TM7i2lP1nUA:10 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A2D2HQBTJgBV/9EU7sMZAkGDBiIwg2W6Q4V1AYcpTQEBAQEBAXyEBjNrCQEwDgKBA4giijWSQIdGiASGU5RmkCKCFwwvEoEzBa1vI4FFDIIePYJ0AQEB Received: from mailrmu001.isp.belgacom.be ([195.238.20.209]) by privrelay.isp.belgacom.be with ESMTP; 11 Mar 2015 12:28:33 +0100 Date: Wed, 11 Mar 2015 12:28:31 +0100 (CET) From: Benny Goemans Reply-To: Benny Goemans To: freebsd-arm@freebsd.org Message-ID: <1839928617.915747.1426073311674.open-xchange@webmail.nmp.proximus.be> Subject: 11.0-CURRENT Beagle Bone Black No NIC? MIME-Version: 1.0 X-Priority: 3 Importance: Medium X-Mailer: Open-Xchange Mailer v7.2.2-Rev27 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Mar 2015 11:28:41 -0000 Just wondering. I've tested the latest image (r279813) this weekend and noticed that I didn't see the internal network interface anymore. Previous images worked correctly. It might be a regression, but could always mean there's something wrong with my device. So, am I the only one with this issue and the latest image? Benny Goemans From owner-freebsd-arm@FreeBSD.ORG Wed Mar 11 14:21:51 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 837939BE for ; Wed, 11 Mar 2015 14:21:51 +0000 (UTC) Received: from gromit.dlib.vt.edu (gromit.dlib.vt.edu [128.173.126.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gromit.dlib.vt.edu", Issuer "Chumby Certificate Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 56DD42CE for ; Wed, 11 Mar 2015 14:21:51 +0000 (UTC) Received: from pmather.lib.vt.edu (pmather.lib.vt.edu [128.173.126.193]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gromit.dlib.vt.edu (Postfix) with ESMTPSA id 5EA62150; Wed, 11 Mar 2015 10:21:44 -0400 (EDT) Subject: Re: 11.0-CURRENT Beagle Bone Black No NIC? Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Content-Type: text/plain; charset=us-ascii From: Paul Mather X-Priority: 3 In-Reply-To: <1839928617.915747.1426073311674.open-xchange@webmail.nmp.proximus.be> Date: Wed, 11 Mar 2015 10:21:43 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: References: <1839928617.915747.1426073311674.open-xchange@webmail.nmp.proximus.be> To: Benny Goemans X-Mailer: Apple Mail (2.1878.6) Cc: freebsd-arm@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Mar 2015 14:21:51 -0000 On Mar 11, 2015, at 7:28 AM, Benny Goemans = wrote: > Just wondering. I've tested the latest image (r279813) this weekend = and noticed > that I didn't see the internal network interface anymore. Previous = images worked > correctly. It might be a regression, but could always mean there's = something > wrong with my device. So, am I the only one with this issue and the = latest > image? I can't speak for the latest image, but I just finished a native build = and install of -CURRENT on my Beaglebone Black and the NIC is working = fine: root@beaglebone:/home/pmather # uname -a FreeBSD beaglebone 11.0-CURRENT FreeBSD 11.0-CURRENT #1 r279828: Tue Mar = 10 09:35:58 EDT 2015 = pmather@beaglebone:/usr/obj/usr/src/sys/BEAGLEBONE-NO_WITNESS arm root@beaglebone:/home/pmather # ifconfig cpsw0: flags=3D8843 metric 0 mtu = 1500 options=3D8000b ether 90:59:af:55:26:eb inet 10.23.5.30 netmask 0xffffff00 broadcast 10.23.5.255 media: Ethernet autoselect (100baseTX ) status: active nd6 options=3D29 lo0: flags=3D8049 metric 0 mtu 16384 options=3D600003 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 inet 127.0.0.1 netmask 0xff000000 groups: lo nd6 options=3D21 (I'm logged in via SSH right now.) Cheers, Paul. From owner-freebsd-arm@FreeBSD.ORG Wed Mar 11 14:29:16 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 95B26D3F for ; Wed, 11 Mar 2015 14:29:16 +0000 (UTC) Received: from gromit.dlib.vt.edu (gromit.dlib.vt.edu [128.173.126.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gromit.dlib.vt.edu", Issuer "Chumby Certificate Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 6970037E for ; Wed, 11 Mar 2015 14:29:16 +0000 (UTC) Received: from pmather.lib.vt.edu (pmather.lib.vt.edu [128.173.126.193]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gromit.dlib.vt.edu (Postfix) with ESMTPSA id 214D0152; Wed, 11 Mar 2015 10:29:15 -0400 (EDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: BBB freebsd-current backtrace. why? From: Paul Mather In-Reply-To: Date: Wed, 11 Mar 2015 10:29:14 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: <85F7C686-B0D3-4A48-9180-C0BA9C7DD651@gromit.dlib.vt.edu> References: To: jungle Boogie X-Mailer: Apple Mail (2.1878.6) Cc: "freebsd-arm@freebsd.org" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Mar 2015 14:29:16 -0000 On Mar 11, 2015, at 12:09 AM, jungle Boogie = wrote: > Hi Jason, > On 10 March 2015 at 19:05, Jason Birch wrote: >>=20 >> They're lock order reversals, as enabled by the WITNESS kernel = option. You >> probably don't need to worry, but it's helpful to check if they've = been >> reported and, if not, report them. >>=20 >> You might be running into this one: >> http://sources.zabbadoz.net/freebsd/lor/261.html >>=20 >> Quick Googling turns up these resources: >>=20 >> lock order reversals - what do they mean?: >> = https://lists.freebsd.org/pipermail/freebsd-current/2003-December/016617.h= tml >> Glossary of Kernel Options for Debugging: >> = https://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-optio= ns.html >> FreeBSD LOR(lock order reversal)s seen and comments: >> http://sources.zabbadoz.net/freebsd/lor.html >=20 > Based on what Ian says, I hope these BT don't continue. Those threads > are very likely before the BBB was made...much less had freeBSD > running, so hopefully some progress has been made with freeBSD. Related to what Ian said (re: the LOR list not being actively maintained = any more), for a while now I have been using this kernel config file = with my Beaglebone Black: =3D=3D=3D=3D=3D8<=3D=3D=3D=3D=3D include BEAGLEBONE ident BEAGLEBONE-NO_WITNESS nooption WITNESS nooption WITNESS_SKIPSPIN =3D=3D=3D=3D=3D>8=3D=3D=3D=3D=3D I did this when the stability of FreeBSD/arm was rather shaky (it's = improved immensely, now), and I'd often confuse the LOR output for = panics at first glance. :-) Cheers, Paul.= From owner-freebsd-arm@FreeBSD.ORG Wed Mar 11 15:06:15 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B357A12D for ; Wed, 11 Mar 2015 15:06:15 +0000 (UTC) Received: from relay.mailchannels.net (ar-005-i207.relay.mailchannels.net [162.253.144.89]) by mx1.freebsd.org (Postfix) with ESMTP id C3C9AAE4 for ; Wed, 11 Mar 2015 15:06:14 +0000 (UTC) X-Sender-Id: duocircle|x-authuser|hippie Received: from smtp1.ore.mailhop.org (ip-10-213-14-133.us-west-2.compute.internal [10.213.14.133]) by relay.mailchannels.net (Postfix) with ESMTPA id 170AE61541; Wed, 11 Mar 2015 14:11:08 +0000 (UTC) X-Sender-Id: duocircle|x-authuser|hippie Received: from smtp1.ore.mailhop.org (smtp1.ore.mailhop.org [10.83.15.107]) (using TLSv1 with cipher DHE-RSA-AES256-SHA) by 0.0.0.0:2500 (trex/5.4.8); Wed, 11 Mar 2015 14:11:08 +0000 X-MC-Relay: Neutral X-MailChannels-SenderId: duocircle|x-authuser|hippie X-MailChannels-Auth-Id: duocircle X-MC-Loop-Signature: 1426083068302:1505907783 X-MC-Ingress-Time: 1426083068302 Received: from c-73-34-117-227.hsd1.co.comcast.net ([73.34.117.227] helo=ilsoft.org) by smtp1.ore.mailhop.org with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.82) (envelope-from ) id 1YVhLn-0003Wa-V1; Wed, 11 Mar 2015 14:11:08 +0000 Received: from revolution.hippie.lan (revolution.hippie.lan [172.22.42.240]) by ilsoft.org (8.14.9/8.14.9) with ESMTP id t2BEB64f011831; Wed, 11 Mar 2015 08:11:06 -0600 (MDT) (envelope-from ian@freebsd.org) X-Mail-Handler: DuoCircle Outbound SMTP X-Originating-IP: 73.34.117.227 X-Report-Abuse-To: abuse@duocircle.com (see https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information for abuse reporting information) X-MHO-User: U2FsdGVkX1+JGALfhblIYjr4gUJLn9xb Message-ID: <1426083066.33324.34.camel@freebsd.org> Subject: Re: BBB freebsd-current backtrace. why? From: Ian Lepore To: jungle Boogie Date: Wed, 11 Mar 2015 08:11:06 -0600 In-Reply-To: References: Content-Type: text/plain; charset="us-ascii" X-Mailer: Evolution 3.12.10 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-AuthUser: hippie Cc: "freebsd-arm@freebsd.org" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Mar 2015 15:06:15 -0000 On Tue, 2015-03-10 at 21:09 -0700, jungle Boogie wrote: > Hi Jason, > On 10 March 2015 at 19:05, Jason Birch wrote: > > > > They're lock order reversals, as enabled by the WITNESS kernel option. You > > probably don't need to worry, but it's helpful to check if they've been > > reported and, if not, report them. > > > > You might be running into this one: > > http://sources.zabbadoz.net/freebsd/lor/261.html > > > > Quick Googling turns up these resources: > > > > lock order reversals - what do they mean?: > > https://lists.freebsd.org/pipermail/freebsd-current/2003-December/016617.html > > Glossary of Kernel Options for Debugging: > > https://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-options.html > > FreeBSD LOR(lock order reversal)s seen and comments: > > http://sources.zabbadoz.net/freebsd/lor.html > > Based on what Ian says, I hope these BT don't continue. Those threads > are very likely before the BBB was made...much less had freeBSD > running, so hopefully some progress has been made with freeBSD. The point is that those LORs are harmless. They were declared harmless by the gurus who understand them, years ago, and apparently just by issuing that proclamation, it's a closed subject and we all just have to live with the spewage. -- Ian From owner-freebsd-arm@FreeBSD.ORG Wed Mar 11 17:09:47 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 40A6216A for ; Wed, 11 Mar 2015 17:09:47 +0000 (UTC) Received: from wa3yre.wynn.com (wa3yre.wynn.com [199.89.147.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EE6EFC9B for ; Wed, 11 Mar 2015 17:09:46 +0000 (UTC) Received: from ivory.wynn.com (mail.wynn.com [199.89.147.3]) (authenticated bits=0) by wa3yre.wynn.com (8.14.3/8.12.6) with ESMTP id t2BH9cIX092943 for ; Wed, 11 Mar 2015 13:09:40 -0400 (EDT) (envelope-from freebsd-arm@wynn.com) Date: Wed, 11 Mar 2015 13:09:32 -0400 From: Brett Wynkoop To: freebsd-arm@freebsd.org Subject: zfs on BeagleBone Message-ID: <20150311130932.3493a938@ivory.wynn.com> X-Mailer: Claws Mail 3.10.1 (GTK+ 2.24.25; x86_64-apple-darwin10.8.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Mar 2015 17:09:47 -0000 Greeting- Since someone suggested as part of my testing the USB Flash Disk crashes on my BeagleBone that I try ZFS I have. At the moment I am running the same copy operation that caused it to crash on UFS. I will report on the success or failure in the original thread. For now these are my zfs settings for the BeagleBone: zfs_load="YES" # from zfstuning wiki # vm.kmem_size="256M" vm.kmem_size_max="256M" #vfs.zfs.arc_max="40M" #vfs.zfs.arc_max="64M" vfs.zfs.arc_max="24M" vfs.zfs.vdev.cache.size="5M" and this is what I am seeing writing to the zpool: root@beaglebone:/usr/src/usr.sbin/ypset # zpool iostat 5 capacity operations bandwidth pool alloc free read write read write ---------- ----- ----- ----- ----- ----- ----- bbexport 149M 14.2G 0 4 6.41K 181K bbexport 151M 14.2G 0 16 28.6K 312K bbexport 152M 14.2G 0 6 12.7K 194K bbexport 152M 14.2G 0 6 0 171K bbexport 153M 14.2G 0 6 12.7K 201K bbexport 154M 14.2G 0 8 12.7K 177K bbexport 154M 14.2G 0 6 12.8K 69.8K bbexport 157M 14.2G 0 12 12.5K 547K bbexport 157M 14.2G 0 6 25.5K 152K bbexport 158M 14.2G 0 6 0 162K bbexport 158M 14.2G 0 6 12.7K 136K bbexport 159M 14.2G 0 6 12.8K 164K bbexport 160M 14.2G 3 8 81.7K 174K bbexport 160M 14.2G 0 6 3.09K 166K bbexport 163M 14.2G 0 9 15.5K 459K bbexport 163M 14.2G 0 7 26.9K 164K I am shocked it is working at all considering I could not get a 384M x86 box to run with zfs! -Brett -- wynkoop@wynn.com http://prd4.wynn.com/wynkoop/pgp-keys.txt 917-642-6925 929-272-0000 If cowardly and dishonorable men sometimes shoot unarmed men with army pistols or guns, the evil must be prevented by the penitentiary and gallows, and not by a general deprivation of a constitutional privilege. -Honorable J. A. Williams, Circuit Judge - Wilson v. State, 33 Ark. 557, 34 Am. Rep. 52 (1878). From owner-freebsd-arm@FreeBSD.ORG Wed Mar 11 17:15:11 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0475531F for ; Wed, 11 Mar 2015 17:15:11 +0000 (UTC) Received: from mail-we0-x234.google.com (mail-we0-x234.google.com [IPv6:2a00:1450:400c:c03::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8B0F9D8D for ; Wed, 11 Mar 2015 17:15:10 +0000 (UTC) Received: by wevk48 with SMTP id k48so10744526wev.7 for ; Wed, 11 Mar 2015 10:15:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=8orURwnJC9om5YkqHHUXPLC1628d6KwGgVho0RAOQ4o=; b=Xb0WXZ9cisBwbzZMSoaBl7QCoeqfp/xTEJDPjwfpSmkupNOMorGwrZOAEl89anqKaS JiP0mtp7Kv44piRMi+N9AHueZpqB00KTYnN4bBMBvmEp1HQdRQGPG/TEPDT6iJGlpHir nmsHJ+x25izu/90Noq8C5WrSmOLIiWB6pIq/CvpEM6M3I+1lTMIWDY+zO+CV/D7XhGQ+ PoZLsi9tv5AkkLiAQYQpwIl5xcc7IfyGMOKJv+BkDQgT0mbTxVMjSmmqWBcw20FeTC7h Da7hLeIo0VSuvY1zIfviTCab8QnJcOg2onH60wFHYCBWpLWxC9Kl1Yh7/wCogCsskOmi 1Lrw== MIME-Version: 1.0 X-Received: by 10.194.121.10 with SMTP id lg10mr81198974wjb.71.1426094109014; Wed, 11 Mar 2015 10:15:09 -0700 (PDT) Received: by 10.180.195.99 with HTTP; Wed, 11 Mar 2015 10:15:08 -0700 (PDT) In-Reply-To: <54FDDBB6.8000101@freenet.de> References: <54FDDBB6.8000101@freenet.de> Date: Wed, 11 Mar 2015 14:15:08 -0300 Message-ID: Subject: Re: GPIO-INTR From: Luiz Otavio O Souza To: =?UTF-8?Q?Manuel_St=C3=BChn?= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: "freebsd-arm@freebsd.org" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Mar 2015 17:15:11 -0000 On 9 March 2015 at 14:43, Manuel St=C3=BChn wrote: > Hi, > i'm trying to get gpio-events signalled into userspace-applications on a > RPi-B. I found some pieces about gpio-interrupts in conjunction with kque= ue > in the web, but nothing that makes me able to get some notification from > gpio. There is an example "gpio-intr-kqueue.c", which compiles smoothly, = but > gives me only something like: > > ./gpio-intr-kqueue 23 > Awaiting interrupts on pin: 23 > error: Operation not supported by device > > How do i configure a gpio-pin as an interrupt? Hi Manuel, I changed the way the GPIO events are passed to userland and gpio-intr-kqueue won't work anymore. I'm working in its replacement and I will soon post the patches and (hopefully) a comprehensive guide to get it working. There is also an ongoing work to change interrupt support on ARM which I need to catch up. Regards, Luiz From owner-freebsd-arm@FreeBSD.ORG Wed Mar 11 17:44:58 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D79E7B10 for ; Wed, 11 Mar 2015 17:44:58 +0000 (UTC) Received: from wa3yre.wynn.com (wa3yre.wynn.com [199.89.147.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8C917144 for ; Wed, 11 Mar 2015 17:44:58 +0000 (UTC) Received: from ivory.wynn.com (mail.wynn.com [199.89.147.3]) (authenticated bits=0) by wa3yre.wynn.com (8.14.3/8.12.6) with ESMTP id t2BHir8D094651; Wed, 11 Mar 2015 13:44:53 -0400 (EDT) (envelope-from freebsd-arm@wynn.com) Date: Wed, 11 Mar 2015 13:44:52 -0400 From: Brett Wynkoop To: Warner Losh , freebsd-arm@freebsd.org Subject: Re: crash on writing usbstick Message-ID: <20150311134452.3abafbe3@ivory.wynn.com> In-Reply-To: <4DC157E8-54FD-4DEA-B437-19470E838C03@bsdimp.com> References: <20150301041855.5352663e@ivory.wynn.com> <20150301144653.63b38cdf@ivory.wynn.com> <20150301184456.7b5e6487@ivory.wynn.com> <1DC8221F-64EA-418C-8CE5-5FFA4F3DBC64@bsdimp.com> <20150301210558.3fbdb18b@ivory.wynn.com> <20150302011446.6743ae97@ivory.wynn.com> <7C0DC8EC-3DC5-4731-8711-45CD1E8C396C@bsdimp.com> <20150302130248.18e80010@ivory.wynn.com> <20150302144013.2ea4283e@ivory.wynn.com> <4DC157E8-54FD-4DEA-B437-19470E838C03@bsdimp.com> X-Mailer: Claws Mail 3.10.1 (GTK+ 2.24.25; x86_64-apple-darwin10.8.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Mar 2015 17:44:58 -0000 Greeting- I just finished a copy of /usr/ports to /export/ports in this manner tar cpf - . | (cd /export/ports ; tar xpvf -) With no incident. At this time /export/ports is a zfs in the zpool bbexport with compression turned on and atime off. To try and stress things again I am doing the same copy again, but with the source on an nfs share. It looks like the copy from NFS will take longer based on my current iostats figures. -Brett -- wynkoop@wynn.com http://prd4.wynn.com/wynkoop/pgp-keys.txt 917-642-6925 929-272-0000 If cowardly and dishonorable men sometimes shoot unarmed men with army pistols or guns, the evil must be prevented by the penitentiary and gallows, and not by a general deprivation of a constitutional privilege. -Honorable J. A. Williams, Circuit Judge - Wilson v. State, 33 Ark. 557, 34 Am. Rep. 52 (1878). From owner-freebsd-arm@FreeBSD.ORG Wed Mar 11 19:28:41 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 08A1FB5F for ; Wed, 11 Mar 2015 19:28:41 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [IPv6:2001:4f8:3:ffe0:406a:0:50:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D497CF20 for ; Wed, 11 Mar 2015 19:28:40 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [127.0.1.5]) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9) with ESMTP id t2BJSeaP028400 for ; Wed, 11 Mar 2015 19:28:40 GMT (envelope-from root@phabric-backend.isc.freebsd.org) Received: (from root@localhost) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9/Submit) id t2BJSeBO028399; Wed, 11 Mar 2015 19:28:40 GMT (envelope-from root) Date: Wed, 11 Mar 2015 19:28:40 +0000 To: freebsd-arm@freebsd.org From: "emaste (Ed Maste)" Subject: [Differential] [Commented On] D2005: Start of arm64 toolchain support (sufficient for kernel-toolchain) Message-ID: X-Priority: 3 Thread-Topic: D2005: Start of arm64 toolchain support (sufficient for kernel-toolchain) X-Herald-Rules: <23> X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: X-Phabricator-Cc: X-Phabricator-Cc: In-Reply-To: References: Thread-Index: MWIwYjI4MjVhOWQ4NTczNDM4ZTQ0MzM1OTZhIFUAl2g= X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Mar 2015 19:28:41 -0000 emaste added inline comments. INLINE COMMENTS lib/msun/arm64/Makefile.inc:3 comment removed in https://github.com/FreeBSDFoundation/freebsd/commit/8307ba52dc092da14233633905b973d3a0229898 after value updated in https://github.com/FreeBSDFoundation/freebsd/commit/89fb7f64e4a938d05f387f8c6dea4bfc6c4882e7 REVISION DETAIL https://reviews.freebsd.org/D2005 To: emaste, bdrewery Cc: imp, andrew, freebsd-arm From owner-freebsd-arm@FreeBSD.ORG Wed Mar 11 20:27:51 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B5570193 for ; Wed, 11 Mar 2015 20:27:51 +0000 (UTC) Received: from mail-pa0-f54.google.com (mail-pa0-f54.google.com [209.85.220.54]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 81D308E0 for ; Wed, 11 Mar 2015 20:27:51 +0000 (UTC) Received: by pabli10 with SMTP id li10so14098125pab.13 for ; Wed, 11 Mar 2015 13:27:45 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; bh=Vh5h8N9m+7Fu4lCHiICszzygwobNzcaaaMjiQ9ptupY=; b=Ey6ojaAgnC1un4g27E5d4IyS1K8ExQ/elGNzydCJcxAcIn5XBbrqsl+yiG2Thr9Gdo R0/D2mzsJJhGudcTJ521FEhJkPBgSQdlMYj8qrty+wt/M3UNUcQTgD7bbD6/wL/kPkpd gqE/VOGmU4zq0XM4Pt0444jVHwTS5XeSEyGM0YdmLbM0V6CIt5tydHeQYCvQFTFMzJfm 5jLJKJ+9cO49WgSxUOuZltQ0qmSYQDNA36yEeqXP67FkqDPqAEskGTwXZxWYuzXm/aa4 BJAUGvxtSsqIt/gwmDAEOVo2R0ysDxcAt0P+3BshTdp/jILzsgVbr9tRdaR5eo1giXDL wexg== X-Gm-Message-State: ALoCoQnLwRP2bio/jw0iECp2nI/2ifnabDucYjMHSuR6+qiX6cSvhcyMvHLEynu4eLYiUw9XKaRA X-Received: by 10.66.121.161 with SMTP id ll1mr45500031pab.131.1426105664739; Wed, 11 Mar 2015 13:27:44 -0700 (PDT) Received: from [192.168.18.6] (221x253x176x170.ap221.ftth.ucom.ne.jp. [221.253.176.170]) by mx.google.com with ESMTPSA id hk6sm7324589pdb.83.2015.03.11.13.27.42 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 11 Mar 2015 13:27:43 -0700 (PDT) Sender: Warner Losh Subject: Re: BBB freebsd-current backtrace. why? Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) Content-Type: multipart/signed; boundary="Apple-Mail=_CB08C7FF-B9EA-4A6B-BCB5-B5D9C0755ECF"; protocol="application/pgp-signature"; micalg=pgp-sha512 X-Pgp-Agent: GPGMail 2.5b5 From: Warner Losh In-Reply-To: <1426083066.33324.34.camel@freebsd.org> Date: Thu, 12 Mar 2015 05:27:40 +0900 Message-Id: <5C9C39FF-CB6D-45B8-A957-06AC5BF5ED91@bsdimp.com> References: <1426083066.33324.34.camel@freebsd.org> To: Ian Lepore X-Mailer: Apple Mail (2.2070.6) Cc: "freebsd-arm@freebsd.org" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Mar 2015 20:27:51 -0000 --Apple-Mail=_CB08C7FF-B9EA-4A6B-BCB5-B5D9C0755ECF Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On Mar 11, 2015, at 11:11 PM, Ian Lepore wrote: >=20 > On Tue, 2015-03-10 at 21:09 -0700, jungle Boogie wrote: >> Hi Jason, >> On 10 March 2015 at 19:05, Jason Birch wrote: >>>=20 >>> They're lock order reversals, as enabled by the WITNESS kernel = option. You >>> probably don't need to worry, but it's helpful to check if they've = been >>> reported and, if not, report them. >>>=20 >>> You might be running into this one: >>> http://sources.zabbadoz.net/freebsd/lor/261.html >>>=20 >>> Quick Googling turns up these resources: >>>=20 >>> lock order reversals - what do they mean?: >>> = https://lists.freebsd.org/pipermail/freebsd-current/2003-December/016617.h= tml >>> Glossary of Kernel Options for Debugging: >>> = https://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-optio= ns.html >>> FreeBSD LOR(lock order reversal)s seen and comments: >>> http://sources.zabbadoz.net/freebsd/lor.html >>=20 >> Based on what Ian says, I hope these BT don't continue. Those threads >> are very likely before the BBB was made...much less had freeBSD >> running, so hopefully some progress has been made with freeBSD. >=20 > The point is that those LORs are harmless. They were declared = harmless > by the gurus who understand them, years ago, and apparently just by > issuing that proclamation, it's a closed subject and we all just have = to > live with the spewage. Except that=E2=80=99s not entirely true. There are some that are known = to be harmless, but others that aren=E2=80=99t. Sadly, there=E2=80=99s no way to mark = the harmless ones in the source. Some LoRs are harmless, others lead to deadlock. Warner --Apple-Mail=_CB08C7FF-B9EA-4A6B-BCB5-B5D9C0755ECF Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJVAKU9AAoJEGwc0Sh9sBEAgEwP/3ACP6oINMsOgVTrLuv+5nR1 vEuoTxH6cVg8KW/hhC1PvCU8PHQMfiLMNqqzB0oJ3xyDL5PWcEcLy5B9gs5li8RU m3CRvCwzuy0VF+I6yVt3NWZqh2VBiwlFzTTjw8AjjA86PN4leT+8YR6Kp7znT7iu 7M84/pkz9FiK8ujt26g8GEULGes1msFNVARrPexqKrWdAMIJjm8ZLpyPYQ717RRr 5WAC+yFVYJ38njsws0vaw9SmXG2q/uu2ouj8VpLXEYl5j68Fz41yjm6Ne+IRULpv CZmJtmhCHODOmK3VqOyVVJNHf24NrPPjfWLoHt1H2hj7NhHVShIZZ3Fx9zq8u9Pj ImUU2fdGpm73FqkALuwjBYjsf91VPLJ1EpNhu9yhk1T6wJg3C81Mwvdusm0YQxgP uV6LM5WIGHbgv0xPbZfCduLKfwZgLKRls9/Cb+/aDyuGywMZexlof/PcpURavMVR RJfAhe/ZegUTqY7iJS403mBPq5w+Gzn3Px5EOJiN+kZQqXn0jGN/VuGYEEePI627 weaKFy37Exbf+Iah+OwJIdMT4at10VMBCs8BCBHv0SjMdhQonVJAX3cPi0oEax6A NqRGkkNSNNh+UOjwLQa6PS6b8i2gnOGTugNYm2Q7HIx69BgddIy9cZKOx68YesaG Rjw8fO0c2wkmPx59kA15 =b6yD -----END PGP SIGNATURE----- --Apple-Mail=_CB08C7FF-B9EA-4A6B-BCB5-B5D9C0755ECF-- From owner-freebsd-arm@FreeBSD.ORG Wed Mar 11 20:51:24 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A0D1CA44 for ; Wed, 11 Mar 2015 20:51:24 +0000 (UTC) Received: from wa3yre.wynn.com (wa3yre.wynn.com [199.89.147.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3F177B63 for ; Wed, 11 Mar 2015 20:51:23 +0000 (UTC) Received: from ivory.wynn.com (mail.wynn.com [199.89.147.3]) (authenticated bits=0) by wa3yre.wynn.com (8.14.3/8.12.6) with ESMTP id t2BKpGmd004430 for ; Wed, 11 Mar 2015 16:51:17 -0400 (EDT) (envelope-from freebsd-arm@wynn.com) Date: Wed, 11 Mar 2015 16:51:15 -0400 From: Brett Wynkoop To: "freebsd-arm@freebsd.org" Subject: BeagleBone slow inbound net I/O Message-ID: <20150311165115.32327c5a@ivory.wynn.com> X-Mailer: Claws Mail 3.10.1 (GTK+ 2.24.25; x86_64-apple-darwin10.8.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Mar 2015 20:51:24 -0000 Greeting- So I am finding that network reads from my nfs server are timing out on the BeagleBone. I am having no similar issues with other nfs clients on my network. In an attempt to eliminate NFS as a possible reason for slowness of transferring the ports tree into the system I am now transferring by piping tar through nc. This is after I had a failure with rsync inbound on the same data. The transfer is going VERY slow. Many times slower than my transfers out of the BB to my 10.1 server. Have I managed to find a network driver issue? Any ideas how to gather more information to help get to the bottom of things? Netstat seems to provide nothing useful: [wynkoop@beaglebone ~]$ netstat -i Name Mtu Network Address Ipkts Ierrs Idrop Opkts Oerrs Coll cpsw0 1500 00:18:31:8c:a5:22 0 0 0 0 0 0 cpsw0 - 199.89.147.0 beaglebone 1117 - - 511 - - lo0 16384 36 0 0 36 0 0 lo0 - localhost ::1 0 - - 0 - - lo0 - fe80::1%lo0 fe80::1%lo0 0 - - 0 - - lo0 - your-net localhost 36 - - 36 - - [wynkoop@beaglebone ~]$ I do not believe the transfer is limited by disk i/o because zpool iostat 5 shows inferior speed as compared to when I did the copy from the sd card to the usb stick. [wynkoop@beaglebone ~]$ zpool iostat 5 capacity operations bandwidth pool alloc free read write read write ---------- ----- ----- ----- ----- ----- ----- bbexport 283M 14.1G 0 0 787 1.15K bbexport 283M 14.1G 0 5 0 28.1K bbexport 283M 14.1G 0 0 0 0 bbexport 283M 14.1G 0 0 0 0 bbexport 283M 14.1G 0 5 0 28.2K bbexport 283M 14.1G 0 0 0 0 bbexport 283M 14.1G 0 0 0 0 bbexport 283M 14.1G 0 6 0 29.6K bbexport 283M 14.1G 0 0 0 0 bbexport 283M 14.1G 0 0 0 0 bbexport 283M 14.1G 0 5 0 29.5K bbexport 283M 14.1G 0 0 0 0 -Brett -- wynkoop@wynn.com http://prd4.wynn.com/wynkoop/pgp-keys.txt 917-642-6925 929-272-0000 If cowardly and dishonorable men sometimes shoot unarmed men with army pistols or guns, the evil must be prevented by the penitentiary and gallows, and not by a general deprivation of a constitutional privilege. -Honorable J. A. Williams, Circuit Judge - Wilson v. State, 33 Ark. 557, 34 Am. Rep. 52 (1878). From owner-freebsd-arm@FreeBSD.ORG Wed Mar 11 22:58:32 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 755C4C08 for ; Wed, 11 Mar 2015 22:58:32 +0000 (UTC) Received: from mail-we0-x236.google.com (mail-we0-x236.google.com [IPv6:2a00:1450:400c:c03::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 07934B9C for ; Wed, 11 Mar 2015 22:58:32 +0000 (UTC) Received: by wevk48 with SMTP id k48so12530295wev.7 for ; Wed, 11 Mar 2015 15:58:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=0FE+ndfs4ipN/u5ZHif3EBlBBKNhvJfKJIPsPBXDFwM=; b=ESzK1+RMbOS81NmVafM49ruwmI7W/8iT19dDp9OBe4Hu2IcT4O5Lzk7/fgEnyZeT3y jXcWCJnEm9DycmSbEEe17ez/spwQTpH5vAljUIP7YaHnAGXzrsyTFtECxK9tPm8kd+lo 4/JPEF7AOMqaWb3SJtF+Ov81jkHqmvjsaLfCNq/FH4vNba7+1HzuSlig+TuGGQB65Qml nrgFod2q5fAyTa7d1qMkYysRur2i0Z6yt6eXioBATeZMaaAw0XFpqbBnp9YCCdfkaHzU ddftQFxsmHNLpU6hiE1OtDo1Hnrpz07Mic6FetxY/c7XdXVrUUolsZaNt64TTOfrlHeW vG2Q== MIME-Version: 1.0 X-Received: by 10.195.12.35 with SMTP id en3mr78846046wjd.129.1426114710297; Wed, 11 Mar 2015 15:58:30 -0700 (PDT) Received: by 10.27.214.136 with HTTP; Wed, 11 Mar 2015 15:58:30 -0700 (PDT) Date: Wed, 11 Mar 2015 15:58:30 -0700 Message-ID: Subject: dhcp-4.3.2 on armv6 From: Waitman Gobble To: "freebsd-arm@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Mar 2015 22:58:32 -0000 I ripped out all GNU autotools/gmake stuff from ISC dhcp-4.3.2 and created BSD Makefiles to avoid additional dependencies building on RPi device running FreeBSD 11.0-Current. https://github.com/waitman/dhcp-4.3.2-mod Builds in about 15 minutes on v1 B+ I was primarily interested in running the dhcpd server but it also builds dhclient and dhcrelay. If you want the api and headers they can be found in the build directory, they aren't installed. -- Waitman Gobble Los Altos California USA 510-830-7975 From owner-freebsd-arm@FreeBSD.ORG Thu Mar 12 03:29:05 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AE2B6F3F for ; Thu, 12 Mar 2015 03:29:05 +0000 (UTC) Received: from mail-oi0-f41.google.com (mail-oi0-f41.google.com [209.85.218.41]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7280FB74 for ; Thu, 12 Mar 2015 03:29:05 +0000 (UTC) Received: by oigi138 with SMTP id i138so11404592oig.4 for ; Wed, 11 Mar 2015 20:29:03 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=nQYvATMcGMgjtOCqw4sbQmlNmXnvAMjW/rG6Lj9GYE0=; b=foijEYBlPxmFiZf3Tt46JikODbRAsl89EE2/oImSeWLTMCfnj8jLFKN0bp3HYHSLeC WyDagZxvI6/kvwu4cLSU10bhVJAUyUmU0ZSGImWInBVmmat0kRCsG+6BNujuZvM2ZKHL aGVp3KqbAWer03jILB9sYHDvM2SBfqL/RhlTSFY8z7JqgBNWo1Qm2f2s2It6Uc4HQvq1 j0gg/IL3I2i1hAFtzjHlxNpleiU2Qzr1tdwFmDiGurbsNr9WypseKIY9LHmAUepJTGD+ GysRV8HQt3REUWIJX+FkH0JGv5JCDs7MqY6EQ3/L4b6uMsf3kAEhSE2FQPae/m6zUm72 N6tA== X-Gm-Message-State: ALoCoQmeR3ESGQD+vkqTZ0OIwrsYBSk+GdfrI7haFbu/mw0Xo46QEY3F0dwAJzdUtgdt45fYKORD MIME-Version: 1.0 X-Received: by 10.60.124.42 with SMTP id mf10mr4989656oeb.81.1426130536272; Wed, 11 Mar 2015 20:22:16 -0700 (PDT) Received: by 10.182.60.226 with HTTP; Wed, 11 Mar 2015 20:22:16 -0700 (PDT) X-Originating-IP: [59.167.133.100] In-Reply-To: <85F7C686-B0D3-4A48-9180-C0BA9C7DD651@gromit.dlib.vt.edu> References: <85F7C686-B0D3-4A48-9180-C0BA9C7DD651@gromit.dlib.vt.edu> Date: Thu, 12 Mar 2015 14:22:16 +1100 Message-ID: Subject: Re: BBB freebsd-current backtrace. why? From: Jason Birch To: Paul Mather Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-arm@freebsd.org" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Mar 2015 03:29:05 -0000 On Thu, Mar 12, 2015 at 1:29 AM, Paul Mather wrote: > > Related to what Ian said (re: the LOR list not being actively maintained > any more)... > > Is there value in someone stepping up and maintaining a LOR archive? The disconnect between "Always have this on and report it" and "Nobody seems to know or care" is disheartening. I'm sure there are people who care for which this information is very useful, of course. Would I be setting myself up for a world of pain if I raised my hand to do something like this? On the face of it, it seems simple enough, but I haven't been involved in the community long enough to know if it'd be problematic or valuable. It just seems like we should either 1) Care about WITNESS by default or 2) Not care about WITNESS by default, instead of straddin' it. JB From owner-freebsd-arm@FreeBSD.ORG Thu Mar 12 05:09:50 2015 Return-Path: Delivered-To: freebsd-arm@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D16DAD4 for ; Thu, 12 Mar 2015 05:09:50 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B75A4938 for ; Thu, 12 Mar 2015 05:09:50 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t2C59o1o099787 for ; Thu, 12 Mar 2015 05:09:50 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-arm@FreeBSD.org Subject: [Bug 197266] DWC interface panics ODROID-C1 Date: Thu, 12 Mar 2015 05:09:50 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: arm X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-arm@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: component assigned_to keywords Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit 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.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Mar 2015 05:09:50 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197266 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Component|kern |arm Assignee|freebsd-bugs@FreeBSD.org |freebsd-arm@FreeBSD.org Keywords| |patch --- Comment #1 from Mark Linimon --- This patch will be more likely to get attention here. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-arm@FreeBSD.ORG Thu Mar 12 13:31:15 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 139C9DDA for ; Thu, 12 Mar 2015 13:31:15 +0000 (UTC) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "raven.bwct.de", Issuer "BWCT" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 7B6659B5 for ; Thu, 12 Mar 2015 13:31:13 +0000 (UTC) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id t2CDRgN0004056 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 12 Mar 2015 14:27:43 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) 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 t2CDReEe077081 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 12 Mar 2015 14:27:40 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.14.2/8.14.2) with ESMTP id t2CDRecc028435; Thu, 12 Mar 2015 14:27:40 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.14.2/8.14.2/Submit) id t2CDReXR028434; Thu, 12 Mar 2015 14:27:40 +0100 (CET) (envelope-from ticso) Date: Thu, 12 Mar 2015 14:27:40 +0100 From: Bernd Walter To: Hellmuth Michaelis Subject: Re: beaglebone boot from eMMC Message-ID: <20150312132739.GA28385@cicely7.cicely.de> Reply-To: ticso@cicely.de References: <3DF08C65-20E3-4524-B0E1-C5C096AA0FE8@hellmuth-michaelis.de> <54BA6DB9-DC61-4A6F-B948-777BB9800F54@bocal.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD cicely7.cicely.de 7.0-STABLE i386 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-0.2 required=5.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9, DNS_FROM_AHBL_RHSBL=2.699, T_RP_MATCHES_RCVD=-0.01 autolearn=no version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de Cc: "freebsd-arm@freebsd.org" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Mar 2015 13:31:15 -0000 On Wed, Mar 11, 2015 at 11:38:39AM +0100, Hellmuth Michaelis wrote: > Further investigation shows, if i dd the local image from /dev/mmcsd0 or a fresh image from remote to /dev/mmcsd1 i get sooner or later > > GEOM_PART: integrity check failed (mmcsd1, MBR) > GEOM_PART: integrity check failed (diskid/DISK-5F817AAF, MBR) > > on the serial console. Is the internal SD broken ? > > I got similar messages when i used the copy script and during probing while start of the kernel. I remember having seen similar problems when I tried using the eMMC last year. I also used crochet and the copy script, but IIRC ended when it didn't boot. Details should be on this list somewhere. > > Am 11.03.2015 um 08:31 schrieb Emmanuel Vadot : > > > > If you have all C it means that the SoC can't find the MLO or that the MLO can't find u-boot.img I don't remember which one. > > > > -- > > Emmanuel Vadot > > > >> On 11 Mar 2015, at 08:27, Hellmuth Michaelis wrote: > >> > >> Hi, > >> > >> i???m running a recent current on a beaglebone black and i???m using crochet to build stuff. I???ve seen the copy to eMMC script in root and tried that. After running it, i checked the MSDOS and UFS partitions and it seems they are OK. But, after removing the SD card and trying to boot from the internal eMMC i just see ???C??????s coming out slowly of the serial console, nothing else is happening. Putting in the SD card and all runs well again. > >> > >> Has someone a hint what to look for to get it working ? -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-arm@FreeBSD.ORG Thu Mar 12 13:33:06 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 886B5ED9 for ; Thu, 12 Mar 2015 13:33:06 +0000 (UTC) Received: from mail-pa0-f45.google.com (mail-pa0-f45.google.com [209.85.220.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 524179D2 for ; Thu, 12 Mar 2015 13:33:05 +0000 (UTC) Received: by pablj1 with SMTP id lj1so20581193pab.8 for ; Thu, 12 Mar 2015 06:33:05 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; bh=3GRkKzocVuvmLjbtpOJrxXnkQp8C4GKTp9zjB6fHTBo=; b=BG6aOkjrTYyPU3/WTR/bldsZfwqA3IN6dvAyJvGyHLvwywJHD5SmasfQhzkyko/vEd H4NbF+ghkVebJrhXbFO0Twwk3tS10lB1RwwKUIG6impv67T/7cDYBtI0pXZJfHiqzQFE 9yrITU7c1930WykWLabSylbBpGm+OMdq7wceGNplvJ7r3cUVvICZdYtlx7YNByA0Lgrr mDDK981FkC2PuMGJrwYoqfDxX9xnV11bJtlrt37tmLiVWzSs1UGX+fQDy2kWgJaxhdaR 3yCYZO6Tk5QWur9etJgmxg37R3Cf5thcd2Rb7jyZMKMQSookOK+K6ytZeLMivEXqXAMU DuXg== X-Gm-Message-State: ALoCoQl//ap1SkW/NjN0+wxhaFlcmiaHTuCIq6adOwa5rzDebKPOcDLPkfDAotro0ZDYG0DvLFQQ X-Received: by 10.70.0.207 with SMTP id 15mr40110247pdg.56.1426167185202; Thu, 12 Mar 2015 06:33:05 -0700 (PDT) Received: from [192.168.18.23] (221x253x176x170.ap221.ftth.ucom.ne.jp. [221.253.176.170]) by mx.google.com with ESMTPSA id dl1sm11019974pdb.75.2015.03.12.06.33.03 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 12 Mar 2015 06:33:04 -0700 (PDT) Sender: Warner Losh Subject: Re: beaglebone boot from eMMC Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) Content-Type: multipart/signed; boundary="Apple-Mail=_9BE6C8E8-9B6C-4DE2-B774-D503E73825A8"; protocol="application/pgp-signature"; micalg=pgp-sha512 X-Pgp-Agent: GPGMail 2.5b5 From: Warner Losh In-Reply-To: <20150312132739.GA28385@cicely7.cicely.de> Date: Thu, 12 Mar 2015 22:33:00 +0900 Message-Id: References: <3DF08C65-20E3-4524-B0E1-C5C096AA0FE8@hellmuth-michaelis.de> <54BA6DB9-DC61-4A6F-B948-777BB9800F54@bocal.org> <20150312132739.GA28385@cicely7.cicely.de> To: ticso@cicely.de X-Mailer: Apple Mail (2.2070.6) Cc: "freebsd-arm@freebsd.org" , Hellmuth Michaelis X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Mar 2015 13:33:06 -0000 --Apple-Mail=_9BE6C8E8-9B6C-4DE2-B774-D503E73825A8 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii > On Mar 12, 2015, at 10:27 PM, Bernd Walter = wrote: >=20 > On Wed, Mar 11, 2015 at 11:38:39AM +0100, Hellmuth Michaelis wrote: >> Further investigation shows, if i dd the local image from /dev/mmcsd0 = or a fresh image from remote to /dev/mmcsd1 i get sooner or later >>=20 >> GEOM_PART: integrity check failed (mmcsd1, MBR) >> GEOM_PART: integrity check failed (diskid/DISK-5F817AAF, MBR) >>=20 >> on the serial console. Is the internal SD broken ? >>=20 >> I got similar messages when i used the copy script and during probing = while start of the kernel. >=20 > I remember having seen similar problems when I tried using the eMMC = last > year. > I also used crochet and the copy script, but IIRC ended when it didn't = boot. > Details should be on this list somewhere. Last time I looked into issues like this it was due to gpart putting too = much stock in the BIOS returned geometry. usb devices rarely match each-other, let = alone the fake geometry we return from mmcsd. I suspect the root of these = weird to diagnose issues lies here. Warner >>> Am 11.03.2015 um 08:31 schrieb Emmanuel Vadot : >>>=20 >>> If you have all C it means that the SoC can't find the MLO or that = the MLO can't find u-boot.img I don't remember which one. >>>=20 >>> -- >>> Emmanuel Vadot >>>=20 >>>> On 11 Mar 2015, at 08:27, Hellmuth Michaelis = wrote: >>>>=20 >>>> Hi, >>>>=20 >>>> i???m running a recent current on a beaglebone black and i???m = using crochet to build stuff. I???ve seen the copy to eMMC script in = root and tried that. After running it, i checked the MSDOS and UFS = partitions and it seems they are OK. But, after removing the SD card and = trying to boot from the internal eMMC i just see ???C??????s coming out = slowly of the serial console, nothing else is happening. Putting in the = SD card and all runs well again. >>>>=20 >>>> Has someone a hint what to look for to get it working ? >=20 > -- > B.Walter http://www.bwct.de > Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. > _______________________________________________ > freebsd-arm@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" --Apple-Mail=_9BE6C8E8-9B6C-4DE2-B774-D503E73825A8 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJVAZWNAAoJEGwc0Sh9sBEADYUQAJjCz3pgfkEv8yTnJyNBhjtW p5FZVZlxqvZqiXSNnRFcqY4xLuU8cVFFTtDStg7paPavrMJH68lyB7aSVZb69xIG +Q7Pd8KH2wZ7VYtWfAplp3PYid2tPG2XW5akbf1jNcARIPRT6Ftn7H3ubWxyAQrn 4hdS7EYaEz5M1bhyHRdjj5Nayv00hpxsNb+CuLfeXCKOoxikXh5vGS6WibpoOMsl agjauZXVpA+fwuV55CQmQlBtpFh4mWVJ+cywaLi6D6qinAhs23IFCn6OmD/FrFlo VUqRIMSWio6HwGWK3BhvaP0ZpHYHAVxO4FoEKFp7gjeHnJ8dSmEMf2xhIK6bDR0I cZF8R3YN/eXTMsdlh9xppYK/GEHYO8CrV5tmWTEon9KGnOEjYQ8GUBtb6iUHQ+TO nMeQeUCY5iipuqSInwdOvMhK1KpSjrjtWmNu+/4wesAet0FFgXDeNq/jR/Ls7Yjb JwRTD3xoG3V5/UEhwm9iZRp59Q/JZfjapqVZABtPjeTopwRmwlSQck0+yO0KkxHW Hd6w2Xcy8sNeFLioINXglM23L3WMNL9spd7CePoeXe/DcHZnU9PFbe3j5V9zyffw ZbrL0XqYa8gMNZuQ66R3MlANTVIOr32gxnb8s1Da8SRoTfgGqf/oXmLSu+qzxMiH SVQYcHC4RL1SoQUjKUQc =x45Y -----END PGP SIGNATURE----- --Apple-Mail=_9BE6C8E8-9B6C-4DE2-B774-D503E73825A8-- From owner-freebsd-arm@FreeBSD.ORG Thu Mar 12 13:34:42 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1FAC2F44 for ; Thu, 12 Mar 2015 13:34:42 +0000 (UTC) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "raven.bwct.de", Issuer "BWCT" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id A7A019E9 for ; Thu, 12 Mar 2015 13:34:41 +0000 (UTC) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id t2CDYbkR004360 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 12 Mar 2015 14:34:37 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) 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 t2CDYYFJ077147 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 12 Mar 2015 14:34:35 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.14.2/8.14.2) with ESMTP id t2CDYYbb028474; Thu, 12 Mar 2015 14:34:34 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.14.2/8.14.2/Submit) id t2CDYYhi028473; Thu, 12 Mar 2015 14:34:34 +0100 (CET) (envelope-from ticso) Date: Thu, 12 Mar 2015 14:34:34 +0100 From: Bernd Walter To: Brett Wynkoop Subject: Re: BeagleBone slow inbound net I/O Message-ID: <20150312133433.GB28385@cicely7.cicely.de> Reply-To: ticso@cicely.de References: <20150311165115.32327c5a@ivory.wynn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150311165115.32327c5a@ivory.wynn.com> X-Operating-System: FreeBSD cicely7.cicely.de 7.0-STABLE i386 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-0.2 required=5.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9, DNS_FROM_AHBL_RHSBL=2.699, T_RP_MATCHES_RCVD=-0.01 autolearn=no version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de Cc: "freebsd-arm@freebsd.org" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Mar 2015 13:34:42 -0000 On Wed, Mar 11, 2015 at 04:51:15PM -0400, Brett Wynkoop wrote: > Greeting- > > So I am finding that network reads from my nfs server are timing out on > the BeagleBone. I am having no similar issues with other nfs clients > on my network. > > In an attempt to eliminate NFS as a possible reason for slowness of > transferring the ports tree into the system I am now transferring by > piping tar through nc. This is after I had a failure with rsync > inbound on the same data. The transfer is going VERY slow. Many times > slower than my transfers out of the BB to my 10.1 server. > > Have I managed to find a network driver issue? Any ideas how to gather > more information to help get to the bottom of things? > > Netstat seems to provide nothing useful: > > [wynkoop@beaglebone ~]$ netstat -i > Name Mtu Network Address Ipkts Ierrs Idrop Opkts Oerrs Coll > cpsw0 1500 00:18:31:8c:a5:22 0 0 0 0 0 0 > cpsw0 - 199.89.147.0 beaglebone 1117 - - 511 - - > lo0 16384 36 0 0 36 0 0 > lo0 - localhost ::1 0 - - 0 - - > lo0 - fe80::1%lo0 fe80::1%lo0 0 - - 0 - - > lo0 - your-net localhost 36 - - 36 - - > [wynkoop@beaglebone ~]$ > > I do not believe the transfer is limited by disk i/o because > zpool iostat 5 shows inferior speed as compared to when I did the copy from > the sd card to the usb stick. Use gstat to monitor disks. If the flash disk is cause the slowness then you likely see a large L(q) and high ms/w. Do not care about %busy - this is an interesting value, but missleading. It is not unlikely for small flash based devices to have problems to keep up with writing - big SSD with many flash chips and decent controller chips balance writes over chips to overcome this issue. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-arm@FreeBSD.ORG Thu Mar 12 13:45:35 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D1BDA3DB for ; Thu, 12 Mar 2015 13:45:35 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [IPv6:2001:4f8:3:ffe0:406a:0:50:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A9846B63 for ; Thu, 12 Mar 2015 13:45:35 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [127.0.1.5]) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9) with ESMTP id t2CDjZSg064442 for ; Thu, 12 Mar 2015 13:45:35 GMT (envelope-from root@phabric-backend.isc.freebsd.org) Received: (from root@localhost) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9/Submit) id t2CDjZqY064441; Thu, 12 Mar 2015 13:45:35 GMT (envelope-from root) Date: Thu, 12 Mar 2015 13:45:35 +0000 To: freebsd-arm@freebsd.org From: "zbb (Zbigniew Bodek)" Subject: [Differential] [Commented On] D1810: Leave HYP mode upon startup Message-ID: X-Priority: 3 Thread-Topic: D1810: Leave HYP mode upon startup X-Herald-Rules: none X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: X-Phabricator-Cc: X-Phabricator-Cc: X-Phabricator-Cc: In-Reply-To: References: Thread-Index: ZjlkNDcyMzZlMWIyNDBkZTI1NTY5ZjZiZGRjIFUBmH8= X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Mar 2015 13:45:35 -0000 zbb added a comment. Any response to the newest revision? REVISION DETAIL https://reviews.freebsd.org/D1810 To: zbb, andrew, ian Cc: emaste, marius, imp, freebsd-arm From owner-freebsd-arm@FreeBSD.ORG Thu Mar 12 17:09:15 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C04F2FFC for ; Thu, 12 Mar 2015 17:09:15 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [IPv6:2001:4f8:3:ffe0:406a:0:50:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A0F83A31 for ; Thu, 12 Mar 2015 17:09:15 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [127.0.1.5]) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9) with ESMTP id t2CH9F7e073144 for ; Thu, 12 Mar 2015 17:09:15 GMT (envelope-from root@phabric-backend.isc.freebsd.org) Received: (from root@localhost) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9/Submit) id t2CH9FSm073143; Thu, 12 Mar 2015 17:09:15 GMT (envelope-from root) Date: Thu, 12 Mar 2015 17:09:15 +0000 To: freebsd-arm@freebsd.org From: "zbb (Zbigniew Bodek)" Subject: [Differential] [Commented On] D2018: Introduce Annapurna Labs AHCI support Message-ID: <25a970433c6e978495538323b05792ff@localhost.localdomain> X-Priority: 3 Thread-Topic: D2018: Introduce Annapurna Labs AHCI support X-Herald-Rules: none X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: In-Reply-To: References: Thread-Index: ZGMxZTcyZjQyYTA3MjQzZjU5NjlmODc0YTQ5IFUByDs= X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Mar 2015 17:09:15 -0000 zbb added a comment. So what do we do with this patch? REVISION DETAIL https://reviews.freebsd.org/D2018 To: zbb, mav, imp, smh Cc: freebsd-arm From owner-freebsd-arm@FreeBSD.ORG Thu Mar 12 17:24:38 2015 Return-Path: Delivered-To: freebsd-arm@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3745F9AA for ; Thu, 12 Mar 2015 17:24:38 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1E24BC64 for ; Thu, 12 Mar 2015 17:24:38 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t2CHObLg019224 for ; Thu, 12 Mar 2015 17:24:37 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-arm@FreeBSD.org Subject: [Bug 197266] DWC interface panics ODROID-C1 Date: Thu, 12 Mar 2015 17:24:38 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: arm X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: john@feith.com X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-arm@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit 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.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Mar 2015 17:24:38 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197266 --- Comment #2 from john@feith.com --- I believe Ruslan Bukin address this in commit 278670. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-arm@FreeBSD.ORG Thu Mar 12 20:15:21 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BE784F5 for ; Thu, 12 Mar 2015 20:15:21 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [IPv6:2001:4f8:3:ffe0:406a:0:50:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9E81737E for ; Thu, 12 Mar 2015 20:15:21 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [127.0.1.5]) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9) with ESMTP id t2CKFLjT068354 for ; Thu, 12 Mar 2015 20:15:21 GMT (envelope-from root@phabric-backend.isc.freebsd.org) Received: (from root@localhost) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9/Submit) id t2CKFLKn068353; Thu, 12 Mar 2015 20:15:21 GMT (envelope-from root) Date: Thu, 12 Mar 2015 20:15:21 +0000 To: freebsd-arm@freebsd.org From: "imp (Warner Losh)" Subject: [Differential] [Commented On] D2018: Introduce Annapurna Labs AHCI support Message-ID: X-Priority: 3 Thread-Topic: D2018: Introduce Annapurna Labs AHCI support X-Herald-Rules: none X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: In-Reply-To: References: Thread-Index: ZGMxZTcyZjQyYTA3MjQzZjU5NjlmODc0YTQ5IFUB89k= X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Mar 2015 20:15:21 -0000 imp added inline comments. INLINE COMMENTS sys/dev/ahci/ahci.c:150-153 We should document this then. Add a comment that states that some platforms, specifically BLAH, require writing to this read-only register so a quirk is provided to update them and prevent writing to standard conforming devices. This way we know we can eliminate it if it turns out that the current root-cause analysis proves to be inaccurate or better worked around. sys/dev/ahci/ahci.c:199-201 I'd add a comment here as well so we know why we do this weird, odd-ball thing. It will also help reduce the temptation to cut and paste it for devices that clearly don't need it. REVISION DETAIL https://reviews.freebsd.org/D2018 To: zbb, mav, imp, smh Cc: freebsd-arm From owner-freebsd-arm@FreeBSD.ORG Thu Mar 12 21:44:39 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1B161676 for ; Thu, 12 Mar 2015 21:44:39 +0000 (UTC) Received: from mail-ob0-x234.google.com (mail-ob0-x234.google.com [IPv6:2607:f8b0:4003:c01::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D1C82F2D for ; Thu, 12 Mar 2015 21:44:38 +0000 (UTC) Received: by obcuz6 with SMTP id uz6so17001076obc.5 for ; Thu, 12 Mar 2015 14:44:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=HzQh6EWij9SkpbhuD7M3iS/x+7iSmV8wwpkaEwhtxWY=; b=VJxBEai0fuX9yveuf7Qoom5cE6yUaudkzcd7zcAr31EwD3044qAtZX8gkBsqWIoduw FS4G91hR2SzsI7GWq9Pr7PEwMubPkTtb9rfxAOM+s/GI6GXTL9ki/sryVtugvYwl9/uQ cv9ATh6LpEUEZImoGQ8f2BZj88jGRTTqb2WXmqK6xViga/WbU6o+qjtmZTanVs/HYs3P X6H8CXeGdteXkEhLVGVPR/U1Jz5XALboyELF3qcOxQV9ml5iQXw6vVDlB8/j56vXMu9d vdCN7M7U6eIZr7Gr5HxA2vsqK4ALkeY9jnuQCYUoR4+BLCkRdn4n1mboMMxsAdWleixP fP3Q== MIME-Version: 1.0 X-Received: by 10.182.60.197 with SMTP id j5mr35857640obr.85.1426196678194; Thu, 12 Mar 2015 14:44:38 -0700 (PDT) Received: by 10.182.247.74 with HTTP; Thu, 12 Mar 2015 14:44:38 -0700 (PDT) In-Reply-To: <20150311130932.3493a938@ivory.wynn.com> References: <20150311130932.3493a938@ivory.wynn.com> Date: Thu, 12 Mar 2015 14:44:38 -0700 Message-ID: Subject: Re: zfs on BeagleBone From: jungle Boogie To: Brett Wynkoop Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-arm@freebsd.org" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Mar 2015 21:44:39 -0000 Hi Brett, On 11 March 2015 at 10:09, Brett Wynkoop wrote: > I am shocked it is working at all considering I could not get a 384M > x86 box to run with zfs! This is great to hear! Nice progress. pkgs coming to arm6 and arm7 and zfs having a POF on arm is pretty amazing. -- ------- inum: 883510009027723 sip: jungleboogie@sip2sip.info xmpp: jungle-boogie@jit.si From owner-freebsd-arm@FreeBSD.ORG Fri Mar 13 00:59:34 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 47CFA3CD for ; Fri, 13 Mar 2015 00:59:34 +0000 (UTC) Received: from gromit.dlib.vt.edu (gromit.dlib.vt.edu [128.173.126.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gromit.dlib.vt.edu", Issuer "Chumby Certificate Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 1D8829CF for ; Fri, 13 Mar 2015 00:59:33 +0000 (UTC) Received: from gromit.chumby.lan (c-71-63-94-21.hsd1.va.comcast.net [71.63.94.21]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gromit.dlib.vt.edu (Postfix) with ESMTPSA id C8DB73A0 for ; Thu, 12 Mar 2015 20:59:25 -0400 (EDT) From: Paul Mather Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: How to use u-boot-beaglebone port? Message-Id: <17B779D7-2962-4455-9062-51411F316648@gromit.dlib.vt.edu> Date: Thu, 12 Mar 2015 20:59:24 -0400 To: "freebsd-arm@freebsd.org" Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) X-Mailer: Apple Mail (2.1878.6) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Mar 2015 00:59:34 -0000 Has anyone successfully used the sysutils/u-boot-beaglebone port? I managed to build [1] and install it today. I tried to install it to = the SD card FAT partition, as per the README, and the result was an = unbootable system. When I copied the u-boot.img file as u-boot.img (rather than the = bb-uboot.img as suggested in the README), I got it to start up to the = "U-Boot#" prompt. However, it complained about not being able to load = ubldr. There isn't a ubldr installed by the u-boot-beaglebone port, so I copied = the version from /boot/ubldr to the FAT partition. That got it a little = bit further, but now it hangs after reading ubldr. This is what I get: =3D=3D=3D=3D=3D8<=3D=3D=3D=3D=3D U-Boot SPL 2014.10 (Mar 12 2015 - 14:38:55) MMC: block number 0x100 exceeds max(0x0) MMC: block number 0x200 exceeds max(0x0) *** Error - No Valid Environment Area found Using default environment reading u-boot.img reading u-boot.img U-Boot 2014.10 (Mar 12 2015 - 14:38:55) Watchdog enabled I2C: ready DRAM: 512 MiB MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1 reading u-boot.env ** Unable to read "u-boot.env" from mmc0:1 ** Using default environment Net: not set. Validating first E-fuse MAC cpsw, usb_ether reading uEnv.txt Hit any key to stop autoboot: 0=20 Booting from: mmc 0 ubldr reading ubldr 201900 bytes read in 18 ms (10.7 MiB/s) =3D=3D=3D=3D=3D>8=3D=3D=3D=3D=3D After a while, I guess the watchdog kicks in and the whole cycle = repeats. I guess I can always restore the FAT partition to its original state, = but it would be nice to know how to use the u-boot-beaglebone port files = now I have them. Cheers, Paul. [1] It required removing "CPUTYPE?=3Dnative" from my make.conf before = devel/arm-none-eabi-gcc would build.= From owner-freebsd-arm@FreeBSD.ORG Fri Mar 13 01:05:04 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 92A7049A for ; Fri, 13 Mar 2015 01:05:04 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [IPv6:2001:4f8:3:ffe0:406a:0:50:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 70C95AB7 for ; Fri, 13 Mar 2015 01:05:04 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [127.0.1.5]) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9) with ESMTP id t2D154jW069090 for ; Fri, 13 Mar 2015 01:05:04 GMT (envelope-from root@phabric-backend.isc.freebsd.org) Received: (from root@localhost) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9/Submit) id t2D154tX069089; Fri, 13 Mar 2015 01:05:04 GMT (envelope-from root) Date: Fri, 13 Mar 2015 01:05:04 +0000 To: freebsd-arm@freebsd.org From: "emaste (Ed Maste)" Subject: [Differential] [Updated, 599 lines] D2005: Start of arm64 toolchain support (sufficient for kernel-toolchain) Message-ID: X-Priority: 3 Thread-Topic: D2005: Start of arm64 toolchain support (sufficient for kernel-toolchain) X-Herald-Rules: <23> X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: X-Phabricator-Cc: X-Phabricator-Cc: X-Phabricator-Cc: In-Reply-To: References: Thread-Index: MWIwYjI4MjVhOWQ4NTczNDM4ZTQ0MzM1OTZhIFUCN8A= X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: , , , MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Mar 2015 01:05:04 -0000 emaste updated this revision to Diff 4203. emaste added a comment. Herald added a subscriber: bdrewery. Rebased and incorporated changes that have gone into HEAD (e.g. BROKEN_OPTIONS) CHANGES SINCE LAST UPDATE https://reviews.freebsd.org/D2005?vs=4099&id=4203 REVISION DETAIL https://reviews.freebsd.org/D2005 AFFECTED FILES Makefile Makefile.inc1 etc/etc.arm64/ttys lib/csu/arm64/Makefile lib/csu/arm64/crt1.c lib/csu/arm64/crti.S lib/csu/arm64/crtn.S lib/libc/arm64/Makefile.inc lib/libthr/arch/arm64/Makefile.inc lib/msun/arm64/Makefile.inc lib/msun/arm64/fenv.h share/mk/bsd.endian.mk share/mk/src.opts.mk share/mk/sys.mk To: emaste, bdrewery Cc: bdrewery, imp, andrew, freebsd-arm From owner-freebsd-arm@FreeBSD.ORG Fri Mar 13 03:26:49 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AB10E304 for ; Fri, 13 Mar 2015 03:26:49 +0000 (UTC) Received: from wa3yre.wynn.com (wa3yre.wynn.com [199.89.147.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 55CA8D7E for ; Fri, 13 Mar 2015 03:26:49 +0000 (UTC) Received: from ivory.wynn.com (mail.wynn.com [199.89.147.3]) (authenticated bits=0) by wa3yre.wynn.com (8.14.3/8.12.6) with ESMTP id t2D3QhYn008904; Thu, 12 Mar 2015 23:26:43 -0400 (EDT) (envelope-from freebsd-arm@wynn.com) Date: Thu, 12 Mar 2015 23:26:41 -0400 From: Brett Wynkoop To: Bernd Walter Subject: Re: BeagleBone slow inbound net I/O Message-ID: <20150312232641.4365263d@ivory.wynn.com> In-Reply-To: <20150312133433.GB28385@cicely7.cicely.de> References: <20150311165115.32327c5a@ivory.wynn.com> <20150312133433.GB28385@cicely7.cicely.de> X-Mailer: Claws Mail 3.10.1 (GTK+ 2.24.25; x86_64-apple-darwin10.8.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: "freebsd-arm@freebsd.org" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Mar 2015 03:26:49 -0000 Greeting- It is confirmed, the net I/O is much slower than reading from the SD card. Here is another run of tar - pipe - tar, but this time the source is the sd card and the destination is still the USB zfs. root@beaglebone:/usr/local/bin # zpool iostat 5 capacity operations bandwidth pool alloc free read write read write ---------- ----- ----- ----- ----- ----- ----- bbexport 295M 14.1G 0 3 27.9K 26.9K bbexport 297M 14.1G 0 10 25.5K 445K bbexport 298M 14.1G 0 9 25.4K 346K bbexport 300M 14.1G 0 9 51.0K 383K bbexport 302M 14.1G 0 12 0 452K bbexport 304M 14.1G 0 10 51.1K 452K bbexport 305M 14.1G 0 10 0 319K bbexport 306M 14.1G 0 8 51.2K 238K bbexport 308M 14.1G 0 11 25.7K 415K bbexport 311M 14.1G 0 14 25.4K 625K bbexport 315M 14.1G 1 23 66.8K 934K bbexport 317M 14.1G 0 11 25.5K 472K bbexport 319M 14.1G 0 14 25.5K 615K bbexport 321M 14.1G 0 8 39.0K 271K bbexport 322M 14.1G 0 8 12.7K 340K bbexport 325M 14.1G 0 11 12.8K 683K bbexport 327M 14.1G 0 9 12.7K 502K bbexport 330M 14.1G 0 11 25.4K 594K bbexport 333M 14.0G 0 12 0 689K bbexport 337M 14.0G 0 23 0 862K bbexport 340M 14.0G 0 15 25.5K 796K bbexport 342M 14.0G 0 8 0 316K bbexport 342M 14.0G 0 6 12.7K 99.7K bbexport 343M 14.0G 0 10 12.8K 261K bbexport 346M 14.0G 0 12 38.2K 534K bbexport 349M 14.0G 1 14 64.2K 688K bbexport 349M 14.0G 0 0 0 19.1K bbexport 351M 14.0G 0 11 12.6K 579K bbexport 352M 14.0G 0 13 12.7K 784K bbexport 358M 14.0G 0 15 25.4K 631K bbexport 360M 14.0G 0 14 12.7K 584K bbexport 363M 14.0G 0 13 0 634K bbexport 366M 14.0G 0 13 12.8K 561K bbexport 369M 14.0G 0 27 12.7K 1.26M bbexport 375M 14.0G 0 17 0 601K bbexport 377M 14.0G 0 12 0 551K bbexport 380M 14.0G 0 11 12.0K 604K bbexport 387M 14.0G 0 24 25.4K 1.40M bbexport 390M 14.0G 0 10 0 572K bbexport 395M 14.0G 0 19 0 1.08M bbexport 400M 14.0G 0 21 0 1.08M bbexport 405M 14.0G 0 20 0 1.07M -Brett -- wynkoop@wynn.com http://prd4.wynn.com/wynkoop/pgp-keys.txt 917-642-6925 929-272-0000 If cowardly and dishonorable men sometimes shoot unarmed men with army pistols or guns, the evil must be prevented by the penitentiary and gallows, and not by a general deprivation of a constitutional privilege. -Honorable J. A. Williams, Circuit Judge - Wilson v. State, 33 Ark. 557, 34 Am. Rep. 52 (1878). From owner-freebsd-arm@FreeBSD.ORG Fri Mar 13 03:32:38 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A87CA465 for ; Fri, 13 Mar 2015 03:32:38 +0000 (UTC) Received: from wa3yre.wynn.com (wa3yre.wynn.com [199.89.147.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 64524E33 for ; Fri, 13 Mar 2015 03:32:37 +0000 (UTC) Received: from ivory.wynn.com (mail.wynn.com [199.89.147.3]) (authenticated bits=0) by wa3yre.wynn.com (8.14.3/8.12.6) with ESMTP id t2D3WTNC009112; Thu, 12 Mar 2015 23:32:30 -0400 (EDT) (envelope-from freebsd-arm@wynn.com) Date: Thu, 12 Mar 2015 23:32:28 -0400 From: Brett Wynkoop To: freebsd-arm@freebsd.org Subject: Re: crash on writing usbstick Message-ID: <20150312233228.2d8d4bdb@ivory.wynn.com> In-Reply-To: References: <20150301041855.5352663e@ivory.wynn.com> <20150301144653.63b38cdf@ivory.wynn.com> <20150301184456.7b5e6487@ivory.wynn.com> <1DC8221F-64EA-418C-8CE5-5FFA4F3DBC64@bsdimp.com> <20150301203244.55578413@ivory.wynn.com> X-Mailer: Claws Mail 3.10.1 (GTK+ 2.24.25; x86_64-apple-darwin10.8.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Mar 2015 03:32:38 -0000 Greeting- I have done two copies of ports to my USB stick, now setup as a zfs pool with compression on and atime off, with no crashes. I could never do 2 copies in a row trying to write to UFS. I think this would point to some issue in the UFS code. Might it be time to pass the previous crash info on to Kirk as the UFS expert? -Brett -- wynkoop@wynn.com http://prd4.wynn.com/wynkoop/pgp-keys.txt 917-642-6925 929-272-0000 If cowardly and dishonorable men sometimes shoot unarmed men with army pistols or guns, the evil must be prevented by the penitentiary and gallows, and not by a general deprivation of a constitutional privilege. -Honorable J. A. Williams, Circuit Judge - Wilson v. State, 33 Ark. 557, 34 Am. Rep. 52 (1878). From owner-freebsd-arm@FreeBSD.ORG Fri Mar 13 04:14:16 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B2E1DBCD for ; Fri, 13 Mar 2015 04:14:16 +0000 (UTC) Received: from wa3yre.wynn.com (wa3yre.wynn.com [199.89.147.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2A5EE27B for ; Fri, 13 Mar 2015 04:14:15 +0000 (UTC) Received: from ivory.wynn.com (mail.wynn.com [199.89.147.3]) (authenticated bits=0) by wa3yre.wynn.com (8.14.3/8.12.6) with ESMTP id t2D4EEXF011095; Fri, 13 Mar 2015 00:14:14 -0400 (EDT) (envelope-from wynkoop@wynn.com) Date: Fri, 13 Mar 2015 00:14:08 -0400 From: Brett Wynkoop To: Brett Wynkoop Subject: Re: zfs on BeagleBone Message-ID: <20150313001408.24fc1469@ivory.wynn.com> In-Reply-To: <20150311130932.3493a938@ivory.wynn.com> References: <20150311130932.3493a938@ivory.wynn.com> X-Mailer: Claws Mail 3.10.1 (GTK+ 2.24.25; x86_64-apple-darwin10.8.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: base64 Cc: freebsd-arm@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Mar 2015 04:14:16 -0000 LS0tLS1CRUdJTiBQR1AgU0lHTkVEIE1FU1NBR0UtLS0tLQ0KSGFzaDogU0hBMQ0KDQpHcmVldGlu Zy0NCg0KSSBoYXZlIGJlZW4gYmFuZ2luZyBvbiBteSB6ZnMgZm9ybWF0ZWQgdXNiIGZsYXNoIGRy aXZlIGZvciBhIGNvdXBsZSBvZg0KZGF5cyB3aXRoIG5vIGNyYXNoZXMsIGFuZCBubyBvdGhlciBw cm9ibGVtcy4NCg0KSSB0aGluayB6ZnMgc2VlbXMgdG8gYmUgd29ya2luZyBtdWNoIGJldHRlciB0 aGFuIHVmcyBvbiBVU0IgZmxhc2ggZHJpdmVzDQppbiB0aGUgQmVhZ2xlQm9uZS4NCg0KSSBwcmV2 aW91c2x5IHBvc3RlZCBteSBzZXR0aW5ncywgYnV0IGhlcmUgdGhleSBhcmUgYWdhaW4gZm9yIGFu eW9uZQ0KZWxzZSB3aG8gd2FudHMgdG8gcnVuIFpGUyBvbiB0aGVpciBCZWFnbGVCb25lLg0KDQov ZXRjL3JjLmNvbmY6DQoNCiMNCnpmc19lbmFibGU9IllFUyINCg0KL2Jvb3QvbG9hZGVyLmNvbmY6 DQoNCnpmc19sb2FkPSJZRVMiDQoNCiMgZnJvbSB6ZnN0dW5pbmcgd2lraQ0KIw0Kdm0ua21lbV9z aXplPSIyNTZNIg0KDQp2bS5rbWVtX3NpemVfbWF4PSIyNTZNIg0KDQp2ZnMuemZzLmFyY19tYXg9 IjI0TSINCg0KdmZzLnpmcy52ZGV2LmNhY2hlLnNpemU9IjVNIg0KDQoNCldoaWxlIHRoZSBCZWFn bGVCb25lIGtlcm5lbCBjb25maWcgdGVsbHMgdGhlIHN5c3RlbSB0byBidWlsZA0Kb3BlbnNvbGFy aXMua28gSSBoYWQgdG8gbWFudWFsbHkgbG9jYXRlIHRoZSB6ZnMgbW9kdWxlIGRpciBhbmQgYnVp bGQNCmFuZCBpbnN0YWxsIGZyb20gdGhlcmUuDQoNClpmcyBhbHNvIHNlZW1zIHRvIGhhdmUgcHJl dHR5IGdvb2Qgd3JpdGUgc3BlZWQgb24gdXNiLWZsYXNoLiAgTXkgd3JpdGUNCnNwZWVkcyBvbiBj b3B5IGZyb20gdGhlIHNkIGNhcmQgdG8gdGhlIHVzYiBmbGFzaCB3ZXJlIDUgdG8gMTAgdGltZXMN CmZhc3Rlci4NCg0KLSAtQnJldHQNCg0KDQotIC0tIA0KDQp3eW5rb29wQHd5bm4uY29tICAgICAg ICAgICAgICAgaHR0cDovL3ByZDQud3lubi5jb20vd3lua29vcC9wZ3Ata2V5cy50eHQNCjkxNy02 NDItNjkyNQ0KOTI5LTI3Mi0wMDAwDQoNCklmIGNvd2FyZGx5IGFuZCBkaXNob25vcmFibGUgbWVu IHNvbWV0aW1lcyBzaG9vdCB1bmFybWVkIG1lbiB3aXRoIGFybXkgDQpwaXN0b2xzIG9yIGd1bnMs IHRoZSBldmlsIG11c3QgYmUgcHJldmVudGVkIGJ5IHRoZSBwZW5pdGVudGlhcnkgYW5kIA0KZ2Fs bG93cywgYW5kIG5vdCBieSBhIGdlbmVyYWwgZGVwcml2YXRpb24gb2YgYSBjb25zdGl0dXRpb25h bCBwcml2aWxlZ2UuDQoNCi0gLUhvbm9yYWJsZSBKLiBBLiBXaWxsaWFtcywgQ2lyY3VpdCBKdWRn ZSAtIA0KICAgICAgICAgICAgICAgICAgV2lsc29uIHYuIFN0YXRlLCAzMyBBcmsuIDU1NywgMzQg QW0uIFJlcC4gNTIgKDE4NzgpLg0KDQotLS0tLUJFR0lOIFBHUCBTSUdOQVRVUkUtLS0tLQ0KVmVy c2lvbjogR251UEcgdjINCg0KaVFFY0JBRUJBZ0FHQlFKVkFtUVZBQW9KRUs2SzN5cmMrUnVEMm5F SC9SdGM2YVovV1pjZDhNOEF0aVJobHljZA0KbVNzeWpxeUh6Q3VQMXRwdUV3Zk15TkptQ2xrTmFp UlVMRStUeHdIRTdMUEpHV3lPSWdwMG5ib1o0V0UvaGw1Yg0KaHZCR2hVS2YwTXNTcTdlUWFVN1U1 Qm5ES1R6TTZuVmRMeVhLbE51ZTd4ejE4YjJXV2pURndsS1JBNURScjBBMA0KK29TREcwYVVTemk3 N0NLeGJzVkRQZ2Y3S2FsZE1lYWF4RFpsSHEzak9oL3hKdjRDbm8yaW9LWkYwTmFRZGZTQg0KWWU0 OU8zaERXallMUVI2ZEV5NVNRT0lDTnFsZi9iYVUzV0tENTl2dk9BSzJTR3pLdndnVXJrS1RUOWFn Zlhqeg0KZXhSUEQvQTNLc2ZJSFluT2NMRFBZa3ZJYTFkK0srUklQdy9HRlVCeDh5dFZsMmlXd1gz bnAvWVZieHBRMFh3PQ0KPTVKWEgNCi0tLS0tRU5EIFBHUCBTSUdOQVRVUkUtLS0tLQ0K From owner-freebsd-arm@FreeBSD.ORG Fri Mar 13 05:19:41 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D9B011A7 for ; Fri, 13 Mar 2015 05:19:41 +0000 (UTC) Received: from st11p02mm-asmtp002.mac.com (st11p02mm-asmtp002.mac.com [17.172.220.237]) (using TLSv1.2 with cipher DHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AE03DA19 for ; Fri, 13 Mar 2015 05:19:41 +0000 (UTC) Received: from [192.168.11.180] (unknown [180.42.49.96]) by st11p02mm-asmtp002.mac.com (Oracle Communications Messaging Server 7.0.5.35.0 64bit (built Dec 4 2014)) with ESMTPSA id <0NL4003IBXGJPQ20@st11p02mm-asmtp002.mac.com> for freebsd-arm@freebsd.org; Fri, 13 Mar 2015 05:19:34 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.13.68,1.0.33,0.0.0000 definitions=2015-03-13_03:2015-03-12,2015-03-13,1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1412110000 definitions=main-1503130055 Content-type: text/plain; charset=us-ascii MIME-version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) Subject: Re: zfs on BeagleBone From: Rui Paulo In-reply-to: <20150313001408.24fc1469@ivory.wynn.com> Date: Fri, 13 Mar 2015 14:19:23 +0900 Content-transfer-encoding: quoted-printable Message-id: <15F9FA58-9412-4F45-BCB0-0C7F79FBF1F9@me.com> References: <20150311130932.3493a938@ivory.wynn.com> <20150313001408.24fc1469@ivory.wynn.com> To: Brett Wynkoop X-Mailer: Apple Mail (2.2070.6) Cc: freebsd-arm@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Mar 2015 05:19:41 -0000 On 13 Mar 2015, at 13:14, Brett Wynkoop wrote: > Zfs also seems to have pretty good write speed on usb-flash. My write > speeds on copy from the sd card to the usb flash were 5 to 10 times > faster. While it's very encouraging that ZFS is performing well on the = BeagleBone, it's, at the same time, worrisome that UFS performs so = poorly. UFS is supposed to deal very well with small embedded = systems/filesystems and ZFS is supposed to deal very well with big = systems/filesystems. I haven't really had any problems with UFS on my = BeagleBone. -- Rui Paulo From owner-freebsd-arm@FreeBSD.ORG Fri Mar 13 06:11:14 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BAE8DAD3 for ; Fri, 13 Mar 2015 06:11:14 +0000 (UTC) Received: from wa3yre.wynn.com (wa3yre.wynn.com [199.89.147.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 78ACCF5C for ; Fri, 13 Mar 2015 06:11:14 +0000 (UTC) Received: from ivory.wynn.com (mail.wynn.com [199.89.147.3]) (authenticated bits=0) by wa3yre.wynn.com (8.14.3/8.12.6) with ESMTP id t2D6BCMi022612; Fri, 13 Mar 2015 02:11:12 -0400 (EDT) (envelope-from freebsd-arm@wynn.com) Date: Fri, 13 Mar 2015 02:11:10 -0400 From: Brett Wynkoop To: Rui Paulo Subject: Re: zfs on BeagleBone Message-ID: <20150313021110.71a896c6@ivory.wynn.com> In-Reply-To: <15F9FA58-9412-4F45-BCB0-0C7F79FBF1F9@me.com> References: <20150311130932.3493a938@ivory.wynn.com> <20150313001408.24fc1469@ivory.wynn.com> <15F9FA58-9412-4F45-BCB0-0C7F79FBF1F9@me.com> X-Mailer: Claws Mail 3.10.1 (GTK+ 2.24.25; x86_64-apple-darwin10.8.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-arm@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Mar 2015 06:11:14 -0000 On Fri, 13 Mar 2015 14:19:23 +0900 Rui Paulo wrote: > While it's very encouraging that ZFS is performing well on the > BeagleBone, it's, at the same time, worrisome that UFS performs so > poorly. UFS is supposed to deal very well with small embedded > systems/filesystems and ZFS is supposed to deal very well with big > systems/filesystems. I haven't really had any problems with UFS on > my BeagleBone. I have no problem with UFS on the sd card, but UFS on ANY USB FLASH has been a failure on the BeagleBone. Are you doing UFS on USB FLASH? -Brett -- wynkoop@wynn.com http://prd4.wynn.com/wynkoop/pgp-keys.txt 917-642-6925 929-272-0000 If cowardly and dishonorable men sometimes shoot unarmed men with army pistols or guns, the evil must be prevented by the penitentiary and gallows, and not by a general deprivation of a constitutional privilege. -Honorable J. A. Williams, Circuit Judge - Wilson v. State, 33 Ark. 557, 34 Am. Rep. 52 (1878). From owner-freebsd-arm@FreeBSD.ORG Fri Mar 13 06:32:00 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EA84CCBD for ; Fri, 13 Mar 2015 06:32:00 +0000 (UTC) Received: from st11p02mm-asmtp001.mac.com (st11p02mm-asmtpout001.mac.com [17.172.220.236]) (using TLSv1.2 with cipher DHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BD25F1A1 for ; Fri, 13 Mar 2015 06:31:59 +0000 (UTC) Received: from [192.168.11.180] (unknown [180.42.49.96]) by st11p02mm-asmtp001.mac.com (Oracle Communications Messaging Server 7.0.5.35.0 64bit (built Dec 4 2014)) with ESMTPSA id <0NL5004S90T20110@st11p02mm-asmtp001.mac.com> for freebsd-arm@freebsd.org; Fri, 13 Mar 2015 06:31:53 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.13.68,1.0.33,0.0.0000 definitions=2015-03-13_03:2015-03-12,2015-03-13,1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1412110000 definitions=main-1503130069 Content-type: text/plain; charset=us-ascii MIME-version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) Subject: Re: zfs on BeagleBone From: Rui Paulo In-reply-to: <20150313021110.71a896c6@ivory.wynn.com> Date: Fri, 13 Mar 2015 15:31:42 +0900 Content-transfer-encoding: quoted-printable Message-id: References: <20150311130932.3493a938@ivory.wynn.com> <20150313001408.24fc1469@ivory.wynn.com> <15F9FA58-9412-4F45-BCB0-0C7F79FBF1F9@me.com> <20150313021110.71a896c6@ivory.wynn.com> To: Brett Wynkoop X-Mailer: Apple Mail (2.2070.6) Cc: freebsd-arm@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Mar 2015 06:32:01 -0000 On 13 Mar 2015, at 15:11, Brett Wynkoop wrote: >=20 > On Fri, 13 Mar 2015 14:19:23 +0900 > Rui Paulo wrote: >=20 >=20 >> While it's very encouraging that ZFS is performing well on the >> BeagleBone, it's, at the same time, worrisome that UFS performs so >> poorly. UFS is supposed to deal very well with small embedded >> systems/filesystems and ZFS is supposed to deal very well with big >> systems/filesystems. I haven't really had any problems with UFS on >> my BeagleBone. >=20 > I have no problem with UFS on the sd card, but UFS on ANY USB FLASH = has > been a failure on the BeagleBone. Are you doing UFS on USB FLASH? Hmm, no, I haven't tried that. I honestly have no idea why it would = work better with ZFS. -- Rui Paulo From owner-freebsd-arm@FreeBSD.ORG Fri Mar 13 07:51:21 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 193F2746 for ; Fri, 13 Mar 2015 07:51:21 +0000 (UTC) Received: from wa3yre.wynn.com (wa3yre.wynn.com [199.89.147.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C70FFAC2 for ; Fri, 13 Mar 2015 07:51:20 +0000 (UTC) Received: from ivory.wynn.com (mail.wynn.com [199.89.147.3]) (authenticated bits=0) by wa3yre.wynn.com (8.14.3/8.12.6) with ESMTP id t2D7pIpI033812; Fri, 13 Mar 2015 03:51:18 -0400 (EDT) (envelope-from freebsd-arm@wynn.com) Date: Fri, 13 Mar 2015 03:51:17 -0400 From: Brett Wynkoop To: Rui Paulo , freebsd-arm@freebsd.org Subject: Re: zfs on BeagleBone Message-ID: <20150313035117.716491dd@ivory.wynn.com> In-Reply-To: References: <20150311130932.3493a938@ivory.wynn.com> <20150313001408.24fc1469@ivory.wynn.com> <15F9FA58-9412-4F45-BCB0-0C7F79FBF1F9@me.com> <20150313021110.71a896c6@ivory.wynn.com> X-Mailer: Claws Mail 3.10.1 (GTK+ 2.24.25; x86_64-apple-darwin10.8.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Mar 2015 07:51:21 -0000 On Fri, 13 Mar 2015 15:31:42 +0900 Rui Paulo wrote: > On 13 Mar 2015, at 15:11, Brett Wynkoop wrote: > > > > On Fri, 13 Mar 2015 14:19:23 +0900 > > Rui Paulo wrote: > Hmm, no, I haven't tried that. I honestly have no idea why it would > work better with ZFS. Greeting- Maybe as another data point you could install a USB flash directly, no usb hub, to your BeagleBone and then format it with at least one UFS partation and try what I did: cd /usr/ports tar cpf - . | (cd /USBFLASH/ports ; tar xpvf -) You could also try rsync -acv . /USBFLASH/ports That too failed with UFS on the Flash Drive. It may be that no one else is seeing this problem because no one else has tried on a USB Flash Drive. I am thinking it might be something about the combination of USBFLASH and UFS. I know others say they are doing fine with rotating usb drives. -Brett -- wynkoop@wynn.com http://prd4.wynn.com/wynkoop/pgp-keys.txt 917-642-6925 929-272-0000 If cowardly and dishonorable men sometimes shoot unarmed men with army pistols or guns, the evil must be prevented by the penitentiary and gallows, and not by a general deprivation of a constitutional privilege. -Honorable J. A. Williams, Circuit Judge - Wilson v. State, 33 Ark. 557, 34 Am. Rep. 52 (1878). From owner-freebsd-arm@FreeBSD.ORG Fri Mar 13 11:55:41 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D2A1F1C8 for ; Fri, 13 Mar 2015 11:55:41 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [IPv6:2001:4f8:3:ffe0:406a:0:50:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B2F18CB5 for ; Fri, 13 Mar 2015 11:55:41 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [127.0.1.5]) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9) with ESMTP id t2DBtfIQ036070 for ; Fri, 13 Mar 2015 11:55:41 GMT (envelope-from root@phabric-backend.isc.freebsd.org) Received: (from root@localhost) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9/Submit) id t2DBtfGV036069; Fri, 13 Mar 2015 11:55:41 GMT (envelope-from root) Date: Fri, 13 Mar 2015 11:55:41 +0000 To: freebsd-arm@freebsd.org From: "zbb (Zbigniew Bodek)" Subject: [Differential] [Updated, 35 lines] D2018: Introduce Annapurna Labs AHCI support Message-ID: X-Priority: 3 Thread-Topic: D2018: Introduce Annapurna Labs AHCI support X-Herald-Rules: none X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: In-Reply-To: References: Thread-Index: ZGMxZTcyZjQyYTA3MjQzZjU5NjlmODc0YTQ5IFUC0D0= X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Mar 2015 11:55:41 -0000 zbb updated this revision to Diff 4211. CHANGES SINCE LAST UPDATE https://reviews.freebsd.org/D2018?vs=4130&id=4211 REVISION DETAIL https://reviews.freebsd.org/D2018 AFFECTED FILES sys/dev/ahci/ahci.c sys/dev/ahci/ahci.h sys/dev/ahci/ahci_pci.c To: zbb, mav, imp, smh Cc: freebsd-arm From owner-freebsd-arm@FreeBSD.ORG Fri Mar 13 12:35:02 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6CBC6865 for ; Fri, 13 Mar 2015 12:35:02 +0000 (UTC) Received: from gromit.dlib.vt.edu (gromit.dlib.vt.edu [128.173.126.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gromit.dlib.vt.edu", Issuer "Chumby Certificate Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 41EB8F7 for ; Fri, 13 Mar 2015 12:35:02 +0000 (UTC) Received: from pmather.lib.vt.edu (pmather.lib.vt.edu [128.173.126.193]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gromit.dlib.vt.edu (Postfix) with ESMTPSA id 1DE57416; Fri, 13 Mar 2015 08:35:00 -0400 (EDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: BeagleBone slow inbound net I/O From: Paul Mather In-Reply-To: <20150312232641.4365263d@ivory.wynn.com> Date: Fri, 13 Mar 2015 08:34:59 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20150311165115.32327c5a@ivory.wynn.com> <20150312133433.GB28385@cicely7.cicely.de> <20150312232641.4365263d@ivory.wynn.com> To: Brett Wynkoop X-Mailer: Apple Mail (2.1878.6) Cc: "freebsd-arm@freebsd.org" , Bernd Walter X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Mar 2015 12:35:02 -0000 On Mar 12, 2015, at 11:26 PM, Brett Wynkoop = wrote: > Greeting- >=20 > It is confirmed, the net I/O is much slower than reading from the SD > card. Here is another run of tar - pipe - tar, but this time the > source is the sd card and the destination is still the USB zfs. The Beaglebone uses a USB NIC so any I/O to/from SD card will be = competing for resources and potentially slowing things down. Have you tried outputting to /dev/null to get a more accurate sense of = how performant the network I/O alone is? Alternatively, how about using = something like benchmarks/netperf? I just tried transferring a big file from another system to my = Beaglebone Black via "nc", piping the output to /dev/null on the = Beaglebone Black, and I am maxing out the 100 Mbit connection: pmather@beaglebone:~ % netstat -w 1 -I cpsw0 input cpsw0 output packets errs idrops bytes packets errs bytes colls 0 0 0 12325666 0 0 269572 0 0 0 0 12302830 0 0 268372 0 0 0 0 12343768 0 0 291730 0 0 0 0 12281634 0 0 267910 0 0 0 0 12284722 0 0 267976 0 0 0 0 12320998 0 0 268768 0 0 0 0 12299862 0 0 268306 0 0 0 0 12290778 0 0 268150 0 0 0 0 12315002 0 0 268636 0 0 0 0 12269522 0 0 267646 0 0 0 0 12322572 0 0 268834 0 0 0 0 12328568 0 0 268900 0 0 0 0 12311974 0 0 268570 0 0 0 0 12281634 0 0 267910 0 0 0 0 12302890 0 0 268372 0 0 0 0 12304344 0 0 268438 0 0 0 0 12289264 0 0 268042 0 0 0 0 12311914 0 0 268570 0 0 0 0 12302890 0 0 268372 0 0 0 0 11554466 0 0 252070 0 0 0 0 12315002 0 0 268636 0 input cpsw0 output packets errs idrops bytes packets errs bytes colls 0 0 0 12307372 0 0 268616 0 0 0 0 12289264 0 0 268042 0 0 0 0 12314942 0 0 268636 0 0 0 0 12299862 0 0 268306 0 ^C So, from my experience, inbound network I/O is as good as can be = expected, at least on the Beaglebone Black. Cheers, Paul.= From owner-freebsd-arm@FreeBSD.ORG Fri Mar 13 13:01:04 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 78C89C5B for ; Fri, 13 Mar 2015 13:01:04 +0000 (UTC) Received: from oj.bangj.com (amt0.gin.ntt.net [129.250.11.170]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4B056402 for ; Fri, 13 Mar 2015 13:01:03 +0000 (UTC) Received: from [172.16.10.140] (gw.mountain2sea.com [71.70.135.90]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by oj.bangj.com (Postfix) with ESMTPSA id C45A41B85; Fri, 13 Mar 2015 08:48:44 -0400 (EDT) Subject: Re: BeagleBone slow inbound net I/O Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) Content-Type: multipart/signed; boundary="Apple-Mail=_0BC6C9EC-6A10-49F8-B933-10BB1F383E63"; protocol="application/pgp-signature"; micalg=pgp-sha1 X-Pgp-Agent: GPGMail 2.5b5 From: Tom Pusateri In-Reply-To: Date: Fri, 13 Mar 2015 08:52:37 -0400 Message-Id: References: <20150311165115.32327c5a@ivory.wynn.com> <20150312133433.GB28385@cicely7.cicely.de> <20150312232641.4365263d@ivory.wynn.com> To: Paul Mather X-Mailer: Apple Mail (2.2070.6) Cc: "freebsd-arm@freebsd.org" , Bernd Walter X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Mar 2015 13:01:04 -0000 --Apple-Mail=_0BC6C9EC-6A10-49F8-B933-10BB1F383E63 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii > On Mar 13, 2015, at 8:34 AM, Paul Mather = wrote: >=20 > On Mar 12, 2015, at 11:26 PM, Brett Wynkoop = wrote: >=20 >> Greeting- >>=20 >> It is confirmed, the net I/O is much slower than reading from the SD >> card. Here is another run of tar - pipe - tar, but this time the >> source is the sd card and the destination is still the USB zfs. >=20 >=20 > The Beaglebone uses a USB NIC so any I/O to/from SD card will be = competing for resources and potentially slowing things down. >=20 > Have you tried outputting to /dev/null to get a more accurate sense of = how performant the network I/O alone is? Alternatively, how about using = something like benchmarks/netperf? benchmarks/iperf is a good one too. It will figure out the maximum = bandwidth you can sustain. It's available on Linux and Mac OSX too for = the other end of the test. # run this on one side of the connection and it will start listening as = a server: % iperf -s # on the client side, pick an IP address on the server % iperf -c There's a pretty nice article here about other features of iperf too: = http://crok-linkblog.homelinux.com/links-cisco/how-to-use-iperf-properly-a= dditions-to-the-tcp-throughput-post/ Tom --Apple-Mail=_0BC6C9EC-6A10-49F8-B933-10BB1F383E63 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org iQEcBAEBAgAGBQJVAt2VAAoJEPk0GMVmUuYM/fUH/RCGFwhAQftuxgM/M5XTts/G GkDatDMmiUtE7g2K9hWj5sXdl6SduDglnseDEYF/iIgzttah9FqvkWuA8BO1mi5L tlJzfXKv/M3Wcmjxj4Kug/duDJUdTUaiXU1U6DPVgeI7FLy4C+sEoKsXkZ7M0fXi V+QEQI1xeOY3iXJ2MAPrwuyv8GqhmG1TvhJp925A1I5esXbtn4gIczKhQA+MS8Q1 OovRMO6ov3BO+SgsRpdo91e6Ox5ZHfgrjL+dt1I9T3er3TLzSbqFh85vw3g9Tbo8 DDpGMYsR5HJ9Ji9d5rA5jfusSByaYLLfEwL+CyG8vQJK/5dPQKA5uRUbkE3IKYg= =8aFb -----END PGP SIGNATURE----- --Apple-Mail=_0BC6C9EC-6A10-49F8-B933-10BB1F383E63-- From owner-freebsd-arm@FreeBSD.ORG Fri Mar 13 13:17:30 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E9A69F9A for ; Fri, 13 Mar 2015 13:17:30 +0000 (UTC) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "raven.bwct.de", Issuer "BWCT" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 76980776 for ; Fri, 13 Mar 2015 13:17:29 +0000 (UTC) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id t2DDH6cQ018594 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 13 Mar 2015 14:17:06 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) 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 t2DDH0an093320 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 13 Mar 2015 14:17:00 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.14.2/8.14.2) with ESMTP id t2DDH0HB034775; Fri, 13 Mar 2015 14:17:00 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.14.2/8.14.2/Submit) id t2DDH06F034774; Fri, 13 Mar 2015 14:17:00 +0100 (CET) (envelope-from ticso) Date: Fri, 13 Mar 2015 14:17:00 +0100 From: Bernd Walter To: Paul Mather Subject: Re: BeagleBone slow inbound net I/O Message-ID: <20150313131700.GA34648@cicely7.cicely.de> Reply-To: ticso@cicely.de References: <20150311165115.32327c5a@ivory.wynn.com> <20150312133433.GB28385@cicely7.cicely.de> <20150312232641.4365263d@ivory.wynn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD cicely7.cicely.de 7.0-STABLE i386 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-0.2 required=5.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9, DNS_FROM_AHBL_RHSBL=2.699, T_RP_MATCHES_RCVD=-0.01 autolearn=no version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de Cc: "freebsd-arm@freebsd.org" , Bernd Walter X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Mar 2015 13:17:31 -0000 On Fri, Mar 13, 2015 at 08:34:59AM -0400, Paul Mather wrote: > On Mar 12, 2015, at 11:26 PM, Brett Wynkoop wrote: > > > Greeting- > > > > It is confirmed, the net I/O is much slower than reading from the SD > > card. Here is another run of tar - pipe - tar, but this time the > > source is the sd card and the destination is still the USB zfs. > > > The Beaglebone uses a USB NIC so any I/O to/from SD card will be competing for resources and potentially slowing things down. No it does not. AFAIK the Sitara SoC even has a second NIC and can do Gbit, which is not supported byt the board. I think some or all of the beagleboards use USB for ethernet. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-arm@FreeBSD.ORG Fri Mar 13 13:56:06 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6F7AD1BD for ; Fri, 13 Mar 2015 13:56:06 +0000 (UTC) Received: from gromit.dlib.vt.edu (gromit.dlib.vt.edu [128.173.126.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gromit.dlib.vt.edu", Issuer "Chumby Certificate Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 42D0FC57 for ; Fri, 13 Mar 2015 13:56:06 +0000 (UTC) Received: from pmather.lib.vt.edu (pmather.lib.vt.edu [128.173.126.193]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gromit.dlib.vt.edu (Postfix) with ESMTPSA id DFBCD428; Fri, 13 Mar 2015 09:56:03 -0400 (EDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: BeagleBone slow inbound net I/O From: Paul Mather In-Reply-To: <20150313131700.GA34648@cicely7.cicely.de> Date: Fri, 13 Mar 2015 09:56:02 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: <2B027037-09EF-4552-9AE2-FC6E51090866@gromit.dlib.vt.edu> References: <20150311165115.32327c5a@ivory.wynn.com> <20150312133433.GB28385@cicely7.cicely.de> <20150312232641.4365263d@ivory.wynn.com> <20150313131700.GA34648@cicely7.cicely.de> To: ticso@cicely.de X-Mailer: Apple Mail (2.1878.6) Cc: "freebsd-arm@freebsd.org" , Bernd Walter X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Mar 2015 13:56:06 -0000 On Mar 13, 2015, at 9:17 AM, Bernd Walter = wrote: > On Fri, Mar 13, 2015 at 08:34:59AM -0400, Paul Mather wrote: >> On Mar 12, 2015, at 11:26 PM, Brett Wynkoop = wrote: >>=20 >>> Greeting- >>>=20 >>> It is confirmed, the net I/O is much slower than reading from the SD >>> card. Here is another run of tar - pipe - tar, but this time the >>> source is the sd card and the destination is still the USB zfs. >>=20 >>=20 >> The Beaglebone uses a USB NIC so any I/O to/from SD card will be = competing for resources and potentially slowing things down. >=20 > No it does not. My mistake; I was confusing it with the Raspberry Pi. Network = performance hasn't been too great on the Raspberry Pi in my experience. = Maybe it has improved lately, though. Cheers, Paul. From owner-freebsd-arm@FreeBSD.ORG Fri Mar 13 15:34:00 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A38A4FDD for ; Fri, 13 Mar 2015 15:34:00 +0000 (UTC) Received: from wa3yre.wynn.com (wa3yre.wynn.com [199.89.147.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3483C9AD for ; Fri, 13 Mar 2015 15:33:59 +0000 (UTC) Received: from ivory.wynn.com (mail.wynn.com [199.89.147.3]) (authenticated bits=0) by wa3yre.wynn.com (8.14.3/8.12.6) with ESMTP id t2DFXvbU073281; Fri, 13 Mar 2015 11:33:57 -0400 (EDT) (envelope-from freebsd-arm@wynn.com) Date: Fri, 13 Mar 2015 11:33:56 -0400 From: Brett Wynkoop To: Brett Wynkoop Subject: Re: Native Buildworld fails on BeagleBone Message-ID: <20150313113356.342f77a7@ivory.wynn.com> In-Reply-To: <20150310121946.13c75571@ivory.wynn.com> References: <20150310121946.13c75571@ivory.wynn.com> X-Mailer: Claws Mail 3.10.1 (GTK+ 2.24.25; x86_64-apple-darwin10.8.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-arm X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Mar 2015 15:34:00 -0000 Greeting- It seems I still can not build world. This time the sources were on the USB FLASH ZFS. At no time did I seem to run out of swap. I had 1024M swap and maxed swap use at 75%. -Brett Stack dump: 0. Program arguments: /usr/bin/c++ -cc1 -triple armv6--freebsd11.0-gnueabi -emit-obj -disable-free -main-file-name AnalysisBasedWarnings.cpp -mrelocation-model static -mdisable-fp-elim -relaxed-aliasing -masm-verbose -mconstructor-aliases -target-cpu arm1176jzf-s -target-feature +soft-float-abi -target-abi aapcs-linux -mfloat-abi soft -dwarf-column-info -coverage-file /usr/obj/export/src/lib/clang/libclangsema/AnalysisBasedWarnings.o -resource-dir /usr/bin/../lib/clang/3.5.1 -D LLVM_ON_UNIX -D LLVM_ON_FREEBSD -D __STDC_LIMIT_MACROS -D __STDC_CONSTANT_MACROS -D LLVM_DEFAULT_TARGET_TRIPLE="armv6-gnueabi-freebsd11.0" -D LLVM_HOST_TRIPLE="armv6-unknown-freebsd11.0" -D DEFAULT_SYSROOT="" -I /export/src/lib/clang/libclangsema/../../../contrib/llvm/include -I /export/src/lib/clang/libclangsema/../../../contrib/llvm/tools/clang/include -I /export/src/lib/clang/libclangsema/../../../contrib/llvm/tools/clang/lib/Sema -I . -I /export/src/lib/clang/libclangsema/../../../contrib/llvm/../../lib/clang/include -internal-isystem /usr/include/c++/v1 -O2 -Wno-c++11-extensions -std=c++11 -fdeprecated-macro -fdebug-compilation-dir /usr/obj/export/src/lib/clang/libclangsema -ferror-limit 19 -fmessage-length 80 -mstackrealign -fno-rtti -fno-signed-char -fobjc-runtime=gnustep -fdiagnostics-show-option -fcolor-diagnostics -vectorize-loops -vectorize-slp -o AnalysisBasedWarnings.o -x c++ /export/src/lib/clang/libclangsema/../../../contrib/llvm/tools/clang/lib/Sema/AnalysisBasedWarnings.cpp 1. parser at end of file 2. Per-file LLVM IR generation 3. /usr/include/c++/v1/algorithm:2654:1: Generating code for declaration 'std::__1::max' c++: error: unable to execute command: Bus error (core dumped) c++: error: clang frontend command failed due to signal (use -v to see invocation) FreeBSD clang version 3.5.1 (tags/RELEASE_351/final 225668) 20150115 Target: armv6--freebsd11.0-gnueabi Thread model: posix c++: note: diagnostic msg: PLEASE submit a bug report to https://bugs.freebsd.org/submit/ and include the crash backtrace, preprocessed source, and associated run script. c++: note: diagnostic msg: ******************** PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT: Preprocessed source(s) and associated run script(s) are located at: c++: note: diagnostic msg: /tmp/AnalysisBasedWarnings-a42e88.cpp c++: note: diagnostic msg: /tmp/AnalysisBasedWarnings-a42e88.sh c++: note: diagnostic msg: ******************** *** Error code 254 Stop. make: stopped in /export/src/lib/clang/libclangsema [root@beaglebone /export/src/lib/clang/libclangsema]# -- wynkoop@wynn.com http://prd4.wynn.com/wynkoop/pgp-keys.txt 917-642-6925 929-272-0000 April 19, 1775 An English attempt to confiscate guns from Americans triggered a successful revolution...... Dear Congress, that's a hint. From owner-freebsd-arm@FreeBSD.ORG Fri Mar 13 18:03:26 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D4504753 for ; Fri, 13 Mar 2015 18:03:26 +0000 (UTC) Received: from gromit.dlib.vt.edu (gromit.dlib.vt.edu [128.173.126.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gromit.dlib.vt.edu", Issuer "Chumby Certificate Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id A957CD75 for ; Fri, 13 Mar 2015 18:03:26 +0000 (UTC) Received: from pmather.lib.vt.edu (pmather.lib.vt.edu [128.173.126.193]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gromit.dlib.vt.edu (Postfix) with ESMTPSA id C8374460; Fri, 13 Mar 2015 14:03:24 -0400 (EDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: Native Buildworld fails on BeagleBone From: Paul Mather In-Reply-To: <20150313113356.342f77a7@ivory.wynn.com> Date: Fri, 13 Mar 2015 14:03:23 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20150310121946.13c75571@ivory.wynn.com> <20150313113356.342f77a7@ivory.wynn.com> To: Brett Wynkoop X-Mailer: Apple Mail (2.1878.6) Cc: freebsd-arm X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Mar 2015 18:03:26 -0000 On Mar 13, 2015, at 11:33 AM, Brett Wynkoop = wrote: > Greeting- >=20 > It seems I still can not build world. This time the sources were on > the USB FLASH ZFS. At no time did I seem to run out of swap. I had > 1024M swap and maxed swap use at 75%. Back in 2013 I was having problems achieving a successful native build = on FreeBSD/arm. Even when it finally worked on Raspberry Pi, it = wouldn't work on BeagleBone Black: = http://lists.freebsd.org/pipermail/freebsd-arm/2013-September/006618.html For a while, there was a lot of turmoil in FreeBSD/arm land, so I = switched to doing cross-builds on my FreeBSD/amd64 system and, when it = came time to installkernel; installworld; and mergemaster, I'd shut down = the BeagleBone Black, put the SD card into my FreeBSD/amd64 system and = do the necessary steps there. Then, I'd put the SD card back into the = BeagleBone Black and boot up the new version. That method always seemed = to work for me. The main advantage of that is I could do a buildworld/buildkernel run in = about 30 minutes instead of the > 1 day it would take natively. But, I = didn't like having to move the SD card. Like many FreeBSD users, I'm = used to being able to do a native build. But, the cross-building was a = successful workaround. When I did try in the past few months to do a native build on the = BeagleBone Black it succeeded. I don't know what had been the problem = before: some clang issue? Whatever it was, it doesn't seem to be an = issue for me now, and I've been able to do native builds both on = Raspberry Pi and BeagleBone Black. It may not simply be a matter of updating /usr/src to a known buildable = version to complete a native build. It might be that your current = installed version is not capable to doing a successful build, like mine = was. In that case, I would suggest either reinstalling from a known = good image (known to have successfully completed a native build), or = doing a cross-build and update of your existing system, like I did. I don't know if that helps, but I hope it does. BTW, my current successful native build is this one: FreeBSD beaglebone 11.0-CURRENT FreeBSD 11.0-CURRENT #2 r279886: Wed Mar = 11 13:25:57 EDT 2015 = pmather@beaglebone:/usr/obj/usr/src/sys/BEAGLEBONE-NO_WITNESS arm Cheers, Paul. >=20 > -Brett >=20 >=20 > Stack dump: > 0. Program arguments: /usr/bin/c++ -cc1 -triple > armv6--freebsd11.0-gnueabi -emit-obj -disable-free -main-file-name > AnalysisBasedWarnings.cpp -mrelocation-model static -mdisable-fp-elim > -relaxed-aliasing -masm-verbose -mconstructor-aliases -target-cpu > arm1176jzf-s -target-feature +soft-float-abi -target-abi aapcs-linux > -mfloat-abi soft -dwarf-column-info > -coverage-file = /usr/obj/export/src/lib/clang/libclangsema/AnalysisBasedWarnings.o > -resource-dir /usr/bin/../lib/clang/3.5.1 -D LLVM_ON_UNIX -D > LLVM_ON_FREEBSD -D __STDC_LIMIT_MACROS -D __STDC_CONSTANT_MACROS -D > LLVM_DEFAULT_TARGET_TRIPLE=3D"armv6-gnueabi-freebsd11.0" -D > LLVM_HOST_TRIPLE=3D"armv6-unknown-freebsd11.0" -D DEFAULT_SYSROOT=3D"" > -I /export/src/lib/clang/libclangsema/../../../contrib/llvm/include > -I = /export/src/lib/clang/libclangsema/../../../contrib/llvm/tools/clang/inclu= de > -I = /export/src/lib/clang/libclangsema/../../../contrib/llvm/tools/clang/lib/S= ema > -I . > -I = /export/src/lib/clang/libclangsema/../../../contrib/llvm/../../lib/clang/i= nclude > -internal-isystem /usr/include/c++/v1 -O2 -Wno-c++11-extensions > -std=3Dc++11 -fdeprecated-macro > -fdebug-compilation-dir /usr/obj/export/src/lib/clang/libclangsema > -ferror-limit 19 -fmessage-length 80 -mstackrealign -fno-rtti > -fno-signed-char -fobjc-runtime=3Dgnustep -fdiagnostics-show-option > -fcolor-diagnostics -vectorize-loops -vectorize-slp -o > AnalysisBasedWarnings.o -x > c++ = /export/src/lib/clang/libclangsema/../../../contrib/llvm/tools/clang/lib/S= ema/AnalysisBasedWarnings.cpp > 1. parser at end of file 2. Per-file LLVM IR = generation > 3. /usr/include/c++/v1/algorithm:2654:1: Generating code for > declaration 'std::__1::max' c++: error: unable to execute command: Bus > error (core dumped) c++: error: clang frontend command failed due to > signal (use -v to see invocation) FreeBSD clang version 3.5.1 > (tags/RELEASE_351/final 225668) 20150115 Target: > armv6--freebsd11.0-gnueabi Thread model: posix c++: note: diagnostic > msg: PLEASE submit a bug report to https://bugs.freebsd.org/submit/ = and > include the crash backtrace, preprocessed source, and associated run > script. c++: note: diagnostic msg: ******************** >=20 > PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT: > Preprocessed source(s) and associated run script(s) are located at: > c++: note: diagnostic msg: /tmp/AnalysisBasedWarnings-a42e88.cpp > c++: note: diagnostic msg: /tmp/AnalysisBasedWarnings-a42e88.sh > c++: note: diagnostic msg: >=20 > ******************** > *** Error code 254 >=20 > Stop. > make: stopped in /export/src/lib/clang/libclangsema > [root@beaglebone /export/src/lib/clang/libclangsema]#=20 >=20 >=20 > --=20 >=20 > wynkoop@wynn.com = http://prd4.wynn.com/wynkoop/pgp-keys.txt > 917-642-6925 > 929-272-0000 >=20 > April 19, 1775 An English attempt to confiscate guns from Americans > triggered a successful revolution...... >=20 > Dear Congress, that's a hint. >=20 > _______________________________________________ > freebsd-arm@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" >=20 From owner-freebsd-arm@FreeBSD.ORG Fri Mar 13 18:18:53 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 17BE8C0E for ; Fri, 13 Mar 2015 18:18:53 +0000 (UTC) Received: from relay.mailchannels.net (nov-007-i624.relay.mailchannels.net [46.232.183.178]) by mx1.freebsd.org (Postfix) with ESMTP id 0FAA0EEC for ; Fri, 13 Mar 2015 18:18:49 +0000 (UTC) X-Sender-Id: duocircle|x-authuser|hippie Received: from smtp2.ore.mailhop.org (ip-10-33-12-218.us-west-2.compute.internal [10.33.12.218]) by relay.mailchannels.net (Postfix) with ESMTPA id 9D736A01E0; Fri, 13 Mar 2015 18:18:43 +0000 (UTC) X-Sender-Id: duocircle|x-authuser|hippie Received: from smtp2.ore.mailhop.org (smtp2.ore.mailhop.org [10.45.8.167]) (using TLSv1 with cipher DHE-RSA-AES256-SHA) by 0.0.0.0:2500 (trex/5.4.8); Fri, 13 Mar 2015 18:18:44 +0000 X-MC-Relay: Neutral X-MailChannels-SenderId: duocircle|x-authuser|hippie X-MailChannels-Auth-Id: duocircle X-MC-Loop-Signature: 1426270723724:3493939974 X-MC-Ingress-Time: 1426270723724 Received: from c-73-34-117-227.hsd1.co.comcast.net ([73.34.117.227] helo=ilsoft.org) by smtp2.ore.mailhop.org with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.82) (envelope-from ) id 1YWUAS-0006ZL-90; Fri, 13 Mar 2015 18:18:40 +0000 Received: from revolution.hippie.lan (revolution.hippie.lan [172.22.42.240]) by ilsoft.org (8.14.9/8.14.9) with ESMTP id t2DIIYra016795; Fri, 13 Mar 2015 12:18:34 -0600 (MDT) (envelope-from ian@freebsd.org) X-Mail-Handler: DuoCircle Outbound SMTP X-Originating-IP: 73.34.117.227 X-Report-Abuse-To: abuse@duocircle.com (see https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information for abuse reporting information) X-MHO-User: U2FsdGVkX1+d6UTvL+kWcBxFQvelJ5mh Message-ID: <1426270714.19693.7.camel@freebsd.org> Subject: Re: BeagleBone slow inbound net I/O From: Ian Lepore To: Brett Wynkoop Date: Fri, 13 Mar 2015 12:18:34 -0600 In-Reply-To: <20150312232641.4365263d@ivory.wynn.com> References: <20150311165115.32327c5a@ivory.wynn.com> <20150312133433.GB28385@cicely7.cicely.de> <20150312232641.4365263d@ivory.wynn.com> Content-Type: text/plain; charset="us-ascii" X-Mailer: Evolution 3.12.10 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-AuthUser: hippie Cc: "freebsd-arm@freebsd.org" , Bernd Walter X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Mar 2015 18:18:53 -0000 On Thu, 2015-03-12 at 23:26 -0400, Brett Wynkoop wrote: > Greeting- > > It is confirmed, the net I/O is much slower than reading from the SD > card. Here is another run of tar - pipe - tar, but this time the > source is the sd card and the destination is still the USB zfs. [...] > You're not actually testing network performance, you're testing a confusing mashup of overall system performance. iperf on my beaglebone shows a throughput of 92mbps in both directions, which is not at all bad for a 100mbps connection. -- Ian From owner-freebsd-arm@FreeBSD.ORG Fri Mar 13 18:21:19 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4E5B4CAC for ; Fri, 13 Mar 2015 18:21:19 +0000 (UTC) Received: from relay.mailchannels.net (si-002-i157.relay.mailchannels.net [108.178.49.169]) by mx1.freebsd.org (Postfix) with ESMTP id 82E31FA7 for ; Fri, 13 Mar 2015 18:21:17 +0000 (UTC) X-Sender-Id: duocircle|x-authuser|hippie Received: from smtp7.ore.mailhop.org (ip-10-220-9-73.us-west-2.compute.internal [10.220.9.73]) by relay.mailchannels.net (Postfix) with ESMTPA id 099A212022B; Fri, 13 Mar 2015 18:21:10 +0000 (UTC) X-Sender-Id: duocircle|x-authuser|hippie Received: from smtp7.ore.mailhop.org (smtp7.ore.mailhop.org [10.45.8.167]) (using TLSv1 with cipher DHE-RSA-AES256-SHA) by 0.0.0.0:2500 (trex/5.4.8); Fri, 13 Mar 2015 18:21:10 +0000 X-MC-Relay: Neutral X-MailChannels-SenderId: duocircle|x-authuser|hippie X-MailChannels-Auth-Id: duocircle X-MC-Loop-Signature: 1426270870125:978847187 X-MC-Ingress-Time: 1426270870125 Received: from c-73-34-117-227.hsd1.co.comcast.net ([73.34.117.227] helo=ilsoft.org) by smtp7.ore.mailhop.org with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.82) (envelope-from ) id 1YWUCq-0004W9-6r; Fri, 13 Mar 2015 18:21:08 +0000 Received: from revolution.hippie.lan (revolution.hippie.lan [172.22.42.240]) by ilsoft.org (8.14.9/8.14.9) with ESMTP id t2DIL2nX016803; Fri, 13 Mar 2015 12:21:02 -0600 (MDT) (envelope-from ian@freebsd.org) X-Mail-Handler: DuoCircle Outbound SMTP X-Originating-IP: 73.34.117.227 X-Report-Abuse-To: abuse@duocircle.com (see https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information for abuse reporting information) X-MHO-User: U2FsdGVkX1+/i8dzel+styb885LQWSKJ Message-ID: <1426270862.19693.9.camel@freebsd.org> Subject: Re: crash on writing usbstick From: Ian Lepore To: Brett Wynkoop Date: Fri, 13 Mar 2015 12:21:02 -0600 In-Reply-To: <20150312233228.2d8d4bdb@ivory.wynn.com> References: <20150301041855.5352663e@ivory.wynn.com> <20150301144653.63b38cdf@ivory.wynn.com> <20150301184456.7b5e6487@ivory.wynn.com> <1DC8221F-64EA-418C-8CE5-5FFA4F3DBC64@bsdimp.com> <20150301203244.55578413@ivory.wynn.com> <20150312233228.2d8d4bdb@ivory.wynn.com> Content-Type: text/plain; charset="us-ascii" X-Mailer: Evolution 3.12.10 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-AuthUser: hippie Cc: freebsd-arm@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Mar 2015 18:21:19 -0000 On Thu, 2015-03-12 at 23:32 -0400, Brett Wynkoop wrote: > Greeting- > > I have done two copies of ports to my USB stick, now setup as a zfs > pool with compression on and atime off, with no crashes. > > I could never do 2 copies in a row trying to write to UFS. I think > this would point to some issue in the UFS code. Might it be time to > pass the previous crash info on to Kirk as the UFS expert? It's kind of hard for me to get past the fact that nobody else can reproduce these problems. In fact, I spent a whole day doing my best to exactly reproduce your test conditions, and couldn't get any kind of problem to happen at all. -- Ian From owner-freebsd-arm@FreeBSD.ORG Fri Mar 13 18:28:43 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id F1824E76 for ; Fri, 13 Mar 2015 18:28:43 +0000 (UTC) Received: from relay.mailchannels.net (aso-006-i431.relay.mailchannels.net [23.91.64.112]) by mx1.freebsd.org (Postfix) with ESMTP id 4E0D6FFA for ; Fri, 13 Mar 2015 18:28:42 +0000 (UTC) X-Sender-Id: duocircle|x-authuser|hippie Received: from smtp2.ore.mailhop.org (ip-10-213-14-133.us-west-2.compute.internal [10.213.14.133]) by relay.mailchannels.net (Postfix) with ESMTPA id 66682600AE; Fri, 13 Mar 2015 18:28:35 +0000 (UTC) X-Sender-Id: duocircle|x-authuser|hippie Received: from smtp2.ore.mailhop.org (smtp2.ore.mailhop.org [10.45.8.167]) (using TLSv1 with cipher DHE-RSA-AES256-SHA) by 0.0.0.0:2500 (trex/5.4.8); Fri, 13 Mar 2015 18:28:35 +0000 X-MC-Relay: Neutral X-MailChannels-SenderId: duocircle|x-authuser|hippie X-MailChannels-Auth-Id: duocircle X-MC-Loop-Signature: 1426271315496:165097303 X-MC-Ingress-Time: 1426271315495 Received: from c-73-34-117-227.hsd1.co.comcast.net ([73.34.117.227] helo=ilsoft.org) by smtp2.ore.mailhop.org with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.82) (envelope-from ) id 1YWUK0-00012n-VY; Fri, 13 Mar 2015 18:28:33 +0000 Received: from revolution.hippie.lan (revolution.hippie.lan [172.22.42.240]) by ilsoft.org (8.14.9/8.14.9) with ESMTP id t2DIRi11016811; Fri, 13 Mar 2015 12:27:44 -0600 (MDT) (envelope-from ian@freebsd.org) X-Mail-Handler: DuoCircle Outbound SMTP X-Originating-IP: 73.34.117.227 X-Report-Abuse-To: abuse@duocircle.com (see https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information for abuse reporting information) X-MHO-User: U2FsdGVkX196LrE0TtvhKGG9GKx/FhZM Message-ID: <1426271264.19693.13.camel@freebsd.org> Subject: Re: zfs on BeagleBone From: Ian Lepore To: Brett Wynkoop Date: Fri, 13 Mar 2015 12:27:44 -0600 In-Reply-To: <20150313035117.716491dd@ivory.wynn.com> References: <20150311130932.3493a938@ivory.wynn.com> <20150313001408.24fc1469@ivory.wynn.com> <15F9FA58-9412-4F45-BCB0-0C7F79FBF1F9@me.com> <20150313021110.71a896c6@ivory.wynn.com> <20150313035117.716491dd@ivory.wynn.com> Content-Type: text/plain; charset="us-ascii" X-Mailer: Evolution 3.12.10 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-AuthUser: hippie Cc: freebsd-arm@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Mar 2015 18:28:44 -0000 On Fri, 2015-03-13 at 03:51 -0400, Brett Wynkoop wrote: > On Fri, 13 Mar 2015 15:31:42 +0900 > Rui Paulo wrote: > > > On 13 Mar 2015, at 15:11, Brett Wynkoop wrote: > > > > > > On Fri, 13 Mar 2015 14:19:23 +0900 > > > Rui Paulo wrote: > > > Hmm, no, I haven't tried that. I honestly have no idea why it would > > work better with ZFS. > > Greeting- > > Maybe as another data point you could install a USB flash directly, no > usb hub, to your BeagleBone and then format it with at least one UFS > partation and try what I did: > > cd /usr/ports > > tar cpf - . | (cd /USBFLASH/ports ; tar xpvf -) > > You could also try > > rsync -acv . /USBFLASH/ports > > That too failed with UFS on the Flash Drive. > > It may be that no one else is seeing this problem because no one else > has tried on a USB Flash Drive. I am thinking it might be something > about the combination of USBFLASH and UFS. I know others say they are > doing fine with rotating usb drives. How many times do I have to say that I tested exactly what you said you tested (granted, we're probably using different size and brands of usb thumb drive), and couldn't reproduce the problems at all? I plugged the memory stick both into a powered hub, and directly into the beaglebone. I used the exact tar and rsync commands you did, using both nfs and ufs-on-sdcard as the source drive. No errors, the copies always completed. I think it's looking increasingly like you have bad hardware. -- Ian From owner-freebsd-arm@FreeBSD.ORG Fri Mar 13 18:39:02 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8E3655A7 for ; Fri, 13 Mar 2015 18:39:02 +0000 (UTC) Received: from mail-we0-x233.google.com (mail-we0-x233.google.com [IPv6:2a00:1450:400c:c03::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2354E1E5 for ; Fri, 13 Mar 2015 18:39:02 +0000 (UTC) Received: by wevl61 with SMTP id l61so25118123wev.10 for ; Fri, 13 Mar 2015 11:39:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=x+FseT4dbXg1b4a70JEO8SL5vSDyJA+TYreyUVFCank=; b=NSI0Z7nw+wDOt4Hk9l6qFrfzmFbu+ib2k4c//PUez4Dicjh8yITLfSk3GcpwHndmLO oRmNPZvNl2yYbHMQhH1lUbFF+yL5U24ZoqEmv0AmDqRdk/AQaGSswhAQwPSM56sWBlD2 bP2ND1T0hnWSqwizB7R00pAba+/dg50I0A/WV5PRYpkGGTz9vlF8k7kZqRoJDPrAYDZT lhu+GcgMcp8QJ2/m7wWZZZQnlvyKZflcPQWxNjApUHdEVfiXTtJokuGjs2rJAQ91ANAQ z0AVKYDe67LILCAdWLJtkreo4h7DT6drZHezWqC7cfrbOF5FwdOJNWa/jZN0fkX5CzTF UPMg== MIME-Version: 1.0 X-Received: by 10.180.90.113 with SMTP id bv17mr17895065wib.3.1426271940471; Fri, 13 Mar 2015 11:39:00 -0700 (PDT) Received: by 10.180.195.99 with HTTP; Fri, 13 Mar 2015 11:39:00 -0700 (PDT) In-Reply-To: <20150313113356.342f77a7@ivory.wynn.com> References: <20150310121946.13c75571@ivory.wynn.com> <20150313113356.342f77a7@ivory.wynn.com> Date: Fri, 13 Mar 2015 15:39:00 -0300 Message-ID: Subject: Re: Native Buildworld fails on BeagleBone From: Luiz Otavio O Souza To: Brett Wynkoop Content-Type: text/plain; charset=UTF-8 Cc: freebsd-arm X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Mar 2015 18:39:02 -0000 On 13 March 2015 at 12:33, Brett Wynkoop wrote: > Greeting- > > It seems I still can not build world. This time the sources were on > the USB FLASH ZFS. At no time did I seem to run out of swap. I had > 1024M swap and maxed swap use at 75%. > > -Brett > > > Stack dump: > 0. Program arguments: /usr/bin/c++ -cc1 -triple > armv6--freebsd11.0-gnueabi -emit-obj -disable-free -main-file-name > AnalysisBasedWarnings.cpp -mrelocation-model static -mdisable-fp-elim > -relaxed-aliasing -masm-verbose -mconstructor-aliases -target-cpu > arm1176jzf-s -target-feature +soft-float-abi -target-abi aapcs-linux It seems that arm1176jzf-s is defined at your system, with this setting you won't be able to do native builds on your BBB. Please check the /etc/make.conf contents. Luiz From owner-freebsd-arm@FreeBSD.ORG Fri Mar 13 20:26:40 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D3FE3748; Fri, 13 Mar 2015 20:26:40 +0000 (UTC) Received: from wa3yre.wynn.com (wa3yre.wynn.com [199.89.147.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8F265110; Fri, 13 Mar 2015 20:26:40 +0000 (UTC) Received: from ivory.wynn.com (mail.wynn.com [199.89.147.3]) (authenticated bits=0) by wa3yre.wynn.com (8.14.3/8.12.6) with ESMTP id t2DKQbhT031608; Fri, 13 Mar 2015 16:26:37 -0400 (EDT) (envelope-from freebsd-arm@wynn.com) Date: Fri, 13 Mar 2015 16:26:36 -0400 From: Brett Wynkoop To: Ian Lepore , freebsd-arm@freebsd.org Subject: Re: zfs on BeagleBone Message-ID: <20150313162636.65db3900@ivory.wynn.com> In-Reply-To: <1426271264.19693.13.camel@freebsd.org> References: <20150311130932.3493a938@ivory.wynn.com> <20150313001408.24fc1469@ivory.wynn.com> <15F9FA58-9412-4F45-BCB0-0C7F79FBF1F9@me.com> <20150313021110.71a896c6@ivory.wynn.com> <20150313035117.716491dd@ivory.wynn.com> <1426271264.19693.13.camel@freebsd.org> X-Mailer: Claws Mail 3.10.1 (GTK+ 2.24.25; x86_64-apple-darwin10.8.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Mar 2015 20:26:40 -0000 On Fri, 13 Mar 2015 12:27:44 -0600 Ian Lepore wrote: say they are doing fine with rotating usb drives. > > How many times do I have to say that I tested exactly what you said > you tested (granted, we're probably using different size and brands > of usb thumb drive), and couldn't reproduce the problems at all? I > plugged the memory stick both into a powered hub, and directly into > the beaglebone. I used the exact tar and rsync commands you did, > using both nfs and ufs-on-sdcard as the source drive. No errors, the > copies always completed. > > I think it's looking increasingly like you have bad hardware. Ian I am sorry. It was totally lost on me that you tested to flash. I thought everyone else that tried were writing to rotating media. It would seem we might be looking at flakey hardware, but I still have to wonder since it seems to run fine on zfs no matter what I pound it with. -Brett -- wynkoop@wynn.com http://prd4.wynn.com/wynkoop/pgp-keys.txt 917-642-6925 929-272-0000 Amendment VIII Excessive bail shall not be required, nor excessive fines imposed, nor cruel and unusual punishments inflicted. From owner-freebsd-arm@FreeBSD.ORG Fri Mar 13 20:32:19 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 740DB84A for ; Fri, 13 Mar 2015 20:32:19 +0000 (UTC) Received: from wa3yre.wynn.com (wa3yre.wynn.com [199.89.147.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 31CD11DB for ; Fri, 13 Mar 2015 20:32:18 +0000 (UTC) Received: from ivory.wynn.com (mail.wynn.com [199.89.147.3]) (authenticated bits=0) by wa3yre.wynn.com (8.14.3/8.12.6) with ESMTP id t2DKWHuM032036; Fri, 13 Mar 2015 16:32:17 -0400 (EDT) (envelope-from freebsd-arm@wynn.com) Date: Fri, 13 Mar 2015 16:32:16 -0400 From: Brett Wynkoop To: Luiz Otavio O Souza , freebsd-arm@freebsd.org Subject: Re: Native Buildworld fails on BeagleBone Message-ID: <20150313163216.2788c73e@ivory.wynn.com> In-Reply-To: References: <20150310121946.13c75571@ivory.wynn.com> <20150313113356.342f77a7@ivory.wynn.com> X-Mailer: Claws Mail 3.10.1 (GTK+ 2.24.25; x86_64-apple-darwin10.8.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Mar 2015 20:32:19 -0000 On Fri, 13 Mar 2015 15:39:00 -0300 Luiz Otavio O Souza wrote: > > Stack dump: > > 0. Program arguments: /usr/bin/c++ -cc1 -triple > > armv6--freebsd11.0-gnueabi -emit-obj -disable-free -main-file-name > > AnalysisBasedWarnings.cpp -mrelocation-model static > > -mdisable-fp-elim -relaxed-aliasing -masm-verbose > > -mconstructor-aliases -target-cpu arm1176jzf-s -target-feature > > +soft-float-abi -target-abi aapcs-linux > > It seems that arm1176jzf-s is defined at your system, with this > setting you won't be able to do native builds on your BBB. > > Please check the /etc/make.conf contents. > > Luiz root@beaglebone:/usr/obj # cat /etc/make.conf cat: /etc/make.conf: No such file or directory root@beaglebone:/usr/obj # It must have changed someplace inside /usr/src. -Brett -- wynkoop@wynn.com http://prd4.wynn.com/wynkoop/pgp-keys.txt 917-642-6925 929-272-0000 Amendment IX The enumeration in the Constitution, of certain rights, shall not be construed to deny or disparage others retained by the people. From owner-freebsd-arm@FreeBSD.ORG Fri Mar 13 23:51:41 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B9C1C821; Fri, 13 Mar 2015 23:51:41 +0000 (UTC) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "raven.bwct.de", Issuer "BWCT" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 2DBD9AC5; Fri, 13 Mar 2015 23:51:40 +0000 (UTC) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id t2DNpF22022017 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sat, 14 Mar 2015 00:51:15 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) 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 t2DNp7Yr002149 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 14 Mar 2015 00:51:07 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.14.2/8.14.2) with ESMTP id t2DNp7kd037405; Sat, 14 Mar 2015 00:51:07 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.14.2/8.14.2/Submit) id t2DNp4nO037404; Sat, 14 Mar 2015 00:51:04 +0100 (CET) (envelope-from ticso) Date: Sat, 14 Mar 2015 00:51:04 +0100 From: Bernd Walter To: Ian Lepore Subject: Re: BeagleBone slow inbound net I/O Message-ID: <20150313235104.GJ34648@cicely7.cicely.de> Reply-To: ticso@cicely.de References: <20150311165115.32327c5a@ivory.wynn.com> <20150312133433.GB28385@cicely7.cicely.de> <20150312232641.4365263d@ivory.wynn.com> <1426270714.19693.7.camel@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1426270714.19693.7.camel@freebsd.org> X-Operating-System: FreeBSD cicely7.cicely.de 7.0-STABLE i386 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-0.2 required=5.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9, DNS_FROM_AHBL_RHSBL=2.699, T_RP_MATCHES_RCVD=-0.01 autolearn=no version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de Cc: "freebsd-arm@freebsd.org" , Bernd Walter X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Mar 2015 23:51:41 -0000 On Fri, Mar 13, 2015 at 12:18:34PM -0600, Ian Lepore wrote: > On Thu, 2015-03-12 at 23:26 -0400, Brett Wynkoop wrote: > > Greeting- > > > > It is confirmed, the net I/O is much slower than reading from the SD > > card. Here is another run of tar - pipe - tar, but this time the > > source is the sd card and the destination is still the USB zfs. > [...] > > > > You're not actually testing network performance, you're testing a > confusing mashup of overall system performance. > > iperf on my beaglebone shows a throughput of 92mbps in both directions, > which is not at all bad for a 100mbps connection. Just checked: I do have a AM3358 board with an AR8035 PHY, which is GMII. http://www.goembed.com/index.php/Products/detail/tpid/49 It is the "SBC3358 ACW-B2A" Unfortunately it doesn't have the same TTL UART console connector as the beaglebone, although it shares the IO module header. Once I've setup an UART cable (JST connector it seems) I can try booting a beaglebone image and do some GBit/s performance tests. They claim it to be software compatible with the beaglebone, which can only partly be true with the Atheros PHY and additional IOs, but chances are good that it works with FreeBSD out of the box. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-arm@FreeBSD.ORG Sat Mar 14 01:29:03 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id F328271A for ; Sat, 14 Mar 2015 01:29:03 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [IPv6:2001:4f8:3:ffe0:406a:0:50:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D3189359 for ; Sat, 14 Mar 2015 01:29:03 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [127.0.1.5]) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9) with ESMTP id t2E1T3FB070451 for ; Sat, 14 Mar 2015 01:29:03 GMT (envelope-from root@phabric-backend.isc.freebsd.org) Received: (from root@localhost) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9/Submit) id t2E1T3iF070450; Sat, 14 Mar 2015 01:29:03 GMT (envelope-from root) Date: Sat, 14 Mar 2015 01:29:03 +0000 To: freebsd-arm@freebsd.org From: "imp (Warner Losh)" Subject: [Differential] [Accepted] D2018: Introduce Annapurna Labs AHCI support Message-ID: <65260d32d448683b765c81e2761126e7@localhost.localdomain> X-Priority: 3 Thread-Topic: D2018: Introduce Annapurna Labs AHCI support X-Herald-Rules: none X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: In-Reply-To: References: Thread-Index: ZGMxZTcyZjQyYTA3MjQzZjU5NjlmODc0YTQ5IFUDjt8= X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: , , MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Mar 2015 01:29:04 -0000 imp accepted this revision. imp added a comment. This revision is now accepted and ready to land. Thanks for the comments. Still not sure what an Annapurna is.... REVISION DETAIL https://reviews.freebsd.org/D2018 To: zbb, mav, smh, imp Cc: freebsd-arm From owner-freebsd-arm@FreeBSD.ORG Sat Mar 14 03:25:11 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E56266FA; Sat, 14 Mar 2015 03:25:11 +0000 (UTC) Received: from wa3yre.wynn.com (wa3yre.wynn.com [199.89.147.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9C7C9112; Sat, 14 Mar 2015 03:25:11 +0000 (UTC) Received: from ivory.wynn.com (mail.wynn.com [199.89.147.3]) (authenticated bits=0) by wa3yre.wynn.com (8.14.3/8.12.6) with ESMTP id t2E3OuKT070384; Fri, 13 Mar 2015 23:24:57 -0400 (EDT) (envelope-from freebsd-arm@wynn.com) Date: Fri, 13 Mar 2015 23:24:55 -0400 From: Brett Wynkoop To: Bernd Walter , "freebsd-arm@freebsd.org" Subject: Re: BeagleBone slow inbound net I/O Message-ID: <20150313232455.3f844d3e@ivory.wynn.com> In-Reply-To: <20150313235104.GJ34648@cicely7.cicely.de> References: <20150311165115.32327c5a@ivory.wynn.com> <20150312133433.GB28385@cicely7.cicely.de> <20150312232641.4365263d@ivory.wynn.com> <1426270714.19693.7.camel@freebsd.org> <20150313235104.GJ34648@cicely7.cicely.de> X-Mailer: Claws Mail 3.10.1 (GTK+ 2.24.25; x86_64-apple-darwin10.8.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Ian Lepore X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Mar 2015 03:25:12 -0000 On Sat, 14 Mar 2015 00:51:04 +0100 Bernd Walter wrote: > On Fri, Mar 13, 2015 at 12:18:34PM -0600, Ian Lepore wrote: > > On Thu, 2015-03-12 at 23:26 -0400, Brett Wynkoop wrote: > > > Greeting- > > > > > > It is confirmed, the net I/O is much slower than reading from the > > > SD card. Here is another run of tar - pipe - tar, but this time > > > the source is the sd card and the destination is still the USB > > > zfs. > > [...] > > > > > > > You're not actually testing network performance, you're testing a > > confusing mashup of overall system performance. > > Ian your point is well taken, but one can have a system where each part works fine on it's own, but when working in concert there is a breakdown. I believe that is what I have observed. Reading from sd card and writing to usb was many times faster than reading from ethernet and writing to usb. I would say I am testing the case where the source of the data is over the ethernet port and the destination is on the USB Flash. I will try grabbing data over the net and sending it to /dev/null, but if we have trouble moving bits from ethernet to USB I would say that is something that we might want to investigate. -Brett -- wynkoop@wynn.com http://prd4.wynn.com/wynkoop/pgp-keys.txt 917-642-6925 929-272-0000 Amendment VII In Suits at common law, where the value in controversy shall exceed twenty dollars, the right of trial by jury shall be preserved, and no fact tried by a jury, shall be otherwise re-examined in any Court of the United States, than according to the rules of the common law. From owner-freebsd-arm@FreeBSD.ORG Sat Mar 14 03:45:18 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 22754818 for ; Sat, 14 Mar 2015 03:45:18 +0000 (UTC) Received: from wa3yre.wynn.com (wa3yre.wynn.com [199.89.147.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5C1282A2 for ; Sat, 14 Mar 2015 03:45:17 +0000 (UTC) Received: from ivory.wynn.com (mail.wynn.com [199.89.147.3]) (authenticated bits=0) by wa3yre.wynn.com (8.14.3/8.12.6) with ESMTP id t2E3jB1C072259; Fri, 13 Mar 2015 23:45:13 -0400 (EDT) (envelope-from freebsd-arm@wynn.com) Date: Fri, 13 Mar 2015 23:45:10 -0400 From: Brett Wynkoop To: Mark Treacy Subject: Re: zfs Message-ID: <20150313234510.3b41611b@ivory.wynn.com> In-Reply-To: References: X-Mailer: Claws Mail 3.10.1 (GTK+ 2.24.25; x86_64-apple-darwin10.8.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-arm@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Mar 2015 03:45:18 -0000 Mark- I did a cc to the list as your questions and my answers might be of interest to others. On Fri, 13 Mar 2015 17:44:39 -0500 Mark Treacy wrote: > Hi Brett, > > What options did you use when you create the zfs pool? Multiple > devices? No special options just zpool create -m /export bbexport /dev/gpt/bbexport (I already had the gpt label from when it was a UFS) Then I used zfs set to turn off atime and turn on compression. [root@beaglebone ~]# zfs get all bbexport | grep compress bbexport compressratio 2.03x - bbexport compression lzjb local bbexport refcompressratio 2.10x - [root@beaglebone ~]# While I think there would be a further space savings with dedupe I did not want the system bogged down doing that work. The BeagleBone is after all a pretty small system. As already posted here are the excerpts from /boot/loader.conf and /etc/rc.conf: rc.conf: # zfs_enable="YES" # loader.conf: zfs_load="YES" # from zfstuning wiki # vm.kmem_size="256M" vm.kmem_size_max="256M" vfs.zfs.arc_max="24M" vfs.zfs.vdev.cache.size="5M" With the above arc I am getting about 50% arc cache hits: [root@beaglebone ~]# zfsci ARC efficiency 50.9707% [root@beaglebone ~]# My experience on my bigger x86 boxes tells me that I could get a better arc cache hit ratio if I kicked the arc_max up some more, but I do not think I want to hand any more main memory to zfs on such a small box. I wonder if we could do zfs on root.....hmmmm. Of course I miss the advantages of RAID or MIRRORS since I have only one disk in the pool, but I can at least do disk i/o to my usb flash fast and without crashing the system. I also get the advantage of a compressed filesystem and in addition to allowing me more storage it may account for the better write performance. There are fewer bits to write, so the slowness of flash media is somewhat compensated for. In a future test I plan to add a hub and stick 3 usb sticks on to form a raidz. > > Since zfs checksums everything you may well just be seeing it > detecting corruption and repairing it. > You could be right on this one. I think I need to dig out my other Beagle Bone and shift the sd and usb flash over to it and run the series of tests against ufs again on the new hardware. I say new because I have never fired up the other BBone. [root@beaglebone ~]# zpool status -v pool: bbexport state: ONLINE status: One or more devices has experienced an error resulting in data corruption. Applications may be affected. action: Restore the file in question if possible. Otherwise restore the entire pool from backup. see: http://illumos.org/msg/ZFS-8000-8A scan: none requested config: NAME STATE READ WRITE CKSUM bbexport ONLINE 0 0 10 gpt/bbexport ONLINE 0 0 99 errors: Permanent errors have been detected in the following files: /export/src/contrib/llvm/tools/clang/lib/Sema/SemaExpr.cpp /export/ports/packages/All/perl5-5.18.4_11.txz /export/ports/distfiles/rsync-3.1.1.tar.gz /export/ports/distfiles/readline-6.3.tar.gz /export/ports/comms/wsjt/files/configure bbexport/ports:<0x253db> [root@beaglebone ~]# > That would support Ian's faulty hardware suggestion... > > - Mark As does the output of zpool status above. -Brett -- wynkoop@wynn.com http://prd4.wynn.com/wynkoop/pgp-keys.txt 917-642-6925 929-272-0000 Amendment II A well regulated militia, being necessary to the security of a free state, the right of the people to keep and bear arms, shall not be infringed. From owner-freebsd-arm@FreeBSD.ORG Sat Mar 14 06:11:28 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EC7A4DF8 for ; Sat, 14 Mar 2015 06:11:28 +0000 (UTC) Received: from wa3yre.wynn.com (wa3yre.wynn.com [199.89.147.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AC1612EC for ; Sat, 14 Mar 2015 06:11:28 +0000 (UTC) Received: from ivory.wynn.com (mail.wynn.com [199.89.147.3]) (authenticated bits=0) by wa3yre.wynn.com (8.14.3/8.12.6) with ESMTP id t2E6BP6v086014; Sat, 14 Mar 2015 02:11:26 -0400 (EDT) (envelope-from freebsd-arm@wynn.com) Date: Sat, 14 Mar 2015 02:11:24 -0400 From: Brett Wynkoop To: Brett Wynkoop Subject: Re: crash on writing usbstick Message-ID: <20150314021124.6ed54708@ivory.wynn.com> In-Reply-To: <20150307055351.10452c23@ivory.wynn.com> References: <20150307055351.10452c23@ivory.wynn.com> X-Mailer: Claws Mail 3.10.1 (GTK+ 2.24.25; x86_64-apple-darwin10.8.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-arm@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Mar 2015 06:11:29 -0000 Greeting- Another data point came out tonight. A head/sys/mips/adm5120/obiovar.h svn: E200030: sqlite[S10]: disk I/O error svn: E200030: Additional errors: svn: E200030: sqlite[S10]: disk I/O error svn: E200030: Additional errors: svn: E200030: sqlite[S10]: disk I/O error svn: E200030: Additional errors: svn: E200030: sqlite[S10]: disk I/O error svn: E200030: Additional errors: svn: E200030: sqlite[S1]: no such savepoint: svn svn: E200030: Additional errors: svn: E200030: sqlite[S1]: no such savepoint: svn svn: E200030: Additional errors: svn: E200030: sqlite[S1]: no such savepoint: svn svn: E200030: Additional errors: svn: E200030: sqlite[S1]: no such savepoint: svn So there are disk I/O errors to the zfs as well, but as others have said the checksumming was helping. It still does not explain why the kernel panic on UFS and I just get disk i/o errors on zfs. I really think disk i/o errors to data disks should not cause a panic. Time for me to swap some hardware around and do some more testing. -Brett -- wynkoop@wynn.com http://prd4.wynn.com/wynkoop/pgp-keys.txt 917-642-6925 929-272-0000 Amendment IV The right of the people to be secure in their persons, houses, papers, and effects, against unreasonable searches and seizures, shall not be violated, and no warrants shall issue, but upon probable cause, supported by oath or affirmation, and particularly describing the place to be searched, and the persons or things to be seized. From owner-freebsd-arm@FreeBSD.ORG Sat Mar 14 06:20:28 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C7AE5EEB for ; Sat, 14 Mar 2015 06:20:28 +0000 (UTC) Received: from monday.kientzle.com (142-254-26-11.dsl.static.fusionbroadband.com [142.254.26.11]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5328F32A for ; Sat, 14 Mar 2015 06:20:27 +0000 (UTC) Received: (from root@localhost) by monday.kientzle.com (8.14.4/8.14.4) id t2E62QRb018971; Sat, 14 Mar 2015 06:02:26 GMT (envelope-from tim@kientzle.com) Received: from [192.168.2.102] (192.168.1.65 [192.168.1.65]) by kientzle.com with SMTP id 4mqyisdfu9k3wjxpc5ydmrjt6w; Sat, 14 Mar 2015 06:02:26 +0000 (UTC) (envelope-from tim@kientzle.com) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) Subject: Re: BeagleBone slow inbound net I/O From: Tim Kientzle In-Reply-To: <20150311165115.32327c5a@ivory.wynn.com> Date: Fri, 13 Mar 2015 23:02:25 -0700 Message-Id: <89CEBFCA-6B94-4F48-8DFD-790E4667632D@kientzle.com> References: <20150311165115.32327c5a@ivory.wynn.com> To: Brett Wynkoop X-Mailer: Apple Mail (2.2070.6) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: freebsd-arm X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Mar 2015 06:20:29 -0000 > On Mar 11, 2015, at 1:51 PM, Brett Wynkoop wrote: > > Have I managed to find a network driver issue? Any ideas how to gather > more information to help get to the bottom of things? > $ sysctl dev.cpsw This will dump detailed statistics from the Ethernet hardware and driver. Tim From owner-freebsd-arm@FreeBSD.ORG Sat Mar 14 07:00:06 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CAE80292 for ; Sat, 14 Mar 2015 07:00:06 +0000 (UTC) Received: from BAY004-OMC2S23.hotmail.com (bay004-omc2s23.hotmail.com [65.54.190.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "*.outlook.com", Issuer "MSIT Machine Auth CA 2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B17D089F for ; Sat, 14 Mar 2015 07:00:06 +0000 (UTC) Received: from BAY182-W5 ([65.54.190.125]) by BAY004-OMC2S23.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.22751); Sat, 14 Mar 2015 00:00:00 -0700 X-TMN: [f1AeuNhPesi/ZcxjuIzTB+UlHFNaMvVh] X-Originating-Email: [sgeos@hotmail.com] Message-ID: From: Brendan Sechter To: Warner Losh , Matthias Gamsjager Subject: RE: FreeBSD 10.1 / 11 on a Raspberry Pi B+ / 2 ? Date: Sat, 14 Mar 2015 15:59:59 +0900 Importance: Normal In-Reply-To: <04594F43-C6FD-4798-ACFF-8BB7179A905F@bsdimp.com> References: , , <6ff566ec17fc2b0d61635d8886261d5a.squirrel@ikornapostur.1984.is>, , <028290c7462d8fcf63b07bfdbbd08897.squirrel@ikornapostur.1984.is>, , , <04594F43-C6FD-4798-ACFF-8BB7179A905F@bsdimp.com> Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginalArrivalTime: 14 Mar 2015 07:00:00.0323 (UTC) FILETIME=[7D07A130:01D05E24] Cc: "freebsd-arm@freebsd.org" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Mar 2015 07:00:06 -0000 > Subject: Re: FreeBSD 10.1 / 11 on a Raspberry Pi B+ / 2 ?=0A= > From: imp@bsdimp.com=0A= > Date: Fri=2C 27 Feb 2015 14:40:05 -0700=0A= > To: mgamsjager@gmail.com=0A= > CC: freebsd-arm@freebsd.org=0A= >=A0=0A= >> On Feb 27=2C 2015=2C at 2:35 PM=2C Matthias Gamsjager wrote:=0A= >>=A0=0A= >> Image does boot on an old model B but not on the new rev.2.=0A= >> Guess there needs to be some work done after all=0A= >=A0=0A= > Support for the new SoC is not yet in the tree. I have one on my desk=2C = but=0A= > haven=92t had time to even boot it. Others are working on it=2C but its n= ot clear=0A= > when they will be able to commit the code.=0A= >=A0=0A= > Warner=0A= =0A= I built a FreeBSD-armv6-11.0-RPI-B-r279900.img image with crochet. =A0This = was the latest=0A= revision when I built it. =A0On the Pi 2=2C=A0the=A0unmodified image=A0boot= s to the so called=A0rainbow=0A= screen=A0and=A0stays there.=0A= =0A= >From what I gather=2C u-boot needs to be updated. =A0Should I be using the = official denx.de=0A= repository (git://git.denx.de/projects/u-boot.git)=2C or is there a better = u-boot repository to=0A= use=A0at this point?=0A= =0A= -Brendan = From owner-freebsd-arm@FreeBSD.ORG Sat Mar 14 07:14:58 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0DAED680 for ; Sat, 14 Mar 2015 07:14:58 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [IPv6:2001:4f8:3:ffe0:406a:0:50:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E2883A5D for ; Sat, 14 Mar 2015 07:14:57 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [127.0.1.5]) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9) with ESMTP id t2E7EvfS023287 for ; Sat, 14 Mar 2015 07:14:57 GMT (envelope-from root@phabric-backend.isc.freebsd.org) Received: (from root@localhost) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9/Submit) id t2E7Evc6023286; Sat, 14 Mar 2015 07:14:57 GMT (envelope-from root) Date: Sat, 14 Mar 2015 07:14:57 +0000 To: freebsd-arm@freebsd.org From: "mav (Alexnder Motin)" Subject: [Differential] [Accepted] D2018: Introduce Annapurna Labs AHCI support Message-ID: X-Priority: 3 Thread-Topic: D2018: Introduce Annapurna Labs AHCI support X-Herald-Rules: none X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: In-Reply-To: References: Thread-Index: ZGMxZTcyZjQyYTA3MjQzZjU5NjlmODc0YTQ5IFUD3/E= X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: , MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Mar 2015 07:14:58 -0000 mav accepted this revision. REVISION DETAIL https://reviews.freebsd.org/D2018 To: zbb, smh, imp, mav Cc: freebsd-arm From owner-freebsd-arm@FreeBSD.ORG Sat Mar 14 07:15:46 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5232F6DC for ; Sat, 14 Mar 2015 07:15:46 +0000 (UTC) Received: from wa3yre.wynn.com (wa3yre.wynn.com [199.89.147.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1457EA68 for ; Sat, 14 Mar 2015 07:15:45 +0000 (UTC) Received: from ivory.wynn.com (mail.wynn.com [199.89.147.3]) (authenticated bits=0) by wa3yre.wynn.com (8.14.3/8.12.6) with ESMTP id t2E7FhDB093561; Sat, 14 Mar 2015 03:15:43 -0400 (EDT) (envelope-from freebsd-arm@wynn.com) Date: Sat, 14 Mar 2015 03:15:42 -0400 From: Brett Wynkoop To: Tim Kientzle Subject: Re: BeagleBone slow inbound net I/O Message-ID: <20150314031542.439cdee3@ivory.wynn.com> In-Reply-To: <89CEBFCA-6B94-4F48-8DFD-790E4667632D@kientzle.com> References: <20150311165115.32327c5a@ivory.wynn.com> <89CEBFCA-6B94-4F48-8DFD-790E4667632D@kientzle.com> X-Mailer: Claws Mail 3.10.1 (GTK+ 2.24.25; x86_64-apple-darwin10.8.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-arm X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Mar 2015 07:15:46 -0000 On Fri, 13 Mar 2015 23:02:25 -0700 Tim Kientzle wrote: > > > On Mar 11, 2015, at 1:51 PM, Brett Wynkoop > > wrote: > > > > Have I managed to find a network driver issue? Any ideas how to > > gather more information to help get to the bottom of things? > > > > $ sysctl dev.cpsw > > This will dump detailed statistics from the Ethernet hardware and > driver. > > Tim > After a short time while doing nfs i/o [wynkoop@beaglebone ~]$ sysctl dev.cpsw | grep -i error dev.cpsw.0.stats.RxCrcErrors: 40 dev.cpsw.0.stats.RxAlignErrors: 32 dev.cpsw.0.stats.CarrierSenseErrors: 0 [wynkoop@beaglebone ~]$ sysctl dev.cpsw | grep -i error dev.cpsw.0.stats.RxCrcErrors: 40 dev.cpsw.0.stats.RxAlignErrors: 32 dev.cpsw.0.stats.CarrierSenseErrors: 0 [wynkoop@beaglebone ~]$ sysctl dev.cpsw | grep -i error dev.cpsw.0.stats.RxCrcErrors: 40 dev.cpsw.0.stats.RxAlignErrors: 32 dev.cpsw.0.stats.CarrierSenseErrors: 0 [wynkoop@beaglebone ~]$ sysctl dev.cpsw | grep -i error dev.cpsw.0.stats.RxCrcErrors: 40 dev.cpsw.0.stats.RxAlignErrors: 32 dev.cpsw.0.stats.CarrierSenseErrors: 0 [wynkoop@beaglebone ~]$ sysctl dev.cpsw | grep -i error dev.cpsw.0.stats.RxCrcErrors: 40 dev.cpsw.0.stats.RxAlignErrors: 32 dev.cpsw.0.stats.CarrierSenseErrors: 0 [wynkoop@beaglebone ~]$ sysctl dev.cpsw | grep -i error dev.cpsw.0.stats.RxCrcErrors: 43 dev.cpsw.0.stats.RxAlignErrors: 32 dev.cpsw.0.stats.CarrierSenseErrors: 0 [wynkoop@beaglebone ~]$ sysctl dev.cpsw | grep -i error dev.cpsw.0.stats.RxCrcErrors: 43 dev.cpsw.0.stats.RxAlignErrors: 32 dev.cpsw.0.stats.CarrierSenseErrors: 0 [wynkoop@beaglebone ~]$ sysctl dev.cpsw | grep -i error dev.cpsw.0.stats.RxCrcErrors: 54 dev.cpsw.0.stats.RxAlignErrors: 36 dev.cpsw.0.stats.CarrierSenseErrors: 0 [wynkoop@beaglebone ~]$ sysctl dev.cpsw | grep -i error dev.cpsw.0.stats.RxCrcErrors: 59 dev.cpsw.0.stats.RxAlignErrors: 40 dev.cpsw.0.stats.CarrierSenseErrors: 0 [wynkoop@beaglebone ~]$ sysctl dev.cpsw | grep -i error dev.cpsw.0.stats.RxCrcErrors: 64 dev.cpsw.0.stats.RxAlignErrors: 48 dev.cpsw.0.stats.CarrierSenseErrors: 0 [wynkoop@beaglebone ~]$ sysctl dev.cpsw | grep -i error dev.cpsw.0.stats.RxCrcErrors: 66 dev.cpsw.0.stats.RxAlignErrors: 50 dev.cpsw.0.stats.CarrierSenseErrors: 0 [wynkoop@beaglebone ~]$ sysctl dev.cpsw | grep -i error dev.cpsw.0.stats.RxCrcErrors: 67 dev.cpsw.0.stats.RxAlignErrors: 53 dev.cpsw.0.stats.CarrierSenseErrors: 0 [wynkoop@beaglebone ~]$ sysctl dev.cpsw | grep -i error dev.cpsw.0.stats.RxCrcErrors: 67 dev.cpsw.0.stats.RxAlignErrors: 53 dev.cpsw.0.stats.CarrierSenseErrors: 0 .... [wynkoop@beaglebone ~]$ sysctl dev.cpsw | grep -i error dev.cpsw.0.stats.RxCrcErrors: 172 dev.cpsw.0.stats.RxAlignErrors: 141 dev.cpsw.0.stats.CarrierSenseErrors: 0 [wynkoop@beaglebone ~]$ ..... [wynkoop@beaglebone ~]$ sysctl dev.cpsw | grep -i error dev.cpsw.0.stats.RxCrcErrors: 262 dev.cpsw.0.stats.RxAlignErrors: 231 dev.cpsw.0.stats.CarrierSenseErrors: 0 [wynkoop@beaglebone ~]$ So we can see climbing errors. I am not sure how this compares to the results of others. The above was during the first few minutes of a buildworld from an nfs share. At the same time on the console: Mar 14 03:07:47 beaglebone amd[1163]: mountd rpc failed: RPC: Can't decode result Mar 14 03:11:48 beaglebone amd[1399]: mountd rpc failed: RPC: Can't decode result which makes sense with the above errors I think. -Brett -- wynkoop@wynn.com http://prd4.wynn.com/wynkoop/pgp-keys.txt 917-642-6925 929-272-0000 Amendment VIII Excessive bail shall not be required, nor excessive fines imposed, nor cruel and unusual punishments inflicted. From owner-freebsd-arm@FreeBSD.ORG Sat Mar 14 07:29:36 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 45C5286C for ; Sat, 14 Mar 2015 07:29:36 +0000 (UTC) Received: from vps.rulingia.com (vps.rulingia.com [103.243.244.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vps.rulingia.com", Issuer "CAcert Class 3 Root" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id CA5D2BBF for ; Sat, 14 Mar 2015 07:29:33 +0000 (UTC) Received: from server.rulingia.com (c220-239-242-83.belrs5.nsw.optusnet.com.au [220.239.242.83]) by vps.rulingia.com (8.14.9/8.14.9) with ESMTP id t2E7TG8Z028601 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Sat, 14 Mar 2015 18:29:23 +1100 (AEDT) (envelope-from peter@rulingia.com) X-Bogosity: Ham, spamicity=0.000000 Received: from server.rulingia.com (localhost.rulingia.com [127.0.0.1]) by server.rulingia.com (8.14.9/8.14.9) with ESMTP id t2E7T7Ip012881 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 14 Mar 2015 18:29:07 +1100 (AEDT) (envelope-from peter@server.rulingia.com) Received: (from peter@localhost) by server.rulingia.com (8.14.9/8.14.9/Submit) id t2E7T6AH012880; Sat, 14 Mar 2015 18:29:06 +1100 (AEDT) (envelope-from peter) Date: Sat, 14 Mar 2015 18:29:06 +1100 From: Peter Jeremy To: Brett Wynkoop Subject: Re: zfs Message-ID: <20150314072906.GA19582@server.rulingia.com> References: <20150313234510.3b41611b@ivory.wynn.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="fUYQa+Pmc3FrFX/N" Content-Disposition: inline In-Reply-To: <20150313234510.3b41611b@ivory.wynn.com> X-PGP-Key: http://www.rulingia.com/keys/peter.pgp User-Agent: Mutt/1.5.23 (2014-03-12) Cc: freebsd-arm@freebsd.org, Mark Treacy X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Mar 2015 07:29:36 -0000 --fUYQa+Pmc3FrFX/N Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2015-Mar-13 23:45:10 -0400, Brett Wynkoop wrote: >While I think there would be a further space savings with dedupe I did >not want the system bogged down doing that work. The BeagleBone is >after all a pretty small system. Whilst an all-flash pool removes one of the main killers for dedupe, I suspect that the extra RAM to handle the DDT would outweigh the possible space-savings. >vfs.zfs.arc_max=3D"24M" =2E.. >With the above arc I am getting about 50% arc cache hits: Depending on your workload, you might find that increasing vfs.zfs.arc_meta_limit might help overall performance - at least on my x86 server, I find the default (25% of arc_max) a bit small. >I wonder if we could do zfs on root.....hmmmm. You'd need to build your own ubldr but it should be doable. >fast and without crashing the system. I also get the advantage of a >compressed filesystem and in addition to allowing me more storage it >may account for the better write performance. There are fewer bits to >write, so the slowness of flash media is somewhat compensated for. ZFS compression trades CPU resources for IO performance. For a modern x86 system, it's virtually always a win but the BBB has far less CPU available (though the flash is also very slow). >> Since zfs checksums everything you may well just be seeing it >> detecting corruption and repairing it. > >You could be right on this one. I think I need to dig out my other >Beagle Bone and shift the sd and usb flash over to it and run the >series of tests against ufs again on the new hardware. I say new >because I have never fired up the other BBone. Note that ZFS can't repair things unless you have redundant copies. Whilst there are redundant copies of metadata by default, there is only one copy of data - which is why you have: >errors: Permanent errors have been detected in the following files: > > /export/src/contrib/llvm/tools/clang/lib/Sema/SemaExpr.cpp > /export/ports/packages/All/perl5-5.18.4_11.txz > /export/ports/distfiles/rsync-3.1.1.tar.gz > /export/ports/distfiles/readline-6.3.tar.gz > /export/ports/comms/wsjt/files/configure You might like to set copies=3D2 if you don't have redundancy at the pool l= evel. > bbexport/ports:<0x253db> This is probably a lost metadata block. --=20 Peter Jeremy --fUYQa+Pmc3FrFX/N Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJVA+NCXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRFRUIyOTg2QzMwNjcxRTc0RTY1QzIyN0Ux NkE1OTdBMEU0QTIwQjM0AAoJEBall6Dkogs0toQP/3HJQGNP74oC/ujDBctCPjPF 1ly5fwidCbA6XyxpzozGaist7Qb+94m8plCO7jGehohd2CqQprpwqD50ayn0Xjbs uBW8aLAvG1hSnQnNaqstW3v44ACeKrqc9sEoSYQYRBKlsNAsLnnVOhHTq09qXHFq yZ0NmUMcN2+DoD3IVP6N9d3JmNsHQfvCPihI6KsgUfUgIDWf394Fp7ehmq8lgpXo uAuDZuPXPcNns/UylazYRcSwMMbyrIe4vXKus7a2rEiCGA3CwZuikGJAlznjmNUP A8SMEO0HroGsTEK8LwMpr0S3OcA2YZBom5cuc8WxZ/haF3x6is3zUK+OXnqaOYZy rQz9wOFMkrxyUrT5qV3UxTuKhCB9X514ZC5bhcfGcY4dsEUwSPhu63JMrmk4l85U m7CtjfBZJC0GMibc+J0jMco/XT7YdtSFxVDcUDH5u0cUad3XG89G3RkZO9VfrdIa RBl53yjDqcjWQrcoZvec6EkXjUhgvHcniuRw/CCVgM2Nyn2aP+05ijERCOObQV7O O4Xik1XknaSYCoZV8yOEN9PlihAXMoDy4s1aPpLDFrpdfWj7VBD7JntrDm6hWFMI MOe1ermy72dCRtSZehlTJ+trklRMcxUOF8MoL6cVGnJSODRju9P+owvrssaoWSrH Q6FS89YFG32jQfErY6b7 =iy24 -----END PGP SIGNATURE----- --fUYQa+Pmc3FrFX/N-- From owner-freebsd-arm@FreeBSD.ORG Sat Mar 14 09:30:27 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5A767AFE for ; Sat, 14 Mar 2015 09:30:27 +0000 (UTC) Received: from mail-ie0-x231.google.com (mail-ie0-x231.google.com [IPv6:2607:f8b0:4001:c03::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1B0379D3 for ; Sat, 14 Mar 2015 09:30:27 +0000 (UTC) Received: by iegc3 with SMTP id c3so140633962ieg.3 for ; Sat, 14 Mar 2015 02:30:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:cc :content-type:content-transfer-encoding; bh=EUS8gDsalz6kmoXc24+2JZZaxP1mBrwxwnATZpZKTfA=; b=vEo0E2xr0Eevp56RVAK0yTk3MpGyBrfZjVTrP0BIESR/8A59RPoAyUh2NMLHWloWkX gijP5+p9TvHOtXscfuq8jfY4RRtuonT/bFLVRtwsIcFlIoPhGBkbE8XyojyWLBHUEkJp B8B911TOkaICn3qzCk3DsONtyVMUMyJivnkAeclFln8tfLFipViaeCzGhMaXml3pvf6t 1Rpc+a7S7L3vxL1FpMqiZ3GXZ073hG9on1VWS7076vNS4nRGsYADz+ZdAcE6udIdcPAK jCZV8cqV7f/0qjSZy9KuqCPHT3DVwjsaDCoNgxOvozSusKYgxUN1MtiSCihRcZqAf35t oLdw== X-Received: by 10.42.118.73 with SMTP id w9mr63771751icq.44.1426325426566; Sat, 14 Mar 2015 02:30:26 -0700 (PDT) MIME-Version: 1.0 Received: by 10.64.227.233 with HTTP; Sat, 14 Mar 2015 02:29:56 -0700 (PDT) In-Reply-To: References: <6ff566ec17fc2b0d61635d8886261d5a.squirrel@ikornapostur.1984.is> <028290c7462d8fcf63b07bfdbbd08897.squirrel@ikornapostur.1984.is> <04594F43-C6FD-4798-ACFF-8BB7179A905F@bsdimp.com> From: Matthias Gamsjager Date: Sat, 14 Mar 2015 10:29:56 +0100 Message-ID: Subject: Re: FreeBSD 10.1 / 11 on a Raspberry Pi B+ / 2 ? Cc: "freebsd-arm@freebsd.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Mar 2015 09:30:27 -0000 On Sat, Mar 14, 2015 at 7:59 AM, Brendan Sechter wrote: >> Subject: Re: FreeBSD 10.1 / 11 on a Raspberry Pi B+ / 2 ? >> From: imp@bsdimp.com >> Date: Fri, 27 Feb 2015 14:40:05 -0700 >> To: mgamsjager@gmail.com >> CC: freebsd-arm@freebsd.org >> >>> On Feb 27, 2015, at 2:35 PM, Matthias Gamsjager = wrote: >>> >>> Image does boot on an old model B but not on the new rev.2. >>> Guess there needs to be some work done after all >> >> Support for the new SoC is not yet in the tree. I have one on my desk, b= ut >> haven=E2=80=99t had time to even boot it. Others are working on it, but = its not clear >> when they will be able to commit the code. >> >> Warner > > I built a FreeBSD-armv6-11.0-RPI-B-r279900.img image with crochet. This = was the latest > revision when I built it. On the Pi 2, the unmodified image boots to the= so called rainbow > screen and stays there. > > From what I gather, u-boot needs to be updated. Should I be using the of= ficial denx.de > repository (git://git.denx.de/projects/u-boot.git), or is there a better = u-boot repository to > use at this point? > > -Brendan What I gathered is that more needs to be done then just a newer version of uboot to get it working. From owner-freebsd-arm@FreeBSD.ORG Sat Mar 14 13:41:03 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 521F0309 for ; Sat, 14 Mar 2015 13:41:03 +0000 (UTC) Received: from relay.mailchannels.net (si-002-i69.relay.mailchannels.net [184.154.112.243]) by mx1.freebsd.org (Postfix) with ESMTP id 7F883214 for ; Sat, 14 Mar 2015 13:41:02 +0000 (UTC) X-Sender-Id: duocircle|x-authuser|hippie Received: from smtp1.ore.mailhop.org (ip-10-229-11-165.us-west-2.compute.internal [10.229.11.165]) by relay.mailchannels.net (Postfix) with ESMTPA id A986B1D030A; Sat, 14 Mar 2015 13:23:22 +0000 (UTC) X-Sender-Id: duocircle|x-authuser|hippie Received: from smtp1.ore.mailhop.org (smtp1.ore.mailhop.org [10.83.15.107]) (using TLSv1 with cipher DHE-RSA-AES256-SHA) by 0.0.0.0:2500 (trex/5.4.8); Sat, 14 Mar 2015 13:23:27 +0000 X-MC-Relay: Neutral X-MailChannels-SenderId: duocircle|x-authuser|hippie X-MailChannels-Auth-Id: duocircle X-MC-Loop-Signature: 1426339403817:2605118784 X-MC-Ingress-Time: 1426339403817 Received: from c-73-34-117-227.hsd1.co.comcast.net ([73.34.117.227] helo=ilsoft.org) by smtp1.ore.mailhop.org with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.82) (envelope-from ) id 1YWm2D-0004Od-JF; Sat, 14 Mar 2015 13:23:21 +0000 Received: from revolution.hippie.lan (revolution.hippie.lan [172.22.42.240]) by ilsoft.org (8.14.9/8.14.9) with ESMTP id t2EDNK0T018769; Sat, 14 Mar 2015 07:23:20 -0600 (MDT) (envelope-from ian@freebsd.org) X-Mail-Handler: DuoCircle Outbound SMTP X-Originating-IP: 73.34.117.227 X-Report-Abuse-To: abuse@duocircle.com (see https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information for abuse reporting information) X-MHO-User: U2FsdGVkX19x+yFBRXn4NvBgqYkzJSzZ Message-ID: <1426339400.52318.3.camel@freebsd.org> Subject: Re: BeagleBone slow inbound net I/O From: Ian Lepore To: Brett Wynkoop Date: Sat, 14 Mar 2015 07:23:20 -0600 In-Reply-To: <20150314031542.439cdee3@ivory.wynn.com> References: <20150311165115.32327c5a@ivory.wynn.com> <89CEBFCA-6B94-4F48-8DFD-790E4667632D@kientzle.com> <20150314031542.439cdee3@ivory.wynn.com> Content-Type: text/plain; charset="us-ascii" X-Mailer: Evolution 3.12.10 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-AuthUser: hippie Cc: Tim Kientzle , freebsd-arm X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Mar 2015 13:41:03 -0000 On Sat, 2015-03-14 at 03:15 -0400, Brett Wynkoop wrote: > On Fri, 13 Mar 2015 23:02:25 -0700 > Tim Kientzle wrote: > > > > > > On Mar 11, 2015, at 1:51 PM, Brett Wynkoop > > > wrote: > > > > > > Have I managed to find a network driver issue? Any ideas how to > > > gather more information to help get to the bottom of things? > > > > > > > $ sysctl dev.cpsw > > > > This will dump detailed statistics from the Ethernet hardware and > > driver. > > > > Tim > > > > After a short time while doing nfs i/o > > > [wynkoop@beaglebone ~]$ sysctl dev.cpsw | grep -i error > dev.cpsw.0.stats.RxCrcErrors: 40 > dev.cpsw.0.stats.RxAlignErrors: 32 > dev.cpsw.0.stats.CarrierSenseErrors: 0 [...] > [wynkoop@beaglebone ~]$ sysctl dev.cpsw | grep -i error > dev.cpsw.0.stats.RxCrcErrors: 262 > dev.cpsw.0.stats.RxAlignErrors: 231 > dev.cpsw.0.stats.CarrierSenseErrors: 0 > [wynkoop@beaglebone ~]$ > > So we can see climbing errors. I am not sure how this compares to the > results of others. The above was during the first few minutes of a > buildworld from an nfs share. > > At the same time on the console: > > Mar 14 03:07:47 beaglebone amd[1163]: mountd rpc failed: RPC: Can't > decode result Mar 14 03:11:48 beaglebone amd[1399]: mountd rpc failed: > RPC: Can't decode result > > which makes sense with the above errors I think. On mine: root@bb:/usr/ports/benchmarks/iperf # sysctl dev.cpsw | grep Err dev.cpsw.0.stats.RxCrcErrors: 0 dev.cpsw.0.stats.RxAlignErrors: 0 dev.cpsw.0.stats.CarrierSenseErrors: 0 That's after 3 days of uptime including doing builds over nfs, and all the iperf testing I was doing yesterday (no errors after megabytes of transfers). I wonder if your power supply is failing and injecting transient glitches under heavy load or something? -- Ian From owner-freebsd-arm@FreeBSD.ORG Sat Mar 14 14:00:22 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 11F7F6C9; Sat, 14 Mar 2015 14:00:22 +0000 (UTC) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "raven.bwct.de", Issuer "BWCT" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id B3D153EB; Sat, 14 Mar 2015 14:00:21 +0000 (UTC) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id t2EDxv9m032137 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sat, 14 Mar 2015 14:59:57 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) 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 t2EDxtue010284 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 14 Mar 2015 14:59:55 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.14.2/8.14.2) with ESMTP id t2EDxtNm041537; Sat, 14 Mar 2015 14:59:55 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.14.2/8.14.2/Submit) id t2EDxsKT041536; Sat, 14 Mar 2015 14:59:54 +0100 (CET) (envelope-from ticso) Date: Sat, 14 Mar 2015 14:59:54 +0100 From: Bernd Walter To: Ian Lepore Subject: Re: BeagleBone slow inbound net I/O Message-ID: <20150314135954.GD40951@cicely7.cicely.de> Reply-To: ticso@cicely.de References: <20150311165115.32327c5a@ivory.wynn.com> <89CEBFCA-6B94-4F48-8DFD-790E4667632D@kientzle.com> <20150314031542.439cdee3@ivory.wynn.com> <1426339400.52318.3.camel@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1426339400.52318.3.camel@freebsd.org> X-Operating-System: FreeBSD cicely7.cicely.de 7.0-STABLE i386 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-0.2 required=5.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9, DNS_FROM_AHBL_RHSBL=2.699, T_RP_MATCHES_RCVD=-0.01 autolearn=no version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de Cc: freebsd-arm , Tim Kientzle X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Mar 2015 14:00:22 -0000 On Sat, Mar 14, 2015 at 07:23:20AM -0600, Ian Lepore wrote: > On Sat, 2015-03-14 at 03:15 -0400, Brett Wynkoop wrote: > > On Fri, 13 Mar 2015 23:02:25 -0700 > > Tim Kientzle wrote: > > > > > > > > > On Mar 11, 2015, at 1:51 PM, Brett Wynkoop > > > > wrote: > > > > > > > > Have I managed to find a network driver issue? Any ideas how to > > > > gather more information to help get to the bottom of things? > > > > > > > > > > $ sysctl dev.cpsw > > > > > > This will dump detailed statistics from the Ethernet hardware and > > > driver. > > > > > > Tim > > > > > > > After a short time while doing nfs i/o > > > > > > [wynkoop@beaglebone ~]$ sysctl dev.cpsw | grep -i error > > dev.cpsw.0.stats.RxCrcErrors: 40 > > dev.cpsw.0.stats.RxAlignErrors: 32 > > dev.cpsw.0.stats.CarrierSenseErrors: 0 > [...] > > [wynkoop@beaglebone ~]$ sysctl dev.cpsw | grep -i error > > dev.cpsw.0.stats.RxCrcErrors: 262 > > dev.cpsw.0.stats.RxAlignErrors: 231 > > dev.cpsw.0.stats.CarrierSenseErrors: 0 > > [wynkoop@beaglebone ~]$ > > > > So we can see climbing errors. I am not sure how this compares to the > > results of others. The above was during the first few minutes of a > > buildworld from an nfs share. > > > > At the same time on the console: > > > > Mar 14 03:07:47 beaglebone amd[1163]: mountd rpc failed: RPC: Can't > > decode result Mar 14 03:11:48 beaglebone amd[1399]: mountd rpc failed: > > RPC: Can't decode result > > > > which makes sense with the above errors I think. It doesn't make sense with the ethernet CRC alone, since ethernet CRC failures are basicly dropped packets. If the RPC answer can't be parsed then ethernet packet CRC was Ok, when verified by the MAC and corrupted later. > On mine: > > root@bb:/usr/ports/benchmarks/iperf # sysctl dev.cpsw | grep Err > dev.cpsw.0.stats.RxCrcErrors: 0 > dev.cpsw.0.stats.RxAlignErrors: 0 > dev.cpsw.0.stats.CarrierSenseErrors: 0 > > That's after 3 days of uptime including doing builds over nfs, and all > the iperf testing I was doing yesterday (no errors after megabytes of > transfers). > > I wonder if your power supply is failing and injecting transient > glitches under heavy load or something? Power seems likely. The RPC error and filesystem corruptions make sense with broken RAM too, but the ethernet CRC should be checked during transfer to RAM. The subsystems with failures are very different and mostly isolated from software and HW-logic. About ZFS: It is designed to handle data corruption to some degree and has an extremly different workload, so possible that it works by luck. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-arm@FreeBSD.ORG Sat Mar 14 14:04:14 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 27E57759; Sat, 14 Mar 2015 14:04:14 +0000 (UTC) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "raven.bwct.de", Issuer "BWCT" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C7CEE673; Sat, 14 Mar 2015 14:04:13 +0000 (UTC) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id t2EE4BfF032174 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sat, 14 Mar 2015 15:04:11 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) 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 t2EE49V9010340 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 14 Mar 2015 15:04:09 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.14.2/8.14.2) with ESMTP id t2EE49op041584; Sat, 14 Mar 2015 15:04:09 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.14.2/8.14.2/Submit) id t2EE49hH041583; Sat, 14 Mar 2015 15:04:09 +0100 (CET) (envelope-from ticso) Date: Sat, 14 Mar 2015 15:04:09 +0100 From: Bernd Walter To: Ian Lepore Subject: Re: BeagleBone slow inbound net I/O Message-ID: <20150314140408.GE40951@cicely7.cicely.de> Reply-To: ticso@cicely.de References: <20150311165115.32327c5a@ivory.wynn.com> <89CEBFCA-6B94-4F48-8DFD-790E4667632D@kientzle.com> <20150314031542.439cdee3@ivory.wynn.com> <1426339400.52318.3.camel@freebsd.org> <20150314135954.GD40951@cicely7.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150314135954.GD40951@cicely7.cicely.de> X-Operating-System: FreeBSD cicely7.cicely.de 7.0-STABLE i386 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-0.2 required=5.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9, DNS_FROM_AHBL_RHSBL=2.699, T_RP_MATCHES_RCVD=-0.01 autolearn=no version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de Cc: Tim Kientzle , freebsd-arm X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Mar 2015 14:04:14 -0000 On Sat, Mar 14, 2015 at 02:59:54PM +0100, Bernd Walter wrote: > On Sat, Mar 14, 2015 at 07:23:20AM -0600, Ian Lepore wrote: > > On Sat, 2015-03-14 at 03:15 -0400, Brett Wynkoop wrote: > > > On Fri, 13 Mar 2015 23:02:25 -0700 > > > Tim Kientzle wrote: > > > > > > > > > > > > On Mar 11, 2015, at 1:51 PM, Brett Wynkoop > > > > > wrote: > > > > > > > > > > Have I managed to find a network driver issue? Any ideas how to > > > > > gather more information to help get to the bottom of things? > > > > > > > > > > > > > $ sysctl dev.cpsw > > > > > > > > This will dump detailed statistics from the Ethernet hardware and > > > > driver. > > > > > > > > Tim > > > > > > > > > > After a short time while doing nfs i/o > > > > > > > > > [wynkoop@beaglebone ~]$ sysctl dev.cpsw | grep -i error > > > dev.cpsw.0.stats.RxCrcErrors: 40 > > > dev.cpsw.0.stats.RxAlignErrors: 32 > > > dev.cpsw.0.stats.CarrierSenseErrors: 0 > > [...] > > > [wynkoop@beaglebone ~]$ sysctl dev.cpsw | grep -i error > > > dev.cpsw.0.stats.RxCrcErrors: 262 > > > dev.cpsw.0.stats.RxAlignErrors: 231 > > > dev.cpsw.0.stats.CarrierSenseErrors: 0 > > > [wynkoop@beaglebone ~]$ > > > > > > So we can see climbing errors. I am not sure how this compares to the > > > results of others. The above was during the first few minutes of a > > > buildworld from an nfs share. > > > > > > At the same time on the console: > > > > > > Mar 14 03:07:47 beaglebone amd[1163]: mountd rpc failed: RPC: Can't > > > decode result Mar 14 03:11:48 beaglebone amd[1399]: mountd rpc failed: > > > RPC: Can't decode result > > > > > > which makes sense with the above errors I think. > > It doesn't make sense with the ethernet CRC alone, since ethernet CRC > failures are basicly dropped packets. > If the RPC answer can't be parsed then ethernet packet CRC was Ok, when > verified by the MAC and corrupted later. > > > On mine: > > > > root@bb:/usr/ports/benchmarks/iperf # sysctl dev.cpsw | grep Err > > dev.cpsw.0.stats.RxCrcErrors: 0 > > dev.cpsw.0.stats.RxAlignErrors: 0 > > dev.cpsw.0.stats.CarrierSenseErrors: 0 > > > > That's after 3 days of uptime including doing builds over nfs, and all > > the iperf testing I was doing yesterday (no errors after megabytes of > > transfers). > > > > I wonder if your power supply is failing and injecting transient > > glitches under heavy load or something? > > Power seems likely. > The RPC error and filesystem corruptions make sense with broken RAM too, > but the ethernet CRC should be checked during transfer to RAM. > The subsystems with failures are very different and mostly isolated from > software and HW-logic. > > About ZFS: > It is designed to handle data corruption to some degree and has an extremly > different workload, so possible that it works by luck. Just noticed in another of your mails that you have uncorrected errors with ZFS too. It is just that ZFS notices the corruption with it's CRC, plus has copies for metadata, so it doesn't need to panic as UFS. But as a user I would panic with such a system ;-) -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-arm@FreeBSD.ORG Sat Mar 14 15:42:36 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9D7D86F6; Sat, 14 Mar 2015 15:42:36 +0000 (UTC) Received: from gromit.dlib.vt.edu (gromit.dlib.vt.edu [128.173.126.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gromit.dlib.vt.edu", Issuer "Chumby Certificate Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 70E4AFB8; Sat, 14 Mar 2015 15:42:36 +0000 (UTC) Received: from macbook.chumby.lan (c-71-63-94-21.hsd1.va.comcast.net [71.63.94.21]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gromit.dlib.vt.edu (Postfix) with ESMTPSA id 16E5853F; Sat, 14 Mar 2015 11:42:27 -0400 (EDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: BeagleBone slow inbound net I/O From: Paul Mather In-Reply-To: <1426339400.52318.3.camel@freebsd.org> Date: Sat, 14 Mar 2015 11:42:25 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: <807E4289-EC2E-49F9-A909-4D2A2A149302@gromit.dlib.vt.edu> References: <20150311165115.32327c5a@ivory.wynn.com> <89CEBFCA-6B94-4F48-8DFD-790E4667632D@kientzle.com> <20150314031542.439cdee3@ivory.wynn.com> <1426339400.52318.3.camel@freebsd.org> To: Ian Lepore X-Mailer: Apple Mail (2.1878.6) Cc: freebsd-arm X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Mar 2015 15:42:36 -0000 On Mar 14, 2015, at 9:23 AM, Ian Lepore wrote: > On Sat, 2015-03-14 at 03:15 -0400, Brett Wynkoop wrote: >> On Fri, 13 Mar 2015 23:02:25 -0700 >> Tim Kientzle wrote: >>=20 >>>=20 >>>> On Mar 11, 2015, at 1:51 PM, Brett Wynkoop >>>> wrote: >>>>=20 >>>> Have I managed to find a network driver issue? Any ideas how to >>>> gather more information to help get to the bottom of things? >>>>=20 >>>=20 >>> $ sysctl dev.cpsw >>>=20 >>> This will dump detailed statistics from the Ethernet hardware and >>> driver. >>>=20 >>> Tim >>>=20 >>=20 >> After a short time while doing nfs i/o >>=20 >>=20 >> [wynkoop@beaglebone ~]$ sysctl dev.cpsw | grep -i error >> dev.cpsw.0.stats.RxCrcErrors: 40 >> dev.cpsw.0.stats.RxAlignErrors: 32 >> dev.cpsw.0.stats.CarrierSenseErrors: 0 > [...] >> [wynkoop@beaglebone ~]$ sysctl dev.cpsw | grep -i error >> dev.cpsw.0.stats.RxCrcErrors: 262 >> dev.cpsw.0.stats.RxAlignErrors: 231 >> dev.cpsw.0.stats.CarrierSenseErrors: 0 >> [wynkoop@beaglebone ~]$=20 >>=20 >> So we can see climbing errors. I am not sure how this compares to = the >> results of others. The above was during the first few minutes of a >> buildworld from an nfs share. >>=20 >> At the same time on the console: >>=20 >> Mar 14 03:07:47 beaglebone amd[1163]: mountd rpc failed: RPC: Can't >> decode result Mar 14 03:11:48 beaglebone amd[1399]: mountd rpc = failed: >> RPC: Can't decode result >>=20 >> which makes sense with the above errors I think. >=20 > On mine: >=20 > root@bb:/usr/ports/benchmarks/iperf # sysctl dev.cpsw | grep Err > dev.cpsw.0.stats.RxCrcErrors: 0 > dev.cpsw.0.stats.RxAlignErrors: 0 > dev.cpsw.0.stats.CarrierSenseErrors: 0 >=20 > That's after 3 days of uptime including doing builds over nfs, and all > the iperf testing I was doing yesterday (no errors after megabytes of > transfers). Here is another data point from my BBB: pmather@beaglebone:~ % sysctl dev.cpsw dev.cpsw.%parent:=20 dev.cpsw.0.%desc: 3-port Switch Ethernet Subsystem dev.cpsw.0.%driver: cpsw dev.cpsw.0.%location:=20 dev.cpsw.0.%pnpinfo: name=3Dethernet@4A100000 compat=3Dti,cpsw dev.cpsw.0.%parent: simplebus0 dev.cpsw.0.attachedSecs: 135771 dev.cpsw.0.uptime: 135750 dev.cpsw.0.stats.GoodRxFrames: 4200799 dev.cpsw.0.stats.BroadcastRxFrames: 8326 dev.cpsw.0.stats.MulticastRxFrames: 132766 dev.cpsw.0.stats.PauseRxFrames: 0 dev.cpsw.0.stats.RxCrcErrors: 0 dev.cpsw.0.stats.RxAlignErrors: 0 dev.cpsw.0.stats.OversizeRxFrames: 0 dev.cpsw.0.stats.RxJabbers: 0 dev.cpsw.0.stats.ShortRxFrames: 0 dev.cpsw.0.stats.RxFragments: 0 dev.cpsw.0.stats.RxOctets: 6141208229 dev.cpsw.0.stats.GoodTxFrames: 2064557 dev.cpsw.0.stats.BroadcastTxFrames: 111 dev.cpsw.0.stats.MulticastTxFrames: 0 dev.cpsw.0.stats.PauseTxFrames: 0 dev.cpsw.0.stats.DeferredTxFrames: 0 dev.cpsw.0.stats.CollisionsTxFrames: 0 dev.cpsw.0.stats.SingleCollisionTxFrames: 0 dev.cpsw.0.stats.MultipleCollisionTxFrames: 0 dev.cpsw.0.stats.ExcessiveCollisions: 0 dev.cpsw.0.stats.LateCollisions: 0 dev.cpsw.0.stats.TxUnderrun: 0 dev.cpsw.0.stats.CarrierSenseErrors: 0 dev.cpsw.0.stats.TxOctets: 203621590 dev.cpsw.0.stats.RxTx64OctetFrames: 82180 dev.cpsw.0.stats.RxTx65to127OctetFrames: 2054745 dev.cpsw.0.stats.RxTx128to255OctetFrames: 10086 dev.cpsw.0.stats.RxTx256to511OctetFrames: 50051 dev.cpsw.0.stats.RxTx512to1024OctetFrames: 303 dev.cpsw.0.stats.RxTx1024upOctetFrames: 4067992 dev.cpsw.0.stats.NetOctets: 6344829819 dev.cpsw.0.stats.RxStartOfFrameOverruns: 1708 dev.cpsw.0.stats.RxMiddleOfFrameOverruns: 0 dev.cpsw.0.stats.RxDmaOverruns: 0 dev.cpsw.0.queue.tx.totalBuffers: 128 dev.cpsw.0.queue.tx.activeBuffers: 2 dev.cpsw.0.queue.tx.maxActiveBuffers: 7 dev.cpsw.0.queue.tx.availBuffers: 126 dev.cpsw.0.queue.tx.maxAvailBuffers: 128 dev.cpsw.0.queue.tx.totalEnqueued: 2128785 dev.cpsw.0.queue.tx.totalDequeued: 2128783 dev.cpsw.0.queue.tx.longestChain: 4 dev.cpsw.0.queue.rx.totalBuffers: 384 dev.cpsw.0.queue.rx.activeBuffers: 384 dev.cpsw.0.queue.rx.maxActiveBuffers: 384 dev.cpsw.0.queue.rx.availBuffers: 0 dev.cpsw.0.queue.rx.maxAvailBuffers: 55 dev.cpsw.0.queue.rx.totalEnqueued: 4201184 dev.cpsw.0.queue.rx.totalDequeued: 4200800 dev.cpsw.0.queue.rx.longestChain: 0 dev.cpsw.0.watchdog.resets: 0 pmather@beaglebone:~ % sysctl dev.cpsw | grep -i error dev.cpsw.0.stats.RxCrcErrors: 0 dev.cpsw.0.stats.RxAlignErrors: 0 dev.cpsw.0.stats.CarrierSenseErrors: 0 pmather@beaglebone:~ % uptime 11:19AM up 1 day, 13:43, 1 users, load averages: 0.93, 0.88, 0.81 The above is also after doing some iperf and inbound transfer tests = yesterday. > I wonder if your power supply is failing and injecting transient > glitches under heavy load or something? Hopefully, the OP is not powering the system via the OTG connector. I = always found my BBB to be somewhat flaky when powered that way. Cheers, Paul.= From owner-freebsd-arm@FreeBSD.ORG Sat Mar 14 16:11:20 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5C9809B8 for ; Sat, 14 Mar 2015 16:11:20 +0000 (UTC) Received: from BAY004-OMC3S17.hotmail.com (bay004-omc3s17.hotmail.com [65.54.190.155]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "*.outlook.com", Issuer "MSIT Machine Auth CA 2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 42D252A9 for ; Sat, 14 Mar 2015 16:11:19 +0000 (UTC) Received: from BAY182-W76 ([65.54.190.189]) by BAY004-OMC3S17.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.22751); Sat, 14 Mar 2015 09:11:19 -0700 X-TMN: [tBUpW7NRvE7FmWHAf+1iRg4QwW6RdACi] X-Originating-Email: [sgeos@hotmail.com] Message-ID: From: Brendan Sechter To: Matthias Gamsjager Subject: RE: FreeBSD 10.1 / 11 on a Raspberry Pi B+ / 2 ? Date: Sun, 15 Mar 2015 01:11:19 +0900 Importance: Normal In-Reply-To: References: , , <6ff566ec17fc2b0d61635d8886261d5a.squirrel@ikornapostur.1984.is>, , <028290c7462d8fcf63b07bfdbbd08897.squirrel@ikornapostur.1984.is>, , , <04594F43-C6FD-4798-ACFF-8BB7179A905F@bsdimp.com>, , Content-Type: text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: base64 MIME-Version: 1.0 X-OriginalArrivalTime: 14 Mar 2015 16:11:19.0686 (UTC) FILETIME=[81DDDA60:01D05E71] Cc: "freebsd-arm@freebsd.org" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Mar 2015 16:11:20 -0000 Jmd0OyBGcm9tOiBtZ2Ftc2phZ2VyQGdtYWlsLmNvbTxicj4mZ3Q7IERhdGU6IFNhdCwgMTQgTWFy IDIwMTUgMTA6Mjk6NTYgKzAxMDA8YnI+Jmd0OyBTdWJqZWN0OiBSZTogRnJlZUJTRCAxMC4xIC8g MTEgb24gYSBSYXNwYmVycnkgUGkgQisgLyAyID88YnI+Jmd0OyBDQzogZnJlZWJzZC1hcm1AZnJl ZWJzZC5vcmc8YnI+Jmd0Ozxicj4mZ3Q7ICZndDsgRnJvbSB3aGF0IEkgZ2F0aGVyLCB1LWJvb3Qg bmVlZHMgdG8gYmUgdXBkYXRlZC4gU2hvdWxkIEkgYmUgdXNpbmcgdGhlIG9mZmljaWFsIGRlbngu ZGU8YnI+Jmd0OyAmZ3Q7IHJlcG9zaXRvcnkgKGdpdDovL2dpdC5kZW54LmRlL3Byb2plY3RzL3Ut Ym9vdC5naXQpLCBvciBpcyB0aGVyZSBhIGJldHRlciB1LWJvb3QgcmVwb3NpdG9yeSB0bzxicj4m Z3Q7ICZndDsgdXNlIGF0IHRoaXMgcG9pbnQ/PGJyPjxicj5JIGFuc3dlcmVkIG15IG93biBxdWVz dGlvbi4gJm5ic3A7VGhlIGdpdDovL2dpdGh1Yi5jb20vZ29uem91YS91LWJvb3QtcGkuZ2l0IHJl cG9zaXRvcnkgaXM8ZGl2Pm1lbnRpb25lZCBpbiZuYnNwO2Nyb2NoZXQvYm9hcmQvUmFzcGJlcnJ5 UGkvc2V0dXAuc2guICZuYnNwO1RoYXQgcmVwb3NpdG9yeSB3YXMgbGFzdCB1cGRhdGVkIGluPC9k aXY+PGRpdj4yMDEyLiAmbmJzcDtJcyB0aGUgUGkgMiB3b3JrIGVudGlyZWx5IGNvbmZpZ3VyYXRp b24sIG9yIGlzIGFueSB1LWJvb3Qgd29yayBpbiBwcm9ncmVzcyBzaW1wbHk8L2Rpdj48ZGl2PnVu Y29tbWl0dGVkIGF0IHRoaXMgcG9pbnQ/PGJyPjxicj4mZ3Q7IFdoYXQgSSBnYXRoZXJlZCBpcyB0 aGF0IG1vcmUgbmVlZHMgdG8gYmUgZG9uZSB0aGVuIGp1c3QgYSBuZXdlcjxicj4mZ3Q7IHZlcnNp b24gb2YgdWJvb3QgdG8gZ2V0IGl0IHdvcmtpbmcuPGJyPjxicj48L2Rpdj48ZGl2PkluIHRoZW9y eSBpcyBzdXBwb3J0aW5nIHRoZSAWQkNNMjgzNiBTb0MgYWxsIHRoYXQgbmVlZHMgdG8gYmUgZG9u ZSwgb3IgaGF2ZSBvdGhlcjwvZGl2PjxkaXY+aW5jb21wYXRpYmlsaXRpZXMgYmVlbiBpZGVudGlm aWVkPzwvZGl2PjxkaXY+PGJyPjwvZGl2PjxkaXY+LUJyZW5kYW48L2Rpdj4gCQkgCSAgIAkJICA= From owner-freebsd-arm@FreeBSD.ORG Sat Mar 14 17:22:17 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8840957A; Sat, 14 Mar 2015 17:22:17 +0000 (UTC) Received: from BAY004-OMC3S11.hotmail.com (bay004-omc3s11.hotmail.com [65.54.190.149]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "*.outlook.com", Issuer "MSIT Machine Auth CA 2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6E9F9AE7; Sat, 14 Mar 2015 17:22:17 +0000 (UTC) Received: from BAY182-W52 ([65.54.190.187]) by BAY004-OMC3S11.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.22751); Sat, 14 Mar 2015 10:22:11 -0700 X-TMN: [KFMbmHQODfBrVzNmKGSIw0m8bpNEdCRO] X-Originating-Email: [sgeos@hotmail.com] Message-ID: From: Brendan Sechter To: "freebsd-arm@freebsd.org" , "freebsd-wireless@freebsd.org" Subject: Recommended WiFi / Bluetooth modules for embedded ARM projects? Date: Sun, 15 Mar 2015 02:22:10 +0900 Importance: Normal MIME-Version: 1.0 X-OriginalArrivalTime: 14 Mar 2015 17:22:11.0466 (UTC) FILETIME=[681FFEA0:01D05E7B] Content-Type: text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: base64 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Mar 2015 17:22:17 -0000 SSBhbSBsb29raW5nIGZvciB0aG91Z2h0cywgb3BpbmlvbnMgYW5kIHJlY29tbWVuZGF0aW9ucyBy ZWdhcmRpbmcgV2lGaSAvIEJsdWV0b290aCBtb2R1bGVzIGZvciBlbWJlZGRlZCBBUk0gRnJlZUJT RCBwcm9qZWN0cy4gIE15IHJlcXVpcmVtZW50cyBhcmUgODAyLjExYWMgLyBCbHVldG9vdGggNC4w LiAgVGhlIGlkZWFsIG1vZHVsZSBpcyBsb3cgY29zdCwgd29ya3Mgd2l0aCBtaW5pbWFsIGVmZm9y dCBhbmQgYWxzbyBoYXMgYSBVU0IgZG9uZ2xlIGFwcHJveGltYXRpb24gZm9yIGVhcmx5IHN0YWdl IGRldmVsb3BtZW50Lg0KLUJyZW5kYW4gCQkgCSAgIAkJICA= From owner-freebsd-arm@FreeBSD.ORG Sat Mar 14 17:51:45 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1073AD66 for ; Sat, 14 Mar 2015 17:51:45 +0000 (UTC) Received: from monday.kientzle.com (142-254-26-11.dsl.static.fusionbroadband.com [142.254.26.11]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AC36DDA7 for ; Sat, 14 Mar 2015 17:51:43 +0000 (UTC) Received: (from root@localhost) by monday.kientzle.com (8.14.4/8.14.4) id t2EHpfAW021152; Sat, 14 Mar 2015 17:51:41 GMT (envelope-from tim@kientzle.com) Received: from [192.168.2.105] (192.168.1.65 [192.168.1.65]) by kientzle.com with SMTP id dtf7im9jx76749dt6thwkhayvi; Sat, 14 Mar 2015 17:51:41 +0000 (UTC) (envelope-from tim@kientzle.com) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) Subject: Re: BeagleBone slow inbound net I/O From: Tim Kientzle In-Reply-To: <20150314031542.439cdee3@ivory.wynn.com> Date: Sat, 14 Mar 2015 10:51:39 -0700 Message-Id: <44FB8364-1310-4FBF-BA79-1B8837DE1C79@kientzle.com> References: <20150311165115.32327c5a@ivory.wynn.com> <89CEBFCA-6B94-4F48-8DFD-790E4667632D@kientzle.com> <20150314031542.439cdee3@ivory.wynn.com> To: Brett Wynkoop X-Mailer: Apple Mail (2.2070.6) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: freebsd-arm X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Mar 2015 17:51:45 -0000 > On Mar 14, 2015, at 12:15 AM, Brett Wynkoop = wrote: >=20 > [wynkoop@beaglebone ~]$ sysctl dev.cpsw | grep -i error > dev.cpsw.0.stats.RxCrcErrors: 262 > dev.cpsw.0.stats.RxAlignErrors: 231 > dev.cpsw.0.stats.CarrierSenseErrors: 0 > [wynkoop@beaglebone ~]$=20 >=20 > So we can see climbing errors. I am not sure how this compares to the > results of others. The above was during the first few minutes of a > buildworld from an nfs share. Your Ethernet hardware is detecting a lot of low-level network errors, which generally indicates hardware problems in your network: a bad cable maybe, or a dying switch or bad power supply. In any event, NFS throughput degrades rapidly on a poor network, so this probably explains your NFS slowness. There are a lot of error-related counters that aren=E2=80=99t called = Errors, by the way. In particular, the various collision and overrun counters don=E2=80=99t actually have =E2=80=9CError=E2=80=9D in the = name. On my BeagleBones, the only non-zero error counter I generally see is the RxStartOfFrameOverruns. Tim From owner-freebsd-arm@FreeBSD.ORG Sat Mar 14 18:12:34 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 94708FBC for ; Sat, 14 Mar 2015 18:12:34 +0000 (UTC) Received: from monday.kientzle.com (142-254-26-11.dsl.static.fusionbroadband.com [142.254.26.11]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2BC14F42 for ; Sat, 14 Mar 2015 18:12:33 +0000 (UTC) Received: (from root@localhost) by monday.kientzle.com (8.14.4/8.14.4) id t2EICTMC021284; Sat, 14 Mar 2015 18:12:29 GMT (envelope-from tim@kientzle.com) Received: from [192.168.2.105] (192.168.1.65 [192.168.1.65]) by kientzle.com with SMTP id 6n3eijpdzwcxhcmu2diwmjakzi; Sat, 14 Mar 2015 18:12:29 +0000 (UTC) (envelope-from tim@kientzle.com) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) Subject: Re: BeagleBone slow inbound net I/O From: Tim Kientzle In-Reply-To: <807E4289-EC2E-49F9-A909-4D2A2A149302@gromit.dlib.vt.edu> Date: Sat, 14 Mar 2015 11:12:28 -0700 Message-Id: <8EAD1C86-B7FD-4B30-A390-8E60D378224F@kientzle.com> References: <20150311165115.32327c5a@ivory.wynn.com> <89CEBFCA-6B94-4F48-8DFD-790E4667632D@kientzle.com> <20150314031542.439cdee3@ivory.wynn.com> <1426339400.52318.3.camel@freebsd.org> <807E4289-EC2E-49F9-A909-4D2A2A149302@gromit.dlib.vt.edu> To: Paul Mather X-Mailer: Apple Mail (2.2070.6) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: freebsd-arm X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Mar 2015 18:12:34 -0000 Paul=E2=80=99s data looks more like I expect from a healthy network: a few explanations below: > On Mar 14, 2015, at 8:42 AM, Paul Mather = wrote: >=20 > Here is another data point from my BBB: >=20 > pmather@beaglebone:~ % sysctl dev.cpsw > dev.cpsw.0.stats.GoodRxFrames: 4200799 > dev.cpsw.0.stats.RxStartOfFrameOverruns: 1708 In Paul's case, the only non-zero =E2=80=9Cerror=E2=80=9D count was the RxStartOfFrameOverruns, which impacted only 0.04% of all RX frames. This is comparable to what I see on my network. > dev.cpsw.0.queue.tx.totalBuffers: 128 > dev.cpsw.0.queue.tx.maxActiveBuffers: 7 > dev.cpsw.0.queue.tx.longestChain: 4 Paul=E2=80=99s stress tests managed to get 7 mbufs onto the hardware TX queue at the same time (out of 128 slots reserved for the hardware TX queue). At some point, there was a single TX packet that required 4 mbufs. > dev.cpsw.0.queue.rx.totalBuffers: 384 > dev.cpsw.0.queue.rx.maxAvailBuffers: 55 Paul managed to stress the RX side a little harder: At one point, there were 55 unprocessed mbufs on the hardware RX queue. If you managed to saturate the RX queue, that could also lead to packet loss, though TCP should adapt automatically; I wouldn=E2=80=99t expect a saturated queue to cause the kind of throughput degradation you would get from more random errors. Tim From owner-freebsd-arm@FreeBSD.ORG Sat Mar 14 18:48:46 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D867B7A6 for ; Sat, 14 Mar 2015 18:48:46 +0000 (UTC) Received: from wa3yre.wynn.com (wa3yre.wynn.com [199.89.147.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 92B1C27E for ; Sat, 14 Mar 2015 18:48:46 +0000 (UTC) Received: from ivory.wynn.com (mail.wynn.com [199.89.147.3]) (authenticated bits=0) by wa3yre.wynn.com (8.14.3/8.12.6) with ESMTP id t2EImgEM031979; Sat, 14 Mar 2015 14:48:43 -0400 (EDT) (envelope-from freebsd-arm@wynn.com) Date: Sat, 14 Mar 2015 14:48:41 -0400 From: Brett Wynkoop To: Peter Jeremy Subject: Re: zfs Message-ID: <20150314144841.789099da@ivory.wynn.com> In-Reply-To: <20150314072906.GA19582@server.rulingia.com> References: <20150313234510.3b41611b@ivory.wynn.com> <20150314072906.GA19582@server.rulingia.com> X-Mailer: Claws Mail 3.10.1 (GTK+ 2.24.25; x86_64-apple-darwin10.8.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-arm@freebsd.org, Mark Treacy X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Mar 2015 18:48:46 -0000 Ian's theory that my BBoard is sick is looking better all the time. Last night I took a rotating USB disk with a working zfs on it off of an x86 box where it was very happy and the BBone errored out just trying to see it, with the end result being no device being visible to the system. It looks like it is time to unbox my other BBone and give it a try. One thing I did discover though is that the cpu hit to write to a compressed zfs is not too much for the BeagleBone to handle. Any disk write actions I took against zfs completed much faster than they did against UFS. -Brett -- wynkoop@wynn.com http://prd4.wynn.com/wynkoop/pgp-keys.txt 917-642-6925 929-272-0000 April 19, 1775 An English attempt to confiscate guns from Americans triggered a successful revolution...... Dear Congress, that's a hint. From owner-freebsd-arm@FreeBSD.ORG Sat Mar 14 18:57:05 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 57A54991; Sat, 14 Mar 2015 18:57:05 +0000 (UTC) Received: from wa3yre.wynn.com (wa3yre.wynn.com [199.89.147.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 13B5A36F; Sat, 14 Mar 2015 18:57:04 +0000 (UTC) Received: from ivory.wynn.com (mail.wynn.com [199.89.147.3]) (authenticated bits=0) by wa3yre.wynn.com (8.14.3/8.12.6) with ESMTP id t2EIv2CY032337; Sat, 14 Mar 2015 14:57:03 -0400 (EDT) (envelope-from freebsd-arm@wynn.com) Date: Sat, 14 Mar 2015 14:57:02 -0400 From: Brett Wynkoop To: Paul Mather Subject: Re: BeagleBone slow inbound net I/O Message-ID: <20150314145702.5c3e9aed@ivory.wynn.com> In-Reply-To: <807E4289-EC2E-49F9-A909-4D2A2A149302@gromit.dlib.vt.edu> References: <20150311165115.32327c5a@ivory.wynn.com> <89CEBFCA-6B94-4F48-8DFD-790E4667632D@kientzle.com> <20150314031542.439cdee3@ivory.wynn.com> <1426339400.52318.3.camel@freebsd.org> <807E4289-EC2E-49F9-A909-4D2A2A149302@gromit.dlib.vt.edu> X-Mailer: Claws Mail 3.10.1 (GTK+ 2.24.25; x86_64-apple-darwin10.8.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-arm , Ian Lepore X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Mar 2015 18:57:05 -0000 On Sat, 14 Mar 2015 11:42:25 -0400 Paul Mather wrote: > Hopefully, the OP is not powering the system via the OTG connector. > I always found my BBB to be somewhat flaky when powered that way. > > Cheers, > > Paul. USB is connected to my FreeBSD 9.1 box for console and I have an independent 2 amp power supply connected to the coaxial power input. I will take a fast look at it with a voltmeter and see if it is solid. If that shows nothing wrong I guess I can pull the scope out and have a look at it with the scope for noise. -Brett -- wynkoop@wynn.com http://prd4.wynn.com/wynkoop/pgp-keys.txt 917-642-6925 929-272-0000 A free people ought to be armed. - George Washington From owner-freebsd-arm@FreeBSD.ORG Sat Mar 14 19:10:30 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 11C39A53 for ; Sat, 14 Mar 2015 19:10:30 +0000 (UTC) Received: from wa3yre.wynn.com (wa3yre.wynn.com [199.89.147.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C0DC863A for ; Sat, 14 Mar 2015 19:10:29 +0000 (UTC) Received: from ivory.wynn.com (mail.wynn.com [199.89.147.3]) (authenticated bits=0) by wa3yre.wynn.com (8.14.3/8.12.6) with ESMTP id t2EJASCL032890; Sat, 14 Mar 2015 15:10:28 -0400 (EDT) (envelope-from freebsd-arm@wynn.com) Date: Sat, 14 Mar 2015 15:10:27 -0400 From: Brett Wynkoop To: Tim Kientzle Subject: Re: BeagleBone slow inbound net I/O Message-ID: <20150314151027.10f9ec5a@ivory.wynn.com> In-Reply-To: <8EAD1C86-B7FD-4B30-A390-8E60D378224F@kientzle.com> References: <20150311165115.32327c5a@ivory.wynn.com> <89CEBFCA-6B94-4F48-8DFD-790E4667632D@kientzle.com> <20150314031542.439cdee3@ivory.wynn.com> <1426339400.52318.3.camel@freebsd.org> <807E4289-EC2E-49F9-A909-4D2A2A149302@gromit.dlib.vt.edu> <8EAD1C86-B7FD-4B30-A390-8E60D378224F@kientzle.com> X-Mailer: Claws Mail 3.10.1 (GTK+ 2.24.25; x86_64-apple-darwin10.8.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-arm X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Mar 2015 19:10:30 -0000 Tim- The idea of problems with network hardware never struck me as I see no similar problems with other systems on the net, but there could be a single bad port to which my BBone is connected. I will swap the BBone to another port on a different switch and see what errors happen, but since I am having what looks like USB problems as well I am leaning to the theory that I have flakey BBone hardware. -Brett -- wynkoop@wynn.com http://prd4.wynn.com/wynkoop/pgp-keys.txt 917-642-6925 929-272-0000 Amendment VIII Excessive bail shall not be required, nor excessive fines imposed, nor cruel and unusual punishments inflicted. From owner-freebsd-arm@FreeBSD.ORG Sat Mar 14 23:08:02 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4E6E1EAE; Sat, 14 Mar 2015 23:08:02 +0000 (UTC) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "raven.bwct.de", Issuer "BWCT" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id D2396D97; Sat, 14 Mar 2015 23:08:00 +0000 (UTC) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id t2EN7QRC034912 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sun, 15 Mar 2015 00:07:41 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) 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 t2EN7N59017835 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 15 Mar 2015 00:07:23 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.14.2/8.14.2) with ESMTP id t2EN7NfZ043765; Sun, 15 Mar 2015 00:07:23 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.14.2/8.14.2/Submit) id t2EN7NgD043764; Sun, 15 Mar 2015 00:07:23 +0100 (CET) (envelope-from ticso) Date: Sun, 15 Mar 2015 00:07:23 +0100 From: Bernd Walter To: Brendan Sechter Subject: Re: Recommended WiFi / Bluetooth modules for embedded ARM projects? Message-ID: <20150314230723.GA41587@cicely7.cicely.de> Reply-To: ticso@cicely.de References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD cicely7.cicely.de 7.0-STABLE i386 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-0.2 required=5.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9, DNS_FROM_AHBL_RHSBL=2.699, T_RP_MATCHES_RCVD=-0.01 autolearn=no version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de Cc: "freebsd-arm@freebsd.org" , "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Mar 2015 23:08:02 -0000 On Sun, Mar 15, 2015 at 02:22:10AM +0900, Brendan Sechter wrote: > I am looking for thoughts, opinions and recommendations regarding WiFi / Bluetooth modules for embedded ARM FreeBSD projects. My requirements are 802.11ac / Bluetooth 4.0. The ideal module is low cost, works with minimal effort and also has a USB dongle approximation for early stage development. I'd bought some nano WiFi USB on AliExpress marketed for Rasberry usage. They are Ralink RT5390 based, but I only used it for some small tests on a Wandboard, since a Wandboard is what I currently use as a lab gadged and the wandboard internal isn't supported by FreeBSD yet. Bluetooth USB isn't a real problem - most cheap should work. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm.