From nemesis!uhclem  Wed Jan  8 22:52:25 1997
Received: from nemesis.lonestar.org (fw4-19.ppp.iadfw.net [206.66.15.148])
          by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id WAA11809
          for <FreeBSD-gnats-submit>; Wed, 8 Jan 1997 22:52:17 -0800 (PST)
Received: by nemesis.lonestar.org (Smail3.1.27.1 #22)
	id m0vi8f0-000uBXC; Wed, 8 Jan 97 18:47 CST
Message-Id: <m0vi8f0-000uBXC@nemesis.lonestar.org>
Date: Wed, 8 Jan 97 18:47 CST
From: uhclem@nemesis.lonestar.org
Reply-To: uhclem
To: FreeBSD-gnats-submit@freebsd.org
Cc: uhclem@nemesis.lonestar.org
Subject: At end of install, panic: Going nowhere without init - FDIV050
X-Send-Pr-Version: 3.2

>Number:         2426
>Category:       conf
>Synopsis:       At end of install, panic: Going nowhere without init - FDIV050
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Jan  8 23:00:01 PST 1997
>Closed-Date:    Sat May 30 17:53:33 PDT 1998
>Last-Modified:  Sat May 30 17:55:30 PDT 1998
>Originator:     Frank Durda IV
>Release:        FreeBSD 2.2-BETA
>Organization:
>Environment:

486DX 66MHz, 12Meg of RAM, 1.2GB IDE hard drive, three mounted partitions
	/ (85MB), /var (12MB), /usr (900MB), 32MB for swap.
WD/SMC 8013 (ed0) ethernet adapter, at either
	0x09 0x280 0xd4000
or	0x05 0x280 0xd8000 (default)	(fails both ways)
or 3Com 3c503 at 0x05 0x280 0xd8000     (fails with this card too)
Boot from boot.flp  -c, change ed0 irq 9 iomem 0xd4000.
OR Boot from boot.flp and make no config changes.

Newfs all partitions.
Select Developer with DES
OR Select Minimal install (fails both ways)
FTP from local system  165.164.6.15/h/freebsd
specify systemname "skaro.lonestar.org", no gateway, no DNS,
IP 165.164.6.19	mask 255.255.0.0 no options
(FYI, specifying a gateway and DNS does not fix the problem)

>Description:

After optionally overriding the memory and IRQ settings, I selected
Developer install and DES or just minimal install.  Download from specified
FTP site appeared to go without incident.  Finally the screen says:

	Information Dialog
	Saving any boot -c changes to new kernel...
	panic: Going nowhere without init!

	syncing disks... 93 93 92 85 78 66 52 26 6 done

	Rebooting in ten seconds...  

I stopped the reboot by pressing a key.  (It is a pity that selecting
another screen after aborting the reboot counts as a "proceed-to-reboot"
command.  It would be nice to allow that if possible for faster debugging.
But I digress.)

Rebooted, selected same options, re-newfs'ed the partitions and received
the same error at the same point.  On the third thru fifth attempts,
I changed the EEPROM settings on the network card so that there would
be no kernel configuration changes to save, thinking that would help
or skip the part of the code that was having problems.  It did not help.
I also started asking for minimal install to speed the failures up.
So the choice of installation package doesn't seem to matter.

However, I left the system on screen F2 during these installs and received:

	sysinstall in free(); chunk is already free
	init died signal 0, exit 1

After a few seconds the system reboots.  Attempting to go to screen F1
with one keystroke combination (ALT+F1) causes continuous beep and system
eventually reboots anyway.


This system had installed 2.2-ALPHA (and did a complete 'make world') with
no incidents with exactly the same hardware and boards installed. 
2.2-ALPHA was installed using the same FTP method via the SMC card.

I did not try installing 2.1.6 or 2.1.6.1 on the system so I don't
know about those behave on this platform.  Before 2.2-ALPHA, the system
had 2.1.5 running without incident and installed via FTP too.


On the 6th 2.2-BETA attempt, I removed the system cache and the problem
did not go away.

On the 7th attempt, I left cache out and replaced network card with
a 3C503 (I was unable to get another type 3Com card to be detected),
which still uses the ed0 driver.  The install failed in the same way.

On the 8th attempt, I had a cable unplugged, so the commit aborted.
After fixing the cable, I simply did an extract.  It went to completion
without error.  I then issued a Commit again (it wanted me to redeclare
the distribution) and then the panic occurred without doing any of
the FTPs.

The 2.2-BETA modules were downloaded around 2-Jan-97 from www.freebsd.org
and appear to be complete/correct.

Again, installing 2.2-ALPHA on this system (with cache and the SMC
network card present) works fine.

>How-To-Repeat:

See above.

>Fix:

I have not been able to find a workaround.


>Release-Note:
>Audit-Trail:

From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
To: uhclem@freefall.freebsd.org
Cc: FreeBSD-gnats-submit@freebsd.org, uhclem@nemesis.lonestar.org
Subject: Re: conf/2426: At end of install, panic: Going nowhere without init - FDIV050 
Date: Thu, 09 Jan 1997 01:43:11 -0800

 Yikes!  All this sounds bad.  Rest assured that I *will* fix these
 problems (to your proven satisfaction) before 2.2 goes out. :-)

