Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 15 Jul 2009 11:07:29 +0200
From:      Florian Smeets <flo@kasimir.com>
To:        Robert Watson <rwatson@FreeBSD.org>
Cc:        Luiz Otavio O Souza <lists.br@gmail.com>, current@FreeBSD.org
Subject:   Re: Rebuild all network-related kernel modules on 8-current due to vnet allocator change
Message-ID:  <4A5D9C51.7070708@kasimir.com>
In-Reply-To: <alpine.BSF.2.00.0907150958250.54568@fledge.watson.org>
References:  <alpine.BSF.2.00.0907150016260.54568@fledge.watson.org>	<05461E04E6BD4477A879553178599F6E@adnote989>	<8026EC1942CE4C128F168BBBFD987B27@adnote989> <alpine.BSF.2.00.0907150958250.54568@fledge.watson.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On 15.07.09 10:59, Robert Watson wrote:
>
> On Wed, 15 Jul 2009, Luiz Otavio O Souza wrote:
>
>>> After update to r195705 my system panic every time i try to create a
>>> new vlan (but i can create a gif interface):
>>>
>>> # ifconfig vlan0 create
>>> panic: link_elf_load_file: unexpected progbits type
>>> cpuid = 1
>>> KDB: enter: panic
>>> [thread pid 1023 tid 100136]
>>>
>>> (hand transcribed - i've just an usb keyboard here)
>>>
>>> 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.
>

Hi,

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.

Cheers,
Florian



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4A5D9C51.7070708>