When multiple default routes are managed by a dynamic routing scheme, as in.routed, the system may panic with the following stack:
000002a1004063b1 ire_round_robin+0x9c(60001ac1778, 0, 2a100406d50, deadbeefdeadbeef, 0, 60001ac1780) 000002a100406481 ire_ftable_lookup+0x2b8(819911c1, 60001bd3bf0, 0, a, 0, 2a100406f88) 000002a1004065c1 ip_newroute+0x350(302882bde48, 60002535320, 0, 0, 0, 600177fcf90) 000002a1004067a1 ip_output+0x1d84(302527cd400, 600177fcf90, 1, 301596d6c80, 0, 302527cd400) 000002a100406891 tcp_rput_data+0x39e8(40000, 2018, 2018, 70461800, 302527cd880, 5c00) 000002a100406a81 squeue_enter_chain+0x1d0(600004b1d00, 30129545580, 302527cd400 , 2561caae75d0, 1, 1) 000002a100406b31 ip_input+0xa50(60000822728, 0, 0, 8192e41f, 7bb3cc00, 30129545580) 000002a100406c41 putnext+0x3ec(60000c577e8, 60000c57540, 60000c57730, 30129545580, 2a1004074f0, 0) : : |
The following error message is displayed:
BAD TRAP: type=31 rp=2a100406b10 addr=deadbeefdeadbf34 mmu_fsr=0 |
Workaround: In feasible environments, manage the default routes through routing schemes as /etc/defaultrouter.