Date: Wed, 15 Jul 2009 21:00:48 -0300 From: "Luiz Otavio O Souza" <lists.br@gmail.com> To: "Robert Watson" <rwatson@FreeBSD.org>, "Florian Smeets" <flo@kasimir.com> Cc: current@FreeBSD.org Subject: Re: Rebuild all network-related kernel modules on 8-current due to vnet allocator change Message-ID: <2C5625D41921454788B78F72DEB7F9CF@adnote989> References: <alpine.BSF.2.00.0907150016260.54568@fledge.watson.org> <05461E04E6BD4477A879553178599F6E@adnote989> <8026EC1942CE4C128F168BBBFD987B27@adnote989> <alpine.BSF.2.00.0907150958250.54568@fledge.watson.org> <4A5D9C51.7070708@kasimir.com> <alpine.BSF.2.00.0907151020590.54568@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> > On Wed, 15 Jul 2009, Florian Smeets wrote: > >>>>> My kernel don't have any VIMAGE options. >>>>> >>>>> The system is working flawless before the upgrade. >>>>> >>>>> If you need any/more information about this, just let me know. >>>> >>>> I've just commented out the panic() in link_elf_obj.c and now i'm able >>>> to create vlans again. >>> >>> This assertion may well be too conservative -- is there any chance you >>> have a kernel built with the DTrace CTF support? It may be using >>> progbits, in which case removing the assertion is the right solution. >>> I'll test this hypothesis. >> >> i'm also seeing this panic, it happens when zfs.ko is loaded in my case. >> I don't have anything DTrace CTF related in my kernel. > > OK. I'm not able to reproduce it here, but clearly there must be some > ELF/etc case I haven't thought of or understood. I've committed a removal > of the assertion, r195707 and will debug it offline, we can re-add it if I > come up with a more refined/useful version. > > Robert N M Watson > Computer Laboratory > University of Cambridge > The kernel i'm running here doesn't have any DTrace facility enabled (it is just the plain GENERIC kernel with ipfw, natd (divert) and kernel nat support). But my system is running on zfs exactly like Florian reported, so it may be related. This firewall is running fine (in production) all day long without any other problem. Here is what i'm using on my rc.conf wich also may be relevant for debug: hostname="fw-sp.xxxxxxx.com.br" cloned_interfaces="vlan0 vlan1 vlan2" ifconfig_bge1="up" ifconfig_vlan0="vlandev bge1 vlan 100" ifconfig_vlan1="vlandev bge1 vlan 101" ifconfig_vlan2="vlandev bge1 vlan 102" ipv4_addrs_bge0="90.0.1.1/24" # internal address - don't ask... ipv4_addrs_vlan0="xxx.x.x.x/28" # external address - uplink 1 ipv4_addrs_vlan1="xxx.x.x.146-148/29" # external address - uplink 2 ipv4_addrs_vlan2="192.168.2.1/24" # dmz network - i've some nated address here defaultrouter="x.x.x.x" # uplink 1 And many thanks for the quick fix. Luiz
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2C5625D41921454788B78F72DEB7F9CF>