On Tue, 25 Oct 2016 11:05:38 +0900
YongHyeon PYUN wrote:
> On Mon, Oct 24, 2016 at 02:03:37PM +0200, O. Hartmann wrote:
> > On Mon, 24 Oct 2016 14:14:00 +0900
> > YongHyeon PYUN wrote:
> >
> > > On Sun, Oct 23, 2016 at 01:25:38PM +0200, Hartmann, O. wrote:
> > > > I tried to report earlier
On Mon, Oct 24, 2016 at 02:03:37PM +0200, O. Hartmann wrote:
> On Mon, 24 Oct 2016 14:14:00 +0900
> YongHyeon PYUN wrote:
>
> > On Sun, Oct 23, 2016 at 01:25:38PM +0200, Hartmann, O. wrote:
> > > I tried to report earlier here that CURRENT does have some serious
> > > problems right now and one o
Hi All
I read that people successfully installed FreeBSD on 2014's MacBook Pros.
I just got a used machine (in excellent shape) and try to install FreeBSD
current from USB memory besides OSX and Linux.
Every time unpacking fails with WRITE_FPDMA_QUEUED timeout error.
I'm worried that the SSD ca
On Mon, Oct 24, 2016 at 10:01:48PM +0200, Hartmann, O. wrote:
> r307877 fails to buildkernel with the error shown below:
>
> [...]
> /usr/src/sys/x86/x86/cpu_machdep.c:564:1: error: function definition is
> not allowed here {
> ^
> /usr/src/sys/x86/x86/cpu_machdep.c:574:2: error: expected '}'
> }
On Mon, Oct 24, 2016 at 02:58:43PM -0400, Michael Butler wrote:
> It seems that compilation of -current fails in the case that KDB is not
> defined.
>
> I'm assuming that the following diff achieves what was intended:
>
> imb@vm01:/usr/src/sys/x86/x86> svn diff
> Index: cpu_machdep.c
> =
r307877 fails to buildkernel with the error shown below:
[...]
/usr/src/sys/x86/x86/cpu_machdep.c:564:1: error: function definition is
not allowed here {
^
/usr/src/sys/x86/x86/cpu_machdep.c:574:2: error: expected '}'
}
^
/usr/src/sys/x86/x86/cpu_machdep.c:541:1: note: to match this '{'
{
^
2 err
It seems that compilation of -current fails in the case that KDB is not
defined.
I'm assuming that the following diff achieves what was intended:
imb@vm01:/usr/src/sys/x86/x86> svn diff
Index: cpu_machdep.c
===
--- cpu_machdep.c
On Sat, 2016-10-15 at 09:36:27 -0700, Kevin Oberman wrote:
> On Sat, Oct 15, 2016 at 9:26 AM, Hans Petter Selasky
> wrote:
>
> > On 10/15/16 18:18, Ulrich Spörlein wrote:
> >
> >> Hey all, while 11.x is -STABLE now, this happens to my machine ever
> >> since I upgraded it to 11-CURRENT years ago.
On Mon, 24 Oct 2016 14:14:00 +0900
YongHyeon PYUN wrote:
> On Sun, Oct 23, 2016 at 01:25:38PM +0200, Hartmann, O. wrote:
> > I tried to report earlier here that CURRENT does have some serious
> > problems right now and one of those problems seems to be triggered by
> > the recent re(4) driver. Th