From owner-freebsd-stable Tue May 21 2:42:18 2002 Delivered-To: freebsd-stable@freebsd.org Received: from alogis.com (firewall.solit-ag.de [212.184.102.1]) by hub.freebsd.org (Postfix) with ESMTP id 7256237B406 for ; Tue, 21 May 2002 02:42:11 -0700 (PDT) Received: from alogis.com (kipp@clausthal.int1.b.intern [10.1.1.30]) by alogis.com (8.11.1/8.9.3) with ESMTP id g4L9fxl87748; Tue, 21 May 2002 11:41:59 +0200 (CEST) (envelope-from holger.kipp@alogis.com) Message-ID: <3CEA128A.AB7FAC93@alogis.com> Date: Tue, 21 May 2002 11:25:30 +0200 From: Holger Kipp X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.13 i686) X-Accept-Language: en MIME-Version: 1.0 To: frank@exit.com Cc: Pete French , stable@FreeBSD.ORG, Maildrop Subject: Re: 4.6-RC system hangs (fxp0, smp, sym) References: <200205210644.g4L6i4HK018378@realtime.exit.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Frank Mayhar wrote: > > Holger Kipp wrote: > > System hangs after some traffic on a 10Mbit link. Hang can be triggered > > by running 'ping -f' against a stupid Win98-System. Hang occurs after > > 50.000 to 1.400.000 packets. I'll have to investigate further to see if > > this depends on other system activity... > it is completely unresponsive. At some point, though, it decides to start > running again. Hmm, I'll give it a try to see if my system comes back also (so far, I only left it running for up to half an hour -- without success...). [mental note: I need more patience] > I'm unable to do _anything_ during a hang. I usually run X and it is > wedged solid. Same with me. I use console, switching between terminals. That also works during hangs. I can't login during hangs, nor can I start programs from disk. But if I started ifconfig before the hang (so it is still _in_memory_), I _can_ use it. Also, other processes like setiathome are just continuing to work happily as top will show (top should be running before the hang, of course). Maybe for debugging we should copy all necessary tools to memory disk, as hard disk access looks pretty frozen ;-) during hangs. [ I'd say this is the time for developers to speak up ;-) ] Regards, Holger -- Holger Kipp, Dipl.-Math., Systemadministrator | alogis AG Fon: +49 (0)30 / 43 65 8 - 114 | Berliner Strasse 26 Fax: +49 (0)30 / 43 65 8 - 214 | D-13507 Berlin Tegel email: holger.kipp@alogis.com | http://www.alogis.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message