Date: Sat, 5 Mar 2005 03:03:43 +0100 From: Maxime Henrion <mux@FreeBSD.org> To: Gavin Atkinson <gavin.atkinson@ury.york.ac.uk> Cc: othermark <atkin901@yahoo.com> Subject: Re: fxp0 and vlan panic Message-ID: <20050305020343.GO31320@elvis.mu.org> In-Reply-To: <20050226120253.O87543@ury.york.ac.uk> References: <1107887237.793.26.camel@buffy.york.ac.uk> <20050226120253.O87543@ury.york.ac.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050305020343.GO31320>