From nobody@FreeBSD.ORG  Sun Jan 16 04:37:24 2000
Return-Path: <nobody@FreeBSD.ORG>
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id D7CD014C19; Sun, 16 Jan 2000 04:37:23 -0800 (PST)
Message-Id: <20000116123723.D7CD014C19@hub.freebsd.org>
Date: Sun, 16 Jan 2000 04:37:23 -0800 (PST)
From: paul@iaehv.nl
Sender: nobody@FreeBSD.ORG
To: freebsd-gnats-submit@FreeBSD.org
Subject: FreeBSd 3.4. /stand/sysinstall cores when accessing 'distributions' menu
X-Send-Pr-Version: www-1.0

>Number:         16144
>Category:       i386
>Synopsis:       FreeBSd 3.4. /stand/sysinstall cores when accessing 'distributions' menu
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    jkh
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Jan 16 04:40:01 PST 2000
>Closed-Date:    Fri Feb 18 10:22:34 PST 2000
>Last-Modified:  Fri Feb 18 10:23:09 PST 2000
>Originator:     Paul Kolenbrander
>Release:        FreeBSD 3.4
>Organization:
PKS Computer Problems
>Environment:
FreeBSD dax.pks.fdns.net 3.4-RELEASE FreeBSD 3.4-RELEASE #4: Sun Jan 16 03:10:39
 CET 2000     root@dax.pks.fdns.net:/usr/src/sys/compile/DAXKERNEL  i386
