From owner-freebsd-stable@freebsd.org Fri Feb 23 17:35:53 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 D1664F0AB6D for ; Fri, 23 Feb 2018 17:35:52 +0000 (UTC) (envelope-from nimrod@nimrod.is-a-geek.net) Received: from mail-yw0-x22a.google.com (mail-yw0-x22a.google.com [IPv6:2607:f8b0:4002:c05::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6996C6C67C for ; Fri, 23 Feb 2018 17:35:52 +0000 (UTC) (envelope-from nimrod@nimrod.is-a-geek.net) Received: by mail-yw0-x22a.google.com with SMTP id y186so3041713ywf.7 for ; Fri, 23 Feb 2018 09:35:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nimrod-is-a-geek-net.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=SehdZA9SboFvm/j9z65FBIzN6NXEsi+RMNPjjC3A4cE=; b=m0gPT4Wr+5VZ/2FWcCve0l6bZwH1e75YPOHvXbjEZoBqKlDQZ1ob4AAkSTj+t7aTB8 veJgwa4WgHjSefJbDNS0ftmQJ9WlvR1zJUMbpEack5eNllY3TLmOCNlKWE9TEMTCDsg8 DKQD8Jx2XX5HiO7kKhEZaQ9+X+iZniY/ZrjcpSZP3zyaYo2STW3T3fnKEvz8gMJ1IpEX zgoK0bhmMLK69LfDybyy+43OJZSd+tweYo0fHtJYXJt3bR5m9C3jZ02GIwY2MCpDnDtW Wb9lKuI/80K52ZG9x1g7HRAwZCiDYc+zgpKbR/u8P/0c3KyGeroP8bcNRWOWTMPJOPWj KNoQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=SehdZA9SboFvm/j9z65FBIzN6NXEsi+RMNPjjC3A4cE=; b=npB951cKIdxdqvlQxN0LVEbPt/Q1PZas/k0GHwrYCiCTmQM5qJzJP4k3JukFvGf0Sx H7USbH+Qe+vno/4UW8L/HGWjYMdWhAPiQqTDNFkiyWSbLKVIpcmqSwReZalNyVdAP9vG xMaK0u4OaCFu9AP5pJE23Uf6rKR3TnAWuKQBX46Ofba5hNBa4cQ85EykLsGQ/OZKG7J4 xkYKhg3Of+uXtR9jIB8AdTcNHqMcFmHEwUMv8E6hTNF47zHbQsYQWIta3NtvstYP6IhO zvoK5AczO3r8DtHh+mDqs5jC8r20gzhuI3WhKJw/gDYrALnVYAO9ADMUPlChRdsk5LG4 m8tg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=SehdZA9SboFvm/j9z65FBIzN6NXEsi+RMNPjjC3A4cE=; b=X8UMhonINt9H1WW5uvlbKlvL5HsN7/upxrDborXei3ysUS1hdx1QQESAloy9Z/9nas 4W1qY/f4zlQxQNRQiv94fYiq24Yrc0Tm1wV0lmkouCqkmgFK5PbFhi4ETbcdRl4y0K2I HStBoczBQHTw19wSY74KDj1i0Rzuwsr2M9+qAHyyS9EicbSyHnoL3nYZUPnkcthduFk5 A6LuVChESK1F6rGg+1iuhcWH/P7Z3WGrT0Wyr8bRoORpFpHt/Dht8hxeO+vlEdCSBUv5 TtXPqrHZSiFbQIov+fyCZeOgw8Jui3AjYJ4A3MoqBWpwihNmuKVUPJoJNMa6qsmaQQBE u6tA== X-Gm-Message-State: APf1xPDOsLPsZUjNrjPPns1odEdSS2Wa7naGE68GgN54g6+p3kPiyDkC Y+GZjZJHl1213jCLgJcl91WzRL/a68uWjtZaSknFxg== X-Google-Smtp-Source: AH8x224eCjuwmw6nGUIUZBgRHXCSfu9giOHHe4uPXN5xETz65j0AcwPywwZycY6cv2bE5S1yYhlHQmoNUcWKKqnR34E= X-Received: by 10.129.148.196 with SMTP id l187mr1577519ywg.453.1519407351396; Fri, 23 Feb 2018 09:35:51 -0800 (PST) MIME-Version: 1.0 Sender: nimrod@nimrod.is-a-geek.net Received: by 10.129.102.69 with HTTP; Fri, 23 Feb 2018 09:35:50 -0800 (PST) X-Originating-IP: [108.31.4.177] In-Reply-To: <92a60e14-f532-2647-d45d-b500fc59ba88@sentex.net> References: <92a60e14-f532-2647-d45d-b500fc59ba88@sentex.net> From: Nimrod Levy Date: Fri, 23 Feb 2018 12:35:50 -0500 X-Google-Sender-Auth: BiqMEF1hE4BI-etlM857T85U3kM Message-ID: Subject: Re: new Ryzen lockup issue ? To: Mike Tancsa Cc: FreeBSD-STABLE Mailing List Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 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: Fri, 23 Feb 2018 17:35:53 -0000 Now that is a fascinating data point. My machine that I've been having issues with has been running a bhyve vm from the beginning. I never made the connection. I'll try throwing some network traffic at the VM and see if I can make it lock up. On Fri, Feb 23, 2018 at 10:14 AM, Mike Tancsa wrote: > On 2/22/2018 3:41 PM, Mike Tancsa wrote: > > On 2/21/2018 3:04 PM, Mike Tancsa wrote: > >> 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 > > > > This looks possibly related to VirtualBox. Doing the same tests and more > > using bhyve, I dont get any lockup. Not to mention, network IO is MUCH > > faster. > > > Actually, it just took a little bit longer to lock up the box with bhyve > on RELENG_11 as the hypervisor. Would be great if anyone can confirm > this locks up their Ryzen boxes ? I tried 2 different boxes to eliminate > a hardware issue. Also tried a similar test on Ubuntu and I can spin up > 4 instances and run without lockups. > > Just grab a copy of > > https://download.freebsd.org/ftp/releases/VM-IMAGES/11.1- > RELEASE/amd64/Latest/FreeBSD-11.1-RELEASE-amd64.raw.xz > > and make 2 copies. tmp.raw and tmp2.raw > > > kldload vmm > ifconfig tap0 create > ifconfig tap1 create > ifconfig tap1 up > ifconfig tap0 up > ifconfig bridge0 create addm tap0 addm tap1 > ifconfig bridge0 192.168.99.1/24 > > screen -d -m sh /usr/share/examples/bhyve/vmrun.sh -c 4 -m 6144M -t tap0 > -d tmp.raw BSD11a > screen -d -m sh /usr/share/examples/bhyve/vmrun.sh -c 4 -m 6144M -t tap1 > -d tmp2.raw BSD11b > > Install netperf on the 2 vms and give the vtnet interface > 192.168.99.2/24 and 192.168.99.3/24 > > In both VMs pkg install iperf3 and start it up as > iperf -s > > In the hypervisor, > iperf -t 10000 -R -c 192.168.99.2 > iperf -t 10000 -c 192.168.99.3 > > > the box locks up solid after 5-20 min. Same hardware with Ubuntu and > virtual box and 4 instances work fine, no lockups after a day so not > sure whats up but it seems to be something with the Ryzen CPU running as > a hypervisor or with some type of load :( > > Prior to lockup I had a stream of netstat -m writing to a file every 5 > seconds. The last entry was below. It doesnt seem to be leak. > > Thu Feb 22 17:14:28 EST 2018 > 8694/10281/18975 mbufs in use (current/cache/total) > 8225/5211/13436/2038424 mbuf clusters in use (current/cache/total/max) > 8225/5184 mbuf+clusters out of packet secondary zone in use (current/cache) > 461/3747/4208/1019211 4k (page size) jumbo clusters in use > (current/cache/total/max) > 0/0/0/301988 9k jumbo clusters in use (current/cache/total/max) > 0/0/0/169868 16k jumbo clusters in use (current/cache/total/max) > 20467K/27980K/48447K bytes allocated to network (current/cache/total) > 0/0/0 requests for mbufs denied (mbufs/clusters/mbuf+clusters) > 0/0/0 requests for mbufs delayed (mbufs/clusters/mbuf+clusters) > 0/0/0 requests for jumbo clusters delayed (4k/9k/16k) > 0/0/0 requests for jumbo clusters denied (4k/9k/16k) > 0 sendfile syscalls > 0 sendfile syscalls completed without I/O request > 0 requests for I/O initiated by sendfile > 0 pages read by sendfile as part of a request > 0 pages were valid at time of a sendfile request > 0 pages were requested for read ahead by applications > 0 pages were read ahead by sendfile > 0 times sendfile encountered an already busy page > 0 requests for sfbufs denied > 0 requests for sfbufs delayed > > > > ---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 > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >