From owner-freebsd-virtualization@freebsd.org Tue Feb 25 12:02:15 2020 Return-Path: Delivered-To: freebsd-virtualization@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id B436825A0CC for ; Tue, 25 Feb 2020 12:02:15 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 48RcxM3n6Bz4Hh3 for ; Tue, 25 Feb 2020 12:02:15 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 8171425A0CB; Tue, 25 Feb 2020 12:02:15 +0000 (UTC) Delivered-To: virtualization@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 8107625A0CA for ; Tue, 25 Feb 2020 12:02:15 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 48RcxM2XTQz4Hh0 for ; Tue, 25 Feb 2020 12:02:15 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 50C52E235 for ; Tue, 25 Feb 2020 12:02:15 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 01PC2Ffg030120 for ; Tue, 25 Feb 2020 12:02:15 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 01PC2FxE030113 for virtualization@FreeBSD.org; Tue, 25 Feb 2020 12:02:15 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 235856] FreeBSD freezes on AWS EC2 t3 machines Date: Tue, 25 Feb 2020 12:02:14 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 12.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: mail@rubenvos.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: virtualization@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Feb 2020 12:02:15 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D235856 --- Comment #32 from mail@rubenvos.com --- (In reply to Colin Percival from comment #31) Hi, I've managed to reboot all servers with the verbose setting active. If the issue occurs again ill be sure to upload the information you requested (unl= ess you want to have a look at it "now"?). One of the machines seemed weirdly impacted by a similar issue whilst recei= ving a stream of 5 MB/s (zfs snapshot): Feb 25 11:04:01 volume3 kernel: ena0: Keep alive watchdog timeout. Feb 25 11:04:01 volume3 kernel: ena0: Trigger reset is on Feb 25 11:04:01 volume3 kernel: ena0: device is going DOWN Feb 25 11:04:19 volume3 kernel: ena0: ena0: device is going UP Feb 25 11:04:19 volume3 kernel: link is UP Feb 25 11:05:10 volume3 dhclient[33054]: send_packet6: Network is down Feb 25 11:05:10 volume3 dhclient[33054]: dhc6: send_packet6() sent -1 of 52 bytes Feb 25 11:26:32 volume3 kernel: ena0: The number of lost tx completion is a= bove the threshold (129 > 128). Reset the device Feb 25 11:26:32 volume3 kernel: ena0: Trigger reset is on Feb 25 11:26:32 volume3 kernel: ena0: device is going DOWN Feb 25 11:26:33 volume3 kernel: ena0: free uncompleted tx mbuf qid 1 idx 0x= 182 Feb 25 11:26:33 volume3 kernel:=20 Feb 25 11:26:33 volume3 kernel: stray irq260 Feb 25 11:26:33 volume3 kernel: ena0: ena0: device is going UP Feb 25 11:26:33 volume3 kernel: link is UP Feb 25 11:34:06 volume3 shutdown[76043]: reboot by ruben:=20 Symptoms : very high load, unresponsive system (freezes/hangs on console).= =20 No nvme messages though. Unfortunately, I did not yet have the verbose boot information you requested at that point. Did not have time to further debug either, since we need this machine up and running (initiated the reboot at 11:34) :( Regards, Ruben --=20 You are receiving this mail because: You are the assignee for the bug.=