On Wed, Dec 16, 2015 at 08:47:02PM +0100, Alexander Bluhm wrote:
> It happened after running the ARP regression test.  I cannot reproduce
> it by running the test.  Perhaps I have to wait for the arp timer.

Reproduceable by waiting for the arp timeout, then it crashes.
I will investigate.

bluhm

root@q70:.../~# netstat -nrf inet        
Routing tables

Internet:
Destination        Gateway            Flags   Refs      Use   Mtu  Prio Iface
10.188.70/24       10.188.70.70       UC         0        1     -     4 vio0 
10.188.70.17       fe:e1:ba:d0:d5:6d  UHLS       0        3     -     8 vio0 
10.188.70.70       70:5f:ca:21:8d:70  UHLl       0       14     -     1 vio0 
10.188.70.255      10.188.70.70       UHb        0        0     -     1 vio0 
10.188.211/24      10.188.211.70      UC         0        0     -     4 vio1 
10.188.211.70      70:5f:ca:21:8d:80  UHLl       0        1     -     1 vio1 
10.188.211.255     10.188.211.70      UHb        0        0     -     1 vio1 
10.188.212/24      10.188.211.71      UGS        0        0     -     8 vio1 
10.188.213/24      10.188.211.71      UGS        0        0     -     8 vio1 
10.188.217/24      127.0.0.1          UGRS       0        0 32768     8 lo0  
10.188.218/24      127.0.0.1          UGRS       0        0 32768     8 lo0  
127/8              127.0.0.1          UGRS       0        0 32768     8 lo0  
127.0.0.1          127.0.0.1          UHl        0        0 32768     1 lo0  
224/4              127.0.0.1          URS        0        0 32768     8 lo0  
root@q70:.../~# panic: kernel diagnostic assertion "!ISSET(rt->rt_flags, 
RTF_UP)" failed: file "../../../../net/route.c", line 444
Stopped at      Debugger+0x9:   leave
   TID    PID    UID     PRFLAGS     PFLAGS  CPU  COMMAND
Debugger() at Debugger+0x9
panic() at panic+0xfe
__assert() at __assert+0x25
rtfree() at rtfree+0x11e
rtable_delete() at rtable_delete+0x5d
rt_delete() at rt_delete+0x6e
rtdeletemsg() at rtdeletemsg+0x2d
arptfree() at arptfree+0x4f
arptimer() at arptimer+0x63
softclock() at softclock+0x315
softintr_dispatch() at softintr_dispatch+0x72
Xsoftclock() at Xsoftclock+0x1f
--- interrupt ---
end of kernel
end trace frame: 0x2710, count: 3
0x8:
http://www.openbsd.org/ddb.html describes the minimum info required in bug
reports.  Insufficient info makes it difficult to find and fix bugs.
ddb> 

Reply via email to