From owner-freebsd-current@freebsd.org Fri Apr 6 15:08:19 2018 Return-Path: Delivered-To: freebsd-current@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 160FCF8CAC5 for ; Fri, 6 Apr 2018 15:08:19 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-io0-x231.google.com (mail-io0-x231.google.com [IPv6:2607:f8b0:4001:c06::231]) (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 9588680164 for ; Fri, 6 Apr 2018 15:08:18 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-io0-x231.google.com with SMTP id d6so2094328iog.1 for ; Fri, 06 Apr 2018 08:08:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=DgOGwv5f/QW1YXNyK2c7YcdC4EXyKd1gJ39ACYvvJ0g=; b=QjN/wtQueAI1Mlfriop1xrkZ6eWfmP+5PEf6B5E2oKbYjgryqXDEJ/pqpt5RXxMd/w YifIiSROSAGkiZkilXIj0XmL85L8iTEn3SM2vtDs8WLf/dl5kMdKgPuujy/pYkhqWmj7 w3Mzr4f09t9BrtJs3vYOM/oksB1wE0sE1qmB+GAompTiMXA8JGCGj2buvyaSABAhYV46 TQBlSH2rRKjINGye8ErM83zHKGpKw8WwA+bBzDNVfLsQfasqfmJioOFfkDkvoFSq8axv mPt7bze3aggumwXn8qCVO4YIFf4KwonCkBw5CRDyc+K1Mj3gGKoy9oSCxOuGyOi++6fZ df3g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=DgOGwv5f/QW1YXNyK2c7YcdC4EXyKd1gJ39ACYvvJ0g=; b=RdNoQ8wD32UxshtVaZpZXQXPSwTuu2rgN5YYIePgWmxllpSYeFpTcLWf9PJp2h7aW6 +1zzV8e3BFdViTOHaTtacVpH58sBVkIgbYZvKLREGBVhyx6FNYWotqS2gJG6tgb/+KPR 4tEiWTgtl+F1Q7tu0GktuLYXIYUUnjxoegda0iEPZYuf6PB2yhDatoAh0QZ1Z5RTFL7G c7m2QWTfLfCB/UJgQpt7GDAS58OeCWiATXOeA7LYz01MKnEWIav+DPwAXHd9XGQ6IjvA zQqQzK+uBj9xCZS7Jo2j1kno+lemXYPVPl3PFPyS8qzHF9uuPvfgiiJyFlB6CU7exQHp uCIA== X-Gm-Message-State: ALQs6tCTinuPbxnToNRTY9PMfcRp8RUWjgboKGMEc6QXMp1wE2KbDIf7 pzmW1Asu918mPONTUU2Slos= X-Google-Smtp-Source: AIpwx4+oJNXEjsFOTuKJAnVZfg6c7FYSDmt9wHnm61ZWcSLi6J50gUHZXhQvM7Cy5IgUNXGOjtcD8w== X-Received: by 10.107.8.32 with SMTP id 32mr23569455ioi.136.1523027297716; Fri, 06 Apr 2018 08:08:17 -0700 (PDT) Received: from raichu (toroon0560w-lp130-04-184-145-252-74.dsl.bell.ca. [184.145.252.74]) by smtp.gmail.com with ESMTPSA id d11sm4157883ioc.13.2018.04.06.08.08.16 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 06 Apr 2018 08:08:16 -0700 (PDT) Sender: Mark Johnston Date: Fri, 6 Apr 2018 11:08:14 -0400 From: Mark Johnston To: Justin Hibbits Cc: Jeff Roberson , FreeBSD current Subject: Re: Strange ARC/Swap/CPU on yesterday's -CURRENT Message-ID: <20180406150814.GB10017@raichu> References: <20180320070745.GA12880@server.rulingia.com> <2b3db2af-03c7-65ff-25e7-425cfd8815b6@FreeBSD.org> <1fd2b47b-b559-69f8-7e39-665f0f599c8f@FreeBSD.org> <20180404174949.GA12271@raichu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Apr 2018 15:08:19 -0000 On Fri, Apr 06, 2018 at 12:47:14AM +0000, Justin Hibbits wrote: > My powerpc64 embedded machine is virtually unusable since these vm changes. > I tried setting vfs.zfs.arc_free_target as suggested, and that didn't help > at all. Eventually the machine hangs and just gets stuck in vmdaemon, with > many processes in wait channel btalloc. You don't really have the same symptoms that Don is reporting. Threads being stuck in btalloc implies a KVA shortage. So: - What do you mean by "stuck in vmdaemon"? - Which commits specifically cause problems? Does reverting r329882 fix the hang? - Can you break to DDB and get "show page" output when the hang occurs? - What is the system doing to cause the hang to occur?