From owner-freebsd-current Mon May 3 11: 0:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id 16BF2156FD for ; Mon, 3 May 1999 11:00:42 -0700 (PDT) (envelope-from bright@rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id NAA13712; Mon, 3 May 1999 13:20:32 -0500 (EST) Date: Mon, 3 May 1999 13:20:30 -0500 (EST) From: Alfred Perlstein To: Luigi Rizzo Cc: current@freebsd.org Subject: Re: bridge+dummynet + "sysctl -a" panics in -current In-Reply-To: <199905030552.HAA21599@labinfo.iet.unipi.it> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 3 May 1999, Luigi Rizzo wrote: > > a box with de and xl interfaces plus BRIDGE and DUMMYNET compiled in, > > doing a "sysctl -a" will panic the box. (currproc == sysctl) > > if you think the panic is bridge-related, can you try manually the > net.link.ether.bridge* sysctl -- if they do not fail, then the problem > could be with the sysctl to fetch bridging statistics (and if you have > a recent system, "netstat -p bdg" should exercise that. > ok, egg in my face, that's not it i guess. What about patching rc.network to allow early setup of bridge though? I'll try to track this down a bit better... I was experianceing it the panic earlier when i had applied matt's NFS patches, however ,my other boxes don't panic when i sysctl -a. thanks, -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message