>Description:
I've encountered a weird problem in updating the below system from 
FreeBSD 3.1 to FreeBSD 3.4. After the upgrade /stand/sysinstall cores 
when I access the 'dictributions' menu. Figuring the upgrade went awry, I 
completely wiped the hd's and installed 3.4 afresh. Same problem. So I 
wiped it again and installed 3.3 instead. Again the same problem. So I 
ended up reinstalling 3.1 on a clean system. /stand/sysinstall works 
fine. Does anybody have any idea what may be causing this? As it prevents 
me fromn getting at, amongst others, the kernel sources. :-( Have there 
been changes in /stand/sysinstall or one of it's components since 3.1 
that may be causing this?

Output of 'strings sysinstal.core | more' produced the following interesting
line: 'erflow pages.  Increase page size'

Note: I installed another system from the same 3.3/3.4 CD's and there /stand/sysinstall
runs fine. System specs for that system are available on http://pks.fdns.net/

System Specifications
---------------------
Motherboard: Intel TC430HX with onboard Yamaha sound and 2Mb S3 VIRGE
                    Phoenix BIOS, 1.00.07.DH0 (last available BIOS)
CPU            : CPU: 133Mhz Pentium/P54C (132.96-MHz 586-class CPU)
                    Origin = "GenuineIntel"  Id = 0x52c  Stepping = 12
                    Features=0x1bf<FPU,VME,DE,PSE,TSC,MSR,MCE,CX8>
Memory     : 64MB, 2 x 32M  EDO DIMM
Ethernet     : Generic PCI (Realtek based) NE-2000 clone 
             ( I use it in my other FBSD 3.3 system without problems. 
Video      : S3 Virge 2MB
             vga0: <S3 ViRGE graphics accelerator> 
             rev 0x06 int a irq 11 on pci0.8.0
keyboard   : Standard 104 keys
Mouse      : PS/2 Mousepad (swapped with mouse, no change)
             psm0 irq 12 on isa
             psm0: model Generic PS/2 mouse, device ID 0
Drives     : Standard floppy
             wdc0: unit 0 (wd0): <NEC Corporation DSE2010A> [MASTER]
             wd0: 1919MB (3931200 sectors)
             wdc1: unit 0 (wd2): <Seagate ST3660A>
             wd2: 520MB (1065456 sectors) [MASTER]
             wdc1: unit 1 (atapi): <HITACHI CDR-8130/0021>, [SLAVE]
             removable, accel, dma, iordy
>How-To-Repeat:
On my system, run /stand/sysinstall and click on the 'distributions' menu item.
>Fix:


>Release-Note:
>Audit-Trail:

From: "S.W. Drinkard" <sam@wa4phy.dyndns.org>
To: freebsd-gnats-submit@FreeBSD.org, paul@iaehv.nl
Cc:  
Subject: Re: i386/16144: FreeBSd 3.4. /stand/sysinstall cores when accessing 
 'distributions' menu
Date: Wed, 19 Jan 2000 17:08:59 -0500

 Exactly the same behaviour I found from the ftp'd kern & mfsroot
 floppies.  I forgot to get the compat2 bits, so went back in after a
 reboot and discovered the same problem, exactly.  Very repeatable.  Can
 not add additional distributions.
 
 Also entering sysinstall after coming up 2nd time,  got complaints about
 not being able to resolve ftp.freebsd.org server.  I KNOW it have
 networking right, because it's my current configuration.  Failing
 apparently on hostlookup, or gethostbyname.
 
 Sam
 
 
 

From: Francois Berjon <berjon@bcv01y01.vz.cit.alcatel.fr>
To: freebsd-gnats-submit@FreeBSD.org, paul@iaehv.nl
Cc:  
Subject: Re: i386/16144: FreeBSd 3.4. /stand/sysinstall cores when accessing 
 'distributions' menu
Date: Tue, 08 Feb 2000 17:28:20 +0100

 Basically the same problem for me: selecting "custom distributions" in
 the
 distributions menu yields an instant segfault every time.
 
 Context: 'Custom' installation of 3.4-RELEASE, system booted from 3.4 
          kern/mfsroot floppies.
 
 I had no problems getting into the top-level 'Distributions' menu.
 Selecting
 one of the canned sets (in particular X-kern-developer) works OK. But
 selecting
 the "Custom distributions" options produces and instant and systematic
 segfault.
 I could not get a core or analysis as the machine of course immediately
 reboots.
 
 There does not seem to be an extremely specific chain of events leading
 to
 this situation: segfault is immediate upon selecting the "custom
 distributions" 
 option, irrespective of the operations performed before.
 
 That bug is non-fatal in the sense that it is still possible to install
 a 3.4 machine with one of the canned filesets, but this makes a custom
 installation
 impossible. Makes it pretty serious, IMHO :-)
 
 Francois.
 

From: Ruslan Ermilov <ru@ucb.crimea.ua>
To: Francois Berjon <berjon@bcv01y01.vz.cit.alcatel.fr>
Cc: freebsd-gnats-submit@freebsd.org
Subject: Re: i386/16144: FreeBSd 3.4. /stand/sysinstall cores when accessing 'distributions' menu
Date: Wed, 9 Feb 2000 00:30:59 +0200

 Please listen to what /etc/motd says to you,
 then go and read the errata for 3.4-RELEASE:
 
 http://www.freebsd.org/releases/3.4R/errata.html
 
 On Tue, Feb 08, 2000 at 08:30:04AM -0800, Francois Berjon wrote:
 > The following reply was made to PR i386/16144; it has been noted by GNATS.
 > 
 > From: Francois Berjon <berjon@bcv01y01.vz.cit.alcatel.fr>
 > To: freebsd-gnats-submit@FreeBSD.org, paul@iaehv.nl
 > Cc:  
 > Subject: Re: i386/16144: FreeBSd 3.4. /stand/sysinstall cores when accessing 
 >  'distributions' menu
 > Date: Tue, 08 Feb 2000 17:28:20 +0100
 > 
 >  Basically the same problem for me: selecting "custom distributions" in
 >  the
 >  distributions menu yields an instant segfault every time.
 >  
 >  Context: 'Custom' installation of 3.4-RELEASE, system booted from 3.4 
 >           kern/mfsroot floppies.
 >  
 >  I had no problems getting into the top-level 'Distributions' menu.
 >  Selecting
 >  one of the canned sets (in particular X-kern-developer) works OK. But
 >  selecting
 >  the "Custom distributions" options produces and instant and systematic
 >  segfault.
 >  I could not get a core or analysis as the machine of course immediately
 >  reboots.
 >  
 >  There does not seem to be an extremely specific chain of events leading
 >  to
 >  this situation: segfault is immediate upon selecting the "custom
 >  distributions" 
 >  option, irrespective of the operations performed before.
 >  
 >  That bug is non-fatal in the sense that it is still possible to install
 >  a 3.4 machine with one of the canned filesets, but this makes a custom
 >  installation
 >  impossible. Makes it pretty serious, IMHO :-)
 >  
 >  Francois.
 >  
 > 
 > 
 > To Unsubscribe: send mail to majordomo@FreeBSD.org
 > with "unsubscribe freebsd-bugs" in the body of the message
 
 -- 
 Ruslan Ermilov		Sysadmin and DBA of the
 ru@ucb.crimea.ua	United Commercial Bank,
 ru@FreeBSD.org		FreeBSD committer,
 +380.652.247.647	Simferopol, Ukraine
 
 http://www.FreeBSD.org	The Power To Serve
 http://www.oracle.com	Enabling The Information Age
 
Responsible-Changed-From-To: freebsd-bugs->jkh 
Responsible-Changed-By: ru 
Responsible-Changed-When: Fri Feb 18 04:38:36 PST 2000 
Responsible-Changed-Why:  
Make what Jordan should have done. 
State-Changed-From-To: open->closed 
State-Changed-By: jkh 
State-Changed-When: Fri Feb 18 10:22:34 PST 2000 
State-Changed-Why:  
This is already documented in the 3.4 release ERRATA.  ALWAYS read 
the ERRATA for your release before reporting a bug! 
>Unformatted:
