hen ?
>
> No change. It attaches dwiic0 and then starts with the messages.
It could also be some sensors I guess. Any chance to see what attaches
at dwiic0 ? Maybe entering ddb before the console gets spammed ?
FWIW I have a laptop with the touchpad as ihidev@dwiic and it works
fine with RC6
--
Manuel Bouyer
NetBSD: 26 ans d'experience feront toujours la difference
--
On Mon, Dec 11, 2023 at 11:27:17AM -0800, Chuck Silvers wrote:
> On Fri, Dec 08, 2023 at 06:13:42PM +0100, Manuel Bouyer wrote:
> > Hello again
> > I see a second rare panic running ATF tests on Xen:
> > lib/libc/regex/t_exhaust (236/949): 1 test cases
> > regc
.
The first time seems to be
https://largo.lip6.fr/~bouyer/NetBSD-tests/xen/HEAD/i386-hvm/202310061820Z_anita.txt
and the second time was
https://largo.lip6.fr/~bouyer/NetBSD-tests/xen/HEAD/i386-hvm/202311250810Z_anita.txt
Has anyone else seen this ?
--
Manuel Bouyer
NetBSD: 26 ans d'experi
ems to be this:
https://largo.lip6.fr/~bouyer/NetBSD-tests/xen/HEAD/amd64-pv/202309261750Z_anita.txt
I see it for PV, PVH and HVM runs, but it's quite rare.
I am the only one seeing this ?
--
Manuel Bouyer
NetBSD: 26 ans d'experience feront toujours la difference
--
On Mon, Nov 13, 2023 at 08:34:04PM +0100, Manuel Bouyer wrote:
> Hello
> I'm facing an issue with postfix+openssl3 which may be critical (depending
> on how it can be fixed).
>
> Now my postfix setup fails to send mails with
> Nov 13 20:20:53 comore postfix/smtp[6449]: wa
d puts a note in
> the headers, but it shouldn't stop mail from going out.
Actually, the client is using SMTP AUTH, so making sure he's sending the
auth credentials to the right SMTP server is critical.
--
Manuel Bouyer
NetBSD: 26 ans d'experience feront toujours la difference
--
On Tue, Nov 14, 2023 at 02:39:53AM +, Taylor R Campbell wrote:
> [trimming tech-crypto from cc because this is a policy and
> configuration issue, not a cryptography issue]
>
> > Date: Mon, 13 Nov 2023 20:34:04 +0100
> > From: Manuel Bouyer
> >
> > I'm faci
ackExchange clarity, so ymmv.
I tried this; but nothing that I've tried in /etc/openssl/openssl.cnf
did seems to have any effect. I wonder if postfix is doing some specific
openssl setup that overrides the openssl.cnf settings.
But also note that I could not reproduce the problem with openssl s_client
--
Manuel Bouyer
NetBSD: 26 ans d'experience feront toujours la difference
--
On Mon, Nov 13, 2023 at 10:56:00PM +0100, Joerg Sonnenberger wrote:
> On Monday, November 13, 2023 8:34:04 PM CET Manuel Bouyer wrote:
> > Hello
> > I'm facing an issue with postfix+openssl3 which may be critical (depending
> > on how it can be fixed).
> >
> > N
On Mon, Nov 13, 2023 at 10:58:38PM +0100, Steffen Nurpmeso wrote:
> Manuel Bouyer wrote in
> :
> |On Mon, Nov 13, 2023 at 10:24:56PM +0100, Steffen Nurpmeso wrote:
> |> Manuel Bouyer wrote in
> |> :
> |>|Hello
> |>|I'm facing an issue with postfix+openss
On Mon, Nov 13, 2023 at 10:24:56PM +0100, Steffen Nurpmeso wrote:
> Manuel Bouyer wrote in
> :
> |Hello
> |I'm facing an issue with postfix+openssl3 which may be critical (depending
> |on how it can be fixed).
> |
> |Now my postfix setup fails to send mails with
>
ers with valid certificates.
The solution (from google) would be to force @SECLEVEL=0 but I didn't find
a way to do this for postfix. The solutions I've seen were for openvpn or
curl, but nothing about postfix :(
Any idea ?
--
Manuel Bouyer
NetBSD: 26 ans d'experience feront toujours la difference
--
On Sat, Oct 21, 2023 at 11:46:48AM +0200, Manuel Bouyer wrote:
> On Fri, Oct 20, 2023 at 06:47:54PM -0500, John D. Baker wrote:
> > On Thu, 19 Oct 2023, Manuel Bouyer wrote:
> >
> > > On Thu, Oct 19, 2023 at 08:46:27AM -0500, John D. Baker wrote:
> > >
> > &
On Fri, Oct 20, 2023 at 06:47:54PM -0500, John D. Baker wrote:
> On Thu, 19 Oct 2023, Manuel Bouyer wrote:
>
> > On Thu, Oct 19, 2023 at 08:46:27AM -0500, John D. Baker wrote:
> >
> > > [...]
> > > # link VERTHANDI/netbsd
> > > /r0/build/netb
i_md_vesa_modenum'
> [...]
>
> I have machines with ACPI for which "genfb" (or any DRMKMS framebuffer)
> is superfluous and therefore are omitted from the configuration.
Hello,
should be fixed on HEAD, will request a pullup to netbsd-10
--
Manuel Bouyer
NetBSD: 26 ans d'experience feront toujours la difference
--
On Tue, Oct 10, 2023 at 03:56:56PM +0200, Manuel Bouyer wrote:
> Hello
> with netbsd-10 from oct, 2 ftp fails to connect to https sites:
> tchatcha:/chroot/usr/pkgsrc-2023Q3/pkgsrc/sysutils/xenkernel418>ftp -o /tmp/o
> https://ftp.netbsd.org/
> Trying [2001:470:a085:999::21]:44
, I tried to re-run
certctl but it didn't help.
I see the same issue with downloads.xen.org
It seems that not all roots are installed ?
--
Manuel Bouyer
NetBSD: 26 ans d'experience feront toujours la difference
--
On Fri, Sep 15, 2023 at 02:00:31PM -, Michael van Elst wrote:
> bou...@antioche.eu.org (Manuel Bouyer) writes:
>
> >But the clock softint shouldn't be locked out for 16s, ever.
>
> Then the clock softint must have a higher priority than
> everything else incl
locked out for 16s, ever.
It means that userland processes are stuck too, as well as kernel threads.
This is a real bug, the network stack should be fixed to relax at
periodic intervals.
--
Manuel Bouyer
NetBSD: 26 ans d'experience feront toujours la difference
--
On Fri, Jul 07, 2023 at 05:10:33PM +, Taylor R Campbell wrote:
> > Date: Fri, 7 Jul 2023 17:56:42 +0200
> > From: Manuel Bouyer
> >
> > On Fri, Jul 07, 2023 at 01:11:54PM +, Taylor R Campbell wrote:
> > > - The magic numbers for debug.crashme.spl_spino
puctl offline 0
> sysctl -w debug.crashme_enable=1
> sysctl -w debug.crashme.spl_spinout=1 # IPL_SOFTCLOCK
> # verify system panics after 15sec
my sysctl command did hang, but the system didn't panic
>
> 7.cpuctl offline 0
> sysctl -w debug.crashme_enable=1
> sysctl -w debug.crashme.spl_spinout=5 # IPL_VM
> # verify system panics after 15sec
and this one did panic
--
Manuel Bouyer
NetBSD: 26 ans d'experience feront toujours la difference
--
esses on Xen IFs? Does an `arp -an' indicate this (I can't test this--
> no Xen set up.)
Xen IFs are no different from regular ethernert interfaces
--
Manuel Bouyer
NetBSD: 26 ans d'experience feront toujours la difference
--
gt; memory=512
> vcpus=2
> vif = ['mac=00:16:3E:00:00:01,bridge=bridge0,ip=192.168.2.51' ]
the ip= part is not used by NetBSD.
A fixed mac address shouldn't make a difference, it's the xl tool which
generates one if needed and the domU doesn't know if it's fixed or
auto-generated.
--
Manuel Bouyer
NetBSD: 26 ans d'experience feront toujours la difference
--
all() at netbsd:syscall+0x17c
[ 538.4648600] --- syscall (number 2) ---
[ 538.4822324] bb3b7027:
[ 538.4876585] cpu0: End traceback...
any idea ?
--
Manuel Bouyer
NetBSD: 26 ans d'experience feront toujours la difference
--
On Sun, May 29, 2022 at 01:18:16PM +0200, J. Hannken-Illjes wrote:
> > On 29. May 2022, at 08:30, Michael van Elst wrote:
> >
> > bou...@antioche.eu.org (Manuel Bouyer) writes:
> >
> >> Hello,
> >> do you have an idea on the problem in this thread:
ight (c) 1996, 1997, 1998, 1999,
> ```
>
> At the "1999," the Dom0 became frozen, again.
A recent change caused xenconsoled to hang, and possibly xenstore to
miss events too. Should be fixed with
src/sys/arch/xen/xen/xenevt.c 1.65
But the hang on the filesystem remains for me.
-
ion,
with or without -o log. It happens even if the dom0 has a single CPU.
Any idea how to debug this further ?
--
Manuel Bouyer
NetBSD: 26 ans d'experience feront toujours la difference
--
On Fri, May 27, 2022 at 04:41:29PM +0200, J. Hannken-Illjes wrote:
> > On 27. May 2022, at 16:24, Manuel Bouyer wrote:
> >
> > On Fri, May 27, 2022 at 02:52:55PM +0200, J. Hannken-Illjes wrote:
> >>> On 27. May 2022, at 14:41, Matthias Petermann
> >
On Fri, May 27, 2022 at 04:24:30PM +0200, Manuel Bouyer wrote:
> On Fri, May 27, 2022 at 02:52:55PM +0200, J. Hannken-Illjes wrote:
> > > On 27. May 2022, at 14:41, Matthias Petermann
> > > wrote:
> > >
> > > Hello Jürgen,
> > >
> &
ck() at netbsd:sleepq_block+0x12c
vndthread() at netbsd:vndthread+0x78c
So it looks like vnconfig waits for the vnd I/O to drain, but the vnd thread
is idle.
--
Manuel Bouyer
NetBSD: 26 ans d'experience feront toujours la difference
--
/p1.jpg
> https://www.petermann-it.de/tmp/p2.jpg
> https://www.petermann-it.de/tmp/p3.jpg
several processes in fstchg wait, a stack trace of these processes
(tr/t 0t or tr/a 0x would show theses) would help.
So it looks like a deadlock in the filesystem. What is your storage
configuration
ce vnd0d for domain 1
> [ 195.450054] xvif1i0: disconnecting
> ```
>
> After the messages appear on the system console, the system does not respond
> to any input either via SSH or on the local console. It seems to be frozen.
> I can still activate the kernel debugger with Control+Alt+Escape.
Can you get a stack trace, and processes list ?
--
Manuel Bouyer
NetBSD: 26 ans d'experience feront toujours la difference
--
s where threads hang
> waiting on locks and/or condvars. it would be more useful to test
> with a HEAD libpthread (which I'll guess requires a HEAD libc too).
the goal is to build the official netbsd-9 packages, so that's not an option
--
Manuel Bouyer
NetBSD: 26 ans d'experien
I see both in almost every pbulk run.
>
>
> please try this patch for the cmake variation of this hang:
>
> http://www.netbsd.org/~chs/diff.pthread-park-stuck.1
would this apply to netbsd-9 too ? The hang I'm seeing is on a system
with a HEAD kernel and a netbsd-9 userland
--
Man
sive lock
for a vnode, could fail to free the associated quota structure.
Shoudln't it wait for the exclusive vnlock or retry in this case ?
--
Manuel Bouyer
NetBSD: 26 ans d'experience feront toujours la difference
--
ption LOCKDEBUG is set.
>
> options LOCKDEBUG # expensive locking checks/support
>
> Should a bug report be made in this case? Or should problems that only occur
> when LOCKDEBUG is enabled be ignored?
Crash with LOCKDEBUG are not expected, so please report.
--
Manu
On Thu, Jan 06, 2022 at 11:38:58PM +, RVP wrote:
> On Thu, 6 Jan 2022, Manuel Bouyer wrote:
>
> > the second issue is that it expects /emul/linux/proc/self/fd/4 to be a
> > working
> > symlink, and on NetBSD it's not. Note that with /bin/ls I get something
> >
t;/proc/self/fd//4"
22875 1 ls RET readlink -1 errno 22 Invalid argument
If I can trust the ktrace output, fd/4 should point to /etc/spwd.db
On linux, strace shows it reading the link from /proc/self/exec, getting back
the executable path and doing a stat on it.
--
Manuel Bouyer
them
(Exec format error. Binary file not executable.).
Is there a way to convert the ELF header so that NetBSD can run them ?
thanks
--
Manuel Bouyer
NetBSD: 26 ans d'experience feront toujours la difference
--
ysctl -a | grep driver | tr ',' '\n' | grep 'x[be]*'
> ...
> [141 -1 xenevt]
> [142 142 xbd]
> [143 -1 xencons]
I think this lists all the known major numbers for the $MACHINE, I don't think
it means that the driver is actually loaded.
--
Manuel Bouyer
NetBSD: 26 ans d'ex
(probably wrong category as it seems to be a userland
bug). It's not related to entropy.
--
Manuel Bouyer
NetBSD: 26 ans d'experience feront toujours la difference
--
On Tue, Oct 05, 2021 at 03:57:14PM +0100, Robert Swindells wrote:
>
> Manuel Bouyer wrote:
> >I'm trying to run a binary-only linux program under NetBSD 9.2.
> >From what I found, the binary was built on Ubuntu 16.04
> >
> >The program dies at at specific point a
On Tue, Oct 05, 2021 at 01:08:52PM +0200, Manuel Bouyer wrote:
> On Tue, Oct 05, 2021 at 12:42:33AM -0400, Eric Hawicz wrote:
> >
> > On 10/4/2021 10:33 AM, Manuel Bouyer wrote:
> > > Hello
> > > I'm trying to run a binary-only linux program under NetBSD 9.2.
>
On Tue, Oct 05, 2021 at 12:42:33AM -0400, Eric Hawicz wrote:
>
> On 10/4/2021 10:33 AM, Manuel Bouyer wrote:
> > Hello
> > I'm trying to run a binary-only linux program under NetBSD 9.2.
> > From what I found, the binary was built on Ubuntu 16.04
> > [...]
> &g
er.
But when run on linux, this clone syscall straces to
CLONE_VM|CLONE_VFORK|SIGCHLD
I tried writing a program using fork(), vfork() or clone() but
none of them would use the clone() syscall as do my linux binary.
Any idea what could cause clone() to be used this way ?
Also, any idea about this fi
preciate it. (Hopefully Matt is still lurking on these mailing
> lists??)
I have:
isp0 at pci10 dev 0 function 0: QLogic FC-AL and 4Gbps Fabric PCI-E HBA
isp1 at pci10 dev 0 function 1: QLogic FC-AL and 4Gbps Fabric PCI-E HBA
connecting to a overland LTO changer
I don't have specific k
On Mon, Jun 28, 2021 at 08:15:29AM +0900, Rin Okuyama wrote:
> Hi,
>
> On 2021/06/28 2:40, Manuel Bouyer wrote:
> > Hello,
> > I'm trying to run a binary which wants GLIBCXX_3.4.21, while with the suse
> > packages we have GLIBCXX_3.4.19. Before I try grabbing newe
Hello,
I'm trying to run a binary which wants GLIBCXX_3.4.21, while with the suse
packages we have GLIBCXX_3.4.19. Before I try grabbing newer libraries,
has anyone tried to run linux binaries with more recent libraries ?
--
Manuel Bouyer
NetBSD: 26 ans d'experience feront toujours la
bus_probe(0,c05c076d,6,c1453c00,0,c0102031,c1453c00,d99000,c0b92200,0) at
netbsd:xenbus_probe+0x2d
[ 2.0100679] xenbus_probe_init(c1453c00,d99000,c0b92200,0,c0100084,0,0,0,0,0)
at netbsd:xenbus_probe_init+0x85
[ 2.0100679] cpu0: End traceback...
Any idea what changed recently ?
--
Manuel Bou
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.
> >
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 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 /va
;
> Thoughts?
one possibility is that the bios has com0 and com1 swapped.
In some case I had to explicitely set ioaddr with installboot to have
the serial console working.
--
Manuel Bouyer
NetBSD: 26 ans d'experience feront toujours la difference
--
On Sat, Apr 17, 2021 at 10:44:36PM +0200, Jaromír Dole?ek wrote:
> Le sam. 17 avr. 2021 à 19:49, Manuel Bouyer a écrit :
> >
> > On Sat, Apr 17, 2021 at 07:25:58PM +0200, Manuel Bouyer wrote:
> > > Hello
> > > trying a build.sh tools on linux I got:
> > >
On Sat, Apr 17, 2021 at 10:54:48AM -0700, Jason Thorpe wrote:
>
> > On Apr 17, 2021, at 10:48 AM, Manuel Bouyer wrote:
> >
> > Well, the build fails later with the same error.
> > Using "-V HOST_CFLAGS=-std=gnu99" allows the tools to build; maybe
> >
On Sat, Apr 17, 2021 at 07:25:58PM +0200, Manuel Bouyer wrote:
> Hello
> trying a build.sh tools on linux I got:
> /dsk/l1/misc/bouyer/HEAD/clean/src/tools/compat/../../lib/libc/regex/regcomp.c:
>
> In function '__regex_wctype':
> /dsk/l1/misc/bouyer/HEAD/clean/src/tools/com
ion outside of the loop
--
Manuel Bouyer
NetBSD: 26 ans d'experience feront toujours la difference
--
On Thu, Apr 15, 2021 at 01:39:37PM +0100, Patrick Welche wrote:
> On Thu, Apr 15, 2021 at 07:28:32AM -0400, Brad Spencer wrote:
> > Manuel Bouyer writes:
> >
> > > On Thu, Apr 15, 2021 at 09:53:50AM +0100, Patrick Welche wrote:
> > >> I have tried and f
that the
> working one is "BIOS" booting rather than EFI booting.
>
> Among all your xen success stories, are any of you EFI booting?
AFAIK EFI is not yet supported by Xen (maybe this is supported by 4.15,
I've not had a chance to try yet). I have it running on fairly recent
Dell
791121 sectors long:
#dd if=FreeBSD-12.2-RELEASE-amd64-mini-memstick.img.orig
of=FreeBSD-12.2-RELEASE-amd64-mini-memstick.img
791121+0 records in
791121+0 records out
#ls -l FreeBSD-12.2-RELEASE-amd64-mini-memstick.img
-rw-r--r-- 1 root wheel 405053952 Apr 11 11:56
FreeBSD-12.2-RELEASE-amd64-mini-memstick.img
#expr 405053952 / 512
791121
--
Manuel Bouyer
NetBSD: 26 ans d'experience feront toujours la difference
--
t; was from a later sparcV9 instruction...
>
> In any case, while one may be able to do that in 'gdb', when running
> normally, it is fatal and there is no recourse. Odd that it doesn't
> dump core.
It should not be fatal. The library traps sigill specially to test for
instruc
lling-replace gets me to a seemingly
> identical hang in cmake in a single package - misc/kdepim4 , in
> apparently the same spot. with similar trace. Attaching to the process
I see the same thing in bulk builds, with various kde packages.
When I asked I've been told that this was a known iss
On Mon, Apr 05, 2021 at 09:30:16AM -0700, Greg A. Woods wrote:
> At Mon, 5 Apr 2021 10:46:19 +0200, Manuel Bouyer
> wrote:
> Subject: Re: regarding the changes to kernel entropy gathering
> >
> > If I understood it properly, there's no need for
> being made "read-only" at the hardware level?
At last some SCSI devices had a pin to make then read-only. I used this
to build ssh gateways in the past ...
--
Manuel Bouyer
NetBSD: 26 ans d'experience feront toujours la difference
--
0 ??? collect
callout 108 skew estimate, collect, v, dv
cpurng 4096 rng estimate, collect, v
--
Manuel Bouyer
NetBSD: 26 ans d'experience feront toujours la difference
--
users--with all appropriate sysinst warnings of course.
If I understood it properly, there's no need for such a knob.
echo 0123456789abcdef0123456789abcdef > /dev/random
will get you back to the state we had in netbsd-9, with (pseudo-)randomness
collected from devices.
--
Manuel Bouyer
On Thu, Apr 01, 2021 at 04:13:59AM +, RVP wrote:
> > [...]
>
> Does this /etc/entropy-file match what's there in your /boot.cfg?
irrelevant for Xen, as Xen uses the multiboot protocol.
--
Manuel Bouyer
NetBSD: 26 ans d'experience feront toujours la difference
--
On Wed, Mar 31, 2021 at 09:58:48PM -0400, Thor Lancelot Simon wrote:
> On Wed, Mar 31, 2021 at 11:24:07AM +0200, Manuel Bouyer wrote:
> > On Tue, Mar 30, 2021 at 10:42:53PM +, Taylor R Campbell wrote:
> > >
> > > There are no virtual RNG devices on the sy
On Tue, Mar 30, 2021 at 10:42:53PM +, Taylor R Campbell wrote:
> > Date: Tue, 30 Mar 2021 23:53:43 +0200
> > From: Manuel Bouyer
> >
> > On Tue, Mar 30, 2021 at 02:40:18PM -0700, Greg A. Woods wrote:
> > > [...]
> > >
> > > Perhaps
he rnd rototill. Virtual devices are
not trusted.
The only way is to manually seed the pool.
--
Manuel Bouyer
NetBSD: 26 ans d'experience feront toujours la difference
--
s out/rom16.strip.o
> out/rom32seg.strip.o out/code32flat.o -o out/rom.o
> ld: out/code32flat.o: in function `memmove':
> /usr/pkgsrc/sysutils/xentools413/work/seabios-rel-1.12.1/./src/string.c:206:
> undefined reference to `memcpy'
strange, I don't get this on my test machine (on netbsd-9
On Tue, Oct 27, 2020 at 10:14:45AM +0100, Martin Husemann wrote:
> On Tue, Oct 27, 2020 at 09:42:41AM +0100, Manuel Bouyer wrote:
> > Hello,
> > in tests from 2020-10-25:
> > http://www-soc.lip6.fr/~bouyer/NetBSD-tests/xen/HEAD/
> > anita fails with
> > Could no
Hello,
in tests from 2020-10-25:
http://www-soc.lip6.fr/~bouyer/NetBSD-tests/xen/HEAD/
anita fails with
Could not locate a CD medium in any drive with the distribution sets
(for both amd64 and i386)
martin, could you please have a look ?
--
Manuel Bouyer
NetBSD: 26 ans d'experience feront
#include
> ^~
> compilation terminated.
> netbsd.c:30:10: fatal error: xen/xenio3.h: No such file or directory
This header is in src/sys/arch/xen/include, it should be installed along with
xenio.h
I just commited a fix for this.
--
Manuel Bouyer
NetBSD: 26 ans d'experience feront toujours la difference
--
Hello,
I will be upgrading the storage on {ftp,www,rsync,anoncvs}.fr.netbsd.org
in the next 2 days. This will requires several reboots and services
interruptions while datas are being moved around.
--
Manuel Bouyer
NetBSD: 26 ans d'experience feront toujours la difference
--
es what other OSes do with 'devtype=cdrom',
we were an outsider here.
For PV or PVH domUs you can omit the devtype keyword, it's only
needed for HVM guests (if you want to boot from the cdrom image).
--
Manuel Bouyer
NetBSD: 26 ans d'experience feront toujours la difference
--
..
[ 872.0704774] dumping to dev 168,1 (offset=524254, size=0): not possible
[ 872.0704774] rebooting...
Any idea what could have changed to cause this ?
2020-05-26 08:40 UTC builds did complete tests.
--
Manuel Bouyer
NetBSD: 26 ans d'experience feront toujours la difference
--
78): undefined reference to `msipic_get_pci_info'
> /home/sysbuild/amd64/tools/bin/x86_64--netbsd-ld: pci_intr_machdep.o:
> in function `pci_intr_release':
> pci_intr_machdep.c:(.text+0x775): undefined reference to
> `x86_pci_msix_release'
Did you clean the build directory ?
--
Manuel Bouy
e to boot ...
--
Manuel Bouyer
NetBSD: 26 ans d'experience feront toujours la difference
--
On Sun, May 10, 2020 at 02:36:15PM +0200, Rhialto wrote:
> Probably similarly, linking fails when building an amd64 MODULAR kernel,
> with some Xen-related undefined symbol errors:
Yes I posted a question to tech-kern, asking how to resolve this, I got
no reply so far.
--
Manuel
a variable overflow somewhere but I can't see how it relates to
64Gb. Does it work with 16Gb ?
Also could you try with a PVH or HVM guest ? These ones would use modules
from /stand/amd64/ and not /stand/amd64-xen/ and should be close to native.
I don't have a box with that much RAM to tes
| grep !$
modstat | grep bpfjit
bpfjit misc filesys -09174 sljit
xen1:/#modload pciverbose
xen1:/#modstat | grep !$
modstat | grep pciverbose
pciverbose misc filesys -0 218 pci
--
Manuel Bouyer
NetBSD: 26 ans d'experience feront toujours la difference
--
n/hypervisor.c:247:27: error: cast to pointer
> from integer of different size [-Werror=int-to-pointer-cast]
> HYPERVISOR_shared_info = (void *)(HYPERVISOR_shared_info_pa + KERNBASE);
Should be fixed with hypervisor.c 1.82
--
Manuel Bouyer
NetBSD: 26 ans d'experience feront toujours la difference
--
gt; error: out of memory
>
> and modload fails with the OOM error.
>
> Is this an expected behavior or a bug? (kern.securelevel is -1).
What does kern.module.path show for you ?
--
Manuel Bouyer
NetBSD: 26 ans d'experience feront toujours la difference
--
'
> /r0/build/current/tools/amd64/bin/i486--netbsdelf-ld: (.text+0x436):
> undefined reference to `HYPERVISOR_shared_info_pa'
Should be fixed now. Sorry for this
--
Manuel Bouyer
NetBSD: 26 ans d'experience feront toujours la difference
--
On Wed, Apr 08, 2020 at 08:26:33PM -, Michael van Elst wrote:
> bou...@antioche.eu.org (Manuel Bouyer) writes:
>
> >Hello,
> >we have a machdep.hypervisor sysctl which returns a specific string when
> >an hypervisor is detected. I'd like to change the string returned
ould
cause problems ?
--
Manuel Bouyer
NetBSD: 26 ans d'experience feront toujours la difference
--
There have been scheduler-related fixes in the last few days; did you
try with an up to date kernel ?
--
Manuel Bouyer
NetBSD: 26 ans d'experience feront toujours la difference
--
that in netbsd9 IPIs don't show up as such.
But there should be some crosscall broadcast. On a netbsd-9 pbulk host
I see more broadcast than unicast.
--
Manuel Bouyer
NetBSD: 26 ans d'experience feront toujours la difference
--
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.
I guess it could be related to IPIs.
But I'm running daily tests on domUs and I didn't notice anythin
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'e
eneck.
>
> Instead DOM0 is only seldom busy for IO. DOMU is crawling along sleeping
>
> at all sorts of places:
What does
iostat 5
show about the disks, in the dom0 and domU ?
--
Manuel Bouyer
NetBSD: 26 ans d'experience feront toujours la difference
--
On Mon, Jan 13, 2020 at 09:00:30PM +, Andrew Doran wrote:
> I reproduced it on native x86. It's a bug in the CPU topology code. Now
> fixed with revision 1.11 src/sys/kern/subr_cpu.c - sorry about that.
I confirm, I now see user activity on all CPUs. Thanks !
--
Manuel Bouyer
On Mon, Jan 13, 2020 at 07:11:21PM +, Andrew Doran wrote:
> On Mon, Jan 13, 2020 at 07:36:41PM +0100, Manuel Bouyer wrote:
>
> > On Mon, Jan 13, 2020 at 06:33:08PM +, Andrew Doran wrote:
> > > On Mon, Jan 13, 2020 at 05:43:51PM +0100, Manuel Bouyer wrote:
> >
On Mon, Jan 13, 2020 at 06:33:08PM +, Andrew Doran wrote:
> On Mon, Jan 13, 2020 at 05:43:51PM +0100, Manuel Bouyer wrote:
>
> > On Mon, Jan 13, 2020 at 04:59:50PM +0100, Manuel Bouyer wrote:
> > > It also sets rsp and rbp. I think rbp is not set by anything else, at
On Mon, Jan 13, 2020 at 05:43:51PM +0100, Manuel Bouyer wrote:
> On Mon, Jan 13, 2020 at 04:59:50PM +0100, Manuel Bouyer wrote:
> > It also sets rsp and rbp. I think rbp is not set by anything else, at last
> > in the Xen case.
> > The different rbp value would explain w
On Mon, Jan 13, 2020 at 04:59:50PM +0100, Manuel Bouyer wrote:
> It also sets rsp and rbp. I think rbp is not set by anything else, at last
> in the Xen case.
> The different rbp value would explain why in one case we hit a KASSERT()
> in lwp_startup later.
> But I don't know what p
83 bouyer330 8992K 2212K RUN/0 0:00 0.00% 0.00% nbmake
21137 bouyer330 7844K 1220K RUN/0 0:00 0.00% 0.00% sed
12098 bouyer330 4288K 164K RUN/0 0:00 0.00% 0.00% sh
22411 bouyer330 4288K 164K RUN/0 0:00 0.00% 0.00% cc
42 root 85080M 5768K poll/0 0:00 0.00% 0.00% sshd
--
Manuel Bouyer
NetBSD: 26 ans d'experience feront toujours la difference
--
pu_switchto() in cpu_hatch() it boots, but it seems
that all user processes are running on cpu0 only ...
I can't see what extra work the cpu_switchto() could be doing that would
matters, execpt maybe the %epb/rbp init. Any idea ?
--
Manuel Bouyer
NetBSD: 26 ans d'experience feront toujours la difference
--
On Mon, Jan 13, 2020 at 11:42:17AM +, Andrew Doran wrote:
> Hi Manuel,
>
> On Mon, Jan 13, 2020 at 10:56:23AM +0100, Manuel Bouyer wrote:
> > Hello,
> > A current Xen domU kernel fails to boot with:
> > [ 1.000] hypervisor0 at mainbus0: Xen version 4.11.3n
1 - 100 of 261 matches
Mail list logo
