Date: Mon, 25 Nov 2019 08:22:24 +0000 From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 235856] FreeBSD freezes on AWS EC2 t3 machines Message-ID: <bug-235856-27103-JMxTPtSTlR@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-235856-27103@https.bugs.freebsd.org/bugzilla/> References: <bug-235856-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=3D235856 mail@rubenvos.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mail@rubenvos.com --- Comment #9 from mail@rubenvos.com --- (In reply to Charles O'Donnell from comment #8) Hi, We just suffered from the same issue. This particular FreeBSD 12.1 r5.large instance with an additional gp2 disk (ZFS) was up for about 2 weeks when t= his occured. These are the last entries in the "logs" : Nov 25 03:04:36 zfs01 kernel: nvme1: cpl does not map to outstanding cmd Nov 25 03:04:36 zfs01 kernel: cdw0:00000000 sqhd:001a sqid:0001 cid:0018 p:0 sc:00 sct:0 m:0 dnr:0 Nov 25 03:04:36 zfs01 kernel: nvme1: Missing interrupt Nov 25 03:04:36 zfs01 kernel: nvme1: Resetting controller due to a timeout. Nov 25 03:04:36 zfs01 kernel: nvme1: resetting controller Nov 25 03:04:36 zfs01 kernel: nvme1: temperature threshold not supported Nov 25 03:04:36 zfs01 kernel: nvme1: aborting outstanding i/o Nov 25 03:05:07 zfs01 kernel: nvme1: Missing interrupt Nov 25 03:05:36 zfs01 kernel: nvme1: Resetting controller due to a timeout. Nov 25 03:05:36 zfs01 kernel: nvme1: resetting controller Nov 25 03:05:37 zfs01 kernel: nvme1: temperature threshold not supported Nov 25 03:05:37 zfs01 kernel: nvme1: aborting outstanding i/o Nov 25 03:05:37 zfs01 syslogd: last message repeated 4 times Nov 25 03:06:07 zfs01 kernel: nvme1: Missing interrupt Nov 25 03:09:08 zfs01 dhclient[84191]: send_packet: Host is down Nov 25 03:09:52 zfs01 syslogd: last message repeated 4 times @Colin/@Alex: Do you know if this occurs on "older" instance types as well?= We would definately switch to older instance-types if this issue doesn't occur= on older generations. Kind regards, Ruben --=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-235856-27103-JMxTPtSTlR>