From owner-freebsd-current@freebsd.org Fri Oct 18 09:01:36 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 BBADD14ADC6; Fri, 18 Oct 2019 09:01:36 +0000 (UTC) (envelope-from neel@neelc.org) Received: from nyc1.neelc.org (nyc1.neelc.org [185.213.26.161]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 46vg4v5YFMz4Kmv; Fri, 18 Oct 2019 09:01:35 +0000 (UTC) (envelope-from neel@neelc.org) Received: from mail.neelc.org (nyc1.neelc.org [IPv6:2a0d:5600:33:11::2]) by nyc1.neelc.org (Postfix) with ESMTPSA id 2775814DC39; Fri, 18 Oct 2019 05:01:32 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Date: Fri, 18 Oct 2019 05:01:32 -0400 From: Neel Chauhan To: d@delphij.net Cc: =?UTF-8?Q?Eirik_=C3=98verby?= , freebsd-current@freebsd.org, mjg@freebsd.org, owner-freebsd-current@freebsd.org Subject: Re: DRM-current-kmod is still a problem at r353339 In-Reply-To: <25593555-6452-0933-d0fe-0459425cde55@delphij.net> References: <7ca3b30a-81f6-f79d-1486-7fd29765646f@acm.org> <99c89ca0-462c-f4c7-fa07-6f61e9d39d66@acm.org> <3bb2e410-51dd-bc3f-7660-41a4683551b3@daemonic.se> <20191017195347.GB6447@raichu> <53ff1ac5-c7e8-1b6c-bd43-481eaef61120@daemonic.se> <72d67f0a-aeef-1c06-2b12-9351a1f52060@anduin.net> <689d53378dcca22adb29aa23f03e8e1b@neelc.org> <25593555-6452-0933-d0fe-0459425cde55@delphij.net> Message-ID: X-Sender: neel@neelc.org User-Agent: Roundcube Webmail/1.3.9 X-Rspamd-Queue-Id: 46vg4v5YFMz4Kmv X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of neel@neelc.org designates 185.213.26.161 as permitted sender) smtp.mailfrom=neel@neelc.org X-Spamd-Result: default: False [-2.82 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+a]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[neelc.org]; RCPT_COUNT_FIVE(0.00)[5]; TO_MATCH_ENVRCPT_SOME(0.00)[]; IP_SCORE(-0.52)[asn: 63473(-2.54), country: US(-0.05)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:63473, ipnet:185.213.26.0/24, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] 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: Fri, 18 Oct 2019 09:01:36 -0000 This still panicks for me, but with a different error. https://i.postimg.cc/K8nxF57G/IMG-20191018-045338.jpg I really should be sleeping but can't because I have to use an older kernel to have working graphics. Thanks, Netflix for making my life harder. -Neel On 2019-10-18 01:01, Xin Li wrote: > Another (semi-fixed!) data point -- I can confirm that with if > (vm_page_sleep_if_busy(page, "linuxkpi")) > -> if (!vm_page_busy_acquire(page, VM_ALLOC_WAITFAIL)) change and > mjg@'s earlier patch at > https://people.freebsd.org/~mjg/pmap-fict-invl.diff (please commit it) > , > the latest drm-v5.0 branch of drm-current-kmod worked just fine with > Intel HD Graphics P630 on Lenovo P51. > > On 2019-10-17 18:37, Neel Chauhan wrote: >> However, the patch to drm-kmod doesn't work for me. I tried both >> drm-devel-kmod and drm-current-kmod. >> >> https://i.imgur.com/81JvaOO.jpg >> >> -Neel >> >> === >> >> https://www.neelc.org/ >> >> On 2019-10-17 17:35, Eirik Øverby wrote: >>> On 10/17/19 11:29 PM, Eirik Øverby wrote: >>>> On 10/17/19 10:31 PM, 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: >>> ...... >>>>>> 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. >>> .......>> >>>>> 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? >>>> >>>> Built, rebooting ... Will hopefully check back in soon. >>> >>> And tada, I'm back. That seemed to do the trick. Thanks! >>> >>> /Eirik >>> _______________________________________________ >>> freebsd-current@freebsd.org mailing list >>> https://lists.freebsd.org/mailman/listinfo/freebsd-current >>> To unsubscribe, send any mail to >>> "freebsd-current-unsubscribe@freebsd.org" >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to >> "freebsd-current-unsubscribe@freebsd.org" > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org"