Re: Automated report: NetBSD-current/i386 build failure

2020-03-03 Thread Martin Husemann
On Tue, Mar 03, 2020 at 01:29:39PM +0200, Andreas Gustafsson wrote: > Would it be too much to ask that imports of entire new subsystems like > this be at least build tested with "build.sh release"? The lossage in this case seems to depend on -j values and whether you do incremental builds, so not

Re: OpenSSL 1.1.1 has incorrect map files

2020-01-24 Thread Martin Husemann
On Fri, Jan 24, 2020 at 08:00:51PM +0100, Adam wrote: > > I upgraded it to 1.1.1d, and synced the map files. > > > > christos > > Perfect! > I updates NodeJS packages. This caused build fallout on all 64 bit architectures but sparc64, maybe pkgsrc should enable the EC_GFp_nistp*_methods too?

Re: Clearing ghosts of wedges (you forgot the subject line)

2020-02-04 Thread Martin Husemann
On Tue, Feb 04, 2020 at 07:40:50AM -0500, MLH wrote: > Thanks. I have tried that. Always says the device is in use, even > though nothing associaated with it is mounted, etc. Are they part of a RAID set? That would qualify as "in use". Martin

Re: ZFS on root - almost there

2020-02-23 Thread Martin Husemann
On Sat, Feb 22, 2020 at 05:03:42PM +, Roy Marples wrote: > Wups! > I missed an instruction step to ensure the label of the FFS partiton is boot. > gpt label -i 1 -l boot wd0 > Replace 1 with the partition index and wd0 with the device. You can also set this directly in sysinst when creating

Re: Compile error in compat_crypto_50

2020-01-16 Thread Martin Husemann
On Thu, Jan 16, 2020 at 12:03:27AM -0800, David Hopper wrote: > For a few days now I'm unable to compile -current modules on Alpha > either natively or cross-compiled due to the following error: > > --- dependall-compat_crypto_50 --- > /raid/src/sys/opencrypto/ocryptodev.h: In function

Re: overflow in libsa dosfs, feature for efiboot (patches provided)

