>>> FYI, I've re-spun today's clearview-ipobs bfu archives to include this
>>> change, and the builds completed a few minutes ago.  The builds in the
>>> gate's archive directory therefore now include this change.
>>>     
>>>       
>> In order for your system to boot after having bfu'ed these bits, you
>> must manually remove the lo driver from your system. 
>>     
> Is it "/kernel/drv/`isainfo -k`/lo" ?
>   
It's verified.
Thanks.
> Thanks.
>   
>>  Otherwise, you are
>> likely to hit the following ASSERT() failure during boot:
>>
>> panic[cpu0]/thread=cf22dde0: assertion failed: ns_reg[moduleid].nr_create == 
>> 0, file: ../../common/os/netstack.c, line: 168                               
>>       
>>                                                                              
>>    
>> cf22db80 genunix:assfail+5a (feafa5e8, feafa640,)                            
>>    
>> cf22dba4 genunix:netstack_register+159 (10, f9d2ed40, 0, f9)                 
>>    
>> cf22dbcc ipnet:_init+4f (3, 0, d17c6aa0, cf2)                                
>>    
>> cf22dbec genunix:modinstall+ef (d17c6aa0)                                    
>>    
>> cf22dc0c genunix:mod_hold_installed_mod+6b (d17c7c80, 1, 0, cf2)
>> cf22dc4c genunix:modrload+c0 (feb1b2a0, c8618b28,)
>> cf22dc64 genunix:modload+13 (feb1b2a0, c8618b28)
>> cf22dc90 genunix:mod_hold_dev_by_major+7f (11e)
>> cf22dca8 genunix:ndi_hold_driver+29 (ca02adf0)
>> cf22dcc8 genunix:probe_node+32 (ca02adf0)
>> cf22dce4 genunix:i_ndi_config_node+f3 (ca02adf0, 6, 0)
>> cf22dd08 genunix:i_ddi_attachchild+56 (ca02adf0)
>> cf22dd24 genunix:devi_attach_node+e4 (ca02adf0, 4004048)
>> cf22dd54 genunix:config_immediate_children+e6 (c8ae2910, 4004048, )
>> cf22dd70 genunix:devi_config_common+7f (c8ae2910, 4004048, )
>> cf22ddc8 genunix:mt_config_thread+53 (cf5e90d0, 0)
>> cf22ddd8 unix:thread_start+8 ()
>>
>> The reason for this failure is that the ipnet module is using a netstack
>> id that was previously the netstack id of the lo module, so both modules
>> have the same netstack id.  Because all modules are loaded during boot
>> on a debug kernel, when the second module loads, netstack_register()
>> thinks that it has already registered and panics.
>>
>> -Seb
>>
>>
>> _______________________________________________
>> clearview-dev mailing list
>> clearview-dev at opensolaris.org
>> http://mail.opensolaris.org/mailman/listinfo/clearview-dev
>>   
>>     
>
>
>   


-- 
Best regards,
Lizhong


Reply via email to