From owner-freebsd-current Sun Feb 27 13:57:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 7A39437B5E5 for ; Sun, 27 Feb 2000 13:57:17 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id NAA67945; Sun, 27 Feb 2000 13:57:11 -0800 (PST) (envelope-from dillon) Date: Sun, 27 Feb 2000 13:57:11 -0800 (PST) From: Matthew Dillon Message-Id: <200002272157.NAA67945@apollo.backplane.com> To: Stefan Schmidt Cc: current@FreeBSD.ORG Subject: Re: Machine is 'hanging'. References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :hi there, :i have got a problem with a router running FreeBSD 3.4-REL: :Every three days or so it hangs, whiche means that the console is not :responding any more, open tcp ports don't respond == are timing-out just :like they're filtered. I guess the machine is just unable to start a :shell. Oh and well it is appearently able to route as the machines behind :it are reachable, and it does repond to pings. :Which brings me to my question: :okay this sounds like a hardware problem, but what could it be, the board :, the memory. If anyone here has seen something similar i'd be glad if you :could help me. : :regards, : Stefan Schmidt Sounds like a kernel bug to me. If you can compile and install a kernel with DDB enabled, you should be able to ctl-alt-esc it on the console when it hangs, then from the DDB prompt do a 'trace' command and a 'ps' command and maybe we can figure out why it hung from that. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message