From nobody@FreeBSD.org  Tue Jan 30 06:17:13 2001
Return-Path: <nobody@FreeBSD.org>
Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21])
	by hub.freebsd.org (Postfix) with ESMTP id 7BC9D37B4F8
	for <freebsd-gnats-submit@FreeBSD.org>; Tue, 30 Jan 2001 06:17:12 -0800 (PST)
Received: (from nobody@localhost)
	by freefall.freebsd.org (8.11.1/8.11.1) id f0UEHCr58587;
	Tue, 30 Jan 2001 06:17:12 -0800 (PST)
	(envelope-from nobody)
Message-Id: <200101301417.f0UEHCr58587@freefall.freebsd.org>
Date: Tue, 30 Jan 2001 06:17:12 -0800 (PST)
From: admin@allegan.net
To: freebsd-gnats-submit@FreeBSD.org
Subject: Still problems (crashes) with ipfw, bridging and dummynet on 4.2-STABLE.
X-Send-Pr-Version: www-1.0

>Number:         24735
>Category:       kern
>Synopsis:       Still problems (crashes) with ipfw, bridging and dummynet on 4.2-STABLE.
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Jan 30 06:20:00 PST 2001
>Closed-Date:    Sun Feb 11 15:07:33 PST 2001
>Last-Modified:  Sun Feb 11 15:11:39 PST 2001
>Originator:     Sean Gum
>Release:        4.2-STABLE
>Organization:
Allegan Internet Services, Inc.
>Environment:
FreeBSD bandwidth.allegan.net 4.2-STABLE FreeBSD 4.2-STABLE #0: Sun Jan 28 13:25
:16 EST 2001     root@bandwidth.allegan.net:/usr/src/sys/compile/FWKERNEL  i386

>Description:
I am still having problems getting ipfw, bridging and dummynet to be
stable. 4.1 and 4.2 caused panics upon startup. 4.2-Stable allows it
to run (yeah!) but it is still unstable. About every hour or so it
reboots. Sometimes it reboots 5 or 6 times in a few minutes time. There
is no pattern. However if I disable bridging it will runs fine.
>How-To-Repeat:
Install ipfw, bridging and dummynet on a 4.2-STABLE release. Run it for
a few hours and you'll get a panic/reboot sometime during that period.

>Fix:
I tried the patch mentioned in PR23187 but it didn't help any. Rebooted
again in less than an hour. No fixes are known to me. (Other than disabling
bridging which I can't do.)


>Release-Note:
>Audit-Trail:

From: Thomas Moestl <tmoestl@gmx.net>
To: freebsd-gnats-submit@FreeBSD.org, admin@allegan.net
Cc:  
Subject: Re: kern/24735: Still problems (crashes) with ipfw, bridging and dummynet on 4.2-STABLE.
Date: Tue, 30 Jan 2001 16:59:32 +0100

 Hi,
 > I am still having problems getting ipfw, bridging and dummynet to be
 > stable. 4.1 and 4.2 caused panics upon startup. 4.2-Stable allows it
 > to run (yeah!) but it is still unstable. About every hour or so it
 > reboots. Sometimes it reboots 5 or 6 times in a few minutes time. There
 > is no pattern. However if I disable bridging it will runs fine.
 Perhaps you are running out of mbuf clusters? You should do a netstat -m 
 to check this. If the peak values are close to max, you need to increase
 NMBCLUSTERS (or probably better maxusers) in you kernel config. These
 settings are also changeable via sysctls (in kern.ipc).
 If this is not the problem, could you please supply more debugging
 info (e.g. panic message, if possible backtrace)?
 
 	- thomas
 
 

From: slacker <slacker@allegan.net>
To: freebsd-gnats-submit@FreeBSD.org, admin@allegan.net
Cc:  
Subject: Re: kern/24735: Still problems (crashes) with ipfw, bridging and 
 dummynet on 4.2-STABLE.
Date: Fri, 09 Feb 2001 12:50:59 -0500

 Not a problem with the NMBCLUSTERS. They get nowhere near max. Here is a
 recent panic log. I hope it helps. Reboots are becoming rather frequent
 again.
 
 \\bandwidth# gdb -k kernel /var/crash/vmcore.1
 GNU gdb 4.18
 Copyright 1998 Free Software Foundation, Inc.
 GDB is free software, covered by the GNU General Public License, and you
 are
 welcome to change it and/or distribute copies of it under certain
 conditions.
 Type "show copying" to see the conditions.
 There is absolutely no warranty for GDB.  Type "show warranty" for
 details.
 This GDB was configured as "i386-unknown-freebsd"...
 (no debugging symbols found)...
 IdlePTD 4624384
 initial pcb at 3b34e0
 panicstr: page fault
 panic messages:
 ---
 Fatal trap 12: page fault while in kernel mode
 fault virtual address   = 0xc08f2000
 fault code              = supervisor write, page not present
 instruction pointer     = 0x8:0xc02ee3e9
 stack pointer           = 0x10:0xc037f9d4
 frame pointer           = 0x10:0xc037f9e0
 code segment            = base 0x0, limit 0xfffff, type 0x1b
                         = DPL 0, pres 1, def32 1, gran 1
 processor eflags        = interrupt enabled, resume, IOPL = 0
 current process         = Idle
 interrupt mask          = net tty
 trap number             = 12
 panic: page fault
 
 syncing disks...
 done
 Uptime: 4m22s
 
 dumping to dev #ad/0x20001, offset 458752
 dump ata0: resetting devices .. done
 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8
 7 6 5 4
  3 2 1
 ---
 #0  0xc01aa842 in dumpsys ()
 
 
 
State-Changed-From-To: open->closed 
State-Changed-By: luigi 
State-Changed-When: Sun Feb 11 15:07:33 PST 2001 
State-Changed-Why:  
the code involved in this PR has been largely modified since 
the report, so the PR is not significant anymore. 
please upgrade to today's version of stable and file a new 
PR if you still have problems. 



http://www.freebsd.org/cgi/query-pr.cgi?pr=24735 
>Unformatted:
