From owner-freebsd-x11@freebsd.org Mon Oct 1 12:22:34 2018 Return-Path: Delivered-To: freebsd-x11@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 D14D610B72E9 for ; Mon, 1 Oct 2018 12:22:34 +0000 (UTC) (envelope-from jakob@alvermark.net) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 6E0B2743F0 for ; Mon, 1 Oct 2018 12:22:34 +0000 (UTC) (envelope-from jakob@alvermark.net) Received: by mailman.ysv.freebsd.org (Postfix) id 3226A10B72E8; Mon, 1 Oct 2018 12:22:34 +0000 (UTC) Delivered-To: x11@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 1019810B72E7 for ; Mon, 1 Oct 2018 12:22:34 +0000 (UTC) (envelope-from jakob@alvermark.net) Received: from out.alvermark.net (out.alvermark.net [185.34.136.138]) (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 A021F743EE for ; Mon, 1 Oct 2018 12:22:33 +0000 (UTC) (envelope-from jakob@alvermark.net) Received: from c-42bc70d5.06-431-73746f70.bbcust.telenor.se ([213.112.188.66] helo=mail.alvermark.net) by out.alvermark.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.91 (FreeBSD)) (envelope-from ) id 1g6xDU-000Oz4-84; Mon, 01 Oct 2018 14:22:24 +0200 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=alvermark.net; s=x; h=Content-Transfer-Encoding:Content-Type:In-Reply-To: MIME-Version:Date:Message-ID:References:Cc:To:From:Subject:Sender:Reply-To: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=wVpBGQ/NQvw1d9M3HH8KHOQXKsbrCzmASNcf0hzCH8Q=; b=LqYF1mqwOKco9R5FvLnzWmZSfm UtvRk9RG3Y3wqUShfhFqaf25hxEC5HZ7cFUIKiA2LPGBZpGkSgq0MP2ExnAW7x+prb5zQoGrYlT1+ z4WiBXfQ4XyFzVcM2OgKMOVFWHU52OF22uWIg2GKusOqH1SM0RIEtuWKurR8O/LXfApOmA5npNxI+ oI7PE2gkeHy9gnTuEnncCGiW4Ys+cdtWO1kbi2t23qjF12qPK7BvWWkQU4taM8PcR9uvXkXVNNp25 C0q8f3zQvMh3h/GVsqGhY34KH1Lbe6A4JBB5/xOvt+ovODkDeJp33YRQmqfDhXzXpSUw6rxlC99e5 +J9k9oIQ==; Received: from [192.168.67.33] by mail.alvermark.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.91 (FreeBSD)) (envelope-from ) id 1g6xDT-0009KF-NO; Mon, 01 Oct 2018 14:22:23 +0200 Subject: Re: drm-devel-kmod-4.16.g20180824 hangs my laptop From: Jakob Alvermark To: Johannes Lundberg Cc: Niclas Zeising , x11@freebsd.org References: <4c80c55c-fa61-b5cf-8720-0b5317763841@alvermark.net> <86zhwuc3rt.fsf@gmail.com> <9f829bf0-e2dd-49ab-ebc6-11a472888c2b@daemonic.se> <7c8d6ce8-4435-eec8-4b69-574354ddb0ad@alvermark.net> Message-ID: <07de3211-6c67-9b1c-5f96-e77f8d49248d@alvermark.net> Date: Mon, 1 Oct 2018 14:22:23 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0.1 MIME-Version: 1.0 In-Reply-To: <7c8d6ce8-4435-eec8-4b69-574354ddb0ad@alvermark.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Oct 2018 12:22:35 -0000 On 9/14/18 9:03 PM, Jakob Alvermark wrote: > On 9/14/18 11:30 AM, Johannes Lundberg wrote: >> >> >> On Thu, Sep 13, 2018 at 4:37 PM Jakob Alvermark > > wrote: >> >>     On 9/6/18 1:25 PM, Jakob Alvermark wrote: >>     > On 9/6/18 12:45 PM, Niclas Zeising wrote: >>     >> On 09/06/18 12:35, Johannes Lundberg wrote: >>     >>> >>     >>> Jakob Alvermark writes: >>     >>> >>     >>>> Hi, >>     >>>> >>     >>>> >>     >>>> When I updated to drm-devel-kmod-4.16.g20180824 my laptop >> hangs. >>     >>>> Previous version of drm-devel-kmod worked. >>     >>>> >>     >>>> kld_list="/boot/modules/i915kms.ko" in /etc/rc.conf >>     >>>> >>     >>>> When it boots and the modules load the screen goes blank >>     (backlight >>     >>>> still on) and the machine is totally non-responsive. >>     >>>> >>     >>>> CPU: Intel(R) Pentium(R) CPU N3540 @ 2.16GHz (2166.72-MHz >>     K8-class >>     >>>> CPU) >>     >>>> >>     >>>> vgapci0@pci0:0:2:0: class=0x030000 card=0x09331025 >>     chip=0x0f318086 >>     >>>> rev=0x0e hdr=0x00 >>     >>>>    vendor = 'Intel Corporation' >>     >>>>    device = 'Atom Processor Z36xxx/Z37xxx Series Graphics & >>     Display' >>     >>>>    class = display >>     >>>>    subclass = VGA >>     >>>> >>     >>> >>     >>> Hi >>     >>> >>     >>> Did you update the kernel as well? >>     >>> >>     >>> I think this is due to a change in HEAD. You need to wait until >>     >>> the binary packages have been updated with a new build or >>     build drm >>     >>> drivers from ports/source with the new head in /usr/src. >>     >>> >>     >>> This would be the same for stable/next as well. >>     >> >>     >> Which versions of FreeBSD and of the -devel port were the last >>     ones >>     >> that worked?  What happens if you downgrade the port to that >>     version, >>     >> but keep the same version of FreeBSD base as is failing? >>     > >>     > >>     > Did some further testing: >>     > >>     > drm-devel-kmod-4.16.g20180822 does not work. Same thing as above, >>     > blank screen and hang. >>     > >>     > drm-devel-kmod-4.15.g20180802 works. >>     > >>     > I am now at r338488 >> >> >>     Another thing I have noticed: >> >>     With drm-devel-kmod-4.15.g20180802 my machine hangs after a while, >>     around 24 hours. If I leave it on overnight it is usually is hung >> the >>     next day. >> >>     Black screen an no response to anything, keyboard or power button. I >>     have to power off hard. >> >>     This doesn't seem to happen with drm-next-kmod-4.11.g20180822. >> >> Thanks for reporting. I think there's a memory leak affecting all >> drivers in drm-devel-kmod. > > > I was guessing it was a memory leak. > > I will stay on drm-next-kmod-4.11.g20180822 for now, but I will be > happy to test anything if requested. On request from Niclas, I tried to get a dump with drm-devel-kmod-4.16.g20180824 on r339036 but it does not give me a dump. Manually triggering a dump with 'sysctl debug.kdb.panic=1' works fine. Jakob