*BSD News Article 25379


Return to BSD News archive

Newsgroups: comp.os.386bsd.bugs
Path: sserve!newshost.anu.edu.au!munnari.oz.au!sgiblab!swrinde!cs.utexas.edu!uunet!ihz.compuserve.com!mfoley
From: mfoley@csi.compuserve.com (M Foley)
Subject: PROBLEMS WITH FreeBSD
Message-ID: <CIq8w7.7rM@csi.compuserve.com>
Organization: CompuServe Incorporated
Date: Tue, 28 Dec 1993 04:09:42 GMT
Lines: 192

Reply-To: 73311.622@compuserve.com

Note - Please reply to the above address, otherwise I will not receive
the response.

The following are some of the misc. problems I have experienced
installing FreeBSD 1.0e. If anyone has advice or insight, I would
appreciate a mail message as I no long have ready access to these news
groups.

1. I installed the system OK, however when I tried to select different
   defaults for the fs fragment size [512], and swap space [40 verses 75 -
   I used the formula in the install instructions], the system would 
   always panic and halt. When I took all the defaults, it installed OK. 
   Any ideas on why the panic?
   
2. Why do I have to have a limit on the root file system size? I took the
   default which, I believe, turned out to be ~14M. I would have
   preferred the entire disk as a single file system. This *feature* has
   caused some minor reconfiguration problems. Also, this configuration
   does not allow enough root file system space for the /var/crash files.

3. I modified the kernel as shown in the attached config file. This was to
   get the correct timezone, get the proper irq for my ethernet card, and
   remove some devices I am not using. This worked OK - except, I got a
   "panic: lock_set_recursive: don't have write lock" when doing the make
   depend the 1st time. Why?

4. I cannot use the sio devices. I tried, but could not log in to my tty01.  
   I reran 'MAKEDEV sio0 sio1 sio2 sio3' - didn't help.  The ttys and 
   gettytab files are vanilla - I haven't touched them since the system 
   install (except that I commented out tty00 - the mouse).  When I tried 
   to cat something to tty01 logged in as root - I was dead.  It never came 
   back.  I couldn't ^C out.  I had to reset the system.

   Same problem with tty02 (modem). When I used kermit to access, after I
   did "set line /dev/tty02", kermit didn't respond back. When I ^C'd, I
   got the kermit prompt and was then able to "connect" and talk to the modem.

   I worked around the problem by removing /dev/tty0* and doing
   "MAKEDEV com0 com1 com2 com3" and rebuilt my kernel using the com
   devices instead of the sio devices. Works fine. What's the problem???
   
5. Before I had the ed0 device configured for my SMC Elite card's irq and
   port (i.e. using the original kernel), the probe function (guess) 
   seemed to modify my card's nvrom irq address. I had it set to 10. After
   booting with my new kernel it probed to 2 and once to 9. I had to boot
   DOS and run a setup program to get it back to 10. This happens each
   time I boot from the generic kernel.
   
6. When compiling bash, and about 20 times when making a new kernel, the
   make stopped with:
   
   cc: Internal compiler error: program gcc1 got fatal signal 11
   
   Restarting the make would resume at the right place and continue for
   a few more programs before stopping again. Finally, I disengaged turbo 
   mode (front panel switch), and the kernel make seemed to proceed without 
   problems. I have had a number of flakey problems like this (see next item)
   which seem to have gone away without turbo. I hope this is not a 
   permanent problem since I am now running as a 386/16 rather than a 386/25. 
   Why?
   
7. When doing a "zcat | cpio -o" operation, the system paniced, dumped and
   rebooted. Upon reboot I got through the file system checks and then:
   
   :
Checking for core dump
vm_fault (fe32a900, 1ab2000,1,0) -> 1
  type c, code fe010000
trap type 12 code=fe010000 eip = fe01aff2 cs=8 eflags = 10282 cr2 1ab2ea6 cpl 0
panic: trap
Syncing disks ...

   At this point the system was hung. I had to reset. I was about to give
   up and reinstall 386bsd when I decided to try taking off the turbo
   switch again. That worked. I was also able to complete the cpio 
   operation.

   I have been running 386bsd with successive patchkits since last April
   (at least). I have *always* left the turbo switch on - never had this
   problem. Like I say, I'd much rather run a 386/25.

