Hi, Friends.
NetBSD-current (-m amd64) stops the crosscompilling process on a Debian amd64
unstable box in the following place:
cc -O -o make ar.o arscan.o commands.o default.o dir.o expand.o file.o
function.o getopt.o getopt1.o implicit.o job.o main.o misc.o read.o remake.o
On Wed, Mar 28, 2018 at 06:08:46AM -0300, Mandacarú Cascavel wrote:
> NetBSD-current (-m amd64) stops the crosscompilling process on a Debian amd64
> unstable box in the following place:
Well, find out what provides alloca -> __alloca on Debian? That seems
broken, it should always map to
On 2018-03-28 18:23, 6b...@6bone.informatik.uni-leipzig.de wrote:
Any ideas how to narrow down the cause?
I would try it with fewer mount options if you can, you seemed to be
using
everything available in the original email.
Hi,
I’ve stumbled upon this too with recently upgraded machine (to NetBSD 8.0_BETA
(GENERIC.201803261630Z))
Kernel RNG “5887 68 5” runs test FAILURE: too many runs of 1 1s (2691 >=2685)
cprng 5887 68 5: failed statistical RNG test
The difference here is that the machine also loses network
On Wed, 28 Mar 2018 12:55:06 +0200
Joerg Sonnenberger wrote:
> On Wed, Mar 28, 2018 at 06:08:46AM -0300, Mandacarú Cascavel wrote:
> > NetBSD-current (-m amd64) stops the crosscompilling process on a Debian
> > amd64 unstable box in the following place:
>
> Well, find out what
Updating src tree:
P src/distrib/amd64/uefi-installimage/Makefile
P src/external/gpl3/gcc/dist/gcc/config/i386/constraints.md
P src/external/gpl3/gcc/dist/gcc/config/i386/i386-opts.h
P src/external/gpl3/gcc/dist/gcc/config/i386/i386-protos.h
P src/external/gpl3/gcc/dist/gcc/config/i386/i386.c
P
On Fri, 23 Mar 2018, SAITOH Masanobu wrote:
How old is your kernel?
If your kernel's ixgbe.c is older than 1.88.2.13 please update the latest
netbsd-8 and try. 1.88.2.13 (and 1.88.2.10) fixed serious interrupt problem.
I changed from 1.88.2.10 to 1.88.2.13. The problem was not solved. I
On Wed, Mar 28, 2018 at 06:23:56PM +0200, 6b...@6bone.informatik.uni-leipzig.de
wrote:
> I changed from 1.88.2.10 to 1.88.2.13. The problem was not solved. I have
> also tested the onboeard network card. After a few hours, the problem also
> occurred here. I still think it's a nfs problem.
>
>