Gregory Sutter writes:
> I am experiencing a problem with syscons and init when I have a 
> certain line in my kernel configuration file, and am hoping that
> you can fix the bug.  My system is a recent 4-STABLE, although
> the problem also showed up in an April 24 4-STABLE.  I do not 
> have a -CURRENT box.  
> 
> FreeBSD trurl.zer0.org 4.3-STABLE FreeBSD 4.3-STABLE #6: Wed May 16 17:44:58 PDT 
>2001     [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GEN  i386
> 
> Here is a diff between a working kernel configuration file (GEN)
> and a non-working one (GEN.not):
> 
> trurl gsutter /sys/i386/conf $diff -u -0 GEN.not GEN
> --- GEN.not     Wed May 16 17:12:42 2001
> +++ GEN Wed May 16 17:49:06 2001
> @@ -61 +61 @@
> -options                SC_HISTORY_SIZE=8000
> +#options               SC_HISTORY_SIZE=8000
> 
> I have not tested with other SC_HISTORY_SIZE values.
> 
> When I boot with a kernel compiled with the SC_HISTORY_SIZE=8000
> option, I observe the following:
> 
> 1. No gettys are spawned.  If I ssh in, I can manually start 
> gettys. 
> 
> 2. Processes remain in zombie state after exiting.  This occurs
> whether they exit normally, or are killed with any signal.
> 
> These two symptoms lead me to believe that init(8) is being
> adversely affected by the syscons history size option.  
> 
> If I can be of assistance in tracking down this problem, please
> let me know.  
0cicuta~(5)>strings /kernel | grep ___ | grep SC_HISTORY_SIZE
___options      SC_HISTORY_SIZE=2118    # number of history buffer lines
0cicuta~(6)>dc 
2118 132 16 **p
4473216
q
0cicuta~(7)>uname -a
FreeBSD cicuta.babolo.ru 4.3-STABLE FreeBSD 4.3-STABLE #2: Mon May  7 05:12:15 MSD 
2001     [EMAIL PROTECTED]:/tmp/babolo/usr/src/sys/cicuta  i386

As far as I remember with SC_HISTORY_SIZE=2200 switich to
132 column mode crashed FreeBSD of some old version.

I think that reason for such behavior is big memory amount
for history (non swapable?)

-- 
@BABOLO      http://links.ru/

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Reply via email to