Any insight/help would be greatly appreciated. Please reply to 
73311.622@compuserve.com) as I do not have access to Internet news. Although,
answers to these problems might be worth posting for others.

My configuration is:

386-25 cpu
387 math processor
8MB memory
IDE ST3550A 453MB Segate hard drive (wd0)
IDE CP3204F 200MB Conner hard drive (wd1)
A: - 3 1/2" floppy
B: - 5 1/4" floppy
SMC Elite 16 Ethernet card which probes as WD8013EPC (ed0)
1 - normal (non-buffered) serial port, used for mouse (com0)
1 - 16550A port, used for terminal connection (com1)
1 - 16550A port, on 14400 modem card, also used for login (com2)

I also have a DOS partition which is mounted under /dos as a pcfs

========================== /sys/i386/conf/FOLEY ==========================
#
# GENERICAH -- Generic machine with WD/AHx family disks
#
#	$Id: GENERICAH,v 1.16 1993/10/19 01:28:07 rgrimes Exp $
#

machine		"i386"
cpu		"I386_CPU"
#cpu		"I486_CPU"
ident		FOLEY
timezone	5 dst
maxusers	10
maxfdescs	2048			#Max file descriptors per process
#options		MATH_EMULATE		#Support for x87 emulation
options		INET			#InterNETworking
options		ISOFS			#ISO File System
options		NFS			#Network File System
options		PCFS			#MSDOS File System
options		"COMPAT_43"		#Compatible with BSD 4.3
options		"TCP_COMPAT_42"		#TCP/IP compatible with 4.2
options		XSERVER			#Xserver
options		UCONSOLE		#X Console support
#options	GATEWAY			#Host is a Gateway (forwards packets)

config		"386bsd"	root on wd0 swap on wd0 and sd0

controller	isa0

controller	fd0	at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr
disk		fd0	at fd0 drive 0
disk		fd1	at fd0 drive 1

controller	wd0	at isa? port "IO_WD1" bio irq 14 vector wdintr
disk		wd0	at wd0 drive 0
disk		wd1	at wd0 drive 1

#controller	ahb0	at isa? bio irq 11 vector ahbintr
#controller	aha0	at isa? port "IO_AHA0" bio irq 11 drq 5 vector ahaintr
#controller	scbus0

#device		sd0
#device		sd1
#device		sd2
#device		sd3

#device		st0
#device		st1

#device		cd0	#Only need one of these, the code dynamically grows

#device		wt0	at isa? port 0x300 bio irq 5 drq 1 vector wtintr
#device		mcd0	at isa? port 0x300 bio irq 10 vector mcdintr

device		pc0	at isa? port "IO_KBD" tty irq 1 vector pcrint
device		npx0	at isa? port "IO_NPX" irq 13 vector npxintr

#The old drivers are rarely needed anymore...
device		com0	at isa? port "IO_COM1" tty irq 4 vector comintr
device		com1	at isa? port "IO_COM2" tty irq 3 vector comintr
device		com2	at isa? port "IO_COM3" tty irq 5 vector comintr
device		com3	at isa? port "IO_COM4" tty irq 9 vector comintr

#For high speed serial lines.
#device		sio0	at isa? port "IO_COM1" tty irq 4 vector siointr
#device		sio1	at isa? port "IO_COM2" tty irq 3 vector siointr
#device		sio2	at isa? port "IO_COM3" tty irq 5 vector siointr
#device		sio3	at isa? port "IO_COM4" tty irq 9 vector siointr

device		lpt0	at isa? port "IO_LPT3" tty irq 7 vector lptintr
device		lpa0	at isa? port "IO_LPT1" tty
device		lpa1	at isa? port "IO_LPT2" tty

device ed0 at isa? port 0x300 net irq 10 iomem 0xcc000 vector edintr
#device ed1 at isa? port 0x300 net irq 5 iomem 0xd8000 vector edintr
#device ie0 at isa? port 0x360 net irq 7 iomem 0xd0000 vector ieintr
#device is0 at isa? port 0x280 net irq 10 drq 7 vector isintr

pseudo-device	loop
pseudo-device	ether
pseudo-device	log
pseudo-device	sl	2
pseudo-device	pty	12
pseudo-device	speaker

pseudo-device	swappager
pseudo-device	vnodepager
pseudo-device	devpager