From owner-freebsd-current@freebsd.org Thu Oct 17 13:04:06 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 1AF8E151B8C; Thu, 17 Oct 2019 13:04:06 +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 46v8W82wYJz4C1f; Thu, 17 Oct 2019 13:04:04 +0000 (UTC) (envelope-from zeising+freebsd@daemonic.se) Received: from cid.daemonic.se (localhost [IPv6:::1]) by mail.daemonic.se (Postfix) with ESMTP id 46v8Vz46kRz3lJt; Thu, 17 Oct 2019 13:03:55 +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=1571317434; bh=6UmFfSj4lFpqzaDxb4aWogDq bu/MKf4pyuZZllcmeQs=; b=CYUXcQU+mU4FIrxoFr0diMcRKg+FVlie7u0EoRQh SYLc9tj1IyFNczfR5INdX2PtKS5rks2qhq3SNoYXvS7eUtt6CKMIG1RsHX5hwsaZ 992qCGOZRyI3osPFnRqqnm4C3Va8S5wC5WfNK5mquSRisveGPNr9g70zDCktNHAJ YQk= X-Virus-Scanned: amavisd-new at daemonic.se Received: from mail.daemonic.se ([IPv6:::1]) (using TLS with cipher ECDHE-RSA-AES128-GCM-SHA256) by cid.daemonic.se (mailscanner.daemonic.se [IPv6:::1]) (amavisd-new, port 10587) with ESMTPS id Wp2JN9cDlCsM; Thu, 17 Oct 2019 13:03:54 +0000 (UTC) Received: from garnet.daemonic.se (host-95-192-102-173.mobileonline.telia.com [95.192.102.173]) by mail.daemonic.se (Postfix) with ESMTPSA id 46v8Vw2gPhz3c7Z; Thu, 17 Oct 2019 13:03:52 +0000 (UTC) Subject: Re: DRM-current-kmod is still a problem at r353339 To: Neel Chauhan , Mateusz Guzik Cc: Evilham , FreeBSD Current , owner-freebsd-current@freebsd.org References: <7ca3b30a-81f6-f79d-1486-7fd29765646f@acm.org> <99c89ca0-462c-f4c7-fa07-6f61e9d39d66@acm.org> From: Niclas Zeising Message-ID: <3bb2e410-51dd-bc3f-7660-41a4683551b3@daemonic.se> Date: Thu, 17 Oct 2019 15:03:51 +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: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 46v8W82wYJz4C1f X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=daemonic.se header.s=20151023 header.b=CYUXcQU+; 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.70 / 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]; RCVD_TLS_LAST(0.00)[]; RCPT_COUNT_FIVE(0.00)[5]; 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]; IP_SCORE(-3.70)[ip: (-9.73), ipnet: 2607:f740:d::/48(-4.87), asn: 36236(-3.85), country: US(-0.05)]; RECEIVED_SPAMHAUS_PBL(0.00)[173.102.192.95.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.11]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:36236, ipnet:2607:f740:d::/48, country:US]; TAGGED_FROM(0.00)[freebsd]; MID_RHS_MATCH_FROM(0.00)[] 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: Thu, 17 Oct 2019 13:04:06 -0000 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? Regards -- Niclas