From owner-freebsd-arm@FreeBSD.ORG Sun Aug 25 15:35:00 2013 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 9B640F42; Sun, 25 Aug 2013 15:35:00 +0000 (UTC) (envelope-from tim@kientzle.com) 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)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 763D523B1; Sun, 25 Aug 2013 15:35:00 +0000 (UTC) Received: (from root@localhost) by monday.kientzle.com (8.14.4/8.14.4) id r7PFYxs4016160; Sun, 25 Aug 2013 15:34:59 GMT (envelope-from tim@kientzle.com) Received: from [192.168.2.123] (CiscoE3000 [192.168.1.65]) by kientzle.com with SMTP id fti3xtthx68d6t7xnbbradebai; Sun, 25 Aug 2013 15:34:59 +0000 (UTC) (envelope-from tim@kientzle.com) Subject: Re: Pretty good RPi version? Mime-Version: 1.0 (Apple Message framework v1283) Content-Type: text/plain; charset=us-ascii From: Tim Kientzle In-Reply-To: Date: Sun, 25 Aug 2013 08:34:59 -0700 Content-Transfer-Encoding: 7bit Message-Id: References: <5218FBE2.2000907@m5p.com> <20130825.195532.59669686.shigeru@os-hackers.jp> To: freebsd-arm@freebsd.org X-Mailer: Apple Mail (2.1283) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Aug 2013 15:35:00 -0000 On Aug 25, 2013, at 5:07 AM, Adrian Chadd wrote: > Hi! > > All - if it's unstable, please complain loudly on -arm and -current and > file PRs. If you have the time, please help figure out which commit(s) > broke things. > > There's been plenty of "stuff is unstable" talk, but I'm not sure it's > percolated its way up to the people doing VM hacking on other platforms > (notably amd64) so they are likely unaware they've broken things. > > It's possible they've also broken things for MIPS, which has me worried. :( On a similar note: FreeBSD is starting the process for branching and releasing FreeBSD 10.0. (The whole process will take a few months, but it means we need to get bugs isolated and fixed NOW.) I would *love* to have a solid, stable FreeBSD/ARM for 10.0. (If nothing else, I started tinkering with BeagleBone in late 2011 specifically so I could move my personal email server onto one. ;-) To get there, we need as many people as possible: * Running the bleeding edge FreeBSD. * Reporting problems. * Helping to diagnose those problems. Q: Does anyone know a good way to test userland locking? Diane Bruce has been continuing to dig into the issue that broke sshd a while back; the clues point to some issue in jemalloc (possibly locking related?). Q: Has anyone tried running some or all of the FreeBSD regression tests? Tim