From owner-freebsd-stable@FreeBSD.ORG Sun Aug 3 19:08:37 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B7E041065676 for ; Sun, 3 Aug 2008 19:08:37 +0000 (UTC) (envelope-from melnik@venik.uplink.net.ua) Received: from venik.uplink.net.ua (venik.uplink.net.ua [195.3.204.34]) by mx1.freebsd.org (Postfix) with ESMTP id 76DAD8FC18 for ; Sun, 3 Aug 2008 19:08:37 +0000 (UTC) (envelope-from melnik@venik.uplink.net.ua) Received: by venik.uplink.net.ua (Postfix, from userid 1000) id A99C928817; Sun, 3 Aug 2008 21:49:51 +0300 (EEST) Date: Sun, 3 Aug 2008 21:49:51 +0300 From: Vladimir Melnik To: freebsd-stable@freebsd.org Message-ID: <20080803184951.GK10693@venik.uplink.net.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.16 (2007-06-09) Subject: 7-STABLE, mpd-4.4.1_1 and others... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Aug 2008 19:08:37 -0000 Hello! We encountered some strange problem with 7.0-RELEASE and 7.0-STABLE. We have an amd64 server which works as core-router on our small network. There are almost one hundred ipfw-pipes for limiting bandwidth, mpd-4.4.1_1 for termination pptp-sessions, ng_ipacct-20061223 for traffic counting and quagga-0.99.9_7 for bgp- and ospf-routing. SOmetimes mpd goes a little crazy: it stops working, but process doesn't stop. Process stays in memory as "uninterruptable" process: PID STAT WCHAN COMMAND 5891 Ds ngsock mpd4 When we trying to send a SIGKILL to this process, nothing changes, of course. But the most strange thing is there: when we trying to reboot the system, system just hangs. There are no messages in logs, no messages on console, it just hangs and doesn't react upon any actions. There was no such problem on 6.2-RELEASE, so we are dissapointed a little. :) Thank you very much in adcance for your help and sorry for my bad English. -- V.Melnik