Bug 24735

Summary: Still problems (crashes) with ipfw, bridging and dummynet on 4.2-STABLE.
Product: Base System Reporter: admin <admin>
Component: kernAssignee: freebsd-bugs (Nobody) <bugs>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: 4.2-STABLE   
Hardware: Any   
OS: Any   

Description admin 2001-01-30 14:20:00 UTC
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.

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.)
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.
Comment 1 tmoestl 2001-01-30 15:59:32 UTC
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
Comment 2 slacker 2001-02-09 17:50:59 UTC
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 rx0, 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 ()
Comment 3 Luigi Rizzo freebsd_committer freebsd_triage 2001-02-11 23:07:33 UTC
State Changed
From-To: open->closed

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.