Date: Sat, 6 Sep 2008 19:51:03 -0500 From: Alec Kloss <alec-keyword-freebsd.befd64@SetFilePointer.com> To: freebsd-questions@freebsd.org Subject: Panic in IPv4 multicast code Message-ID: <20080907005103.GZ53100@hamlet.SetFilePointer.com>
next in thread | raw e-mail | index | archive | help
--Q7MaAb+MMjzLKrXy Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I've been playing around with some multicast stuff with rtpdump=20 and I have what appears to be a 100%-repeatable panic on 7.1-PRERELEASE (csupped on 20080905): (kgdb) bt #0 doadump () at pcpu.h:196 #1 0xc078f8c7 in boot (howto=3D260) at /usr/src/sys/kern/kern_shutdown.c:4= 18 #2 0xc078fb89 in panic (fmt=3DVariable "fmt" is not available. ) at /usr/src/sys/kern/kern_shutdown.c:572 #3 0xc07c406e in propagate_priority (td=3D0xc50c7000) at /usr/src/sys/kern/subr_turnstile.c:222 #4 0xc07c4f38 in turnstile_wait (ts=3D0xc482edc0, owner=3D0xc50c7000, queu= e=3DVariable "queue" is not available. ) at /usr/src/sys/kern/subr_turnstile.c:739 #5 0xc07825be in _mtx_lock_sleep (m=3D0xc0c4884c, tid=3D3300787856, opts= =3D0, file=3D0x0, line=3D0) at /usr/src/sys/kern/kern_mutex.c:420 #6 0xc087051f in ip_output (m=3D0xc4b7f600, opt=3D0x0, ro=3D0xe7155b20, fl= ags=3D34, imo=3D0x0, inp=3D0x0) at /usr/src/sys/netinet/ip_output.c:305 #7 0xc07e74e5 in sosend_generic (so=3D0xc4caf340, addr=3D0xc49b18e0, uio= =3D0xe7155be8, top=3D0xc4b7f600, control=3D0x0, flags=3D0, td=3D0xc4be0690) at /usr/src/sys/kern/uipc_socket.c:1246 #8 0xc07e2fff in sosend (so=3D0xc4caf340, addr=3D0xc49b18e0, uio=3D0xe7155= be8, top=3D0x0, control=3D0x0, flags=3D0, td=3D0xc4be0690) at /usr/src/sys/kern/uipc_so= cket.c:1292 #9 0xc07e9d86 in kern_sendit (td=3D0xc4be0690, s=3D4, mp=3D0xe7155c64, fla= gs=3D0, control=3D0x0, segflg=3DUIO_USERSPACE) at /usr/src/sys/kern/uipc_syscalls.c:805 #10 0xc07ecfd1 in sendit (td=3D0xc4be0690, s=3D4, mp=3D0xe7155c64, flags=3D= 0) at /usr/src/sys/kern/uipc_syscalls.c:742 #11 0xc07ed0e8 in sendto (td=3D0xc4be0690, uap=3D0xe7155cfc) at /usr/src/sys/kern/uipc_syscalls.c:857 #12 0xc0aa14a5 in syscall (frame=3D0xe7155d38) at /usr/src/sys/i386/i386/tr= ap.c:1090 #13 0xc0a87920 in Xint0x80_syscall () at /usr/src/sys/i386/i386/exception.s= :255 #14 0x00000033 in ?? () (kgdb) According to the comments at kern/subr_turnstile.c:222 I'm supposed to be looking for another thread to blame for the issue... does anyone have any thoughts about how to go about doing that? Interestingly, I have another similarly-configured (but radically different hardware) system that seems to do this okay. That system is currently running some older version of RELENG_7, but I'm in process updating it to the same version as the troublesome system. =20 The troublesome system is using the em driver, the working system is using rl, if there's something about the NIC that's involved. --=20 Alec Kloss alec@SetFilePointer.com IM: angryspamhater@yahoo.com PGP key at http://pgp.mit.edu:11371/pks/lookup?op=3Dget&search=3D0xA241980E "No Bunny!" -- Simon, http://wiki.adultswim.com/xwiki/bin/Frisky+Dingo/Simon --Q7MaAb+MMjzLKrXy Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFIwyV32s33paJBmA4RAn2pAJ4uEkF7ty2zXDmTL+IXeMXE9uoKRwCfUBeR 2C0lt5VGztk9pf6f/eTKS88= =B0pQ -----END PGP SIGNATURE----- --Q7MaAb+MMjzLKrXy--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080907005103.GZ53100>