From owner-freebsd-net@FreeBSD.ORG Mon Jul 11 11:51:50 2011 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B9D9B1065672 for ; Mon, 11 Jul 2011 11:51:50 +0000 (UTC) (envelope-from egrosbein@rdtc.ru) Received: from eg.sd.rdtc.ru (unknown [IPv6:2a03:3100:c:13::5]) by mx1.freebsd.org (Postfix) with ESMTP id 22CFC8FC14 for ; Mon, 11 Jul 2011 11:51:49 +0000 (UTC) Received: from eg.sd.rdtc.ru (localhost [127.0.0.1]) by eg.sd.rdtc.ru (8.14.4/8.14.4) with ESMTP id p6BBpfkU079375; Mon, 11 Jul 2011 18:51:41 +0700 (NOVST) (envelope-from egrosbein@rdtc.ru) Message-ID: <4E1AE3C8.8030708@rdtc.ru> Date: Mon, 11 Jul 2011 18:51:36 +0700 From: Eugene Grosbein User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; ru-RU; rv:1.9.2.13) Gecko/20110112 Thunderbird/3.1.7 MIME-Version: 1.0 To: Vlad Galu References: <4E1AE1AD.4020907@rdtc.ru> <833EECF8-245B-4085-B853-AC753DBE0D19@dudu.ro> In-Reply-To: <833EECF8-245B-4085-B853-AC753DBE0D19@dudu.ro> Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 8bit Cc: "net@freebsd.org" Subject: Re: Repeating kernel panic within dummynet X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jul 2011 11:51:50 -0000 11.07.2011 18:45, Vlad Galu пишет: > > On Jul 11, 2011, at 1:42 PM, Eugene Grosbein wrote: > >> Hi! >> >> My FreeBSD 8.2/amd64 routers use dummynet heavily >> and keep panic with the *same* KDB backtrace: >> >> dummynet: bad switch -256! Forgot to mention that I use io_fast dummynet mode and have increased pipe lengths: net.inet.ip.dummynet.pipe_slot_limit=1000 net.inet.ip.dummynet.io_fast=1 Distinct pipes do really use long lengths. >> Sadly, I cannot add options INVARIANTS to the kernel because it makes my mpd-based >> routers to panic very often (every 2-3 hours) due to famous 'dangling pointer' >> problem - PPPoE user disconnects, its ngXXX interface got removed, then its traffic >> goes out various system queues (netisr, dummynet etc.) and another kind of panic >> occurs due to INVARIANTS' references to non-existent ifp. > > Hi Eugene, > If your ISR threads aren't already bound to CPUs, you can bind them and try using INVARIANTS. Please explain how to bind them. I have 4-core boxes with 4 NICs grouped to 2 laggs, one lagg(4) for uplink and another one for downlink. Eugene Grosbein