rry about the markup too much, I'll clean it up if necessary.
>
> -uwe
While it may not be the most obvious, the required information is
already in swapctl(8) (at least in -current) as far as I can tell.
--
Brad Spencer - b...@anduin.eldar.org - KC8VKS - http://anduin.eldar.org
ile as swap):
/swap/swap.1noneswapsw,priority=2 0 0
--
Brad Spencer - b...@anduin.eldar.org - KC8VKS - http://anduin.eldar.org
specially with pkgsrc.
--
Brad Spencer - b...@anduin.eldar.org - KC8VKS - http://anduin.eldar.org
hard drive in it that could not be upgraded as its physical size was not
standard. It used a cardbus card for networking. There was just enough
room for the newer kernel and modules in / but nothing else and no other
room for the sets anywhere. I used a thumb drive to transport the sets
into the system. Updated in one leap more or less...
--
Brad Spencer - b...@anduin.eldar.org - KC8VKS - http://anduin.eldar.org
other stuff. I don't know if
the patch caused the trouble, or if 10.99.6 has trouble for me in a
general sense (or if I am not allowed any more to make IFQ_MAXLEN larger
than the default). I won't have time to mess with this again for a
while, but the results were not encouraging.
--
Taylor R Campbell writes:
> [1:text/plain Hide]
>
>> Date: Tue, 01 Aug 2023 16:02:17 -0400
>> From: Brad Spencer
>>
>> Taylor R Campbell writes:
>>
>> > So I just added a printf to the kernel in case this jump happens. Can
>> > you upda
stile was shown).
I also probably should have mentioned that the DOM0 (NOT the DOMU) that
the target system is running under has HZ set to 1000. This is mostly
to help keep the ntpd and chronyd happy on the Xen guests. If the DOM0
is left at 100 the drift can be too much on the DOMU systems. Been
running like this for a long time...
--
Brad Spencer - b...@anduin.eldar.org - KC8VKS - http://anduin.eldar.org
Taylor R Campbell writes:
>> Date: Sun, 30 Jul 2023 14:56:53 -0400
>> From: Brad Spencer
>>
>> Taylor R Campbell writes:
>>
>> > Can you please try running with the attached patch and share the
>> > warnings it produces? Should give slightly
nt and NetBSD 10.x and/or perhaps rebuilding cscope indexes. I
am getting the general sense that some of the trigger for this problem
may be disk activity, but I can't really prove it.
--
Brad Spencer - b...@anduin.eldar.org - KC8VKS - http://anduin.eldar.org
Taylor R Campbell writes:
>> Date: Fri, 28 Jul 2023 07:42:04 -0400
>> From: Brad Spencer
>>
>> dtrace: invalid probe specifier sdt:xen:hardclock:jump { @ = quantize(arg1 -
>> arg0) } tick-10s { printa(@) }: probe description :::tick-10s does not match
>> a
Taylor R Campbell writes:
>> Date: Fri, 28 Jul 2023 07:42:04 -0400
>> From: Brad Spencer
>>
>> dtrace: invalid probe specifier sdt:xen:hardclock:jump { @ = quantize(arg1 -
>> arg0) } tick-10s { printa(@) }: probe description :::tick-10s does not match
>> a
Taylor R Campbell writes:
>> Date: Thu, 27 Jul 2023 11:17:30 -0400
>> From: Brad Spencer
>>
>> On the system that I have that exhibits the negative runtime problem, it
>> may very well be the case that hardclocks are missed for 4.3sec. The
>> system has to
in this case, is a rate.. that is, there are
continuous missed hardclocks even while idle.
If the system is freshly rebooted, the vmstat will not show anything
until after the system has been busy for a while and likewise the dtrace
is nearly free of events.
--
Brad Spencer - b...@anduin.eldar.org - KC8VKS - http://anduin.eldar.org
if any).
--
Brad Spencer - b...@anduin.eldar.org - KC8VKS - http://anduin.eldar.org
Taylor R Campbell writes:
>> Date: Thu, 20 Jul 2023 21:50:26 -0400
>> From: Brad Spencer
>>
>> With a DOMU kernel compiled with KDTRACE_HOOKS I get the following with
>> either of those dtrace probes on the DOMU:
>>
>> dtrace -n 'sdt:xen:
Taylor R Campbell writes:
>> Date: Thu, 20 Jul 2023 21:50:26 -0400
>> From: Brad Spencer
>>
>> With a DOMU kernel compiled with KDTRACE_HOOKS I get the following with
>> either of those dtrace probes on the DOMU:
>>
>> dtrace -n 'sdt:xen:
Taylor R Campbell writes:
>> Date: Thu, 20 Jul 2023 21:50:26 -0400
>> From: Brad Spencer
>>
>> With a DOMU kernel compiled with KDTRACE_HOOKS I get the following with
>> either of those dtrace probes on the DOMU:
>>
>> dtrace -n 'sdt:xen:
Taylor R Campbell writes:
>> Date: Thu, 20 Jul 2023 21:50:26 -0400
>> From: Brad Spencer
>>
>> With a DOMU kernel compiled with KDTRACE_HOOKS I get the following with
>> either of those dtrace probes on the DOMU:
>>
>> dtrace -n 'sdt:xen:
Taylor R Campbell writes:
>> Date: Sat, 08 Jul 2023 14:34:56 -0400
>> From: Brad Spencer
>>
>> Taylor R Campbell writes:
>>
>> > Can you either:
>>
>> Yes, I can perform as much of this as needed after I get some other
>> stuff in lif
Taylor R Campbell writes:
>> Date: Wed, 04 Jan 2023 14:43:25 -0500
>> From: Brad Spencer
>>
>> So... I have a PV+PVSHIM DOMU running a pretty recent 9.x on a DOM0
>> running a 9.99.xx kernel. The DOM0 is not large, a 4 processor E-2224
>> with 32GB of memo
> advance; that usually is enough.
Snapshot the zfs fileset when it is empty and rollback when you want to
make it empty again. Very quick works best when obj is its own
fileset.
>>
>> Do a clean build and everything should work.
>
> That's next.
--
Brad Spencer - b...@anduin.eldar.org - KC8VKS - http://anduin.eldar.org
ort one of the sensors
correctly and/or the APMI driver doesn't pull it correctly. It is a
fixed values that never changes for nothing...
--
Brad Spencer - b...@anduin.eldar.org - KC8VKS - http://anduin.eldar.org
en at pretty much the same
rate. I can't discount memory fragmentation, but I can't really say
that is much of a factor either. The system really should not need
anything like 12GB, and in fact top says that almost 9GB is free at this
point.
--
Brad Spencer - b...@anduin.eldar.org - KC8VKS - http://anduin.eldar.org
pening about every 30 hours.
Any help or hints would be greatly appreciated. With some planning I
can perform tests.
--
Brad Spencer - b...@anduin.eldar.org - KC8VKS - http://anduin.eldar.org
oes a
'cvs update' sort of thing from time to time, but than that is it right
now.
Any thoughts??
--
Brad Spencer - b...@anduin.eldar.org - KC8VKS - http://anduin.eldar.org
oes not work at least from 9.99.104.
--
Brad Spencer - b...@anduin.eldar.org - KC8VKS - http://anduin.eldar.org
addresses one at a
time to see if that actually works. Clearly large full table loads will
not work right now.
--
Brad Spencer - b...@anduin.eldar.org - KC8VKS - http://anduin.eldar.org
o 100%, probably loading
the large table...
--
Brad Spencer - b...@anduin.eldar.org - KC8VKS - http://anduin.eldar.org
n one system, but it is not likely to be critical to
anything. The system in question creates a whole ton of short lived
connections and I think I was trying to get them to expire quicker then
normal.
--
Brad Spencer - b...@anduin.eldar.org - KC8VKS - http://anduin.eldar.org
x
from their package manager won't work on a -current NetBSD kernel, which
panics somehere in the ACPI code. -current, after removing PVH and
PVHVM, worked fine on the version I built on 9.x.
--
Brad Spencer - b...@anduin.eldar.org - KC8VKS - http://anduin.eldar.org
bios and get a more or less working UEFI
setup without physical hardware (you will have to compile a custom
kernel without PVM or PVHVM support). I posted a note on port-xen a bit
ago about what works and what had trouble. You can probably do the same
thing with qemu and/or nvmm but I have not messed
ng... can't explain that as they claim
to all be the same version on the board and using the same SDCARD.
Literally using the same SDCARD on some has this problem and others do
not.
--
Brad Spencer - b...@anduin.eldar.org - KC8VKS - http://anduin.eldar.org
at one case a little strange.
On a -currentish test system with zfs filesets for object artifacts and
build artifacts if I didn't revert the mentioned patch to arc.c the
system could not make it though a build of qemu from pkgsrc and maybe
not even though unpacking the source for building (sorr
ementation. This makes me sad because zvols are
> such a tidy way to
> manage so many different kinds of things.
>
> -thanks
> -Brian
I freely admit that I don't use zvols very much in NetBSD, but did you
mess with the volblocksize any on the volume??
--
Brad Spencer - b...@anduin.eldar.org - KC8VKS - http://anduin.eldar.org
Matthias Petermann writes:
> Hello,
>
> On 01.07.22 12:48, Brad Spencer wrote:
>> "J. Hannken-Illjes" writes:
>>
>>>> On 1. Jul 2022, at 07:55, Matthias Petermann wrote:
>>>>
>>>> Good day,
>>>>
>>>>
rly all available "something" (pools, RAM, etc..) without
limit but have no specific proof (or there is a leak somewhere). I
mostly run 9.x ZFS right now (which may have other problems), and have
been setting maxvnodes way down for some time. If I don't do that the
Xen PV will hang itself up after a couple of 'build.sh release' runs
when the source and build artifacts are on ZFS filesets.
--
Brad Spencer - b...@anduin.eldar.org - KC8VKS - http://anduin.eldar.org
CHINE, I don't think
> it means that the driver is actually loaded.
... and a PVHVM guest can use the GENERIC kernel, but will want the Xen
devices too.
--
Brad Spencer - b...@anduin.eldar.org - KC8VKS - http://anduin.eldar.org
caused any
problems at all. Even a 7.x kernel, as an initial test, booted with a
4.x userland didn't really have any real trouble in that it ran all of
the /etc/rc stuff mostly just fine and I could log in. I would suspect
that going from 5.x forward would not be just too much of a problem.
--
Brad Spencer - b...@anduin.eldar.org - KC8VKS - http://anduin.eldar.org
Brad Spencer writes:
> You can also shut the DOMU down and present the disks to another DOMU in
> real time using "xl block-attach " just use the "r" device if you
> use devices or the file otherwise. I have done this for many years with
> PV DOMUs on many d
sually from the Xen
console in single user mode. This has also generally worked out just
fine and I use that in the case where I have made /usr a LVM disk inside
of the DOMU and it is a pain to present that to another DOMU.
--
Brad Spencer - b...@anduin.eldar.org - KC8VKS - http://anduin.eldar.org
4.0 to 7.x some time ago, the only thing that
I had problems with was anything that used scheduler activations since
that had been removed. For me this only effected stuff from pkgsrc, as
I also rolled in new userland at the same time.
--
Brad Spencer - b...@anduin.eldar.org - KC8VKS - http://anduin.eldar.org
r more of them.. I can also build a newer tree from -current. I was
working on device drivers in -current when I noted the mentioned panic.
> On Mon, Oct 18, 2021 at 3:42 AM Brad Spencer wrote:
>
>> Kimmo Suominen writes:
>>
>> > On Fri, Oct 01, 2021 at 05:03:01PM -0400,
Kimmo Suominen writes:
> On Fri, Oct 01, 2021 at 05:03:01PM -0400, Brad Spencer wrote:
>>
>> I did a build of -current from source taken on 2021-09-30 and had it
>> panic on my RPI 3.
>>
>> Just wondering if this a known problem. The panic is as foll
aef94: netbsd:cpu_hatch+0x1bc
[ 1.4478405] cpu1: End traceback...
Stopped in pid 0.16 (system) at netbsd:cpu_Debugger+0x4:bx r14
db{1}>
--
Brad Spencer - b...@anduin.eldar.org - KC8VKS - http://anduin.eldar.org
. It seems like the dts files that are in the tree would
contain a description for the SPI bus and the driver appears to have
been modified for FDT support. Running ofctl appears to show a number
of /spi@ lines but I don't know exactly what they indicate.
--
Brad Spencer - b...@anduin.elda
se a number of filesystems that have the quota
attribute (zfs get quota / zfs set quota=something ) set and do not
observe this. However, there are user quotas too and I don't use them.
I also am using ZFS with 9.x mostly and not -current. The latest build
I have is 9.99.74 and also does not appe
if it would boot a NetBSD DOM0 kernel. I am in
no position to try any tests with this right now personally, but it is
tempting as I have a EFI only laptop that I could probably replace the
hard drive temporarily.
--
Brad Spencer - b...@anduin.eldar.org - KC8VKS - http://anduin.eldar.org
ry
brief look and did not see anything that would exclude the devices
property, but did not have a great deal of time to sift though the code.
There may be a translation missing somewhere too.
--
Brad Spencer - b...@anduin.eldar.org - KC8VKS - http://anduin.eldar.org
ee that it isn't totally broken. I am by no means an expert in
the ZFS code, and I am not in a position to take a lot of time looking
at it right now, but if the trace back in the PR is correct, it makes it
almost totally though the mkdir call and crashes in the log create step
after th
stalled_src/PKGSRC_2018Q4
NAME USED AVAIL REFER MOUNTPOINT
tank/installed_src/PKGSRC_2018Q4 414M 250G 414M
/usr/installed_src/PKGSRC_2018Q4
These are DOMUs running NetBSD 9.0_STABLE from around September. I have
not tried this with -current, but there are n
oking at this. It is all over the
place, however, and currently if_wg does not build as a module anyway.
I think a lot more work will need to be done to get it there. I did not
look to see how any of the other if_xxx drivers deal with the lack of
INET or INET6 when modularized.
--
Brad Spencer - b...@anduin.eldar.org - KC8VKS - http://anduin.eldar.org
Roy Marples writes:
> On 11/11/2020 01:49, Brad Spencer wrote:
>> @@ -2352,6 +2361,7 @@
>> if (*af == AF_INET) {
>> packet_len = ntohs(ip->ip_len);
>> } else {
>> +#ifdef INET6
>> const struct ip6_hdr *ip6;
dr *)packet;
packet_len = sizeof(struct ip6_hdr) + ntohs(ip6->ip6_plen);
+#else
+ packet_len = decrypted_len + 1;
+#endif
}
WG_DLOG("packet_len=%u\n", packet_len);
--
Brad Spencer - b...@anduin.eldar.org - KC8VKS - http://anduin.eldar.org
Tom Ivar Helbekkmo writes:
> Brad Spencer writes:
>
>> Just wondering if anyone has succeeded in getting the wg(4) network
>> driver working with one of the commercial VPN providers? I attempted it
>> with one in particular, with an admitted slightly older -current a
Just wondering if anyone has succeeded in getting the wg(4) network
driver working with one of the commercial VPN providers? I attempted it
with one in particular, with an admitted slightly older -current and did
not succeed in getting it working.
--
Brad Spencer - b...@anduin.eldar.org
ant to try disabling dk support and retrying but haven't gotten around
> to it yet).
>
>
> Sevan
I am a little suprised that the import didn't work. "zpool import"
didn't find anything to import?? I currently use a gpt presented disk
between NetBSD and FreeBSD
Thomas
For gpt, I think anything will work, but I use fbsd-zfs especially if I
think I might share the pool with FreeBSD. I have also put pools on raw
devices and DOMU xbd* back stored by a LVM lvs. A lot of different
combinations seem to work fine.
--
Brad Spencer - b...@anduin.eldar.org - KC8VKS - http://anduin.eldar.org
0ec]...
> Trampoline space cannot be allocated; will try fallback.
>
>
>
> Cheers,
>
> Patrick
I didn't think that a DOM0 + UEFI worked anywhere very well at this
point or at least was not a default...
See https://wiki.xenproject.org/wiki/Xen_EFI for example...
or ...
on shutdown there too. I also had lvm involved so I was never
very sure what the problem was. This would have been in the late 6.x
and early 7.x days.
--
Brad Spencer - b...@anduin.eldar.org - KC8VKS - http://anduin.eldar.org
Andreas Gustafsson writes:
> Brad Spencer wrote:
>> I committed a change today to add USE_SHLIBDIR=yes to the libraries used
>> by /sbin/{zfs,mount_zfs,zpool}. The general effect will be to move the
>> libraries from /usr/lib to /lib and put compatibility links in place s
there may be problems,
but hopefully that is very uncommon.
--
Brad Spencer - b...@anduin.eldar.org - KC8VKS - http://anduin.eldar.org
with a 32bit
> kernel.
>
> Martin
Interesting... it appears we may still be building the solaris module.
Is that for dtrace??
--
Brad Spencer - b...@anduin.eldar.org - KC8VKS - http://anduin.eldar.org
quot;no"
> -CONFIGFILES+= zfs
> -.endif
> -
> .SUFFIXES: .in
> .in:
> ${_MKTARGET_CREATE}
> ${TOOL_SED} -e 's,@X11ROOTDIR@,${X11ROOTDIR},g' < ${.IMPSRC} >
> ${.TARGET}
> .endif
>
> +.if ${MKZFS} != "no"
> +CON
e wasn't installed ?
> --
> ./usr/share/man/html8/mount_zfs.html
> ./usr/share/man/man8/mount_zfs.8
> end of 2 missing files ==
I will look at that, but won't be for a bit... apparently a "./build.sh
.. release" does not show off that sort of
usual.
Add zfs=YES to your rc.conf. It works like LVM and raidframe now...
This get the module started early and allows you to disable the support
later (as opposed to by accident which is how it mostly worked before).
It was in the commit message, but should have been mentioned more
broadly.
y) but did not use a ZFS
filesystem/dataset for anything in the DOM0.
To cover the various cases, I don't see how one gets all the bits and
pieces in place in really any other manor. As I said, this is all done
more or less in this way for raidframe and LVM.
--
Brad Spencer - b...@anduin.eldar.org - KC8VKS - http://anduin.eldar.org
may end up doing more in the future, like zpool
import and the like.
Make sense??
--
Brad Spencer - b...@anduin.eldar.org - KC8VKS - http://anduin.eldar.org
nt problems. It will also apply cleanly to 9.0.
I won't get to committing this for a few days.
--
Brad Spencer - b...@anduin.eldar.org - KC8VKS - http://anduin.eldar.org
fferent once PVHVM is available, but for now, a DOM0 can not
use more than one CPU:
menu=Xen:load /netbsd-XEN3_DOM0.gz console=pc root=wd0a;multiboot /xen.gz
dom0_mem=2048M dom0_max_vcpus=1
--
Brad Spencer - b...@anduin.eldar.org - KC8VKS - http://anduin.eldar.org
Masanobu SAITOH writes:
> On 2018/10/03 5:47, Brad Spencer wrote:
>> m...@netbsd.org writes:
>>
>>> On Tue, Oct 02, 2018 at 06:55:48AM -0400, Brad Spencer wrote:
>>>>
[snip]
>> Here is more information:
>>
>> Screen shot of the pan
m...@netbsd.org writes:
> On Tue, Oct 02, 2018 at 06:55:48AM -0400, Brad Spencer wrote:
>>
>> Just wondering if anyone else has seen this, but I am getting panics on
>> boot during probe with sources after 2018-09-23 [at some point, at least
>> 2018-09-29 and 2018-
The panics seem related to setting up interrupts or printing
interrupt information in the intel wm(4) driver. The system in question
does not have a serial port on it in any form, but I can probably
capture a screen shot of the panic. The keyboard works and ddb seems
usable.
--
Brad Spence
erations, but it probably is the simplest. The 4.2 Android tablet
also worked and I moved files from it without any real problems. I
didn't fiddle much with the Cyanogenmod 13 based phone much as it way
too long for it to actually complete any operations. It was much
simpler to just sftp fil
ed from and not the one that
is chrooted to from init. It sound like in your case that would have
been the ramdrive, in my version of this it was an external flash disk.
I basically put a copy of /libdata on the boot media. Without doing
this, the firmware wouldn't be found even if it was presen
es to pass packets. I have not tried 802.11b, but
802.11g is fairly stable and works with wpa_supplicant.
--
Brad Spencer - b...@anduin.eldar.org - KC8VKS
http://anduin.eldar.org - & - http://anduin.ipv6.eldar.org [IPv6 only]
75 matches
Mail list logo