From owner-freebsd-current@FreeBSD.ORG Sat Mar 5 02:03:43 2005 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 6B8E816A4D0 for ; Sat, 5 Mar 2005 02:03:43 +0000 (GMT) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 43C2943D2D for ; Sat, 5 Mar 2005 02:03:43 +0000 (GMT) (envelope-from mux@freebsd.org) Received: by elvis.mu.org (Postfix, from userid 1920) id 3E6255C996; Fri, 4 Mar 2005 18:03:43 -0800 (PST) Date: Sat, 5 Mar 2005 03:03:43 +0100 From: Maxime Henrion To: Gavin Atkinson Message-ID: <20050305020343.GO31320@elvis.mu.org> References: <1107887237.793.26.camel@buffy.york.ac.uk> <20050226120253.O87543@ury.york.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050226120253.O87543@ury.york.ac.uk> User-Agent: Mutt/1.4.2.1i cc: freebsd-current@freebsd.org cc: othermark Subject: Re: fxp0 and vlan panic 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, 05 Mar 2005 02:03:43 -0000 Gavin Atkinson wrote: > On Thu, 24 Feb 2005, othermark wrote: > > Mark Huizer wrote: > > > On Mon, Feb 14, 2005 at 12:56:08PM -0800, othermark wrote: > > >> Gavin Atkinson wrote: > > >> > There's an easily reproduceable panic involving configuring vlans on > > >> > fxp cards. I've recreated it in single user mode on a top-of-tree > > >> > -CURRENT machine as well as on a 5.3-STABLE machine. > > >> > > >> I reported this during December. > > >> > > >> http://article.gmane.org/gmane.os.freebsd.current/63657 > > > > > > Are more people seeing this? > > > > I think you should file a PR, this is a safe one. I have at least > > 5 different machines running -current with various revs Intel 8255* which > > all panic after the LOR. All thats required is these three commands after > > a fresh boot up. > > > > ifconfig vlan0 create > > ifconfig vlan0 vlan 999 vlandev fxp0 > > ifconfig vlan0 inet 172.16.64.3 netmask 255.255.240.0 > > Indeed. I've filed a PR about it, kern/78112. > > I hope it's not too late to get this resolved for 5.4. Just for the record, and for people not reading CVS commit logs, I committed a fix for this a few days ago and I will make sure to MFC it in time for 5.4-RELEASE. Cheers, Maxime