Date: Tue, 26 Aug 2008 17:04:29 -0600 From: James Gritton <jamie@gritton.org> To: FreeBSD virtualization mailing list <freebsd-virtualization@freebsd.org> Cc: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> Subject: Re: panic in vimage/jamie_jail_set Message-ID: <48B48BFD.4050108@gritton.org> In-Reply-To: <20080824141835.K66593@maildrop.int.zabbadoz.net> References: <20080824141835.K66593@maildrop.int.zabbadoz.net>
next in thread | previous in thread | raw e-mail | index | archive | help
I haven't seen the panic you describe, but on a jail_set_vimage integrated from the latest vimage code, I get a similar idle network panic. This happens in tcp_hc_purge(), which clearly expected a struct vnet pointer as its argument, but is only ever called with NULL. It seems reasonable to pass tcp_hc_init's curvnet as the argument, but I don't know if there are referencing issues. - Jamie Bjoern A. Zeeb wrote: > Hi, > > I had a jamie_jail_set kernel running from > db> x/s version > version: FreeBSD 8.0-CURRENT #0: Fri Aug 15 10:01:11 UTC 2008 ... > > and it paniced while standing idle. I am not sure if that had been > fixed in the vimage branch but not integrated into jamie_jail_set or > if this was a different issue to what kris had seen? > > Unfortunately the console hasn't been to reliable, so this is what I > have: > > panic: in ../../../netinet/tcp_usrreq.c:1281 tcp_ctloutput()^M^@ > vnet=0xc7067000 curvnet=0^M^@ > cpuid = 0^M^@ > KDB: enter: panic^M^@ > [thread pid 852 tid 100051 ]^M^@ > Stopped at kdb_enter+0x3a: movl $0,kdb_why^M^@ > > Tracing pid 852 tid 100051 td 0xc74f5d20 > kdb_enter(c0b04531,c0b04531,c0b05c88,c6f4b59c,0,...) at kdb_enter+0x3a > panic(c0b05c88,c0b1cb7f,501,c0a9f8a2,c7067000,...) at panic+0x12c > tcp_ctloutput(c7546c60,c6f4b744,c07f3c0a,c7546c60,0,...) at > tcp_ctloutput+0x5e > sosetopt(c7546c60,c6f4b744,1,0,c73b6400,...) at sosetopt+0x3d > nfs_connect(c7467000,c7670000,c0b20436,21d,c7670044,...) at > nfs_connect+0x1b9 > nfs_reconnect(c7670044,0,c0b20436,2e2,0,...) at nfs_reconnect+0x15e > nfs_request(c725bb84,c7379400,4,c74f5d20,c7547900,...) at > nfs_request+0x6c3 > nfs3_access_otw(c7547900,0,c0b20ac9,180,0,...) at nfs3_access_otw+0xde > nfs_access(c6f4b9cc,c6f4b9b4,c077bed7,c74f5d20,c6f4ba18,...) at > nfs_access+0x15e > VOP_ACCESS_APV(c0bf16a0,c6f4b9cc,c6f4b954,0,c6f4b95c,...) at > VOP_ACCESS_APV+0xa5 > nfs_lookup(c6f4ba78,c6f4ba78,5000044,80000,c725bb84,...) at > nfs_lookup+0xcb > VOP_LOOKUP_APV(c0bf16a0,c6f4ba78,c0b0fd3c,1b0,c6f4bb9c,...) at > VOP_LOOKUP_APV+0xa5 > lookup(c6f4bb84,c0b0fd3c,d8,c0,c7547e2c,...) at lookup+0x57e > namei(c6f4bb84,c6f4bb24,60,0,c74f5d20,...) at namei+0x44b > kern_statat(c74f5d20,0,ffffff9c,804ec77,0,...) at kern_statat+0x64 > kern_stat(c74f5d20,804ec77,0,c6f4bc18,6b,...) at kern_stat+0x36 > stat(c74f5d20,c6f4bcf8,8,c0b0a981,c0bd7400,...) at stat+0x2f > syscall(c6f4bd38) at syscall+0x2a3 > Xint0x80_syscall() at Xint0x80_syscall+0x20 > --- syscall (188, FreeBSD ELF32, stat), eip = 0x28163c6b, esp = > 0xbfbfea3c, ebp = 0xbfbfed38 --- > > /bz >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?48B48BFD.4050108>