2020-01-21 Thread Martin Husemann
On Tue, Jan 21, 2020 at 01:12:58PM -0800, Rob Newberry wrote: > And the code in efi_block_probe will only identify partitions if: > > - it's GPT (mine isn't) > > - it's MBR (mine is) and it's a NETBSD partition type (mine isn't) OK, have to admit the code confuses me. I'm not

Re: overflow in libsa dosfs, feature for efiboot (patches provided)

2020-01-20 Thread Martin Husemann
On Mon, Jan 20, 2020 at 03:41:33PM -0800, Rob Newberry wrote: > Below are patches -- one to "dosfs.c" to fix the overflow problem, > one to "efiblock.c" to add the "deal with no disklabel" feature. I > don't know the proper way to propose or advocate for these, but I'm > sharing them here in the

Re: Current wisdom on printing from Firefox

2019-12-29 Thread Martin Husemann
On Sun, Dec 29, 2019 at 08:42:36PM +, David Brownlee wrote: > What is the current wisdom on printing from Firefox? > > It appears that from firefox-60 the ability to generale ps was > removed, so the lpd backend was also removed. It still works fine for me in firefox 70, but I compile with

Re: How to make XZ_SETS compress using multiple threads?

2020-01-05 Thread Martin Husemann
On Sun, Jan 05, 2020 at 05:34:51AM -0800, Paul Goyette wrote: > I see that we have an XZ_ARGS variable which we can force to define > with ``-V XZ_ARGS=-T6'' and that appears that it will add the "-T6" > argument when invoking xz to build sets. ... which won't help as the tools xz version is not

Re: xsrc build failure

2020-01-06 Thread Martin Husemann
On Mon, Jan 06, 2020 at 11:25:01AM +, Patrick Welche wrote: > yet neither src/sys/sys/queue.h nor > xsrc/external/mit/libdrm/dist/util_double_list.h > appear to have changed in ages?! It was sys/sched.h and I just fixed it. Martin

Re: failure to build current kernel (stripattach)

2020-03-11 Thread Martin Husemann
On Wed, Mar 11, 2020 at 09:32:38AM +0100, Riccardo Mottola wrote: > ${EXTRA_OBJ} vers.o swapnetbsd.o > /usr/src/obj/tooldir.NetBSD-9.99.34-amd64/bin/x86_64--netbsd-ld: > ioconf.o:(.rodata+0x120): undefined reference to `stripattach' > > > any clues? strip(4) has been removed, are you sure you

Re: current crashes on X start

2020-03-12 Thread Martin Husemann
On Thu, Mar 12, 2020 at 06:40:13PM +0100, Riccardo Mottola wrote: > Hi! > > I completed now build and full userland including X, installed. > > I launch X11. A cursor appears, evberything else is black. > Computer resets. > Fun. Give us some details ;-) I updated a machine today and it does

Re: problem w/dhcpcd vs libsupc++.a on sparc?

2020-04-20 Thread Martin Husemann
On Mon, Apr 20, 2020 at 12:39:01PM -0500, John D. Baker wrote: > #0 dhcp_handledhcp (ifp=0xedc1a2a0, bootp=0xefffd362, bootp_len=311, > from=0xefffd320) > at /x/netbsd-9/src/external/bsd/dhcpcd/dist/src/dhcp.c:2891 > 2891 if (state->xid != ntohl(bootp->xid)) { > (gdb) bt > #0

Re: dhcpcd hiccups in -current

2020-04-19 Thread Martin Husemann
On Sun, Apr 19, 2020 at 08:53:09AM -0500, John D. Baker wrote: > Although "/etc/master.passwd" is updated to add the "_dhcpcd" user, the > insecure "/etc/passwd" is not regenerated to reflect this addition. How did you update? postinstall(8) does no automatic updates for uid/gid, but prompts you

Re: init's MAKEDEV vs. postinstall fix (old tty nodes)

2020-03-27 Thread Martin Husemann
On Fri, Mar 27, 2020 at 08:36:39AM +0100, Thomas Klausner wrote: > So my question is: if "postinstall fix" removes these devices on an > upgrade, why does init still create them? This is mostly for install media where we want to avoid to create the ptyfs mount (and don't fear the security issues

Re: build failure in libz

2020-04-22 Thread Martin Husemann
On Wed, Apr 22, 2020 at 03:48:30PM +0900, Rin Okuyama wrote: > I don't understand why commits to phil-wifi affected to -HEAD... ARGH - I hate cvs. Will fix... Martin

Re: build failure in libz

2020-04-22 Thread Martin Husemann
On Wed, Apr 22, 2020 at 09:27:44PM +0900, Rin Okuyama wrote: > Seems fixed now. Thank you! No quite sure what happened, but every file affected by the re-adding that was from a vendor branch and unchanged on the wifi branch got its default branch set to trunk (instead of the vendor branch). spz

Re: build failure in libz

2020-04-22 Thread Martin Husemann
On Wed, Apr 22, 2020 at 01:45:25PM +0100, Robert Swindells wrote: > Do we need to do anything special to fix it in our checked out trees, or > will just a 'cvs update' do it ? I think a cvs up should do. Martin

Re: Build error when crypto and swcrypto are omitted from kernel

2020-05-10 Thread Martin Husemann
On Sun, May 10, 2020 at 07:52:42PM -, Michael van Elst wrote: > And I'd like to talk to Martin, since 100% of the task is done if > we just add the missing dependency without the option. Lets start with just the dependency and see if everything fits in the next build run. We can add the

Re: lang/rust build fails

2020-05-15 Thread Martin Husemann
On Fri, May 15, 2020 at 06:27:41AM -0500, Robert Nestor wrote: > Yes, and it appears to be different from what Chavdar has on his slightly > earlier system. > seed 0 ??? estimate, collect, v Bingo! You do not have a hardware random number generator, and your setup did not

Re: NFS swap on current appears to deadlock

2020-05-18 Thread Martin Husemann
On Mon, May 18, 2020 at 09:41:17PM +, Andrew Doran wrote: > 64 megs, I'm surprised it makes to the login prompt. Why suprised? I run several production XEN DomUs with 128 MB ram, and some of my regular test machines only have 64 MB. Martin

Re: lang/rust build fails

2020-05-14 Thread Martin Husemann
Can you show output (as root) of rndctl -l please? Martin

Re: lang/rust build fails

2020-05-15 Thread Martin Husemann
On Fri, May 15, 2020 at 09:15:20AM +0100, Chavdar Ivanov wrote: > Sure, here it is. Heh, sorry- I meant Robert. > rdrand 512 rng estimate, collect, v I wanted to know if a line with "rng" is in his output (just a wild guess). Martin

Re: ongoing git vs hg (was: github.com/NetBSD/src 5 days old?)

2020-05-14 Thread Martin Husemann
On Wed, May 13, 2020 at 09:16:31PM -0700, Greg A. Woods wrote: > I.e. the final repo DAG should contain all submitted commits, and all > that history should be visible to those who look for it (just as is the > case with merges from github "pull requests"). This is the case in our setup. In the

Re: How long to build from source?

2020-05-08 Thread Martin Husemann
On Fri, May 08, 2020 at 08:54:32AM -0400, Greg Troxel wrote: > Why do you need to know? It will almost certainly be less than a day. > Is that going to cause you do try netbsd, or not try netbsd? As others have said, it highly depends on your hard disk and amount of ram installed. Our build

Re: no entropy?

2020-09-10 Thread Martin Husemann
On Thu, Sep 10, 2020 at 04:06:12PM +0100, Patrick Welche wrote: > I just upgraded to ancient boxen to -current/amd64. One has its 256 bits, > the other has none?! I have tried playing spot the difference but > haven't spotted anything: Both machines do not have a proper hardware random number

Re: hang while updating pkg_rolling-replace libvdpau

2020-09-08 Thread Martin Husemann
On Mon, Sep 07, 2020 at 11:40:58PM +0200, Riccardo Mottola wrote: > > It mentions a workaround, but what does it mean to: > > dd if=/dev/urandom of=/dev/random bs=32 count=1 > > sysctl -w kern.entropy.consolidate=1 > > > I tried this "quick fix" and then was able to leave the laptop several

Re: arp: ioctl(SIOCGNBRINFO): Inappropriate ioctl for device

2020-09-16 Thread Martin Husemann
On Wed, Sep 16, 2020 at 10:52:46AM +0200, Thomas Klausner wrote: > Hi! > > I ran arp today and saw new errors: > > arp: ioctl(SIOCGNBRINFO): Inappropriate ioctl for device > ? (192.168.0.x) at > arp: ioctl(SIOCGNBRINFO): Inappropriate ioctl for device > ? (192.168.0.x) at > arp:

Re: arp: ioctl(SIOCGNBRINFO): Inappropriate ioctl for device

2020-09-16 Thread Martin Husemann
On Wed, Sep 16, 2020 at 11:05:49AM +0200, Thomas Klausner wrote: > The one with 192.168.0.x configured is wm0. (I only have an lo0 except for > that.) Strange, your kernel is newer or same age as your userland? Martin

Re: -current fails to boot

2020-10-04 Thread Martin Husemann
On Sun, Oct 04, 2020 at 01:52:43PM +0200, Martin Husemann wrote: > On Sun, Oct 04, 2020 at 02:51:16PM +0300, Andreas Gustafsson wrote: > > All, > > > > At least i386 and amd64 are currently in a state where installation > > using sysinst completes successfully, but

Re: -current fails to boot

2020-10-04 Thread Martin Husemann
On Sun, Oct 04, 2020 at 02:51:16PM +0300, Andreas Gustafsson wrote: > All, > > At least i386 and amd64 are currently in a state where installation > using sysinst completes successfully, but the installed system fails > to boot. The problem appears to have started yesterday during a > period of

Re: UEFI boot on amd64 and i386?

2020-10-11 Thread Martin Husemann
On Mon, Oct 12, 2020 at 03:06:56AM +, Thomas Mueller wrote: [..] > -r--r--r-- 1 root wheel 216493 Jul 23 2019 bootia32.efi > -r--r--r-- 1 root wheel 204662 Jul 23 2019 bootx64.efi [..] > If I want to boot NetBSD-i386, could I use /usr/mdec/bootia32.efi, > /usr/mdec/bootx64.efi, or

Re: file system corruption

2020-10-11 Thread Martin Husemann
On Sun, Oct 11, 2020 at 11:19:16PM +0200, Thomas Klausner wrote: > I don't know enough about the internals of the hg and sqlite3, but I > also saw a broken zip archive and had a good copy for comparison. In > that case, a block of 256 bytes was zero instead of the real data. Do you know the file

Re: if_percpuq_softint/pool_sysctl panics on ure0

2020-08-28 Thread Martin Husemann
On Fri, Aug 28, 2020 at 12:04:04PM +0100, David Brownlee wrote: > ure0: discarding oversize frame (len=1757) > ure0: discarding oversize frame (len=8136) Try newer -current, ure had a very recent change in that area. Martin

Avoid -current for today :-/

2020-08-21 Thread Martin Husemann
Carefull when updating, -current is broken in several ways (does not compile for 32bit architectures, make is broken, maybe more). Should be fixed soon... Martin

Re: cannot allocate memory running mame

2020-10-01 Thread Martin Husemann
On Thu, Oct 01, 2020 at 01:56:15PM +0200, Thomas Klausner wrote: > Program Headers: > Type Offset VirtAddr PhysAddr > FileSizMemSiz Flags Align [..] > LOAD 0x 0x0040

Re: cannot allocate memory running mame

2020-10-01 Thread Martin Husemann
On Thu, Oct 01, 2020 at 01:27:38PM +0200, Thomas Klausner wrote: > but that was not sufficient. > > > du -sh /usr/pkg/bin/mame > 269M/usr/pkg/bin/mame that is .. big. Can you show readelf -l output for the binary? Martin

Re: cannot allocate memory running mame

2020-10-01 Thread Martin Husemann
On Thu, Oct 01, 2020 at 02:03:30PM +0200, Martin Husemann wrote: > On Thu, Oct 01, 2020 at 01:56:15PM +0200, Thomas Klausner wrote: > > Program Headers: > > Type Offset VirtAddr PhysAddr > > FileSizMemSiz

Re: cannot allocate memory running mame

2020-10-01 Thread Martin Husemann
On Thu, Oct 01, 2020 at 02:06:55PM +0200, Thomas Klausner wrote: > Actually, that is the size of mame stripped, so yes, I need this bigger :) The unstripped code size should not be bigger, symbols are a separate (non loadable) section. > Should we bump it in general? Don't think so (but also

Re: mesalib abort

2020-09-17 Thread Martin Husemann
On Thu, Sep 17, 2020 at 02:11:13PM +0100, Patrick Welche wrote: > #2 0x7f7ff160c63d in pthread_create (thread=0x2f9d, > thread@entry=0x7f7fd588, attr=attr@entry=0x0, > startfunc=startfunc@entry=0x7f7fed764930 , > arg=arg@entry=0x7f7ff7e9f230) at

Re: odd missing symbols like rumpns_lockdebug_* in an i386 build

2020-05-28 Thread Martin Husemann
On Thu, May 28, 2020 at 01:48:49PM -0700, Greg A. Woods wrote: > So, I thought I'd try to find out where these symbols might have come > from, but I came up completely empty with no matches: > > $ cd /usr/src > $ find . -type f -print0 | xargs -0 fgrep rumpns_lockebug_ > $ > >

Re: ctype and gcc9

2020-09-21 Thread Martin Husemann
On Mon, Sep 21, 2020 at 09:32:08AM +0100, Patrick Welche wrote: > Since gcc9, essentially every ctype using piece of software fails with > >error: array subscript has type 'char' [-Werror=char-subscripts] > > which prompts a style question: cast every argument of every call to > a ctype

Re: build-success/install-fault on i486 with xsrc

2020-10-27 Thread Martin Husemann
On Tue, Oct 27, 2020 at 10:57:28PM +0100, Miranda van den Breukelingen wrote: > installed it with ./build.sh -u -U install=/ I get a fine install but on > postinstall it tells me /usr/src/sbin/postinstall/postinstall is not > available. I checked and fixed it manually with the new build

Re: All ATF curses tests failing on babylon5 i386

2020-10-27 Thread Martin Husemann
On Tue, Oct 27, 2020 at 11:53:47AM +0100, Herbert J. Skuhra wrote: > Maybe a typo in t_curses.sh? > > cvs diff -u -r 1.17 -r 1.18 tests/lib/libcurses/t_curses.sh > > - $(atf_get_srcdir)/director $2 \ > [...] > + $(atf_get_srcdir)/director/director $2 \ > Yes, plus another similar

Re: install from CD fails on Xen

2020-10-27 Thread Martin Husemann
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 not locate a CD medium in any drive with the distribution sets > (for both amd64 and i386) > > martin, could you

Re: early tools -current build failure

2020-07-19 Thread Martin Husemann
On Sun, Jul 19, 2020 at 01:42:30PM +0100, Chavdar Ivanov wrote: > Any ideas? Perhaps I've missed something new in the BUILDING file? > there is nothing particular in these two lines of the bsd.nls.mk: make(1) is broken right now. Martin

Re: NetBSD-7.0 boots OK and NetBSD-8.0 hangs/crashes during boot on a MacBook7,1

2020-07-06 Thread Martin Husemann
On Mon, Jul 06, 2020 at 09:52:31AM +0100, Mike Pumford wrote: > Like it or not its probably going to be a long term requirement to have > console USB support. If not for the serial output its becoming more and more > necessary just to get a console keyboard for DDB. USB keyboards as console in

Re: NetBSD-7.0 boots OK and NetBSD-8.0 hangs/crashes during boot on a MacBook7,1

2020-07-06 Thread Martin Husemann
On Mon, Jul 06, 2020 at 12:34:32PM +0300, Andreas Gustafsson wrote: > Why would acting as a device be needed? To emulate a serial console on an USB OTG port. Martin

Re: NetBSD-7.0 boots OK and NetBSD-8.0 hangs/crashes during boot on a MacBook7,1

2020-07-06 Thread Martin Husemann
On Mon, Jul 06, 2020 at 07:55:29AM -0700, Brian Buhrow wrote: > hello. In my case, there are times when I want a serial console, for > set up or troubleshooting, but cannot use the built-in display for various > reasons. So, I think it would be useful in more situations than might > first

Re: NetBSD-7.0 boots OK and NetBSD-8.0 hangs/crashes during boot on a MacBook7,1

2020-07-06 Thread Martin Husemann
On Mon, Jul 06, 2020 at 05:07:51PM +0100, Mike Pumford wrote: > A quick look around suggests that some of the very high end gaming ones > don't. Also assuming users will actually be able to find a cable to actually > hook up the motherboard COM port is optimistic. You would probably have to > get

Re: recent changes to pthread_fork.c:fork() cause static linking to fail if the app provides its own malloc()

2020-07-13 Thread Martin Husemann
On Tue, Jul 14, 2020 at 02:49:00AM +0200, Joerg Sonnenberger wrote: > Replacing malloc is just as invalid from a strict standard compliance > perspective, so *shrug* Why is that? We have e.g. shells/standalone-tcsh that does it. Is it broken now? Martin

Re: is this crash while coredumping to NFS known?

2020-07-09 Thread Martin Husemann
On Thu, Jul 09, 2020 at 06:03:23PM -0700, Greg A. Woods wrote: > The system is running my version of 9.99.64, so it's not quite current, > and thus I wanted to ask if anyone knows if this particular crash is > known of before I send-pr. > > I think this is the first time I've had a core dump over

Re: Automated report: NetBSD-current/i386 test failure

2020-06-19 Thread Martin Husemann
On Fri, Jun 19, 2020 at 08:56:32PM +0900, Rin Okuyama wrote: > I will make these tests (and similar ones in kernel/t_trapsignal) skipped on > QEMU, if there's no objection. No objections from me. Could you file a qemu bug for this, please? Thanks! Martin

Re: Automated report: NetBSD-current/i386 build failure

2020-06-21 Thread Martin Husemann
On Sun, Jun 21, 2020 at 12:00:41PM +0300, Andreas Gustafsson wrote: > Martin pointed me to this error some 63 lines from the end of the log: > > --- dependall-tests --- > nbmake[7]: nbmake[7]: don't know how to make t_cabsl.cc. Stop > > I think the reason I didn't find it myself is that I

Re: sysinst extended partitioning won't set/do the "newfs" flag!

2020-06-09 Thread Martin Husemann
On Mon, Jun 08, 2020 at 04:42:42PM -0700, Greg A. Woods wrote: > What magic am I missing, or is this a bug? A bug, probably related to not using MBR on xen devices (but most other x86 code expecting disklabel inside MBR). It worked (last I tested) in the default partition editor, not sure what

Re: ctfmerge stuck on CPU

2020-06-12 Thread Martin Husemann
On Fri, Jun 12, 2020 at 06:21:29PM +0100, Sad Clouds wrote: > I'm testing very recent -current on RPi4. Threaded programs are broken for aarch64 since ~1 week (most of the pthread tests fail, programs get stuck in jemalloc cleanup on thread exit). It is not clear what goes wrong exactly (or: why

Re: RAIDframe question

2020-06-14 Thread Martin Husemann
On Sat, Jun 13, 2020 at 09:44:35PM -0700, Greywolf wrote: > raidctl -a /dev/wd0c raid1 > > raidctl -F component0 raid1 I would have expected that to work. What is the raidctl status output after the -a ? Martin

Re: usb handling broken with -current

2020-07-30 Thread Martin Husemann
On Thu, Jul 30, 2020 at 10:55:05AM -0400, MLH wrote: > > > Jul 29 12:04:59 tiamat /netbsd: [ 96208.8263223] uhub3: autoconfiguration > > > error: device problem, disabling port 2 I see that every now and then on some machines/host controllers. It is not exactly reproducable (for me) though.

Re: acpi panic on Dell Optiplex 760 (i82Q45 chip set)

2020-11-29 Thread Martin Husemann
On Sun, Nov 29, 2020 at 06:23:40PM -0600, John D. Baker wrote: > On Sun, 29 Nov 2020 17:55:41 - (UTC), chris...@astron.com (Christos > Zoulas) wrote: > > > If you have netbsd.gdb and the crash file it should be simple... > > No crashdump as it boots -current via NFS. When next the machine

Re: MAKEDEV ptm devices and /dev/pts

2020-11-23 Thread Martin Husemann
On Sun, Nov 22, 2020 at 06:51:04PM -0700, Brook Milligan wrote: > - create an empty /dev/pts directory during installation as is done > for /dev/altq and /dev/fd. [..] > The first option seems simplest, but if the ptm* devices should > always be available and ptyfs is supposed to work in all

Re: atppc_acpi.c change breaks amd64 build

2020-12-10 Thread Martin Husemann
On Thu, Dec 10, 2020 at 06:59:13PM -0600, John D. Baker wrote: > Recently "atppc_acpi.c" was changed in this commit: > > https://mail-index.netbsd.org/source-changes/2020/12/07/msg124923.html > > The Log Message reads: > > Fix 32-bit build. > > but it seems to have broken 64-bit builds (at

Re: atppc_acpi.c change breaks amd64 build

2020-12-13 Thread Martin Husemann
On Sat, Dec 12, 2020 at 08:36:47PM -0600, John D. Baker wrote: > With sources of 202012121334Z, building kernels with "atppc at acpi" > still fail as originally reported (both amd64 and i386). Indeed - fixed for real, and now also added to the ALL kernel. Martin

Re: How to fall back to PIO for IDE CD's?

2020-11-18 Thread Martin Husemann
On Wed, Nov 18, 2020 at 09:10:17AM +0100, Julian Coleman wrote: > Hi, > > Most (all) sparc64 have problems with DMA and CD/DVD drives connected to > the internal controller (aceride). Can you elaborate on that part? I have cd0 at atapibus0 drive 0: cdrom removable in the SB2500 and something

Re: How to fall back to PIO for IDE CD's?

2020-11-18 Thread Martin Husemann
On Wed, Nov 18, 2020 at 10:09:10AM +0100, Julian Coleman wrote: > I see the same on the V240. If I try to read a DVD with mplayer on the > V240 or SPARCle in -9, I'll see "error reading" messages and it will fall > back to DMA then PIO and work. In current, I just see the error messages > and

Re: CVS Problem (again) ,Slightly lesser old code, but old still [was Re: Console problem ,older code]

2020-11-19 Thread Martin Husemann
On Wed, Nov 18, 2020 at 10:41:31PM -0800, Germain Le Chapelain wrote: > client_loop: send disconnect: Broken pipe > cvs [checkout aborted]: end of file from server (conslut above messages if > any) The second line refers to the ssh error in the first line, which is trying to tell you that

Re: CVS Problem (again) ,Slightly lesser old code, but old still [was Re: Console problem ,older code]

2020-11-19 Thread Martin Husemann
On Thu, Nov 19, 2020 at 01:59:28AM -0800, Germain Le Chapelain wrote: > But I wonder if: > > 1) I should use netbsd-9 > 2) Atheros works reliably, Both work very well for me, but: there are lots of atheros chip variants, and bugs often are only triggered by certain wlan AP actions (so I may be

Re: recent sysinst UX changes

2020-11-08 Thread Martin Husemann
On Sun, Nov 08, 2020 at 05:32:16PM +, nia wrote: > after several changes in 9.1 and -current, it's strange to me that the option > that I expect is the most popular for installing NetBSD (start over, fresh > partitions, use the whole disk) is no longer the default option: It never was and I

Re: recent sysinst UX changes

2020-11-09 Thread Martin Husemann
On Mon, Nov 09, 2020 at 10:10:56AM +, nia wrote: > fwiw, i think the default options should be as close to Just Work as possible. > > i have installed NetBSD irl with people who have only a little bit of unix > knowledge, and watched them wince every time something doesn't go as planned. >

Re: virtio scsi under VirtualBox

2020-11-21 Thread Martin Husemann
On Sat, Nov 21, 2020 at 02:44:35PM +, Chavdar Ivanov wrote: > Hi, > > I noticed the other day that he missing QUMRANET/VIRTIO PCI devices > have been added Only the PCI IDs, no support for them yet. Martin

Re: Automated report: NetBSD-current/i386 build failure

2020-10-30 Thread Martin Husemann
On Fri, Oct 30, 2020 at 03:02:16PM +0900, Rin Okuyama wrote: > On 2020/10/30 2:10, Rin Okuyama wrote: > > On 2020/10/30 1:58, nia wrote: > > > It should be fixed already. > > > > Please also try build for sun2, which does not support shlib; > > All programs linked to libsqlite3 need -lm

Re: Automated report: NetBSD-current/i386 build failure

2021-01-21 Thread Martin Husemann
On Thu, Jan 21, 2021 at 04:33:40PM +0100, Reinoud Zandijk wrote: > I'd like to fix this ASAP but what is the correct way of dealing with this? Is > this an i386 failure or should code just not use bus_space_read_8() or > bus_space_write_8() ? Unless the spec requires it, you should just avoid

Re: Automated report: NetBSD-current/i386 build failure

2021-01-25 Thread Martin Husemann
On Sun, Jan 24, 2021 at 12:10:46PM -0800, Jason Thorpe wrote: > > > On Jan 24, 2021, at 11:31 AM, Robert Elz wrote: > > > > /tmp/build/2021.01.24.17.44.16-i386/tools/lib/gcc/i486--netbsdelf/9.3.0/../../../../i486--netbsdelf/bin/ld: > >

Re: bmake inefficiencies

2021-01-31 Thread Martin Husemann
On Sun, Jan 31, 2021 at 12:41:47PM -0800, Simon J. Gerraty wrote: > David Holland wrote: > > "static volatile sig_atomic_t reap_children;" > > I chose int (which is what sig_atomic_t is) for portability. No, it is not int - several NetBSD architectures use long. Martin

Re: bmake inefficiencies

2021-01-31 Thread Martin Husemann
On Sun, Jan 31, 2021 at 10:52:03PM -0800, Simon J. Gerraty wrote: > > No, it is not int - several NetBSD architectures use long. > > Sorry, the one I checked as int, but I don't see that it should really > matter? int should be the type that any architecture deals with most > naturally. You

Re: Automated report: NetBSD-current/i386 build failure

2021-02-03 Thread Martin Husemann
On Wed, Feb 03, 2021 at 05:31:11PM +, Roy Marples wrote: > I cannot replicate this? > I'm just building a stock kernel - what extra options do I need? It happens in the userland build. Martin

Re: Entropy error blocks lang/python38 installation

2021-06-14 Thread Martin Husemann
On Mon, Jun 14, 2021 at 08:15:27AM +, Thomas Mueller wrote: > [ 386.3532035] entropy: pid 24617 (python) blocking due to lack of entropy This means your setup is incomplete. You need to seed entropy, e.g. by one of the methods in entropy(7) in the "Adding entropy" subsection. Python is

Re: Entropy error blocks lang/python38 installation

2021-06-15 Thread Martin Husemann
On Wed, Jun 16, 2021 at 03:42:35AM +, Thomas Mueller wrote: > I believe I must apply the fix/workaround every time. The entropy state gets stored on shutdown and reloaded on next boot. Fixing it once is enough. > Last time I looked at the releng wiki page, I noticed that there were > issues

Re: Entropy error blocks lang/python38 installation

2021-06-16 Thread Martin Husemann
On Wed, Jun 16, 2021 at 11:10:34AM +0200, Joerg Sonnenberger wrote: > On Wed, Jun 16, 2021 at 06:13:23AM +0200, Martin Husemann wrote: > > On Wed, Jun 16, 2021 at 03:42:35AM +, Thomas Mueller wrote: > > > I believe I must apply the fix/workaround every time. > > &g

Re: Build failures?

2021-06-23 Thread Martin Husemann
On Wed, Jun 23, 2021 at 03:11:23PM -0700, Paul Goyette wrote: > > Have you seen this in the officials builds? Yes, Brett was going to look at it (latest libcurses changes caused it). Martin

Re: Xen panics in autoconf

2021-06-15 Thread Martin Husemann
On Tue, Jun 15, 2021 at 09:17:17AM +0200, Manuel Bouyer wrote: > Hello, > some recent changes broke Xen: > [ 2.919] panic: kernel diagnostic assertion "KERNEL_LOCKED_P()" failed: > file "/usr/src/sys/kern/subr_autoconf.c", line 1039 > [ 2.919] cpu0: Begin traceback... > [

Re: Entropy error blocks lang/python38 installation

2021-06-15 Thread Martin Husemann
On Tue, Jun 15, 2021 at 09:24:01AM +, Thomas Mueller wrote: > This entropy thing seems crazy to me It is! But it also is: - a one time only thing (supposed to happen when you set the machine up for the first time) - a current only issue - only affecting some machines - a blocker for

Re: Build failures?

2021-06-24 Thread Martin Husemann
On Thu, Jun 24, 2021 at 03:49:15PM +0930, Brett Lymn wrote: > On Thu, Jun 24, 2021 at 12:23:26AM +0200, Martin Husemann wrote: > > > > Yes, Brett was going to look at it (latest libcurses changes caused it). > > > > Hopefully it is fixed now. The current autobu

Re: 9.99.86 system lockup opening Firefox's about:support page

2021-07-02 Thread Martin Husemann
On Sat, Jul 03, 2021 at 12:55:33AM +, RVP wrote: > Anybody else have this issue? Not this specific one, but test runs still do not complete with -current for me (both evbarm and macppc locked up [differently to the deadlock before]). Will investigate and provide more details later. Martin

Re: 9.99.86 HEAD

2021-07-03 Thread Martin Husemann
On Sat, Jul 03, 2021 at 10:36:07AM +0100, Chavdar Ivanov wrote: > At least I found out what causes it - I ran /etc/daily and it promptly > crashed the same way eventually. I'll repeat it on the console to try > to see if something else shows when it happens. Can you show all your mounts? Martin

Re: 9.99.86 HEAD

2021-06-30 Thread Martin Husemann
On Wed, Jun 30, 2021 at 03:49:52PM +0200, Martin Husemann wrote: > On Wed, Jun 30, 2021 at 02:23:23PM +0100, Patrick Welche wrote: > > The one bug I see is that running cgdconfig causes a panic > > > > --- trap (number 6) --- > > vn_open() at vn_open+0x31d

Re: 9.99.86 HEAD

2021-07-01 Thread Martin Husemann
On Thu, Jul 01, 2021 at 10:54:45AM +0300, Andreas Gustafsson wrote: > Martin Husemann wrote: > > Hmm, that is the last commit I needed to get everything working again > > here - any idea what exactly hangs and where? > > The same way it has been hanging ever si

Re: 9.99.86 HEAD

2021-07-01 Thread Martin Husemann
On Thu, Jul 01, 2021 at 09:56:03AM +0300, Andreas Gustafsson wrote: > Martin Husemann wrote: > > All regressions I am aware of have been fixed now. > > At least i386 still hangs while running the ATF tests as of source > date 2021.07.01.04.25.51. Hmm, that is the last comm

Re: 9.99.86 HEAD

2021-07-01 Thread Martin Husemann
Here is show locks and ps output while the test hangs Martin db{0}> show locks [Locks tracked through LWPs] ** LWP 1856.1856 (rxvt) @ 0x1372f100, l_stat=3 *** Locks held: none *** Locks wanted: * Lock 0 (initialized at fstrans_init) lock address : 0x00c0f2c0 type :

Re: 9.99.86 HEAD

2021-07-01 Thread Martin Husemann
Same output again, augmented with stack traces. Martin db{0}> show locks [Locks tracked through LWPs] ** LWP 1856.1856 (rxvt) @ 0x1372f100, l_stat=3 *** Locks held: none *** Locks wanted: * Lock 0 (initialized at fstrans_init) lock address : 0x00c0f2c0 type :

Re: 9.99.86 HEAD

2021-06-30 Thread Martin Husemann
On Wed, Jun 30, 2021 at 02:23:23PM +0100, Patrick Welche wrote: > The one bug I see is that running cgdconfig causes a panic > > --- trap (number 6) --- > vn_open() at vn_open+0x31d That one is fixed now, but there is still serious fallout. Martin

Anyone feel like fixing pkgsrc/emulators/tme ?

2021-07-10 Thread Martin Husemann
The emulators/tme pkg is a nice, lightweight pkg allowing you to run various sun machines on amd64 (and others). I recently needed it for testing some openssl fallout in netbsd-9 (where qemu seems to only emulate machines for which it works and that I also have as real hardware). Unfortunately

Re: requires a working dlopen()

2021-07-10 Thread Martin Husemann
On Sat, Jul 10, 2021 at 09:00:37AM +, dashdruid wrote: > Also LEX was not present in /usr/bin so I have installed flex and > linked the flex binary to lex, idk if its a problem. Assuming you actually mean /usr/bin/lex then this tells you that something went wrong during installation of your

Re: Anyone feel like fixing pkgsrc/emulators/tme ?

2021-07-10 Thread Martin Husemann
On Sat, Jul 10, 2021 at 03:46:46PM +0200, Rhialto wrote: > On Sat 10 Jul 2021 at 15:41:27 +0200, Martin Husemann wrote: > > On Sat, Jul 10, 2021 at 03:39:10PM +0200, Rhialto wrote: > > > How far did you get? I tried sun3, and I got to booting the ramdisk > > Oh this

Re: Anyone feel like fixing pkgsrc/emulators/tme ?

2021-07-10 Thread Martin Husemann
On Sat, Jul 10, 2021 at 03:48:35PM +0200, Martin Husemann wrote: > On Sat, Jul 10, 2021 at 03:46:46PM +0200, Rhialto wrote: > > On Sat 10 Jul 2021 at 15:41:27 +0200, Martin Husemann wrote: > > > On Sat, Jul 10, 2021 at 03:39:10PM +0200, Rhialto wrote: > > > > How

Re: Anyone feel like fixing pkgsrc/emulators/tme ?

2021-07-10 Thread Martin Husemann
On Sat, Jul 10, 2021 at 03:39:10PM +0200, Rhialto wrote: > How far did you get? I tried sun3, and I got to booting the ramdisk > kernel from tape. But when I did the "dd bs=32k if=/dev/nrst0 > of=/dev/rsd0b" I got a core dump. Possibly I had not used edlabel > correctly due to it not getting a

Re: 9.99.86 HEAD

2021-07-01 Thread Martin Husemann
I did not trust macppc / lockdebug so reproduced it on evbarm. Unfortunately nearly identical (not making any sense to me) output again... Martin db> show locks [Locks tracked through LWPs] ** LWP 1370.1370 (umount) @ 0xc488b180, l_stat=3 db> bt/a 0xc488b180 trace: pid 1370 lid 1370 at

Re: posix_spawn issue?

2021-05-01 Thread Martin Husemann
On Sat, May 01, 2021 at 02:50:02PM +0200, Jaromír Dole?ek wrote: > Well, there is one obvious difference - gmake uses > POSIX_SPAWN_USEVFORK - glibc supports it, we don't. Well, it does not use it on NetBSD (and it makes no sense to support here). And that flag is not allowed to change any

Re: posix_spawn issue?

2021-05-01 Thread Martin Husemann
On Sat, May 01, 2021 at 11:02:26AM +0200, Thomas Klausner wrote: > gmake since version 4.3 uses posix_spawn(), but that breaks the build > of firefox (and libreoffice). Disabling posix_spawn() support in gmake > works around this problem.[1] > > Is there a bug/incompatibility in our posix_spawn()

Re: posix_spawn issue?

2021-05-01 Thread Martin Husemann
On Sat, May 01, 2021 at 01:13:43PM +0200, Thomas Klausner wrote: > The whole file is here: > > https://git.savannah.gnu.org/cgit/make.git/tree/src/job.c But since it mostly works (and only fails in some environments) there must be something special ongoing, and we will have to find out what that

Re: posix_spawn issue?

2021-05-02 Thread Martin Husemann
On Sun, May 02, 2021 at 03:33:32PM +0900, Ryo ONODERA wrote: > Hi, > > I have uploaded simple test Makefiles: > https://www.netbsd.org/~ryoon/gmake-tests-20210502.tar.gz > > It is as follows: > > $ cat Makefile > all: > ${MAKE} -C test-a > > clean: > ${MAKE} -C test-a clean >

<    1   2   3   4   5   6   7   >