I have a qemu guest for experimenting with -current, 1 CPU & 64MiB RAM.
I gave it an NFS swap space to cope with a few small builds, and it now
locks up hard after touching that swap device.
>From ddb, stacks are like:
db{0}> t
sched_resched_cpu() at netbsd:sched_resched_cpu+0x3f
sleepq_wake()
Updating src tree:
P src/common/lib/libc/arch/i386/atomic/atomic.S
P src/distrib/notes/hp300/hardware
P src/distrib/sets/sets.subr
P src/distrib/sets/lists/base/mi
P src/distrib/sets/lists/comp/mi
P src/distrib/sets/lists/debug/mi
U src/distrib/sets/lists/debug/module.ad.aarch64
U
Since I have my qemu disk images on slow spinning rust host disks, when the
host disk is busy (esp. daily+security runs), I find my qemu vm's see disk
timeouts, and end up crashing. This isn't great behaviour.
Is anyone else seeing this? Any workarounds? I haven't looked, but I assume
I'd be able
On Fri, 1 May 2020 at 18:46, Thomas Klausner wrote:
>
> Could it be because I have a userland built with MKLLVM=yes?
I don't have it, to the best of my knowledge.
If it is of any help, I have
PKG_OPTIONS.llvm += -llvm-target-aarch64 -llvm-target-arm
-llvm-target-bpf -llvm-target-hexagon
Could it be because I have a userland built with MKLLVM=yes?
Thomas
On Fri, 1 May 2020 at 13:13, Thomas Klausner wrote:
>
> On Thu, Apr 30, 2020 at 06:22:01AM +0900, Ryo ONODERA wrote:
> > Hi,
> >
> > On my NetBSD/amd64 9.99.59 of 2020-04-29,
> > pkgsrc/www/firefox builds without any problem.
> >
> > I have tested with pkgsrc/lang/rust built on both 9.99.57
> >
On Fri, May 01, 2020 at 09:06:45AM +0100, Chavdar Ivanov wrote:
> Mine is from 6 hours ago and works fine.
Yes, a newer kernel worked.
Thomas
On Thu, Apr 30, 2020 at 06:22:01AM +0900, Ryo ONODERA wrote:
> Hi,
>
> On my NetBSD/amd64 9.99.59 of 2020-04-29,
> pkgsrc/www/firefox builds without any problem.
>
> I have tested with pkgsrc/lang/rust built on both 9.99.57
> and 9.99.59 of 2020-04-29, and I did not have any problem.
That's
On Fri, 1 May 2020 at 08:54, Thomas Klausner wrote:
>
> Hi!
>
> With an amd64 kernel from about 12 hours ago I get an immediate reboot
> after the boot prompt has decided it wants to load the kernel.
>
> I.e. I don't even see the numbers going up when the sections are loaded.
$ date
Fri May 1
Hi!
With an amd64 kernel from about 12 hours ago I get an immediate reboot
after the boot prompt has decided it wants to load the kernel.
I.e. I don't even see the numbers going up when the sections are loaded.
Thomas
On Fri, May 01, 2020 at 04:09:38AM +, Thomas Mueller wrote:
> Mercurial has a problem which may be resolved in a future release, if it
> hasn't already: dependency on the deprecated Python 2.7.
The information you read is outdated.
The pkgsrc package already builds hg against python 3.7.
11 matches
Mail list logo