Re[2]: Getting this Fatal Trap with heavy network activity

#16 0xc0539c1c in ithread_execute_handlers () #17 0xc0539d66 in ithread_loop () #18 0xc053878f in fork_exit () #19 0xc06ec18c in fork_trampoline () XL I think this was a fatal trap 12 and you may want to try if updating to XL 6.2-STABLE helps. There was some important related fixes in

Re: Getting this Fatal Trap with heavy network activity

Alexey Sopov wrote: #16 0xc0539c1c in ithread_execute_handlers () #17 0xc0539d66 in ithread_loop () #18 0xc053878f in fork_exit () #19 0xc06ec18c in fork_trampoline () XL I think this was a fatal trap 12 and you may want to try if updating to XL 6.2-STABLE helps. There was some important

Re: Getting this Fatal Trap with heavy network activity

Alexey Sopov wrote: Hi Yesterday and today I've got this fatal trap (kgdb) kldsyms add symbol table from file /usr/obj/usr/src/sys/router/modules/usr/src/sys/modules/netgraph/ether/ng_ether.ko.debug at .text_addr = 0xc77b20a0 .data_addr = 0xc77b4260 .bss_addr

Getting this Fatal Trap with heavy network activity

Hi Yesterday and today I've got this fatal trap (kgdb) kldsyms add symbol table from file /usr/obj/usr/src/sys/router/modules/usr/src/sys/modules/netgraph/ether/ng_ether.ko.debug at .text_addr = 0xc77b20a0 .data_addr = 0xc77b4260 .bss_addr = 0xc77b436c (kgdb) bt #0