Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 11 Sep 2016 21:50:39 +0000
From:      twilight <pipfstarrd@openmailbox.org>
To:        Matthew Pounsett <matt@conundrum.com>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: freebsd-update not updating kernel?
Message-ID:  <7e471e4c-2c11-bbe2-7549-18bd4b16471d@openmailbox.org>
In-Reply-To: <CAAiTEH-DC8riFyroP-kMuptXut5-CJLk9M52vd9kH9FJ_y=8GQ@mail.gmail.com>
References:  <CAAiTEH-DC8riFyroP-kMuptXut5-CJLk9M52vd9kH9FJ_y=8GQ@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
> It looks to me from what I'm pasting below as if there is a kernel out
> there somewhere for 9.3-RELEASE-p45, but freebsd-update is
unable/unwilling
> to fetch it.  I've also got Virtualbox segfaulting, which frequently
> happens to me mid-upgrade when there's a kernel/package mismatch.
>
> Does anyone have an explanation for what's happening here?
>
> % uname -a
> FreeBSD localhost 9.3-RELEASE-p43 FreeBSD 9.3-RELEASE-p43 #0: Sat May 28
> 00:19:32 UTC 2016
> root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC
>  amd64

Consider checking freebsd-version(1) output as:

> The following options are available:
> -k          Print the version and patch level of the installed kernel.
>   Unlike uname(1), if a new kernel has been installed but the system
has not yet rebooted, freebsd-version will print the version and patch
level of the new kernel.

And as you get from this quote, the following:

> % lsof >/dev/null
> lsof: WARNING: compiled for FreeBSD release 9.3-RELEASE-p45; this is
> 9.3-RELEASE-p43.

might occur if you forgot to reboot.

Yeah, it's a stupid advice and you've probably rebooted, but just in case.
-- 
Cheers~

PGP key fingerprint:
07B3 2177 3E27 BF41 DC65  CC95 BDA8 88F1 E9F9 CEEF

You can retrieve my public key at pgp.mit.edu.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7e471e4c-2c11-bbe2-7549-18bd4b16471d>