Date: Sat, 15 Oct 2016 09:11:29 +0200 From: CeDeROM <cederom@tlen.pl> To: David Benfell <benfell@parts-unknown.org> Cc: FreeBSD Questions Mailing List <freebsd-questions@freebsd.org> Subject: Re: apparent kernel segfaults and "failed to write core file" even after putting old kernel back Message-ID: <CAFYkXjnOZgAX5=-Y99yvtJsgK7cPrkZN3qso8NCUs7BU9JJBOw@mail.gmail.com> In-Reply-To: <b830fc1c-2339-8db7-41ef-7bcf90647223@parts-unknown.org> References: <0ef6721d-4b53-e3a2-55d7-66b997818e80@parts-unknown.org> <CAFYkXj=9RD-PDYE3mo5BgL2reikoVeJYoO-e=5VnSm8Pm9rGzw@mail.gmail.com> <b830fc1c-2339-8db7-41ef-7bcf90647223@parts-unknown.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Oct 15, 2016 at 3:40 AM, David Benfell
<benfell@parts-unknown.org> wrote:
> I managed to get an original 10.3 release kernel on the VPS and tried
> booting it. I get the same result. It's been a few days, so I'm thinking
> if there was a hardware failure of the VPS, other users would have
> encountered it.
But exactly the same 10.3 worked for you well before? The same
configuration, modules, sysctl?
Try adding new machines (add new next to another to use different
memory/storage space) with the same configuration exactly the same as
previously worked fine (10.{2,3}-RELEASE?), so you can track whether
this is a hardware or software problem.. mayabe you got into a
corrupted memory/storage region or something changed since
10.3-RELEASE that breaks VM compatibility..
Good luck! :-)
Tomek
--
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFYkXjnOZgAX5=-Y99yvtJsgK7cPrkZN3qso8NCUs7BU9JJBOw>