From owner-freebsd-current@freebsd.org Fri Dec 1 07:53:03 2017 Return-Path: Delivered-To: freebsd-current@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 25CA6DEF0FC; Fri, 1 Dec 2017 07:53:03 +0000 (UTC) (envelope-from agapon@gmail.com) Received: from mail-lf0-f54.google.com (mail-lf0-f54.google.com [209.85.215.54]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BCDAC750F0; Fri, 1 Dec 2017 07:53:02 +0000 (UTC) (envelope-from agapon@gmail.com) Received: by mail-lf0-f54.google.com with SMTP id f18so10714801lfg.8; Thu, 30 Nov 2017 23:53:02 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=GLZUVxOEDKVCCpqyxSvojZQwJrDB8VdXbktkBa1QxoI=; b=B8PxrjN4FmvRJc5WqPPh5rfXLOW3UQcUqZAxniPobSHgqFlT8RF31ALc8kxUcZJgkb X4BNEZNYyPqX9jylwQdmI4O5dy0lPukNmK6+qJnqC8Cy7lQszd2orSUD/wrN3xJKg14M 65nR/r+Sh3pfl86zjcEr1toBEm8ZIxrB10Z2N3B+hciA/YR4ONYm8ODTe678ZeZf8toR 4DX4jZZRzp304fTIVG6uRusXNsj7jIIptHlXpAYSwSh6aTn4YZopKknuSqCdjJ2WtWp+ 6/ap19UJ8cxG7nKgt1IYl5/oBZaSO0gQoi438LmrOu80k6Z8zgG49slGAqCJQ2fht5j2 n6+Q== X-Gm-Message-State: AJaThX7gudVVRpOjjnzQy1B71uC8+/d2UojaonxWUUDX+TC6fHRGcMxj VtHKYs1dnxw8UIGjxYPVoweDKDK/QnI= X-Google-Smtp-Source: AGs4zMY/1zXKPfMDCM043B5/26d5nRUZ0YINZJrus1R8ZyG65LC8NNl8z8UmJflINWSOcNDmxUVmNg== X-Received: by 10.46.2.197 with SMTP id y66mr4430199lje.113.1512114281788; Thu, 30 Nov 2017 23:44:41 -0800 (PST) Received: from [192.168.0.88] (east.meadow.volia.net. [93.72.151.96]) by smtp.googlemail.com with ESMTPSA id x20sm1165813ljd.88.2017.11.30.23.44.40 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 30 Nov 2017 23:44:40 -0800 (PST) Subject: Re: dmesg -a shows "Failed to fully fault in a core file segment at VA" examples, anything to worry about? To: Mark Millard , FreeBSD Current , freebsd-hackers References: <4D8DB370-AC0F-40F8-B5FC-213D5A3409FD@dsl-only.net> From: Andriy Gapon Message-ID: Date: Fri, 1 Dec 2017 09:44:39 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: <4D8DB370-AC0F-40F8-B5FC-213D5A3409FD@dsl-only.net> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Dec 2017 07:53:03 -0000 On 30/11/2017 23:04, Mark Millard wrote: > 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. The messages are produced if there is a problem while writing a core file. So, they can appear only if (after) a process crashed. -- Andriy Gapon