Date: Sun, 25 Aug 2013 08:34:59 -0700 From: Tim Kientzle <tim@kientzle.com> To: freebsd-arm@freebsd.org Subject: Re: Pretty good RPi version? Message-ID: <E0163ECC-386A-415E-AC97-631DD9E0C7B1@kientzle.com> In-Reply-To: <CAJ-VmondKrRr_oxHDRULTiwb-EL3rXrVv1shJc09%2B4auXj%2ByCA@mail.gmail.com> References: <5218FBE2.2000907@m5p.com> <20130825.195532.59669686.shigeru@os-hackers.jp> <CAJ-VmondKrRr_oxHDRULTiwb-EL3rXrVv1shJc09%2B4auXj%2ByCA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E0163ECC-386A-415E-AC97-631DD9E0C7B1>