Received: by 2002:a25:6193:0:0:0:0:0 with SMTP id v141csp3680839ybb; Mon, 6 Apr 2020 13:26:53 -0700 (PDT) X-Google-Smtp-Source: APiQypICSsOL3/bucJcUGYOKr46wYRVUwWAd+dypsWYEfcu0O7WgDt2ULpHbl2qWXep41l8+D1h3 X-Received: by 2002:a4a:3854:: with SMTP id o20mr809362oof.69.1586204812903; Mon, 06 Apr 2020 13:26:52 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1586204812; cv=none; d=google.com; s=arc-20160816; b=QVWLs6OTmEO1JclrejxK6IKRn3CeYz3kaHN1lj912BCznW7UWMZjJDPDFfTox8POzr BPA9SgJBYDOLBP7aMXTTFXb1TUAeIEW/7tYaVuWYn5f2ZGQjvZvaxuaRehKgDVL7dU6W CloLTo1VRgJn9+27cQm1W3LR79h2Ij5Zikahi+ollrOol/y9pu7eDhp7PpgtN/ARtt// MsTSfbOpuj3M/YaqwzlBunitGvVoQ/ZDwBj/ujEWmsZcRrEH6zBW73t+ZWb34zAqI050 k6tsim+HbS92/Ki46FXltonKz9REsAGpZhK/JzDdEdkSsoRaMdQZ/0/oiDFgnWEw40/2 LgxA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-language :content-transfer-encoding:in-reply-to:mime-version:user-agent:date :message-id:organization:from:references:cc:to:subject :dkim-signature; bh=x0BbyVMIRbUnKWB/iRRb3qLHLWJynwL0o1n+cg1YWeE=; b=FjOesO8+3z+JObAAnpRFdrlyJKB/be8Gp80ulzZS7+6fg6iWUV8b9RTh2sh31Wp6Dg 2/HgIOUgD5+lcqaWopdLoaaBhGw6R7GAhuJKZ5VE10o64YGf58N4+Iq1chltNHVUYRa2 DDmF5ye6tVXZqce6hLd10p6eH0ZDQGIwIvKl+jAnVrcpRyXLqKEeYIBjGdi8BODvykEV HObrB2PRewqzh6+cLqNVBDu/8+uszgKIaQEPXbhCfbKM2ZYvibk7EYRoPuiWwHtWBJUe TUgp6qAAxQvJtKHuo8DM/dNaIcI75sY9uFsassVv35jjCBayk20OqUdYbKKG/mpT1Ex+ R4ug== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail (test mode) header.i=@shipmail.org header.s=mail header.b=j4IsSgXC; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id z3si301228oth.163.2020.04.06.13.26.40; Mon, 06 Apr 2020 13:26:52 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=fail (test mode) header.i=@shipmail.org header.s=mail header.b=j4IsSgXC; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726269AbgDFU0F (ORCPT + 99 others); Mon, 6 Apr 2020 16:26:05 -0400 Received: from ste-pvt-msa2.bahnhof.se ([213.80.101.71]:46023 "EHLO ste-pvt-msa2.bahnhof.se" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725957AbgDFU0E (ORCPT ); Mon, 6 Apr 2020 16:26:04 -0400 Received: from localhost (localhost [127.0.0.1]) by ste-pvt-msa2.bahnhof.se (Postfix) with ESMTP id A8CC343DF6; Mon, 6 Apr 2020 22:26:02 +0200 (CEST) Authentication-Results: ste-pvt-msa2.bahnhof.se; dkim=pass (1024-bit key; unprotected) header.d=shipmail.org header.i=@shipmail.org header.b=j4IsSgXC; dkim-atps=neutral X-Virus-Scanned: Debian amavisd-new at bahnhof.se X-Spam-Flag: NO X-Spam-Score: -2.099 X-Spam-Level: X-Spam-Status: No, score=-2.099 tagged_above=-999 required=6.31 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ste-ftg-msa2.bahnhof.se (amavisd-new); dkim=pass (1024-bit key) header.d=shipmail.org Received: from ste-pvt-msa2.bahnhof.se ([127.0.0.1]) by localhost (ste-ftg-msa2.bahnhof.se [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4SIvHs6jCMD6; Mon, 6 Apr 2020 22:26:01 +0200 (CEST) Received: from mail1.shipmail.org (h-205-35.A357.priv.bahnhof.se [155.4.205.35]) (Authenticated sender: mb878879) by ste-pvt-msa2.bahnhof.se (Postfix) with ESMTPA id AEB7B43DF7; Mon, 6 Apr 2020 22:25:53 +0200 (CEST) Received: from localhost.localdomain (h-205-35.A357.priv.bahnhof.se [155.4.205.35]) by mail1.shipmail.org (Postfix) with ESMTPSA id 00151360153; Mon, 6 Apr 2020 22:25:50 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=shipmail.org; s=mail; t=1586204753; bh=WbUdhT5dg8z6hiyUYRS2nHJSvQqFxrl6lLG86/Mrvrw=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=j4IsSgXCnt5Bt0aXP9MiHm1kUCfwxku/J/HE5dUuMTKMOEMowSsbZEHrWcuUNN0yH WDg9Fkb77WT1LTTjQ+N2NawXF8q8m2i5RnfAxXl442JoAsMc1xjDwrnanD0DAp+Sbo SoUUE3bwPLSNgtYb+QJg2M+7TmotgzrwwCvNB0jk= Subject: Re: Bad rss-counter state from drm/ttm, drm/vmwgfx: Support huge TTM pagefaults To: "Alex Xu (Hello71)" , linux-mm@kvack.org, dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org Cc: pv-drivers@vmware.com, linux-graphics-maintainer@vmware.com, Andrew Morton , Michal Hocko , "Matthew Wilcox (Oracle)" , "Kirill A. Shutemov" , Ralph Campbell , =?UTF-8?B?SsOpcsO0bWUgR2xpc3Nl?= , =?UTF-8?Q?Christian_K=c3=b6nig?= , Dan Williams , Roland Scheidegger References: <1586138158.v5u7myprlp.none.ref@localhost> <1586138158.v5u7myprlp.none@localhost> From: =?UTF-8?Q?Thomas_Hellstr=c3=b6m_=28VMware=29?= Organization: VMware Inc. Message-ID: <249c73d2-991a-56b0-53b5-677e9ca54aae@shipmail.org> Date: Mon, 6 Apr 2020 22:25:49 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.2.2 MIME-Version: 1.0 In-Reply-To: <1586138158.v5u7myprlp.none@localhost> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 4/6/20 9:51 PM, Alex Xu (Hello71) wrote: > Using 314b658 with amdgpu, starting sway and firefox causes "BUG: Bad > rss-counter state" and "BUG: non-zero pgtables_bytes on freeing mm" to > start filling dmesg, and then closing programs causes more BUGs and > hangs, and then everything grinds to a halt (can't start more programs, > can't even reboot through systemd). > > Using master and reverting that branch up to that point fixes the > problem. > > I'm using a Ryzen 1600 and AMD Radeon RX 480 on an ASRock B450 Pro4 > board with IOMMU enabled. Hmm. That sounds bad. Could you send a copy of your config? Meanwhile, I'll prepare a small patch that disables the non-vmwgfx huge_fault() until we've figured out what's happening. /Thomas