WARNING: 7-STABLE BROKEN -- please wait to upgrade / Should be OK now

[O. Hartmann]

Kris Kennaway wrote:
> O. Hartmann wrote:
>> O. Hartmann wrote:
>>> Kris Kennaway wrote:
>>>> O. Hartmann wrote:
>>>>> Kris Kennaway wrote:
>>>>>> O. Hartmann wrote:
>>>>>>> Steve Bertrand wrote:
>>>>>>>> Dan Allen wrote:
>>>>>>>>> Well I got bit by this and am dead in the water.  Nothing 
>>>>>>>>> builds.  I tried the DEBUG_FLAGS=-g trick but to no avail.
>>>>>>>>
>>>>>>>> My 7.0 box upgraded fine this morning:
>>>>>>>>
>>>>>>>> FreeBSD ids.eagle.ca 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #0: 
>>>>>>>> Fri Aug 29 11:38:12 EDT 2008     
>>>>>>>> steve at ids:/usr/obj/usr/src/sys/SMP  i386
>>>>>>>>
>>>>>>>> The dmesg if it is relevant:
>>>>>>>>
>>>>>>>> http://ww3.ibctech.ca/ids.dmesg
>>>>>>>>
>>>>>>>> Steve
>>>>>>> Well, mine did not. I was capable of compiling world and kernel 
>>>>>>> and also capable of installing all things like I did in the 
>>>>>>> past, but ZFS seems still broken - the module does not load 
>>>>>>> automatically at initialization time nor is it loadable via 
>>>>>>> kldload (there is an error about missing opensolaris module but 
>>>>>>> I can't find anything about this module ...).
>>>>>>
>>>>>> It's new, you need to build it.
>>>>>>
>>>>>> Kris
>>>>>> _______________________________________________
>>>>>> freebsd-stable at freebsd.org mailing list
>>>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
>>>>>> To unsubscribe, send any mail to 
>>>>>> "freebsd-stable-unsubscribe at freebsd.org"
>>>>> Well, I hoped the 'buildworld' build everything process would do 
>>>>> so? Do I need an extra option in my kernel config?
>>>>
>>>> It is a kernel module, it doesn't get built by buildworld (by 
>>>> default).  If you use the default build settings for your kernel, 
>>>> it builds all modules including this one.  If you use 
>>>> MODULES_OVERRIDE or similar to specify a list of modules to build, 
>>>> you have to add it to the list.
>>>>
>>>> Kris
>>> The module is indeed present, and it was all the time present. 
>>> Obviously is something wrong or not in the right order with my 
>>> config. When makeing buildworld and then rebooting the box, ZFS 
>>> module does not automatically load OpenSOLARIS module when it 
>>> detects its absence. I guess  I need to fix an 'option opensolaris' 
>>> in my kernel config.
>>>
>>> Thanks,
>>>
>>> Oliver
>>
>>
>> here I am again. On a less critical mashine the installation process 
>> (buildwork/installworld and the same to the kernel) went through 
>> without problems. This box does have a ZFS device for backup purposes 
>> only, not essential.
>>
>> The box starts/booot.
>> When I try loading either opensolaris.ko/zfs.ko, I get this:
>>
>> link_elf_obj: symbol stack_save undefined
>> kldload: /boot/kernel/opensolaris.ko: Unsupported file type
>> link_elf_obj: symbol stack_save undefined
>> kldload: /boot/kernel/opensolaris.ko: Unsupported file type
>> KLD zfs.ko: depends on opensolaris - not available
>> kldload: /boot/kernel/zfs.ko: Unsupported file type
>>
>> I guess I forgot some of the recommended compiler switches ... ??
>
> The link_elf_obj error is important.  It looks like they rely on 
> either DDB or STACK in your kernel.
>
> Kris
> _______________________________________________
> freebsd-stable at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe at freebsd.org"

As recommended formerly in this list I defined 'options KDTRACE_HOOKS' 
in my kernel config due to the DTRACE merge. But I do not have any 
debugging option defined yet in any of my machine's kernels because of 
performance reasons.
So, if  I understand your comment the right way, I need to enable either 
STACK or DDB or both? I will try this anyway, starting with STACK, but I 
do not understand why I'm forced to do so.

Thanks,
Oliver