From owner-freebsd-questions@freebsd.org  Thu Jun 17 19:57:21 2021
Return-Path: <owner-freebsd-questions@freebsd.org>
Delivered-To: freebsd-questions@mailman.nyi.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.nyi.freebsd.org (Postfix) with ESMTP id 261CC65D60F
 for <freebsd-questions@mailman.nyi.freebsd.org>;
 Thu, 17 Jun 2021 19:57:21 +0000 (UTC)
 (envelope-from rfg@tristatelogic.com)
Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com
 [69.62.255.118])
 by mx1.freebsd.org (Postfix) with ESMTP id 4G5Xrw3lf7z3nR9
 for <freebsd-questions@freebsd.org>; Thu, 17 Jun 2021 19:57:20 +0000 (UTC)
 (envelope-from rfg@tristatelogic.com)
Received: by segfault.tristatelogic.com (Postfix, from userid 1237)
 id A3FE84E680; Thu, 17 Jun 2021 12:57:19 -0700 (PDT)
From: "Ronald F. Guilmette" <rfg@tristatelogic.com>
To: freebsd-questions@freebsd.org
Subject: Re: Safety harnesses (was: Is a successful call to write(2) atomic?)
In-Reply-To: <a17cf47d-5aef-1623-46da-51c83054f083@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <36521.1623959839.1@segfault.tristatelogic.com>
Date: Thu, 17 Jun 2021 12:57:19 -0700
Message-ID: <36522.1623959839@segfault.tristatelogic.com>
X-Rspamd-Queue-Id: 4G5Xrw3lf7z3nR9
X-Spamd-Bar: /
Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none;
 spf=pass (mx1.freebsd.org: domain of rfg@tristatelogic.com designates
 69.62.255.118 as permitted sender) smtp.mailfrom=rfg@tristatelogic.com
X-Spamd-Result: default: False [0.47 / 15.00]; ARC_NA(0.00)[];
 RBL_DBL_DONT_QUERY_IPS(0.00)[69.62.255.118:from];
 FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[];
 R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain];
 TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[tristatelogic.com];
 NEURAL_SPAM_MEDIUM(0.81)[0.808]; RCPT_COUNT_ONE(0.00)[1];
 SPAMHAUS_ZRD(0.00)[69.62.255.118:from:127.0.2.255];
 NEURAL_SPAM_SHORT(0.96)[0.965]; NEURAL_HAM_LONG(-1.00)[-1.000];
 RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[];
 R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+];
 ASN(0.00)[asn:14051, ipnet:69.62.128.0/17, country:US];
 MAILMAN_DEST(0.00)[freebsd-questions];
 SUBJECT_HAS_QUESTION(0.00)[]
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Jun 2021 19:57:21 -0000

In message <a17cf47d-5aef-1623-46da-51c83054f083@gmail.com>, 
Graham Perrin <grahamperrin@gmail.com> wrote:

>The surprise, to me, was losing fifty-something seconds' worth of data 
>in a kernel panic situation...

In an ideal universe, the kernel never panics.

Mine however still does from time to time.

I have been informed that this is attributable to me continuing to use an
otherwise perfectly servicable AMD graphics card that the X maintainer
has elected to no longer support.

I have suggested that there might possibly be some more graceful failure
mode than a kernel panic in response to some unhandled condition, but to
no avail.

(Hardware upgrade has been pednding on my end for more than a year.  I have
all of the necessary parts... new motherboard, new CPU/APU and new memory...
however I just never seem to find the time.)


Regards,
rfg