From owner-freebsd-hackers Mon Feb 24 08:19:13 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id IAA26528 for hackers-outgoing; Mon, 24 Feb 1997 08:19:13 -0800 (PST) Received: from whyy.org (root@whyy.org [207.245.67.105]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA26522 for ; Mon, 24 Feb 1997 08:19:09 -0800 (PST) Received: from tvmaster1.whyy.org (tvmaster1.whyy.org [199.234.236.48]) by whyy.org (8.7.5/8.7.3) with SMTP id LAA03302; Mon, 24 Feb 1997 11:19:03 -0500 (EST) Date: Mon, 24 Feb 1997 11:19:03 -0500 (EST) Message-Id: <199702241619.LAA03302@whyy.org> X-Sender: jehrenkrantz@whyy.org X-Mailer: Windows Eudora Pro Version 2.1.2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: Jim Riffle From: "..je" Subject: Re: Recurring freeze with 2.1.5 system Cc: freebsd-hackers@FreeBSD.ORG Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 10:09 AM 2/24/97 -0500, you wrote: > > >On Sun, 23 Feb 1997, Jake Hamby wrote: > >> There's a 486 system at my Internet provider that he's set up as a "geek >> box" for people to hack on. It's a fairly lame configuration (486DX/4 >> 100MHz, 8MB RAM, IDE drives, NE2000 card). Anyway, it has a recurring >> problem where it will only answer pings. Logins, either remote or from the >> console, will hang (telnet will connect, but not prompt for username), and >> the system must be forcibly rebooted. >> >> We think it may be a hardware problem, perhaps bad RAM. I'm just curious if >> there are any known bugs in 2.1.5-RELEASE which might cause this. The >> systems are similar to a SYN attack, except for the frozen local login. >> We're going to upgrade it to 2.2-GAMMA next weekend, and hopefully the >> problems will go away. If not, can we safely conclude that it is a problem >> of buggy hardware? > >I ran into a very similar problem to this some time ago. I am not sure if >this is your problem, but it would definatly be worth tring before >swapping out your hardware. > >Add these 2 lines into you kernel config file (you can change the 256 to >anything you like) > >options "CHILD_MAX=256" >options "OPEN_MAX=256" > > >I belive the default is 64. > >My symptoms were similar to where the machine would respond to pings, but >would not start anything new. no logins, no web. Name server would >continue to function. Basically anything running would still run as long >as it didn't have to open any files. > >Jim > > i had a similar problem it turned out to be the nic a gvc technoligies the only change i made was to replace the nic with an smc-whatever and all problems went away gud luk ..je Regards ..je