Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 20 Apr 2020 08:35:29 +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-tNQ5NyfWqp@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

--- Comment #50 from mail@rubenvos.com ---
(In reply to Colin Percival from comment #49)

Hi Colin,

The machine that was exhibiting the most freezes will be tested extensively
during the next couple of days. No errors on that instance yet. We will
probably have to decommission this particular instance end of this week tho=
ugh
:(

I just had a look on one of the other machines and there is an error in one=
 of
the logs:

Apr  5 09:31:41 volume3 ec2[7704]: -----END SSH HOST KEY FINGERPRINTS-----
Apr  5 09:31:41 volume3 ec2[14622]:
#############################################################
Apr 16 04:08:31 volume3 kernel: nvme1: nvme_timeout
Apr 16 04:08:31 volume3 kernel: nvme1:=20
Apr 16 04:08:31 volume3 kernel: Resetting controller due to a timeout.
Apr 16 04:08:31 volume3 kernel: nvme1: resetting controller
Apr 16 04:08:31 volume3 kernel: nvme1: temperature threshold not supported
Apr 16 04:08:31 volume3 kernel: nvme1: resubmitting queued i/o
Apr 16 04:08:31 volume3 kernel: nvme1: READ sqid:2 cid:0 nsid:1 lba:2029427=
280
len:8
Apr 16 04:08:31 volume3 kernel: nvme1: resubmitting queued i/o
Apr 16 04:08:31 volume3 kernel: nvme1: READ sqid:2 cid:0 nsid:1 lba:1776954=
392
len:8
Apr 16 04:08:31 volume3 kernel: nvme1: resubmitting queued i/o
Apr 16 04:08:31 volume3 kernel: nvme1: READ sqid:2 cid:0 nsid:1 lba:1315250=
264
len:8
Apr 16 04:08:31 volume3 kernel: nvme1: resubmitting queued i/o
Apr 16 04:08:31 volume3 kernel: nvme1: READ sqid:2 cid:0 nsid:1 lba:8718688=
18
len:8
Apr 16 04:08:31 volume3 kernel: nvme1: resubmitting queued i/o
Apr 16 04:08:31 volume3 kernel: nvme1: READ sqid:2 cid:0 nsid:1 lba:4230187=
43
len:7
Apr 16 04:08:31 volume3 kernel: nvme1: resubmitting queued i/o
Apr 16 04:08:31 volume3 kernel: nvme1: READ sqid:2 cid:0 nsid:1 lba:2561980=
904
len:8
Apr 16 04:08:31 volume3 kernel: nvme1: resubmitting queued i/o
Apr 16 04:08:31 volume3 kernel: nvme1: READ sqid:2 cid:0 nsid:1 lba:1987706=
424
len:8
Apr 16 04:08:31 volume3 kernel: nvme1: resubmitting queued i/o
Apr 16 04:08:31 volume3 kernel: nvme1: READ sqid:2 cid:0 nsid:1 lba:1154816=
96
len:8
Apr 16 04:08:31 volume3 kernel: nvme1: resubmitting queued i/o
Apr 16 04:08:31 volume3 kernel: nvme1: READ sqid:2 cid:0 nsid:1 lba:1095204=
568
len:8
Apr 16 04:08:31 volume3 kernel: nvme1: resubmitting queued i/o
Apr 16 04:08:31 volume3 kernel: nvme1: READ sqid:2 cid:0 nsid:1 lba:9482113=
34
len:12

No freezing or any other symptoms yet. This machine runs the patched kernel=
 but
doesn't have a "hw.nvme.timeout_period" setting configured in its
/boot/loader.conf .

Will provide feedback on new developments.

Regards,

Ruben(In reply to Colin Percival from comment #49)
(In reply to Colin Percival from comment #49)

--=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-tNQ5NyfWqp>