From: Russell Coker <russell@coker.com.au>
To: Nicolas Iooss <nicolas.iooss@m4x.org>
Cc: SElinux list <selinux@vger.kernel.org>,
Laurent Bigonville <bigon@debian.org>
Subject: Re: semodule -i and load_policy coredumps on version 3.0 - not latest GIT
Date: Wed, 22 Apr 2020 20:49:10 +1000 [thread overview]
Message-ID: <1991878.H4qNpjkt8I@liv> (raw)
In-Reply-To: <2529366.HMiiFnPMKa@liv>
On Tuesday, 21 April 2020 2:01:45 PM AEST Russell Coker wrote:
> After the reboot I could not reproduce it on saved snapshots of the VM in
> question dating back to when I had previously had problems. I conclude that
> rebooting the hardware solved the problem.
>
> The problem was either an issue of failing hardware (I am running memtest86+
> right now) or hostile action. When testing for issues with libsepol I got
Memtest86+ has proven that the system in question had a damaged motherboard,
any time when any DIMM socket other than socket 1 was in use Memtest86+ would
lock up solid in less than 7 seconds (for reference a complete Memtest86+ run
was successful at the time the system was deployed). The system is on the e-
waste pile and I don't expect to see such semodule problems again.
How the system in question managed to boot Linux and run multiple VMs while
Memtest86+ crashed so soon remains a mystery to me.
--
My Main Blog http://etbe.coker.com.au/
My Documents Blog http://doc.coker.com.au/
prev parent reply other threads:[~2020-04-22 10:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-14 0:29 semodule -i and load_policy coredumps on version 3.0 - not latest GIT Russell Coker
2020-04-14 17:27 ` Nicolas Iooss
2020-04-15 17:17 ` Russell Coker
2020-04-21 4:01 ` Russell Coker
2020-04-22 10:49 ` Russell Coker [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1991878.H4qNpjkt8I@liv \
--to=russell@coker.com.au \
--cc=bigon@debian.org \
--cc=nicolas.iooss@m4x.org \
--cc=selinux@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.