Updating src tree:
P src/distrib/sets/lists/comp/md.amd64
P src/distrib/sets/lists/comp/md.i386
P src/distrib/sets/lists/tests/mi
P src/doc/CHANGES
P src/external/bsd/compiler_rt/lib/clang/lib/netbsd/asan-m64/Makefile
P src/external/bsd/compiler_rt/lib/clang/lib/netbsd/asan_cxx-m64/Makefile
P
On 30/04/21 9:50 pm, Joerg Sonnenberger wrote:
On Fri, Apr 30, 2021 at 05:31:53PM +1200, Lloyd Parkes wrote:
ceph4% hg --version
Mercurial Distributed SCM (version 5.3.2)
Please note that this is quite an old version and a lot of work on
improving both CPU time and memory use has
On 30/04/21 8:36 pm, Hauke Fath wrote:
Out of curiosity: Do you use a ZIL SLOG* volume with that setup? I
remember cvs operations used to be a lot slower on spinning rust than
on SSD.
I'm not using a SLOG. I couldn't be bothered setting one up on my crash
and burn systems. It doesn't seem
On Fri, Apr 30, 2021 at 08:50:10PM +0200, Manuel Bouyer wrote:
> On Fri, Apr 30, 2021 at 07:28:57PM +0100, Patrick Welche wrote:
> > On Fri, Apr 30, 2021 at 07:00:38PM +0200, Manuel Bouyer wrote:
> > > On Fri, Apr 30, 2021 at 05:55:37PM +0100, Patrick Welche wrote:
> > > > no luck. I see loading
On Fri, Apr 30, 2021 at 07:28:57PM +0100, Patrick Welche wrote:
> On Fri, Apr 30, 2021 at 07:00:38PM +0200, Manuel Bouyer wrote:
> > On Fri, Apr 30, 2021 at 05:55:37PM +0100, Patrick Welche wrote:
> > > no luck. I see loading /netbsd-XEN3_DOM0, and then it just reboots.
> > > Nothing more appears
hello. Because of the BIOS mixup on your serial port numbering, what
happens if you
change the com1 to com0 on the boot.cfg line where you tell xen to use com1?
(Leave the
consdev com0 alone for the NetBSD kernel). It may not work, but it might give
you more
information.
-Brian
On Fri, Apr 30, 2021 at 07:28:57PM +0100, Patrick Welche wrote:
> On Fri, Apr 30, 2021 at 07:00:38PM +0200, Manuel Bouyer wrote:
> > On Fri, Apr 30, 2021 at 05:55:37PM +0100, Patrick Welche wrote:
> > > no luck. I see loading /netbsd-XEN3_DOM0, and then it just reboots.
> > > Nothing more appears
On Fri, Apr 30, 2021 at 07:00:38PM +0200, Manuel Bouyer wrote:
> On Fri, Apr 30, 2021 at 05:55:37PM +0100, Patrick Welche wrote:
> > no luck. I see loading /netbsd-XEN3_DOM0, and then it just reboots.
> > Nothing more appears on the console. (-current XEN, xen.gz from
> > xenkernel415)
>
> Try
hello Patrick. Are you using a custom kernel with the console defined
in it? That
overrides any settings in the boot.cfg file. Another thing to check. Are you
using a machine
that has had NetBSD on it for a long time? Is it possible the boot block on
the boot disk is
old enough
On Fri, Apr 30, 2021 at 05:55:37PM +0100, Patrick Welche wrote:
> On Fri, Apr 30, 2021 at 04:52:41PM +0100, Patrick Welche wrote:
> > On Fri, Apr 30, 2021 at 05:23:54PM +0200, Manuel Bouyer wrote:
> > > On Fri, Apr 30, 2021 at 04:18:49PM +0100, Patrick Welche wrote:
> > > > On Fri, Apr 30, 2021 at
On Fri, Apr 30, 2021 at 04:52:41PM +0100, Patrick Welche wrote:
> On Fri, Apr 30, 2021 at 05:23:54PM +0200, Manuel Bouyer wrote:
> > On Fri, Apr 30, 2021 at 04:18:49PM +0100, Patrick Welche wrote:
> > > On Fri, Apr 30, 2021 at 05:04:34PM +0200, Manuel Bouyer wrote:
> > > > On Fri, Apr 30, 2021 at
The NetBSD-current/i386 build is working again.
The following commits were made between the last failed build and the
successful build:
2021.04.30.15.37.05 christos src/sys/arch/x86/include/gdt.h,v 1.1
Logs can be found at:
On Fri, Apr 30, 2021 at 05:23:54PM +0200, Manuel Bouyer wrote:
> On Fri, Apr 30, 2021 at 04:18:49PM +0100, Patrick Welche wrote:
> > On Fri, Apr 30, 2021 at 05:04:34PM +0200, Manuel Bouyer wrote:
> > > On Fri, Apr 30, 2021 at 03:44:46PM +0100, Patrick Welche wrote:
> > > > In /boot.cfg:
> > > >
>
On Fri, Apr 30, 2021 at 04:18:49PM +0100, Patrick Welche wrote:
> On Fri, Apr 30, 2021 at 05:04:34PM +0200, Manuel Bouyer wrote:
> > On Fri, Apr 30, 2021 at 03:44:46PM +0100, Patrick Welche wrote:
> > > In /boot.cfg:
> > >
> > > menu=Boot normally:rndseed /var/db/entropy-file;consdev
On Fri, Apr 30, 2021 at 05:04:34PM +0200, Manuel Bouyer wrote:
> On Fri, Apr 30, 2021 at 03:44:46PM +0100, Patrick Welche wrote:
> > In /boot.cfg:
> >
> > menu=Boot normally:rndseed /var/db/entropy-file;consdev com0,57600;boot
> >
> > # installboot -ve /dev/rsd0a
> > File system:
On Fri, Apr 30, 2021 at 03:44:46PM +0100, Patrick Welche wrote:
> In /boot.cfg:
>
> menu=Boot normally:rndseed /var/db/entropy-file;consdev com0,57600;boot
>
> # installboot -ve /dev/rsd0a
> File system: /dev/rsd0a
> Boot options:timeout 5, flags 0, speed 57600, ioaddr 0, console
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon5.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2021.04.30.13.55.18.
An extract from the build.sh output follows:
nbmake[3]: stopped in
In /boot.cfg:
menu=Boot normally:rndseed /var/db/entropy-file;consdev com0,57600;boot
# installboot -ve /dev/rsd0a
File system: /dev/rsd0a
Boot options:timeout 5, flags 0, speed 57600, ioaddr 0, console com0
Yet in dmesg:
com0 at isa0 port 0x3f8-0x3ff irq 4: ns16550a, 1-byte
On 4/30/21 7:31 AM, Lloyd Parkes wrote:
Hi all,
The problem reports people have in their emails are completely
inadequate for trying to determine what is going wrong for people
trying to access the NetBSD source.
I'm rsync'ing the CVS tree to my local server and then run CVS against
On Fri, 30 Apr 2021 19:51:27 +1000, matthew green wrote:
>> I too get long pauses with cvs, both at the beginning,
>> and even longer at the end after update is complete.
>
> the end part is most likely cvs cleaning up after itslf by
> removing all the subdirs it created but doesn't need.
...
> I too get long pauses with cvs, both at the beginning,
> and even longer at the end after update is complete.
the end part is most likely cvs cleaning up after itslf by
removing all the subdirs it created but doesn't need.
check disk io or ktrace for this part -- it's usually a
local iops
On Fri, Apr 30, 2021 at 05:31:53PM +1200, Lloyd Parkes wrote:
> ceph4% hg --version
> Mercurial Distributed SCM (version 5.3.2)
Please note that this is quite an old version and a lot of work on
improving both CPU time and memory use has been spend since then.
Joerg
> Hi all,
> The problem reports people have in their emails are completely inadequate for
> trying to determine what is going wrong for people trying to access the
> NetBSD
> source.
> Since I was the first person to post an inadequate report in this first batch,
> I'll go first at
On Fri, 30 Apr 2021 17:31:53 +1200, Lloyd Parkes wrote:
> The host is a Xeon E3-1241 v3 @ 3.50GHz with eight hyperthreads and
> 32GB RAM. It has a 128GB SSD for / and 4x4TB disks in a raidz zpool
> on /vol. All work is being done on /vol.
Out of curiosity: Do you use a ZIL SLOG* volume with
On Thu, 29 Apr 2021 at 22:20, Paul Goyette wrote:
>
> On Thu, 29 Apr 2021, Chavdar Ivanov wrote:
>
> > ...
> > Populating `work.efi'
> > Image `work.efi' complete
> > cat work.mbr.truncated work.efi imgroot.fs work.gpt > work.img
> > /home/sysbuild/amd64/tools/bin/nbgpt work.img biosboot -i 2
>
25 matches
Mail list logo
