Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 15 Mar 2020 06:16:59 +0000
From:      bugzilla-noreply@freebsd.org
To:        virtualization@FreeBSD.org
Subject:   [Bug 236989] AWS EC2 lockups "Missing interrupt"
Message-ID:  <bug-236989-27103-g4MzCYUcVh@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-236989-27103@https.bugs.freebsd.org/bugzilla/>
References:  <bug-236989-27103@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D236989

Vincent Milum Jr <freebsd@darkain.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |freebsd@darkain.com

--- Comment #14 from Vincent Milum Jr <freebsd@darkain.com> ---
I just ran into the "nvmeX: Missing interrupt" on FreeNAS under VMWare when
testing something out tonight. It happened right at boot, and repeated quite
often (to the point I couldn't even fully boot the OS after ~20 minutes).
FreeNAS is still on 11.3-RELEASE. But this is a homelab system that I can
easily build test cases with.

nvme drives are Intel Optane M10 16GB. These are cheap on eBay right now. No
data on them at all yet (empty partition table). I was using PCIe passthrou=
gh
on ESXi-6.7.0-20190802001-standard.

I'll start testing various 12.x and 13 kernels to see if conditions are
repeatable on any of those with this config too (if it is, I'll post more
details)

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-236989-27103-g4MzCYUcVh>