From owner-freebsd-current@FreeBSD.ORG Fri Feb 6 10:33:14 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2DEA616A4CE for ; Fri, 6 Feb 2004 10:33:14 -0800 (PST) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id C8B0043D2F for ; Fri, 6 Feb 2004 10:33:12 -0800 (PST) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (IDENT:brdavis@localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.12.10/8.12.3) with ESMTP id i16IX62h017660; Fri, 6 Feb 2004 10:33:07 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.12.10/8.12.3/Submit) id i16IX6RI017659; Fri, 6 Feb 2004 10:33:06 -0800 Date: Fri, 6 Feb 2004 10:33:06 -0800 From: Brooks Davis To: Kevin Day Message-ID: <20040206183306.GA13801@Odin.AC.HMC.Edu> References: <356CD0A4-5828-11D8-A138-000A95A8A1F2@dragondata.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="huq684BweRXVnRxX" Content-Disposition: inline In-Reply-To: <356CD0A4-5828-11D8-A138-000A95A8A1F2@dragondata.com> User-Agent: Mutt/1.5.4i X-Virus-Scanned: by amavisd-milter (http://amavis.org/) on odin.ac.hmc.edu cc: freebsd-current@freebsd.org Subject: Re: vlan panic in -CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Feb 2004 18:33:14 -0000 --huq684BweRXVnRxX Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Feb 05, 2004 at 04:11:12PM -0600, Kevin Day wrote: >=20 > This crashes -CURRENT (from a couple of days ago) for me: >=20 > ifconfig vlan0 create > ifconfig vlan0 vlan 2 vlandev fxp0 > ifconfig vlan0 up >=20 > (immediate trap 12/page fault while in kernel mode crash) >=20 > BUT, if I manually bring up fxp0 first, everything is fine. >=20 > ifconfig fxp0 up > ifconfig vlan0 create > ifconfig vlan0 vlan 2 vlandev fxp0 > ifconfig vlan0 up >=20 > I don't have a crash dump since I don't have enough space on this=20 > drive. but this should be pretty easy to reproduce. If this isn't=20 > reproducible by whoever wants to look at this, I'm happy to get a=20 > backtrace through some other means. I'm using a stock GENERIC kernel,=20 > except I've added bridging and ipfw. >=20 > Sorry if this has already been reported, but I don't see anything in=20 > gnats or the mailing lists about it. Well, it's not related to simply upping a vlan on a down interface since I can't reproduce it with fwe0. I've got a shortage of systems configured for debugging that have an extra nic in them so I can't seem to replicate this. Since it should be possiable to replicate in single user mode, you might try setting hw.physmem to something small enough that you can get a crashdump. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --huq684BweRXVnRxX Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFAI93hXY6L6fI4GtQRArzbAJ90HSrsRztqi6nqeBsmq57FVrJw+wCgk38C 9/3oe5WwGqKNGiAeH/My72Q= =LXtp -----END PGP SIGNATURE----- --huq684BweRXVnRxX--