From owner-freebsd-current@FreeBSD.ORG Wed Feb 27 15:02:21 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2BAB31065671 for ; Wed, 27 Feb 2008 15:02:21 +0000 (UTC) (envelope-from matthew@matthew.sk) Received: from mailserver.antik.sk (mailserver.antik.sk [88.212.10.6]) by mx1.freebsd.org (Postfix) with ESMTP id 6F4F18FC2D for ; Wed, 27 Feb 2008 15:02:20 +0000 (UTC) (envelope-from matthew@matthew.sk) Received: (qmail 11715 invoked from network); 27 Feb 2008 15:35:37 +0100 Received: by simscan 1.4.0 ppid: 11704, pid: 11712, t: 0.0078s scanners: regex: 1.4.0 attach: 1.4.0 clamav: 0.91.2/m:45/d:6004 Received: from unknown (HELO ?10.252.4.243?) (matthew@matthew.sk@10.252.4.243) by mailserver.antik.sk with AES256-SHA encrypted SMTP; 27 Feb 2008 15:35:37 +0100 Message-ID: <47C5753A.8010806@matthew.sk> Date: Wed, 27 Feb 2008 15:35:38 +0100 From: matthew User-Agent: Mozilla-Thunderbird 2.0.0.9 (X11/20080110) MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: FreeBSD 7.0 Beta,RC,RELEASE (amd64) freezes with dummynet enabled X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Feb 2008 15:02:21 -0000 I have posted before that i have a stability issue with the 7.0 branch on my servers. Tested on BETA2,BETA4,RC1,RC2,RELEASE The original thread and my post with details is at: http://unix.derkeiler.com/Mailing-Lists/FreeBSD/current/2007-12/msg00674.html I was waiting for the 7.0-RELEASE, updated the whole servers, and enabled dummynet again, but it always freezes after some minutes, 100% reproducible. I tested it also on a HP 140 G3 1U server, where 6.3 has absolutely no problems, but the 7.0 branch keeps freezing. Again, if it helps to solve this bug, i can rebuild the kernel with debug symbols a take some screenshots :)