search for: 0xdd100

Hi Benjamin: I think that the following link will give you an idea for what you need to know: http://www.cisco.com/warp/customer/620/roadmap_b.shtml This is for the naming: http://www.cisco.com/en/US/products/sw/iosswrel/ps1818/products_tech_note09186a0080101cda.shtml In this case 11.1CC goes to 12.0T and 12.0T migrate to 12.1 mainline. Do not you worry you will not loose anything with the new

...\000\000\000\000\000\000\000\020\000\000\000\000\000\000\000", st_pad4 = {0, 0, 0, 0, 173, 0, 2141451620, 0}} fd = 18 ret = 1 #3 0x38bc8 in mbox_lock_dotlock (ctx=0xffbef2c0, lock_type=2, max_wait_time=1169749509) at mbox-lock.c:259 mbox = (struct mbox_mailbox *) 0xdd100 set = {temp_prefix = 0x0, lock_suffix = 0x0, timeout = 300, stale_timeout = 120, callback = 0x38a04 <dotlock_callback>, context = 0xffbef2c0, use_excl_lock = 0} ret = 1 #4 0x38fe0 in mbox_lock_list (ctx=0xffbef2c0, lock_type=2, max_wait_time=1169749509, idx=1) at mbox...