From owner-freebsd-current@FreeBSD.ORG Sat Feb 7 00:51:20 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 1817E16A4CE for ; Sat, 7 Feb 2004 00:51:20 -0800 (PST) Received: from mail.dragondata.com (server2-b.dragondata.com [64.202.113.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id B74DC43D2F for ; Sat, 7 Feb 2004 00:51:19 -0800 (PST) (envelope-from toasty@dragondata.com) Received: (qmail 83187 invoked by uid 1092); 7 Feb 2004 08:52:08 -0000 Received: from toasty@dragondata.com by server2.dragondata.com by uid 82 with qmail-scanner-1.20rc3 (uvscan: v4.2.40/v4296. spamassassin: 2.60-cvs. Clear:RC:1:. Processed in 0.641918 secs); 07 Feb 2004 08:52:08 -0000 Received: from ppp045.dhcp.your.org (HELO ?199.165.179.45?) (199.165.179.45) by mail.dragondata.com with RC4-SHA encrypted SMTP; 7 Feb 2004 08:52:08 -0000 In-Reply-To: References: <356CD0A4-5828-11D8-A138-000A95A8A1F2@dragondata.com> <20040206183306.GA13801@Odin.AC.HMC.Edu> Mime-Version: 1.0 (Apple Message framework v612) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Kevin Day Date: Sat, 7 Feb 2004 02:51:17 -0600 To: SUZUKI Shinsuke X-Mailer: Apple Mail (2.612) X-Mailman-Approved-At: Sat, 07 Feb 2004 04:52:48 -0800 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: Sat, 07 Feb 2004 08:51:20 -0000 On Feb 6, 2004, at 5:50 PM, SUZUKI Shinsuke wrote: > > I can reproduce the problem, and here's the trace: > if_up->if_route->in6_if_up->in6_ifattach->in6_ifattach_link > ->in6_update_ifa->in6_addmulti->if_addmulti->vlan_ioctl > ->vlan_setmulti->if_delmulti->fxp_ioctl->fxp_mc_setup > > The reason of this panic lies in if_fxp.c; fxp's > ethernet-multicast-filter is configured before the initializtion of > fxp driver. > > The attached ad-hoc patch fixed the problem, but IMHO much further > considerataion is necessary; this happens when vlan is initialized > before the initialization of its physical interface, and there might > be a similar different bug (in other driver or in different situation). > > So could anyone see to it? > #I'm afraid I cannot, because I'm not a device-driver expert... > Thanks a lot for tracking this down, I spent a few hours trying to reproduce it and couldn't before I discovered something slightly odd. This only seems to cause a panic if the fxp card has never been brought up since power on. If I "ifconfig fxp0 up" then warm-reboot, I can't make it crash. If I actually kill the power then try bringing up the vlan without bringing fxp0 up first, it will crash. That took a VERY long time to track down what was happening, but i've pretty much confirmed that's what is happening for me. Kinda strange, but I suppose I can understand what's happening. -- Kevin