Re: panic route.c:565

Sam Leffler wrote:

> Any chance you can get a stack trace the next time this happens?  The LOR by 
> itself is hard to go from...

Hi Sam,

i get a slightly different LOR.

lock order reversal
  1st 0xc2dd6c90 rtentry (rtentry) _at_ /space/src/sys/net/route.c:182
  2nd 0xc2d4887c radix node head (radix node head) _at_ 
/space/src/sys/net/route.c:544
Stack backtrace:
backtrace(c0681530,c2d4887c,c06870aa,c06870aa,c0687100) at backtrace+0x17
witness_lock(c2d4887c,8,c0687100,220,1) at witness_lock+0x672
_mtx_lock_flags(c2d4887c,0,c0687100,220,cf428938) at _mtx_lock_flags+0xba
rtrequest1(1,cf428944,cf428998,0,c2eb9eb0) at rtrequest1+0x59
rtrequest(1,c2eb9eb0,c2eb9eb0,cf42899c,405) at rtrequest+0x4a
in6_ifloop_request(1,c2eb9e00,0,c2eb9e00,40) at in6_ifloop_request+0x76
in6_ifaddloop(c2eb9e00,0,c2eb9e00,0,cf428cbc) at in6_ifaddloop+0x50
in6_ifinit(c2ce7408,c2eb9e00,cf428c64,1,c04e092b) at in6_ifinit+0x147
in6_update_ifa(c2ce7408,cf428c54,0,0,cf428af4) at in6_update_ifa+0x500
in6_control(c2ea2800,8078691a,cf428c54,c2ce7408,c2e0c130) at 
in6_control+0x731
ifioctl(c2ea2800,8078691a,cf428c54,c2e0c130,c2e9e7fc) at ifioctl+0x1c8
soo_ioctl(c2e02f68,8078691a,cf428c54,c2e06a00,c2e0c130) at soo_ioctl+0x19c
ioctl(c2e0c130,cf428d10,c069ca3f,3ed,3) at ioctl+0x475
syscall(2f,2f,2f,8097785,8078691a) at syscall+0x2c0
Xint0x80_syscall() at Xint0x80_syscall+0x1d
--- syscall (54), eip = 0x2828768f, esp = 0xbfbff4ec, ebp = 0xbfbff518 ---


hth,
flo