Automated report: NetBSD-current/i386 test failure
This is an automatically generated notice of a new failure of the NetBSD test suite. The newly failing test case is: net/if_pppoe/t_pppoe:pppoe6_chap The above test failed in each of the last 4 test runs, and passed in at least 21 consecutive runs before that. The following commits were made between the last successful test and the failed test: 2020.04.24.03.22.06 thorpej src/sys/compat/linux/common/linux_exec.c,v 1.122 2020.04.24.03.22.06 thorpej src/sys/compat/linux/common/linux_sched.c,v 1.75 2020.04.24.03.22.06 thorpej src/sys/kern/kern_exec.c,v 1.499 2020.04.24.03.22.06 thorpej src/sys/kern/kern_exit.c,v 1.289 2020.04.24.03.22.06 thorpej src/sys/kern/kern_fork.c,v 1.223 2020.04.24.03.22.06 thorpej src/sys/kern/kern_lwp.c,v 1.235 2020.04.24.03.22.06 thorpej src/sys/kern/kern_proc.c,v 1.247 2020.04.24.03.22.06 thorpej src/sys/kern/sys_lwp.c,v 1.79 2020.04.24.03.22.06 thorpej src/sys/sys/lwp.h,v 1.207 2020.04.24.03.22.06 thorpej src/sys/sys/proc.h,v 1.363 2020.04.24.03.22.52 thorpej src/sys/sys/param.h,v 1.662 2020.04.24.03.25.20 thorpej src/tests/lib/libc/sys/t_ptrace_wait.c,v 1.172 2020.04.24.03.25.20 thorpej src/tests/lib/libc/sys/t_ptrace_x86_wait.h,v 1.25 2020.04.24.03.56.12 thorpej src/sys/rump/librump/rumpkern/lwproc.c,v 1.46 2020.04.24.04.34.57 ryo src/sys/dev/pci/if_aq.c,v 1.15 2020.04.24.04.37.27 ryo src/share/man/man4/aq.4,v 1.4 2020.04.24.04.55.40 ryo src/sys/dev/pci/if_aq.c,v 1.16 2020.04.24.05.21.18 thorpej src/sys/kern/kern_proc.c,v 1.248 Logs can be found at: http://releng.NetBSD.org/b5reports/i386/commits-2020.04.html#2020.04.24.05.21.18
Automated report: NetBSD-current/i386 test failure
This is an automatically generated notice of new failures of the NetBSD test suite. The newly failing test cases are: fs/vfs/t_mtime_otrunc:puffs_otrunc_mtime_update net/if_vlan/t_vlan:vlan_vlanid6 The above tests failed in each of the last 4 test runs, and passed in at least 23 consecutive runs before that. The following commits were made between the last successful test and the failed test: 2020.04.24.03.22.06 thorpej src/sys/compat/linux/common/linux_exec.c,v 1.122 2020.04.24.03.22.06 thorpej src/sys/compat/linux/common/linux_sched.c,v 1.75 2020.04.24.03.22.06 thorpej src/sys/kern/kern_exec.c,v 1.499 2020.04.24.03.22.06 thorpej src/sys/kern/kern_exit.c,v 1.289 2020.04.24.03.22.06 thorpej src/sys/kern/kern_fork.c,v 1.223 2020.04.24.03.22.06 thorpej src/sys/kern/kern_lwp.c,v 1.235 2020.04.24.03.22.06 thorpej src/sys/kern/kern_proc.c,v 1.247 2020.04.24.03.22.06 thorpej src/sys/kern/sys_lwp.c,v 1.79 2020.04.24.03.22.06 thorpej src/sys/sys/lwp.h,v 1.207 2020.04.24.03.22.06 thorpej src/sys/sys/proc.h,v 1.363 2020.04.24.03.22.52 thorpej src/sys/sys/param.h,v 1.662 2020.04.24.03.25.20 thorpej src/tests/lib/libc/sys/t_ptrace_wait.c,v 1.172 2020.04.24.03.25.20 thorpej src/tests/lib/libc/sys/t_ptrace_x86_wait.h,v 1.25 2020.04.24.03.56.12 thorpej src/sys/rump/librump/rumpkern/lwproc.c,v 1.46 2020.04.24.04.34.57 ryo src/sys/dev/pci/if_aq.c,v 1.15 2020.04.24.04.37.27 ryo src/share/man/man4/aq.4,v 1.4 2020.04.24.04.55.40 ryo src/sys/dev/pci/if_aq.c,v 1.16 2020.04.24.05.21.18 thorpej src/sys/kern/kern_proc.c,v 1.248 Logs can be found at: http://releng.NetBSD.org/b5reports/i386/commits-2020.04.html#2020.04.24.05.21.18
Automated report: NetBSD-current/i386 test failure
This is an automatically generated notice of new failures of the NetBSD test suite. The newly failing test cases are: fs/vfs/t_full:nfs_fillfs net/if_ipsec/t_ipsec_natt:ipsecif_natt_transport_null The above tests failed in each of the last 4 test runs, and passed in at least 24 consecutive runs before that. The following commits were made between the last successful test and the failed test: 2020.04.24.03.22.06 thorpej src/sys/compat/linux/common/linux_exec.c,v 1.122 2020.04.24.03.22.06 thorpej src/sys/compat/linux/common/linux_sched.c,v 1.75 2020.04.24.03.22.06 thorpej src/sys/kern/kern_exec.c,v 1.499 2020.04.24.03.22.06 thorpej src/sys/kern/kern_exit.c,v 1.289 2020.04.24.03.22.06 thorpej src/sys/kern/kern_fork.c,v 1.223 2020.04.24.03.22.06 thorpej src/sys/kern/kern_lwp.c,v 1.235 2020.04.24.03.22.06 thorpej src/sys/kern/kern_proc.c,v 1.247 2020.04.24.03.22.06 thorpej src/sys/kern/sys_lwp.c,v 1.79 2020.04.24.03.22.06 thorpej src/sys/sys/lwp.h,v 1.207 2020.04.24.03.22.06 thorpej src/sys/sys/proc.h,v 1.363 2020.04.24.03.22.52 thorpej src/sys/sys/param.h,v 1.662 2020.04.24.03.25.20 thorpej src/tests/lib/libc/sys/t_ptrace_wait.c,v 1.172 2020.04.24.03.25.20 thorpej src/tests/lib/libc/sys/t_ptrace_x86_wait.h,v 1.25 2020.04.24.03.56.12 thorpej src/sys/rump/librump/rumpkern/lwproc.c,v 1.46 2020.04.24.04.34.57 ryo src/sys/dev/pci/if_aq.c,v 1.15 2020.04.24.04.37.27 ryo src/share/man/man4/aq.4,v 1.4 2020.04.24.04.55.40 ryo src/sys/dev/pci/if_aq.c,v 1.16 2020.04.24.05.21.18 thorpej src/sys/kern/kern_proc.c,v 1.248 Logs can be found at: http://releng.NetBSD.org/b5reports/i386/commits-2020.04.html#2020.04.24.05.21.18
daily CVS update output
Updating src tree: P src/crypto/external/bsd/openssl/dist/CHANGES P src/crypto/external/bsd/openssl/dist/INSTALL P src/crypto/external/bsd/openssl/dist/NEWS P src/crypto/external/bsd/openssl/dist/README P src/crypto/external/bsd/openssl/dist/apps/build.info P src/crypto/external/bsd/openssl/dist/apps/dhparam.c P src/crypto/external/bsd/openssl/dist/apps/dsa.c P src/crypto/external/bsd/openssl/dist/apps/dsaparam.c P src/crypto/external/bsd/openssl/dist/apps/ec.c P src/crypto/external/bsd/openssl/dist/apps/ecparam.c P src/crypto/external/bsd/openssl/dist/apps/engine.c P src/crypto/external/bsd/openssl/dist/apps/gendsa.c P src/crypto/external/bsd/openssl/dist/apps/genrsa.c P src/crypto/external/bsd/openssl/dist/apps/ocsp.c P src/crypto/external/bsd/openssl/dist/apps/pkcs12.c P src/crypto/external/bsd/openssl/dist/apps/rsa.c P src/crypto/external/bsd/openssl/dist/apps/rsautl.c P src/crypto/external/bsd/openssl/dist/apps/s_time.c P src/crypto/external/bsd/openssl/dist/apps/srp.c P src/crypto/external/bsd/openssl/dist/apps/ts.c P src/crypto/external/bsd/openssl/dist/crypto/threads_win.c P src/crypto/external/bsd/openssl/dist/crypto/aes/aes_core.c P src/crypto/external/bsd/openssl/dist/crypto/aes/aes_local.h P src/crypto/external/bsd/openssl/dist/crypto/asn1/asn1_lib.c P src/crypto/external/bsd/openssl/dist/crypto/bio/bss_acpt.c P src/crypto/external/bsd/openssl/dist/crypto/ec/ec_asn1.c P src/crypto/external/bsd/openssl/dist/crypto/ec/ec_lib.c P src/crypto/external/bsd/openssl/dist/crypto/ec/ec_mult.c P src/crypto/external/bsd/openssl/dist/crypto/ec/ecp_smpl.c P src/crypto/external/bsd/openssl/dist/crypto/evp/e_aes.c P src/crypto/external/bsd/openssl/dist/crypto/rand/build.info P src/crypto/external/bsd/openssl/dist/crypto/rand/drbg_ctr.c P src/crypto/external/bsd/openssl/dist/crypto/x509/x509_vfy.c P src/crypto/external/bsd/openssl/dist/crypto/x509v3/v3_purp.c P src/crypto/external/bsd/openssl/dist/doc/man1/s_time.pod P src/crypto/external/bsd/openssl/dist/doc/man3/EVP_aes.pod P src/crypto/external/bsd/openssl/dist/doc/man3/RAND_set_rand_method.pod U src/crypto/external/bsd/openssl/dist/doc/man3/X509_check_purpose.pod P src/crypto/external/bsd/openssl/dist/include/openssl/opensslv.h P src/crypto/external/bsd/openssl/dist/ssl/t1_lib.c P src/crypto/external/bsd/openssl/dist/test/sm2_internal_test.c U src/crypto/external/bsd/openssl/dist/test/certs/ee-pathlen.pem P src/crypto/external/bsd/openssl/dist/test/certs/setup.sh P src/crypto/external/bsd/openssl/dist/test/recipes/25-test_verify.t P src/crypto/external/bsd/openssl/dist/test/recipes/70-test_sslsigalgs.t P src/doc/3RDPARTY P src/doc/CHANGES P src/share/man/man4/aq.4 P src/share/man/man4/options.4 P src/sys/arch/amd64/amd64/netbsd32_machdep.c P src/sys/arch/amd64/include/gdt.h P src/sys/arch/i386/include/gdt.h P src/sys/arch/macppc/conf/GENERIC P src/sys/arch/mips/cavium/dev/if_cnmac.c P src/sys/arch/mips/cavium/dev/octeon_gmx.c P src/sys/arch/mips/cavium/dev/octeon_gmxvar.h P src/sys/arch/x86/include/pmap.h P src/sys/arch/x86/include/specialreg.h P src/sys/arch/x86/x86/pmap.c P src/sys/arch/x86/x86/procfs_machdep.c P src/sys/arch/x86/x86/svs.c P src/sys/arch/x86/x86/sys_machdep.c P src/sys/compat/linux/common/linux_exec.c P src/sys/compat/linux/common/linux_sched.c P src/sys/dev/ata/ata.c P src/sys/dev/ata/ata_subr.c P src/sys/dev/ata/atavar.h P src/sys/dev/hid/hidkbdmap.c U src/sys/dev/i2c/asms.c P src/sys/dev/i2c/files.i2c P src/sys/dev/ic/hpet.c P src/sys/dev/ic/hpetvar.h P src/sys/dev/ic/vga.c P src/sys/dev/ic/vga_raster.c P src/sys/dev/isa/pcdisplay.c P src/sys/dev/pci/if_aq.c P src/sys/dev/pci/if_mcx.c P src/sys/kern/kern_exec.c P src/sys/kern/kern_exit.c P src/sys/kern/kern_fork.c P src/sys/kern/kern_lwp.c P src/sys/kern/kern_proc.c P src/sys/kern/sys_lwp.c P src/sys/kern/uipc_mbuf.c P src/sys/netinet6/in6_proto.c P src/sys/rump/librump/rumpkern/lwproc.c P src/sys/sys/lwp.h P src/sys/sys/param.h P src/sys/sys/proc.h P src/sys/uvm/uvm_bio.c P src/tests/lib/libc/sys/t_ptrace_wait.c P src/tests/lib/libc/sys/t_ptrace_x86_wait.h P src/tests/usr.bin/printf/printf.sh Updating xsrc tree: Killing core files: Updating tar files: src/top-level: collecting... replacing... done src/bin: collecting... replacing... done src/common: collecting... replacing... done src/compat: collecting... replacing... done src/crypto: collecting... replacing... done src/dist: collecting... replacing... done src/distrib: collecting... replacing... done src/doc: collecting... replacing... done src/etc: collecting... replacing... done src/external: collecting... replacing... done src/extsrc: collecting... replacing... done src/games: collecting... replacing... done src/gnu: collecting...pax: Unable to access src/gnu (No such file or directory) pax: WARNING! These file names were not selected: src/gnu done src/include: collecting... replacing... done src/lib: collecting... replacing... done src/libexec: collecting... replacing... done src/regress: collecting... replacing... done
Re: vboxguest on 9.0-BETA
Hi, 2020年4月24日(金) 17:30 Chavdar Ivanov : > > On Fri, 24 Apr 2020 at 05:10, itou keiki wrote: > > > > * The clipboard sharing is bidirectional. > > I don't think I've had the clipboard working at all, so I will check the > patch. I forgot to mention it, but I installed GCC7 from the package because it said it couldn't be built with the standard GCC8. Then I used a configure script like the following. ./configure --disable-hardening --only-additions --with-gcc=/usr/pkg/gcc7/bin/gcc \ --with-g++=/usr/pkg/gcc7/bin/g++ > Since VirtualBox 6.1.6 VBoxClient no longer supports VBoxSVGA; even if > its help shows the '--display' qualifier, it noloner works: > ... > $ /usr/local/bin/additions/VBoxClient --help > Usage: VBoxClient > --clipboard|--display|--checkhostversion|--seamless|--vmsvga|--vmsvga-x11[-d|--nodaemon] > Starts the VirtualBox DRM/X Window System guest services. OK. I used --vmsvga-x11 only. I put the following lines into my ~/.xinitrc. xrandr -s 1920x1080 # 1920x1200 does not work?? VBoxClient --clipboard VBoxClient --seamless VBoxClient --vmsvga-x11 > > Phenomenon with graphics controller VBoxVGA/VBoxSVGA > > X server does not start when I select vmware in the Driver of Xorg.conf > > Of course, it wouldn't start with the wrong driver, you need driver 'vmware'. When I set the video controller of the VBox host to VboxSVGA or VboxVGA, the video driver "vboxvideo" in the xorg.conf works with 256MB video memory. When with VMSVGA controller, "vmware" driver works with 128MB. (not tested with other amount of memory) > > Do you have any thoughts or comments? > > It would appear VBoxSVGA is phased out, as most of the guest operating > systems already have built-in 'vmware' graphics. If you select > VBoxSVGA display type, it display a permanent warning message that the > machine is configured with the wrong adapter, not with the recommended > VMSVGA. Yes, VBox Host always complains except for the VMSVGA controller, and once VMSVGA is the standard, the client-sid configuration will be a little easier. I have one correction. When the VMSVGA controller is used, the module auto-load does not work well when the VBoxService is started, and the following error message is output. VBoxService: error: VbglR3Init failed with rc=VERR_DEV_IO_ERROR It is OK to start the VBoxService after loading the vboxguest module beforehand. Also, when I quit VBoxService, unload the vboxgust module, and then start VBoxServie again, the automatic loading of the module worked. > The latest version of VBoxClient has --vmsvga and --vmsvga-x11 modes, > but I found that the former does not start at all, whereas the latter > starts but does not obtain the physical display sizes from VirtualBox; > with or without it xrandr works properly though - you can check the > available modes and resize the display to the value closest to > whatever you want. In my environment, on the VMSVGA controller and vmware driver, running "VBoxClient -f --vmsvga-x11" will output xrandr's errors. In the VboxVGA or VboxSVGA controller and vboxvideo driver, that command is silently quit. > I had initially problems with the mouse driver with the VMSVGA mode - > very likely my fault; eventually I sorted them out by selecting mouse > type 'multitouch tablet' and specifying > > Section "InputDevice" > Identifier "Mouse0" > Driver "ws" > Option "Protocol" "wmmouse" > Option "Device" "/dev/wsmouse" > Option "ZAxisMapping" "4 5 6 7" > EndSection > > in xorg.conf; mind you, dmesg shows > > % dmesg | grep mouse > [ 1.008399] wsmouse0 at pms0 mux 0 > [ 5.096014] wsmouse1 at ums0 mux 0 > [ 6.708228] wsmouse2 at ums1 mux 0 > [ 6.708228] wsmouse3 at uts0 mux 0 > [29.765032] wsmouse4 at vboxguest0 mux 0 > > % ls -l /dev/wsmouse* > crw--- 1 root wheel 65, 0 Jul 29 2019 /dev/wsmouse > crw--- 1 root wheel 49, 0 Jul 29 2019 /dev/wsmouse0 > crw--- 1 root wheel 49, 1 Jul 29 2019 /dev/wsmouse1 > crw--- 1 root wheel 49, 2 Jul 29 2019 /dev/wsmouse2 > crw--- 1 root wheel 49, 3 Jul 29 2019 /dev/wsmouse3 > > To get it working, you have to select /dev/wsmouse in xorg.conf, it > didn't work with the rest for me. Thank you for pointing. I commented out the "Protocol" "wsmouse" line and will enable it. > There is one more glitch - NetBSD has virtio driver, the network > interface - vioif - also works, seems fine; however, there is also > viroscsi driver in GENERIC: > vioscsi* at virtio? # Virtio SCSI device > > but this one does not recognize the vioscsi interface: > ... > Qumranet product 1048 (SCSI mass storage, revision 0x01) at pci0 dev > 15 function 0 not configured > ... This also reproduced for me. > Perhaps this doesn't matter a lot, though. Thank you for your informative comment, Chavdar! -- ITOU Keiki (I forgot I changed my own family name since I still use it for business..)
Re: Automated report: NetBSD-current/i386 test failure
Date:Fri, 24 Apr 2020 19:59:31 + (UTC) From:NetBSD Test Fixture Message-ID: <158775837076.23438.17159050926672197...@babylon5.netbsd.org> | The newly failing test cases are: | | usr.bin/printf/t_builtin:A_floats | usr.bin/printf/t_command:A_floats Those should be fixed already. kre
Re: vboxguest on 9.0-BETA
On Fri, 24 Apr 2020 at 05:10, itou keiki wrote: > > Hi! > > I tried running Virtualbox Guest Addition with NetBSD-9.99.56/amd64. The host > is Windows 10, Virtualbox-6.1.6. I appreciate the efforts of those involved. > > Because the version of xorg-server attached to NetBSD is 1.20.6, a patch like > the link below was needed to make GuestAdditions of Virtualbox work. This is > the difference against svn revision 83708. > > https://www.dropbox.com/s/hthsagl61oqhqhu/vbox-r83708-diff.txt.xz?dl=0 > > * The mouse driver of Xorg.conf uses "ws". 'Xorg -configure' sets 'mouse', which I manually change to 'ws'. Good if it is recognized properly, of course. > * The clipboard sharing is bidirectional. I don't think I've had the clipboard working at all, so I will check the patch. > * The loadable kernel module is automatically loaded when the VBoxService is > started. That's how it always have worked for me, I have never manually loaded vboxguest module (I always place it in the required location, though - in yout case: $ ls -l /stand/amd64/9.99.56/modules/vboxguest total 352 -rwxr-xr-x 1 root wheel 332088 Apr 19 18:59 vboxguest.kmod ... > > With the above settings, things are working for the most part, but there is a > small problem. I can select the screen resolution at Display->Virtual Screen > 1 in the virtual machine, but it doesn't change. I can still change the > screen size with xrandr though. Since VirtualBox 6.1.6 VBoxClient no longer supports VBoxSVGA; even if its help shows the '--display' qualifier, it noloner works: ... $ /usr/local/bin/additions/VBoxClient --help Usage: VBoxClient --clipboard|--display|--checkhostversion|--seamless|--vmsvga|--vmsvga-x11[-d|--nodaemon] Starts the VirtualBox DRM/X Window System guest services. Options: --clipboardstarts the shared clipboard service --display starts the display management service --checkhostversion starts the host version notifier service --seamless starts the seamless windows service --vmsvga starts VMSVGA dynamic resizing for DRM --vmsvga-x11 starts VMSVGA dynamic resizing for X11 -f, --foreground run in the foreground (no daemonizing) -d, --nodaemon continues running as a system service -h, --help shows this help text -v, --verbose increases logging verbosity level -V, --version shows version information % /usr/local/bin/additions/VBoxClient --display VBoxClient: error: unrecognized option '--display' VBoxClient: info: Try 'VBoxClient --help' for more information -- If the graphics selected is VBoxSVGA, you can still use '--display' with the older versions of VBoxClient, e.g. 6.1.5: $ /usr/local/bin/additions-99956/VBoxClient --display # version 6.1.6 fails VBoxClient: error: unrecognized option '--display' VBoxClient: info: Try 'VBoxClient --help' for more information $ /usr/local/bin/additions-99954/VBoxClient --display # version 6.1.4 starts properly $ ps ax | grep -i box 500 ? Ssl 0:15.53 /usr/local/bin/additions/VBoxService --pidfile /var/run/VBoxService.pid 1935 ? Ss 0:00.00 /usr/local/bin/additions-99954/VBoxClient --display 2193 ? S0:00.00 /usr/local/bin/additions-99954/VBoxClient --display - > > Phenomenon in the graphics controller VMSVGA > * When vboxvideo is selected in the Driver of Xorg.conf, it does not start > with an error. If my /etc/X11/xorg.conf specifies vboxvideo, but I have selected VMSVGA, then X does not start for me. > * Virtual machine resets when running X with 256MB of video memory, OK for > 128MB I haven't tried anything above 128MB video memory yet. > > Phenomenon with graphics controller VBoxVGA/VBoxSVGA > X server does not start when I select vmware in the Driver of Xorg.conf Of course, it wouldn't start with the wrong driver, you need driver 'vmware'. > > Do you have any thoughts or comments? It would appear VBoxSVGA is phased out, as most of the guest operating systems already have built-in 'vmware' graphics. If you select VBoxSVGA display type, it display a permanent warning message that the machine is configured with the wrong adapter, not with the recommended VMSVGA. The latest version of VBoxClient has --vmsvga and --vmsvga-x11 modes, but I found that the former does not start at all, whereas the latter starts but does not obtain the physical display sizes from VirtualBox; with or without it xrandr works properly though - you can check the available modes and resize the display to the value closest to whatever you want. I had initially problems with the mouse driver with the VMSVGA mode - very likely my fault; eventually I sorted them out by selecting mouse type 'multitouch tablet' and specifying Section "InputDevice" Identifier "Mouse0" Driver "ws" Option "Protocol" "wmmouse" Option "Device" "/dev/wsmouse" Option "ZAxisMapping" "4 5 6 7" EndSection in xorg.conf; mind you, dmesg
