NetBSD Problem Report #57295

From  Sat Mar 25 07:56:45 2023
Return-Path: <>
Received: from ( [])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits))
	(Client CN "", Issuer " CA" (not verified))
	by (Postfix) with ESMTPS id C335E1A923C
	for <>; Sat, 25 Mar 2023 07:56:45 +0000 (UTC)
Message-Id: <>
Date: Sat, 25 Mar 2023 07:56:44 +0000 (UTC)
Subject: sysinst segmentation fault
X-Send-Pr-Version: www-1.0

>Number:         57295
>Category:       port-hpcmips
>Synopsis:       sysinst segmentation fault
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    port-hpcmips-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Mar 25 08:00:01 +0000 2023
>Originator:     b9
>Release:        9.3
Unsure as NetBSD isn't installed yet on this NEC Mobile Pro 800.
Booted from Windows CE to NetBSD-9.3 using hpcboot.exe. Sysinst seemed to work and gave me a menu. However, network configuration failed, so I went to "e: Utility menu" and then "a: Run /bin/sh", and got some strange error messages:

uid 0, pid 6, command sysinst, on /: file system full
/: write failed, file system is full 
pid 6 (sysinst): user write of 4136@0x7dd00000 at 161428 failed: 28
[1] Segmentation fault     sysinst

After that, it did give me a root prompt ('#'), so I tried `df -a` to see what was going on and it gave me another error:

sh: Cannot set process group (Operation not permitted) at 225

df reported that / was mounted on a 4MB memory disk (md0a), so it is not too surprising it filled up. I understand that these hpcmips machines often have a very small amount of RAM, but if the memory disk is so small that it is causing problems, perhaps the size should be increased slightly, perhaps to 6 or 8MB.
I tried a second time and discovered that there is a tiny amount of space available (~200 KB) on the memory disk. The problem is likely was possibly that I had started up sysinst and walked away for several hours. Another issue is that many programs want to dump core by default which is not a good idea when there is so little free space. 

For example, the `ping` command always dumps core when I exit it by hitting ^C (Ctrl + C). It says:

Floating point exception (core dumped)   ping

This implies to me that likely this version of ping was not compiled with the right flags. This VR4121 machine does not have floating point arithmetic on the CPU; when it hits an FPU instruction, it is supposed to cause a fault which allows the floating point operation to be processed in the kernel. 
Not yet known. Is there a way to limit the coredump size based on how much freespace is available? 

Also, I notice that when I first had the issue, I had walked away for hours with the Sysinst Menu on the screen before interacting with it. Is it possible there's a leak somewhere?

NetBSD Home
NetBSD PR Database Search

(Contact us) $NetBSD: query-full-pr,v 1.47 2022/09/11 19:34:41 kim Exp $
$NetBSD:,v 1.9 2014/08/02 14:16:04 spz Exp $
Copyright © 1994-2023 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.