Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 21 Dec 2018 21:15:21 +0000
From:      bugzilla-noreply@freebsd.org
To:        virtualization@FreeBSD.org
Subject:   [Bug 225791] ena driver causing kernel panics on AWS EC2
Message-ID:  <bug-225791-27103-4R3gZ0bGOx@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-225791-27103@https.bugs.freebsd.org/bugzilla/>
References:  <bug-225791-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=3D225791

berend@pobox.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |berend@pobox.com

--- Comment #28 from berend@pobox.com ---
Seeing exactly the same thing on m5.large. 100% repeatable (full zfs send/r=
ecv
from another server).

Dec 21 21:07:10 nfs1 kernel: Fatal trap 12: page fault while in kernel mode
Dec 21 21:07:10 nfs1 kernel: cpuid =3D 0; apic id =3D 00
Dec 21 21:07:10 nfs1 kernel: fault virtual address      =3D 0x1c
Dec 21 21:07:10 nfs1 kernel: fault code         =3D supervisor write data, =
page
not present
Dec 21 21:07:10 nfs1 kernel: instruction pointer        =3D
0x20:0xffffffff82269f5c
Dec 21 21:07:10 nfs1 kernel: stack pointer              =3D
0x0:0xfffffe02259ac180
Dec 21 21:07:10 nfs1 kernel: frame pointer              =3D
0x0:0xfffffe02259ac260
Dec 21 21:07:10 nfs1 kernel: code segment               =3D base 0x0, limit
0xfffff, type 0x1b
Dec 21 21:07:10 nfs1 kernel: =3D DPL 0, pres 1, long 1, def32 0, gran 1
Dec 21 21:07:10 nfs1 kernel: processor eflags   =3D interrupt enabled, resu=
me,
IOPL =3D 0
Dec 21 21:07:10 nfs1 kernel: current process            =3D 12 (irq260: ena=
0)
Dec 21 21:07:10 nfs1 kernel: trap number                =3D 12
Dec 21 21:07:10 nfs1 kernel: panic: page fault
Dec 21 21:07:10 nfs1 kernel: cpuid =3D 0
Dec 21 21:07:10 nfs1 kernel: KDB: stack backtrace:
Dec 21 21:07:10 nfs1 kernel: #0 0xffffffff80b3d577 at kdb_backtrace+0x67
Dec 21 21:07:10 nfs1 kernel: #1 0xffffffff80af6b17 at vpanic+0x177
Dec 21 21:07:10 nfs1 kernel: #2 0xffffffff80af6993 at panic+0x43
Dec 21 21:07:10 nfs1 kernel: #3 0xffffffff80f77fdf at trap_fatal+0x35f
Dec 21 21:07:10 nfs1 kernel: #4 0xffffffff80f78039 at trap_pfault+0x49
Dec 21 21:07:10 nfs1 kernel: #5 0xffffffff80f77807 at trap+0x2c7
Dec 21 21:07:10 nfs1 kernel: #6 0xffffffff80f5808c at calltrap+0x8
Dec 21 21:07:10 nfs1 kernel: #7 0xffffffff80abcd69 at
intr_event_execute_handlers+0xe9
Dec 21 21:07:10 nfs1 kernel: #8 0xffffffff80abd047 at ithread_loop+0xe7
Dec 21 21:07:10 nfs1 kernel: #9 0xffffffff80aba093 at fork_exit+0x83
Dec 21 21:07:10 nfs1 kernel: #10 0xffffffff80f58fae at fork_trampoline+0xe
Dec 21 21:07:10 nfs1 kernel: Uptime: 11h49m3s
Dec 21 21:07:10 nfs1 kernel: Rebooting...

--=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-225791-27103-4R3gZ0bGOx>