Date: Fri, 05 Jun 2020 10:46:43 +0000 From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 243531] Unstable ena and nvme on AWS Message-ID: <bug-243531-27103-66Gu29VZ3g@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-243531-27103@https.bugs.freebsd.org/bugzilla/> References: <bug-243531-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=3D243531 Tom=C3=A1=C5=A1 =C4=8Ciernik <tomas@ciernik.sk> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tomas@ciernik.sk --- Comment #13 from Tom=C3=A1=C5=A1 =C4=8Ciernik <tomas@ciernik.sk> --- Hello, today I had service outage on 12.1-RELEASE-p5. After cca. 10 minutes system= and all services went back to normal. Here is output of /var/log/messages: Jun 5 08:58:37 mail kernel: ena0: The number of lost tx completion is above the threshold (129 > 128). Reset the device Jun 5 08:58:37 mail kernel: ena0: Trigger reset is on Jun 5 08:58:37 mail kernel: ena0: device is going DOWN Jun 5 08:58:37 mail kernel: swap_pager: indefinite wait buffer: bufobj: 0, blkno: 475845, size: 28672 Jun 5 08:58:37 mail kernel: ena0: free uncompleted tx mbuf qid 0 idx 0x8ee= na0: free uncompleted tx mbuf qid 1 idx 0x0swap_pager: indefinite wait buffer: bufobj: 0, blkno: 295657, size: 28672 Jun 5 08:58:38 mail kernel: ena0: ena0: device is going UP Jun 5 08:58:38 mail kernel: link is UP What can I do to confirm relation to this bug? --=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-243531-27103-66Gu29VZ3g>