From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
To: uhclem@freefall.freebsd.org
Cc: FreeBSD-gnats-submit@freebsd.org, uhclem@nemesis.lonestar.org
Subject: Re: conf/2426: At end of install, panic: Going nowhere without init - FDIV050 
Date: Tue, 14 Jan 1997 23:21:01 -0800

 > 	Information Dialog
 > 	Saving any boot -c changes to new kernel...
 > 	panic: Going nowhere without init!
 
 This may have been due to an error in the SaveUserconfig() code which
 somehow gets confused by certain SCSI configurations.  Since we don't
 save that information here anyway, this was recently disabled in
 sysconfig.  Can you try the 3.0-970114-SNAP floppies/newer/boot.flp
 image and see if this still occurs?  Thanks!

From: uhclem@nemesis.lonestar.org (Frank Durda IV)
To: jkh@time.cdrom.com, FreeBSD-gnats-submit@freebsd.org
Cc: uhclem@nemesis.lonestar.org
Subject: Re: conf/2426: At end of install, panic: Going nowhere without init - FDIV050 
Date: Thu, 16 Jan 97 00:29 CST

 uhclem wrote in conf/2426:
 [0]	Information Dialog
 [0]	Saving any boot -c changes to new kernel...
 [0]	panic: Going nowhere without init!
 
 jkh writes:
 [1]This may have been due to an error in the SaveUserconfig() code which
 [1]somehow gets confused by certain SCSI configurations.  Since we don't
 [1]save that information here anyway, this was recently disabled in
 [1]sysconfig.  Can you try the 3.0-970114-SNAP floppies/newer/boot.flp
 [1]image and see if this still occurs?  Thanks!
 
 FYI, systems I ran into the problem on did not have any SCSI adapters or
 devices.
 
 However, I tried both the floppies/boot.flp and the floppies/newer/boot.flp
 from the 3.0 SNAP.
 
 FYI, floppies/boot.flp failed attempting to FTP the file "bin/bin.tgz",
 but in changing to a different FTP site for a retry, the "going nowhere"
 panic message occurred after selecting FTP Passive in error and then
 selecting Cancel in the next menu, so the bug still exists in some
 form here.  
 
 The newer/floppies/boot.flp successfully installed the minimal 
 2.2-BETA tree (via a symlinked to 3.0-970114-SNAP on the local FTP
 system), without producing this particular error message.  The
 system was configured back with the SMC 8013 network adapter for
 this test.  I'll try doing the developer distribution install of
 2.2-BETA next.
 
 Despite the fix mentioned being targeted at SCSI issues, it seems to
 correct the problem on non-SCSI platforms as well.  But this makes me
 think the true cause of the problem is not well-understood at this
 time.
 
 Thanks!
 
 Frank Durda IV <uhclem@nemesis.lonestar.org>|"The Knights who say "LETNi"
 or uhclem%nemesis@rwsystr.nkn.net           | demand...  A SEGMENT REGISTER!!!"
 					    |"A what?"
 or ...letni!rwsys!nemesis!uhclem	    |"LETNi! LETNi! LETNi!"  - 1983
 

From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
To: uhclem@nemesis.lonestar.org (Frank Durda IV)
Cc: FreeBSD-gnats-submit@freebsd.org
Subject: Re: conf/2426: At end of install, panic: Going nowhere without init - FDIV050 
Date: Wed, 15 Jan 1997 23:18:06 -0800

 > The newer/floppies/boot.flp successfully installed the minimal 
 > 2.2-BETA tree (via a symlinked to 3.0-970114-SNAP on the local FTP
 > system), without producing this particular error message.  The
 
 I found and fixed a number of sysinstall bogons after the SNAP went
 out, which is why I dumped (and will continue to dump) new versions of
 the boot floppies into the floppies/newer/ directory for awhile.  I've
 got this handy chroot environment built up for rolling new boot floppy
 updates to 3.0-970114-SNAP, so I'm going to get some more testing
 mileage out of it before tearing it down and going back to 2.2-GAMMA
 testing.  I'll probably roll at least one more set of boot floppies
 before I do that - I don't think I have all the outstanding PRs closed
 yet.
 
 If you can also test various failure conditions, like misspelled paths
 or bogus host names for FTP and NFS, that would be good - I tried to
 code more defensively for those cases in the last rev of the floppies.
 
 					Jordan
State-Changed-From-To: open->closed 
State-Changed-By: steve 
State-Changed-When: Sat May 30 17:53:33 PDT 1998 
State-Changed-Why:  
I'm assuming that Jordan fixed all of the problems that you 
mentioned.  If not and you're still listening Frank (numerous 
attempts at three different email addresses all bomb), please 
give us a jingle.  Thanks. 
>Unformatted:
