On 15 November 2017 at 10:58, Conrad Meyer <c...@freebsd.org> wrote:
> Hi Wolfram,
> Looks like the same issue as
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223531 .
thanks for the hint. Do you know which commit may broke the driver? Is
there any patch or workaround?
I do not have access to the physical machine, only full root access to
the guest. I don't want to bother with the cloud provider, I'm happy
that they offer FreeBSD at all as a default installation.
> On Wed, Nov 15, 2017 at 1:31 AM, Wolfram Schneider <wo...@freebsd.org> wrote:
>> I have a virtual machine running with FreeBSD 11-stable at a cloud
>> provider. It runs fine. I tried to upgrade to FreeBSD 12-current and
>> the kernel panics at boot time with:
>> make_dev_alias_v bad si_name (error=22) si_name=vtcon/
>> and hangs. Lucky, I still can boot from kernel.old and bring the machine up.
>> any idea whats wrong here?
Wolfram Schneider <wo...@freebsd.org> https://wolfram.schneider.org
firstname.lastname@example.org mailing list
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"