Created attachment 150577 [details]
I had a panic while using VirtualBox. core.txt is attached. I have the full core dump available.
I just paste here what seems to be the most relevant part of the backtrace:
#8 0xffffffff809d1bed in sbappendstream_locked (sb=0xfffff8019920dd30,
#9 0xffffffff809d1cac in sbappendstream (sb=0xfffff8019920dd30, m=0x4,
#10 0xffffffff80b118ab in tcp_usr_send (so=0xfffff8019920dba0, flags=0,
m=0x0, nam=0x0, control=<value optimized out>, td=0xfffff800c02074a0)
m is NULL, which is unexpected to the following code:
sbappendstream_locked(struct sockbuf *sb, struct mbuf *m, int flags)
KASSERT(m->m_nextpkt == NULL,("sbappendstream 0"));
KASSERT(sb->sb_mb == sb->sb_lastrecord,("sbappendstream 1"));
Note that the panic occurs on line 641, which corresponds to:
As I use a Git checkout, the Subversion revision doesn't appear: it corresponds to r275576 for both world and kernel.
The panic seems reproducible.
I try to install Debian Wheezy in VirtualBox. The panic occurs as soon as I hit "Continue" on the HTTP proxy dialog (after choosing the package mirror). I'll investigate a bit and report back.
Some more informations:
o VirtualBox is 4.3.20_2 installed from a binary package
o Debian ISO is debian-7.7.0-amd64-netinst.iso
This was fixed in r275955.