Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 7 Mar 2003 10:22:17 +0200 (EET)
From:      hw <hw@ksue.edu.ua>
To:        FreeBSD-gnats-submit@FreeBSD.org
Subject:   kern/48995: kernel crashes when ipfw configured with multiply pipes
Message-ID:  <200303070822.h278MHi52393@ksue.edu.ua>

next in thread | raw e-mail | index | archive | help

>Number:         48995
>Category:       kern
>Synopsis:       kernel crashes when ipfw configured with multiply pipes
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Mar 07 00:30:10 PST 2003
>Closed-Date:
>Last-Modified:
>Originator:     hw
>Release:        from FreeBSD 4.4-RELEASE i386 upto FreeBSD 4.7-RELEASE i386
>Organization:
Kharkov State University of Economics
>Environment:
System:
 FreeBSD ksue.edu.ua 4.4-RELEASE FreeBSD 4.4-RELEASE #0: Fri Aug 16 13:29:53 EEST 2002 root@mirinda.local:/usr/src/sys/compile/MIRINDA i386


>Description:
when ipfw configured that packet passes multiply pipes
at once kernel hangs almost on all spectrum of computers and FreeBSD
versions I seen. Crash behaviour depends upon network load and with
big amount of pipes can be achieved with sending one ip/icmp packet.
Regulating amount of pipes used one can crash network activity only
(computer itself will work normally using non-network software).

This piece of /etc/messages is only from one of crashes....
in other circumstances kernel was even unable to record
anything... even unable to reboot.

Fatal trap 10: trace trap while in kernel mode
instruction pointer    = 0x8:0xc013efbd
stack pointer          = 0x10:0xc9947ce4
frame pointer          = 0x10:0xc9947cfc
code segment           = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags       = trace trap, IOPL = 0
current process                = 34772 (perl)
interrupt mask         = net tty
trap number            = 10
panic: trace trap

>How-To-Repeat:
ipfw pipe 1 config
ipfw add 1 pipe 1 all from any to any
ipfw add 1 pipe 1 all from any to any
ipfw add 1 pipe 1 all from any to any
ipfw add 1 pipe 1 all from any to any
ipfw add 1 pipe 1 all from any to any
ipfw add 1 pipe 1 all from any to any
ipfw add 1 pipe 1 all from any to any
ipfw add 1 pipe 1 all from any to any
ipfw add 1 pipe 1 all from any to any
............at your wish.............

>Fix:
Sorry, don't know solution... anyway, queue rules of ipfw works queer
I was unable to implement WF2Q policy using them and code snippet above
was an attempt to solve queues queerness.

>Release-Note:
>Audit-Trail:
>Unformatted:

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200303070822.h278MHi52393>