Re: serial console
Patrick Welche writes: > On Wed, Feb 17, 2021 at 12:34:21AM -0800, Darrin B. Jewell wrote: >> >> I honestly hope this isn't related to your problem, but I did make a >> change to the amd64 cdrom building recently that is in this area >> and may be the issue. >> >>https://mail-index.netbsd.org/source-changes/2021/02/06/msg126676.html >> >> I thought I was only affecting the boot-com.iso install cd, but this >> change should probably be examined to make sure it isn't causing your >> problem. > > I didn't think your change had anything to do with it, but just in case, > I repeated the experiment with today's code (as you reverted your > change already) and had the same outcome. Thank you for the validation. I also did a clean build and checked all the bootloaders in OBJDIR and confirmed it only affects boot-com.iso. I'll recommit my change when I get a chance. Darrin > > > Cheers, > > Patrick
daily CVS update output
Updating src tree: P src/distrib/sets/lists/man/mi P src/distrib/sun2/miniroot/Makefile P src/distrib/sun2/miniroot/list P src/distrib/sun2/ramdisk/Makefile P src/doc/3RDPARTY P src/doc/CHANGES P src/etc/rc.d/amd P src/external/bsd/wpa/bin/hostapd/Makefile P src/external/mit/ctwm/libexec/ctwm_app_menu P src/lib/libc/time/Makefile P src/lib/libc/time/NEWS P src/lib/libc/time/theory.html P src/lib/libc/time/tz-art.html P src/lib/libc/time/tz-link.html U src/lib/libc/time/version P src/lib/libc/time/zic.8 P src/lib/libc/time/zic.c P src/sbin/ifconfig/Makefile.common P src/share/man/man4/Makefile P src/share/man/man4/pci.4 P src/share/man/man4/rge.4 P src/sys/arch/aarch64/aarch64/vm_machdep.c P src/sys/arch/aarch64/include/locore.h P src/sys/arch/amd64/conf/ALL P src/sys/arch/amd64/conf/GENERIC P src/sys/arch/amd64/conf/XEN3_DOM0 P src/sys/arch/arm/include/cpufunc.h P src/sys/arch/arm/pic/pic_splfuncs.c P src/sys/arch/evbarm/conf/GENERIC64 P src/sys/arch/i386/conf/ALL P src/sys/arch/i386/conf/GENERIC P src/sys/arch/powerpc/include/ofw_machdep.h P src/sys/arch/powerpc/include/oea/pmap.h P src/sys/arch/powerpc/oea/pmap.c P src/sys/arch/powerpc/oea/pmap_kernel.c P src/sys/arch/powerpc/powerpc/ofw_machdep.c P src/sys/dev/DEVNAMES P src/sys/dev/i2c/dstemp.c P src/sys/dev/i2c/lm75.c P src/sys/dev/pci/files.pci P src/sys/dev/pci/if_rge.c P src/sys/dev/pci/if_rgereg.h P src/sys/dev/pci/if_wm.c P src/sys/dev/usb/if_axe.c P src/sys/dev/usb/ukbd.c P src/sys/dev/usb/usbnet.c P src/sys/dev/usb/usbnet.h P src/sys/kern/kern_mutex.c P src/sys/kern/subr_lockdebug.c P src/usr.bin/netstat/vtw.c P src/usr.bin/newsyslog/newsyslog.8 P src/usr.bin/newsyslog/newsyslog.c Updating xsrc tree: Killing core files: Updating file list: -rw-rw-r-- 1 srcmastr netbsd 40291138 Mar 2 03:03 ls-lRA.gz
Automated report: NetBSD-current/i386 build success
The NetBSD-current/i386 build is working again. The following commits were made between the last failed build and the successful build: 2021.03.01.21.01.39 jakllsch src/distrib/sets/lists/man/mi,v 1.1716 Logs can be found at: http://releng.NetBSD.org/b5reports/i386/commits-2021.03.html#2021.03.01.21.01.39
Re: pkgsrc build hang of python38
On 2/03/21 6:51 am, Riccardo Mottola wrote: I thouht your cited entropy fix was a "once time" not to be reissued again (when? at every reboot? kernel update?) I don't think it is that user friendly to recularly "feed" this entropy... and it gets lost at the next reboot? Could we have a script on boot? The entropy is preserved across reboot by the shutdown hooks, so you normally only need to do this once. If you have the bad habit (like I do) of rebooting some systems with the "reboot" command instead of "shutdown -r", then your entropy will not be preserved. Once I setup some entropy and started using "shutdown -r" everything worked fine. Cheers, Lloyd
Re: pkgsrc build hang of python38
Hi Lloyd and Chavdar, Lloyd Parkes wrote: > > On 28/02/21 9:50 am, Riccardo Mottola wrote: >> python38 hangs during build. I tried several times, it hangs in >> exactly the same place again. I don't know of course where the issue >> comes from, since all is new now :) > > Do you have any console messages? Maybe messages about blocking the > python process because of not enough entropy? > > That's a problem I encountered when I was building Python on current. > If you are working on the console, then it's all obvious, but if you > aren't on the console then it's all mysterious. > > If that is your problem, then generate some entropy with something > like "ls -lR /" and then run > > dd if=/dev/urandom of=/dev/random bs=32 count=1 > sysctl -w kern.entropy.consolidate=1 > > See > https://mail-index.netbsd.org/current-users/2020/05/01/msg038495.html > for all the details. yes, I have an entropy issue, console shows: [ 300.511173] entropy: pid 3383 (python) blocking due to lack of entropy I wasn't running on console because it is "spammed" with cron message pam_vprompt(): no conversation functions - dont know where they are coming from I remember this discussion past year, now that you tell me. But I it was related to the fact that random wasn't initialized well for certain specific CPU architectures, but then the technical discussion died there. I don't see any warnings in dmesg during boot that my CPU/Architecture is missing some support, so I wasn't thinking of it anymore. I thouht your cited entropy fix was a "once time" not to be reissued again (when? at every reboot? kernel update?) I don't think it is that user friendly to recularly "feed" this entropy... and it gets lost at the next reboot? Could we have a script on boot? Riccardo
Automated report: NetBSD-current/i386 build failure
This is an automatically generated notice of a NetBSD-current/i386 build failure. The failure occurred on babylon5.netbsd.org, a NetBSD/amd64 host, using sources from CVS date 2021.03.01.18.08.36. An extract from the build.sh output follows: --- check_DESTDIR --- --- checkflist --- cd /tmp/build/2021.03.01.18.08.36-i386/src/distrib/sets && DESTDIR=/tmp/build/2021.03.01.18.08.36-i386/destdir MACHINE=i386 MACHINE_ARCH=i386 AWK=/tmp/build/2021.03.01.18.08.36-i386/tools/bin/nbawk CKSUM=/tmp/build/2021.03.01.18.08.36-i386/tools/bin/nbcksum DB=/tmp/build/2021.03.01.18.08.36-i386/tools/bin/nbdb EGREP=/tmp/build/2021.03.01.18.08.36-i386/tools/bin/nbgrep\ -E HOST_SH=/bin/sh MAKE=/tmp/build/2021.03.01.18.08.36-i386/tools/bin/nbmake MKTEMP=/tmp/build/2021.03.01.18.08.36-i386/tools/bin/nbmktemp MTREE=/tmp/build/2021.03.01.18.08.36-i386/tools/bin/nbmtree PAX=/tmp/build/2021.03.01.18.08.36-i386/tools/bin/nbpax COMPRESS_PROGRAM=gzip GZIP=-n XZ_OPT=-9 TAR_SUFF=tgz PKG_CREATE=/tmp/build/2021.03.01.18.08.36-i386/tools/bin/nbpkg_create SED=/tmp/build/2021.03.01.18.08.36-i386/tools/bin/nbsed TSORT=/tmp/build/2021.03.01.18.08.36-i386/tools/bin/nbtsort\ -q /bin/sh /tmp/build/2021.03.01.18.08.36-i386/src/distrib/sets/checkflist -L base -M /tmp/build/2021.03. 01.18.08.36-i386/destdir/METALOG.sanitised === 1 extra files in DESTDIR = Files in DESTDIR but missing from flist. File is obsolete or flist is out of date ? -- ./usr/share/man/html4/rge.html = end of 1 extra files === *** [checkflist] Error code 1 nbmake[2]: stopped in /tmp/build/2021.03.01.18.08.36-i386/src/distrib/sets 1 error nbmake[2]: stopped in /tmp/build/2021.03.01.18.08.36-i386/src/distrib/sets nbmake[1]: stopped in /tmp/build/2021.03.01.18.08.36-i386/src nbmake: stopped in /tmp/build/2021.03.01.18.08.36-i386/src ERROR: Failed to make release The following commits were made between the last successful build and the failed build: 2021.03.01.17.41.00 jakllsch src/sys/dev/usb/if_axe.c,v 1.132 2021.03.01.17.41.44 jakllsch src/sys/dev/usb/usbnet.c,v 1.40 2021.03.01.17.48.52 jakllsch src/sys/dev/pci/files.pci,v 1.435 2021.03.01.17.48.52 jakllsch src/sys/dev/pci/if_rge.c,v 1.17 2021.03.01.17.48.52 jakllsch src/sys/dev/pci/if_rgereg.h,v 1.5 2021.03.01.17.53.29 jakllsch src/sys/arch/amd64/conf/ALL,v 1.166 2021.03.01.17.53.29 jakllsch src/sys/arch/i386/conf/ALL,v 1.498 2021.03.01.17.58.33 jakllsch src/share/man/man4/rge.4,v 1.2 2021.03.01.18.01.05 jakllsch src/distrib/sets/lists/man/mi,v 1.1715 2021.03.01.18.01.05 jakllsch src/share/man/man4/Makefile,v 1.712 2021.03.01.18.08.36 jakllsch src/share/man/man4/pci.4,v 1.105 Logs can be found at: http://releng.NetBSD.org/b5reports/i386/commits-2021.03.html#2021.03.01.18.08.36
Re: serial console
On Wed, Feb 17, 2021 at 12:34:21AM -0800, Darrin B. Jewell wrote: > > I honestly hope this isn't related to your problem, but I did make a > change to the amd64 cdrom building recently that is in this area > and may be the issue. > >https://mail-index.netbsd.org/source-changes/2021/02/06/msg126676.html > > I thought I was only affecting the boot-com.iso install cd, but this > change should probably be examined to make sure it isn't causing your > problem. I didn't think your change had anything to do with it, but just in case, I repeated the experiment with today's code (as you reverted your change already) and had the same outcome. Cheers, Patrick
