From owner-freebsd-hackers@freebsd.org Thu Nov 30 21:11:16 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C31EEDBAB1F for ; Thu, 30 Nov 2017 21:11:16 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-136.reflexion.net [208.70.210.136]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 74E6B7604F for ; Thu, 30 Nov 2017 21:11:15 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 16592 invoked from network); 30 Nov 2017 21:04:29 -0000 Received: from unknown (HELO rtc-sm-01.app.dca.reflexion.local) (10.81.150.1) by 0 (rfx-qmail) with SMTP; 30 Nov 2017 21:04:29 -0000 Received: by rtc-sm-01.app.dca.reflexion.local (Reflexion email security v8.40.3) with SMTP; Thu, 30 Nov 2017 16:04:29 -0500 (EST) Received: (qmail 3999 invoked from network); 30 Nov 2017 21:04:29 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 30 Nov 2017 21:04:29 -0000 Received: from [192.168.1.25] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id F133DEC9591; Thu, 30 Nov 2017 13:04:28 -0800 (PST) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: dmesg -a shows "Failed to fully fault in a core file segment at VA" examples, anything to worry about? Message-Id: <4D8DB370-AC0F-40F8-B5FC-213D5A3409FD@dsl-only.net> Date: Thu, 30 Nov 2017 13:04:28 -0800 To: FreeBSD Current , freebsd-hackers X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Nov 2017 21:11:16 -0000 Basic context: # uname -apKU FreeBSD FBSDHUGE 12.0-CURRENT FreeBSD 12.0-CURRENT r326192M amd64 = amd64 1200054 1200054 During an experiment with a "poudriere bulk -a" I've noticed the following 2 message sequences: > Failed to fully fault in a core file segment at VA 0x80064b000 with = size 0x1000 to be written at offset 0x2e000 for process conftest > pid 26417 (conftest), uid 0: exited on signal 11 (core dumped) > Nov 30 03:37:25 FBSDHUGE kernel: Failed to fully fault in a core file = segment at VA 0x80064b000 with size 0x1000 to be written at offset = 0x2e000 for process conftest and: > Failed to fully fault in a core file segment at VA 0x80064c000 with = size 0x1000 to be written at offset 0x2d000 for process a.out > pid 65189 (a.out), uid 0: exited on signal 11 (core dumped) > Nov 30 04:58:23 FBSDHUGE kernel: Failed to fully fault in a core file = segment at VA 0x80064c000 with size 0x1000 to be written at offset = 0x2d000 for process a.out (The console only shows the two non-timestampted "Failed to . . ." messages.) I note that VA+offset =3D=3D 0x800679000 in both cases. This suggests a common cause associated with that spot in some way. The messages seem to be considered non-fatal at the system level, although the processes are getting signal 11. It is not clear to me if the signal 11's are consequences, causes, or just happen to be associated. So far I've only had the 2 examples as of: # poudriere status SET PORTS JAIL BUILD STATUS QUEUE BUILT = FAIL SKIP IGNORE REMAIN TIME LOGS - default FBSDFSSDjail 2017-11-29_03h45m33s parallel_build 27777 14609 = 156 2015 136 10861 33:09:51 = /usr/local/poudriere/data/logs/bulk/FBSDFSSDjail-default/2017-11-29_03h45m= 33s More context: FreeBSD is running under a Windows 10 Pro Hyper-V virtual machine. =3D=3D=3D Mark Millard markmi at dsl-only.net