From owner-freebsd-bugs Thu Feb 6 7:30:14 2003 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 27CEC37B406 for ; Thu, 6 Feb 2003 07:30:09 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5668243FE0 for ; Thu, 6 Feb 2003 07:30:06 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.6/8.12.6) with ESMTP id h16FU6NS054924 for ; Thu, 6 Feb 2003 07:30:06 -0800 (PST) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.6/8.12.6/Submit) id h16FU6V9054923; Thu, 6 Feb 2003 07:30:06 -0800 (PST) Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2817537B401 for ; Thu, 6 Feb 2003 07:21:21 -0800 (PST) Received: from unia.3lo.lublin.pl (unia.3lo.lublin.pl [212.182.70.2]) by mx1.FreeBSD.org (Postfix) with SMTP id EE93E43F3F for ; Thu, 6 Feb 2003 07:21:19 -0800 (PST) (envelope-from pawmal@unia.3lo.lublin.pl) Received: (qmail 52737 invoked by uid 1007); 6 Feb 2003 15:21:57 -0000 Message-Id: <20030206152157.52736.qmail@unia.3lo.lublin.pl> Date: 6 Feb 2003 15:21:57 -0000 From: "Paweł" "Małachowski" Reply-To: "Paweł" "Małachowski" To: FreeBSD-gnats-submit@FreeBSD.org X-Send-Pr-Version: 3.113 Subject: kern/48009: dummynet(4) related machine hangs Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >Number: 48009 >Category: kern >Synopsis: dummynet(4) related machine hangs >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Feb 06 07:30:05 PST 2003 >Closed-Date: >Last-Modified: >Originator: Paweł Małachowski >Release: FreeBSD 4.7-STABLE i386 >Organization: ASK ZiN >Environment: System: FreeBSD gargantua.zin.ask 4.7-STABLE FreeBSD 4.7-STABLE #0: Mon Feb 3 23:33:35 CET 2003 root@gargantua.zin.ask:/mnt/j1/obj/usr/src/sys/PM-UX-AUTO-47S i386 >Description: Machine hangs within few hours after playing with dummynet(4) pipes configuration. System looks completly `frozen', only power-off/power-on cycle helps. It's easy to reproduce, see the How-To-Repeat section. This is the 4.7-STABLE, compiled from cvsupped sources dated 3rd February 2003. The IPFW2 IP Firewall code is used. However, similar problems were noticed in the past with the IPFW1, please compare with: kern/37573, kern/43133. It looks it was reported 9 months ago but was never fixed. >How-To-Repeat: Configure dummynet as shown here and run the test-ipfw.sh script. rl0 is my external interface. # ipfw show 65535 14249742 10902331939 allow ip from any to any # ipfw add 10 pipe 10 ip from any to any out xmit rl0 # ipfw pipe 10 config bw 0 # ipfw add 20 pipe 20 ip from any to any in recv rl0 # ipfw pipe 20 config bw 0 # sh ./test-ipfw.sh [...] Test number 375 (Czw 6 Lut 14:52:29 2003 CET). Step 1. Step 2. Step 3. And machine hangs. Once again, with the same configuration: Test number 22 (Czw 6 Lut 15:12:36 2003 CET). Step 1. Step 2. Step 3. And machine hangs again. This script was also `sucessfully' tested by my friend on some other 4.7-STABLE machine -- reported hang within 3 minutes... Here is the script I used to provoke the problem: # cat test-ipfw.sh #!/bin/sh i=1 while [ 1 ] do echo Test number $i \(`date`\). echo Step 1. ipfw pipe 10 config bw 2Mbit/s queue 10 sleep 1 echo Step 2. ipfw pipe 20 config bw 2Mbit/s queue 10 sleep 2 echo Step 3. ipfw pipe 10 config bw 4096kbit/s queue 20 sleep 1 echo Step 4. ipfw pipe 20 config bw 4096kbit/s queue 20 echo OK, waiting 3 seconds, and... sleep 3 i=`expr $i + 1` done >Fix: Unknown. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message