Date: Sat, 15 Oct 2016 04:15:27 -0700 From: David Benfell <benfell@parts-unknown.org> To: CeDeROM <cederom@tlen.pl> 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: <4ca2ad36-7160-0ed3-e1ee-2e7347889ad4@parts-unknown.org> In-Reply-To: <CAFYkXjnOZgAX5=-Y99yvtJsgK7cPrkZN3qso8NCUs7BU9JJBOw@mail.gmail.com> 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> <CAFYkXjnOZgAX5=-Y99yvtJsgK7cPrkZN3qso8NCUs7BU9JJBOw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--anpObXmbexTCDApnRPLW3BQdqDPaciSWe
Content-Type: multipart/mixed; boundary="OoeM1mq9vam773fGTIBPC4CvMqD2kqI86"
From: David Benfell <benfell@parts-unknown.org>
To: CeDeROM <cederom@tlen.pl>
Cc: FreeBSD Questions Mailing List <freebsd-questions@freebsd.org>
Message-ID: <4ca2ad36-7160-0ed3-e1ee-2e7347889ad4@parts-unknown.org>
Subject: Re: apparent kernel segfaults and "failed to write core file" even
after putting old kernel back
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>
<CAFYkXjnOZgAX5=-Y99yvtJsgK7cPrkZN3qso8NCUs7BU9JJBOw@mail.gmail.com>
In-Reply-To: <CAFYkXjnOZgAX5=-Y99yvtJsgK7cPrkZN3qso8NCUs7BU9JJBOw@mail.gmail.com>
--OoeM1mq9vam773fGTIBPC4CvMqD2kqI86
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Hi Tomek,
On 10/15/2016 12:11 AM, CeDeROM wrote:
> 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 thinki=
ng
>> 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..
I don't control the host, only my guest. But yes, I hadn't installed any
new files from the software update yet and this had been a working
secondary. I guess I'm looking at a reinstall. **sigh**
Thanks!
--OoeM1mq9vam773fGTIBPC4CvMqD2kqI86--
--anpObXmbexTCDApnRPLW3BQdqDPaciSWe
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCgAGBQJYAg/cAAoJEOoml8Ul4D7Wqz4P/1ZJIp5cJD/CFNEgOHM8t8cx
p/e4ZUyHGwlf9xO5xlMFdEB7qlbCzUWZ5MkzmYPEo13IUP2xG7dsQPNIAO497BI3
BOBSPx837dLNP4zeNKxAKlpUlfr9G9CAaGTdZSFQANSy59omHgOT+JR8VDEseqzf
2Ve4voXoO68uhJtDjjsBs8YAAxpx6IfAOtsT5UsSx29zgxXI8ei0vpF3OvShHiKz
OwLiDw6mjkKReF2ykgRYBaag81BBLXVypbuAJxsU0Vsrage9DAM9qWaNIJiVn6Tr
cnfBxWMkAgesnGlTAyFmLCNrMwuVnx6ZGTphDcib0/zhIJSnM28u774oJpfVx8P7
6EvBkRn0xURR81Fxwnsxiht2jSe5cX8wV6AaRB9UjphRa7JtJPOVSh4vB2BkfmaX
1oIqCIOBitJNJ5zW+5XysRdylG6zEoIZoE/QvPGrl2tKDyGZvwP/sO9obT2PHCq8
JTD3Crxm0BBJa15EFiLy9IvGsK5lfvi8IpFe9uKxfT/yNTx/MAE8q1uiWHA+kiyy
6tJG38gT8G5dYHQIJXKaxYdgRrJWWi+64RfVJc1WBPq3kehZLdbobnMqUiJi1dzz
oNLjhf9vucBBBAjVIhIyZuLs2X/TFdb7GnOuaNpgQs0GHWlECJ78TOyTPMPcrsEO
28yfVrv3Y+f5Q5nMfTQ3
=7aPV
-----END PGP SIGNATURE-----
--anpObXmbexTCDApnRPLW3BQdqDPaciSWe--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4ca2ad36-7160-0ed3-e1ee-2e7347889ad4>