On Mon, Mar 09, 2020 at 09:55:41PM +1100, Paul Ripke wrote:
> Noticed this mucking with some pthread code that does pthread_setaffinity_np.
> Is this expected? I would've thought it still possible at securelevel 1?
>
> thing1:ksh$ sysctl security.models.extensions.user_set_cpu_affinity
>
Updating src tree:
P src/common/lib/libc/arch/m68k/string/ffs.S
P src/external/bsd/blacklist/bin/blacklistd.c
P src/external/bsd/blacklist/bin/conf.c
P src/external/bsd/blacklist/bin/run.c
P src/external/bsd/blacklist/bin/support.c
P src/external/bsd/blacklist/lib/bl.c
P
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
NetBSD Security Advisory 2020-002
=
Topic: Specific ICMPv6 error message packet can crash the system
Version:NetBSD-current: affected untill January 23, 2020
Just tried to upgrade a 8.99.19/amd64 box to today's 9.99.49, but I get
(gdb) x/s panicstr
0x81954800 : "kernel diagnostic assertion
\"(l->l_pflag & LP_INTR) == 0 || panicstr != NULL\" failed: file
\"/usr/src/sys/kern/kern_condvar.c\", line 170 "
(gdb) bt
#0 0x80224235 in
On Tue, Mar 10, 2020 at 08:11:46PM +0100, Frank Kardel wrote:
> interrupt total rate type
> vmcmd kills 179840 misc
> vmcmd extends 179800 misc
> vmcmd calls 1850330 misc
> pserialize
interrupt total rate type
vmcmd kills 179840 misc
vmcmd extends 179800 misc
vmcmd calls 1850330 misc
pserialize exclusive access 1450 misc
vmem static_bt_inuse
On Tue, Mar 10, 2020 at 07:30:33PM +0100, Frank Kardel wrote:
> No information about IPI in vmstat -i in DOM0 and DOMU.
the dom0 is not MP so I don't expect to see IPIs here.
But the domU is, so there should be IPIs here.
Hum, it looks like IPIs are in vmstat -e, not -i ...
sorry
>
> Otherwise
Dear current-users,
Can anyone else record audio correctly via ossaudio?
audiorecord seems to work as long as the frequency
divides the native frequency (see dmesg excerpt below)
audiorecord -d /dev/audio -c 1 -s 48000 -e slinear_le -P 16 /tmp/test.wav
seems to work fine, and
audiorecord
No information about IPI in vmstat -i in DOM0 and DOMU.
Otherwise it is usually responsive. Sometimes things get stuck but
switching a screen in screen seems to unstick things.
It seems like "wakeups" get sometimes lost.
Frank
On 03/10/20 19:20, Manuel Bouyer wrote:
On Tue, Mar 10, 2020
On Tue, Mar 10, 2020 at 06:48:14PM +0100, Frank Kardel wrote:
> [...]
>
> To me it looks more like locking issues or xen scheduling features.
yes, that could be. does vmstat -i show anything about IPIs ?
Is the domU otherwise responsive ?
--
Manuel Bouyer
NetBSD: 26 ans d'experience
DOMU
tty xbd0 dk0 xbd1
dk1 CPU
tin tout KB/t t/s MB/s KB/t t/s MB/s KB/t t/s MB/s KB/t
t/s MB/s us ni sy in id
045 15.330 0.006 15.330 0.006 29.09 38 1.079 29.09
38 1.079 0 0 0 0 100
0 284
On Tue, Mar 10, 2020 at 04:20:22PM +0100, Frank Kardel wrote:
> This is my first XEN setup so I may have misconfigured something:
>
> I have a 4G DOM0 on a 512G System with a EPYC 7302P 16-Core Processor.
>
> On that I configured a 400G DOMU with 12 vcpus. like this:
>
> name = "system"
>
I wonder if the issue is that the dom0 is single threaded, serializing
all the IO.
Have you done dd bs=1m from the dom0 raw disk, the dom0 backing file,
and the domU ('raw disk')? I used to see X, 0.9X, and (0.9)^2 X, ish,
on somewhat old Xen and older NetBSD.
I would run "systat vmstat" in
This is my first XEN setup so I may have misconfigured something:
I have a 4G DOM0 on a 512G System with a EPYC 7302P 16-Core Processor.
On that I configured a 400G DOMU with 12 vcpus. like this:
name = "system"
kernel = "/netbsd-XEN3_DOMU.gz"
memory = 40
cpus="all"
vcpus=4
maxvcpus=12
vif
On 2020-03-09, Chavdar Ivanov wrote:
> On Mon, 9 Mar 2020 at 19:52, Yorick Hardy wrote:
> >
> > Dear Chavdar,
> >
> > On 2020-03-08, Chavdar Ivanov wrote:
> > > Hi,
> > >
> > > On a -current (from today, but has happened before), when running a
> > > particular nvmm guest (32-bit Windows 10),
15 matches
Mail list logo
