Date: Wed, 6 Aug 2014 06:19:32 +0300 From: Konstantin Belousov <kostikbel@gmail.com> To: Bryan Drewery <bdrewery@FreeBSD.org> Cc: current@FreeBSD.org Subject: Re: r269147: NULL mp in getnewvnode() via kern_proc_filedesc_out() Message-ID: <20140806031932.GE93733@kib.kiev.ua> In-Reply-To: <53E1975D.4010703@FreeBSD.org> References: <53E1975D.4010703@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--bG3OVe1RvEtjCM5X Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Aug 05, 2014 at 09:47:57PM -0500, Bryan Drewery wrote: > Has anyone else encountered this? Got it while running poudriere. >=20 > > NULL mp in getnewvnode() > > [...] > > vn_fullpath1() at vn_fullpath1+0x19d/frame 0xfffffe1247d8e540 > > vn_fullpath() at vn_fullpath+0xc1/frame 0xfffffe1247d8e590 > > export_fd_to_sb() at export_fd_to_sb+0x489/frame 0xfffffe1247d8e7c0 > > kern_proc_filedesc_out() at kern_proc_filedesc_out+0x234/frame 0xfffffe= 1247d8e840 > > sysctl_kern_proc_filedesc() at sysctl_kern_proc_filedesc+0x84/frame 0xf= ffffe1247d8e900 > > sysctl_root_handler_locked() at sysctl_root_handler_locked+0x68/frame 0= xfffffe1247d8e940 > > sysctl_root() at sysctl_root+0x18e/frame 0xfffffe1247d8e990 > > userland_sysctl() at userland_sysctl+0x192/frame 0xfffffe1247d8ea30 > > sys___sysctl() at sys___sysctl+0x74/frame 0xfffffe1247d8eae0 > > amd64_syscall() at amd64_syscall+0x25a/frame 0xfffffe1247d8ebf0 > > Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfffffe1247d8ebf0 >=20 > Unfortunately I have no dump as the kmem was too large compared to my=20 > swap, and I didn't get to the console before some of the text was=20 > overwritten. Perhaps it will hit it again soon after reboot and I'll get= =20 > a core. "NULL mp in getnewvnode()" is only the printf(), it is not a panic or KASSERT. The event does not stop the machine, nor it prints the backtrace. You mentioned that you was unable to dump, so did the system paniced ? Without full log of the panic messages and backtrace, it is impossible to start guessing what the problem is. That said, the printf seemingly outlived its usefulness. --bG3OVe1RvEtjCM5X Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBAgAGBQJT4Z7DAAoJEJDCuSvBvK1BkcwP/A4MKPktAe1B3Md2nxOjSjjA X8FxCRdOsbhdLiiFsmn2GuV2bm8DZHZUH+fzM/m4pDkF09OJ3OKLzmdKE8fp6ZVG ss4CuxklBaC8O+UYZ7oy/cfwIosXlm+iaDwGDp39Uh1XMB5FhGx23x5oABxG7DTW FLbh0LAw9uLAvJv82m1Bi3LDj3EzQCo5m8s/MfbvPj+6PpEVNNUsxc8OZYZ6awUl HsG27dZPBu+XqutKxcJAzpc5CW8owQfnFV8tmXn4rcBgKT5RglJ/JT+L0SbdrOfd 0zgPVFn9pyKcn0QGU6W47GBGTk6i93OfPHyBIB7f0AOqd0w4W1ibyPagy3snwd4g dBAsMEtWxuBidQ5dbCnUGb6SrqhQqHGF6jcUQjEB1Adqt/yR51kHGN4HlvLITfdD f61B68qxRwxikk4pBjpKv3cCem4LdlMQBq6nztblHY0ZbCPym/O3/R9hA/YteBwR 76s5my79ioxj+2p9pk1LLmdIHUQQWaU6K2OJslAM0neGDj4T+1JBNgwmyRozHoxB 9Fwe5ZBNpR4JyN4KekWd0wsC/Hw8X+HQeUpe8WO3vqyr3WdKimsiFtxFY0ZEdjdb 4Qpvp6sU8In2sFODnoJvWeCt5znafX29Eh6stwvhnntjClNF899yatdMYnVUBr9m GrBndcWbZLNDP7RRHSsn =vL2Z -----END PGP SIGNATURE----- --bG3OVe1RvEtjCM5X--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140806031932.GE93733>