From owner-freebsd-current@freebsd.org Mon Oct 21 08:14:00 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 62CDB177D88; Mon, 21 Oct 2019 08:14:00 +0000 (UTC) (envelope-from zeising+freebsd@daemonic.se) Received: from mail.daemonic.se (mail.daemonic.se [IPv6:2607:f740:d:20::25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 46xTtb48VMz3R7Y; Mon, 21 Oct 2019 08:13:59 +0000 (UTC) (envelope-from zeising+freebsd@daemonic.se) Received: from cid.daemonic.se (localhost [IPv6:::1]) by mail.daemonic.se (Postfix) with ESMTP id 46xTtZ2Jvxz3lJt; Mon, 21 Oct 2019 08:13:58 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=daemonic.se; h= content-transfer-encoding:content-language:content-type :content-type:in-reply-to:mime-version:user-agent:date:date :message-id:from:from:references:subject:subject:received :received; s=20151023; t=1571645637; bh=K/vL7NEAeBgnyJC3JklI/XEo 8ZrWtl4Z6a7SsO93cxg=; b=BISbznMin92uUt7VO05rzMc/9lJ05/KdPsywWVXP I2dgpwd74AulTZmE8WmMPYfo1ySXOHLzsNoBAn8br2gDWF/2u7/QK9IxXDRY2kZ1 wADejk6qY6MjlcRWz7YYCr+jtHk74z07tNplGcuWQ0Dpr3ixE/dZE/iuHrWQev9B JZE= X-Virus-Scanned: amavisd-new at daemonic.se Received: from mail.daemonic.se ([127.0.0.1]) (using TLS with cipher ECDHE-RSA-AES128-GCM-SHA256) by cid.daemonic.se (mailscanner.daemonic.se [127.0.0.1]) (amavisd-new, port 10587) with ESMTPS id Z-kuyb_XeysR; Mon, 21 Oct 2019 08:13:57 +0000 (UTC) Received: from garnet.daemonic.se (host-95-192-35-193.mobileonline.telia.com [95.192.35.193]) by mail.daemonic.se (Postfix) with ESMTPSA id 46xTtY1Wsdz3c7Z; Mon, 21 Oct 2019 08:13:57 +0000 (UTC) Subject: Re: DRM-current-kmod is still a problem at r353339 To: Mark Johnston Cc: Neel Chauhan , Mateusz Guzik , Evilham , FreeBSD Current , owner-freebsd-current@freebsd.org References: <99c89ca0-462c-f4c7-fa07-6f61e9d39d66@acm.org> <3bb2e410-51dd-bc3f-7660-41a4683551b3@daemonic.se> <20191017195347.GB6447@raichu> <53ff1ac5-c7e8-1b6c-bd43-481eaef61120@daemonic.se> <20191017210510.GC6447@raichu> From: Niclas Zeising Message-ID: <96d8f37a-179b-ecad-62d1-5a097d30c0ed@daemonic.se> Date: Mon, 21 Oct 2019 10:13:56 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.1.1 MIME-Version: 1.0 In-Reply-To: <20191017210510.GC6447@raichu> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 46xTtb48VMz3R7Y X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=daemonic.se header.s=20151023 header.b=BISbznMi; dmarc=pass (policy=none) header.from=daemonic.se; spf=pass (mx1.freebsd.org: domain of zeising@daemonic.se designates 2607:f740:d:20::25 as permitted sender) smtp.mailfrom=zeising@daemonic.se X-Spamd-Result: default: False [-6.71 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[daemonic.se:s=20151023]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; IP_SCORE(-3.71)[ip: (-9.76), ipnet: 2607:f740:d::/48(-4.88), asn: 36236(-3.85), country: US(-0.05)]; RCPT_COUNT_FIVE(0.00)[6]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[daemonic.se:+]; DMARC_POLICY_ALLOW(-0.50)[daemonic.se,none]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:36236, ipnet:2607:f740:d::/48, country:US]; TAGGED_FROM(0.00)[freebsd]; MID_RHS_MATCH_FROM(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[193.35.192.95.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.11] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Mon, 21 Oct 2019 08:14:00 -0000 On 2019-10-17 23:05, Mark Johnston wrote: > On Thu, Oct 17, 2019 at 10:31:12PM +0200, Niclas Zeising wrote: >> On 2019-10-17 21:53, markj@freebsd.org wrote: >>> On Thu, Oct 17, 2019 at 03:03:51PM +0200, Niclas Zeising wrote: >>>> On 2019-10-16 18:57, Neel Chauhan wrote: >>>>> While drm-current-kmod worked for a little while, it broke with r353645. >>>>> >>>>> https://i.imgur.com/Q5nYZf2.jpg >>>>> >>>>> I'm using the same HP Spectre that I used earlier (where it worked and >>>>> where it panicked). >>>>> >>>> >>>> That commit looks unrelated, it touches the wbwd and superio drivers, >>>> nothing else. Any chance you can bisect exactly which revision that >>>> caused the new issues? >>> >>> I believe it was the recent work on the vm page busy state, r353539 >>> specifically. This patch should fix it; we don't yet have a >>> __FreeBSD_version number bump on which to gate the patch. >>> >>> diff --git a/linuxkpi/gplv2/src/linux_page.c b/linuxkpi/gplv2/src/linux_page.c >>> index e2b85c45c..060ae85ed 100644 >>> --- a/linuxkpi/gplv2/src/linux_page.c >>> +++ b/linuxkpi/gplv2/src/linux_page.c >>> @@ -239,7 +239,7 @@ retry: >>> page = vm_page_lookup(devobj, i); >>> if (page == NULL) >>> continue; >>> - if (vm_page_sleep_if_busy(page, "linuxkpi")) >>> + if (!vm_page_busy_acquire(page, VM_ALLOC_WAITFAIL)) >>> goto retry; >>> cdev_pager_free_page(devobj, page); >>> } >> >> Hi! >> Hopefully someone can confirm that this patch to drm-current-kmod or >> drm-devel-kmod fixes the issue. I won't be able to work on this before >> the weekend at the earliest, I'm afraid. >> Mark, is it possible to get a belated version bump for this fix, and >> what changed to require it? > > I committed the bump and verified the patch on amdgpu. Here are some > PRs for the drivers: > > https://github.com/FreeBSDDesktop/kms-drm/pull/180 > https://github.com/FreeBSDDesktop/kms-drm/pull/181 Hi! I'm working on getting this into the versions that are in ports. For drm-current-kmod it's fairly simple, but for drm-devel-kmod there are unrelated changes which I need to check if they are ready to go in or not, so it will take some more time. Looking at the mail list thread, there seems to be a patch needed for base as well, has this been committed? Regards -- Niclas