From owner-freebsd-stable@freebsd.org Wed Feb 21 20:04:24 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1CEC2F25AFC for ; Wed, 21 Feb 2018 20:04:24 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [IPv6:2607:f3e0:80:80::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "smarthost.sentex.ca", Issuer "smarthost.sentex.ca" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id BD6446FDE3; Wed, 21 Feb 2018 20:04:23 +0000 (UTC) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (lava.sentex.ca [IPv6:2607:f3e0:0:5::11]) by smarthost2.sentex.ca (8.15.2/8.15.2) with ESMTPS id w1LK4NZf049602 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 21 Feb 2018 15:04:23 -0500 (EST) (envelope-from mike@sentex.net) Received: from [192.168.43.26] (saphire3.sentex.net [192.168.43.26]) by lava.sentex.ca (8.15.2/8.15.2) with ESMTP id w1LK4Kjj095898; Wed, 21 Feb 2018 15:04:21 -0500 (EST) (envelope-from mike@sentex.net) To: FreeBSD-STABLE Mailing List From: Mike Tancsa Subject: new Ryzen lockup issue ? Organization: Sentex Communications Message-ID: Date: Wed, 21 Feb 2018 15:04:21 -0500 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 2.78 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Feb 2018 20:04:24 -0000 Not sure if I have found another issue specific to Ryzen, or a bug that manifests itself on Ryzen systems easier. I installed the latest virtualbox from the ports and was doing some network performance tests between a vm and the hypervisor using iperf3. The guest is just a RELENG11 image and the network is an em nic bridged to epair1b Then running in a loop #!/bin/sh while true do iperf3 -t 20 -R -c 192.168.19.18 iperf3 -t 20 -c 192.168.19.18 sleep 20 done where 192.168.17.19 is the guest image, the box locks up solid after 10min to 30min of letting the script run. By lockup I mean the keyboard is not responsive or anything. I can do this on two separate physical machines (both ASUS MBs). # ifconfig epair1a epair1a: flags=8943 metric 0 mtu 1500 description: -------FreeBSD11-generic-VM options=8 ether 02:ff:20:00:06:0a hwaddr 02:ff:20:00:06:0a inet 192.168.19.17 netmask 0xffffff00 broadcast 192.168.19.255 nd6 options=29 media: Ethernet 10Gbase-T (10Gbase-T ) status: active groups: epair # ifconfig epair1b epair1b: flags=8843 metric 0 mtu 1500 options=8 ether 02:00:60:00:07:0b hwaddr 02:00:60:00:07:0b nd6 options=29 media: Ethernet 10Gbase-T (10Gbase-T ) status: active groups: epair Any idea how to debug this to see if this is a hardware issue vs the kernel deadlocking ? If I need to upgrade it to HEAD I can do so if need be, but it would be nice to try and narrow it down first to a hardware issue (its 2 different boxes) or software issue. ---Mike -- ------------------- Mike Tancsa, tel +1 519 651 3400 x203 Sentex Communications, mike@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada