Re: panic: already on hash list

[Matthew Dillon <dillon@xxxxxxxxxxxxxxxxxxxx>]

:Hi.
:Caught this panic while playing with my build box.  I don't know the exact
:moment when it panicked, as the monitor was connected to another box, but
:here's what I was doing before the panic anyway:
:
:...
:
:Probably this panic only occurs on SMP machines, but I'd like to make sure
:it won't happen on the router box before upgrading it.
:
:The kernel dump is uploaded as ~y0netan1/crash/{kernel,vmcore}.11 on my
:leaf account, in case someone is interested.
:
:Thanks.
:    at /home/source/dragonfly/R2_0/src/sys/kern/kern_shutdown.c:375
:#2  0xc0198f80 in panic (fmt=0xc02e2386 "already on hash list")
:    at /home/source/dragonfly/R2_0/src/sys/kern/kern_shutdown.c:800
:#3  0xc01ff460 in in_pcbinsconnhash (inp=0xd316c260)
:    at /home/source/dragonfly/R2_0/src/sys/netinet/in_pcb.c:1053
:#4  0xc02124d7 in tcp_connect_oncpu (tp=0xd316c320, sin=0xd7ef3d80, 
:    if_sin=0xd316c260)
:    at /home/source/dragonfly/R2_0/src/sys/netinet/tcp_usrreq.c:917
:#5  0xc02126e1 in tcp_connect (tp=0xd316c320, nam=<value optimized out>, 
:    td=<value optimized out>)
:    at /home/source/dragonfly/R2_0/src/sys/netinet/tcp_usrreq.c:1036

    Definitely one for Seph.  The permissions are set properly on your
    crash dump so Seph should be able to dive into it with kgdb on leaf.

					-Matt
					Matthew Dillon 
					<dillon@backplane.com>