From owner-freebsd-net@FreeBSD.ORG Mon Jul 11 12:02:29 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 00B161065672 for ; Mon, 11 Jul 2011 12:02:29 +0000 (UTC) (envelope-from dudu@dudu.ro) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 8E0298FC1C for ; Mon, 11 Jul 2011 12:02:28 +0000 (UTC) Received: by bwa20 with SMTP id 20so4298642bwa.13 for ; Mon, 11 Jul 2011 05:02:27 -0700 (PDT) Received: by 10.204.169.66 with SMTP id x2mr1547648bky.399.1310385747016; Mon, 11 Jul 2011 05:02:27 -0700 (PDT) Received: from [192.168.10.3] ([82.76.253.74]) by mx.google.com with ESMTPS id e16sm9266726bke.6.2011.07.11.05.02.24 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 11 Jul 2011 05:02:26 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=utf-8 From: Vlad Galu In-Reply-To: <4E1AE3C8.8030708@rdtc.ru> Date: Mon, 11 Jul 2011 14:02:22 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <30BDDC28-275C-4DAA-9AC8-621F36A19D3B@dudu.ro> References: <4E1AE1AD.4020907@rdtc.ru> <833EECF8-245B-4085-B853-AC753DBE0D19@dudu.ro> <4E1AE3C8.8030708@rdtc.ru> To: Eugene Grosbein X-Mailer: Apple Mail (2.1084) 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 12:02:29 -0000 On Jul 11, 2011, at 1:51 PM, Eugene Grosbein wrote: > 11.07.2011 18:45, Vlad Galu =D0=BF=D0=B8=D1=88=D0=B5=D1=82: >>=20 >> On Jul 11, 2011, at 1:42 PM, Eugene Grosbein wrote: >>=20 >>> Hi! >>>=20 >>> My FreeBSD 8.2/amd64 routers use dummynet heavily >>> and keep panic with the *same* KDB backtrace: >>>=20 >>> dummynet: bad switch -256! >=20 > Forgot to mention that I use io_fast dummynet mode > and have increased pipe lengths: >=20 > net.inet.ip.dummynet.pipe_slot_limit=3D1000 > net.inet.ip.dummynet.io_fast=3D1 >=20 > Distinct pipes do really use long lengths. >=20 >>> 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. >>=20 >> Hi Eugene, >> If your ISR threads aren't already bound to CPUs, you can bind them = and try using INVARIANTS. >=20 > 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. >=20 net.isr.bindthreads=3D1 I'm not sure how and if that would help your particular setup, but it = did so in Adrian Minta's recent netgraph/mpd experiments. According to = an off-list chat I had with him, the machine would panic unless the ISRs = were bound. > Eugene Grosbein