Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 01 Sep 2018 11:05:57 +0000
From:      bugzilla-noreply@freebsd.org
To:        bugs@FreeBSD.org
Subject:   [Bug 231070] Crash in nvme_qpair_reset() on base/head r338418 on VirtualBox 5.2.18
Message-ID:  <bug-231070-227@https.bugs.freebsd.org/bugzilla/>

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

            Bug ID: 231070
           Summary: Crash in nvme_qpair_reset() on base/head r338418 on
                    VirtualBox 5.2.18
           Product: Base System
           Version: CURRENT
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: kern
          Assignee: bugs@FreeBSD.org
          Reporter: Trond.Endrestol@ximalas.info

Host is VirtualBox 5.2.18, Windows 7 x64 SP1, and Intel Core i7 960 @ 3.2 G=
Hz.
Guest is amd64 base/head r338418. Last known good revision is r338206.

This can so easily be a bug in the VirtualBox implementation as it can be a=
 bug
in the FreeBSD implementation.
The NVMe controller isn't critical to me, so I removed it from the VM, edit=
ed
/etc/fstab, and carried on.

Screenshots are available at
https://ximalas.info/~trond/NVMe-crash-base-head-r338418/

Kernel messages (typed in from the screenshots, typo's quite possible):

nvme0: Resetting controller due to a timeout.
nvme0: resetting controller


Fatal trap 12: page fault while in kernel mode
cpuid =3D 0; apic id =3D 00
fault virtual address   =3D 0x40
fault code              =3D supervisor write data, page not present
instruction pointer     =3D 0x20:0xffffffff805d7bd9
stack pointer           =3D 0x28:0ffffffe00331a6a80
frame pointer           =3D 0x28:0xfffffe00331a6a90
code segment            =3D base 0x0, limit 0xfffff, type 0x1b
                        =3D CPL 0, pres 1, long 1, def32 0, gran 1
processor eflags        =3D interrupt enable,d resume, IOPL =3D 0
current process         =3D 0 (nvme taskq)
[ thread pid 0 tid 100051 ]
Stopped at      0xffffffff805d7bd9 =3D nvme_qpair_reset+0x9:      movl    $=
0,0x40
=3D ll+x1f(%rbx)
db> bt
Tracing pid 0 tid 100051 td 0xfffff8000c015580
nvme_qpair_reset() at 0xffffffff805d3207 =3D nvme_qpair_reset+0x9/frame
0xfffffe00113a6a90
nvme_ctrlr_start() at 0xffffffff805d3207 =3D nvme_ctrlr_start+0x57/frame
0xfffffe00331a6af0
taskqueue_run_locked() at 0xffffffff807ddaa4 =3D taskqueue_run_locked+0x154=
/frame
0xfffffe00331a6bb0
fork_exit() at 0xffffffff8073d8a3 =3D fork_exit+0x83/frame 0xfffffe00331a6b=
f0
forkt_rampoline() at 0xffffffff80ab97ae =3D fork_trampoline+0xe/frame
0xfffffe00331a6bf0
--- trap 0, rip =3D 0, rsp =3D 0, rbp =3D 0 ---
db>

--=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-231070-227>