kern/74635: [panic] vlan over fxp driver IP assignment crash

[Jonas Nagel]

The following reply was made to PR kern/74635; it has been noted by GNATS.

From: Jonas Nagel <fireball at zerouptime.ch>
To: freebsd-gnats-submit at FreeBSD.org,
	=?ISO-8859-1?Q?Micha=B3?= Listos <mcl at mclhq.com>
Cc:  
Subject: Re: kern/74635: [panic] vlan over fxp driver IP assignment crash
Date: Sat, 04 Dec 2004 18:15:46 +0100

 Micha=B3 Listos mcl <at> mclhq.com wrote:
 > I don't want to pollute freebsd-bugs, and have no time to read about=20
 > proper way to answer there,
 > so I mail you directly.
 
 Well if you decide to follow up, you could simply click on the bottom
 link in the web pr (http://www.freebsd.org/cgi/query-pr.cgi?pr=3D74635).=20
 
 OR you can simply reply to the bug either to freebsd-gnats-submit but
 then make sure you keep the subject the way it is (plus a Re: or
 whatever in front). When replying make sure you only quote the
 absolutely necessary and don't do jeopary quoting. Reply between the
 lines you refer to (like I do now).
 
 > Make sure you did "ifconfig fxp0 up" before issuing the above commands,=
 =20
 > it worked for me
 > some time ago on stationary pc.
 
 I noticed that doing
 # ifconfig vlan0 create
 # ifconfig vlan0 vlan 1 vlandev fxp0
 and
 # ifconfig vlan0 up
 panics the kernel as well. That means its not the assigning of the IP
 but its the 'bringing up the interface', which is the problem.
 
 Actually I had to do
 # ifconfig fxp0 up
 AFTER configuring the vlan0 interface and BEFORE assigning an IP (thus
 bringing the vlan0 interface up). Then it worked for me without crash!
 
 Thanks to you, Micha, since this is a workaround, I replied directly to
 gnats as well.
 
 But the crash should still be fixed. Since we tracked down the issue to
 a very specific action I think this shouldn't be too hard anymore.
 
 
 Regards,
 --=20
 Jonas Nagel <fireball at zerouptime.ch>