From owner-freebsd-current@freebsd.org Sun May 13 02:25:47 2018 Return-Path: Delivered-To: freebsd-current@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 6845FFDFF3E for ; Sun, 13 May 2018 02:25:47 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from vps-mail.nomadlogic.org (mail.nomadlogic.org [IPv6:2607:f2f8:a098::2]) (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 E7B9D7FC71 for ; Sun, 13 May 2018 02:25:46 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from [192.168.2.7] (cpe-23-243-163-13.socal.res.rr.com [23.243.163.13]) by vps-mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id c5c50993 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO for ; Sat, 12 May 2018 19:25:45 -0700 (PDT) To: FreeBSD Current From: Pete Wright Subject: suspend/resume regression Message-ID: <1e608109-fcdd-d794-b03a-2e417300b95a@nomadlogic.org> Date: Sat, 12 May 2018 19:25:44 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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: Sun, 13 May 2018 02:25:47 -0000 hi there - i have an amd64 laptop that's been running CURRENT for a while using both drm-next and drm-stable for graphics. during the past week or so i've run into issues with suspend resume...well technically resume has stopped working.  i've tested a couple configurations and none have allowed my system to resume successfully: - drm-next installed with DMC firmware loaded - drm-next installed without DMC firmware loaded (worked previously) - drm-stable with DMC - drm-stable without DMC - no drm modules loaded. I've also tested these configs with the following sysctl set to 0 and 1: hw.acpi.reset_video at this point i'd like to help find what the regression i'm running into is, so any pointers on how i can help? the system seems to boot and i'm pretty sure i can ssh into it most times, just not sure what info i should grab to help.  nothing of interest in messages or dmesg buffer either. cheers, -pete -- Pete Wright pete@nomadlogic.org @nomadlogicLA From owner-freebsd-current@freebsd.org Sun May 13 07:48:54 2018 Return-Path: Delivered-To: freebsd-current@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 D7795FCBEF8 for ; Sun, 13 May 2018 07:48:53 +0000 (UTC) (envelope-from agapon@gmail.com) Received: from mail-lf0-f53.google.com (mail-lf0-f53.google.com [209.85.215.53]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2F97168E52 for ; Sun, 13 May 2018 07:48:53 +0000 (UTC) (envelope-from agapon@gmail.com) Received: by mail-lf0-f53.google.com with SMTP id r2-v6so13563607lff.4 for ; Sun, 13 May 2018 00:48:53 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:openpgp:autocrypt :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=jQe612o0GeYa16qTSgPKqN46Zn/S1ILKpwn26ISYuGY=; b=Rix/2FUxtDiNn0tYgENo4g4mZ+kaAsV2lJykd71UuAb77ZcXAlEbVeI3ex/ZEvKP1K x0s+z1eGk7kB/d6TcjfR/x1h+2a3NCFfslaBRYAKGcgL1Ayhw2Le/Hn0so2zEHrZgmgD Zm1xw2dUaiEBBmXETHPfpLfSIuW+WLjol/Rdp2ukMvPkxxaC19oL06N3CevU8g0DwQSY 4tPQ0Jd9bjNzVnSIJjWr+dnWQdU0AWRTIa6Xkp6wNvPiz7ZC9Md8ngpWuBwaRkwJ2Urn nZ6Z8/SOChjD9YjEg459ZNlE/t0aFCXqLqMek6R5daFua8mI+hQeYHCuhcp8SCDUruxy /jRg== X-Gm-Message-State: ALKqPwet8Zwk93gdJeAwjs2Y36pq6MH9yFLN26U2ZN/lRUtFIggF+EGL avZmPgx6v1fbaHeWhQyQm9CZVgGj X-Google-Smtp-Source: AB8JxZq4UZNWsEfwGh120kHsDmPRSJVi0C97kOt0emgie3TUzSUaujSW+LYHRkBYgus0TW2dvVhkDg== X-Received: by 2002:a19:519a:: with SMTP id g26-v6mr5391767lfl.50.1526197725937; Sun, 13 May 2018 00:48:45 -0700 (PDT) Received: from [192.168.0.88] (east.meadow.volia.net. [93.72.151.96]) by smtp.googlemail.com with ESMTPSA id q68-v6sm1625227lfb.68.2018.05.13.00.48.45 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 13 May 2018 00:48:45 -0700 (PDT) Subject: Re: suspend/resume regression To: Pete Wright , FreeBSD Current References: <1e608109-fcdd-d794-b03a-2e417300b95a@nomadlogic.org> From: Andriy Gapon Openpgp: preference=signencrypt Autocrypt: addr=avg@FreeBSD.org; prefer-encrypt=mutual; keydata= xsFNBFm4LIgBEADNB/3lT7f15UKeQ52xCFQx/GqHkSxEdVyLFZTmY3KyNPQGBtyvVyBfprJ7 mAeXZWfhat6cKNRAGZcL5EmewdQuUfQfBdYmKjbw3a9GFDsDNuhDA2QwFt8BmkiVMRYyvI7l N0eVzszWCUgdc3qqM6qqcgBaqsVmJluwpvwp4ZBXmch5BgDDDb1MPO8AZ2QZfIQmplkj8Y6Z AiNMknkmgaekIINSJX8IzRzKD5WwMsin70psE8dpL/iBsA2cpJGzWMObVTtCxeDKlBCNqM1i gTXta1ukdUT7JgLEFZk9ceYQQMJJtUwzWu1UHfZn0Fs29HTqawfWPSZVbulbrnu5q55R4PlQ /xURkWQUTyDpqUvb4JK371zhepXiXDwrrpnyyZABm3SFLkk2bHlheeKU6Yql4pcmSVym1AS4 dV8y0oHAfdlSCF6tpOPf2+K9nW1CFA8b/tw4oJBTtfZ1kxXOMdyZU5fiG7xb1qDgpQKgHUX8 7Rd2T1UVLVeuhYlXNw2F+a2ucY+cMoqz3LtpksUiBppJhw099gEXehcN2JbUZ2TueJdt1FdS ztnZmsHUXLxrRBtGwqnFL7GSd6snpGIKuuL305iaOGODbb9c7ne1JqBbkw1wh8ci6vvwGlzx rexzimRaBzJxlkjNfMx8WpCvYebGMydNoeEtkWldtjTNVsUAtQARAQABzR5BbmRyaXkgR2Fw b24gPGF2Z0BGcmVlQlNELm9yZz7CwZQEEwEIAD4WIQS+LEO7ngQnXA4Bjr538m7TUc1yjwUC WbgsiAIbIwUJBaOagAULCQgHAgYVCAkKCwIEFgIDAQIeAQIXgAAKCRB38m7TUc1yj+JAEACV l9AK/nOWAt/9cufV2fRj0hdOqB1aCshtSrwHk/exXsDa4/FkmegxXQGY+3GWX3deIyesbVRL rYdtdK0dqJyT1SBqXK1h3/at9rxr9GQA6KWOxTjUFURsU7ok/6SIlm8uLRPNKO+yq0GDjgaO LzN+xykuBA0FlhQAXJnpZLcVfPJdWv7sSHGedL5ln8P8rxR+XnmsA5TUaaPcbhTB+mG+iKFj GghASDSfGqLWFPBlX/fpXikBDZ1gvOr8nyMY9nXhgfXpq3B6QCRYKPy58ChrZ5weeJZ29b7/ QdEO8NFNWHjSD9meiLdWQaqo9Y7uUxN3wySc/YUZxtS0bhAd8zJdNPsJYG8sXgKjeBQMVGuT eCAJFEYJqbwWvIXMfVWop4+O4xB+z2YE3jAbG/9tB/GSnQdVSj3G8MS80iLS58frnt+RSEw/ psahrfh0dh6SFHttE049xYiC+cM8J27Aaf0i9RflyITq57NuJm+AHJoU9SQUkIF0nc6lfA+o JRiyRlHZHKoRQkIg4aiKaZSWjQYRl5Txl0IZUP1dSWMX4s3XTMurC/pnja45dge/4ESOtJ9R 8XuIWg45Oq6MeIWdjKddGhRj3OohsltKgkEU3eLKYtB6qRTQypHHUawCXz88uYt5e3w4V16H lCpSTZV/EVHnNe45FVBlvK7k7HFfDDkryM7BTQRZuCyIARAAlq0slcsVboY/+IUJdcbEiJRW be9HKVz4SUchq0z9MZPX/0dcnvz/gkyYA+OuM78dNS7Mbby5dTvOqfpLJfCuhaNYOhlE0wY+ 1T6Tf1f4c/uA3U/YiadukQ3+6TJuYGAdRZD5EqYFIkreARTVWg87N9g0fT9BEqLw9lJtEGDY EWUE7L++B8o4uu3LQFEYxcrb4K/WKmgtmFcm77s0IKDrfcX4doV92QTIpLiRxcOmCC/OCYuO jB1oaaqXQzZrCutXRK0L5XN1Y1PYjIrEzHMIXmCDlLYnpFkK+itlXwlE2ZQxkfMruCWdQXye syl2fynAe8hvp7Mms9qU2r2K9EcJiR5N1t1C2/kTKNUhcRv7Yd/vwusK7BqJbhlng5ZgRx0m WxdntU/JLEntz3QBsBsWM9Y9wf2V4tLv6/DuDBta781RsCB/UrU2zNuOEkSixlUiHxw1dccI 6CVlaWkkJBxmHX22GdDFrcjvwMNIbbyfQLuBq6IOh8nvu9vuItup7qemDG3Ms6TVwA7BD3j+ 3fGprtyW8Fd/RR2bW2+LWkMrqHffAr6Y6V3h5kd2G9Q8ZWpEJk+LG6Mk3fhZhmCnHhDu6CwN MeUvxXDVO+fqc3JjFm5OxhmfVeJKrbCEUJyM8ESWLoNHLqjywdZga4Q7P12g8DUQ1mRxYg/L HgZY3zfKOqcAEQEAAcLBfAQYAQgAJhYhBL4sQ7ueBCdcDgGOvnfybtNRzXKPBQJZuCyIAhsM BQkFo5qAAAoJEHfybtNRzXKPBVwQAKfFy9P7N3OsLDMB56A4Kf+ZT+d5cIx0Yiaf4n6w7m3i ImHHHk9FIetI4Xe54a2IXh4Bq5UkAGY0667eIs+Z1Ea6I2i27Sdo7DxGwq09Qnm/Y65ADvXs 3aBvokCcm7FsM1wky395m8xUos1681oV5oxgqeRI8/76qy0hD9WR65UW+HQgZRIcIjSel9vR XDaD2HLGPTTGr7u4v00UeTMs6qvPsa2PJagogrKY8RXdFtXvweQFz78NbXhluwix2Tb9ETPk LIpDrtzV73CaE2aqBG/KrboXT2C67BgFtnk7T7Y7iKq4/XvEdDWscz2wws91BOXuMMd4c/c4 OmGW9m3RBLufFrOag1q5yUS9QbFfyqL6dftJP3Zq/xe+mr7sbWbhPVCQFrH3r26mpmy841ym dwQnNcsbIGiBASBSKksOvIDYKa2Wy8htPmWFTEOPRpFXdGQ27awcjjnB42nngyCK5ukZDHi6 w0qK5DNQQCkiweevCIC6wc3p67jl1EMFY5+z+zdTPb3h7LeVnGqW0qBQl99vVFgzLxchKcl0 R/paSFgwqXCZhAKMuUHncJuynDOP7z5LirUeFI8qsBAJi1rXpQoLJTVcW72swZ42IdPiboqx NbTMiNOiE36GqMcTPfKylCbF45JNX4nF9ElM0E+Y8gi4cizJYBRr2FBJgay0b9Cp Message-ID: Date: Sun, 13 May 2018 10:48:44 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <1e608109-fcdd-d794-b03a-2e417300b95a@nomadlogic.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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: Sun, 13 May 2018 07:48:54 -0000 On 13/05/2018 05:25, Pete Wright wrote: > hi there - i have an amd64 laptop that's been running CURRENT for a while using > both drm-next and drm-stable for graphics. during the past week or so i've run > into issues with suspend resume...well technically resume has stopped working.  > i've tested a couple configurations and none have allowed my system to resume > successfully: > > - drm-next installed with DMC firmware loaded > - drm-next installed without DMC firmware loaded (worked previously) > - drm-stable with DMC > - drm-stable without DMC > - no drm modules loaded. > > I've also tested these configs with the following sysctl set to 0 and 1: > hw.acpi.reset_video > > at this point i'd like to help find what the regression i'm running into is, so > any pointers on how i can help? the system seems to boot and i'm pretty sure i > can ssh into it most times, just not sure what info i should grab to help.  > nothing of interest in messages or dmesg buffer either. Did you do any OS upgrades what was last working version and what is the current version (svn revision number)? Or any other notable changes before resume stopped working... -- Andriy Gapon From owner-freebsd-current@freebsd.org Sun May 13 09:54:49 2018 Return-Path: Delivered-To: freebsd-current@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 520BCFD1FCA for ; Sun, 13 May 2018 09:54:49 +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 C367F78E3E; Sun, 13 May 2018 09:54:48 +0000 (UTC) (envelope-from zeising+freebsd@daemonic.se) Received: from cid.daemonic.se (localhost [IPv6:::1]) by mail.daemonic.se (Postfix) with ESMTP id 40kK1f6YXMzDhG6; Sun, 13 May 2018 09:54:46 +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=1526205286; bh=J5S73eMsJ1GWjULibBlDs3q8 mv72teaGx881Yt0chiU=; b=ugL2yL6BwQzrDtjYz8vYVuTPn6PfwqVIW2sHEbTr l+/a8buC2YDzpoewO4ZYuvOtlUdavpuspXpliBWctFph7fpkW0p9nrfcXP4AdfAc hqaQtQTvleQ9Pf/GmFGqzKuqqaaKXMhqluAVuKN21zKOshSNnArZcLM3HkW4kbQa 4BI= 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 3k76arAYYKDW; Sun, 13 May 2018 09:54:46 +0000 (UTC) Received: from celes.daemonic.se (celes.daemonic.se [IPv6:2001:470:dca9:2::3]) by mail.daemonic.se (Postfix) with ESMTPSA id 40kK1f1xFwzDhBg; Sun, 13 May 2018 09:54:46 +0000 (UTC) Subject: Re: suspend/resume regression To: Andriy Gapon , Pete Wright , FreeBSD Current References: <1e608109-fcdd-d794-b03a-2e417300b95a@nomadlogic.org> From: Niclas Zeising Message-ID: Date: Sun, 13 May 2018 11:54:45 +0200 User-Agent: Mutt/1.5.21 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-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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: Sun, 13 May 2018 09:54:49 -0000 On 05/13/18 09:48, Andriy Gapon wrote: > On 13/05/2018 05:25, Pete Wright wrote: >> hi there - i have an amd64 laptop that's been running CURRENT for a while using >> both drm-next and drm-stable for graphics. during the past week or so i've run >> into issues with suspend resume...well technically resume has stopped working. >> i've tested a couple configurations and none have allowed my system to resume >> successfully: >> >> - drm-next installed with DMC firmware loaded >> - drm-next installed without DMC firmware loaded (worked previously) >> - drm-stable with DMC >> - drm-stable without DMC >> - no drm modules loaded. >> >> I've also tested these configs with the following sysctl set to 0 and 1: >> hw.acpi.reset_video >> >> at this point i'd like to help find what the regression i'm running into is, so >> any pointers on how i can help? the system seems to boot and i'm pretty sure i >> can ssh into it most times, just not sure what info i should grab to help. >> nothing of interest in messages or dmesg buffer either. > > Did you do any OS upgrades what was last working version and what is the current > version (svn revision number)? > Or any other notable changes before resume stopped working... > Hi! I'm also seeing issues, not as severe as Pete, but after I resume (which works, with drm-next and DMC firmware), the system becomes sluggish. It feels like I/O takes more time, and graphics are sluggish (very sientific, I know, but for instance git operations are much slower after a resume). I know there's been an update to acpica between my system updates, when this started to happen, but I haven't had time to revert that update and test again. I will try to do that and report back. Regards -- Niclas From owner-freebsd-current@freebsd.org Sun May 13 15:58:14 2018 Return-Path: Delivered-To: freebsd-current@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 03252FADA4C for ; Sun, 13 May 2018 15:58:14 +0000 (UTC) (envelope-from theron.tarigo@gmail.com) Received: from mail-qk0-x231.google.com (mail-qk0-x231.google.com [IPv6:2607:f8b0:400d:c09::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 864FC697C6; Sun, 13 May 2018 15:58:13 +0000 (UTC) (envelope-from theron.tarigo@gmail.com) Received: by mail-qk0-x231.google.com with SMTP id c11-v6so8157029qkm.0; Sun, 13 May 2018 08:58:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:subject:to:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=2P1bf7HXLLZeW/6fxH0rZ3z0CDSPoJwpaMXBvePmFgQ=; b=cQG7aR7vdGqiOhEGnaq6f5zif0XjHIsNpJ+1R1d4fKkQ3n3rqE233GOWhCO8GURDss Pe+pkBQ0HF1hiyX1e50BbR9BkMcyiOpjiAR89/Sa0k8xwgLVm0sHm3/j/XcKfBKENn4A aEsp4Pv/igoBRoU5KtGE9CwelW2MlxxrdOQKutYOv2ampiZFduvV436V0+zjK5qbrS0t GWYjs7paksa+vaR/Gq+VI5+4nkiQjQngEUPPJzNmrR38wJyiFxlq2lFGCLJ/6PvpMh1t 7kw7CztrfZKihPOrRMU7MZ6tvIZN8JQhw/ltOL+c4/09VAgHTswyEFrYYTvZz8LWmxFz GbCg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:subject:to:references:from:message-id :date:user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=2P1bf7HXLLZeW/6fxH0rZ3z0CDSPoJwpaMXBvePmFgQ=; b=IInLvyGy3EPAI0e+N410AEeuLilwkQ5faav5qTbEJez1/OCqdevQwW82CGrjXyQvWr SW3xTXQeC61wtLVYpeFUjhMc/Jgo8xaY/1rlOMlzOefO0BpSahCYvrppssB4Iwx8LFOx Z1lwJHPrsxE+NZ3vtlC8ZbrHbwEQykmHr+MuBhPJH0NZkVFumNgku2Ujp8sJOy2L9XJg 3Yo3S86Il8G+G9p8CblxggomahZ3ZScCgUf+VjvrP6Z5wvX+5tLhn0aY7jPmyMqzfANF hpt35mUh1xgZsOetW6TWjIS4slQ22hu6+r+XjOsYUly34t65R5Y4owOFio/waTsm5gJ2 xaXA== X-Gm-Message-State: ALKqPweDx572eg5chQlNJvDpkqiYx4vZozyFCHYLYgtCH2Zg6LdwOsm6 oTsk8KtN6vImonSckMbIU07Vt8KKMYg= X-Google-Smtp-Source: AB8JxZosacRLZ8Zz/I81z1kSSxS33xB2kY8q+dRqyMq7+yWOG46aAo4tqEGDTcx0tJFpZmZS1swMHw== X-Received: by 2002:a37:b384:: with SMTP id c126-v6mr5085964qkf.160.1526227092943; Sun, 13 May 2018 08:58:12 -0700 (PDT) Received: from [10.0.0.163] (c-65-96-175-209.hsd1.ma.comcast.net. [65.96.175.209]) by smtp.gmail.com with ESMTPSA id l75-v6sm5479346qke.81.2018.05.13.08.58.12 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 13 May 2018 08:58:12 -0700 (PDT) Sender: Theron Tarigo Subject: Re: suspend/resume regression To: Niclas Zeising , Andriy Gapon , Pete Wright , FreeBSD Current References: <1e608109-fcdd-d794-b03a-2e417300b95a@nomadlogic.org> From: Theron Message-ID: <3488a8a4-8cad-d6a8-0852-3bbbdd971c7f@gmail.com> Date: Sun, 13 May 2018 11:58:11 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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: Sun, 13 May 2018 15:58:14 -0000 > Hi! > I'm also seeing issues, not as severe as Pete, but after I resume > (which works, with drm-next and DMC firmware), the system becomes > sluggish.  It feels like I/O takes more time, and graphics are > sluggish (very sientific, I know, but for instance git operations are > much slower after a resume).  I know there's been an update to acpica > between my system updates, when this started to happen, but I haven't > had time to revert that update and test again.  I will try to do that > and report back. > Regards Hi Niclas, I used drm-next on Skylake with issues which sound similar. Resuming from suspend, or simply switching the laptop display output off and on from xrandr, resulted in graphics sluggishness (drop to 30fps in glxgears) and graphical corruption in Xorg apps, which persisted even after restarting these apps.  Switching to drm-stable made the problems go away; I haven't had time to figure out what -next is doing differently to cause them. Pete's issue sounds more severe, and unrelated as it happens without drm loaded.  My kernel is two weeks out of date (r333093), so I need to check whether the more recent changes affect my system as well. Theron From owner-freebsd-current@freebsd.org Sun May 13 17:27:14 2018 Return-Path: Delivered-To: freebsd-current@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 6A311FC5986 for ; Sun, 13 May 2018 17:27:14 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from vps-mail.nomadlogic.org (mail.nomadlogic.org [IPv6:2607:f2f8:a098::2]) (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 CF37D770B5; Sun, 13 May 2018 17:27:13 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from [192.168.2.7] (cpe-23-243-163-13.socal.res.rr.com [23.243.163.13]) by vps-mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id 92383b6b TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO; Sun, 13 May 2018 10:27:11 -0700 (PDT) Subject: Re: suspend/resume regression To: Theron , Niclas Zeising , Andriy Gapon , FreeBSD Current References: <1e608109-fcdd-d794-b03a-2e417300b95a@nomadlogic.org> <3488a8a4-8cad-d6a8-0852-3bbbdd971c7f@gmail.com> From: Pete Wright Message-ID: <26f5ec31-3994-eac9-0c43-6d2458c35ad0@nomadlogic.org> Date: Sun, 13 May 2018 10:27:11 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <3488a8a4-8cad-d6a8-0852-3bbbdd971c7f@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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: Sun, 13 May 2018 17:27:14 -0000 On 05/13/2018 08:58, Theron wrote: >> Hi! >> I'm also seeing issues, not as severe as Pete, but after I resume >> (which works, with drm-next and DMC firmware), the system becomes >> sluggish.  It feels like I/O takes more time, and graphics are >> sluggish (very sientific, I know, but for instance git operations are >> much slower after a resume).  I know there's been an update to acpica >> between my system updates, when this started to happen, but I haven't >> had time to revert that update and test again.  I will try to do that >> and report back. >> Regards > Hi Niclas, > I used drm-next on Skylake with issues which sound similar. Resuming > from suspend, or simply switching the laptop display output off and on > from xrandr, resulted in graphics sluggishness (drop to 30fps in > glxgears) and graphical corruption in Xorg apps, which persisted even > after restarting these apps.  Switching to drm-stable made the > problems go away; I haven't had time to figure out what -next is doing > differently to cause them. > > Pete's issue sounds more severe, and unrelated as it happens without > drm loaded.  My kernel is two weeks out of date (r333093), so I need > to check whether the more recent changes affect my system as well. > so i've done a bit more debugging on my end.  i've even installed the 11.2-BETA branch last night since 11-STABLE worked without issues about a month or so ago. i've set "debug.acpi.resume_beep=1" and when resuming after entering an S3 sleep state the bell rings and does not stop until i do a hard reset (both with i915kms loaded and unloaded). kinda at a loss as to how this could break both CURRENT and basically 11-STABLE.  i'm going to make a ubuntu live image and test that, my laptop is a System76 laptop that shipped with ubuntu originally.  if that is broken as well then i guess this could be a hardware issue. the good news is that 11.2-BETA and drm-next works great (aside from suspend/resume) :) -p -- Pete Wright pete@nomadlogic.org @nomadlogicLA From owner-freebsd-current@freebsd.org Sun May 13 18:03:06 2018 Return-Path: Delivered-To: freebsd-current@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 63D7CFC8823 for ; Sun, 13 May 2018 18:03:06 +0000 (UTC) (envelope-from freebsd@grem.de) Received: from mail.grem.de (outcast.grem.de [213.239.217.27]) by mx1.freebsd.org (Postfix) with SMTP id D46857F837 for ; Sun, 13 May 2018 18:03:05 +0000 (UTC) (envelope-from freebsd@grem.de) Received: (qmail 99966 invoked by uid 89); 13 May 2018 16:16:22 -0000 Received: from unknown (HELO ?192.168.250.192?) (mg@grem.de@93.104.91.248) by mail.grem.de with ESMTPA; 13 May 2018 16:16:22 -0000 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) Subject: Re: suspend/resume regression From: Michael Gmelin X-Mailer: iPhone Mail (15E302) In-Reply-To: Date: Sun, 13 May 2018 18:16:21 +0200 Cc: Andriy Gapon , Pete Wright , FreeBSD Current Content-Transfer-Encoding: quoted-printable Message-Id: <7591CD82-3691-4153-AEC0-F7335417AC3B@grem.de> References: <1e608109-fcdd-d794-b03a-2e417300b95a@nomadlogic.org> To: Niclas Zeising X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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: Sun, 13 May 2018 18:03:06 -0000 > On 13. May 2018, at 11:54, Niclas Zeising wr= ote: >=20 >> On 05/13/18 09:48, Andriy Gapon wrote: >>> On 13/05/2018 05:25, Pete Wright wrote: >>> hi there - i have an amd64 laptop that's been running CURRENT for a whil= e using >>> both drm-next and drm-stable for graphics. during the past week or so i'= ve run >>> into issues with suspend resume...well technically resume has stopped wo= rking. >>> i've tested a couple configurations and none have allowed my system to r= esume >>> successfully: >>>=20 >>> - drm-next installed with DMC firmware loaded >>> - drm-next installed without DMC firmware loaded (worked previously) >>> - drm-stable with DMC >>> - drm-stable without DMC >>> - no drm modules loaded. >>>=20 >>> I've also tested these configs with the following sysctl set to 0 and 1:= >>> hw.acpi.reset_video >>>=20 >>> at this point i'd like to help find what the regression i'm running into= is, so >>> any pointers on how i can help? the system seems to boot and i'm pretty s= ure i >>> can ssh into it most times, just not sure what info i should grab to hel= p. >>> nothing of interest in messages or dmesg buffer either. >> Did you do any OS upgrades what was last working version and what is the c= urrent >> version (svn revision number)? >> Or any other notable changes before resume stopped working... >=20 > Hi! > I'm also seeing issues, not as severe as Pete, but after I resume (which w= orks, with drm-next and DMC firmware), the system becomes sluggish. It feel= s like I/O takes more time, and graphics are sluggish (very sientific, I kno= w, but for instance git operations are much slower after a resume). I know t= here's been an update to acpica between my system updates, when this started= to happen, but I haven't had time to revert that update and test again. I w= ill try to do that and report back. Maybe a stupid question, but did you check the cpu frequency before and afte= r suspend/resume? (sysctl dev.cpu) Best, Michael From owner-freebsd-current@freebsd.org Sun May 13 19:17:05 2018 Return-Path: Delivered-To: freebsd-current@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 B27E8FCD579 for ; Sun, 13 May 2018 19:17:05 +0000 (UTC) (envelope-from jhs@berklix.com) 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 3E2746E6A5 for ; Sun, 13 May 2018 19:17:05 +0000 (UTC) (envelope-from jhs@berklix.com) Received: by mailman.ysv.freebsd.org (Postfix) id F1FC7FCD578; Sun, 13 May 2018 19:17:04 +0000 (UTC) Delivered-To: current@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 E04E5FCD577 for ; Sun, 13 May 2018 19:17:04 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from land.berklix.org (land.berklix.org [144.76.10.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "land.berklix.org", Issuer "land.berklix.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 565556E6A4 for ; Sun, 13 May 2018 19:17:03 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from mart.js.berklix.net (pD9FA824B.dip0.t-ipconnect.de [217.250.130.75]) (authenticated bits=0) by land.berklix.org (8.15.2/8.15.2) with ESMTPSA id w4DIPCS4024782 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sun, 13 May 2018 18:25:16 GMT (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by mart.js.berklix.net (8.14.3/8.14.3) with ESMTP id w4DIQo6p068197 for ; Sun, 13 May 2018 20:26:51 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.7/8.14.7) with ESMTP id w4DIQcYZ060477 for ; Sun, 13 May 2018 20:26:50 +0200 (CEST) (envelope-from jhs@berklix.com) Message-Id: <201805131826.w4DIQcYZ060477@fire.js.berklix.net> To: current@freebsd.org Subject: cd /sys/amd64/compile/GENERIC;make cleandepend; make cleandepend From: "Julian H. Stacey" Organization: http://berklix.eu BSD Linux Unix Consultants, Munich Germany User-agent: EXMH on FreeBSD http://www.berklix.eu/free/ X-From: http://www.berklix.eu/~jhs/ Date: Sun, 13 May 2018 20:26:38 +0200 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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: Sun, 13 May 2018 19:17:05 -0000 Hi current@ Any ideas please on a problem with a current kernel from a day or 2 ago, & after a make world: uname -a FreeBSD lapr.js.berklix.net 12.0-CURRENT FreeBSD 12.0-CURRENT #0: Sat May 12 13:37:23 CEST 2018 jhs@lapr.js.berklix.net:/data/release/s4/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 cd /sys/amd64/compile/GENERIC make cleandepend make: "../../../conf/../../../conf/kern.pre.mk" line 125: amd64 kernel requires linker ifunc support /etc/make.conf : .include "/site/domain/this/etc/make.conf" .include "/site/etc/make.conf.sasl" DEFAULT_VERSIONS+=ssl=openssl All commented out & I still see it. /etc/src.conf : WITH_RCMDS=YES I updated to .svn_revision 333575 .ctm_status src-cur 13520 Patched out /usr/src/sys/conf/kern.pre.mk # .error amd64 kernel requires linker ifunc support make depend && make all && make install linking kernel.full iflib.o:(.rodata+0x178): undefined reference to `noop_attach' iflib.o:(.rodata+0x188): undefined reference to `iflib_pseudo_detach' find . -name \*iflib\* | sort| xargs ls -l -rw-r--r-- 1 jhs staff 0 May 13 16:28 ./amd64/compile/GENERIC/opt_iflib.h -rw-r--r-- 1 root staff 4651 May 13 18:35 ./amd64/compile/LAPR.small/.depend.iflib.o -rw-r--r-- 1 root staff 648592 May 13 18:35 ./amd64/compile/LAPR.small/iflib.o -rw-r--r-- 1 jhs staff 0 May 12 17:29 ./amd64/compile/LAPR.small/opt_iflib.h -rw-r--r-- 1 jhs staff 174046 May 13 16:31 ./net/iflib.c -rw-r--r-- 1 jhs staff 13187 May 13 16:31 ./net/iflib.h -rw-r--r-- 1 jhs staff 7674 May 13 16:31 ./net/iflib_clone.c -rw-r--r-- 1 jhs staff 2480 May 13 16:31 ./net/iflib_private.h /usr/src/UPDATING last ref. to iflib is way back: 20170112 Cheers, Julian -- Julian Stacey, Computer Consultant, Systems Engineer, BSD Linux Unix, Munich Brexit Referendum stole 3,700,000 votes, inc. 700,000 from British in EU. UK Govt. lied it's "democratic" in Article 50 letter to EU paragraph 3. Petition for votes: http://berklix.eu/queen/ From owner-freebsd-current@freebsd.org Sun May 13 19:44:31 2018 Return-Path: Delivered-To: freebsd-current@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 519A0FCEF0F for ; Sun, 13 May 2018 19:44:31 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from vps-mail.nomadlogic.org (mail.nomadlogic.org [IPv6:2607:f2f8:a098::2]) (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 B88E374589; Sun, 13 May 2018 19:44:30 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from [192.168.2.9] (cpe-23-243-163-13.socal.res.rr.com [23.243.163.13]) by vps-mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id 3fedb49e TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO; Sun, 13 May 2018 12:44:27 -0700 (PDT) Subject: Re: suspend/resume regression From: Pete Wright To: Theron , Niclas Zeising , Andriy Gapon , FreeBSD Current References: <1e608109-fcdd-d794-b03a-2e417300b95a@nomadlogic.org> <3488a8a4-8cad-d6a8-0852-3bbbdd971c7f@gmail.com> <26f5ec31-3994-eac9-0c43-6d2458c35ad0@nomadlogic.org> Message-ID: <9f7fcdaa-99ea-98f4-8ef3-c8da6060542e@nomadlogic.org> Date: Sun, 13 May 2018 12:44:26 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <26f5ec31-3994-eac9-0c43-6d2458c35ad0@nomadlogic.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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: Sun, 13 May 2018 19:44:31 -0000 On 05/13/2018 10:27, Pete Wright wrote: > > > On 05/13/2018 08:58, Theron wrote: >>> Hi! >>> I'm also seeing issues, not as severe as Pete, but after I resume >>> (which works, with drm-next and DMC firmware), the system becomes >>> sluggish.  It feels like I/O takes more time, and graphics are >>> sluggish (very sientific, I know, but for instance git operations >>> are much slower after a resume).  I know there's been an update to >>> acpica between my system updates, when this started to happen, but I >>> haven't had time to revert that update and test again.  I will try >>> to do that and report back. >>> Regards >> Hi Niclas, >> I used drm-next on Skylake with issues which sound similar. Resuming >> from suspend, or simply switching the laptop display output off and >> on from xrandr, resulted in graphics sluggishness (drop to 30fps in >> glxgears) and graphical corruption in Xorg apps, which persisted even >> after restarting these apps. Switching to drm-stable made the >> problems go away; I haven't had time to figure out what -next is >> doing differently to cause them. >> >> Pete's issue sounds more severe, and unrelated as it happens without >> drm loaded.  My kernel is two weeks out of date (r333093), so I need >> to check whether the more recent changes affect my system as well. >> > so i've done a bit more debugging on my end.  i've even installed the > 11.2-BETA branch last night since 11-STABLE worked without issues > about a month or so ago. > > i've set "debug.acpi.resume_beep=1" and when resuming after entering > an S3 sleep state the bell rings and does not stop until i do a hard > reset (both with i915kms loaded and unloaded). > > kinda at a loss as to how this could break both CURRENT and basically > 11-STABLE.  i'm going to make a ubuntu live image and test that, my > laptop is a System76 laptop that shipped with ubuntu originally.  if > that is broken as well then i guess this could be a hardware issue. > ubuntu live image suspends/resumes without issue so this certainly seems to be a freebsd issue unfortunately.  i guess next step is to attempt to find a working CURRENT snapshot that does suspend/resume without issue then start looking at commits? -pete -- Pete Wright pete@nomadlogic.org @nomadlogicLA From owner-freebsd-current@freebsd.org Sun May 13 20:20:36 2018 Return-Path: Delivered-To: freebsd-current@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 B55FEFD0BE1 for ; Sun, 13 May 2018 20:20:36 +0000 (UTC) (envelope-from freebsd-current@textmail.me) Received: from mail.codevoid.de (brews.the.best.midnight.coffee [176.9.40.102]) by mx1.freebsd.org (Postfix) with ESMTP id 516B97D8EA for ; Sun, 13 May 2018 20:20:35 +0000 (UTC) (envelope-from freebsd-current@textmail.me) Received: from localhost (HSI-KBW-37-49-77-182.hsi14.kabel-badenwuerttemberg.de [37.49.77.182]) by mail.codevoid.de (Postfix) with ESMTPSA id 741AD15B29 for ; Sun, 13 May 2018 22:11:15 +0200 (CEST) MIME-Version: 1.0 Date: Sun, 13 May 2018 22:13:45 +0200 From: Stefan Hagen To: freebsd-current@freebsd.org Subject: How to access SIGWINCH? Message-ID: <20180513201344.GA34676@ptrace.hagen.corp> Mail-Followup-To: freebsd-current@freebsd.org Precedence: first-class Priority: normal X-Editor: VIM - Vi IMproved 8.0 X-Operating-System: FreeBSD 12.0-CURRENT amd64 X-Mailer: Mutt 1.9.5 (2018-04-13) X-PGP-Fingerprint: 4192 8A31 504A D6D6 6167 2C3C 1AFE 4370 883F CC91 OpenPGP: id=883FCC91; url=https://pgp.ptrace.org; preference=sign User-Agent: Mutt/1.9.5 (2018-04-13) Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 May 2018 20:20:36 -0000 Hello, I'm wondering how to get access to to the SIGWINCH signal. It is defined in /usr/include/sys/signal.h and behind the -D__BSD_VISIBLE switch. I can compile my code with this switch, but is this the proper way to do it? I would expect something like this behind -D_BSD_SOURCE or -D_XOPEN_SOURCE=700. What's the right way to access this signal? Best Regards, Stefan -- Stefan Hagen Phone: +49 (0)176 642 925 17 Defender of RFC 1855 | PGP Key in Header. From owner-freebsd-current@freebsd.org Sun May 13 20:36:45 2018 Return-Path: Delivered-To: freebsd-current@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 B2AC6FD1AE9 for ; Sun, 13 May 2018 20:36:45 +0000 (UTC) (envelope-from freebsd-current@textmail.me) Received: from mail.codevoid.de (brews.the.best.midnight.coffee [176.9.40.102]) by mx1.freebsd.org (Postfix) with ESMTP id 439E480CC0 for ; Sun, 13 May 2018 20:36:44 +0000 (UTC) (envelope-from freebsd-current@textmail.me) Received: from localhost (HSI-KBW-37-49-77-182.hsi14.kabel-badenwuerttemberg.de [37.49.77.182]) by mail.codevoid.de (Postfix) with ESMTPSA id D294115148 for ; Sun, 13 May 2018 22:34:12 +0200 (CEST) MIME-Version: 1.0 Date: Sun, 13 May 2018 22:36:42 +0200 From: Stefan Hagen To: freebsd-current@freebsd.org Subject: Re: How to access SIGWINCH? Message-ID: <20180513203642.GA35071@ptrace.hagen.corp> Mail-Followup-To: freebsd-current@freebsd.org References: <20180513201344.GA34676@ptrace.hagen.corp> In-Reply-To: <20180513201344.GA34676@ptrace.hagen.corp> Precedence: first-class Priority: normal X-Editor: VIM - Vi IMproved 8.0 X-Operating-System: FreeBSD 12.0-CURRENT amd64 X-Mailer: Mutt 1.9.5 (2018-04-13) X-PGP-Fingerprint: 4192 8A31 504A D6D6 6167 2C3C 1AFE 4370 883F CC91 OpenPGP: id=883FCC91; url=https://pgp.ptrace.org; preference=sign User-Agent: Mutt/1.9.5 (2018-04-13) Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 May 2018 20:36:45 -0000 Stefan Hagen wrote: > I can compile my code with this switch, but is this the proper way to do it? > I would expect something like this behind -D_BSD_SOURCE or > -D_XOPEN_SOURCE=700. Answering myself. I had -D_XOPEN_SOURCE=700 defined which essentially blocks access to SIGWINCH. Not defining -D_XOPEN_SOURCE on FreeBSD fixed my issue. Best Regards, Stefan -- Stefan Hagen Phone: +49 (0)176 642 925 17 Defender of RFC 1855 | PGP Key in Header. From owner-freebsd-current@freebsd.org Sun May 13 21:00:54 2018 Return-Path: Delivered-To: freebsd-current@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 B1277FD301E for ; Sun, 13 May 2018 21:00:54 +0000 (UTC) (envelope-from rysto32@gmail.com) 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 4169186B01 for ; Sun, 13 May 2018 21:00:54 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 007D2FD3013; Sun, 13 May 2018 21:00:54 +0000 (UTC) Delivered-To: current@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 E35BAFD3010 for ; Sun, 13 May 2018 21:00:53 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: from mail-qt0-x229.google.com (mail-qt0-x229.google.com [IPv6:2607:f8b0:400d:c0d::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 299CA86AE2 for ; Sun, 13 May 2018 21:00:52 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: by mail-qt0-x229.google.com with SMTP id q6-v6so13730908qtn.3 for ; Sun, 13 May 2018 14:00:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=MuugEDwFfS2J5tEyE7ieN2mVJSWUewcoBFZec4T3yfM=; b=ewXuHQe+Smpw7qcbMeT3Xzl/augKN/KD2bzHL/lDrL3yiguVpo6fnVAXUQG4aoIrQ1 e4VyRt7aZGD9i78TOS+qZ2dIySJLhHJNPLyDFQy+AP6XcOaBGK52DKxvYbZ8eUBT+/Hs ROWjYRpH406SZ3SlDjpkjYtG9dr4rb3k9QKaoNdf6+WYkYrYdCZkUn8zFUt8SQ43iJtn iNvn+OZuNy38kQfRwWYC+/o5yhADgKNOWMK0qz4CvCuqbQ14Frd6Ps7+A/UdhqU6qzKl tH5egZiDvwuIxnIDhw7BoeaoeY0uy3V4GrjwMTuvCIP33gDPykaV9lPtnpGQQAVQlnch lDUw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=MuugEDwFfS2J5tEyE7ieN2mVJSWUewcoBFZec4T3yfM=; b=tArOX1FcZb1rRW0rr44MkXK3OTUSNof0VC060CUEdE/KB1E1bw4bPoARctVzMyXg8I 07Y6DLtB0rDw+4xzV0+MF/wG6QptKVN08kBSL6H7+rMJd/Gbb0P7u3TMJ5oCzMH3kCBS TiYpRUirbRo7dArdNc5MDuC82jAVb97CLvFVvAQcSbJ+T1tz+0XJIIfZ+0sceP+QpSea ekegWkDSwHvuX2tUFdxto13ZiwiMoANBFi4jCWMEoNDHDh8oG8ZYEpL6akaYkCFkWsmY hNKxJ/gHT94nzCnRLqqxIP7qkUtBKzZQADTk7iTi6/o2sQ1Nb+m6tJVRWRvUi5SKKm64 XrYg== X-Gm-Message-State: ALKqPwe0m8nHlRSOKl2dSjMscETly6Y3X83A3Oz28LJaO2vE69G1SJnS rfSYpKFyENMZFIds8z64XcTRKY4NOxlalM2lmOc= X-Google-Smtp-Source: AB8JxZqCjaHfmJFLaKgcsvZ26vL8t7zMWGerMb97l8NDrbrGw0zpsW0NLY57lnr6uUGMgTEuLyKghlPBwLw90yE0szA= X-Received: by 2002:a0c:fac2:: with SMTP id p2-v6mr6575002qvo.59.1526245251221; Sun, 13 May 2018 14:00:51 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:ac8:6707:0:0:0:0:0 with HTTP; Sun, 13 May 2018 14:00:50 -0700 (PDT) In-Reply-To: <201805131826.w4DIQcYZ060477@fire.js.berklix.net> References: <201805131826.w4DIQcYZ060477@fire.js.berklix.net> From: Ryan Stone Date: Sun, 13 May 2018 17:00:50 -0400 Message-ID: Subject: Re: cd /sys/amd64/compile/GENERIC;make cleandepend; make cleandepend To: "Julian H. Stacey" Cc: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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: Sun, 13 May 2018 21:00:54 -0000 Are you building with WITH_LD_IS_LLD=no? -CURRENT can no longer be built with a GPLv2 ld. You either have to use ldd or install a newer (GPLv3) binutils package. From owner-freebsd-current@freebsd.org Mon May 14 00:16:52 2018 Return-Path: Delivered-To: freebsd-current@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 3E2E2FDC38B for ; Mon, 14 May 2018 00:16:52 +0000 (UTC) (envelope-from jhs@berklix.com) 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 CC45F73F22 for ; Mon, 14 May 2018 00:16:51 +0000 (UTC) (envelope-from jhs@berklix.com) Received: by mailman.ysv.freebsd.org (Postfix) id 86411FDC382; Mon, 14 May 2018 00:16:51 +0000 (UTC) Delivered-To: current@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 73A28FDC380 for ; Mon, 14 May 2018 00:16:51 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from land.berklix.org (land.berklix.org [144.76.10.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "land.berklix.org", Issuer "land.berklix.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id EE61773F20 for ; Mon, 14 May 2018 00:16:50 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from mart.js.berklix.net (pD9FA824B.dip0.t-ipconnect.de [217.250.130.75]) (authenticated bits=0) by land.berklix.org (8.15.2/8.15.2) with ESMTPSA id w4E0Ep18038571 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 14 May 2018 00:15:09 GMT (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by mart.js.berklix.net (8.14.3/8.14.3) with ESMTP id w4E0GTgr070370; Mon, 14 May 2018 02:16:29 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.7/8.14.7) with ESMTP id w4E0GBKv001634; Mon, 14 May 2018 02:16:23 +0200 (CEST) (envelope-from jhs@berklix.com) Message-Id: <201805140016.w4E0GBKv001634@fire.js.berklix.net> To: Ryan Stone cc: FreeBSD Current Subject: Re: cd /sys/amd64/compile/GENERIC;make cleandepend; make cleandepend From: "Julian H. Stacey" Organization: http://berklix.eu BSD Unix Linux Consultants, Munich Germany User-agent: EXMH on FreeBSD http://berklix.eu/free/ X-From: http://www.berklix.eu/~jhs/ In-reply-to: Your message "Sun, 13 May 2018 17:00:50 -0400." Date: Mon, 14 May 2018 02:16:11 +0200 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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, 14 May 2018 00:16:52 -0000 Hi, Reference: > From: Ryan Stone > Date: Sun, 13 May 2018 17:00:50 -0400 Thanks for reply :-) Ryan Stone wrote: > Are you building with WITH_LD_IS_LLD=no? Not that I've set anywhere. Unless it comes from make world ? > -CURRENT can no longer be > built with a GPLv2 ld. You either have to use ldd or install a newer -r-xr-xr-x 1 root wheel 19352 May 13 12:52 /usr/bin/ldd* > (GPLv3) binutils package. pkg info | grep binutils binutils-2.30_3,1 GNU binary tools gnatdroid-binutils-2.27_1 Infrastructure for C/Ada Android cross-compiler (ARMv7) pkg upgrade The process will require 132 MiB more space. 569 MiB to be downloaded. I'll leave it running & report back later, Thanks Cheers, Julian -- Julian Stacey, Computer Consultant, Systems Engineer, BSD Linux Unix, Munich Brexit Referendum stole 3,700,000 votes, inc. 700,000 from British in EU. UK Govt. lied it's "democratic" in Article 50 letter to EU paragraph 3. Petition for votes: http://berklix.eu/queen/ From owner-freebsd-current@freebsd.org Sun May 13 22:16:30 2018 Return-Path: Delivered-To: freebsd-current@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 416AAFD6E5E for ; Sun, 13 May 2018 22:16:30 +0000 (UTC) (envelope-from wollman@hergotha.csail.mit.edu) Received: from hergotha.csail.mit.edu (wollman-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:ccb::2]) (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 D55AA76C91 for ; Sun, 13 May 2018 22:16:29 +0000 (UTC) (envelope-from wollman@hergotha.csail.mit.edu) Received: from hergotha.csail.mit.edu (localhost [127.0.0.1]) by hergotha.csail.mit.edu (8.15.2/8.15.2) with ESMTP id w4DMGSvE036743 for ; Sun, 13 May 2018 18:16:28 -0400 (EDT) (envelope-from wollman@hergotha.csail.mit.edu) Received: (from wollman@localhost) by hergotha.csail.mit.edu (8.15.2/8.14.4/Submit) id w4DMGSmb036742; Sun, 13 May 2018 18:16:28 -0400 (EDT) (envelope-from wollman) Date: Sun, 13 May 2018 18:16:28 -0400 (EDT) From: Garrett Wollman Message-Id: <201805132216.w4DMGSmb036742@hergotha.csail.mit.edu> To: freebsd-current@freebsd.org Subject: Re: How to access SIGWINCH? In-Reply-To: <20180513201344.GA34676@ptrace.hagen.corp> References: <20180513201344.GA34676@ptrace.hagen.corp> Organization: none Cc: X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.2 (hergotha.csail.mit.edu [127.0.0.1]); Sun, 13 May 2018 18:16:28 -0400 (EDT) X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED autolearn=disabled version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on hergotha.csail.mit.edu X-Mailman-Approved-At: Mon, 14 May 2018 01:28:43 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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: Sun, 13 May 2018 22:16:30 -0000 In article <20180513201344.GA34676@ptrace.hagen.corp> you write: >I'm wondering how to get access to to the SIGWINCH signal. It is defined in >/usr/include/sys/signal.h and behind the -D__BSD_VISIBLE switch. > >I can compile my code with this switch, but is this the proper way to do it? >I would expect something like this behind -D_BSD_SOURCE or >-D_XOPEN_SOURCE=700. > >What's the right way to access this signal? The right way is to *not* request strict adherence to a standard that doesn't include that signal. Do not define any of these macros and you will get SIGWINCH defined. The next POSIX revision will probably include SIGWINCH, so come 2022 you can define _POSIX_C_SOURCE to something like 202207 and get it. (I'm not actually certain when the next revision is planned to be released -- we just went through an IEEE-mandated reaffirmation cycle but I don't believe a new signal and the related data structures can be introduced in a technical corrigendum so it will have to wait for the next opportunity to do a full revision of standard, which will have to be agreed upon by IEEE, ISO/IEC JTC1, and The Open Group.) -GAWollman From owner-freebsd-current@freebsd.org Mon May 14 08:06:09 2018 Return-Path: Delivered-To: freebsd-current@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 527A1FDFA45 for ; Mon, 14 May 2018 08:06:09 +0000 (UTC) (envelope-from etnapierala@gmail.com) Received: from mail-wr0-x22e.google.com (mail-wr0-x22e.google.com [IPv6:2a00:1450:400c:c0c::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B5F81791FC; Mon, 14 May 2018 08:06:08 +0000 (UTC) (envelope-from etnapierala@gmail.com) Received: by mail-wr0-x22e.google.com with SMTP id 94-v6so11228272wrf.5; Mon, 14 May 2018 01:06:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:mail-followup-to :references:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=25bZsCsYRtVzBSXuq4yusu6ubWgwk2pGd5KM5YgvQEk=; b=h/jFJx7ZQOhnSDqCoBUAU122mXCpmjMdjDO4DBrq8NJ55GIRIFse+98xrZMumIqECv pP+xxtZLitYinqFdeWJ+cpC7FgVd3KO2cxKVC7iLc1GHICvNIn18EH+36qso9QzhNKps gMCAwuEtCnqF9hIYXwF7g8eJId1FThdyyisDyhRFpHRiKUtpRvh2+LfGEIUAYRqA3NV4 TYy4KzGd+/FtU4bwiFSamnYRxXIhujZwjSlFVBfBFBDVoo3z4LQYnDcDQUVBjmpqGfQx Ja3UAH3wh8DrxvaytduHstIckmY5zxLgEUvkgHzkLGkTUjDCc6WBDmlZfvUO/NW4gcCp BBcg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=25bZsCsYRtVzBSXuq4yusu6ubWgwk2pGd5KM5YgvQEk=; b=Qu8ZZmkVLX603iOq+4P0epxZxrMO4zRK1aLhfRBGB8W6NVl7tALLwtjJY+R6aJXxjt SywQ+ZkaJU6NjS2WnL13pUO3PcICDZ/YHhwiOlYvOK+hwuA88uUV8TammmL30qTAr6VR ZMR0Z09xX1hD4TT5r8y4r072vPixq2dMwhAEbWfGm+cQ9xCH1M60Yd3h/GHJUARc9O7P 6TKBBV2oEwkGbwuVWJALJEvrcoJdj4UwMB5IYG18ycBcJ8QyNslsBL/PdRqRNmWHdj/a mxsHrWpWOEM12OXeIbTq3fXTrI+hcokdg/B7ZDrv9NfRz5N6pej9nRdKmBEiLlkW23yJ fUNA== X-Gm-Message-State: ALKqPwfJYN6ij4UV98Ze51I46lQu8F894usFbDpxe4u0mxbm9FTqt96w YpFSeLZTOlg2ON4NU1oNbwY= X-Google-Smtp-Source: AB8JxZqWSWD/fnLYN06Vg9Yw3JGg1s5w5Op0As39lv9POqrjcm9ReN5NJKJik7jRXpM59LIqT+CbvQ== X-Received: by 2002:adf:ab0a:: with SMTP id q10-v6mr6036156wrc.239.1526285167577; Mon, 14 May 2018 01:06:07 -0700 (PDT) Received: from brick (cpc92302-cmbg19-2-0-cust461.5-4.cable.virginm.net. [82.1.209.206]) by smtp.gmail.com with ESMTPSA id q2-v6sm11098349wrj.57.2018.05.14.01.06.06 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 14 May 2018 01:06:06 -0700 (PDT) Sender: =?UTF-8?Q?Edward_Tomasz_Napiera=C5=82a?= Date: Mon, 14 May 2018 09:06:04 +0100 From: Edward Tomasz =?utf-8?Q?Napiera=C5=82a?= To: Pete Wright Cc: Theron , Niclas Zeising , Andriy Gapon , FreeBSD Current Subject: Re: suspend/resume regression Message-ID: <20180514080604.GA2006@brick> Mail-Followup-To: Pete Wright , Theron , Niclas Zeising , Andriy Gapon , FreeBSD Current References: <1e608109-fcdd-d794-b03a-2e417300b95a@nomadlogic.org> <3488a8a4-8cad-d6a8-0852-3bbbdd971c7f@gmail.com> <26f5ec31-3994-eac9-0c43-6d2458c35ad0@nomadlogic.org> <9f7fcdaa-99ea-98f4-8ef3-c8da6060542e@nomadlogic.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <9f7fcdaa-99ea-98f4-8ef3-c8da6060542e@nomadlogic.org> User-Agent: Mutt/1.9.5 (2018-04-13) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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, 14 May 2018 08:06:09 -0000 On 0513T1244, Pete Wright wrote: > > > On 05/13/2018 10:27, Pete Wright wrote: > > > > > > On 05/13/2018 08:58, Theron wrote: > >>> Hi! > >>> I'm also seeing issues, not as severe as Pete, but after I resume > >>> (which works, with drm-next and DMC firmware), the system becomes > >>> sluggish.  It feels like I/O takes more time, and graphics are > >>> sluggish (very sientific, I know, but for instance git operations > >>> are much slower after a resume).  I know there's been an update to > >>> acpica between my system updates, when this started to happen, but I > >>> haven't had time to revert that update and test again.  I will try > >>> to do that and report back. > >>> Regards > >> Hi Niclas, > >> I used drm-next on Skylake with issues which sound similar. Resuming > >> from suspend, or simply switching the laptop display output off and > >> on from xrandr, resulted in graphics sluggishness (drop to 30fps in > >> glxgears) and graphical corruption in Xorg apps, which persisted even > >> after restarting these apps. Switching to drm-stable made the > >> problems go away; I haven't had time to figure out what -next is > >> doing differently to cause them. > >> > >> Pete's issue sounds more severe, and unrelated as it happens without > >> drm loaded.  My kernel is two weeks out of date (r333093), so I need > >> to check whether the more recent changes affect my system as well. > >> > > so i've done a bit more debugging on my end.  i've even installed the > > 11.2-BETA branch last night since 11-STABLE worked without issues > > about a month or so ago. > > > > i've set "debug.acpi.resume_beep=1" and when resuming after entering > > an S3 sleep state the bell rings and does not stop until i do a hard > > reset (both with i915kms loaded and unloaded). > > > > kinda at a loss as to how this could break both CURRENT and basically > > 11-STABLE.  i'm going to make a ubuntu live image and test that, my > > laptop is a System76 laptop that shipped with ubuntu originally.  if > > that is broken as well then i guess this could be a hardware issue. > > > ubuntu live image suspends/resumes without issue so this certainly seems > to be a freebsd issue unfortunately.  i guess next step is to attempt to > find a working CURRENT snapshot that does suspend/resume without issue > then start looking at commits? FWIW, I'm seeing the same - sluggishness after resume - with stock 12-CURRENT, without drm-next, just vanilla i915kms.ko, on T420. TBH I'm not entirely sure it's X11 problem - as I'm writing it now, under vt(4), it seems somewhat slow too. From owner-freebsd-current@freebsd.org Mon May 14 08:18:57 2018 Return-Path: Delivered-To: freebsd-current@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 56AC1FE0473 for ; Mon, 14 May 2018 08:18:57 +0000 (UTC) (envelope-from zeising+freebsd@daemonic.se) Received: from mail.daemonic.se (mail.daemonic.se [176.58.89.161]) (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 E2BF07DA23; Mon, 14 May 2018 08:18:56 +0000 (UTC) (envelope-from zeising+freebsd@daemonic.se) Received: from cid.daemonic.se (localhost [IPv6:::1]) by mail.daemonic.se (Postfix) with ESMTP id 40ktrT1D19zDhS5; Mon, 14 May 2018 08:18:49 +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=1526285928; bh=Yf5JmyYHNmitrNQrMQ31c15U pFuRbWCodEbkjhABK2Y=; b=PiaB1MTLJjSxUup0N6iGOz+plX/jqSSNRAj+1DKC AZF5fq5njHQG6zIEqHUakM14gO/5zwUyxD9u2pSBmPB7LuZu1HrhDPz2/w4E+QPg WdUs8KZvtS29lhKfJ57PgsQjPd/Q6kLXamZSJ/k3pNfyKHhEMrGyMp1ShbgYX4Wz hMQ= 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 ooSul8_j2pnR; Mon, 14 May 2018 08:18:48 +0000 (UTC) Received: from garnet.daemonic.se (host-95-192-250-89.mobileonline.telia.com [95.192.250.89]) by mail.daemonic.se (Postfix) with ESMTPSA id 40ktrR6K8dzDhS4; Mon, 14 May 2018 08:18:47 +0000 (UTC) Subject: Re: suspend/resume regression To: Pete Wright , Theron , Andriy Gapon , FreeBSD Current References: <1e608109-fcdd-d794-b03a-2e417300b95a@nomadlogic.org> <3488a8a4-8cad-d6a8-0852-3bbbdd971c7f@gmail.com> <26f5ec31-3994-eac9-0c43-6d2458c35ad0@nomadlogic.org> <9f7fcdaa-99ea-98f4-8ef3-c8da6060542e@nomadlogic.org> From: Niclas Zeising Message-ID: <92bc7e50-2252-5e6a-cf2c-165ef5f6f2d3@daemonic.se> Date: Mon, 14 May 2018 10:18:35 +0200 User-Agent: Mutt/1.5.21 MIME-Version: 1.0 In-Reply-To: <9f7fcdaa-99ea-98f4-8ef3-c8da6060542e@nomadlogic.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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, 14 May 2018 08:18:57 -0000 On 05/13/18 21:44, Pete Wright wrote: >=20 >=20 > On 05/13/2018 10:27, Pete Wright wrote: >> >> >> On 05/13/2018 08:58, Theron wrote: >>>> Hi! >>>> I'm also seeing issues, not as severe as Pete, but after I resume=20 >>>> (which works, with drm-next and DMC firmware), the system becomes=20 >>>> sluggish.=C2=A0 It feels like I/O takes more time, and graphics are=20 >>>> sluggish (very sientific, I know, but for instance git operations=20 >>>> are much slower after a resume).=C2=A0 I know there's been an update= to=20 >>>> acpica between my system updates, when this started to happen, but I= =20 >>>> haven't had time to revert that update and test again.=C2=A0 I will = try=20 >>>> to do that and report back. >>>> Regards >>> Hi Niclas, >>> I used drm-next on Skylake with issues which sound similar. Resuming=20 >>> from suspend, or simply switching the laptop display output off and=20 >>> on from xrandr, resulted in graphics sluggishness (drop to 30fps in=20 >>> glxgears) and graphical corruption in Xorg apps, which persisted even= =20 >>> after restarting these apps. Switching to drm-stable made the=20 >>> problems go away; I haven't had time to figure out what -next is=20 >>> doing differently to cause them. >>> >>> Pete's issue sounds more severe, and unrelated as it happens without=20 >>> drm loaded.=C2=A0 My kernel is two weeks out of date (r333093), so I = need=20 >>> to check whether the more recent changes affect my system as well. >>> >> so i've done a bit more debugging on my end.=C2=A0 i've even installed= the=20 >> 11.2-BETA branch last night since 11-STABLE worked without issues=20 >> about a month or so ago. >> >> i've set "debug.acpi.resume_beep=3D1" and when resuming after entering= =20 >> an S3 sleep state the bell rings and does not stop until i do a hard=20 >> reset (both with i915kms loaded and unloaded). >> >> kinda at a loss as to how this could break both CURRENT and basically=20 >> 11-STABLE.=C2=A0 i'm going to make a ubuntu live image and test that, = my=20 >> laptop is a System76 laptop that shipped with ubuntu originally.=C2=A0= if=20 >> that is broken as well then i guess this could be a hardware issue. >> > ubuntu live image suspends/resumes without issue so this certainly seem= s=20 > to be a freebsd issue unfortunately.=C2=A0 i guess next step is to atte= mpt to=20 > find a working CURRENT snapshot that does suspend/resume without issue=20 > then start looking at commits? >=20 Hi! It's a bit worrisome that your regression occurs both on CURRENT and=20 STABLE. There was an update to both drm-next-kmod and drm-stable-kmod=20 last week, but both are very minor. One question, did you install from=20 pkg or compile from ports? Wrt. my own issues, I'm not entirely sure what's going on. I tried a=20 kernel from r333269 and that worked fine, however, r333340 did not.=20 I'll need to bisect exactly which revision causes my regression, with=20 slowness and lag after resume from sleep. Regards --=20 Niclas From owner-freebsd-current@freebsd.org Mon May 14 08:22:01 2018 Return-Path: Delivered-To: freebsd-current@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 89FFDFE0829 for ; Mon, 14 May 2018 08:22:01 +0000 (UTC) (envelope-from zeising+freebsd@daemonic.se) Received: from mail.daemonic.se (mail.daemonic.se [176.58.89.161]) (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 23AF67EDBE; Mon, 14 May 2018 08:22:00 +0000 (UTC) (envelope-from zeising+freebsd@daemonic.se) Received: from cid.daemonic.se (localhost [IPv6:::1]) by mail.daemonic.se (Postfix) with ESMTP id 40ktw75Yw6zDhG6; Mon, 14 May 2018 08:21:59 +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=1526286119; bh=B+pOGcO61riS/S/PQ4J3zeto vWkU5wZNoLakCQsJMCQ=; b=kUvHuSf3z5gTUuMNQugn8U57QmOF3DzHf7KMwk1W /0UGjM/ef7zlO/WADiQnx+xADRWXVP5AT02bvQ64qNpwvhBeNko/VCHqdj2NNwV+ mk7ORTYwysy2qb893+sdAuIfiDQ9Jce/xzootU73T00C0RBmXOHXqKweY8txxcqR aZY= 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 JOWJaThjSxWj; Mon, 14 May 2018 08:21:59 +0000 (UTC) Received: from garnet.daemonic.se (host-95-192-250-89.mobileonline.telia.com [95.192.250.89]) by mail.daemonic.se (Postfix) with ESMTPSA id 40ktw65H8YzDhBg; Mon, 14 May 2018 08:21:58 +0000 (UTC) Subject: Re: suspend/resume regression To: Michael Gmelin Cc: Andriy Gapon , Pete Wright , FreeBSD Current References: <1e608109-fcdd-d794-b03a-2e417300b95a@nomadlogic.org> <7591CD82-3691-4153-AEC0-F7335417AC3B@grem.de> From: Niclas Zeising Message-ID: <31ff347c-9e4e-ca17-4ef7-7c3e51c44e97@daemonic.se> Date: Mon, 14 May 2018 10:21:58 +0200 User-Agent: Mutt/1.5.21 MIME-Version: 1.0 In-Reply-To: <7591CD82-3691-4153-AEC0-F7335417AC3B@grem.de> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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, 14 May 2018 08:22:01 -0000 On 05/13/18 18:16, Michael Gmelin wrote: > > >> On 13. May 2018, at 11:54, Niclas Zeising wrote: >> >>> On 05/13/18 09:48, Andriy Gapon wrote: >>>> On 13/05/2018 05:25, Pete Wright wrote: >>>> hi there - i have an amd64 laptop that's been running CURRENT for a while using >>>> both drm-next and drm-stable for graphics. during the past week or so i've run >>>> into issues with suspend resume...well technically resume has stopped working. >>>> i've tested a couple configurations and none have allowed my system to resume >>>> successfully: >>>> >>>> - drm-next installed with DMC firmware loaded >>>> - drm-next installed without DMC firmware loaded (worked previously) >>>> - drm-stable with DMC >>>> - drm-stable without DMC >>>> - no drm modules loaded. >>>> >>>> I've also tested these configs with the following sysctl set to 0 and 1: >>>> hw.acpi.reset_video >>>> >>>> at this point i'd like to help find what the regression i'm running into is, so >>>> any pointers on how i can help? the system seems to boot and i'm pretty sure i >>>> can ssh into it most times, just not sure what info i should grab to help. >>>> nothing of interest in messages or dmesg buffer either. >>> Did you do any OS upgrades what was last working version and what is the current >>> version (svn revision number)? >>> Or any other notable changes before resume stopped working... >> >> Hi! >> I'm also seeing issues, not as severe as Pete, but after I resume (which works, with drm-next and DMC firmware), the system becomes sluggish. It feels like I/O takes more time, and graphics are sluggish (very sientific, I know, but for instance git operations are much slower after a resume). I know there's been an update to acpica between my system updates, when this started to happen, but I haven't had time to revert that update and test again. I will try to do that and report back. > > Maybe a stupid question, but did you check the cpu frequency before and after suspend/resume? (sysctl dev.cpu) As far as I can tell, the frequency remains the same. I looked at dev.cpu.0.freq, if there's any other sysctl to look at as well, please let me know. Regards -- Niclas From owner-freebsd-current@freebsd.org Mon May 14 08:23:45 2018 Return-Path: Delivered-To: freebsd-current@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 3F8B5FE09A6 for ; Mon, 14 May 2018 08:23:45 +0000 (UTC) (envelope-from zeising+freebsd@daemonic.se) Received: from mail.daemonic.se (mail.daemonic.se [176.58.89.161]) (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 CF5B27EFAE; Mon, 14 May 2018 08:23:44 +0000 (UTC) (envelope-from zeising+freebsd@daemonic.se) Received: from cid.daemonic.se (localhost [IPv6:::1]) by mail.daemonic.se (Postfix) with ESMTP id 40kty75NyyzDhS4; Mon, 14 May 2018 08:23:43 +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=1526286223; bh=KZLn+GJLCNstcDb4z0ajpHte +blqXSfpuHE+PbMGztY=; b=i3fBw/7rn8xktXTJcusXGY+EscSp3Q+XsudlCeCw bwpaHW7LxWeq8apLWhtlWmsX8blLnXjPQpuFWTcv0OvEUXgZN9I+eKJi3IUdGA9p 08aZKkdQHKiYt5wEzmCRR0UCWa/xozoZe47tkMx1YMpMiuzEeoLoHcEr17OIUFiW DIA= 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 QlBUko7o3Smv; Mon, 14 May 2018 08:23:43 +0000 (UTC) Received: from garnet.daemonic.se (host-95-192-250-89.mobileonline.telia.com [95.192.250.89]) by mail.daemonic.se (Postfix) with ESMTPSA id 40kty66YyqzDhBg; Mon, 14 May 2018 08:23:42 +0000 (UTC) Subject: Re: suspend/resume regression To: Theron , Andriy Gapon , Pete Wright , FreeBSD Current References: <1e608109-fcdd-d794-b03a-2e417300b95a@nomadlogic.org> <3488a8a4-8cad-d6a8-0852-3bbbdd971c7f@gmail.com> From: Niclas Zeising Message-ID: <4725b2ef-37c7-85eb-a2fa-8dd96d1d9ad6@daemonic.se> Date: Mon, 14 May 2018 10:23:42 +0200 User-Agent: Mutt/1.5.21 MIME-Version: 1.0 In-Reply-To: <3488a8a4-8cad-d6a8-0852-3bbbdd971c7f@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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, 14 May 2018 08:23:45 -0000 On 05/13/18 17:58, Theron wrote: >> Hi! >> I'm also seeing issues, not as severe as Pete, but after I resume=20 >> (which works, with drm-next and DMC firmware), the system becomes=20 >> sluggish.=C2=A0 It feels like I/O takes more time, and graphics are=20 >> sluggish (very sientific, I know, but for instance git operations are=20 >> much slower after a resume).=C2=A0 I know there's been an update to ac= pica=20 >> between my system updates, when this started to happen, but I haven't=20 >> had time to revert that update and test again.=C2=A0 I will try to do = that=20 >> and report back. >> Regards > Hi Niclas, > I used drm-next on Skylake with issues which sound similar. Resuming=20 > from suspend, or simply switching the laptop display output off and on=20 > from xrandr, resulted in graphics sluggishness (drop to 30fps in=20 > glxgears) and graphical corruption in Xorg apps, which persisted even=20 > after restarting these apps.=C2=A0 Switching to drm-stable made the pro= blems=20 > go away; I haven't had time to figure out what -next is doing=20 > differently to cause them. >=20 > Pete's issue sounds more severe, and unrelated as it happens without dr= m=20 > loaded.=C2=A0 My kernel is two weeks out of date (r333093), so I need t= o=20 > check whether the more recent changes affect my system as well. >=20 I have a Kaby Lake system. I haven't tried switching outputs with=20 xrandr, I have to do that as well. What versions of drm-next and=20 drm-stable have you tested? Regards --=20 Niclas From owner-freebsd-current@freebsd.org Mon May 14 08:28:02 2018 Return-Path: Delivered-To: freebsd-current@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 A4CF5FE0D4C for ; Mon, 14 May 2018 08:28:02 +0000 (UTC) (envelope-from zeising+freebsd@daemonic.se) Received: from mail.daemonic.se (mail.daemonic.se [176.58.89.161]) (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 3DBE280301; Mon, 14 May 2018 08:28:02 +0000 (UTC) (envelope-from zeising+freebsd@daemonic.se) Received: from cid.daemonic.se (localhost [IPv6:::1]) by mail.daemonic.se (Postfix) with ESMTP id 40kv351p6NzDhS4; Mon, 14 May 2018 08:28:01 +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=1526286480; bh=9CvB8+FvHTbTOgQkKl4JoAwx XCmd38NaKekrX8XPk7E=; b=KL55/V2xGXrlP4aGkppZnWatEbjthcR0qf7mYOc0 7+B05j8f48KjaTf8RtVHl7QbLZ+jm4GU6unm2v+vscbbRnDyQusQZZR+0ytezuUI M+huccrDbgNGYp/Vfx+/lLBABLc4aXm9hEUdfrFq4c174TtOUo6x0BMUeNLhliSz gGA= 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 UuUr387T3CKI; Mon, 14 May 2018 08:28:00 +0000 (UTC) Received: from garnet.daemonic.se (host-95-192-250-89.mobileonline.telia.com [95.192.250.89]) by mail.daemonic.se (Postfix) with ESMTPSA id 40kv342fbNzDhBg; Mon, 14 May 2018 08:28:00 +0000 (UTC) Subject: Re: suspend/resume regression To: Pete Wright , Theron , Andriy Gapon , FreeBSD Current References: <1e608109-fcdd-d794-b03a-2e417300b95a@nomadlogic.org> <3488a8a4-8cad-d6a8-0852-3bbbdd971c7f@gmail.com> <26f5ec31-3994-eac9-0c43-6d2458c35ad0@nomadlogic.org> <9f7fcdaa-99ea-98f4-8ef3-c8da6060542e@nomadlogic.org> <20180514080604.GA2006@brick> From: Niclas Zeising Message-ID: Date: Mon, 14 May 2018 10:27:59 +0200 User-Agent: Mutt/1.5.21 MIME-Version: 1.0 In-Reply-To: <20180514080604.GA2006@brick> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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, 14 May 2018 08:28:02 -0000 On 05/14/18 10:06, Edward Tomasz Napiera=C5=82a wrote: > On 0513T1244, Pete Wright wrote: >> >> >> On 05/13/2018 10:27, Pete Wright wrote: >>> >>> >>> On 05/13/2018 08:58, Theron wrote: >>>>> Hi! >>>>> I'm also seeing issues, not as severe as Pete, but after I resume >>>>> (which works, with drm-next and DMC firmware), the system becomes >>>>> sluggish.=C2=A0 It feels like I/O takes more time, and graphics are >>>>> sluggish (very sientific, I know, but for instance git operations >>>>> are much slower after a resume).=C2=A0 I know there's been an updat= e to >>>>> acpica between my system updates, when this started to happen, but = I >>>>> haven't had time to revert that update and test again.=C2=A0 I will= try >>>>> to do that and report back. >>>>> Regards >>>> Hi Niclas, >>>> I used drm-next on Skylake with issues which sound similar. Resuming >>>> from suspend, or simply switching the laptop display output off and >>>> on from xrandr, resulted in graphics sluggishness (drop to 30fps in >>>> glxgears) and graphical corruption in Xorg apps, which persisted eve= n >>>> after restarting these apps. Switching to drm-stable made the >>>> problems go away; I haven't had time to figure out what -next is >>>> doing differently to cause them. >>>> >>>> Pete's issue sounds more severe, and unrelated as it happens without >>>> drm loaded.=C2=A0 My kernel is two weeks out of date (r333093), so I= need >>>> to check whether the more recent changes affect my system as well. >>>> >>> so i've done a bit more debugging on my end.=C2=A0 i've even installe= d the >>> 11.2-BETA branch last night since 11-STABLE worked without issues >>> about a month or so ago. >>> >>> i've set "debug.acpi.resume_beep=3D1" and when resuming after enterin= g >>> an S3 sleep state the bell rings and does not stop until i do a hard >>> reset (both with i915kms loaded and unloaded). >>> >>> kinda at a loss as to how this could break both CURRENT and basically >>> 11-STABLE.=C2=A0 i'm going to make a ubuntu live image and test that,= my >>> laptop is a System76 laptop that shipped with ubuntu originally.=C2=A0= if >>> that is broken as well then i guess this could be a hardware issue. >>> >> ubuntu live image suspends/resumes without issue so this certainly see= ms >> to be a freebsd issue unfortunately.=C2=A0 i guess next step is to att= empt to >> find a working CURRENT snapshot that does suspend/resume without issue >> then start looking at commits? >=20 > FWIW, I'm seeing the same - sluggishness after resume - with stock > 12-CURRENT, without drm-next, just vanilla i915kms.ko, on T420. >=20 > TBH I'm not entirely sure it's X11 problem - as I'm writing it now, > under vt(4), it seems somewhat slow too. >=20 It's not impossible that there are two different regressions, one=20 causing sluggishness and one causing graphics corruption, or that they=20 are intertwined. I have a Kaby Lake system which I run these tests on.=20 I also have a window where the regression seem to have happened.=20 r333269 to r333340, so once I have time I'll start bisecting. Hopefully I can test on older systems as well. Regards --=20 Niclas From owner-freebsd-current@freebsd.org Mon May 14 08:45:36 2018 Return-Path: Delivered-To: freebsd-current@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 DEED2FE1ABC for ; Mon, 14 May 2018 08:45:35 +0000 (UTC) (envelope-from mikael.urankar@gmail.com) Received: from mail-pl0-x22b.google.com (mail-pl0-x22b.google.com [IPv6:2607:f8b0:400e:c01::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 59B4184EAB; Mon, 14 May 2018 08:45:35 +0000 (UTC) (envelope-from mikael.urankar@gmail.com) Received: by mail-pl0-x22b.google.com with SMTP id e6-v6so6945536plt.11; Mon, 14 May 2018 01:45:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Id8tBbzf6ZxBkj6FCC6/VLRTo1SDpBlUH2JfeQQzA+o=; b=ctdIzuoCP20gVhWXSodIhNiwLlh0PKYvSqfFCQgpttiif53Dist78InVD8pid07kgt ck4EEQeXR2/7IiPlFuhIR7e1DmwN9yxKWhMzGF4t+v4BWxVt5e+0+/eLIUSJk/5gzpSx lWVUWlJsFp1fAcHbIu1dF+dfpaB1k6XOXvu+p3MzJ+Len+lkcK2xnCKGFO6taku78agD gJTMuzDTpjVNsl0Bx7Kp8inxLwztCryuE5G7zZ+9PQUnZ+wS9m75OstwcLjZd1nblnf3 x2g7gL1R/sqjM/u5LFMGBu+VPO61ZNBdKF/kUfBAaCRhh8CAaIku03fZi4DxNYtaq3+6 9QFw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Id8tBbzf6ZxBkj6FCC6/VLRTo1SDpBlUH2JfeQQzA+o=; b=HEfomiv4S0uBhSFsYhgzcHdxvqrFg41TECHmYT8C1DCG/8DKLNQNnbPASS9Rhqbwm0 OBSKWGqZjZCRSv6C2NEMUqDI4EGwn2ac/CR4mf++OQAKaUhEw9tWXaBh1XdbpnRjidv3 /GqpeVdOu80VISzHOzlJQMWBDgtcrF/58d9RwAwOSnetqJPhz5V8hxvebSK5Wb2VfYqU KW0Mq6Q/+J3AEuA0S0qB/Mhx6RU9ZqQ9pRaRXbp2NP+yDvesamDTt37E57peQRUYqo9B kXkWO98MYXlC8jHVQWWa27Gxpf86IWIsKfpev9hgodlrQ42oStbVjFYDHwP9vX2+X83Z rw8w== X-Gm-Message-State: ALKqPwfZ0F3xbd8zU/ZkOPIcZJEbCLsIBA1UhW0L8aoTVgA1TVX41riG LOchNkPk0QgtERpa99SP22imCQtxddAMYFmiRdQ= X-Google-Smtp-Source: AB8JxZqEZJ/4G5ofl60A8WhUOaxLBAy+rU7DpgjDq8h2jOZxFInRHDkEZl2E5vyfhQGfE44qiQdQfjG5YQoy4AFjuck= X-Received: by 2002:a17:902:2f84:: with SMTP id t4-v6mr9210559plb.24.1526287534467; Mon, 14 May 2018 01:45:34 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a17:90a:20ab:0:0:0:0 with HTTP; Mon, 14 May 2018 01:44:54 -0700 (PDT) In-Reply-To: References: <1e608109-fcdd-d794-b03a-2e417300b95a@nomadlogic.org> <3488a8a4-8cad-d6a8-0852-3bbbdd971c7f@gmail.com> <26f5ec31-3994-eac9-0c43-6d2458c35ad0@nomadlogic.org> <9f7fcdaa-99ea-98f4-8ef3-c8da6060542e@nomadlogic.org> <20180514080604.GA2006@brick> From: =?UTF-8?Q?Mika=C3=ABl_Urankar?= Date: Mon, 14 May 2018 10:44:54 +0200 Message-ID: Subject: Re: suspend/resume regression To: Niclas Zeising Cc: Pete Wright , Theron , Andriy Gapon , FreeBSD Current Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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, 14 May 2018 08:45:36 -0000 2018-05-14 10:27 GMT+02:00 Niclas Zeising : > On 05/14/18 10:06, Edward Tomasz Napiera=C5=82a wrote: > >> On 0513T1244, Pete Wright wrote: >> >>> >>> >>> On 05/13/2018 10:27, Pete Wright wrote: >>> >>>> >>>> >>>> On 05/13/2018 08:58, Theron wrote: >>>> >>>>> Hi! >>>>>> I'm also seeing issues, not as severe as Pete, but after I resume >>>>>> (which works, with drm-next and DMC firmware), the system becomes >>>>>> sluggish. It feels like I/O takes more time, and graphics are >>>>>> sluggish (very sientific, I know, but for instance git operations >>>>>> are much slower after a resume). I know there's been an update to >>>>>> acpica between my system updates, when this started to happen, but I >>>>>> haven't had time to revert that update and test again. I will try >>>>>> to do that and report back. >>>>>> Regards >>>>>> >>>>> Hi Niclas, >>>>> I used drm-next on Skylake with issues which sound similar. Resuming >>>>> from suspend, or simply switching the laptop display output off and >>>>> on from xrandr, resulted in graphics sluggishness (drop to 30fps in >>>>> glxgears) and graphical corruption in Xorg apps, which persisted even >>>>> after restarting these apps. Switching to drm-stable made the >>>>> problems go away; I haven't had time to figure out what -next is >>>>> doing differently to cause them. >>>>> >>>>> Pete's issue sounds more severe, and unrelated as it happens without >>>>> drm loaded. My kernel is two weeks out of date (r333093), so I need >>>>> to check whether the more recent changes affect my system as well. >>>>> >>>>> so i've done a bit more debugging on my end. i've even installed the >>>> 11.2-BETA branch last night since 11-STABLE worked without issues >>>> about a month or so ago. >>>> >>>> i've set "debug.acpi.resume_beep=3D1" and when resuming after entering >>>> an S3 sleep state the bell rings and does not stop until i do a hard >>>> reset (both with i915kms loaded and unloaded). >>>> >>>> kinda at a loss as to how this could break both CURRENT and basically >>>> 11-STABLE. i'm going to make a ubuntu live image and test that, my >>>> laptop is a System76 laptop that shipped with ubuntu originally. if >>>> that is broken as well then i guess this could be a hardware issue. >>>> >>>> ubuntu live image suspends/resumes without issue so this certainly see= ms >>> to be a freebsd issue unfortunately. i guess next step is to attempt t= o >>> find a working CURRENT snapshot that does suspend/resume without issue >>> then start looking at commits? >>> >> >> FWIW, I'm seeing the same - sluggishness after resume - with stock >> 12-CURRENT, without drm-next, just vanilla i915kms.ko, on T420. >> >> TBH I'm not entirely sure it's X11 problem - as I'm writing it now, >> under vt(4), it seems somewhat slow too. >> >> > It's not impossible that there are two different regressions, one causing > sluggishness and one causing graphics corruption, or that they are > intertwined. I have a Kaby Lake system which I run these tests on. I also > have a window where the regression seem to have happened. r333269 to > r333340, so once I have time I'll start bisecting. > > Hopefully I can test on older systems as well. Could it be the same problem described here? https://lists.freebsd.org/pipermail/freebsd-hackers/2018-May/052778.html From owner-freebsd-current@freebsd.org Mon May 14 08:58:57 2018 Return-Path: Delivered-To: freebsd-current@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 113BDFE258D for ; Mon, 14 May 2018 08:58:57 +0000 (UTC) (envelope-from agapon@gmail.com) Received: from mail-lf0-f44.google.com (mail-lf0-f44.google.com [209.85.215.44]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5013F87F40 for ; Mon, 14 May 2018 08:58:56 +0000 (UTC) (envelope-from agapon@gmail.com) Received: by mail-lf0-f44.google.com with SMTP id j193-v6so16774800lfg.6 for ; Mon, 14 May 2018 01:58:56 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:openpgp:autocrypt :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=6hMonAlCgxXqDD3DnLG5wzpq0qxrWUfDW3RmZ8WPshs=; b=M1ZLg7W/QsROPTonwK7y+POuefWVb+ggLxP/02tNgmp4zqFzqEQihxb4gjIKhet7wY QBdeVTXIekbAd9P0j9m8A2IWYCvFQvxEs8ei2EOoYwn//YyZhKqimdzaDIoy4pfFtIHo SnnAGPmoO6Kofj3kQVMShR5GGwtgyECJrDlOPkrvJB6LRo+TY5Js3wooOqkGVcok9JFd 3KrFF+K4grlgVzgwrRE9dbV3OlAVffkgqg6XuH5BW6XeNV0euobUrx2eWhL0HgXQRqB5 9f+IJVb97f5AL1sN2eQxlzDl6Opm6siJ4ALOlWqkTvzeTPUxFVvgEJJjJkAJLwHKYMAJ eplA== X-Gm-Message-State: ALKqPwdg0qNdsG2ypPZHpRJ/3T+FLWuTFVOPSZIM3rvcNO1VCLn2AuJD 0lbiAr3jsqSbAkIZB1ZJ54RPDJ9I X-Google-Smtp-Source: AB8JxZrOd60pYAdTB9uKsFW8dG8wPOY2NNSp3WsYYXkJIqkZTT483d35zdHnZ+pDinzLbcpddGmCUQ== X-Received: by 2002:a19:c6c1:: with SMTP id w184-v6mr8298086lff.126.1526288329423; Mon, 14 May 2018 01:58:49 -0700 (PDT) Received: from [192.168.0.88] (east.meadow.volia.net. [93.72.151.96]) by smtp.googlemail.com with ESMTPSA id g71-v6sm2297145lfh.85.2018.05.14.01.58.47 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 14 May 2018 01:58:48 -0700 (PDT) Subject: Re: suspend/resume regression To: =?UTF-8?Q?Mika=c3=abl_Urankar?= , Niclas Zeising Cc: Pete Wright , Theron , FreeBSD Current References: <1e608109-fcdd-d794-b03a-2e417300b95a@nomadlogic.org> <3488a8a4-8cad-d6a8-0852-3bbbdd971c7f@gmail.com> <26f5ec31-3994-eac9-0c43-6d2458c35ad0@nomadlogic.org> <9f7fcdaa-99ea-98f4-8ef3-c8da6060542e@nomadlogic.org> <20180514080604.GA2006@brick> From: Andriy Gapon Openpgp: preference=signencrypt Autocrypt: addr=avg@FreeBSD.org; prefer-encrypt=mutual; keydata= xsFNBFm4LIgBEADNB/3lT7f15UKeQ52xCFQx/GqHkSxEdVyLFZTmY3KyNPQGBtyvVyBfprJ7 mAeXZWfhat6cKNRAGZcL5EmewdQuUfQfBdYmKjbw3a9GFDsDNuhDA2QwFt8BmkiVMRYyvI7l N0eVzszWCUgdc3qqM6qqcgBaqsVmJluwpvwp4ZBXmch5BgDDDb1MPO8AZ2QZfIQmplkj8Y6Z AiNMknkmgaekIINSJX8IzRzKD5WwMsin70psE8dpL/iBsA2cpJGzWMObVTtCxeDKlBCNqM1i gTXta1ukdUT7JgLEFZk9ceYQQMJJtUwzWu1UHfZn0Fs29HTqawfWPSZVbulbrnu5q55R4PlQ /xURkWQUTyDpqUvb4JK371zhepXiXDwrrpnyyZABm3SFLkk2bHlheeKU6Yql4pcmSVym1AS4 dV8y0oHAfdlSCF6tpOPf2+K9nW1CFA8b/tw4oJBTtfZ1kxXOMdyZU5fiG7xb1qDgpQKgHUX8 7Rd2T1UVLVeuhYlXNw2F+a2ucY+cMoqz3LtpksUiBppJhw099gEXehcN2JbUZ2TueJdt1FdS ztnZmsHUXLxrRBtGwqnFL7GSd6snpGIKuuL305iaOGODbb9c7ne1JqBbkw1wh8ci6vvwGlzx rexzimRaBzJxlkjNfMx8WpCvYebGMydNoeEtkWldtjTNVsUAtQARAQABzR5BbmRyaXkgR2Fw b24gPGF2Z0BGcmVlQlNELm9yZz7CwZQEEwEIAD4WIQS+LEO7ngQnXA4Bjr538m7TUc1yjwUC WbgsiAIbIwUJBaOagAULCQgHAgYVCAkKCwIEFgIDAQIeAQIXgAAKCRB38m7TUc1yj+JAEACV l9AK/nOWAt/9cufV2fRj0hdOqB1aCshtSrwHk/exXsDa4/FkmegxXQGY+3GWX3deIyesbVRL rYdtdK0dqJyT1SBqXK1h3/at9rxr9GQA6KWOxTjUFURsU7ok/6SIlm8uLRPNKO+yq0GDjgaO LzN+xykuBA0FlhQAXJnpZLcVfPJdWv7sSHGedL5ln8P8rxR+XnmsA5TUaaPcbhTB+mG+iKFj GghASDSfGqLWFPBlX/fpXikBDZ1gvOr8nyMY9nXhgfXpq3B6QCRYKPy58ChrZ5weeJZ29b7/ QdEO8NFNWHjSD9meiLdWQaqo9Y7uUxN3wySc/YUZxtS0bhAd8zJdNPsJYG8sXgKjeBQMVGuT eCAJFEYJqbwWvIXMfVWop4+O4xB+z2YE3jAbG/9tB/GSnQdVSj3G8MS80iLS58frnt+RSEw/ psahrfh0dh6SFHttE049xYiC+cM8J27Aaf0i9RflyITq57NuJm+AHJoU9SQUkIF0nc6lfA+o JRiyRlHZHKoRQkIg4aiKaZSWjQYRl5Txl0IZUP1dSWMX4s3XTMurC/pnja45dge/4ESOtJ9R 8XuIWg45Oq6MeIWdjKddGhRj3OohsltKgkEU3eLKYtB6qRTQypHHUawCXz88uYt5e3w4V16H lCpSTZV/EVHnNe45FVBlvK7k7HFfDDkryM7BTQRZuCyIARAAlq0slcsVboY/+IUJdcbEiJRW be9HKVz4SUchq0z9MZPX/0dcnvz/gkyYA+OuM78dNS7Mbby5dTvOqfpLJfCuhaNYOhlE0wY+ 1T6Tf1f4c/uA3U/YiadukQ3+6TJuYGAdRZD5EqYFIkreARTVWg87N9g0fT9BEqLw9lJtEGDY EWUE7L++B8o4uu3LQFEYxcrb4K/WKmgtmFcm77s0IKDrfcX4doV92QTIpLiRxcOmCC/OCYuO jB1oaaqXQzZrCutXRK0L5XN1Y1PYjIrEzHMIXmCDlLYnpFkK+itlXwlE2ZQxkfMruCWdQXye syl2fynAe8hvp7Mms9qU2r2K9EcJiR5N1t1C2/kTKNUhcRv7Yd/vwusK7BqJbhlng5ZgRx0m WxdntU/JLEntz3QBsBsWM9Y9wf2V4tLv6/DuDBta781RsCB/UrU2zNuOEkSixlUiHxw1dccI 6CVlaWkkJBxmHX22GdDFrcjvwMNIbbyfQLuBq6IOh8nvu9vuItup7qemDG3Ms6TVwA7BD3j+ 3fGprtyW8Fd/RR2bW2+LWkMrqHffAr6Y6V3h5kd2G9Q8ZWpEJk+LG6Mk3fhZhmCnHhDu6CwN MeUvxXDVO+fqc3JjFm5OxhmfVeJKrbCEUJyM8ESWLoNHLqjywdZga4Q7P12g8DUQ1mRxYg/L HgZY3zfKOqcAEQEAAcLBfAQYAQgAJhYhBL4sQ7ueBCdcDgGOvnfybtNRzXKPBQJZuCyIAhsM BQkFo5qAAAoJEHfybtNRzXKPBVwQAKfFy9P7N3OsLDMB56A4Kf+ZT+d5cIx0Yiaf4n6w7m3i ImHHHk9FIetI4Xe54a2IXh4Bq5UkAGY0667eIs+Z1Ea6I2i27Sdo7DxGwq09Qnm/Y65ADvXs 3aBvokCcm7FsM1wky395m8xUos1681oV5oxgqeRI8/76qy0hD9WR65UW+HQgZRIcIjSel9vR XDaD2HLGPTTGr7u4v00UeTMs6qvPsa2PJagogrKY8RXdFtXvweQFz78NbXhluwix2Tb9ETPk LIpDrtzV73CaE2aqBG/KrboXT2C67BgFtnk7T7Y7iKq4/XvEdDWscz2wws91BOXuMMd4c/c4 OmGW9m3RBLufFrOag1q5yUS9QbFfyqL6dftJP3Zq/xe+mr7sbWbhPVCQFrH3r26mpmy841ym dwQnNcsbIGiBASBSKksOvIDYKa2Wy8htPmWFTEOPRpFXdGQ27awcjjnB42nngyCK5ukZDHi6 w0qK5DNQQCkiweevCIC6wc3p67jl1EMFY5+z+zdTPb3h7LeVnGqW0qBQl99vVFgzLxchKcl0 R/paSFgwqXCZhAKMuUHncJuynDOP7z5LirUeFI8qsBAJi1rXpQoLJTVcW72swZ42IdPiboqx NbTMiNOiE36GqMcTPfKylCbF45JNX4nF9ElM0E+Y8gi4cizJYBRr2FBJgay0b9Cp Message-ID: Date: Mon, 14 May 2018 11:58:47 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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, 14 May 2018 08:58:57 -0000 On 14/05/2018 11:44, Mikaël Urankar wrote: > Could it be the same problem described here? > https://lists.freebsd.org/pipermail/freebsd-hackers/2018-May/052778.html That problem is _not_ a regression. -- Andriy Gapon From owner-freebsd-current@freebsd.org Mon May 14 10:55:09 2018 Return-Path: Delivered-To: freebsd-current@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 45A4DFE7245 for ; Mon, 14 May 2018 10:55:09 +0000 (UTC) (envelope-from jhs@berklix.com) 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 D504879C01 for ; Mon, 14 May 2018 10:55:08 +0000 (UTC) (envelope-from jhs@berklix.com) Received: by mailman.ysv.freebsd.org (Postfix) id 96156FE7242; Mon, 14 May 2018 10:55:08 +0000 (UTC) Delivered-To: current@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 7190BFE7241 for ; Mon, 14 May 2018 10:55:08 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from land.berklix.org (land.berklix.org [144.76.10.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "land.berklix.org", Issuer "land.berklix.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id F25FF79BE1 for ; Mon, 14 May 2018 10:55:07 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from mart.js.berklix.net (pD9FA824B.dip0.t-ipconnect.de [217.250.130.75]) (authenticated bits=0) by land.berklix.org (8.15.2/8.15.2) with ESMTPSA id w4EArNEm059573 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 14 May 2018 10:53:27 GMT (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by mart.js.berklix.net (8.14.3/8.14.3) with ESMTP id w4EAspo1074054; Mon, 14 May 2018 12:55:03 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.7/8.14.7) with ESMTP id w4E1OFtV002650; Mon, 14 May 2018 03:25:57 +0200 (CEST) (envelope-from jhs@berklix.com) Message-Id: <201805140125.w4E1OFtV002650@fire.js.berklix.net> To: Ryan Stone Cc: FreeBSD Current Subject: Re: cd /sys/amd64/compile/GENERIC;make cleandepend; make cleandepend From: "Julian H. Stacey" Organization: http://berklix.eu BSD Unix Linux Consultants, Munich Germany User-agent: EXMH on FreeBSD http://berklix.eu/free/ X-From: http://www.berklix.eu/~jhs/ In-reply-to: Your message "Mon, 14 May 2018 02:16:11 +0200." Date: Mon, 14 May 2018 03:24:15 +0200 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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, 14 May 2018 10:55:09 -0000 "Julian H. Stacey" wrote: > Hi, Reference: > > From: Ryan Stone > > Date: Sun, 13 May 2018 17:00:50 -0400 > > Thanks for reply :-) > > Ryan Stone wrote: > > Are you building with WITH_LD_IS_LLD=no? > > Not that I've set anywhere. Unless it comes from make world ? > > > -CURRENT can no longer be > > built with a GPLv2 ld. You either have to use ldd or install a newer > > -r-xr-xr-x 1 root wheel 19352 May 13 12:52 /usr/bin/ldd* > > > (GPLv3) binutils package. > > pkg info | grep binutils > binutils-2.30_3,1 GNU binary tools > gnatdroid-binutils-2.27_1 Infrastructure for C/Ada Android cross-compiler (ARMv7) > > pkg upgrade > The process will require 132 MiB more space. > 569 MiB to be downloaded. > > I'll leave it running & report back later, Thanks /sys/amd64/compile/LAPR.small xs !! xs make cc -c -O2 -pipe -fno-strict-aliasing -g -nostdinc -I. -I../../.. -I../../../contrib/ck/include -I../../../contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -MD -MF.depend.iflib.o -MTiflib.o -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fwrapv -fstack-protector -gdwarf-2 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wcast-qual -Wundef -Wno-pointer-sign -D__printf__=__freebsd_kprintf__ -Wmissing-include-dirs -fdiagnostics-show-option -Wno-unknown-pragmas -Wno-error-tautological-compare -Wno-error-empty-body -Wno-error-parentheses-equality -Wno-error-unused-function -Wno-error-pointer-sign -Wno-error-shift-negative-value -Wno-error-address-of-packed-member -mno-aes -mno-avx -std=iso9899:1999 -Werror ../../../net/iflib.c ctfconvert -L VERSION -g iflib.o MAKE="make" sh ../../../conf/newvers.sh JHS_Lapr cc -c -O2 -pipe -fno-strict-aliasing -g -nostdinc -I. -I../../.. -I../../../contrib/ck/include -I../../../contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fwrapv -fstack-protector -gdwarf-2 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wcast-qual -Wundef -Wno-pointer-sign -D__printf__=__freebsd_kprintf__ -Wmissing-include-dirs -fdiagnostics-show-option -Wno-unknown-pragmas -Wno-error-tautological-compare -Wno-error-empty-body -Wno-error-parentheses-equality -Wno-error-unused-function -Wno-error-pointer-sign -Wno-error-shift-negative-value -Wno-error-address-of-packed-member -mno-aes -mno-avx -std=iso9899:1999 -Werror vers.c ctfconvert -L VERSION -g vers.o linking kernel.full iflib.o:(.rodata+0x178): undefined reference to `noop_attach' iflib.o:(.rodata+0x188): undefined reference to `iflib_pseudo_detach' *** Error code 1 pkg info | grep binutils l `which ldd` -r-xr-xr-x 1 root wheel 19352 May 13 12:52 /usr/bin/ldd* l /usr/bin/ld -r-xr-xr-x 2 root wheel 1935992 May 13 12:48 /usr/bin/ld* cd /usr;mv local localMV;rehash cd /sys/amd64/conf;cd ../compile/`hostname -s | dd conv=ucase`.small make iflib.o:(.rodata+0x178): undefined reference to `noop_attach' iflib.o:(.rodata+0x188): undefined reference to `iflib_pseudo_detach' so nothing to do with packages & local. For decades it been policy that src/ must be able to build itself without needing ports/ So what's wrong ? Anyone else see this ? Cheers, Julian -- Julian Stacey, Computer Consultant, Systems Engineer, BSD Linux Unix, Munich Brexit Referendum stole 3,700,000 votes, inc. 700,000 from British in EU. UK Govt. lied it's "democratic" in Article 50 letter to EU paragraph 3. Petition for votes: http://berklix.eu/queen/ From owner-freebsd-current@freebsd.org Mon May 14 12:21:33 2018 Return-Path: Delivered-To: freebsd-current@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 3BC80D844DE for ; Mon, 14 May 2018 12:21:33 +0000 (UTC) (envelope-from jhs@berklix.com) 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 F113A6A47F for ; Mon, 14 May 2018 12:21:32 +0000 (UTC) (envelope-from jhs@berklix.com) Received: by mailman.ysv.freebsd.org (Postfix) id B5A35D844D1; Mon, 14 May 2018 12:21:32 +0000 (UTC) Delivered-To: current@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 A327FD844CF for ; Mon, 14 May 2018 12:21:32 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from land.berklix.org (land.berklix.org [144.76.10.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "land.berklix.org", Issuer "land.berklix.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4A1756A467 for ; Mon, 14 May 2018 12:21:32 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from mart.js.berklix.net (pD9FA824B.dip0.t-ipconnect.de [217.250.130.75]) (authenticated bits=0) by land.berklix.org (8.15.2/8.15.2) with ESMTPSA id w4ECJlwq063260 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 14 May 2018 12:19:51 GMT (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by mart.js.berklix.net (8.14.3/8.14.3) with ESMTP id w4ECLQ8r074676 for ; Mon, 14 May 2018 14:21:26 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.7/8.14.7) with ESMTP id w4ECLEqL070053 for ; Mon, 14 May 2018 14:21:26 +0200 (CEST) (envelope-from jhs@berklix.com) Message-Id: <201805141221.w4ECLEqL070053@fire.js.berklix.net> cc: FreeBSD Current Subject: Re: cd /sys/amd64/compile/GENERIC;make cleandepend; make cleandepend From: "Julian H. Stacey" Organization: http://berklix.eu BSD Unix Linux Consultants, Munich Germany User-agent: EXMH on FreeBSD http://berklix.eu/free/ X-From: http://www.berklix.eu/~jhs/ In-reply-to: Your message "Mon, 14 May 2018 03:24:15 +0200." <201805140125.w4E1OFtV002650@fire.js.berklix.net> Date: Mon, 14 May 2018 14:21:14 +0200 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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, 14 May 2018 12:21:33 -0000 Hi, Reference my > linking kernel.full > iflib.o:(.rodata+0x178): undefined reference to `noop_attach' > iflib.o:(.rodata+0x188): undefined reference to `iflib_pseudo_detach' [ Thanks for call Gary, I have: ] ls -l /usr/bin/ld* -r-xr-xr-x 2 root wheel 1935992 May 13 12:48 /usr/bin/ld* -r-xr-xr-x 2 root wheel 1935992 May 13 12:48 /usr/bin/ld.bfd* -r-xr-xr-x 1 root wheel 40449288 May 13 12:54 /usr/bin/ld.lld* -r-xr-xr-x 1 root wheel 19352 May 13 12:52 /usr/bin/ldd* -r-xr-xr-x 1 root wheel 26872 May 13 08:59 /usr/bin/ldd32* uname -a FreeBSD lapr.js.berklix.net 12.0-CURRENT FreeBSD 12.0-CURRENT #0: Sat May 12 13:37:23 CEST 2018 jhs@lapr.js.berklix.net:/data/release/s4/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 cat .svn_revision # 333575 cat .ctm_status # src-cur 13520 In case there's more tool dependency checking/ auto update done, I'm now running 'script' & within that 'cd /usr/src; make buildkernel' (Instead of my previous cd /sys/amd64/conf; make links; make # (makes my host conf.) config `hostname -s | dd conv=ucase`.small cd ../compile/`hostname -s | dd conv=ucase`.small make obj; make cleandepend && make depend && make all && make install ) Cheers, Julian -- Julian Stacey, Computer Consultant, Systems Engineer, BSD Linux Unix, Munich Brexit Referendum stole 3,700,000 votes, inc. 700,000 from British in EU. UK Govt. lied it's "democratic" in Article 50 letter to EU paragraph 3. Petition for votes: http://berklix.eu/queen/ From owner-freebsd-current@freebsd.org Mon May 14 14:34:59 2018 Return-Path: Delivered-To: freebsd-current@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 8133DDF03C3 for ; Mon, 14 May 2018 14:34:59 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from vps-mail.nomadlogic.org (mail.nomadlogic.org [IPv6:2607:f2f8:a098::2]) (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 0247C69CD9; Mon, 14 May 2018 14:34:58 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from [192.168.2.9] (cpe-23-243-163-13.socal.res.rr.com [23.243.163.13]) by vps-mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id 7eb07e0e TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO; Mon, 14 May 2018 07:34:57 -0700 (PDT) Subject: Re: suspend/resume regression To: Niclas Zeising , Theron , Andriy Gapon , FreeBSD Current References: <1e608109-fcdd-d794-b03a-2e417300b95a@nomadlogic.org> <3488a8a4-8cad-d6a8-0852-3bbbdd971c7f@gmail.com> <26f5ec31-3994-eac9-0c43-6d2458c35ad0@nomadlogic.org> <9f7fcdaa-99ea-98f4-8ef3-c8da6060542e@nomadlogic.org> <92bc7e50-2252-5e6a-cf2c-165ef5f6f2d3@daemonic.se> From: Pete Wright Message-ID: <46e8a643-a6b0-b291-093b-7cf21c41c8fd@nomadlogic.org> Date: Mon, 14 May 2018 07:34:56 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <92bc7e50-2252-5e6a-cf2c-165ef5f6f2d3@daemonic.se> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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, 14 May 2018 14:34:59 -0000 On 05/14/2018 01:18, Niclas Zeising wrote: > On 05/13/18 21:44, Pete Wright wrote: >> >> >> On 05/13/2018 10:27, Pete Wright wrote: >>> >>> >>> On 05/13/2018 08:58, Theron wrote: >>>>> Hi! >>>>> I'm also seeing issues, not as severe as Pete, but after I resume >>>>> (which works, with drm-next and DMC firmware), the system becomes >>>>> sluggish.  It feels like I/O takes more time, and graphics are >>>>> sluggish (very sientific, I know, but for instance git operations >>>>> are much slower after a resume).  I know there's been an update to >>>>> acpica between my system updates, when this started to happen, but >>>>> I haven't had time to revert that update and test again.  I will >>>>> try to do that and report back. >>>>> Regards >>>> Hi Niclas, >>>> I used drm-next on Skylake with issues which sound similar. >>>> Resuming from suspend, or simply switching the laptop display >>>> output off and on from xrandr, resulted in graphics sluggishness >>>> (drop to 30fps in glxgears) and graphical corruption in Xorg apps, >>>> which persisted even after restarting these apps. Switching to >>>> drm-stable made the problems go away; I haven't had time to figure >>>> out what -next is doing differently to cause them. >>>> >>>> Pete's issue sounds more severe, and unrelated as it happens >>>> without drm loaded.  My kernel is two weeks out of date (r333093), >>>> so I need to check whether the more recent changes affect my system >>>> as well. >>>> >>> so i've done a bit more debugging on my end.  i've even installed >>> the 11.2-BETA branch last night since 11-STABLE worked without >>> issues about a month or so ago. >>> >>> i've set "debug.acpi.resume_beep=1" and when resuming after entering >>> an S3 sleep state the bell rings and does not stop until i do a hard >>> reset (both with i915kms loaded and unloaded). >>> >>> kinda at a loss as to how this could break both CURRENT and >>> basically 11-STABLE.  i'm going to make a ubuntu live image and test >>> that, my laptop is a System76 laptop that shipped with ubuntu >>> originally.  if that is broken as well then i guess this could be a >>> hardware issue. >>> >> ubuntu live image suspends/resumes without issue so this certainly >> seems to be a freebsd issue unfortunately.  i guess next step is to >> attempt to find a working CURRENT snapshot that does suspend/resume >> without issue then start looking at commits? >> > > Hi! > It's a bit worrisome that your regression occurs both on CURRENT and > STABLE.  There was an update to both drm-next-kmod and drm-stable-kmod > last week, but both are very minor.  One question, did you install > from pkg or compile from ports? i create a package directly from the github mirror of the ports tree (i.e. make package; pkg install...). -pete -- Pete Wright pete@nomadlogic.org @nomadlogicLA From owner-freebsd-current@freebsd.org Mon May 14 14:46:41 2018 Return-Path: Delivered-To: freebsd-current@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 3DEF6DF3158 for ; Mon, 14 May 2018 14:46:41 +0000 (UTC) (envelope-from jhs@berklix.com) 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 A7EF86C9E6 for ; Mon, 14 May 2018 14:46:40 +0000 (UTC) (envelope-from jhs@berklix.com) Received: by mailman.ysv.freebsd.org (Postfix) id 6AFF2DF3157; Mon, 14 May 2018 14:46:40 +0000 (UTC) Delivered-To: current@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 40F75DF3156 for ; Mon, 14 May 2018 14:46:40 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from land.berklix.org (land.berklix.org [144.76.10.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "land.berklix.org", Issuer "land.berklix.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id B7B706C9C0 for ; Mon, 14 May 2018 14:46:39 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from mart.js.berklix.net (pD9FA824B.dip0.t-ipconnect.de [217.250.130.75]) (authenticated bits=0) by land.berklix.org (8.15.2/8.15.2) with ESMTPSA id w4EEisTO067549 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 14 May 2018 14:44:58 GMT (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by mart.js.berklix.net (8.14.3/8.14.3) with ESMTP id w4EEkXCa075624 for ; Mon, 14 May 2018 16:46:33 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.7/8.14.7) with ESMTP id w4EEkL7p072460 for ; Mon, 14 May 2018 16:46:33 +0200 (CEST) (envelope-from jhs@berklix.com) Message-Id: <201805141446.w4EEkL7p072460@fire.js.berklix.net> cc: FreeBSD Current Subject: Re: cd /sys/amd64/compile/GENERIC;make cleandepend; make cleandepend From: "Julian H. Stacey" Organization: http://berklix.eu BSD Unix Linux Consultants, Munich Germany User-agent: EXMH on FreeBSD http://berklix.eu/free/ X-From: http://www.berklix.eu/~jhs/ In-reply-to: Your message "Mon, 14 May 2018 14:21:14 +0200." <201805141221.w4ECLEqL070053@fire.js.berklix.net> Date: Mon, 14 May 2018 16:46:21 +0200 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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, 14 May 2018 14:46:41 -0000 Hi, Reference: > From: "Julian H. Stacey" > Date: Mon, 14 May 2018 14:21:14 +0200 > In case there's more tool dependency checking/ auto update done, > I'm now running 'script' & within that 'cd /usr/src; make buildkernel' That worked ! (Although looking at my template script I've run that before recently) ===> zlib (all) [Creating objdir /data/release/s4/usr/obj/usr/src/amd64.amd64/sys/GENERIC/modules/usr/src/sys/modules/zlib...] machine -> /usr/src/sys/amd64/include x86 -> /usr/src/sys/x86/include cc -target x86_64-unknown-freebsd12.0 --sysroot=/data/release/s4/usr/obj/usr/src/amd64.amd64/tmp -B/data/release/s4/usr/obj/usr/src/amd64.amd64/tmp/usr/bin -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -DHAVE_KERNEL_OPTION_HEADERS -include /data/release/s4/usr/obj/usr/src/amd64.amd64/sys/GENERIC/opt_global.h -I. -I/usr/src/sys -I/usr/src/sys/contrib/ck/include -fno-common -g -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/data/release/s4/usr/obj/usr/src/amd64.amd64/sys/GENERIC -MD -MF.depend.zlib.o -MTzlib.o -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fwrapv -fstack-protector -gdwarf-2 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wcast-qual -Wundef -Wno-pointer-sign -D__printf__=__freebsd_kprintf__ -Wmissing-include-dirs -fdiagnostics-show-option -Wno-unknown-pragmas -Wno-error-tautological-compare -Wno-error-empty-b! ody -Wno-error-parentheses-equality -Wno-error-unused-function -Wno-error-pointer-sign -Wno-error-shift-negative-value -Wno-error-address-of-packed-member -mno-aes -mno-avx -std=iso9899:1999 -c /usr/src/sys/libkern/zlib.c -o zlib.o ctfconvert -L VERSION -g zlib.o ld -m elf_x86_64_fbsd -d -warn-common --build-id=sha1 -r -d -o zlib.ko.full zlib.o ctfmerge -L VERSION -g -o zlib.ko.full zlib.o :> export_syms awk -f /usr/src/sys/conf/kmod_syms.awk zlib.ko.full export_syms | xargs -J% objcopy % zlib.ko.full objcopy --only-keep-debug zlib.ko.full zlib.ko.debug objcopy --strip-debug --add-gnu-debuglink=zlib.ko.debug zlib.ko.full zlib.ko -------------------------------------------------------------- >>> Kernel build for GENERIC completed on Mon May 14 15:07:43 CEST 2018 make installkernel ; reboot # OK! Sorry, I can't pin it down, at least yet, now trying a custom kernel. Cheers, Julian -- Julian Stacey, Computer Consultant, Systems Engineer, BSD Linux Unix, Munich Brexit Referendum stole 3,700,000 votes, inc. 700,000 from British in EU. UK Govt. lied it's "democratic" in Article 50 letter to EU paragraph 3. Petition for votes: http://berklix.eu/queen/ From owner-freebsd-current@freebsd.org Mon May 14 17:50:55 2018 Return-Path: Delivered-To: freebsd-current@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 549B4DFD237; Mon, 14 May 2018 17:50:55 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-it0-x229.google.com (mail-it0-x229.google.com [IPv6:2607:f8b0:4001:c0b::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EB7EA7B8BA; Mon, 14 May 2018 17:50:54 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mail-it0-x229.google.com with SMTP id p3-v6so12422774itc.0; Mon, 14 May 2018 10:50:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:from:date:message-id:subject:to; bh=KeD+v2ksyTZGBeMeecyIVeHVm7HyBB7lVqL1sBunHGo=; b=koolnF0h/jaA+D3fXDF6fBf1VeNYkO2dkqq8x1ydfPlBmgIMJQjEQSNkAWmFxM2wWL 5A1QV9gsDGK1R6Rt7kwP8GguwBVkA/gGDVhBgRfcqGO1q1Ueoyi0UNFRGevVLL0qoFUh SGnnSN4t5mYP265TrXbyg5zR0vT42eFOsjFI+jxzRF/UqMawRRsywDRQnCFAD/yw7uOL cDiyeHq3JxkqL5oTL3RMHYnPUbZhWKwnQC5lSmw+bAylThHrIgMxbgxbYzbZvBWRKp4R Epk4/DbvxxztE1tqR027GVKvhal1opXyjygi3Q+pq080yace5A+/Dn5tj0L+/jsdrSBp VV2w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:from:date:message-id:subject :to; bh=KeD+v2ksyTZGBeMeecyIVeHVm7HyBB7lVqL1sBunHGo=; b=OwiDVhErubHdd9Ckr5lJAJeeGWNZzydUia8Miu9jhh7ixPq2F6w2jC2YmkAmx+6oUY itjveK22auKl2mGBFrSdtUlfqx3wQAXgVz36KB8Bi8of7xwEOQXcDrFmtB3u1xaeC+HO 5V56gpq1KBBVC/FsCZiy24O0u/I0S3hjrXqY+2PcHTgEvHdvVsCla7yQwhwUrTvJmyaZ n1X0FpGoVlmK9lMOiDhyISxHPhGDYPZrmZcFtH/jkfpGaj2ZjbeNUZWMKcFjhDxL6RaJ r9exYmpAhN0QDHjnXt4cZNU/XV5OV3TVDZrSqknVAqpmFRNTLaG73/8f1wW7lAT2C7nw +Ajg== X-Gm-Message-State: ALKqPwcoak00czj7LD8/TlxQJhoEeuROi6+WqfbYzp3N8W+zCsjMIWyQ +t6xugyyyVa1bKhK05NgMf4W+FwMoLm9Hro27fwwjQ== X-Google-Smtp-Source: AB8JxZrByTOhuptaKq3MXIiy8kak23eSj22GvnoNMPJ6QD1a3oKefgNbiI33JJXzH7q2mmkgqZsO3/0VcP1RDF9uMrA= X-Received: by 2002:a24:3555:: with SMTP id k82-v6mr10373058ita.49.1526320254222; Mon, 14 May 2018 10:50:54 -0700 (PDT) MIME-Version: 1.0 Sender: carpeddiem@gmail.com Received: by 10.107.130.167 with HTTP; Mon, 14 May 2018 10:50:33 -0700 (PDT) From: Ed Maste Date: Mon, 14 May 2018 13:50:33 -0400 X-Google-Sender-Auth: 1o2Dlmi1Wq8lJ9WbLbn_85l46ZQ Message-ID: Subject: HEADS-UP: Linker issues building amd64 kernels with config & make To: FreeBSD Current , "freebsd-toolchain@FreeBSD.org" Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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, 14 May 2018 17:50:55 -0000 As of r333461 the amd64 kernel makes use of ifuncs, and requires support in the linker. A safety belt added in r333470 enforces this, and will produce an explicit error if the linker does not support ifuncs. lld is the default bootstrap linker for amd64 and has ifunc support. The typical 'make buildworld' (or kernel-toolchain) followed by 'make buildkernel' process will use lld and successfully link a working kernel. The old-style kernel build (using 'config' followed by a 'make' in the kernel directory) uses the host linker (/usr/bin/ld). This still defaults to GNU ld 2.17.50, which does not support ifuncs. This can be worked around in one of two ways: 1. Install lld as the system linker (/usr/bin/ld), by adding WITH_LLD_IS_LD to /etc/src.conf and building and install world. WITH_LLD_IS_LD will become the default on amd64 in the near future - I'm just waiting on updates to the lang/ghc port and another exp-run. 2. Override LD when you build the kernel: $ LD=ld.lld make These tool chain components will undergo additional changes for the next while. From owner-freebsd-current@freebsd.org Mon May 14 22:06:13 2018 Return-Path: Delivered-To: freebsd-current@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 A5939E7B2BD for ; Mon, 14 May 2018 22:06:13 +0000 (UTC) (envelope-from jhs@berklix.com) 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 41F1B7A264 for ; Mon, 14 May 2018 22:06:13 +0000 (UTC) (envelope-from jhs@berklix.com) Received: by mailman.ysv.freebsd.org (Postfix) id F0163E7B2B9; Mon, 14 May 2018 22:06:12 +0000 (UTC) Delivered-To: current@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 DE02AE7B2B8 for ; Mon, 14 May 2018 22:06:12 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from land.berklix.org (land.berklix.org [144.76.10.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "land.berklix.org", Issuer "land.berklix.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 5BA157A23C; Mon, 14 May 2018 22:06:10 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from mart.js.berklix.net (pD9FA824B.dip0.t-ipconnect.de [217.250.130.75]) (authenticated bits=0) by land.berklix.org (8.15.2/8.15.2) with ESMTPSA id w4EM4JMr080335 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 14 May 2018 22:04:24 GMT (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by mart.js.berklix.net (8.14.3/8.14.3) with ESMTP id w4EM5vpw078260; Tue, 15 May 2018 00:05:57 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.7/8.14.7) with ESMTP id w4EM5j5w010919; Tue, 15 May 2018 00:05:57 +0200 (CEST) (envelope-from jhs@berklix.com) Message-Id: <201805142205.w4EM5j5w010919@fire.js.berklix.net> To: current@freebsd.org cc: Ed Maste Subject: Re: HEADS-UP: Linker issues building amd64 kernels with config & make From: "Julian H. Stacey" Organization: http://berklix.eu BSD Unix Linux Consultants, Munich Germany User-agent: EXMH on FreeBSD http://berklix.eu/free/ X-From: http://www.berklix.eu/~jhs/ In-reply-to: Your message "Mon, 14 May 2018 13:50:33 -0400." Date: Tue, 15 May 2018 00:05:45 +0200 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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, 14 May 2018 22:06:14 -0000 Ed Maste wrote: > As of r333461 the amd64 kernel makes use of ifuncs, and requires > support in the linker. A safety belt added in r333470 enforces this, > and will produce an explicit error if the linker does not support > ifuncs. > > lld is the default bootstrap linker for amd64 and has ifunc support. > The typical 'make buildworld' (or kernel-toolchain) followed by 'make > buildkernel' process will use lld and successfully link a working > kernel. > > The old-style kernel build (using 'config' followed by a 'make' in the > kernel directory) uses the host linker (/usr/bin/ld). This still > defaults to GNU ld 2.17.50, which does not support ifuncs. This can be > worked around in one of two ways: > > 1. Install lld as the system linker (/usr/bin/ld), by adding > WITH_LLD_IS_LD to /etc/src.conf and building and install world. > WITH_LLD_IS_LD will become the default on amd64 in the near future - > I'm just waiting on updates to the lang/ghc port and another exp-run. > > 2. Override LD when you build the kernel: > $ LD=ld.lld make > > These tool chain components will undergo additional changes for the next while. I guess this explains : Date: Sun, 13 May 2018 20:26:38 +0200 Subject: cd /sys/amd64/compile/GENERIC;make cleandepend; make cleandepend .svn_revision 333575 linking kernel.full iflib.o:(.rodata+0x178): undefined reference to `noop_attach' iflib.o:(.rodata+0x188): undefined reference to `iflib_pseudo_detach' PS Bloat factor > 20: 2M static V 40M dynamic, (normaly dynamics are smaller, not larger). cd /usr/bin; ls -l *ld* -r-xr-xr-x 2 root wheel 1935992 May 13 12:48 ld* -r-xr-xr-x 1 root wheel 40449288 May 13 12:54 ld.lld* file ld ld.lld ld: ELF 64-bit LSB executable, x86-64, version 1 (FreeBSD), statically linked, for FreeBSD 12.0 (1200063), FreeBSD-style, stripped ld.lld: ELF 64-bit LSB executable, x86-64, version 1 (FreeBSD), dynamically linked, interpreter /libexec/ld-elf.so.1, for FreeBSD 12.0 (1200063), FreeBSD-style, stripped Cheers, Julian -- Julian Stacey, Computer Consultant, Systems Engineer, BSD Linux Unix, Munich Brexit Referendum stole 3,700,000 votes, inc. 700,000 from British in EU. UK Govt. lied it's "democratic" in Article 50 letter to EU paragraph 3. Petition for votes: http://berklix.eu/queen/ From owner-freebsd-current@freebsd.org Mon May 14 22:58:48 2018 Return-Path: Delivered-To: freebsd-current@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 A3736E7E110 for ; Mon, 14 May 2018 22:58:48 +0000 (UTC) (envelope-from carpeddiem@gmail.com) 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 2C70C68CAB for ; Mon, 14 May 2018 22:58:48 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id DE890E7E10C; Mon, 14 May 2018 22:58:47 +0000 (UTC) Delivered-To: current@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 CCCB3E7E10B for ; Mon, 14 May 2018 22:58:47 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-it0-x22a.google.com (mail-it0-x22a.google.com [IPv6:2607:f8b0:4001:c0b::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 635EC68C91 for ; Mon, 14 May 2018 22:58:47 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mail-it0-x22a.google.com with SMTP id q4-v6so15309266ite.3 for ; Mon, 14 May 2018 15:58:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=zCraJ8n+JPtNo2WcUyHYSKSuZh5yfg36dB881d3wdeU=; b=MRSY8xvirxVXrbGwyuz8f0yoCpfnEpTRVBmFgsL7TJSMvo2aUNSe1emK+0Y1m6ZrIv 4v4zN/CK9FVxZufjwQXWUCVz0CAM8vb066OAA8pNSb4JTm+PII/mxYLBLyFiU/SkCyTA 6kF0Jk9jNsuNVvXjB/OIuCgBEHO4uJpKoRwdJ+YMNXlasrPyHmjgAyr8O0St/DQJNtI2 EbYBWmAt9cosBgCk4AgNYtFQMrNI+ZcG5+yAOch++yOfsmU07zskZ6W3TllTSuPU5arK BHzV7Qu7xSiF/9tW6IR4Vk7UUdPk97npo/GIz19tfeVq9OCrZRONpXoTd5j6x/t7OGUn eiAw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=zCraJ8n+JPtNo2WcUyHYSKSuZh5yfg36dB881d3wdeU=; b=bm/nOgSJJzgooL/4KYSQmWVWc2yq9JVIwlDttJaY40bLiX8FuIqeweiWSDhF18nk2O RHBthv3OJbIPYXQbtCFCA1s5uP7mX6gHCm5p19cO7yS2YDdTweQcBqdG1hibCq2rb2Ib vbvRsBhauh4z6gPxIKvRgYRJXPORk9sT7E5klAXt3eJqiByP7dsEX9gdj84Y7qI7KJ82 ywmgZ2fgw1Zv71qLBCSaWDUT4WXNbUK2tFSwGqAfupr9hZCKF8i5lGY3r/kACTyOA1Em d5B2BEI9IvTk9VRLjiXaWBddNES55+Dw/cnZXZt3A0zAqJahii+WsKbz6Sd6zmC+yxMj R4nQ== X-Gm-Message-State: ALKqPwfPgFMVmeILJjU0mekAISIH4Ne5NIGwu88hDHiO0PZZi9dwAvKY ScwhAYhwOnAQLa/Q3I75tozoOV3eP3qZZob9XdGYlK3H X-Google-Smtp-Source: AB8JxZr9wScjbkLm/epHMM6Y4yRmJ7k+Bc3EY1dVvpiBjBsZ6vWoCD7dTqtAnSX/4QWrcsT9RRKgIXnOlP7dOIX42ag= X-Received: by 2002:a6b:298f:: with SMTP id p137-v6mr13230112iop.288.1526338726432; Mon, 14 May 2018 15:58:46 -0700 (PDT) MIME-Version: 1.0 Sender: carpeddiem@gmail.com Received: by 10.107.130.167 with HTTP; Mon, 14 May 2018 15:58:25 -0700 (PDT) In-Reply-To: <201805142205.w4EM5j5w010919@fire.js.berklix.net> References: <201805142205.w4EM5j5w010919@fire.js.berklix.net> From: Ed Maste Date: Mon, 14 May 2018 18:58:25 -0400 X-Google-Sender-Auth: scRqC-42i3giK4YthoVKii4LKXg Message-ID: Subject: Re: HEADS-UP: Linker issues building amd64 kernels with config & make To: "Julian H. Stacey" Cc: current Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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, 14 May 2018 22:58:49 -0000 On 14 May 2018 at 18:05, Julian H. Stacey wrote: > > I guess this explains : > Date: Sun, 13 May 2018 20:26:38 +0200 > Subject: cd /sys/amd64/compile/GENERIC;make cleandepend; make cleandepend > .svn_revision 333575 > linking kernel.full > iflib.o:(.rodata+0x178): undefined reference to `noop_attach' > iflib.o:(.rodata+0x188): undefined reference to `iflib_pseudo_detach' No, that's something else; I haven't seen that problem before. Note that we've been using lld as the default bootstrap linker (i.e., the linker used to link the world and kernel via 'make buildworld' and 'make buildkernel') since Jan 10 (r327783). > PS Bloat factor > 20: 2M static V 40M dynamic, Keep in mind that the in-tree ld.bfd was released over a decade ago, and has been obsolete for years now; a dynamically-linked contemporary ld.bfd 12MB. lld is much faster than any of them (more than 20x compared to in-tree ld.bfd on some operations) and all of the target architectures are supported by a single binary. From owner-freebsd-current@freebsd.org Mon May 14 23:33:29 2018 Return-Path: Delivered-To: freebsd-current@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 E1F80EA72FE for ; Mon, 14 May 2018 23:33:29 +0000 (UTC) (envelope-from jhs@berklix.com) 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 A3D6370311 for ; Mon, 14 May 2018 23:33:29 +0000 (UTC) (envelope-from jhs@berklix.com) Received: by mailman.ysv.freebsd.org (Postfix) id 643BFEA72F7; Mon, 14 May 2018 23:33:29 +0000 (UTC) Delivered-To: current@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 51A74EA72F6 for ; Mon, 14 May 2018 23:33:29 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from land.berklix.org (land.berklix.org [144.76.10.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "land.berklix.org", Issuer "land.berklix.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C750F7030D; Mon, 14 May 2018 23:33:28 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from mart.js.berklix.net (pD9FA824B.dip0.t-ipconnect.de [217.250.130.75]) (authenticated bits=0) by land.berklix.org (8.15.2/8.15.2) with ESMTPSA id w4ENVh4A082564 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 14 May 2018 23:31:47 GMT (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by mart.js.berklix.net (8.14.3/8.14.3) with ESMTP id w4ENXM35078987; Tue, 15 May 2018 01:33:22 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.7/8.14.7) with ESMTP id w4ENX9Xc095858; Tue, 15 May 2018 01:33:22 +0200 (CEST) (envelope-from jhs@berklix.com) Message-Id: <201805142333.w4ENX9Xc095858@fire.js.berklix.net> To: Ed Maste cc: current Subject: Re: HEADS-UP: Linker issues building amd64 kernels with config & make From: "Julian H. Stacey" Organization: http://berklix.eu BSD Unix Linux Consultants, Munich Germany User-agent: EXMH on FreeBSD http://berklix.eu/free/ X-From: http://www.berklix.eu/~jhs/ In-reply-to: Your message "Mon, 14 May 2018 18:58:25 -0400." Date: Tue, 15 May 2018 01:33:09 +0200 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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, 14 May 2018 23:33:30 -0000 Hi, Reference: > From: Ed Maste > Date: Mon, 14 May 2018 18:58:25 -0400 Ed Maste wrote: > On 14 May 2018 at 18:05, Julian H. Stacey wrote: > > > > I guess this explains : > > Date: Sun, 13 May 2018 20:26:38 +0200 > > Subject: cd /sys/amd64/compile/GENERIC;make cleandepend; make cleandepend > > .svn_revision 333575 > > linking kernel.full > > iflib.o:(.rodata+0x178): undefined reference to `noop_attach' > > iflib.o:(.rodata+0x188): undefined reference to `iflib_pseudo_detach' > > No, that's something else; I haven't seen that problem before. Ah ! Thanks > Note that we've been using lld as the default bootstrap linker (i.e., > the linker used to link the world and kernel via 'make buildworld' and > 'make buildkernel') since Jan 10 (r327783). > > > PS Bloat factor > 20: 2M static V 40M dynamic, > > Keep in mind that the in-tree ld.bfd was released over a decade ago, > and has been obsolete for years now; a dynamically-linked contemporary > ld.bfd 12MB. lld is much faster than any of them (more than 20x > compared to in-tree ld.bfd on some operations) and all of the target > architectures are supported by a single binary. OK Thanks. Cheers, Julian -- Julian Stacey, Computer Consultant, Systems Engineer, BSD Linux Unix, Munich Brexit Referendum stole 3,700,000 votes, inc. 700,000 from British in EU. UK Govt. lied it's "democratic" in Article 50 letter to EU paragraph 3. Petition for votes: http://berklix.eu/queen/ From owner-freebsd-current@freebsd.org Mon May 14 23:55:43 2018 Return-Path: Delivered-To: freebsd-current@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 C6AA4EA87A2 for ; Mon, 14 May 2018 23:55:43 +0000 (UTC) (envelope-from dim@FreeBSD.org) 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 63A5B75A5F for ; Mon, 14 May 2018 23:55:43 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 20F8FEA87A1; Mon, 14 May 2018 23:55:43 +0000 (UTC) Delivered-To: current@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 0F5E0EA87A0 for ; Mon, 14 May 2018 23:55:43 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (tensor.andric.com [87.251.56.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "tensor.andric.com", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 90CAB75A5D; Mon, 14 May 2018 23:55:42 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from coleburn.home.andric.com (coleburn.home.andric.com [192.168.0.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 1001653468; Tue, 15 May 2018 01:46:19 +0200 (CEST) From: Dimitry Andric Message-Id: Content-Type: multipart/signed; boundary="Apple-Mail=_F918EBE5-EB57-42D3-B15A-CB527D8CD307"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\)) Subject: Re: HEADS-UP: Linker issues building amd64 kernels with config & make Date: Tue, 15 May 2018 01:46:13 +0200 In-Reply-To: Cc: "Julian H. Stacey" , current To: Ed Maste References: <201805142205.w4EM5j5w010919@fire.js.berklix.net> X-Mailer: Apple Mail (2.3445.6.18) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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, 14 May 2018 23:55:44 -0000 --Apple-Mail=_F918EBE5-EB57-42D3-B15A-CB527D8CD307 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 15 May 2018, at 00:58, Ed Maste wrote: >=20 > On 14 May 2018 at 18:05, Julian H. Stacey wrote: >>=20 >> I guess this explains : >> Date: Sun, 13 May 2018 20:26:38 +0200 >> Subject: cd /sys/amd64/compile/GENERIC;make cleandepend; make = cleandepend >> .svn_revision 333575 >> linking kernel.full >> iflib.o:(.rodata+0x178): undefined reference to `noop_attach' >> iflib.o:(.rodata+0x188): undefined reference to = `iflib_pseudo_detach' >=20 > No, that's something else; I haven't seen that problem before. >=20 > Note that we've been using lld as the default bootstrap linker (i.e., > the linker used to link the world and kernel via 'make buildworld' and > 'make buildkernel') since Jan 10 (r327783). >=20 >> PS Bloat factor > 20: 2M static V 40M dynamic, >=20 > Keep in mind that the in-tree ld.bfd was released over a decade ago, > and has been obsolete for years now; a dynamically-linked contemporary > ld.bfd 12MB. lld is much faster than any of them (more than 20x > compared to in-tree ld.bfd on some operations) and all of the target > architectures are supported by a single binary. Not just that: since lld can do link time optimization (LTO), it also contains large parts of LLVM, e.g. the backend of the compiler. We could maybe save some space by putting all the LLVM stuff into a separate dynamic library, and re-using that from both clang and lld, but such a dynamic library has its own issues. (Takes a long time and lots of memory to link, and probably takes quite some time to dynamically load at runtime too.) -Dimitry --Apple-Mail=_F918EBE5-EB57-42D3-B15A-CB527D8CD307 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.2 iF0EARECAB0WIQR6tGLSzjX8bUI5T82wXqMKLiCWowUCWvofxQAKCRCwXqMKLiCW o6fLAKDaMI5uW/1iefhUIEFPqzbA3MOn8wCg9kmf7AUL9rOqE8S+OQsVOKT/ajI= =qP6/ -----END PGP SIGNATURE----- --Apple-Mail=_F918EBE5-EB57-42D3-B15A-CB527D8CD307-- From owner-freebsd-current@freebsd.org Tue May 15 03:35:24 2018 Return-Path: Delivered-To: freebsd-current@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 8B47BED0668 for ; Tue, 15 May 2018 03:35:24 +0000 (UTC) (envelope-from theron.tarigo@gmail.com) Received: from mail-qk0-x22e.google.com (mail-qk0-x22e.google.com [IPv6:2607:f8b0:400d:c09::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 25A9E86907; Tue, 15 May 2018 03:35:24 +0000 (UTC) (envelope-from theron.tarigo@gmail.com) Received: by mail-qk0-x22e.google.com with SMTP id p186-v6so11856974qkd.1; Mon, 14 May 2018 20:35:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:subject:to:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=k9M+2zJ5aCB4UY1M1/RV0klZ3bRqrUzXqKsT746v6TY=; b=SpxASwLRQ2dohQCeWovNdIV0UvbQ0ki0DzJHuuosspOKXtRKFh9eXGPlunettjfqXx O4xcih2ONGhODJHmdW27dNqePQipZI0fy4uqOZmr8IrjWdc8hzDIFloicKtXkpqkwcX7 jnE41Djr7sGTZIanU7A0QqxkN5wTSD3MgvNAXA98j00Rmr0+BQ+iSwlLWONHWVF7VFna NpYYKFW72XaOX8xc6cHNgaQK4N3Eh0B+TJLE0XXlh4BNv5bc8LDfeNbo1XASjs1LrBa5 0+IIwL+61Eh7u3qUxhlcmqWx0KO4plvHndjwGF5Udt8PZ8yEq2c5tv3QCvV5f6AqOVF6 ZjHA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:subject:to:references:from:message-id :date:user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=k9M+2zJ5aCB4UY1M1/RV0klZ3bRqrUzXqKsT746v6TY=; b=BVWrQP0JREZoNvPVN+UfE1XQ8i30WLWd2aJPMP163bR0FVnNfRHM0r2jwa2EHSEavc vcoalvIp+VV3xqeaC/Q+v7Q9jOK6lbHO4N2JENJAzFSdb55bEL3BvFQgpRjrTGPtVyug Ge75KO9rAfkNusASTLcZtcVYaBOYJYoLbARIVyEkc0TapyCCSoKFVIjS6cRtRq9CU3PX GZ/b+yOtIPkiD/HIQP0paCcBuY8FuQoYsf8qEZ89NsAYrnyeKn2LTKOEk9yjhP1wBTnS x8HMtG8ckqPWHX33kfRsGiFIzfd0TOxyeYkGcFEKz+iqh3rqpSsAgPaYWmep8C44a/Q8 k5vQ== X-Gm-Message-State: ALKqPwdjoKKYnRjy+zl22E+QvCBV4SHmufUWKWLixGZ9KRiebjCH/0ys +UoOUjFRWGGzf46JG11QtSBHn392T7o= X-Google-Smtp-Source: AB8JxZpkJchBx6piu/RnDVxjyVbGBMWc4vRf0QckbcqhH8xnBncJA36KJHSJhuZOex5aQzNHZXJT+g== X-Received: by 2002:a37:5ac5:: with SMTP id o188-v6mr10639167qkb.295.1526355323337; Mon, 14 May 2018 20:35:23 -0700 (PDT) Received: from [10.0.0.163] (c-65-96-175-209.hsd1.ma.comcast.net. [65.96.175.209]) by smtp.gmail.com with ESMTPSA id w51-v6sm8648544qtc.97.2018.05.14.20.35.22 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 14 May 2018 20:35:22 -0700 (PDT) Sender: Theron Tarigo Subject: Re: suspend/resume regression To: Pete Wright , Niclas Zeising , Andriy Gapon , FreeBSD Current References: <1e608109-fcdd-d794-b03a-2e417300b95a@nomadlogic.org> <3488a8a4-8cad-d6a8-0852-3bbbdd971c7f@gmail.com> <26f5ec31-3994-eac9-0c43-6d2458c35ad0@nomadlogic.org> <9f7fcdaa-99ea-98f4-8ef3-c8da6060542e@nomadlogic.org> From: Theron Message-ID: Date: Mon, 14 May 2018 23:35:21 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <9f7fcdaa-99ea-98f4-8ef3-c8da6060542e@nomadlogic.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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: Tue, 15 May 2018 03:35:24 -0000 On 05/13/18 15:44, Pete Wright wrote: >> so i've done a bit more debugging on my end.  i've even installed the >> 11.2-BETA branch last night since 11-STABLE worked without issues >> about a month or so ago. >> >> i've set "debug.acpi.resume_beep=1" and when resuming after entering >> an S3 sleep state the bell rings and does not stop until i do a hard >> reset (both with i915kms loaded and unloaded). >> >> kinda at a loss as to how this could break both CURRENT and basically >> 11-STABLE.  i'm going to make a ubuntu live image and test that, my >> laptop is a System76 laptop that shipped with ubuntu originally.  if >> that is broken as well then i guess this could be a hardware issue. >> > ubuntu live image suspends/resumes without issue so this certainly > seems to be a freebsd issue unfortunately.  i guess next step is to > attempt to find a working CURRENT snapshot that does suspend/resume > without issue then start looking at commits? > > -pete > Returning to the original issue: complete failure to resume, rather than slowness: I am affected as well.  CURRENT r333093 worked, but r333582 fails in a manner consistent with what Pete has described, with or without drm loaded.  There have been a few commit messages mentioning ACPI in that window of history, which I will use to help me bisect when I have time. Theron From owner-freebsd-current@freebsd.org Tue May 15 08:53:21 2018 Return-Path: Delivered-To: freebsd-current@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 EFAD1EEA854 for ; Tue, 15 May 2018 08:53:20 +0000 (UTC) (envelope-from etnapierala@gmail.com) Received: from mail-wr0-x22e.google.com (mail-wr0-x22e.google.com [IPv6:2a00:1450:400c:c0c::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 543766DEF0; Tue, 15 May 2018 08:53:20 +0000 (UTC) (envelope-from etnapierala@gmail.com) Received: by mail-wr0-x22e.google.com with SMTP id q3-v6so15097610wrj.6; Tue, 15 May 2018 01:53:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:mail-followup-to :references:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=05ez7RR98m0YeBSGBGW6np86Ms0fMH9OwdfGMjD0B84=; b=rNHcjv0N+JsHBFl7KmBfMVLnkelk5xH1o1j+vElA0XiEVfAQ+DgjhTmUbLourKmVFB gQY8cnup5dYCqTjKbVP0qa2o6A/n7Y/YBSUEIE4r1UYFRHlRDP3NO0J+1qY/hznhTHzp QPL6Kdz7633zrQ+Vc9pftDTnDNrXdiGCUYyDa4rJWkauD0P9goUrxmjDPCqqkx9I3NVH EJFRylRZpgPOHFZOCJ1rxc8pCseXDWZww8nANfPXAf0Nqzp0BsHWzlYxY5pNk2PkLtLA 7muPovq+UHNT+nlNNXIH0G4QT8xtGsI8HGv5UKG3do08JuVIfllQMvKGlJmJR9M/nWOc howg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=05ez7RR98m0YeBSGBGW6np86Ms0fMH9OwdfGMjD0B84=; b=ms7SWbsGvZ/0nrCPJ2GWn5PhjfPfkY+Wq4ZlS0RzERCCzhVlxPWoAvgJs14gs/T5s4 Vxa4moCxBVp9KLwB8LeWwP81O0lxfGR/6xHRtj5tnR+TmVRQv9F6aRnwKdVjL/Vb24ke /mA9DCinU3hicYvJEE5cR8DyzWVMN2SnsEar6JIQElFd64ZM/1TZkF/3t2FnShC3MHDW AL0OevO5X01PXdjXUPFc+5kjzM7Q8qFYbj00iVQyjkO0HaNmbs/NyhdtupirtyhgSGBR 9TjOKCyHJbhFilE7neRXf8j9S9xlyvuyCehRISoz47d2JpEhKikap05rhzDvGy040Od8 F0AA== X-Gm-Message-State: ALKqPwffFn1PD0x1iqgaCydwle+Wb/GwkI3aWwv5uqjQ5VkJpIlQrNG8 1Qp8UIWTj8LyD5fr50cy8Ecphg== X-Google-Smtp-Source: AB8JxZruQXpXqFo6rN6Ll7n0vvsNVUrdt21irggN/bk3PEUnfLXFgzZiMEV2lz2OvRlt87Pe15xZkw== X-Received: by 2002:adf:c412:: with SMTP id v18-v6mr10250437wrf.20.1526374398877; Tue, 15 May 2018 01:53:18 -0700 (PDT) Received: from brick (cpc92302-cmbg19-2-0-cust461.5-4.cable.virginm.net. [82.1.209.206]) by smtp.gmail.com with ESMTPSA id y42-v6sm15714586wry.21.2018.05.15.01.53.17 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 15 May 2018 01:53:17 -0700 (PDT) Sender: =?UTF-8?Q?Edward_Tomasz_Napiera=C5=82a?= Date: Tue, 15 May 2018 09:53:15 +0100 From: Edward Tomasz =?utf-8?Q?Napiera=C5=82a?= To: Andriy Gapon Cc: =?iso-8859-1?Q?Mika=EBl?= Urankar , Niclas Zeising , Pete Wright , Theron , FreeBSD Current Subject: Re: suspend/resume regression Message-ID: <20180515085315.GA3309@brick> Mail-Followup-To: Andriy Gapon , =?iso-8859-1?Q?Mika=EBl?= Urankar , Niclas Zeising , Pete Wright , Theron , FreeBSD Current References: <1e608109-fcdd-d794-b03a-2e417300b95a@nomadlogic.org> <3488a8a4-8cad-d6a8-0852-3bbbdd971c7f@gmail.com> <26f5ec31-3994-eac9-0c43-6d2458c35ad0@nomadlogic.org> <9f7fcdaa-99ea-98f4-8ef3-c8da6060542e@nomadlogic.org> <20180514080604.GA2006@brick> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.9.5 (2018-04-13) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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: Tue, 15 May 2018 08:53:21 -0000 On 0514T1158, Andriy Gapon wrote: > On 14/05/2018 11:44, Mikaël Urankar wrote: > > Could it be the same problem described here? > > https://lists.freebsd.org/pipermail/freebsd-hackers/2018-May/052778.html > > That problem is _not_ a regression. FWIW, this machine (the one affected by the sluggishness) uses TSC-low by default, not HPET. Changing the kern.timecounter.hardware to eg HPET or ACPI-fast doesn't change the symptoms. From owner-freebsd-current@freebsd.org Tue May 15 14:48:28 2018 Return-Path: Delivered-To: freebsd-current@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 6119EEDEE26 for ; Tue, 15 May 2018 14:48:28 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from vps-mail.nomadlogic.org (mail.nomadlogic.org [IPv6:2607:f2f8:a098::2]) (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 87E9F7CBAB; Tue, 15 May 2018 14:48:27 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from [192.168.2.9] (cpe-23-243-163-13.socal.res.rr.com [23.243.163.13]) by vps-mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id 4db3d14d TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO; Tue, 15 May 2018 07:48:24 -0700 (PDT) Subject: Re: suspend/resume regression To: Theron , Niclas Zeising , Andriy Gapon , FreeBSD Current References: <1e608109-fcdd-d794-b03a-2e417300b95a@nomadlogic.org> <3488a8a4-8cad-d6a8-0852-3bbbdd971c7f@gmail.com> <26f5ec31-3994-eac9-0c43-6d2458c35ad0@nomadlogic.org> <9f7fcdaa-99ea-98f4-8ef3-c8da6060542e@nomadlogic.org> From: Pete Wright Message-ID: <35d0f223-681a-205a-0f57-4ec360761726@nomadlogic.org> Date: Tue, 15 May 2018 07:48:23 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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: Tue, 15 May 2018 14:48:28 -0000 On 05/14/2018 20:35, Theron wrote: > On 05/13/18 15:44, Pete Wright wrote: >>> so i've done a bit more debugging on my end.  i've even installed >>> the 11.2-BETA branch last night since 11-STABLE worked without >>> issues about a month or so ago. >>> >>> i've set "debug.acpi.resume_beep=1" and when resuming after entering >>> an S3 sleep state the bell rings and does not stop until i do a hard >>> reset (both with i915kms loaded and unloaded). >>> >>> kinda at a loss as to how this could break both CURRENT and >>> basically 11-STABLE.  i'm going to make a ubuntu live image and test >>> that, my laptop is a System76 laptop that shipped with ubuntu >>> originally.  if that is broken as well then i guess this could be a >>> hardware issue. >>> >> ubuntu live image suspends/resumes without issue so this certainly >> seems to be a freebsd issue unfortunately.  i guess next step is to >> attempt to find a working CURRENT snapshot that does suspend/resume >> without issue then start looking at commits? >> >> -pete >> > Returning to the original issue: complete failure to resume, rather > than slowness: I am affected as well.  CURRENT r333093 worked, but > r333582 fails in a manner consistent with what Pete has described, > with or without drm loaded.  There have been a few commit messages > mentioning ACPI in that window of history, which I will use to help me > bisect when I have time. > do you think it may be due to r333150 "Merge ACPICA 20180427." not sure if that's been merged into 11-STABLE, but it seems to touch a lot of bits that could effect suspend/resume. -p -- Pete Wright pete@nomadlogic.org @nomadlogicLA From owner-freebsd-current@freebsd.org Tue May 15 15:09:16 2018 Return-Path: Delivered-To: freebsd-current@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 32A78EE0420 for ; Tue, 15 May 2018 15:09:16 +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 A542E81FE7; Tue, 15 May 2018 15:09:15 +0000 (UTC) (envelope-from zeising+freebsd@daemonic.se) Received: from cid.daemonic.se (localhost [IPv6:::1]) by mail.daemonic.se (Postfix) with ESMTP id 40lgvZ03p5zDhSJ; Tue, 15 May 2018 15:09:14 +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=1526396953; bh=wR1W8WErrnzqgfQG37adoOmQ qey5tfSarYnPlQXDR8E=; b=Kkdr2JeuicvVaaQD0asvnn+dbn94+mjeRZmacR6t yBCsgMbZA1CoO2ZFpjZK1uPW1N+8XVd/TBmusAQjC781Ef3kRxqj4YBRvkmJXnct NomsAYwJI6yh+LLIp7xKnxDuSLJY7wBdgVZeNkLNgaUUFXCL5AoTdg9ZQwJByhy7 p6w= 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 8YnLoW27en68; Tue, 15 May 2018 15:09:13 +0000 (UTC) Received: from garnet.daemonic.se (host-90-236-56-126.mobileonline.telia.com [90.236.56.126]) by mail.daemonic.se (Postfix) with ESMTPSA id 40lgvY1dWdzDhBg; Tue, 15 May 2018 15:09:13 +0000 (UTC) Subject: Re: suspend/resume regression To: Pete Wright , Theron , Andriy Gapon , FreeBSD Current References: <1e608109-fcdd-d794-b03a-2e417300b95a@nomadlogic.org> <3488a8a4-8cad-d6a8-0852-3bbbdd971c7f@gmail.com> <26f5ec31-3994-eac9-0c43-6d2458c35ad0@nomadlogic.org> <9f7fcdaa-99ea-98f4-8ef3-c8da6060542e@nomadlogic.org> <35d0f223-681a-205a-0f57-4ec360761726@nomadlogic.org> From: Niclas Zeising Message-ID: <86e84442-d54c-a7da-3849-d0d1ad6e7475@daemonic.se> Date: Tue, 15 May 2018 17:09:12 +0200 User-Agent: Mutt/1.5.21 MIME-Version: 1.0 In-Reply-To: <35d0f223-681a-205a-0f57-4ec360761726@nomadlogic.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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: Tue, 15 May 2018 15:09:16 -0000 On 05/15/18 16:48, Pete Wright wrote: >=20 >=20 > On 05/14/2018 20:35, Theron wrote: >> On 05/13/18 15:44, Pete Wright wrote: >>>> so i've done a bit more debugging on my end.=C2=A0 i've even install= ed=20 >>>> the 11.2-BETA branch last night since 11-STABLE worked without=20 >>>> issues about a month or so ago. >>>> >>>> i've set "debug.acpi.resume_beep=3D1" and when resuming after enteri= ng=20 >>>> an S3 sleep state the bell rings and does not stop until i do a hard= =20 >>>> reset (both with i915kms loaded and unloaded). >>>> >>>> kinda at a loss as to how this could break both CURRENT and=20 >>>> basically 11-STABLE.=C2=A0 i'm going to make a ubuntu live image and= test=20 >>>> that, my laptop is a System76 laptop that shipped with ubuntu=20 >>>> originally.=C2=A0 if that is broken as well then i guess this could = be a=20 >>>> hardware issue. >>>> >>> ubuntu live image suspends/resumes without issue so this certainly=20 >>> seems to be a freebsd issue unfortunately.=C2=A0 i guess next step is= to=20 >>> attempt to find a working CURRENT snapshot that does suspend/resume=20 >>> without issue then start looking at commits? >>> >>> -pete >>> >> Returning to the original issue: complete failure to resume, rather=20 >> than slowness: I am affected as well.=C2=A0 CURRENT r333093 worked, bu= t=20 >> r333582 fails in a manner consistent with what Pete has described,=20 >> with or without drm loaded.=C2=A0 There have been a few commit message= s=20 >> mentioning ACPI in that window of history, which I will use to help me= =20 >> bisect when I have time. >> >=20 > do you think it may be due to r333150 >=20 > "Merge ACPICA 20180427." >=20 > not sure if that's been merged into 11-STABLE, but it seems to touch a=20 > lot of bits that could effect suspend/resume. >=20 I tried to revert that, but if I remember correctly, it didn't matter.=20 I have to do a new test though, when I have more time. Regards --=20 Niclas From owner-freebsd-current@freebsd.org Wed May 16 12:43:00 2018 Return-Path: Delivered-To: freebsd-current@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 43336EDFF0A for ; Wed, 16 May 2018 12:43:00 +0000 (UTC) (envelope-from david@catwhisker.org) 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 CD2A486FD6 for ; Wed, 16 May 2018 12:42:59 +0000 (UTC) (envelope-from david@catwhisker.org) Received: by mailman.ysv.freebsd.org (Postfix) id 8D89CEDFF09; Wed, 16 May 2018 12:42:59 +0000 (UTC) Delivered-To: current@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 7855DEDFF08 for ; Wed, 16 May 2018 12:42:59 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from mx.catwhisker.org (mx.catwhisker.org [198.144.209.73]) (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 B7BBC86FD5 for ; Wed, 16 May 2018 12:42:57 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.15.2/8.15.2) with ESMTP id w4GCguqK057320 for ; Wed, 16 May 2018 12:42:56 GMT (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.15.2/8.15.2/Submit) id w4GCgtx8057319 for current@freebsd.org; Wed, 16 May 2018 05:42:55 -0700 (PDT) (envelope-from david) Date: Wed, 16 May 2018 05:42:55 -0700 From: David Wolfskill To: current@freebsd.org Subject: Something between r333623 - r333670 locks up at start of boot Message-ID: <20180516124255.GJ1204@albert.catwhisker.org> Mail-Followup-To: David Wolfskill , current@freebsd.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="D8HGaWww+jmMTa6P" Content-Disposition: inline User-Agent: Mutt/1.9.5 (2018-04-13) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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: Wed, 16 May 2018 12:43:00 -0000 --D8HGaWww+jmMTa6P Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable =2E..on my laptop. Build machine was "fine." Links -- including to copies of most recent verbose dmesg.boot files -- may be found at . Last successful build & smoke-test of head on my laptop was: FreeBSD g1-215.catwhisker.org 12.0-CURRENT FreeBSD 12.0-CURRENT #190 r3336= 23M/333625:1200063: Tue May 15 04:24:00 PDT 2018 root@g1-215.catwhisker= =2Eorg:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY amd64 After updating sources to r333670, build was OK; smoke-test came to a screeching halt at: Booting... / (The "propeller" spins brefly -- maybe a second or two, then stops. At that point, the only thing I've found to break out of that is a power-cycle.) One possibly-salient item: while the build machine uses the default vt(4), I had switched the laptop to 'kern.vty=3D"sc"' via /boot/loader.conf no later than 23 August 2017 (mtime of the file), which seemed to have had a positive effect with respect to suspend/resume. (The laptop uses an Nvidia graphics card, in case that's useful to note, and I prefer to suspend it while I'm commuting by bike with it on my back.) I confirmed that booting kernel.old works OK, as does booting/running stable/11 (which I'm running as I type). CPU on the laptop is "Intel(R) Core(TM) i7-4810MQ CPU @ 2.80GHz (2793.60-MHz K8-class CPU)" Sorry; I don't know how that translates to Intel code names. There's more information about the laptop at . Peace, david --=20 David H. Wolfskill david@catwhisker.org Mr. Trump: Just how does reneging on the Iran nuclear deal make the US "saf= er?" See http://www.catwhisker.org/~david/publickey.gpg for my public key. --D8HGaWww+jmMTa6P Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEEzLfO+ReoAfQwZNd7FTnMQKBJ7hcFAlr8J09fFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEND QjdDRUY5MTdBODAxRjQzMDY0RDc3QjE1MzlDQzQwQTA0OUVFMTcACgkQFTnMQKBJ 7heAagf/bbNXGoMftDRjQHkpv4VMOcvWUf8J2pNQmZAmmR5N+RADi3d7GuysOtzv kFSIZy6KvQONibszyprG1+h3KM/zxlsxzNehOZRBCI41BjCHpxWsUKiUzSxgaxoX J99gM5JpNnLc3M/RZF5S8ajZCrkpGyr3/sF9Qzu2lP8I00NpA+aP6gCKho1EBnHx yfz9PNEiqJGmrCNw5C8Y1gaMmpEUAY1mvqe8YdPIFw5kHAt/uKXSmJuJjF0fbHN0 ee1sRwstlkF0bpwBwaPiGLrp68T/1iuyi9+IHv7N3nSj45EU941BBE1ZSJpiN3FV yGA0kTezwtQMF1OTkN9QO7ViaVV7iw== =T1uo -----END PGP SIGNATURE----- --D8HGaWww+jmMTa6P-- From owner-freebsd-current@freebsd.org Wed May 16 16:42:30 2018 Return-Path: Delivered-To: freebsd-current@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 EEB05EEC72F for ; Wed, 16 May 2018 16:42:29 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from mail.ignoranthack.me (ignoranthack.me [199.102.79.106]) (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 8FAAD705B7; Wed, 16 May 2018 16:42:28 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from [192.168.0.6] (67-0-228-75.albq.qwest.net [67.0.228.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: sbruno@ignoranthack.me) by mail.ignoranthack.me (Postfix) with ESMTPSA id 58058192ACC; Wed, 16 May 2018 08:45:26 +0000 (UTC) To: freebsd-current From: Sean Bruno Subject: Microcode Updater Changes Openpgp: preference=signencrypt Autocrypt: addr=sbruno@freebsd.org; prefer-encrypt=mutual; keydata= xsBNBFk+0UEBCADaf4bgxxKvMOhRV5NPoGWRCCGm49d6+1VFNlQ77WsY/+Zvf95TPULdRlnG w648KfxWt7+O3kdKhdRwnqlXWC7zA2Qt0dRE1yIqOGJ4jp4INvp/bcxWzgr0aoKOjrlnfxRV bh+s0rzdZt6TsNL3cVYxkC8oezjaUkHdW4mFJU249U1QJogkF8g0FeKNfEcjEkwJNX6lQJH+ EzCWT0NCk6J+Xyo+zOOljxPp1OUfdvZi3ulkU/qTZstGVWxFVsP8xQklV/y3AFcbIYx6iGJ4 5L7WuB0IWhO7Z4yHENr8wFaNYwpod9i4egX2BugbrM8pOfhN2/qqdeG1L5LMtXw3yyAhABEB AAHNN1NlYW4gQnJ1bm8gKEZyZWVCU0QgRGV2ZWxvcGVyIEtleSkgPHNicnVub0BmcmVlYnNk Lm9yZz7CwJQEEwEKAD4WIQToxOn4gDUE4eP0ujS95PX+ibX8tgUCWT7RQQIbAwUJBaOagAUL CQgHAwUVCgkICwUWAwIBAAIeAQIXgAAKCRC95PX+ibX8ttKTCACFKzRc56EBAlVotq02EjZP SfX+unlk6AuPBzShxqRxeK+bGYVCigrYd1M8nnskv0dEiZ5iYeND9HIxbpEyopqgpVTibA7w gBXaZ7SOEhNX1wXwg14JrralfSmPFMYni+sWegPMX/zwfAsn1z4mG1Nn44Xqo3o7CfpkMPy6 M5Bow2IDzIhEYISLR+urxs74/aHU35PLtBSDtu18914SEMDdva27MARN8mbeCDbuJVfGCPWy YHuy2t+9u2Zn5Dd+t3sBXLM9gpeaMm+4x6TNPpESygbVdh4tDdjVZ9DK/bWFg0kMgfZoaq6J l0jNsQXrZV3bzYNFbVw04pFcvA2GIJ7xzsBNBFk+0UEBCADIXBmQOaKMHGbc9vwjhV4Oj5aZ DdhNedn12FVeTdOXJvuTOusgxS29lla0RenHGDsgD08UiFpasBXWq/E+BhQ19d+iRbLLR17O KKc1ZGefoVbLARLXD68J5j4XAyK+6k2KqBLlqzAEpHTzsksM9naARkVXiEVcrt6ciw0FSm8n kuK3gDKKe93XfzfP+TQdbvvzJc7Fa+appLbXz61TM1aikaQlda8bWubDegwXbuoJdB34xU1m yjr/N4o+raL0x7QrzdH+wwgrTTo+H4S2c1972Skt5K5tbxLowfHicRl23V8itVQr3sBtlX4+ 66q+Apm7+R36bUS/k+G45Sp6iPpxABEBAAHCwHwEGAEKACYWIQToxOn4gDUE4eP0ujS95PX+ ibX8tgUCWT7RQQIbDAUJBaOagAAKCRC95PX+ibX8trrIB/9Pljqt/JGamD9tx4dOVmxSyFg9 z2xzgklTLuDgS73MM120mM7ao9AQUeWiSle/H0UCK7xPOzC/aeUC4oygDQKAfkkNbCNTo3+A qDjBRA8qx0e9a/QjDL+RFgD4L5kLT4tToY8T8HaBp8h03LBfk510IaI8oL/Jg7vpM3PDtJMW tUi2H+yNFmL3NfM2oBToWKLFsoP54f/eeeImrNnrlLjLHPzqS+/9apgYqX2Jwiv3tHBc4FTO GuY8VvF7BpixJs8Pc2RUuCfSyodrp1YG1kRGlXAH0cqwwr0Zmk4+7dZvtVQMCl6kS6q1+84q JwtItxS2eXSEA4NO0sQ3BXUywANh Message-ID: <17625f2a-c637-26dd-1d6d-93b733781f6c@freebsd.org> Date: Wed, 16 May 2018 10:42:21 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="dqt9w8dod20nNcuTH4Ts3EME7Wi5rhKgs" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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: Wed, 16 May 2018 16:42:30 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --dqt9w8dod20nNcuTH4Ts3EME7Wi5rhKgs Content-Type: multipart/mixed; boundary="AtIAIB4embo8wk5HNRH41Yj6X688907dt"; protected-headers="v1" From: Sean Bruno To: freebsd-current Message-ID: <17625f2a-c637-26dd-1d6d-93b733781f6c@freebsd.org> Subject: Microcode Updater Changes --AtIAIB4embo8wk5HNRH41Yj6X688907dt Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable https://reviews.freebsd.org/D15443 The FreeBSD Foundation has collaborated with a few folks so that we can continue to process and update microcode on FreeBSD. This review represents the first step in updating our infrastructure. If you are currently using microcode updates, please give this a spin and report back if you see a different version of microcode being loaded on the new package vs the old package. sean bcc emaste --AtIAIB4embo8wk5HNRH41Yj6X688907dt-- --dqt9w8dod20nNcuTH4Ts3EME7Wi5rhKgs Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEE6MTp+IA1BOHj9Lo0veT1/om1/LYFAlr8X21fFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEU4 QzRFOUY4ODAzNTA0RTFFM0Y0QkEzNEJERTRGNUZFODlCNUZDQjYACgkQveT1/om1 /LaR1wf+Kx5fT1MYFBEfuKYgpYNx5OTnSL0ce7x5vd+mGMLw5yHOj8YSPElVVdF5 5tmzLHK1j8hP/zhc1bUq+8qc9DUOjtXygCD/6VVzvbzv1o4TwEI1ijm2t67ru5OI 77Cq0gm0dixkjGTZOLUjhWefhbaZhdH2ezyEU8iRR9Xpy1UaEl3OrIt3oNfFz9lw ZTNzEesexhiESb3eiAR3a6XXdMx9g+XdlxMCeUKHdyn/rknzBIm7c3x6R+7S5C0C vM4qUp8NSb61PQ97aNJx9JS2WM+M7F0myj+0MlUdipplCO7ECWLuYMPc963GcBUo MlgslHMXc5VNrtzNTTDMX+rvYZAiyA== =3tO+ -----END PGP SIGNATURE----- --dqt9w8dod20nNcuTH4Ts3EME7Wi5rhKgs-- From owner-freebsd-current@freebsd.org Wed May 16 23:08:39 2018 Return-Path: Delivered-To: freebsd-current@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 5BF31EDBA3C; Wed, 16 May 2018 23:08:39 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-wr0-x22d.google.com (mail-wr0-x22d.google.com [IPv6:2a00:1450:400c:c0c::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CF0B481920; Wed, 16 May 2018 23:08:38 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-wr0-x22d.google.com with SMTP id y15-v6so3672803wrg.11; Wed, 16 May 2018 16:08:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to:cc; bh=HIZaOFtP6cLPAhv8pjEc86XrKKNKcLhaq6NbnpPP1Jw=; b=C4BIywzA0c4rraL26B62VlBKoPqPXQi+iOwcGEJJfIqKP5xBb4AzlggLLNdVcHeT1R +/5FT2A1Ar5rdaZtegnfM6gKdWXQoKFJ4j/nnR9WQWl8ZMP65/z8lHZf2J0JPqR9oTSi QeiDXjpM6a+BJCBxQuXNA4Ac+EEKd23FrjXWCnHxhZXTC/WY9gpO3sQ3WW9JeBBAQiwh PP1K5QBm/LYu151jY+gySXNT/xnuOJhcTG9R57tRZ59fQ7Dwg6/pxMBHFHwvhAd1101h Xg6d8dyUzdDS6A29Uk7+LszzdVI0RMkkLFjE2yNcPZFc5ciq/LvDLYXf+g3inVsAcSKS 21Jg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=HIZaOFtP6cLPAhv8pjEc86XrKKNKcLhaq6NbnpPP1Jw=; b=f6mSke6aeSKLXBDCCD0rLIEPDjXOea1J3A8TJ4nJnDkq/y/Ve8exn//FqQg/o/wnkl tOaosPmQES9KYUaM4iWVtXaRJVc5awtBh5LD22wghobAl+XTWgNjKKnhKgnekpaVz2ua CUe2kgIv+JXxakmCqSCV38id+wodSN/qSCX3A1Yx+NA5w0Vjn6u762TEsG0EL7EEtzgy UZ1Ez1BKaFyClVT/C/6wHgnZefb2+HhrF0OiBfpfw5ANuHGcNS7OAWpE7N8WEfU39Wja kq7Li78peQHBU6qP2zE1aiSkxSeCDJNjQiKJ/TgIrp8xNxqkjSZ7SxPD22KdWUzMBEVa W6Gw== X-Gm-Message-State: ALKqPwfhlD2VWI3lHx2PQKKFC2pE5MD6m1knh8VrHFPY4UcY+UsfwgjT XFF9Pfl9Gemq4MELQqfxZNsSi7FB03Fjt7w24AfaXw== X-Google-Smtp-Source: AB8JxZrI2LsqFEQSbBRHavzGjiH+NLr4UgrcNPVDLruGPfotoI/0YZsLXKKFcqQdBf2sxoXJa0V6slS4b0wfUfKXkkI= X-Received: by 2002:adf:d10f:: with SMTP id a15-v6mr2366485wri.165.1526512116913; Wed, 16 May 2018 16:08:36 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.146.194 with HTTP; Wed, 16 May 2018 16:07:56 -0700 (PDT) From: Johannes Lundberg Date: Thu, 17 May 2018 00:07:56 +0100 Message-ID: Subject: Lag after resume culprit found To: freebsd-current Cc: x11-list freebsd Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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: Wed, 16 May 2018 23:08:39 -0000 https://github.com/freebsd/freebsd/commit/66f063557f257baa9c8aeab9f933171eaa6e1cfa x86 cpususpend_handler: call wbinvd after setting suspend state bits How to test (i915kms) Start X with glxgears Confirm running stable at 60 fps suspend/resume (S3) glxgears is now fluctuating between 10-40 fps. Way past bedtime now so I stop here for today. Note: cross-posting - please think before "reply-to-all" /Johannes From owner-freebsd-current@freebsd.org Thu May 17 06:49:36 2018 Return-Path: Delivered-To: freebsd-current@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 EB234ED6DFE for ; Thu, 17 May 2018 06:49:35 +0000 (UTC) (envelope-from agapon@gmail.com) Received: from mail-lf0-f65.google.com (mail-lf0-f65.google.com [209.85.215.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 509396F125 for ; Thu, 17 May 2018 06:49:35 +0000 (UTC) (envelope-from agapon@gmail.com) Received: by mail-lf0-f65.google.com with SMTP id w202-v6so7033823lff.12 for ; Wed, 16 May 2018 23:49:35 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:openpgp:autocrypt :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=jzyZCCARl9xv0WeQxzp/FQAdWlaqw9SICT6k76DsSeM=; b=b6hmDlF4Cxq0wphqDuXyQCRfsl6ZuNf/9T6GASEfKbaCAphGedJRUJmtfYRsG4pHcn UWIXALroSNS7B6t3I2LpXHk9cf/LT3bGjtCuZHZEsvBhOJGAq/O8yMdAGkyqkzaCLGi3 eJrzZP3mMGqZnIvRQMTjxfWMyXZFBELYOpWEY9zmk5qFuZzbaUpe1Po3eDDGSI5Sje/V lQdKr5SR3IkqCloxJ0jKDIgEt4nfkdLsVB9oW35wtxmIef0VTkJ7dFNskE5FZtW7WOKw I/35rIplEe55u7eAG5axf+9YBmX7ci6jmX1pnWoS8n6EOh9IQwhtDxEEqeXG71yyXzdU 9QdA== X-Gm-Message-State: ALKqPweQe6KHlpRfJefKYDARzf20ZFfIBiuvrEO/825Lz7sTXO5v/fml Fp+t0dePeHHG9VmTv/2RcS9NY+Fs X-Google-Smtp-Source: AB8JxZpqCCPVCTXdagJxRBMBig/K6ke0+d/QyVBO5PKkoam6xv6MQScH1D5/qqt/0XM0T44/gcQeWQ== X-Received: by 2002:a2e:8595:: with SMTP id b21-v6mr2125005lji.131.1526539435644; Wed, 16 May 2018 23:43:55 -0700 (PDT) Received: from [192.168.0.88] (east.meadow.volia.net. [93.72.151.96]) by smtp.googlemail.com with ESMTPSA id h82-v6sm1043874lfb.31.2018.05.16.23.43.54 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 16 May 2018 23:43:55 -0700 (PDT) Subject: Re: Lag after resume culprit found To: Johannes Lundberg , freebsd-current References: From: Andriy Gapon Openpgp: preference=signencrypt Autocrypt: addr=avg@FreeBSD.org; prefer-encrypt=mutual; keydata= xsFNBFm4LIgBEADNB/3lT7f15UKeQ52xCFQx/GqHkSxEdVyLFZTmY3KyNPQGBtyvVyBfprJ7 mAeXZWfhat6cKNRAGZcL5EmewdQuUfQfBdYmKjbw3a9GFDsDNuhDA2QwFt8BmkiVMRYyvI7l N0eVzszWCUgdc3qqM6qqcgBaqsVmJluwpvwp4ZBXmch5BgDDDb1MPO8AZ2QZfIQmplkj8Y6Z AiNMknkmgaekIINSJX8IzRzKD5WwMsin70psE8dpL/iBsA2cpJGzWMObVTtCxeDKlBCNqM1i gTXta1ukdUT7JgLEFZk9ceYQQMJJtUwzWu1UHfZn0Fs29HTqawfWPSZVbulbrnu5q55R4PlQ /xURkWQUTyDpqUvb4JK371zhepXiXDwrrpnyyZABm3SFLkk2bHlheeKU6Yql4pcmSVym1AS4 dV8y0oHAfdlSCF6tpOPf2+K9nW1CFA8b/tw4oJBTtfZ1kxXOMdyZU5fiG7xb1qDgpQKgHUX8 7Rd2T1UVLVeuhYlXNw2F+a2ucY+cMoqz3LtpksUiBppJhw099gEXehcN2JbUZ2TueJdt1FdS ztnZmsHUXLxrRBtGwqnFL7GSd6snpGIKuuL305iaOGODbb9c7ne1JqBbkw1wh8ci6vvwGlzx rexzimRaBzJxlkjNfMx8WpCvYebGMydNoeEtkWldtjTNVsUAtQARAQABzR5BbmRyaXkgR2Fw b24gPGF2Z0BGcmVlQlNELm9yZz7CwZQEEwEIAD4WIQS+LEO7ngQnXA4Bjr538m7TUc1yjwUC WbgsiAIbIwUJBaOagAULCQgHAgYVCAkKCwIEFgIDAQIeAQIXgAAKCRB38m7TUc1yj+JAEACV l9AK/nOWAt/9cufV2fRj0hdOqB1aCshtSrwHk/exXsDa4/FkmegxXQGY+3GWX3deIyesbVRL rYdtdK0dqJyT1SBqXK1h3/at9rxr9GQA6KWOxTjUFURsU7ok/6SIlm8uLRPNKO+yq0GDjgaO LzN+xykuBA0FlhQAXJnpZLcVfPJdWv7sSHGedL5ln8P8rxR+XnmsA5TUaaPcbhTB+mG+iKFj GghASDSfGqLWFPBlX/fpXikBDZ1gvOr8nyMY9nXhgfXpq3B6QCRYKPy58ChrZ5weeJZ29b7/ QdEO8NFNWHjSD9meiLdWQaqo9Y7uUxN3wySc/YUZxtS0bhAd8zJdNPsJYG8sXgKjeBQMVGuT eCAJFEYJqbwWvIXMfVWop4+O4xB+z2YE3jAbG/9tB/GSnQdVSj3G8MS80iLS58frnt+RSEw/ psahrfh0dh6SFHttE049xYiC+cM8J27Aaf0i9RflyITq57NuJm+AHJoU9SQUkIF0nc6lfA+o JRiyRlHZHKoRQkIg4aiKaZSWjQYRl5Txl0IZUP1dSWMX4s3XTMurC/pnja45dge/4ESOtJ9R 8XuIWg45Oq6MeIWdjKddGhRj3OohsltKgkEU3eLKYtB6qRTQypHHUawCXz88uYt5e3w4V16H lCpSTZV/EVHnNe45FVBlvK7k7HFfDDkryM7BTQRZuCyIARAAlq0slcsVboY/+IUJdcbEiJRW be9HKVz4SUchq0z9MZPX/0dcnvz/gkyYA+OuM78dNS7Mbby5dTvOqfpLJfCuhaNYOhlE0wY+ 1T6Tf1f4c/uA3U/YiadukQ3+6TJuYGAdRZD5EqYFIkreARTVWg87N9g0fT9BEqLw9lJtEGDY EWUE7L++B8o4uu3LQFEYxcrb4K/WKmgtmFcm77s0IKDrfcX4doV92QTIpLiRxcOmCC/OCYuO jB1oaaqXQzZrCutXRK0L5XN1Y1PYjIrEzHMIXmCDlLYnpFkK+itlXwlE2ZQxkfMruCWdQXye syl2fynAe8hvp7Mms9qU2r2K9EcJiR5N1t1C2/kTKNUhcRv7Yd/vwusK7BqJbhlng5ZgRx0m WxdntU/JLEntz3QBsBsWM9Y9wf2V4tLv6/DuDBta781RsCB/UrU2zNuOEkSixlUiHxw1dccI 6CVlaWkkJBxmHX22GdDFrcjvwMNIbbyfQLuBq6IOh8nvu9vuItup7qemDG3Ms6TVwA7BD3j+ 3fGprtyW8Fd/RR2bW2+LWkMrqHffAr6Y6V3h5kd2G9Q8ZWpEJk+LG6Mk3fhZhmCnHhDu6CwN MeUvxXDVO+fqc3JjFm5OxhmfVeJKrbCEUJyM8ESWLoNHLqjywdZga4Q7P12g8DUQ1mRxYg/L HgZY3zfKOqcAEQEAAcLBfAQYAQgAJhYhBL4sQ7ueBCdcDgGOvnfybtNRzXKPBQJZuCyIAhsM BQkFo5qAAAoJEHfybtNRzXKPBVwQAKfFy9P7N3OsLDMB56A4Kf+ZT+d5cIx0Yiaf4n6w7m3i ImHHHk9FIetI4Xe54a2IXh4Bq5UkAGY0667eIs+Z1Ea6I2i27Sdo7DxGwq09Qnm/Y65ADvXs 3aBvokCcm7FsM1wky395m8xUos1681oV5oxgqeRI8/76qy0hD9WR65UW+HQgZRIcIjSel9vR XDaD2HLGPTTGr7u4v00UeTMs6qvPsa2PJagogrKY8RXdFtXvweQFz78NbXhluwix2Tb9ETPk LIpDrtzV73CaE2aqBG/KrboXT2C67BgFtnk7T7Y7iKq4/XvEdDWscz2wws91BOXuMMd4c/c4 OmGW9m3RBLufFrOag1q5yUS9QbFfyqL6dftJP3Zq/xe+mr7sbWbhPVCQFrH3r26mpmy841ym dwQnNcsbIGiBASBSKksOvIDYKa2Wy8htPmWFTEOPRpFXdGQ27awcjjnB42nngyCK5ukZDHi6 w0qK5DNQQCkiweevCIC6wc3p67jl1EMFY5+z+zdTPb3h7LeVnGqW0qBQl99vVFgzLxchKcl0 R/paSFgwqXCZhAKMuUHncJuynDOP7z5LirUeFI8qsBAJi1rXpQoLJTVcW72swZ42IdPiboqx NbTMiNOiE36GqMcTPfKylCbF45JNX4nF9ElM0E+Y8gi4cizJYBRr2FBJgay0b9Cp Message-ID: Date: Thu, 17 May 2018 09:43:54 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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 May 2018 06:49:36 -0000 On 17/05/2018 02:07, Johannes Lundberg wrote: > https://github.com/freebsd/freebsd/commit/66f063557f257baa9c8aeab9f933171eaa6e1cfa > x86 cpususpend_handler: call wbinvd after setting suspend state bits That's very interesting and surprising. That commit changes something that happens before suspend, it should not have any effect on the system state after resume. Does anyone have a theory of what could be wrong? > How to test (i915kms) > > Start X with glxgears > Confirm running stable at 60 fps > suspend/resume (S3) > glxgears is now fluctuating between 10-40 fps. -- Andriy Gapon From owner-freebsd-current@freebsd.org Thu May 17 07:34:10 2018 Return-Path: Delivered-To: freebsd-current@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 49A83EDACC8 for ; Thu, 17 May 2018 07:34:10 +0000 (UTC) (envelope-from jean-sebastien.pedron@dumbbell.fr) Received: from mail.made4.biz (mail.made4.biz [195.154.164.132]) (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 C410570B48 for ; Thu, 17 May 2018 07:34:09 +0000 (UTC) (envelope-from jean-sebastien.pedron@dumbbell.fr) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=dumbbell.fr ; s=20170531; h=Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From: References:To:Subject:Sender:Reply-To:Cc:Content-Transfer-Encoding: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=ocOchrL6DRl7LhgVWn7xtm4EzA0vT8e28ySiuDb4gb4=; b=AWVyPab8DIwAIOkVbL+uDqky37 bamE63aEF91ntLfb3HoAljSQkyBUjCgfvjyaUgXb2nihEaDshiDuhlSLREPSfEmvEm/Pweu1bdQid D18B64JBQ0FcdWHEggHddgUcfQQEvvTJ1SQTkxOaaldogP6Qqeoav+cqp6DFOQAHmfVY=; Received: from 2a02-8428-011a-ed01-6176-a9f1-6e42-08c8.rev.sfr.net ([2a02:8428:11a:ed01:6176:a9f1:6e42:8c8] helo=cassini.dumbbell.fr) by mail.made4.biz with esmtpa (Exim 4.90_1 (FreeBSD)) (envelope-from ) id 1fJDQN-000DNV-Jt for freebsd-current@freebsd.org; Thu, 17 May 2018 09:34:07 +0200 Subject: Re: Something between r333623 - r333670 locks up at start of boot To: freebsd-current@freebsd.org References: <20180516124255.GJ1204@albert.catwhisker.org> From: =?UTF-8?Q?Jean-S=c3=a9bastien_P=c3=a9dron?= Openpgp: preference=signencrypt Autocrypt: addr=jean-sebastien.pedron@dumbbell.fr; prefer-encrypt=mutual; keydata= xsFNBFLVuqcBEADJ1gT22qIjHl/i5wD6n6Bx38BU3YxhoJKLFMtf10+hDgvttdVlRskqw5Kd hixPFbpsWPNhd09vR2He1M8+jUybsQwZulcE63+Mz7z7TVpBcepy8ejHFoQ5eT6cOfKosZZ4 5fEIZiZKSzMncIkyhUFpbpXl/MQRvCEBQEmg6NAjXmaClGcGB4J9deKrib3UvrClYGNuVPiZ 21YLrG/dOiaSWoh+367bqA8bLUIU4G3sgGCYlj9V4UGOu8belQKF1urxp87qSB3KFhVxJTCn n6+rBPYgFLfJ6UT39NwsFsfcdwq16hyIdr4lZOitTtH6WJBDRDlcxOoLcobDLEOg0xntAXEN 1X3sKhpyChmsLU0wGaCSZXTkP60UONkTAi1xCaOwq1/R/vBDWh7b/DKqg194ymZWzilEwE/x jQVT+R85EKbqW1faZrrAQWPnekw4Kl/Ozow6cgTGa96oYTmIO/nGRqRwMhyyuQMG9DUnGZvB Gy5Nub64/i2/TBWN/iiM8g+400Tkz7KUJd/6+fFKdza2i6/3vQJ+MAS3WNp7fFY4tsX1fM03 zqD2KfNE9Xt6GZEwpaUMjGkHNoi+by6CcA/saggrRZQHFp9aFde2ivCLq4n9yh2Zy9yFGklq dhyvI+iBSxt46pGlihNeTX79Yris30WR/BvLxR+z1Y6YEO6eZQARAQABzTtKZWFuLVPDqWJh c3RpZW4gUMOpZHJvbiA8amVhbi1zZWJhc3RpZW4ucGVkcm9uQGR1bWJiZWxsLmZyPsLBlwQT AQoAQQIbAwULCQgHAwUVCgkICwUWAwIBAAIeAQIXgAIZARYhBNcvS4RwmJJEIOYrk9k4+cho FpgcBQJYdnydBQkJYyj2AAoJENk4+choFpgcHzAP/3cbgHofr0qk7DF5Ch+3dIapxbLbbf44 af30RdML9lmFarN7nYxkTlJMSdd8d8FfkL9XuGBZWrd5zxToDJ71xcvW6zbj6DwEsuCis6Np DYX5+cjGRuyIw2/stwWGmAaqHIUAwVNFd3p8A/ZDiBbnZXMFOiJCbogMhQlFuOlgjk1DfrE+ 3rfkTt+obfIe9c7ExjkCM85K3Iud2XbmXMJ+fU0PbaH2FVRly71vH6+y/puB2SQvXQ/MKT1Y cUjKph8+koJRwLuzlmbh2UmrxVhKW/cFx5VU0xEBNY2/ysgxndKlO2Q97sedAEuVzfaAJIQx plDKhoDBWVBoleExoJyyD8QfI3ACvHKxorh+dd4wyMuU1OfWExqlEhkYa/v3S9xeWy6hyA7J wrZtuVgafJfJK3qTj98E1yXeuvAACECQtcNHuZP1TuscBztNXvzGGutPnq3MniHOITm2xdJl +zQyheAe+NbxByCtbtyp6Y+OxTXJCRoEb5eiyvhLNdhGZkyYMJ44kPosc8dOm9aNiapeZWYJ bksTKJSeXaJMP1BBDHc3kugTK+f0bkoiR/vqGNUqIGD4/7KArssRvOBHub1G1Erbkj7YoiGE iLx2mrGFM7n/JoZowlw5fvvJS+RB39u3SGiXzAIuNl2VK9tRcHSpvAzYstyQRCGYUdE6xLVy 6PZMzsFNBFLVuqcBEADNXJ6T/nh6ZuNjqULb/WVL2KUStzw9ynAazw+rz74GxH6me1oURIvV u2YKWXgTydSLNzo8bDLde0PT1si1CsKHIYiFIglmG6LEXfYj/P2xwC6IFQD4rsbtphXUkaLa 6npUgqbqhSK0NItuJGyv7ODfmkvCX1Unto+eamES3S8wil8u3Azs0qe/Q/gDGAEZTQM/Uq76 Vwp37mN4c1nGCKePZJtywtAg9vUD/Lx7uRWIjGTR95gTBY5AUeX5VGeBiomUgGnG7nI3HoiZ hWu/KdmYfSzjYYj9739uGCzdpSyR/fAL9NWa6XeVpNm4QUPJAn1Gr556l6yiE6m118RNjuI8 5+z9ABCCSAdI+XS8qyFGc+8q7phpSTNjmSrVT1qzyoeNfrdv1kgTBolSzyCnawu8MjzZ7llj DuUqiF3huIjLu5BVBq+6f0UEC0LpYohZ2KGoN1y5oSEcHN0pmXKFglYrqG4zF3SCOve+/1DK 63L8zun1PGbza/h/Cjicv7qHNhprjNEHr4Bvbq+ibKjpRClxOcLWLv5+lhc1owHSdKQp5ylC EmIxgt9Xu8SYV5pwIQam4MUV2zPN5j/Rj26F4QNNQWmXvbF2qQjutHb6YdnYdEYDjF4b86JT 1h2WBhInB6CL1EyV3dkcin4PkKpJQIEzhmIuD9NxcMxqBYZRsigU4wARAQABwsF8BBgBCgAm AhsMFiEE1y9LhHCYkkQg5iuT2Tj5yGgWmBwFAlh2fO0FCQljKUYACgkQ2Tj5yGgWmBySsQ/+ Iuxc9Q0R5BeR7o4JXbXGlCn6FqgugMfYvZ/fNxPJ5Sn9SiPOezho00jswjQC3w26SwPhGQ8L v+y4ZNWk7zsrS2Y+1m3r278rm8hr59fmbV/EjthfG4rtYlAeiWYxmg2xsFGqb9VQhj5i0Aze SbGnZ8namMU/+zfYNc4/LGGatG245lCvLMZcgGxEk2E1IVHh2g0nAC0nQ+xlmfvrNshLz4WY hrZS0t3Q4VDsL6bmywcdtFvURYKadyZ9H0UAkkg+H+QEwfH5HLhwai/5uZNfSllbQfJosy0Y KdzzMTjPYp21tKVvUIBmw5NREb5E23IzQZB1FR7nwBE2mx7O6BkVrpfo4mUqDZYuJsp9R9V5 EeMvFS9cbax8g9zCOps+rzLkz/Ab6NWdvydIZIqR+f/55o8VliNF5qANwLKcHfDdr8HljaCo tS3OnV9KdnW50/rORGvy1WXVvcKcqbPSArcjR2PZW/jPJo/2JVu9dfLT3x7U+E/jT2mYQtY2 99mVduvdNTbG30AeXfMAGikNXn9Sc3nFWTMUoiniLmYvNTwl0AhUdtXT52b+8c3hjBx2Mq9r D4PUVBn8wXqIMqQBPg633mFM9X3fAPQGvrJEpc3INv84f9DsNO65YQkS6uUEuQFMKwXIs9zl KCX0cFBuqlnaE/YLB+L4IJMyan8Jk9NDa0A= Message-ID: Date: Thu, 17 May 2018 09:34:03 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <20180516124255.GJ1204@albert.catwhisker.org> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="2OK8DKkQXW7hvGFhGQnOii3bY2FD0v0wR" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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 May 2018 07:34:10 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --2OK8DKkQXW7hvGFhGQnOii3bY2FD0v0wR Content-Type: multipart/mixed; boundary="hGrHDkSRWv5qzkcNdp3z8wXrvl5MOA1eP"; protected-headers="v1" From: =?UTF-8?Q?Jean-S=c3=a9bastien_P=c3=a9dron?= To: freebsd-current@freebsd.org Message-ID: Subject: Re: Something between r333623 - r333670 locks up at start of boot References: <20180516124255.GJ1204@albert.catwhisker.org> In-Reply-To: <20180516124255.GJ1204@albert.catwhisker.org> --hGrHDkSRWv5qzkcNdp3z8wXrvl5MOA1eP Content-Type: text/plain; charset=windows-1252 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 16.05.2018 14:42, David Wolfskill wrote: > After updating sources to r333670, build was OK; smoke-test came to a > screeching halt at: >=20 > Booting... > / >=20 > (...) >=20 > One possibly-salient item: while the build machine uses the default > vt(4), I had switched the laptop to 'kern.vty=3D"sc"' via /boot/loader.= conf > no later than 23 August 2017 (mtime of the file) I broke syscons(4) yesterday and bde@ provided a patch which cem@ committed in r333683 [1]. It should work again for you now. Sorry for the breakage. [1] https://svnweb.freebsd.org/changeset/base/333683 --=20 Jean-S=E9bastien P=E9dron --hGrHDkSRWv5qzkcNdp3z8wXrvl5MOA1eP-- --2OK8DKkQXW7hvGFhGQnOii3bY2FD0v0wR Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEZwh/0a6uDhLbxqbwOemXYaX9lMwFAlr9MG8ACgkQOemXYaX9 lMxa6Q//WXzU8LMQiZ/5HLZjrej9lev8+ksewneC3IDMakPZTbHCoagm57EWRVNd re/0QB1ekgre331YwLm1vTUalAaIag18A/AicMSJwi9j+/XBCiht5u44S/QRrGPu 1oa37q1V5Lob0UmGbbC4EsLTmZRrOsXfWe69dL0DQvLOx3rd4sMdXcCZTezJCMxl WKH8jGPfK2EhzYuX5eaPIjzkMv4na2nyilEzBwbwrZqH4+n7AkPbRi1Gcg2a2R75 1HQ4/94L+Jj3/Rzhzg0KCMmGzhJTzubyBxKEF9Fu7+/UxJebIeTRBypf1Vx/7tLU MZNN6Zac5h5z3QcT992M0IHWtu0VsQp6kdxKGP3Eds0ft/RZCRxh/4JR4i3K4j9b lE/W2Lqp3UT/9OqZ1mgSjD87yJeDYFgt8MH9D0mdQf6OFJb2WyGMH7DiJQ/82/lV KeHt5S6WX0pF4iZj+edDFDgvZltj0oKGaX/KoK3wcbqL4zl08Y+ts56DcuFltpfs EjIMI+1AXnthPsxIxysHQa6ZFjDcDF1PweU/+1Qkh9k4q4tJPwSaWs0QDQioodZi 0cQuhcEU3d6/DnDbMabpaIQBdaWjZD3n4Bzw4CZH49z4bRzXQabfKzXzfmUAS/KJ DVRgxiRB7U9M3yDZ3oIDwevPLloJOulP9jAoftFMbE2a9/EXyho= =JgVH -----END PGP SIGNATURE----- --2OK8DKkQXW7hvGFhGQnOii3bY2FD0v0wR-- From owner-freebsd-current@freebsd.org Thu May 17 07:47:10 2018 Return-Path: Delivered-To: freebsd-current@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 0676AEDBAAD for ; Thu, 17 May 2018 07:47:10 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-wr0-x231.google.com (mail-wr0-x231.google.com [IPv6:2a00:1450:400c:c0c::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 26D50713F7; Thu, 17 May 2018 07:47:09 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-wr0-x231.google.com with SMTP id g21-v6so4566270wrb.8; Thu, 17 May 2018 00:47:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=y36kiCm2xKNZ9Ayc5DAe+bXFU4J/FP0n+h0+uLH5cRk=; b=nbU1mPUq1xa3MVK2Pi841QDkUkcEh2T2xXcsLenf5x30jt5KMEp1LIiTWjl7uQ3KFz 6AyylmE7iLI+urNeKpcaRdtu4uP6rjnYp6PwwYNs74W8XHxDNaURJqB4jyxnqOgwRoLi rwfPLpc8194Mo56LQ1Lg3b3UiW6UnnpBAa07fKbSOaaPvNW3gMrDBYsdgERNDFQlYsuw E4zk2E66CpfnYAzePJd57Q62qVPzT9QlpLCfu9Z/KotHnonl3v6/M9M1HOeg1bR0mgDt medV7Og0z1ZctYK4QesOPWwI+tHxdpujUaaoMnFwnM6QULp/bjzVXab+H6hDzFCC6bpL 3szg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=y36kiCm2xKNZ9Ayc5DAe+bXFU4J/FP0n+h0+uLH5cRk=; b=qhN2JRoqcpVG+bR0oXNK6FgDBRo8Qkk6LsfLjJaVy8YxKF3wFUqt9yKAtcUSNvbVxk T7QydZ1ZtT/O5oAwoaT+AbLyO8e0+3F9F+hswOrqFrlxBhWVDcubld3B5uxoAuiNuCSk 7aHCuqjar/iuCehhyF2fzZZk+ryn13gI0bwyypz4BiQsSJGJhBkqDUMMTvuRFYj5DCXT oLJuypLkWJyo1MhoWiZf/2RpmPSykMtWDiro693HJvaRJohX9a1O11epH4GM5g8UK5yJ ryPStJ0Jnk75gwKmlAiczuQDsVHhVIgekOVCikn7Nm3qka9l5ThLfP9hXuqAxwLmhMRi a9Sw== X-Gm-Message-State: ALKqPwdFUQywFtvvV5XE47WJAAZwYgsrJPQvyVPqvECR7EM9y/qi3Ivj 2jqq8gk9kyDTvQXnYqw7FfGn54pMzvRcs4JPfyNjzQ== X-Google-Smtp-Source: AB8JxZqlWr1cED7+Bow/0XMJ/KivHbc/0ZMLqa+fQ/smEPqPPRBrPCtrYkpxVD9USmMHIUnBxK0IeXIuKpi/NgFJKTE= X-Received: by 2002:adf:a70c:: with SMTP id c12-v6mr3076069wrd.140.1526543227591; Thu, 17 May 2018 00:47:07 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.146.194 with HTTP; Thu, 17 May 2018 00:46:27 -0700 (PDT) In-Reply-To: References: From: Johannes Lundberg Date: Thu, 17 May 2018 08:46:27 +0100 Message-ID: Subject: Re: Lag after resume culprit found To: Andriy Gapon Cc: freebsd-current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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 May 2018 07:47:10 -0000 On Thu, May 17, 2018 at 7:43 AM, Andriy Gapon wrote: > On 17/05/2018 02:07, Johannes Lundberg wrote: > > https://github.com/freebsd/freebsd/commit/66f063557f257baa9c8aeab9f93317 > 1eaa6e1cfa > > x86 cpususpend_handler: call wbinvd after setting suspend state bits > > That's very interesting and surprising. > That commit changes something that happens before suspend, it should not > have > any effect on the system state after resume. > > Does anyone have a theory of what could be wrong? > Nope but moving CPU_CLR_ATOMIC(cpu, &suspended_cpus); back to the end of that scope fixes it. > > > How to test (i915kms) > > > > Start X with glxgears > > Confirm running stable at 60 fps > > suspend/resume (S3) > > glxgears is now fluctuating between 10-40 fps. > > > > -- > Andriy Gapon > From owner-freebsd-current@freebsd.org Thu May 17 07:54:48 2018 Return-Path: Delivered-To: freebsd-current@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 7F7E7EDC28F; Thu, 17 May 2018 07:54:48 +0000 (UTC) (envelope-from agapon@gmail.com) Received: from mail-lf0-f50.google.com (mail-lf0-f50.google.com [209.85.215.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A8788718A6; Thu, 17 May 2018 07:54:47 +0000 (UTC) (envelope-from agapon@gmail.com) Received: by mail-lf0-f50.google.com with SMTP id r25-v6so7348681lfd.1; Thu, 17 May 2018 00:54:47 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:openpgp:autocrypt:message-id :date:user-agent:mime-version:content-language :content-transfer-encoding; bh=kPiGJk4V4oEhvP+TKNTJAyYpAR3uuMX5XlAvvHS16pk=; b=ef19HWaOsm6TdZZItAFRELFWE9a+bCwVVF2J2T8KwhZkmLrbTmyF1RShecdF1lcqSA ghSLPQNOqAeGHC41gbD+1Ok7DYY3k4oTvuGa2Ynumptn/gS0LXoJlg/ht5zM2tExB4i6 mIRiFpsOH8zXkYDlqs+QR/i3s0cTGkMvUKlsXQaXh2IjqJ8aq3Q3x28bNanwhtfVDAkf k0r0NyRP/xo3ku5EOXbfSRpNO4sdDkXbD0hvr/tO/2I+qWFmXyqv0FmHnJFXNuuOOrU2 GyORfQPbv5hpUCdlDkbSwHVMV/GDGUsBmYO19C2ANefwSvcHDjvNWqwPwz3cPbyc3MeW zC2g== X-Gm-Message-State: ALKqPwfQjGnNgLwWYEKRyMKDV7V/AXCBynfRNKbH/QmHqacSvlq99dnr E608O0AZ/4FaSzkE0NMvzpHYXYSi X-Google-Smtp-Source: AB8JxZrrqPt1Ob4wk5TlhoAGCHCDfXmqt/92fMrAyDr0ZZsddcZ0tpNgzuJ8EK10oQAzIkf2dVLFQQ== X-Received: by 2002:a19:ead6:: with SMTP id y83-v6mr16447218lfi.117.1526543679677; Thu, 17 May 2018 00:54:39 -0700 (PDT) Received: from [192.168.0.88] (east.meadow.volia.net. [93.72.151.96]) by smtp.googlemail.com with ESMTPSA id q18-v6sm1068333lfi.97.2018.05.17.00.54.38 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 17 May 2018 00:54:39 -0700 (PDT) To: freebsd-hackers , FreeBSD Current From: Andriy Gapon Subject: serial console vs suspend Openpgp: preference=signencrypt Autocrypt: addr=avg@FreeBSD.org; prefer-encrypt=mutual; keydata= xsFNBFm4LIgBEADNB/3lT7f15UKeQ52xCFQx/GqHkSxEdVyLFZTmY3KyNPQGBtyvVyBfprJ7 mAeXZWfhat6cKNRAGZcL5EmewdQuUfQfBdYmKjbw3a9GFDsDNuhDA2QwFt8BmkiVMRYyvI7l N0eVzszWCUgdc3qqM6qqcgBaqsVmJluwpvwp4ZBXmch5BgDDDb1MPO8AZ2QZfIQmplkj8Y6Z AiNMknkmgaekIINSJX8IzRzKD5WwMsin70psE8dpL/iBsA2cpJGzWMObVTtCxeDKlBCNqM1i gTXta1ukdUT7JgLEFZk9ceYQQMJJtUwzWu1UHfZn0Fs29HTqawfWPSZVbulbrnu5q55R4PlQ /xURkWQUTyDpqUvb4JK371zhepXiXDwrrpnyyZABm3SFLkk2bHlheeKU6Yql4pcmSVym1AS4 dV8y0oHAfdlSCF6tpOPf2+K9nW1CFA8b/tw4oJBTtfZ1kxXOMdyZU5fiG7xb1qDgpQKgHUX8 7Rd2T1UVLVeuhYlXNw2F+a2ucY+cMoqz3LtpksUiBppJhw099gEXehcN2JbUZ2TueJdt1FdS ztnZmsHUXLxrRBtGwqnFL7GSd6snpGIKuuL305iaOGODbb9c7ne1JqBbkw1wh8ci6vvwGlzx rexzimRaBzJxlkjNfMx8WpCvYebGMydNoeEtkWldtjTNVsUAtQARAQABzR5BbmRyaXkgR2Fw b24gPGF2Z0BGcmVlQlNELm9yZz7CwZQEEwEIAD4WIQS+LEO7ngQnXA4Bjr538m7TUc1yjwUC WbgsiAIbIwUJBaOagAULCQgHAgYVCAkKCwIEFgIDAQIeAQIXgAAKCRB38m7TUc1yj+JAEACV l9AK/nOWAt/9cufV2fRj0hdOqB1aCshtSrwHk/exXsDa4/FkmegxXQGY+3GWX3deIyesbVRL rYdtdK0dqJyT1SBqXK1h3/at9rxr9GQA6KWOxTjUFURsU7ok/6SIlm8uLRPNKO+yq0GDjgaO LzN+xykuBA0FlhQAXJnpZLcVfPJdWv7sSHGedL5ln8P8rxR+XnmsA5TUaaPcbhTB+mG+iKFj GghASDSfGqLWFPBlX/fpXikBDZ1gvOr8nyMY9nXhgfXpq3B6QCRYKPy58ChrZ5weeJZ29b7/ QdEO8NFNWHjSD9meiLdWQaqo9Y7uUxN3wySc/YUZxtS0bhAd8zJdNPsJYG8sXgKjeBQMVGuT eCAJFEYJqbwWvIXMfVWop4+O4xB+z2YE3jAbG/9tB/GSnQdVSj3G8MS80iLS58frnt+RSEw/ psahrfh0dh6SFHttE049xYiC+cM8J27Aaf0i9RflyITq57NuJm+AHJoU9SQUkIF0nc6lfA+o JRiyRlHZHKoRQkIg4aiKaZSWjQYRl5Txl0IZUP1dSWMX4s3XTMurC/pnja45dge/4ESOtJ9R 8XuIWg45Oq6MeIWdjKddGhRj3OohsltKgkEU3eLKYtB6qRTQypHHUawCXz88uYt5e3w4V16H lCpSTZV/EVHnNe45FVBlvK7k7HFfDDkryM7BTQRZuCyIARAAlq0slcsVboY/+IUJdcbEiJRW be9HKVz4SUchq0z9MZPX/0dcnvz/gkyYA+OuM78dNS7Mbby5dTvOqfpLJfCuhaNYOhlE0wY+ 1T6Tf1f4c/uA3U/YiadukQ3+6TJuYGAdRZD5EqYFIkreARTVWg87N9g0fT9BEqLw9lJtEGDY EWUE7L++B8o4uu3LQFEYxcrb4K/WKmgtmFcm77s0IKDrfcX4doV92QTIpLiRxcOmCC/OCYuO jB1oaaqXQzZrCutXRK0L5XN1Y1PYjIrEzHMIXmCDlLYnpFkK+itlXwlE2ZQxkfMruCWdQXye syl2fynAe8hvp7Mms9qU2r2K9EcJiR5N1t1C2/kTKNUhcRv7Yd/vwusK7BqJbhlng5ZgRx0m WxdntU/JLEntz3QBsBsWM9Y9wf2V4tLv6/DuDBta781RsCB/UrU2zNuOEkSixlUiHxw1dccI 6CVlaWkkJBxmHX22GdDFrcjvwMNIbbyfQLuBq6IOh8nvu9vuItup7qemDG3Ms6TVwA7BD3j+ 3fGprtyW8Fd/RR2bW2+LWkMrqHffAr6Y6V3h5kd2G9Q8ZWpEJk+LG6Mk3fhZhmCnHhDu6CwN MeUvxXDVO+fqc3JjFm5OxhmfVeJKrbCEUJyM8ESWLoNHLqjywdZga4Q7P12g8DUQ1mRxYg/L HgZY3zfKOqcAEQEAAcLBfAQYAQgAJhYhBL4sQ7ueBCdcDgGOvnfybtNRzXKPBQJZuCyIAhsM BQkFo5qAAAoJEHfybtNRzXKPBVwQAKfFy9P7N3OsLDMB56A4Kf+ZT+d5cIx0Yiaf4n6w7m3i ImHHHk9FIetI4Xe54a2IXh4Bq5UkAGY0667eIs+Z1Ea6I2i27Sdo7DxGwq09Qnm/Y65ADvXs 3aBvokCcm7FsM1wky395m8xUos1681oV5oxgqeRI8/76qy0hD9WR65UW+HQgZRIcIjSel9vR XDaD2HLGPTTGr7u4v00UeTMs6qvPsa2PJagogrKY8RXdFtXvweQFz78NbXhluwix2Tb9ETPk LIpDrtzV73CaE2aqBG/KrboXT2C67BgFtnk7T7Y7iKq4/XvEdDWscz2wws91BOXuMMd4c/c4 OmGW9m3RBLufFrOag1q5yUS9QbFfyqL6dftJP3Zq/xe+mr7sbWbhPVCQFrH3r26mpmy841ym dwQnNcsbIGiBASBSKksOvIDYKa2Wy8htPmWFTEOPRpFXdGQ27awcjjnB42nngyCK5ukZDHi6 w0qK5DNQQCkiweevCIC6wc3p67jl1EMFY5+z+zdTPb3h7LeVnGqW0qBQl99vVFgzLxchKcl0 R/paSFgwqXCZhAKMuUHncJuynDOP7z5LirUeFI8qsBAJi1rXpQoLJTVcW72swZ42IdPiboqx NbTMiNOiE36GqMcTPfKylCbF45JNX4nF9ElM0E+Y8gi4cizJYBRr2FBJgay0b9Cp Message-ID: <0e1d5601-f792-0708-3bcf-7153bea8f679@FreeBSD.org> Date: Thu, 17 May 2018 10:54:38 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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 May 2018 07:54:48 -0000 It seems that the serial console, or rather a UART used by it, may require re-initialization after waking up (from suspend to RAM). At least one of my systems fails to wake up properly if I configure the serial console. I've done some experimenting with cu (and without the console) and the UART seems to be in some weird state, it echoes back the input and does not send anything on the wire. I guess that trying to print to the serial console while the UART is in that state results in a hang. To test the theory I made this hack and it does help: Index: sys/dev/uart/uart_tty.c =================================================================== --- sys/dev/uart/uart_tty.c (revision 333667) +++ sys/dev/uart/uart_tty.c (working copy) @@ -114,6 +114,13 @@ uart_cninit(struct consdev *cp) uart_init(di); } +void uart_resume(void); +void +uart_resume(void) +{ + uart_init(&uart_console); +} + static void uart_cnterm(struct consdev *cp) { Index: sys/x86/acpica/acpi_wakeup.c =================================================================== --- sys/x86/acpica/acpi_wakeup.c (revision 333667) +++ sys/x86/acpica/acpi_wakeup.c (working copy) @@ -204,6 +205,8 @@ acpi_wakeup_cpus(struct acpi_softc *sc) } #endif +extern void uart_resume(void); + int acpi_sleep_machdep(struct acpi_softc *sc, int state) { @@ -300,6 +303,7 @@ acpi_sleep_machdep(struct acpi_softc *sc, int stat #else npxresume(susppcbs[0]->sp_fpususpend); #endif + uart_resume(); } return (1); /* wakeup successfully */ =================================================================== This is quick and dirty, of course. I think that this should go through the console layer. And, obviously, not all consoles actually need such a reinit. So, maybe: cnresume() { for each console { if cn->cn_ops->cn_resume != NULL cn->cn_ops->cn_resume(cn) } } uart_resume(struct consdev *cp) { uart_init(cp->cn_arg); } What do you think? Hmm, it looks like CONSOLE_DRIVER() does not allow to omit a console method. So, will I have to add a dummy resume to all console drivers? -- Andriy Gapon From owner-freebsd-current@freebsd.org Thu May 17 07:56:57 2018 Return-Path: Delivered-To: freebsd-current@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 44B4DEDC49C for ; Thu, 17 May 2018 07:56:57 +0000 (UTC) (envelope-from agapon@gmail.com) Received: from mail-lf0-f65.google.com (mail-lf0-f65.google.com [209.85.215.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9E7C7719C5 for ; Thu, 17 May 2018 07:56:56 +0000 (UTC) (envelope-from agapon@gmail.com) Received: by mail-lf0-f65.google.com with SMTP id h197-v6so7315359lfg.11 for ; Thu, 17 May 2018 00:56:56 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:openpgp:autocrypt :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=r1o9kxxesoFpLleFZLz4Wdl0wgx+PwuaJ5V7WOwwFKY=; b=RA6KLSDFegTqgwTyCXekpLAQss+kydiLL/f+nS0DORNF+651sZFiun7Om7xx73db8n 4H36/Wx3QvMbRd+cQ2SpLie95rMx4FyW758b5G3M/Nm2cjZLRKfWFIEK/HJmSoHR+KzC sTJnVUY+Otuht507XYo+dmjP+JIFqHkmlO2sOnEVowZd4uR1cCSdHwLr0l0r6lsOPdp+ JCQ5z0FxFHdZ59vXD71Tv6LG1QWs/EQR9jEbobF+IJH9sqpL0akO9P9KJ4TvE4HVnurM OZKJ38Q0AS8HAn3nP6o3lSn1KdXm4QddCeSVBG1rOnd2XWl+YOxPK5gahl9LA7IKIHkj OK6g== X-Gm-Message-State: ALKqPwfu2lTkfBjkxhctHLWtQnm6M6k8GeRxdgCwp4HoAXEvwXygBPq2 zUB8svCRChiPVkNhxCCYHcqQ7LkL X-Google-Smtp-Source: AB8JxZojqwUyncuN5MKrzFZCMtur8EyCM61OK5GO8rSCboBmvGzE6dtlSElcNFAnHjde4MrilVTTqw== X-Received: by 2002:a2e:8350:: with SMTP id l16-v6mr2393263ljh.28.1526543814831; Thu, 17 May 2018 00:56:54 -0700 (PDT) Received: from [192.168.0.88] (east.meadow.volia.net. [93.72.151.96]) by smtp.googlemail.com with ESMTPSA id d3-v6sm728097lja.38.2018.05.17.00.56.53 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 17 May 2018 00:56:54 -0700 (PDT) Subject: Re: Lag after resume culprit found To: Johannes Lundberg Cc: freebsd-current References: From: Andriy Gapon Openpgp: preference=signencrypt Autocrypt: addr=avg@FreeBSD.org; prefer-encrypt=mutual; keydata= xsFNBFm4LIgBEADNB/3lT7f15UKeQ52xCFQx/GqHkSxEdVyLFZTmY3KyNPQGBtyvVyBfprJ7 mAeXZWfhat6cKNRAGZcL5EmewdQuUfQfBdYmKjbw3a9GFDsDNuhDA2QwFt8BmkiVMRYyvI7l N0eVzszWCUgdc3qqM6qqcgBaqsVmJluwpvwp4ZBXmch5BgDDDb1MPO8AZ2QZfIQmplkj8Y6Z AiNMknkmgaekIINSJX8IzRzKD5WwMsin70psE8dpL/iBsA2cpJGzWMObVTtCxeDKlBCNqM1i gTXta1ukdUT7JgLEFZk9ceYQQMJJtUwzWu1UHfZn0Fs29HTqawfWPSZVbulbrnu5q55R4PlQ /xURkWQUTyDpqUvb4JK371zhepXiXDwrrpnyyZABm3SFLkk2bHlheeKU6Yql4pcmSVym1AS4 dV8y0oHAfdlSCF6tpOPf2+K9nW1CFA8b/tw4oJBTtfZ1kxXOMdyZU5fiG7xb1qDgpQKgHUX8 7Rd2T1UVLVeuhYlXNw2F+a2ucY+cMoqz3LtpksUiBppJhw099gEXehcN2JbUZ2TueJdt1FdS ztnZmsHUXLxrRBtGwqnFL7GSd6snpGIKuuL305iaOGODbb9c7ne1JqBbkw1wh8ci6vvwGlzx rexzimRaBzJxlkjNfMx8WpCvYebGMydNoeEtkWldtjTNVsUAtQARAQABzR5BbmRyaXkgR2Fw b24gPGF2Z0BGcmVlQlNELm9yZz7CwZQEEwEIAD4WIQS+LEO7ngQnXA4Bjr538m7TUc1yjwUC WbgsiAIbIwUJBaOagAULCQgHAgYVCAkKCwIEFgIDAQIeAQIXgAAKCRB38m7TUc1yj+JAEACV l9AK/nOWAt/9cufV2fRj0hdOqB1aCshtSrwHk/exXsDa4/FkmegxXQGY+3GWX3deIyesbVRL rYdtdK0dqJyT1SBqXK1h3/at9rxr9GQA6KWOxTjUFURsU7ok/6SIlm8uLRPNKO+yq0GDjgaO LzN+xykuBA0FlhQAXJnpZLcVfPJdWv7sSHGedL5ln8P8rxR+XnmsA5TUaaPcbhTB+mG+iKFj GghASDSfGqLWFPBlX/fpXikBDZ1gvOr8nyMY9nXhgfXpq3B6QCRYKPy58ChrZ5weeJZ29b7/ QdEO8NFNWHjSD9meiLdWQaqo9Y7uUxN3wySc/YUZxtS0bhAd8zJdNPsJYG8sXgKjeBQMVGuT eCAJFEYJqbwWvIXMfVWop4+O4xB+z2YE3jAbG/9tB/GSnQdVSj3G8MS80iLS58frnt+RSEw/ psahrfh0dh6SFHttE049xYiC+cM8J27Aaf0i9RflyITq57NuJm+AHJoU9SQUkIF0nc6lfA+o JRiyRlHZHKoRQkIg4aiKaZSWjQYRl5Txl0IZUP1dSWMX4s3XTMurC/pnja45dge/4ESOtJ9R 8XuIWg45Oq6MeIWdjKddGhRj3OohsltKgkEU3eLKYtB6qRTQypHHUawCXz88uYt5e3w4V16H lCpSTZV/EVHnNe45FVBlvK7k7HFfDDkryM7BTQRZuCyIARAAlq0slcsVboY/+IUJdcbEiJRW be9HKVz4SUchq0z9MZPX/0dcnvz/gkyYA+OuM78dNS7Mbby5dTvOqfpLJfCuhaNYOhlE0wY+ 1T6Tf1f4c/uA3U/YiadukQ3+6TJuYGAdRZD5EqYFIkreARTVWg87N9g0fT9BEqLw9lJtEGDY EWUE7L++B8o4uu3LQFEYxcrb4K/WKmgtmFcm77s0IKDrfcX4doV92QTIpLiRxcOmCC/OCYuO jB1oaaqXQzZrCutXRK0L5XN1Y1PYjIrEzHMIXmCDlLYnpFkK+itlXwlE2ZQxkfMruCWdQXye syl2fynAe8hvp7Mms9qU2r2K9EcJiR5N1t1C2/kTKNUhcRv7Yd/vwusK7BqJbhlng5ZgRx0m WxdntU/JLEntz3QBsBsWM9Y9wf2V4tLv6/DuDBta781RsCB/UrU2zNuOEkSixlUiHxw1dccI 6CVlaWkkJBxmHX22GdDFrcjvwMNIbbyfQLuBq6IOh8nvu9vuItup7qemDG3Ms6TVwA7BD3j+ 3fGprtyW8Fd/RR2bW2+LWkMrqHffAr6Y6V3h5kd2G9Q8ZWpEJk+LG6Mk3fhZhmCnHhDu6CwN MeUvxXDVO+fqc3JjFm5OxhmfVeJKrbCEUJyM8ESWLoNHLqjywdZga4Q7P12g8DUQ1mRxYg/L HgZY3zfKOqcAEQEAAcLBfAQYAQgAJhYhBL4sQ7ueBCdcDgGOvnfybtNRzXKPBQJZuCyIAhsM BQkFo5qAAAoJEHfybtNRzXKPBVwQAKfFy9P7N3OsLDMB56A4Kf+ZT+d5cIx0Yiaf4n6w7m3i ImHHHk9FIetI4Xe54a2IXh4Bq5UkAGY0667eIs+Z1Ea6I2i27Sdo7DxGwq09Qnm/Y65ADvXs 3aBvokCcm7FsM1wky395m8xUos1681oV5oxgqeRI8/76qy0hD9WR65UW+HQgZRIcIjSel9vR XDaD2HLGPTTGr7u4v00UeTMs6qvPsa2PJagogrKY8RXdFtXvweQFz78NbXhluwix2Tb9ETPk LIpDrtzV73CaE2aqBG/KrboXT2C67BgFtnk7T7Y7iKq4/XvEdDWscz2wws91BOXuMMd4c/c4 OmGW9m3RBLufFrOag1q5yUS9QbFfyqL6dftJP3Zq/xe+mr7sbWbhPVCQFrH3r26mpmy841ym dwQnNcsbIGiBASBSKksOvIDYKa2Wy8htPmWFTEOPRpFXdGQ27awcjjnB42nngyCK5ukZDHi6 w0qK5DNQQCkiweevCIC6wc3p67jl1EMFY5+z+zdTPb3h7LeVnGqW0qBQl99vVFgzLxchKcl0 R/paSFgwqXCZhAKMuUHncJuynDOP7z5LirUeFI8qsBAJi1rXpQoLJTVcW72swZ42IdPiboqx NbTMiNOiE36GqMcTPfKylCbF45JNX4nF9ElM0E+Y8gi4cizJYBRr2FBJgay0b9Cp Message-ID: <1cc60c25-c316-cd22-63d5-fc61d66c930a@FreeBSD.org> Date: Thu, 17 May 2018 10:56:53 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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 May 2018 07:56:57 -0000 On 17/05/2018 10:46, Johannes Lundberg wrote: > On Thu, May 17, 2018 at 7:43 AM, Andriy Gapon > wrote: > > On 17/05/2018 02:07, Johannes Lundberg wrote: > > https://github.com/freebsd/freebsd/commit/66f063557f257baa9c8aeab9f933171eaa6e1cfa > > > x86 cpususpend_handler: call wbinvd after setting suspend state bits > > That's very interesting and surprising. > That commit changes something that happens before suspend, it should not have > any effect on the system state after resume. > > Does anyone have a theory of what could be wrong? > > Nope but moving >         CPU_CLR_ATOMIC(cpu, &suspended_cpus); > back to the end of that scope fixes it. That's interesting. Thank you for testing it! And let me think about it. > > How to test (i915kms) > > > > Start X with glxgears > > Confirm running stable at 60 fps > > suspend/resume (S3) > > glxgears is now fluctuating between 10-40 fps. -- Andriy Gapon From owner-freebsd-current@freebsd.org Thu May 17 07:57:42 2018 Return-Path: Delivered-To: freebsd-current@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 DFE0FEDC522 for ; Thu, 17 May 2018 07:57:41 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-wm0-x236.google.com (mail-wm0-x236.google.com [IPv6:2a00:1450:400c:c09::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5954A719EF; Thu, 17 May 2018 07:57:41 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-wm0-x236.google.com with SMTP id l1-v6so7217645wmb.2; Thu, 17 May 2018 00:57:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=qGXVJvloNb4RWIRd//LxQrUr+v3SkKDFYUM+O4gA+ds=; b=XNAGdoX2+pxCPddIT5y0u/oIgpx0t5X8Z3/+2H7mxypTl7SAnOFe/PBkRIxRSRrlNC V1tldSwMDejCujgkXMW0a5gnT2fgDHvF5uHTCoZ9V8jI/i1MTatiHB4EYTxkTqpqI2Rs NF/iLJ2zdj6kocu0YlVP2+vKLrNpgjwHdcrnCeC/GQ8trX/HAdgV57/ErByPhKIcT8A3 0b0hdhaKJjeyqD2DctpYuzQbV3atnSUzr01juobiLk353AcxnI2889/JUqYppkM9fKuj JRKaV3v1P7O1BvGEzrldH/f9H423ZrJhPPgVYfMdJJbPTJPN8PWO+mPlOU03TpT57Kk1 ox6w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=qGXVJvloNb4RWIRd//LxQrUr+v3SkKDFYUM+O4gA+ds=; b=LJyb/5OBq5RyrO258xMK/1YG9GYYz/5ryZBmEUaTgCVEZVe5BWPlpxBjv4v1YlZPfZ CGHlJTx56l/Cuz0BP5wuJtZW7sSwEUWFXNG9X6z9evk5N5CMi5cw/BaDnhAoQOsY7MOi yClq398j7n7KJP27/bP/V8Eb82ty4z2F7gW9TveejB00i5QwDt0h1bhmkzm4WXx3sYoT g6JxCpFWy/cYzebj8cTXhvKiIsgIA35DaiBiZTqmvQ96QT2Zu+YHr0Y+bLsilS+FSsEi rQaPt9DOwlSzfhEtmWjSD0U9b0YRX/dNKqkm1NqBey++Xa5EHNLPn9k8QUl/Xq1uWS4K OZ8Q== X-Gm-Message-State: ALKqPwc70Jy4h+Q6jomZflAhDa0rbRVfHPmBs8pnOnkrLadGYCuB4GFJ NsyRdgphIBp1JeXhEwxa5dKuKmKhNB0z3TX2q0zyeA== X-Google-Smtp-Source: AB8JxZrOy5vdyxNHq4aKxuc9345wIzNSQ61TIItMdk0FwudEXvwep+ps56GAKOvXHEzeZLOcVjxebk42TNWIqRdgT00= X-Received: by 2002:a1c:f714:: with SMTP id v20-v6mr1022407wmh.73.1526543860265; Thu, 17 May 2018 00:57:40 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.146.194 with HTTP; Thu, 17 May 2018 00:56:59 -0700 (PDT) In-Reply-To: References: From: Johannes Lundberg Date: Thu, 17 May 2018 08:56:59 +0100 Message-ID: Subject: Re: Lag after resume culprit found To: Andriy Gapon Cc: freebsd-current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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 May 2018 07:57:42 -0000 On Thu, May 17, 2018 at 8:46 AM, Johannes Lundberg wrote: > > > On Thu, May 17, 2018 at 7:43 AM, Andriy Gapon wrote: > >> On 17/05/2018 02:07, Johannes Lundberg wrote: >> > https://github.com/freebsd/freebsd/commit/66f063557f257baa9c >> 8aeab9f933171eaa6e1cfa >> > x86 cpususpend_handler: call wbinvd after setting suspend state bits >> >> That's very interesting and surprising. >> That commit changes something that happens before suspend, it should not >> have >> any effect on the system state after resume. >> >> Does anyone have a theory of what could be wrong? >> > > Nope but moving > CPU_CLR_ATOMIC(cpu, &suspended_cpus); > back to the end of that scope fixes it. > > I did some further testing. Calling CPU_CLR_ATOMIC(cpu, &suspended_cpus); before pmap_init_pat(); is what "breaks" resume. Is this Intel only or this it happen on AMD as well (which this patch was intended for)? >> > How to test (i915kms) >> > >> > Start X with glxgears >> > Confirm running stable at 60 fps >> > suspend/resume (S3) >> > glxgears is now fluctuating between 10-40 fps. >> >> >> >> -- >> Andriy Gapon >> > > From owner-freebsd-current@freebsd.org Thu May 17 07:59:52 2018 Return-Path: Delivered-To: freebsd-current@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 0148DEDC82F for ; Thu, 17 May 2018 07:59:52 +0000 (UTC) (envelope-from agapon@gmail.com) Received: from mail-lf0-f66.google.com (mail-lf0-f66.google.com [209.85.215.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5A10371B9C for ; Thu, 17 May 2018 07:59:51 +0000 (UTC) (envelope-from agapon@gmail.com) Received: by mail-lf0-f66.google.com with SMTP id w202-v6so7303182lff.12 for ; Thu, 17 May 2018 00:59:51 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:from:to:cc:references:openpgp:autocrypt :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=finuqU8HWfLXw5tjHZisQLFy8yEUw208G5z76i8FRwQ=; b=UMNUQNxnD3UKyXWbcV3zkxOH8HM9Of12EOclQNFvblqHI00R9sKMxPVujAp+Ke07D9 451WkoSZe1YJS42mkLqoh0N+D9BuFJvglwv4X4lxy4vu1IsBxNzoEH0kqhh9vL0LdoWP wFAKttPA7mnZUXhut3BlgHXeV57el2/QTaKY2mevB21uc/5eMle84gsFsXmDM6Fix1kp y+PDEpChOow71/s2k5pxkbCVfdPYmfRVjRs+EwxM/qSdikKtyihd5wzChElfFON23lKh 8H8Riy1fPk9NRhcS1RdxWgPO0Yj3KUJTVS8K/6wnkjJlIrtTCi5th25+e68uA0xDVpfw 3mvw== X-Gm-Message-State: ALKqPwcS2EssIfDfksksMKyzlSg/1HLDvXLN1zHg5V7m/FtA2du1OTtl bpVpwgb2NgqWUdlTfT5J7cv9rFXr X-Google-Smtp-Source: AB8JxZrFikLt0S2T9OuDjbpts4VAuckGYu4QrrCmmcDWO6CJOPFHvDKMfRBsFdJDjHePh6RVvU8AAQ== X-Received: by 2002:a19:8ec2:: with SMTP id a63-v6mr16592015lfl.122.1526543984014; Thu, 17 May 2018 00:59:44 -0700 (PDT) Received: from [192.168.0.88] (east.meadow.volia.net. [93.72.151.96]) by smtp.googlemail.com with ESMTPSA id r11-v6sm740186ljg.37.2018.05.17.00.59.43 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 17 May 2018 00:59:43 -0700 (PDT) Subject: Re: Lag after resume culprit found From: Andriy Gapon To: Johannes Lundberg Cc: freebsd-current References: <1cc60c25-c316-cd22-63d5-fc61d66c930a@FreeBSD.org> Openpgp: preference=signencrypt Autocrypt: addr=avg@FreeBSD.org; prefer-encrypt=mutual; keydata= xsFNBFm4LIgBEADNB/3lT7f15UKeQ52xCFQx/GqHkSxEdVyLFZTmY3KyNPQGBtyvVyBfprJ7 mAeXZWfhat6cKNRAGZcL5EmewdQuUfQfBdYmKjbw3a9GFDsDNuhDA2QwFt8BmkiVMRYyvI7l N0eVzszWCUgdc3qqM6qqcgBaqsVmJluwpvwp4ZBXmch5BgDDDb1MPO8AZ2QZfIQmplkj8Y6Z AiNMknkmgaekIINSJX8IzRzKD5WwMsin70psE8dpL/iBsA2cpJGzWMObVTtCxeDKlBCNqM1i gTXta1ukdUT7JgLEFZk9ceYQQMJJtUwzWu1UHfZn0Fs29HTqawfWPSZVbulbrnu5q55R4PlQ /xURkWQUTyDpqUvb4JK371zhepXiXDwrrpnyyZABm3SFLkk2bHlheeKU6Yql4pcmSVym1AS4 dV8y0oHAfdlSCF6tpOPf2+K9nW1CFA8b/tw4oJBTtfZ1kxXOMdyZU5fiG7xb1qDgpQKgHUX8 7Rd2T1UVLVeuhYlXNw2F+a2ucY+cMoqz3LtpksUiBppJhw099gEXehcN2JbUZ2TueJdt1FdS ztnZmsHUXLxrRBtGwqnFL7GSd6snpGIKuuL305iaOGODbb9c7ne1JqBbkw1wh8ci6vvwGlzx rexzimRaBzJxlkjNfMx8WpCvYebGMydNoeEtkWldtjTNVsUAtQARAQABzR5BbmRyaXkgR2Fw b24gPGF2Z0BGcmVlQlNELm9yZz7CwZQEEwEIAD4WIQS+LEO7ngQnXA4Bjr538m7TUc1yjwUC WbgsiAIbIwUJBaOagAULCQgHAgYVCAkKCwIEFgIDAQIeAQIXgAAKCRB38m7TUc1yj+JAEACV l9AK/nOWAt/9cufV2fRj0hdOqB1aCshtSrwHk/exXsDa4/FkmegxXQGY+3GWX3deIyesbVRL rYdtdK0dqJyT1SBqXK1h3/at9rxr9GQA6KWOxTjUFURsU7ok/6SIlm8uLRPNKO+yq0GDjgaO LzN+xykuBA0FlhQAXJnpZLcVfPJdWv7sSHGedL5ln8P8rxR+XnmsA5TUaaPcbhTB+mG+iKFj GghASDSfGqLWFPBlX/fpXikBDZ1gvOr8nyMY9nXhgfXpq3B6QCRYKPy58ChrZ5weeJZ29b7/ QdEO8NFNWHjSD9meiLdWQaqo9Y7uUxN3wySc/YUZxtS0bhAd8zJdNPsJYG8sXgKjeBQMVGuT eCAJFEYJqbwWvIXMfVWop4+O4xB+z2YE3jAbG/9tB/GSnQdVSj3G8MS80iLS58frnt+RSEw/ psahrfh0dh6SFHttE049xYiC+cM8J27Aaf0i9RflyITq57NuJm+AHJoU9SQUkIF0nc6lfA+o JRiyRlHZHKoRQkIg4aiKaZSWjQYRl5Txl0IZUP1dSWMX4s3XTMurC/pnja45dge/4ESOtJ9R 8XuIWg45Oq6MeIWdjKddGhRj3OohsltKgkEU3eLKYtB6qRTQypHHUawCXz88uYt5e3w4V16H lCpSTZV/EVHnNe45FVBlvK7k7HFfDDkryM7BTQRZuCyIARAAlq0slcsVboY/+IUJdcbEiJRW be9HKVz4SUchq0z9MZPX/0dcnvz/gkyYA+OuM78dNS7Mbby5dTvOqfpLJfCuhaNYOhlE0wY+ 1T6Tf1f4c/uA3U/YiadukQ3+6TJuYGAdRZD5EqYFIkreARTVWg87N9g0fT9BEqLw9lJtEGDY EWUE7L++B8o4uu3LQFEYxcrb4K/WKmgtmFcm77s0IKDrfcX4doV92QTIpLiRxcOmCC/OCYuO jB1oaaqXQzZrCutXRK0L5XN1Y1PYjIrEzHMIXmCDlLYnpFkK+itlXwlE2ZQxkfMruCWdQXye syl2fynAe8hvp7Mms9qU2r2K9EcJiR5N1t1C2/kTKNUhcRv7Yd/vwusK7BqJbhlng5ZgRx0m WxdntU/JLEntz3QBsBsWM9Y9wf2V4tLv6/DuDBta781RsCB/UrU2zNuOEkSixlUiHxw1dccI 6CVlaWkkJBxmHX22GdDFrcjvwMNIbbyfQLuBq6IOh8nvu9vuItup7qemDG3Ms6TVwA7BD3j+ 3fGprtyW8Fd/RR2bW2+LWkMrqHffAr6Y6V3h5kd2G9Q8ZWpEJk+LG6Mk3fhZhmCnHhDu6CwN MeUvxXDVO+fqc3JjFm5OxhmfVeJKrbCEUJyM8ESWLoNHLqjywdZga4Q7P12g8DUQ1mRxYg/L HgZY3zfKOqcAEQEAAcLBfAQYAQgAJhYhBL4sQ7ueBCdcDgGOvnfybtNRzXKPBQJZuCyIAhsM BQkFo5qAAAoJEHfybtNRzXKPBVwQAKfFy9P7N3OsLDMB56A4Kf+ZT+d5cIx0Yiaf4n6w7m3i ImHHHk9FIetI4Xe54a2IXh4Bq5UkAGY0667eIs+Z1Ea6I2i27Sdo7DxGwq09Qnm/Y65ADvXs 3aBvokCcm7FsM1wky395m8xUos1681oV5oxgqeRI8/76qy0hD9WR65UW+HQgZRIcIjSel9vR XDaD2HLGPTTGr7u4v00UeTMs6qvPsa2PJagogrKY8RXdFtXvweQFz78NbXhluwix2Tb9ETPk LIpDrtzV73CaE2aqBG/KrboXT2C67BgFtnk7T7Y7iKq4/XvEdDWscz2wws91BOXuMMd4c/c4 OmGW9m3RBLufFrOag1q5yUS9QbFfyqL6dftJP3Zq/xe+mr7sbWbhPVCQFrH3r26mpmy841ym dwQnNcsbIGiBASBSKksOvIDYKa2Wy8htPmWFTEOPRpFXdGQ27awcjjnB42nngyCK5ukZDHi6 w0qK5DNQQCkiweevCIC6wc3p67jl1EMFY5+z+zdTPb3h7LeVnGqW0qBQl99vVFgzLxchKcl0 R/paSFgwqXCZhAKMuUHncJuynDOP7z5LirUeFI8qsBAJi1rXpQoLJTVcW72swZ42IdPiboqx NbTMiNOiE36GqMcTPfKylCbF45JNX4nF9ElM0E+Y8gi4cizJYBRr2FBJgay0b9Cp Message-ID: <6c53b46c-a0b3-069d-5478-f8480f2177b3@FreeBSD.org> Date: Thu, 17 May 2018 10:59:42 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <1cc60c25-c316-cd22-63d5-fc61d66c930a@FreeBSD.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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 May 2018 07:59:52 -0000 On 17/05/2018 10:56, Andriy Gapon wrote: > On 17/05/2018 10:46, Johannes Lundberg wrote: >> On Thu, May 17, 2018 at 7:43 AM, Andriy Gapon > > wrote: >> >> On 17/05/2018 02:07, Johannes Lundberg wrote: >> > https://github.com/freebsd/freebsd/commit/66f063557f257baa9c8aeab9f933171eaa6e1cfa >> >> > x86 cpususpend_handler: call wbinvd after setting suspend state bits >> >> That's very interesting and surprising. >> That commit changes something that happens before suspend, it should not have >> any effect on the system state after resume. >> >> Does anyone have a theory of what could be wrong? >> >> Nope but moving >>         CPU_CLR_ATOMIC(cpu, &suspended_cpus); >> back to the end of that scope fixes it. > > That's interesting. > Thank you for testing it! > And let me think about it. Oh, I am stupid. I intended that operation to be right after the CPU is done with restoring its saved context. Which means that it has to be after fpuresume/npxresume block. Could you please re-test with CPU_CLR_ATOMIC(cpu, &suspended_cpus) at that position? And my apologies. >> > How to test (i915kms) >> > >> > Start X with glxgears >> > Confirm running stable at 60 fps >> > suspend/resume (S3) >> > glxgears is now fluctuating between 10-40 fps. > -- Andriy Gapon From owner-freebsd-current@freebsd.org Thu May 17 08:06:53 2018 Return-Path: Delivered-To: freebsd-current@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 09569EDD4F4 for ; Thu, 17 May 2018 08:06:53 +0000 (UTC) (envelope-from agapon@gmail.com) Received: from mail-lf0-f67.google.com (mail-lf0-f67.google.com [209.85.215.67]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 56E36722B5 for ; Thu, 17 May 2018 08:06:52 +0000 (UTC) (envelope-from agapon@gmail.com) Received: by mail-lf0-f67.google.com with SMTP id 16-v6so7340700lfs.13 for ; Thu, 17 May 2018 01:06:52 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:openpgp:autocrypt :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=hqSyCm2jt/MHy4XkHG4UL9qgBUKSlBJrfcGt7Y2bXxo=; b=An3T9Dcb9cXCxas7/Lzn0dIzYcF4U+G5C9Ku2+WaIEEVIAmtu5xY/pRLOZiwIYQtZj ex41FWPScY6W7yjfGUQGRyZlen9jhQkTBJqLwxeLI3RWxM9cbWVrYM/Jesq6Fq1aC9F4 m1a9qiLAIP3zWeXcLP0EjxTY9UP31B6Et84vz08mhd8CZR8YAYzV0eXJOThDNo9EC9o8 sYIk2bdGNjw7jV1kf+RwUtLb/RzRFtRVECFyyleTmkLGpLyrRuo5cG3OvPNRxOf41G3E x9Baa06fdGfE/NGB7A9YPs9RKUj/9ZaZw83OFreWF7Bv6yvNmmw1Baoej2KPVoQu9B1m rCtg== X-Gm-Message-State: ALKqPwen8J5OCJisiWTjQ5oYG04UotKYUKpPxf+d/Cu1xF2G35gMuHV2 QudZb2O4D3JZ5YCkLgPbVw8MqHgH X-Google-Smtp-Source: AB8JxZq968AfUEn1gvJpX0ZZnUGPKDRl8YYN4nCmysTcPylX7/9B5B3iEnBrK//sFZNVAIZJorHh6Q== X-Received: by 2002:a2e:3112:: with SMTP id x18-v6mr2341907ljx.107.1526544404948; Thu, 17 May 2018 01:06:44 -0700 (PDT) Received: from [192.168.0.88] (east.meadow.volia.net. [93.72.151.96]) by smtp.googlemail.com with ESMTPSA id z11-v6sm237441lff.43.2018.05.17.01.06.43 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 17 May 2018 01:06:43 -0700 (PDT) Subject: Re: Lag after resume culprit found To: Johannes Lundberg Cc: freebsd-current References: From: Andriy Gapon Openpgp: preference=signencrypt Autocrypt: addr=avg@FreeBSD.org; prefer-encrypt=mutual; keydata= xsFNBFm4LIgBEADNB/3lT7f15UKeQ52xCFQx/GqHkSxEdVyLFZTmY3KyNPQGBtyvVyBfprJ7 mAeXZWfhat6cKNRAGZcL5EmewdQuUfQfBdYmKjbw3a9GFDsDNuhDA2QwFt8BmkiVMRYyvI7l N0eVzszWCUgdc3qqM6qqcgBaqsVmJluwpvwp4ZBXmch5BgDDDb1MPO8AZ2QZfIQmplkj8Y6Z AiNMknkmgaekIINSJX8IzRzKD5WwMsin70psE8dpL/iBsA2cpJGzWMObVTtCxeDKlBCNqM1i gTXta1ukdUT7JgLEFZk9ceYQQMJJtUwzWu1UHfZn0Fs29HTqawfWPSZVbulbrnu5q55R4PlQ /xURkWQUTyDpqUvb4JK371zhepXiXDwrrpnyyZABm3SFLkk2bHlheeKU6Yql4pcmSVym1AS4 dV8y0oHAfdlSCF6tpOPf2+K9nW1CFA8b/tw4oJBTtfZ1kxXOMdyZU5fiG7xb1qDgpQKgHUX8 7Rd2T1UVLVeuhYlXNw2F+a2ucY+cMoqz3LtpksUiBppJhw099gEXehcN2JbUZ2TueJdt1FdS ztnZmsHUXLxrRBtGwqnFL7GSd6snpGIKuuL305iaOGODbb9c7ne1JqBbkw1wh8ci6vvwGlzx rexzimRaBzJxlkjNfMx8WpCvYebGMydNoeEtkWldtjTNVsUAtQARAQABzR5BbmRyaXkgR2Fw b24gPGF2Z0BGcmVlQlNELm9yZz7CwZQEEwEIAD4WIQS+LEO7ngQnXA4Bjr538m7TUc1yjwUC WbgsiAIbIwUJBaOagAULCQgHAgYVCAkKCwIEFgIDAQIeAQIXgAAKCRB38m7TUc1yj+JAEACV l9AK/nOWAt/9cufV2fRj0hdOqB1aCshtSrwHk/exXsDa4/FkmegxXQGY+3GWX3deIyesbVRL rYdtdK0dqJyT1SBqXK1h3/at9rxr9GQA6KWOxTjUFURsU7ok/6SIlm8uLRPNKO+yq0GDjgaO LzN+xykuBA0FlhQAXJnpZLcVfPJdWv7sSHGedL5ln8P8rxR+XnmsA5TUaaPcbhTB+mG+iKFj GghASDSfGqLWFPBlX/fpXikBDZ1gvOr8nyMY9nXhgfXpq3B6QCRYKPy58ChrZ5weeJZ29b7/ QdEO8NFNWHjSD9meiLdWQaqo9Y7uUxN3wySc/YUZxtS0bhAd8zJdNPsJYG8sXgKjeBQMVGuT eCAJFEYJqbwWvIXMfVWop4+O4xB+z2YE3jAbG/9tB/GSnQdVSj3G8MS80iLS58frnt+RSEw/ psahrfh0dh6SFHttE049xYiC+cM8J27Aaf0i9RflyITq57NuJm+AHJoU9SQUkIF0nc6lfA+o JRiyRlHZHKoRQkIg4aiKaZSWjQYRl5Txl0IZUP1dSWMX4s3XTMurC/pnja45dge/4ESOtJ9R 8XuIWg45Oq6MeIWdjKddGhRj3OohsltKgkEU3eLKYtB6qRTQypHHUawCXz88uYt5e3w4V16H lCpSTZV/EVHnNe45FVBlvK7k7HFfDDkryM7BTQRZuCyIARAAlq0slcsVboY/+IUJdcbEiJRW be9HKVz4SUchq0z9MZPX/0dcnvz/gkyYA+OuM78dNS7Mbby5dTvOqfpLJfCuhaNYOhlE0wY+ 1T6Tf1f4c/uA3U/YiadukQ3+6TJuYGAdRZD5EqYFIkreARTVWg87N9g0fT9BEqLw9lJtEGDY EWUE7L++B8o4uu3LQFEYxcrb4K/WKmgtmFcm77s0IKDrfcX4doV92QTIpLiRxcOmCC/OCYuO jB1oaaqXQzZrCutXRK0L5XN1Y1PYjIrEzHMIXmCDlLYnpFkK+itlXwlE2ZQxkfMruCWdQXye syl2fynAe8hvp7Mms9qU2r2K9EcJiR5N1t1C2/kTKNUhcRv7Yd/vwusK7BqJbhlng5ZgRx0m WxdntU/JLEntz3QBsBsWM9Y9wf2V4tLv6/DuDBta781RsCB/UrU2zNuOEkSixlUiHxw1dccI 6CVlaWkkJBxmHX22GdDFrcjvwMNIbbyfQLuBq6IOh8nvu9vuItup7qemDG3Ms6TVwA7BD3j+ 3fGprtyW8Fd/RR2bW2+LWkMrqHffAr6Y6V3h5kd2G9Q8ZWpEJk+LG6Mk3fhZhmCnHhDu6CwN MeUvxXDVO+fqc3JjFm5OxhmfVeJKrbCEUJyM8ESWLoNHLqjywdZga4Q7P12g8DUQ1mRxYg/L HgZY3zfKOqcAEQEAAcLBfAQYAQgAJhYhBL4sQ7ueBCdcDgGOvnfybtNRzXKPBQJZuCyIAhsM BQkFo5qAAAoJEHfybtNRzXKPBVwQAKfFy9P7N3OsLDMB56A4Kf+ZT+d5cIx0Yiaf4n6w7m3i ImHHHk9FIetI4Xe54a2IXh4Bq5UkAGY0667eIs+Z1Ea6I2i27Sdo7DxGwq09Qnm/Y65ADvXs 3aBvokCcm7FsM1wky395m8xUos1681oV5oxgqeRI8/76qy0hD9WR65UW+HQgZRIcIjSel9vR XDaD2HLGPTTGr7u4v00UeTMs6qvPsa2PJagogrKY8RXdFtXvweQFz78NbXhluwix2Tb9ETPk LIpDrtzV73CaE2aqBG/KrboXT2C67BgFtnk7T7Y7iKq4/XvEdDWscz2wws91BOXuMMd4c/c4 OmGW9m3RBLufFrOag1q5yUS9QbFfyqL6dftJP3Zq/xe+mr7sbWbhPVCQFrH3r26mpmy841ym dwQnNcsbIGiBASBSKksOvIDYKa2Wy8htPmWFTEOPRpFXdGQ27awcjjnB42nngyCK5ukZDHi6 w0qK5DNQQCkiweevCIC6wc3p67jl1EMFY5+z+zdTPb3h7LeVnGqW0qBQl99vVFgzLxchKcl0 R/paSFgwqXCZhAKMuUHncJuynDOP7z5LirUeFI8qsBAJi1rXpQoLJTVcW72swZ42IdPiboqx NbTMiNOiE36GqMcTPfKylCbF45JNX4nF9ElM0E+Y8gi4cizJYBRr2FBJgay0b9Cp Message-ID: <4d69b9f6-9406-74ba-1780-ac783adcf107@FreeBSD.org> Date: Thu, 17 May 2018 11:06:42 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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 May 2018 08:06:53 -0000 On 17/05/2018 10:56, Johannes Lundberg wrote: > > > On Thu, May 17, 2018 at 8:46 AM, Johannes Lundberg > wrote: > > > > On Thu, May 17, 2018 at 7:43 AM, Andriy Gapon > wrote: > > On 17/05/2018 02:07, Johannes Lundberg wrote: > > https://github.com/freebsd/freebsd/commit/66f063557f257baa9c8aeab9f933171eaa6e1cfa > > > x86 cpususpend_handler: call wbinvd after setting suspend state bits > > That's very interesting and surprising. > That commit changes something that happens before suspend, it should not > have > any effect on the system state after resume. > > Does anyone have a theory of what could be wrong? > > > Nope but moving >         CPU_CLR_ATOMIC(cpu, &suspended_cpus); > back to the end of that scope fixes it. >   > > > I did some further testing. > Calling > CPU_CLR_ATOMIC(cpu, &suspended_cpus); > before > pmap_init_pat(); >  is what "breaks" resume. > > Is this Intel only or this it happen on AMD as well (which this patch was > intended for)? Not sure about the PAT part, but fpuresume/npxresume would affect all platforms. It's a bit puzzling that doing PAT manipulations on one AP while another AP is being brought up is problematic. Probably there is something that I am missing. Thank you very much again for zeroing in on it. > > How to test (i915kms) > > > > Start X with glxgears > > Confirm running stable at 60 fps > > suspend/resume (S3) > > glxgears is now fluctuating between 10-40 fps. -- Andriy Gapon From owner-freebsd-current@freebsd.org Thu May 17 09:20:09 2018 Return-Path: Delivered-To: freebsd-current@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 A0EE3EE2769 for ; Thu, 17 May 2018 09:20:09 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (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 3DC1875718; Thu, 17 May 2018 09:20:09 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id w4H9JvXR016269 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 17 May 2018 12:20:01 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua w4H9JvXR016269 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id w4H9JvRh016268; Thu, 17 May 2018 12:19:57 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Thu, 17 May 2018 12:19:57 +0300 From: Konstantin Belousov To: Andriy Gapon Cc: Johannes Lundberg , freebsd-current Subject: Re: Lag after resume culprit found Message-ID: <20180517091957.GF6887@kib.kiev.ua> References: <4d69b9f6-9406-74ba-1780-ac783adcf107@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <4d69b9f6-9406-74ba-1780-ac783adcf107@FreeBSD.org> User-Agent: Mutt/1.9.5 (2018-04-13) X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,FREEMAIL_REPLY,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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 May 2018 09:20:09 -0000 On Thu, May 17, 2018 at 11:06:42AM +0300, Andriy Gapon wrote: > On 17/05/2018 10:56, Johannes Lundberg wrote: > > > > > > On Thu, May 17, 2018 at 8:46 AM, Johannes Lundberg > > wrote: > > > > > > > > On Thu, May 17, 2018 at 7:43 AM, Andriy Gapon > > wrote: > > > > On 17/05/2018 02:07, Johannes Lundberg wrote: > > > https://github.com/freebsd/freebsd/commit/66f063557f257baa9c8aeab9f933171eaa6e1cfa > > > > > x86 cpususpend_handler: call wbinvd after setting suspend state bits > > > > That's very interesting and surprising. > > That commit changes something that happens before suspend, it should not > > have > > any effect on the system state after resume. > > > > Does anyone have a theory of what could be wrong? > > > > > > Nope but moving > > ššš ššš CPU_CLR_ATOMIC(cpu, &suspended_cpus); > > back to the end of that scope fixes it. > > š > > > > > > I did some further testing. > > Calling > > CPU_CLR_ATOMIC(cpu, &suspended_cpus); > > before > > pmap_init_pat(); > > šis what "breaks" resume. > > > > Is this Intel only or this it happen on AMD as well (which this patch was > > intended for)? > > Not sure about the PAT part, but fpuresume/npxresume would affect all platforms. > It's a bit puzzling that doing PAT manipulations on one AP while another AP is > being brought up is problematic. Probably there is something that I am missing. Manipulating PAT might affect the cache consistency, since contradicting caching attributes are applied to the line of the suspended_cpus variable which is already cached. It might be not the variable itself that causes the final mis-operation, but some other data sharing the line. From owner-freebsd-current@freebsd.org Thu May 17 10:02:13 2018 Return-Path: Delivered-To: freebsd-current@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 4DD46EE543E for ; Thu, 17 May 2018 10:02:13 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c:c09::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BEC927744E for ; Thu, 17 May 2018 10:02:12 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-wm0-x233.google.com with SMTP id n10-v6so7900728wmc.1 for ; Thu, 17 May 2018 03:02:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=tVv+Vfnnebucit7zfNA85xqx518DbqL2h1RJH2umzPI=; b=fiOdFv7XtmjqUV1W6w0RjJPj37vL9Ryu3+xei8lsAJtN+Xm1g+YfU7Te/9M6W7sHVb NGN4v7GvTOzVJXCzNQD14a4I06VxC8IxqOeQYJkBxoXM+x65joRpI8fOjFavl7EHfUDs i61gnnt3OhNdw3PjgLflpFoxbbMq1E1ZFEqWPRIjzXV0NbROUar/iw6Gh0WVGDfpUiqr gwSouWH66+Nn/97hxdBugKf+ctkolSLvzUNtz16BO+H2IzX3tjaluaGIRSsNlnZ/qpt+ gUuj/3ZGSFK4O4f/zrYR66ma4WKKML2IQYPZYVM10qm1kUojbgJIiJfVT/nHVtwqTFVz DzPw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=tVv+Vfnnebucit7zfNA85xqx518DbqL2h1RJH2umzPI=; b=mfRf9wo+D0QG0MT7MBNdKyLLdGyRmY+deae0NVtcEs7+wiQwc8RdXNLrEfLL9M+6aH PylzIZLzccCsLbWS+Ia84VaWSmJZ8YY4glcR7SLCm/LfEOfpzq5ikmUwgp1GS8GCdb21 zbiJ2OZGSpq/W4QOMwjRQmGma04JKwllQo0LnhJC8uFNrtYXWmKV5IcPd20ULyP9kn3H mN/48/VjgE/eIlVN8IlMj03Of+fGSmdtnnOrCV60PzDMnLo/Pf3aDlQtU5ioyIXRwYro PCS+/0DCL4YCTkpK9r3CWfydrpYfMq2li9YA2my1FUANxRpy0/2ecodXRGjbLKS+2c1P 9kaw== X-Gm-Message-State: ALKqPwfpjmvFanJbF/ktwhdVDfX3aNWgdVjIJyOz+Z2apTEx7YjNDl6U sbx8wz4V2bt84Y6FoBIojELQDFSpExQJDT3qSy5Zzg== X-Google-Smtp-Source: AB8JxZozbvkhM3sXBugXItlaoWSp4H48TSiYq14ozutgvAv/9ZFiOJvMbX16c31fP4DFCAfBeyQfn1yzIrGT6SDGGvk= X-Received: by 2002:a1c:c355:: with SMTP id t82-v6mr1248431wmf.129.1526551331545; Thu, 17 May 2018 03:02:11 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.146.194 with HTTP; Thu, 17 May 2018 03:01:31 -0700 (PDT) From: Johannes Lundberg Date: Thu, 17 May 2018 11:01:31 +0100 Message-ID: Subject: Resume without drm driver results in black screen To: freebsd-current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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 May 2018 10:02:13 -0000 Hi I revived this old bug https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213501 Considering this also affects all X users using scfb driver it's worth investigating. From owner-freebsd-current@freebsd.org Thu May 17 12:32:30 2018 Return-Path: Delivered-To: freebsd-current@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 60E1DEEE88D for ; Thu, 17 May 2018 12:32:30 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from mx.catwhisker.org (mx.catwhisker.org [198.144.209.73]) (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 A97F87DA10 for ; Thu, 17 May 2018 12:32:29 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.15.2/8.15.2) with ESMTP id w4HCV6IV075460; Thu, 17 May 2018 12:31:06 GMT (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.15.2/8.15.2/Submit) id w4HCV4Nt075459; Thu, 17 May 2018 05:31:04 -0700 (PDT) (envelope-from david) Date: Thu, 17 May 2018 05:31:04 -0700 From: David Wolfskill To: =?iso-8859-1?Q?Jean-S=E9bastien_P=E9dron?= Cc: freebsd-current@freebsd.org Subject: Re: Something between r333623 - r333670 locks up at start of boot Message-ID: <20180517123104.GL1204@albert.catwhisker.org> Mail-Followup-To: David Wolfskill , =?iso-8859-1?Q?Jean-S=E9bastien_P=E9dron?= , freebsd-current@freebsd.org References: <20180516124255.GJ1204@albert.catwhisker.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="VWsRa3B5GiQd+kAA" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.5 (2018-04-13) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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 May 2018 12:32:30 -0000 --VWsRa3B5GiQd+kAA Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, May 17, 2018 at 09:34:03AM +0200, Jean-S=E9bastien P=E9dron wrote: > ... > I broke syscons(4) yesterday and bde@ provided a patch which cem@ > committed in r333683 [1]. >=20 > It should work again for you now. Sorry for the breakage. > .... Aye, all better now: FreeBSD g1-215.catwhisker.org 12.0-CURRENT FreeBSD 12.0-CURRENT #192 r3337= 10M/333710:1200063: Thu May 17 05:23:56 PDT 2018 root@g1-215.catwhisker= =2Eorg:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY amd64 Thanks! :-) Peace, david --=20 David H. Wolfskill david@catwhisker.org Mr. Trump: Just how does reneging on the Iran nuclear deal make the US "saf= er?" See http://www.catwhisker.org/~david/publickey.gpg for my public key. --VWsRa3B5GiQd+kAA Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEEzLfO+ReoAfQwZNd7FTnMQKBJ7hcFAlr9dghfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEND QjdDRUY5MTdBODAxRjQzMDY0RDc3QjE1MzlDQzQwQTA0OUVFMTcACgkQFTnMQKBJ 7het7Af+InuK3up68YL107+wM0Iy+CeKjcOnOKwPXQ5yYh9tduAVsnnd4X21MvPd eLST29XCmC7YdBCeWli4aUmnHfRWL03yE4ltfYh4L8gh4cNUQaIccQBe/v/noBog 1JN3r9vr/kQ9sHy5sNB4PGzylx2S8VLmrYDbdULNiaw6z/Pz5/KbkpauXmDyzOLU FVT13NM/c4ffmQ5ymCtl2Idf8LBgGXhNOJ3lV8hJSx1M29nhWCkBm6inpr33ryjF +Zs5y0H+hQKQ4eChCu1IOo8VabFZZw/21DFJkE+FK2byjC8RLgEpxnHMnLPuQUDL nJ7Z7WV+VFyzTS2ayObvVjmzOnwr4Q== =w5LJ -----END PGP SIGNATURE----- --VWsRa3B5GiQd+kAA-- From owner-freebsd-current@freebsd.org Thu May 17 13:26:05 2018 Return-Path: Delivered-To: freebsd-current@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 11D1CEF118B for ; Thu, 17 May 2018 13:26:05 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1a.eu.mailhop.org (outbound1a.eu.mailhop.org [52.58.109.202]) (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 93EAE7F566 for ; Thu, 17 May 2018 13:26:03 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: d247bfed-59d5-11e8-afd2-4ddcc8249dd4 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound1.eu.mailhop.org (Halon) with ESMTPSA id d247bfed-59d5-11e8-afd2-4ddcc8249dd4; Thu, 17 May 2018 13:25:53 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id w4HDPq3M083860; Thu, 17 May 2018 07:25:52 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1526563552.32688.47.camel@freebsd.org> Subject: Re: serial console vs suspend From: Ian Lepore To: Andriy Gapon , freebsd-hackers , FreeBSD Current Date: Thu, 17 May 2018 07:25:52 -0600 In-Reply-To: <0e1d5601-f792-0708-3bcf-7153bea8f679@FreeBSD.org> References: <0e1d5601-f792-0708-3bcf-7153bea8f679@FreeBSD.org> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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 May 2018 13:26:05 -0000 On Thu, 2018-05-17 at 10:54 +0300, Andriy Gapon wrote: > > It seems that the serial console, or rather a UART used by it, may require > re-initialization after waking up (from suspend to RAM).  At least one of my > systems fails to wake up properly if I configure the serial console.  I've done > some experimenting with cu (and without the console) and the UART seems to be in > some weird state, it echoes back the input and does not send anything on the > wire.  I guess that trying to print to the serial console while the UART is in > that state results in a hang. > > To test the theory I made this hack and it does help: > Index: sys/dev/uart/uart_tty.c > =================================================================== > --- sys/dev/uart/uart_tty.c (revision 333667) > +++ sys/dev/uart/uart_tty.c (working copy) > @@ -114,6 +114,13 @@ uart_cninit(struct consdev *cp) >   uart_init(di); >  } > > +void uart_resume(void); > +void > +uart_resume(void) > +{ > + uart_init(&uart_console); > +} > + >  static void >  uart_cnterm(struct consdev *cp) >  { > Index: sys/x86/acpica/acpi_wakeup.c > =================================================================== > --- sys/x86/acpica/acpi_wakeup.c (revision 333667) > +++ sys/x86/acpica/acpi_wakeup.c (working copy) > @@ -204,6 +205,8 @@ acpi_wakeup_cpus(struct acpi_softc *sc) >  } >  #endif > > +extern void uart_resume(void); > + >  int >  acpi_sleep_machdep(struct acpi_softc *sc, int state) >  { > @@ -300,6 +303,7 @@ acpi_sleep_machdep(struct acpi_softc *sc, int stat >  #else >   npxresume(susppcbs[0]->sp_fpususpend); >  #endif > + uart_resume(); >   } > >   return (1); /* wakeup successfully */ > > > =================================================================== > > This is quick and dirty, of course. > I think that this should go through the console layer. > And, obviously, not all consoles actually need such a reinit. > > So, maybe: > cnresume() > { > for each console { > if cn->cn_ops->cn_resume != NULL > cn->cn_ops->cn_resume(cn) > } > } > > uart_resume(struct consdev *cp) > { > uart_init(cp->cn_arg); > } > > What do you think? > > Hmm, it looks like CONSOLE_DRIVER() does not allow to omit a console method. > So, will I have to add a dummy resume to all console drivers? Why should it go through the console layer? If the uart hardware needs some re-init on resume, won't that be true whether the uart is serving as a console, a dial-in terminal, or the interface to wifi or bluetooth chip? -- Ian From owner-freebsd-current@freebsd.org Thu May 17 13:28:52 2018 Return-Path: Delivered-To: freebsd-current@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 3FBB2EF147F; Thu, 17 May 2018 13:28:52 +0000 (UTC) (envelope-from agapon@gmail.com) Received: from mail-lf0-f54.google.com (mail-lf0-f54.google.com [209.85.215.54]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 99AF57FA13; Thu, 17 May 2018 13:28:51 +0000 (UTC) (envelope-from agapon@gmail.com) Received: by mail-lf0-f54.google.com with SMTP id b18-v6so8756180lfa.9; Thu, 17 May 2018 06:28:51 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:openpgp:autocrypt :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=xiW/oUiGJsHv95mXAGlg8nzZjReZ0wqnAplT+Vjfkp8=; b=LsA7qghI1PCb/XWgeqEgVzRrNqHK7cKEMpG+WL0NzAtZNablpctP9DyW2uQGaDYoLC OqsbQCEQzXQcmTUoX4DgevRn607IwW5p8epISBICnJxlwEh5/L+4EDfmn1CnqcRfHywe YKPc/H2fvm4XhtXFT8uVj9rEiJ2G16yMltbNs2HpEhjxX+SjfEpdPmUpikRVo8tupqmI eIdGfAjVrEpI6QEnsDd5Nwg5rImzxEqkUb2ly1tXHazO7p4ohXX2wuubGLSVPWvumRwH lrUaytia7IJ55ZmR/H5utv6kzWfIZBC/jK/omBl+LUI9/8bKIPN1efhryWIG6h568fzc D6qw== X-Gm-Message-State: ALKqPwfFV5XsgEsH0wv9TdN8SkokEK3R5jLKAxFeheabQ2KEpPjl2Zns /UDcD9xLwxCsIE+WUak5mDRsS1Ro X-Google-Smtp-Source: AB8JxZr1XRtiBp/EV0j58F8gTnkyPjy9Zy+2o6YVWaFrKgCtmCZuwPqQY+kSPt+K4S7RrPLynZaJGQ== X-Received: by 2002:a19:4e1c:: with SMTP id c28-v6mr17287004lfb.61.1526563729465; Thu, 17 May 2018 06:28:49 -0700 (PDT) Received: from [192.168.0.88] (east.meadow.volia.net. [93.72.151.96]) by smtp.googlemail.com with ESMTPSA id v9-v6sm1227354lfa.30.2018.05.17.06.28.48 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 17 May 2018 06:28:48 -0700 (PDT) Subject: Re: serial console vs suspend To: Ian Lepore , freebsd-hackers , FreeBSD Current References: <0e1d5601-f792-0708-3bcf-7153bea8f679@FreeBSD.org> <1526563552.32688.47.camel@freebsd.org> From: Andriy Gapon Openpgp: preference=signencrypt Autocrypt: addr=avg@FreeBSD.org; prefer-encrypt=mutual; keydata= xsFNBFm4LIgBEADNB/3lT7f15UKeQ52xCFQx/GqHkSxEdVyLFZTmY3KyNPQGBtyvVyBfprJ7 mAeXZWfhat6cKNRAGZcL5EmewdQuUfQfBdYmKjbw3a9GFDsDNuhDA2QwFt8BmkiVMRYyvI7l N0eVzszWCUgdc3qqM6qqcgBaqsVmJluwpvwp4ZBXmch5BgDDDb1MPO8AZ2QZfIQmplkj8Y6Z AiNMknkmgaekIINSJX8IzRzKD5WwMsin70psE8dpL/iBsA2cpJGzWMObVTtCxeDKlBCNqM1i gTXta1ukdUT7JgLEFZk9ceYQQMJJtUwzWu1UHfZn0Fs29HTqawfWPSZVbulbrnu5q55R4PlQ /xURkWQUTyDpqUvb4JK371zhepXiXDwrrpnyyZABm3SFLkk2bHlheeKU6Yql4pcmSVym1AS4 dV8y0oHAfdlSCF6tpOPf2+K9nW1CFA8b/tw4oJBTtfZ1kxXOMdyZU5fiG7xb1qDgpQKgHUX8 7Rd2T1UVLVeuhYlXNw2F+a2ucY+cMoqz3LtpksUiBppJhw099gEXehcN2JbUZ2TueJdt1FdS ztnZmsHUXLxrRBtGwqnFL7GSd6snpGIKuuL305iaOGODbb9c7ne1JqBbkw1wh8ci6vvwGlzx rexzimRaBzJxlkjNfMx8WpCvYebGMydNoeEtkWldtjTNVsUAtQARAQABzR5BbmRyaXkgR2Fw b24gPGF2Z0BGcmVlQlNELm9yZz7CwZQEEwEIAD4WIQS+LEO7ngQnXA4Bjr538m7TUc1yjwUC WbgsiAIbIwUJBaOagAULCQgHAgYVCAkKCwIEFgIDAQIeAQIXgAAKCRB38m7TUc1yj+JAEACV l9AK/nOWAt/9cufV2fRj0hdOqB1aCshtSrwHk/exXsDa4/FkmegxXQGY+3GWX3deIyesbVRL rYdtdK0dqJyT1SBqXK1h3/at9rxr9GQA6KWOxTjUFURsU7ok/6SIlm8uLRPNKO+yq0GDjgaO LzN+xykuBA0FlhQAXJnpZLcVfPJdWv7sSHGedL5ln8P8rxR+XnmsA5TUaaPcbhTB+mG+iKFj GghASDSfGqLWFPBlX/fpXikBDZ1gvOr8nyMY9nXhgfXpq3B6QCRYKPy58ChrZ5weeJZ29b7/ QdEO8NFNWHjSD9meiLdWQaqo9Y7uUxN3wySc/YUZxtS0bhAd8zJdNPsJYG8sXgKjeBQMVGuT eCAJFEYJqbwWvIXMfVWop4+O4xB+z2YE3jAbG/9tB/GSnQdVSj3G8MS80iLS58frnt+RSEw/ psahrfh0dh6SFHttE049xYiC+cM8J27Aaf0i9RflyITq57NuJm+AHJoU9SQUkIF0nc6lfA+o JRiyRlHZHKoRQkIg4aiKaZSWjQYRl5Txl0IZUP1dSWMX4s3XTMurC/pnja45dge/4ESOtJ9R 8XuIWg45Oq6MeIWdjKddGhRj3OohsltKgkEU3eLKYtB6qRTQypHHUawCXz88uYt5e3w4V16H lCpSTZV/EVHnNe45FVBlvK7k7HFfDDkryM7BTQRZuCyIARAAlq0slcsVboY/+IUJdcbEiJRW be9HKVz4SUchq0z9MZPX/0dcnvz/gkyYA+OuM78dNS7Mbby5dTvOqfpLJfCuhaNYOhlE0wY+ 1T6Tf1f4c/uA3U/YiadukQ3+6TJuYGAdRZD5EqYFIkreARTVWg87N9g0fT9BEqLw9lJtEGDY EWUE7L++B8o4uu3LQFEYxcrb4K/WKmgtmFcm77s0IKDrfcX4doV92QTIpLiRxcOmCC/OCYuO jB1oaaqXQzZrCutXRK0L5XN1Y1PYjIrEzHMIXmCDlLYnpFkK+itlXwlE2ZQxkfMruCWdQXye syl2fynAe8hvp7Mms9qU2r2K9EcJiR5N1t1C2/kTKNUhcRv7Yd/vwusK7BqJbhlng5ZgRx0m WxdntU/JLEntz3QBsBsWM9Y9wf2V4tLv6/DuDBta781RsCB/UrU2zNuOEkSixlUiHxw1dccI 6CVlaWkkJBxmHX22GdDFrcjvwMNIbbyfQLuBq6IOh8nvu9vuItup7qemDG3Ms6TVwA7BD3j+ 3fGprtyW8Fd/RR2bW2+LWkMrqHffAr6Y6V3h5kd2G9Q8ZWpEJk+LG6Mk3fhZhmCnHhDu6CwN MeUvxXDVO+fqc3JjFm5OxhmfVeJKrbCEUJyM8ESWLoNHLqjywdZga4Q7P12g8DUQ1mRxYg/L HgZY3zfKOqcAEQEAAcLBfAQYAQgAJhYhBL4sQ7ueBCdcDgGOvnfybtNRzXKPBQJZuCyIAhsM BQkFo5qAAAoJEHfybtNRzXKPBVwQAKfFy9P7N3OsLDMB56A4Kf+ZT+d5cIx0Yiaf4n6w7m3i ImHHHk9FIetI4Xe54a2IXh4Bq5UkAGY0667eIs+Z1Ea6I2i27Sdo7DxGwq09Qnm/Y65ADvXs 3aBvokCcm7FsM1wky395m8xUos1681oV5oxgqeRI8/76qy0hD9WR65UW+HQgZRIcIjSel9vR XDaD2HLGPTTGr7u4v00UeTMs6qvPsa2PJagogrKY8RXdFtXvweQFz78NbXhluwix2Tb9ETPk LIpDrtzV73CaE2aqBG/KrboXT2C67BgFtnk7T7Y7iKq4/XvEdDWscz2wws91BOXuMMd4c/c4 OmGW9m3RBLufFrOag1q5yUS9QbFfyqL6dftJP3Zq/xe+mr7sbWbhPVCQFrH3r26mpmy841ym dwQnNcsbIGiBASBSKksOvIDYKa2Wy8htPmWFTEOPRpFXdGQ27awcjjnB42nngyCK5ukZDHi6 w0qK5DNQQCkiweevCIC6wc3p67jl1EMFY5+z+zdTPb3h7LeVnGqW0qBQl99vVFgzLxchKcl0 R/paSFgwqXCZhAKMuUHncJuynDOP7z5LirUeFI8qsBAJi1rXpQoLJTVcW72swZ42IdPiboqx NbTMiNOiE36GqMcTPfKylCbF45JNX4nF9ElM0E+Y8gi4cizJYBRr2FBJgay0b9Cp Message-ID: Date: Thu, 17 May 2018 16:28:47 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <1526563552.32688.47.camel@freebsd.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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 May 2018 13:28:52 -0000 On 17/05/2018 16:25, Ian Lepore wrote: > Why should it go through the console layer? If the uart hardware needs > some re-init on resume, won't that be true whether the uart is serving > as a console, a dial-in terminal, or the interface to wifi or bluetooth > chip? I think that for those things a normal device resume should do. console gets used very early, so it may require a special resume. -- Andriy Gapon From owner-freebsd-current@freebsd.org Thu May 17 14:59:29 2018 Return-Path: Delivered-To: freebsd-current@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 19B96EAAFC1 for ; Thu, 17 May 2018 14:59:29 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x22f.google.com (mail-it0-x22f.google.com [IPv6:2607:f8b0:4001:c0b::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9B3738396D for ; Thu, 17 May 2018 14:59:28 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x22f.google.com with SMTP id 70-v6so9247456ity.2 for ; Thu, 17 May 2018 07:59:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=SWA8guDu/EEAqWB6dQPgZ5VBMKLP4AxtihbKV7/947M=; b=DVRszpDE3tBqnGcG6dzmsiwhqsfMlWiXm3lTnHHtKSgGQMMB8Z6CyfyKDNBVdB8/AX m+qrsK5kugojgE65U15E50x2IcINWYwv5S6vY8DX2/BQZEpC3RS3lDB2soQMfsUDDbN4 xaLoHfP0tBfwhaXOvUHx5E9CNbCpC2a/IogtAioah8XbPIWKQTrwHF/zp2Q8uzr8c+F+ 6LTKDHKHL7T8jW8PRyEz+pTfbXhc39nH5dHyml1MSwOqv2NvVT+m+haXO1786l2uUF+K O9QAn75oaz2uPq32Bk5isQ7yubYxbvFgZLhLtuVI5sXYjBShdC5b0u5JjOsfIzTbdANV EMtw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=SWA8guDu/EEAqWB6dQPgZ5VBMKLP4AxtihbKV7/947M=; b=sIC78dWMn5ZEGdoEdgmagz4NRgmpRLF435YF7mBY85gbb5DkcVo3hAGZTKDmfxmNlT 8DB6tTVE8SqjwaTZZ2MG1mvHy1nx8pijW4UtD7B2xG6lHOqvL/pUZ/Jq3VZ4eGmlLAtc kaJeUaWINaKirxTP6hrG6/mFo/xkURbePikwodYm4UGSPJSHDxqfm+JX6tfQsuzHiLFF j3mYBl0t5MsHOwh4OltG/lH6HnhJg4dPuWbovwYAKinng2UFQuYFujG9XJEZth/WkAol GbQtEiB6QUVOqSGU0IsIqah0AqYKBkrzQ0BHt/Eru9U5Yharrr3oqh9P8FzI6FMwt9i8 NyMw== X-Gm-Message-State: ALKqPwcSrGTlDIrnQaucovgZP2e5PEBGZ2uza0UnsK/IN6//iBD9scA7 TewU7QAs8M5a8/J8tO8hKXgvVoLmsIjTQULRnNaJIg== X-Google-Smtp-Source: AB8JxZpE5rUA/S59ZANxtyX8/ZIVD6PvrLbOStbyKj+tEn+Z6UqGMth5Qz5XNCCPEBG8v+xLJ41zdk0a1Bd8/qc49fg= X-Received: by 2002:a24:4c55:: with SMTP id a82-v6mr2926477itb.1.1526569168004; Thu, 17 May 2018 07:59:28 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 2002:a4f:a649:0:0:0:0:0 with HTTP; Thu, 17 May 2018 07:59:27 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: References: <0e1d5601-f792-0708-3bcf-7153bea8f679@FreeBSD.org> <1526563552.32688.47.camel@freebsd.org> From: Warner Losh Date: Thu, 17 May 2018 08:59:27 -0600 X-Google-Sender-Auth: MbM5vind_VP0OzOtzw_oxqu9Vhk Message-ID: Subject: Re: serial console vs suspend To: Andriy Gapon Cc: Ian Lepore , freebsd-hackers , FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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 May 2018 14:59:29 -0000 On Thu, May 17, 2018 at 7:28 AM, Andriy Gapon wrote: > On 17/05/2018 16:25, Ian Lepore wrote: > > Why should it go through the console layer? If the uart hardware needs > > some re-init on resume, won't that be true whether the uart is serving > > as a console, a dial-in terminal, or the interface to wifi or bluetooth > > chip? > > I think that for those things a normal device resume should do. > console gets used very early, so it may require a special resume. > We should re-init both places (maybe with a flag to prevent double if that's harmful). The console is needed very early after the resume, often earlier than the accidental location in the device tree the console device_t node lives. That way we don't lose output. The console layer gives us a convenient hook early in resume to cope. It's yet another reason, though, it should be restricted to true console devices, but that's another conversation. Warner From owner-freebsd-current@freebsd.org Thu May 17 18:14:08 2018 Return-Path: Delivered-To: freebsd-current@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 D3128EDBF60 for ; Thu, 17 May 2018 18:14:08 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from vps-mail.nomadlogic.org (mail.nomadlogic.org [IPv6:2607:f2f8:a098::2]) (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 557316E3C4 for ; Thu, 17 May 2018 18:14:08 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from [192.168.1.223] (cpe-75-82-194-8.socal.res.rr.com [75.82.194.8]) by vps-mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id c6563bcf TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO for ; Thu, 17 May 2018 11:14:07 -0700 (PDT) Subject: Re: suspend/resume regression From: Pete Wright To: FreeBSD Current References: <1e608109-fcdd-d794-b03a-2e417300b95a@nomadlogic.org> Message-ID: Date: Thu, 17 May 2018 11:14:06 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <1e608109-fcdd-d794-b03a-2e417300b95a@nomadlogic.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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 May 2018 18:14:09 -0000 On 05/12/2018 19:25, Pete Wright wrote: > hi there - i have an amd64 laptop that's been running CURRENT for a > while using both drm-next and drm-stable for graphics. during the past > week or so i've run into issues with suspend resume...well technically > resume has stopped working.  i've tested a couple configurations and > none have allowed my system to resume successfully: > > - drm-next installed with DMC firmware loaded > - drm-next installed without DMC firmware loaded (worked previously) > - drm-stable with DMC > - drm-stable without DMC > - no drm modules loaded. > > I've also tested these configs with the following sysctl set to 0 and 1: > hw.acpi.reset_video > > at this point i'd like to help find what the regression i'm running > into is, so any pointers on how i can help? the system seems to boot > and i'm pretty sure i can ssh into it most times, just not sure what > info i should grab to help.  nothing of interest in messages or dmesg > buffer either. > Closing the loop on this thread.  Git commit 4e99d4e797ba9cea01897b6909b061db841f855a fixes this issue on my end.  For more info there is a thread on this list named "Lag after resume culprit found" that has details. -pete -- Pete Wright pete@nomadlogic.org @nomadlogicLA From owner-freebsd-current@freebsd.org Thu May 17 19:42:43 2018 Return-Path: Delivered-To: freebsd-current@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 ED49CEDEAA1 for ; Thu, 17 May 2018 19:42:42 +0000 (UTC) (envelope-from agapon@gmail.com) Received: from mail-lf0-f54.google.com (mail-lf0-f54.google.com [209.85.215.54]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5373173653 for ; Thu, 17 May 2018 19:42:42 +0000 (UTC) (envelope-from agapon@gmail.com) Received: by mail-lf0-f54.google.com with SMTP id h197-v6so10465066lfg.11 for ; Thu, 17 May 2018 12:42:41 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:openpgp:autocrypt :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=1fO9E4noVtAn4fEZ/z2M11tttxGbBvlD+x+FiPzCd6Y=; b=tVHvkAtpNpjPQrxeZUAYLyPK3s/uARbpiRKI6krTCE1v9UL11jfbp9aC6ZoNLzCH8X IwYprpXJepioxL2y+Hglux+zthzisn4CD0akvk8cp8nHJFcPXrx7Wi0VouR590nU43h0 AuPAG+OxhIa/44Jh5tJMzkgP/EgLUW2B0ZNirNUBvMB0DVD+UEOiSVkz1pX0NC0u6YEx 1uUzNXMhJkP7Txpc5iyDA27mYRwvC2IuLgWKPb7s2Ke66jGYpv3XjKdWBERZ17VQNmoU 7nSglOFGXLJrClRaamVEstkRc7cgN7KS5fY5xBS9E5QfDOk2clAoxUL90ClqXiB3psTV D8MQ== X-Gm-Message-State: ALKqPwcFm2Ax/B77Zsxn0KSqMyGUFZ1j7fUHy2xUW8hrwCybPsDj76sG XaulvTKKEBfcqKduHHACsY34uDqf X-Google-Smtp-Source: AB8JxZrrXxfhmxVaxgxmYlVk8Uz4yx38DpR1egC2iNNPeEKkfxwQ2EXcFpcm9+DFRqxybwNgs90L7Q== X-Received: by 2002:a19:5d43:: with SMTP id p3-v6mr2671824lfj.142.1526586160349; Thu, 17 May 2018 12:42:40 -0700 (PDT) Received: from [192.168.0.88] (east.meadow.volia.net. [93.72.151.96]) by smtp.googlemail.com with ESMTPSA id a21-v6sm1403887lfl.84.2018.05.17.12.42.38 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 17 May 2018 12:42:39 -0700 (PDT) Subject: Re: suspend/resume regression To: Pete Wright , FreeBSD Current References: <1e608109-fcdd-d794-b03a-2e417300b95a@nomadlogic.org> From: Andriy Gapon Openpgp: preference=signencrypt Autocrypt: addr=avg@FreeBSD.org; prefer-encrypt=mutual; keydata= xsFNBFm4LIgBEADNB/3lT7f15UKeQ52xCFQx/GqHkSxEdVyLFZTmY3KyNPQGBtyvVyBfprJ7 mAeXZWfhat6cKNRAGZcL5EmewdQuUfQfBdYmKjbw3a9GFDsDNuhDA2QwFt8BmkiVMRYyvI7l N0eVzszWCUgdc3qqM6qqcgBaqsVmJluwpvwp4ZBXmch5BgDDDb1MPO8AZ2QZfIQmplkj8Y6Z AiNMknkmgaekIINSJX8IzRzKD5WwMsin70psE8dpL/iBsA2cpJGzWMObVTtCxeDKlBCNqM1i gTXta1ukdUT7JgLEFZk9ceYQQMJJtUwzWu1UHfZn0Fs29HTqawfWPSZVbulbrnu5q55R4PlQ /xURkWQUTyDpqUvb4JK371zhepXiXDwrrpnyyZABm3SFLkk2bHlheeKU6Yql4pcmSVym1AS4 dV8y0oHAfdlSCF6tpOPf2+K9nW1CFA8b/tw4oJBTtfZ1kxXOMdyZU5fiG7xb1qDgpQKgHUX8 7Rd2T1UVLVeuhYlXNw2F+a2ucY+cMoqz3LtpksUiBppJhw099gEXehcN2JbUZ2TueJdt1FdS ztnZmsHUXLxrRBtGwqnFL7GSd6snpGIKuuL305iaOGODbb9c7ne1JqBbkw1wh8ci6vvwGlzx rexzimRaBzJxlkjNfMx8WpCvYebGMydNoeEtkWldtjTNVsUAtQARAQABzR5BbmRyaXkgR2Fw b24gPGF2Z0BGcmVlQlNELm9yZz7CwZQEEwEIAD4WIQS+LEO7ngQnXA4Bjr538m7TUc1yjwUC WbgsiAIbIwUJBaOagAULCQgHAgYVCAkKCwIEFgIDAQIeAQIXgAAKCRB38m7TUc1yj+JAEACV l9AK/nOWAt/9cufV2fRj0hdOqB1aCshtSrwHk/exXsDa4/FkmegxXQGY+3GWX3deIyesbVRL rYdtdK0dqJyT1SBqXK1h3/at9rxr9GQA6KWOxTjUFURsU7ok/6SIlm8uLRPNKO+yq0GDjgaO LzN+xykuBA0FlhQAXJnpZLcVfPJdWv7sSHGedL5ln8P8rxR+XnmsA5TUaaPcbhTB+mG+iKFj GghASDSfGqLWFPBlX/fpXikBDZ1gvOr8nyMY9nXhgfXpq3B6QCRYKPy58ChrZ5weeJZ29b7/ QdEO8NFNWHjSD9meiLdWQaqo9Y7uUxN3wySc/YUZxtS0bhAd8zJdNPsJYG8sXgKjeBQMVGuT eCAJFEYJqbwWvIXMfVWop4+O4xB+z2YE3jAbG/9tB/GSnQdVSj3G8MS80iLS58frnt+RSEw/ psahrfh0dh6SFHttE049xYiC+cM8J27Aaf0i9RflyITq57NuJm+AHJoU9SQUkIF0nc6lfA+o JRiyRlHZHKoRQkIg4aiKaZSWjQYRl5Txl0IZUP1dSWMX4s3XTMurC/pnja45dge/4ESOtJ9R 8XuIWg45Oq6MeIWdjKddGhRj3OohsltKgkEU3eLKYtB6qRTQypHHUawCXz88uYt5e3w4V16H lCpSTZV/EVHnNe45FVBlvK7k7HFfDDkryM7BTQRZuCyIARAAlq0slcsVboY/+IUJdcbEiJRW be9HKVz4SUchq0z9MZPX/0dcnvz/gkyYA+OuM78dNS7Mbby5dTvOqfpLJfCuhaNYOhlE0wY+ 1T6Tf1f4c/uA3U/YiadukQ3+6TJuYGAdRZD5EqYFIkreARTVWg87N9g0fT9BEqLw9lJtEGDY EWUE7L++B8o4uu3LQFEYxcrb4K/WKmgtmFcm77s0IKDrfcX4doV92QTIpLiRxcOmCC/OCYuO jB1oaaqXQzZrCutXRK0L5XN1Y1PYjIrEzHMIXmCDlLYnpFkK+itlXwlE2ZQxkfMruCWdQXye syl2fynAe8hvp7Mms9qU2r2K9EcJiR5N1t1C2/kTKNUhcRv7Yd/vwusK7BqJbhlng5ZgRx0m WxdntU/JLEntz3QBsBsWM9Y9wf2V4tLv6/DuDBta781RsCB/UrU2zNuOEkSixlUiHxw1dccI 6CVlaWkkJBxmHX22GdDFrcjvwMNIbbyfQLuBq6IOh8nvu9vuItup7qemDG3Ms6TVwA7BD3j+ 3fGprtyW8Fd/RR2bW2+LWkMrqHffAr6Y6V3h5kd2G9Q8ZWpEJk+LG6Mk3fhZhmCnHhDu6CwN MeUvxXDVO+fqc3JjFm5OxhmfVeJKrbCEUJyM8ESWLoNHLqjywdZga4Q7P12g8DUQ1mRxYg/L HgZY3zfKOqcAEQEAAcLBfAQYAQgAJhYhBL4sQ7ueBCdcDgGOvnfybtNRzXKPBQJZuCyIAhsM BQkFo5qAAAoJEHfybtNRzXKPBVwQAKfFy9P7N3OsLDMB56A4Kf+ZT+d5cIx0Yiaf4n6w7m3i ImHHHk9FIetI4Xe54a2IXh4Bq5UkAGY0667eIs+Z1Ea6I2i27Sdo7DxGwq09Qnm/Y65ADvXs 3aBvokCcm7FsM1wky395m8xUos1681oV5oxgqeRI8/76qy0hD9WR65UW+HQgZRIcIjSel9vR XDaD2HLGPTTGr7u4v00UeTMs6qvPsa2PJagogrKY8RXdFtXvweQFz78NbXhluwix2Tb9ETPk LIpDrtzV73CaE2aqBG/KrboXT2C67BgFtnk7T7Y7iKq4/XvEdDWscz2wws91BOXuMMd4c/c4 OmGW9m3RBLufFrOag1q5yUS9QbFfyqL6dftJP3Zq/xe+mr7sbWbhPVCQFrH3r26mpmy841ym dwQnNcsbIGiBASBSKksOvIDYKa2Wy8htPmWFTEOPRpFXdGQ27awcjjnB42nngyCK5ukZDHi6 w0qK5DNQQCkiweevCIC6wc3p67jl1EMFY5+z+zdTPb3h7LeVnGqW0qBQl99vVFgzLxchKcl0 R/paSFgwqXCZhAKMuUHncJuynDOP7z5LirUeFI8qsBAJi1rXpQoLJTVcW72swZ42IdPiboqx NbTMiNOiE36GqMcTPfKylCbF45JNX4nF9ElM0E+Y8gi4cizJYBRr2FBJgay0b9Cp Message-ID: <34cfc5d0-041b-4822-6e8a-5949b4cc183a@FreeBSD.org> Date: Thu, 17 May 2018 22:42:38 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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 May 2018 19:42:43 -0000 On 17/05/2018 21:14, Pete Wright wrote: > > > On 05/12/2018 19:25, Pete Wright wrote: >> hi there - i have an amd64 laptop that's been running CURRENT for a while >> using both drm-next and drm-stable for graphics. during the past week or so >> i've run into issues with suspend resume...well technically resume has stopped >> working.  i've tested a couple configurations and none have allowed my system >> to resume successfully: >> >> - drm-next installed with DMC firmware loaded >> - drm-next installed without DMC firmware loaded (worked previously) >> - drm-stable with DMC >> - drm-stable without DMC >> - no drm modules loaded. >> >> I've also tested these configs with the following sysctl set to 0 and 1: >> hw.acpi.reset_video >> >> at this point i'd like to help find what the regression i'm running into is, >> so any pointers on how i can help? the system seems to boot and i'm pretty >> sure i can ssh into it most times, just not sure what info i should grab to >> help.  nothing of interest in messages or dmesg buffer either. >> > > Closing the loop on this thread.  Git commit > 4e99d4e797ba9cea01897b6909b061db841f855a fixes this issue on my end.  For more > info there is a thread on this list named "Lag after resume culprit found" that > has details. Thank you for confirming that it was the same issue and that (or, rather, because) it's fixed now. -- Andriy Gapon From owner-freebsd-current@freebsd.org Fri May 18 01:34:42 2018 Return-Path: Delivered-To: freebsd-current@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 114C3EE5711 for ; Fri, 18 May 2018 01:34:42 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from mail.ignoranthack.me (ignoranthack.me [199.102.79.106]) (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 870CF7E743 for ; Fri, 18 May 2018 01:34:41 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from [192.168.0.6] (67-0-228-75.albq.qwest.net [67.0.228.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: sbruno@ignoranthack.me) by mail.ignoranthack.me (Postfix) with ESMTPSA id 4F283192882 for ; Thu, 17 May 2018 17:38:36 +0000 (UTC) Subject: Re: Microcode Updater Changes To: freebsd-current@freebsd.org References: <17625f2a-c637-26dd-1d6d-93b733781f6c@freebsd.org> From: Sean Bruno Openpgp: preference=signencrypt Autocrypt: addr=sbruno@freebsd.org; prefer-encrypt=mutual; keydata= xsBNBFk+0UEBCADaf4bgxxKvMOhRV5NPoGWRCCGm49d6+1VFNlQ77WsY/+Zvf95TPULdRlnG w648KfxWt7+O3kdKhdRwnqlXWC7zA2Qt0dRE1yIqOGJ4jp4INvp/bcxWzgr0aoKOjrlnfxRV bh+s0rzdZt6TsNL3cVYxkC8oezjaUkHdW4mFJU249U1QJogkF8g0FeKNfEcjEkwJNX6lQJH+ EzCWT0NCk6J+Xyo+zOOljxPp1OUfdvZi3ulkU/qTZstGVWxFVsP8xQklV/y3AFcbIYx6iGJ4 5L7WuB0IWhO7Z4yHENr8wFaNYwpod9i4egX2BugbrM8pOfhN2/qqdeG1L5LMtXw3yyAhABEB AAHNN1NlYW4gQnJ1bm8gKEZyZWVCU0QgRGV2ZWxvcGVyIEtleSkgPHNicnVub0BmcmVlYnNk Lm9yZz7CwJQEEwEKAD4WIQToxOn4gDUE4eP0ujS95PX+ibX8tgUCWT7RQQIbAwUJBaOagAUL CQgHAwUVCgkICwUWAwIBAAIeAQIXgAAKCRC95PX+ibX8ttKTCACFKzRc56EBAlVotq02EjZP SfX+unlk6AuPBzShxqRxeK+bGYVCigrYd1M8nnskv0dEiZ5iYeND9HIxbpEyopqgpVTibA7w gBXaZ7SOEhNX1wXwg14JrralfSmPFMYni+sWegPMX/zwfAsn1z4mG1Nn44Xqo3o7CfpkMPy6 M5Bow2IDzIhEYISLR+urxs74/aHU35PLtBSDtu18914SEMDdva27MARN8mbeCDbuJVfGCPWy YHuy2t+9u2Zn5Dd+t3sBXLM9gpeaMm+4x6TNPpESygbVdh4tDdjVZ9DK/bWFg0kMgfZoaq6J l0jNsQXrZV3bzYNFbVw04pFcvA2GIJ7xzsBNBFk+0UEBCADIXBmQOaKMHGbc9vwjhV4Oj5aZ DdhNedn12FVeTdOXJvuTOusgxS29lla0RenHGDsgD08UiFpasBXWq/E+BhQ19d+iRbLLR17O KKc1ZGefoVbLARLXD68J5j4XAyK+6k2KqBLlqzAEpHTzsksM9naARkVXiEVcrt6ciw0FSm8n kuK3gDKKe93XfzfP+TQdbvvzJc7Fa+appLbXz61TM1aikaQlda8bWubDegwXbuoJdB34xU1m yjr/N4o+raL0x7QrzdH+wwgrTTo+H4S2c1972Skt5K5tbxLowfHicRl23V8itVQr3sBtlX4+ 66q+Apm7+R36bUS/k+G45Sp6iPpxABEBAAHCwHwEGAEKACYWIQToxOn4gDUE4eP0ujS95PX+ ibX8tgUCWT7RQQIbDAUJBaOagAAKCRC95PX+ibX8trrIB/9Pljqt/JGamD9tx4dOVmxSyFg9 z2xzgklTLuDgS73MM120mM7ao9AQUeWiSle/H0UCK7xPOzC/aeUC4oygDQKAfkkNbCNTo3+A qDjBRA8qx0e9a/QjDL+RFgD4L5kLT4tToY8T8HaBp8h03LBfk510IaI8oL/Jg7vpM3PDtJMW tUi2H+yNFmL3NfM2oBToWKLFsoP54f/eeeImrNnrlLjLHPzqS+/9apgYqX2Jwiv3tHBc4FTO GuY8VvF7BpixJs8Pc2RUuCfSyodrp1YG1kRGlXAH0cqwwr0Zmk4+7dZvtVQMCl6kS6q1+84q JwtItxS2eXSEA4NO0sQ3BXUywANh Message-ID: Date: Thu, 17 May 2018 19:34:36 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <17625f2a-c637-26dd-1d6d-93b733781f6c@freebsd.org> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="eUqo1bDlxdbZMZijWzmoUKxV9niCtyCNy" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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 May 2018 01:34:42 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --eUqo1bDlxdbZMZijWzmoUKxV9niCtyCNy Content-Type: multipart/mixed; boundary="8kE6vYaI2wFUmVo4f7F3MTV9xcQFLLjYS"; protected-headers="v1" From: Sean Bruno To: freebsd-current@freebsd.org Message-ID: Subject: Re: Microcode Updater Changes References: <17625f2a-c637-26dd-1d6d-93b733781f6c@freebsd.org> In-Reply-To: <17625f2a-c637-26dd-1d6d-93b733781f6c@freebsd.org> --8kE6vYaI2wFUmVo4f7F3MTV9xcQFLLjYS Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 05/16/18 10:42, Sean Bruno wrote: > https://reviews.freebsd.org/D15443 >=20 > The FreeBSD Foundation has collaborated with a few folks so that we can= > continue to process and update microcode on FreeBSD. >=20 > This review represents the first step in updating our infrastructure. > If you are currently using microcode updates, please give this a spin > and report back if you see a different version of microcode being loade= d > on the new package vs the old package. >=20 > sean >=20 > bcc emaste >=20 Ports svn 470255 updates the microcode package devcpu-data to process the same files that linux (and the only ones Intel releases now). If you are a consumer of this package, you should see *no* difference in the version update to your CPU. If you do, please respond to this thread= =2E sean --8kE6vYaI2wFUmVo4f7F3MTV9xcQFLLjYS-- --eUqo1bDlxdbZMZijWzmoUKxV9niCtyCNy Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEE6MTp+IA1BOHj9Lo0veT1/om1/LYFAlr+LaxfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEU4 QzRFOUY4ODAzNTA0RTFFM0Y0QkEzNEJERTRGNUZFODlCNUZDQjYACgkQveT1/om1 /LZTqAgAwW1heEtHhRu/lvf9zZO3Kud6S122blL8xH7+BiK/uK+LIXUyp+j1J4pS nTs6/vvRVhG59eGW6pjzQe9pKwyuMCiiPPl1wMwjP2pBK6n/JPGwbERBVF/9Uqd5 9DAVPHhOHEHX66ZIBppYf+07mGwkslxQGM+muEo16/nzTqpePVC3MYs8CaBCRRAP /aQ0mU6hvZOtRJYzysEFW5mGf+POBslUBZD7vkC1fVa+VKvmceKn7EfbKA/L5hMP 4FJ7yGKV95Ay9nxWJYfJhzSkEPHVBNBt/KoGafPeSoF7urlHVInjCybs4i2z/9iD 7IrPYYUfvErubCLHJlimdAISXkNFmA== =hHRX -----END PGP SIGNATURE----- --eUqo1bDlxdbZMZijWzmoUKxV9niCtyCNy-- From owner-freebsd-current@freebsd.org Fri May 18 17:44:53 2018 Return-Path: Delivered-To: freebsd-current@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 212AEEAFC31 for ; Fri, 18 May 2018 17:44:53 +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 5950B814A8 for ; Fri, 18 May 2018 17:44:52 +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.90_1 (FreeBSD)) (envelope-from ) id 1fJity-000Ilc-W3 for freebsd-current@freebsd.org; Fri, 18 May 2018 19:10:46 +0200 Received: from [192.168.67.31] by mail.alvermark.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.90_1 (FreeBSD)) (envelope-from ) id 1fJity-000Lvh-Fz for freebsd-current@freebsd.org; Fri, 18 May 2018 19:10:46 +0200 To: freebsd-current@freebsd.org From: Jakob Alvermark Subject: EFI boot on ThinkPad X131e hangs Message-ID: <90c8ca1b-2848-e6ad-e429-a143ddbb576c@alvermark.net> Date: Fri, 18 May 2018 19:10:46 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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 May 2018 17:44:53 -0000 Hi, I was going to install FreeBSD on a ThinkPad X131e. It has the latest BIOS/EFI firmware (2.97) and is set to only boot UEFI. memstick.img created from -current r333786. The boot hangs after printing this: Consoles: EFI console I also tried FreeBSD-11.1-RELEASE-amd64-mini-memstick.img, same thing happens. OpenBSD 6.3 works fine. How can I debug this? Thanks, Jakob From owner-freebsd-current@freebsd.org Fri May 18 17:58:12 2018 Return-Path: Delivered-To: freebsd-current@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 587B2EB0472 for ; Fri, 18 May 2018 17:58:12 +0000 (UTC) (envelope-from zeising@freebsd.org) 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 EBBEB8201A for ; Fri, 18 May 2018 17:58:11 +0000 (UTC) (envelope-from zeising@freebsd.org) Received: from cid.daemonic.se (localhost [IPv6:::1]) by mail.daemonic.se (Postfix) with ESMTP id 40nbW70t3kzDhSq for ; Fri, 18 May 2018 17:58:11 +0000 (UTC) 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 OOoVz_lKIRAE for ; Fri, 18 May 2018 17:58:10 +0000 (UTC) Received: from celes.daemonic.se (celes.daemonic.se [IPv6:2001:470:dca9:2::3]) by mail.daemonic.se (Postfix) with ESMTPSA id 40nbW64xCMzDhBg for ; Fri, 18 May 2018 17:58:10 +0000 (UTC) From: Niclas Zeising Subject: [RFC] Deprecation and removal of the drm2 driver To: freebsd-current@freebsd.org Reply-To: freebsd-x11@freebsd.org Followup-To: freebsd-x11@freebsd.org Message-ID: <3a5edc5c-3caa-830b-4bd9-53ff52feb8a7@freebsd.org> Date: Fri, 18 May 2018 19:58:10 +0200 User-Agent: Mutt/1.5.21 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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 May 2018 17:58:12 -0000 [ Cross posted to freebsd-current@ and freebsd-x11@. Please respect=20 reply-to and send all replies to freebsd-x11@. Thanks! ] Hi! I propose that we remove the old drm2 driver (sys/dev/drm2) from=20 FreeBSD. I suggest the driver is marked as deprecated in 11.x and=20 removed from 12.0, as was done for other drivers recently. Some=20 background and rationale: The drm2 driver was the original port of a KMS driver to FreeBSD. It=20 was done by Konstantin Belousov to support Intel graphics cards, and=20 later extended by Jean-S=C3=A9bastien P=C3=A9dron as well as Konstantin t= o match=20 what's in Linux 3.8. This included unstable support from Haswell, but=20 nothing newer than that. For quite some time now we have had the graphics/drm-stable-kmod and=20 graphics/drm-next-kmods which provides support for modern AMD and Intel=20 graphics cards. These ports, together with the linuxkpi, or lkpi, has=20 made it significantly easier to port and update our graphics drivers.=20 Further, these new drivers cover the same drivers as the old drm2 driver. What does the community think? Is there anyone still using the drm2=20 driver on 12-CURRENT? If so, what is preventing you from switching to=20 the port? Thank you Regards --=20 Niclas Zeising FreeBSD x11/graphics team From owner-freebsd-current@freebsd.org Fri May 18 19:12:51 2018 Return-Path: Delivered-To: freebsd-current@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 A7748ED608C; Fri, 18 May 2018 19:12:51 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from smtp-out-so.shaw.ca (smtp-out-so.shaw.ca [64.59.136.138]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 24C0984CBD; Fri, 18 May 2018 19:12:50 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from spqr.komquats.com ([70.67.125.17]) by shaw.ca with ESMTPA id JknxfcSLz5wO5JknyfKlOP; Fri, 18 May 2018 13:12:43 -0600 X-Authority-Analysis: v=2.3 cv=SJtsqtnH c=1 sm=1 tr=0 a=VFtTW3WuZNDh6VkGe7fA3g==:117 a=VFtTW3WuZNDh6VkGe7fA3g==:17 a=VUJBJC2UJ8kA:10 a=YxBL1-UpAAAA:8 a=6I5d2MoRAAAA:8 a=kfqetBiWL20DLmbj0dEA:9 a=Mko7QwP8A-Fn5Cgz:21 a=XyS4Itba-1nQL2I0:21 a=QEXdDO2ut3YA:10 a=ayh4KuAN70hAMfvHlcAA:9 a=HgYwxTq5jBfRq67n:21 a=jFgkPnztwZeY-EKZ:21 a=mW0igfanQaLJB1Xb:21 a=_W_S_7VecoQA:10 a=Ia-lj3WSrqcvXOmTRaiG:22 a=IjZwj45LgO3ly-622nXo:22 Received: from [25.170.45.77] (unknown [72.143.234.207]) by spqr.komquats.com (Postfix) with ESMTPSA id AC74AB5D; Fri, 18 May 2018 12:12:39 -0700 (PDT) MIME-Version: 1.0 From: Cy Schubert Subject: RE: [RFC] Deprecation and removal of the drm2 driver Date: Fri, 18 May 2018 12:12:43 -0700 To: "freebsd-x11@freebsd.org" , "freebsd-current@freebsd.org" Message-Id: <20180518191239.AC74AB5D@spqr.komquats.com> X-CMAE-Envelope: MS4wfJJ5GeWMvH0cadamxO8HijqRXW+CCtSyYVcq72Bu96m3g3tbKERmn/ZGuWNnzlr8K0oaUIRgQBPHJU3MSsbXndDPbHglb3ruBBcm/cTZzHGktcyfW2Hn uYaWTlajLU2UN4w3wxdyUckX8AODIQAmYTUyORbGXLeAobLSzCL/fgXCB1tdtkBRubsjFTixyJ7f6x+aVN0qXpjGJLJqMPSfE+pscWcxNkA1SYdJJoQRhcVO Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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 May 2018 19:12:52 -0000 The port doesn't support i386. --- Sent using a tiny phone keyboard. Apologies for any typos and autocorrect. Also, this old phone only supports top post. Apologies. Cy Schubert or The need of the many outweighs the greed of the few. --- -----Original Message----- From: Niclas Zeising Sent: 18/05/2018 11:00 To: freebsd-current@freebsd.org Subject: [RFC] Deprecation and removal of the drm2 driver [ Cross posted to freebsd-current@ and freebsd-x11@. Please respect =0A= reply-to and send all replies to freebsd-x11@. Thanks! ]=0A= =0A= =0A= Hi!=0A= I propose that we remove the old drm2 driver (sys/dev/drm2) from =0A= FreeBSD. I suggest the driver is marked as deprecated in 11.x and =0A= removed from 12.0, as was done for other drivers recently. Some =0A= background and rationale:=0A= =0A= The drm2 driver was the original port of a KMS driver to FreeBSD. It =0A= was done by Konstantin Belousov to support Intel graphics cards, and =0A= later extended by Jean-S=C3=A9bastien P=C3=A9dron as well as Konstantin to = match =0A= what's in Linux 3.8. This included unstable support from Haswell, but =0A= nothing newer than that.=0A= =0A= For quite some time now we have had the graphics/drm-stable-kmod and =0A= graphics/drm-next-kmods which provides support for modern AMD and Intel =0A= graphics cards. These ports, together with the linuxkpi, or lkpi, has =0A= made it significantly easier to port and update our graphics drivers. =0A= Further, these new drivers cover the same drivers as the old drm2 driver.= =0A= =0A= What does the community think? Is there anyone still using the drm2 =0A= driver on 12-CURRENT? If so, what is preventing you from switching to =0A= the port?=0A= =0A= Thank you=0A= Regards=0A= -- =0A= Niclas Zeising=0A= FreeBSD x11/graphics team=0A= _______________________________________________=0A= freebsd-current@freebsd.org mailing list=0A= https://lists.freebsd.org/mailman/listinfo/freebsd-current=0A= To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"= =0A= From owner-freebsd-current@freebsd.org Fri May 18 19:14:36 2018 Return-Path: Delivered-To: freebsd-current@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 DABEEED613E; Fri, 18 May 2018 19:14:35 +0000 (UTC) (envelope-from andrnils@gmail.com) Received: from mail-lf0-x233.google.com (mail-lf0-x233.google.com [IPv6:2a00:1450:4010:c07::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3E9DA84DA9; Fri, 18 May 2018 19:14:35 +0000 (UTC) (envelope-from andrnils@gmail.com) Received: by mail-lf0-x233.google.com with SMTP id 16-v6so15464026lfs.13; Fri, 18 May 2018 12:14:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=8djXp2Ssf+gan03jycCxC7/Cspip8TLbvDIXGw4xurY=; b=Asr0j/MoVakBvVJTn4w6vFFXR+l1g3kMGmJ7ZXPLBWeLWz7PiqtoXUTTK9EI9ARQlQ bnWD2F4KcpWgT+0pq728SjPE28C4NoxXUlQrjtV7zC3PVbd12qndAEl9OoCNk8M9cJUf MaeJjuPXzNrSNCSLg6kTGj0HpmRJjbHzA7TBkhofsKdqNyNV1vp8Es4uCmL4qGEfqPQ1 OHVElbpTMR3uAXTkiS7ccx77pLDCdBJsG/e1lzDNoKqAc75um68k8u+TBpYVXyiE7DA5 Jc3HeRfRWwo/uXvNM+iZctk2qc5+Hw2WlywxzhxfX5FPcIOBrUhxIcvYD3PUysrNMjeD LW8Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=8djXp2Ssf+gan03jycCxC7/Cspip8TLbvDIXGw4xurY=; b=Ok6g0ESswCMyelcDUjc9Di747lx3yebXFO3XYqqM/Kkzfi0q2y6Rhoz0WyErOruS5+ nuufLfIdv3dlhPYVV1a1UCSfrXKUz7yFy8rK+jpEUTZpkVqCmTxzblM1C4WdeyDRmq3D gzWENwTnMKjNQiDYVaXMgewCwo6ZGdyyiLY7FfDuc1ifMuMqaD68S5BuuNLMu4Qfkvvv GfGnPDYyTVoic1zQ37m4IBRRG+rx4vZtkFxvQIXieQ5erEykPK4HlLAsQoFGjHdqG5XI opCqANooGf0jkHyL6F2+QbLtsHg7bjDLRiGjzyxidcMrIxlqZyHjWhxCdenF9083D0ck zAnA== X-Gm-Message-State: ALKqPwe2bhQBISe6XNeopT/jbe+2e2Ucmera5udGc5TSXV++erxZwwDZ Gij67IOhwTBw+E3GOrPaferhhHSvuldbCWx/Pfk= X-Google-Smtp-Source: AB8JxZrsicZuoPss0ZdJeXlvgxMpTnvzRlkLLhaocU+JkRsom2jxlSeolbp4Xje/hqROdPJqBZiiJ0fO0+etD0HXY6U= X-Received: by 2002:a2e:954b:: with SMTP id t11-v6mr6828090ljh.138.1526670873377; Fri, 18 May 2018 12:14:33 -0700 (PDT) MIME-Version: 1.0 References: <3a5edc5c-3caa-830b-4bd9-53ff52feb8a7@freebsd.org> In-Reply-To: <3a5edc5c-3caa-830b-4bd9-53ff52feb8a7@freebsd.org> From: Andreas Nilsson Date: Fri, 18 May 2018 21:14:24 +0200 Message-ID: Subject: Re: [RFC] Deprecation and removal of the drm2 driver To: FreeBSD X11 mailing list Cc: Current FreeBSD Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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 May 2018 19:14:36 -0000 On Fri, May 18, 2018, 20:00 Niclas Zeising wrote: > [ Cross posted to freebsd-current@ and freebsd-x11@. Please respect > reply-to and send all replies to freebsd-x11@. Thanks! ] > > > Hi! > I propose that we remove the old drm2 driver (sys/dev/drm2) from > FreeBSD. I suggest the driver is marked as deprecated in 11.x and > removed from 12.0, as was done for other drivers recently. Some > background and rationale: > > The drm2 driver was the original port of a KMS driver to FreeBSD. It > was done by Konstantin Belousov to support Intel graphics cards, and > later extended by Jean-S=C3=A9bastien P=C3=A9dron as well as Konstantin t= o match > what's in Linux 3.8. This included unstable support from Haswell, but > nothing newer than that. > > For quite some time now we have had the graphics/drm-stable-kmod and > graphics/drm-next-kmods which provides support for modern AMD and Intel > graphics cards. These ports, together with the linuxkpi, or lkpi, has > made it significantly easier to port and update our graphics drivers. > Further, these new drivers cover the same drivers as the old drm2 driver. > > What does the community think? Is there anyone still using the drm2 > driver on 12-CURRENT? If so, what is preventing you from switching to > the port? > > Thank you > Regards > -- > Niclas Zeising > FreeBSD x11/graphics team > _______________________________________________ > 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= " > Sounds good ( deprecate resp remove ). It causes more confusion and problems and it solves nothing. Best regards Andreas > From owner-freebsd-current@freebsd.org Fri May 18 19:30:17 2018 Return-Path: Delivered-To: freebsd-current@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 DFC9CED6CD4; Fri, 18 May 2018 19:30:17 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 5E56A85890; Fri, 18 May 2018 19:30:17 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.15.2/8.15.2) with ESMTPS id w4IJU9Xd088465 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 18 May 2018 12:30:09 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.15.2/8.15.2/Submit) id w4IJU9mq088464; Fri, 18 May 2018 12:30:09 -0700 (PDT) (envelope-from sgk) Date: Fri, 18 May 2018 12:30:09 -0700 From: Steve Kargl To: Andreas Nilsson Cc: FreeBSD X11 mailing list , Current FreeBSD Subject: Re: [RFC] Deprecation and removal of the drm2 driver Message-ID: <20180518193009.GA88432@troutmask.apl.washington.edu> Reply-To: sgk@troutmask.apl.washington.edu References: <3a5edc5c-3caa-830b-4bd9-53ff52feb8a7@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.9.2 (2017-12-15) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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 May 2018 19:30:18 -0000 On Fri, May 18, 2018 at 09:14:24PM +0200, Andreas Nilsson wrote: > On Fri, May 18, 2018, 20:00 Niclas Zeising wrote: > > > I propose that we remove the old drm2 driver (sys/dev/drm2) from > > FreeBSD. I suggest the driver is marked as deprecated in 11.x and > > removed from 12.0, as was done for other drivers recently. Some > > background and rationale: > > > > The drm2 driver was the original port of a KMS driver to FreeBSD. It > > was done by Konstantin Belousov to support Intel graphics cards, and > > later extended by Jean-Sébastien Pédron as well as Konstantin to match > > what's in Linux 3.8. This included unstable support from Haswell, but > > nothing newer than that. > > > > For quite some time now we have had the graphics/drm-stable-kmod and > > graphics/drm-next-kmods which provides support for modern AMD and Intel > > graphics cards. These ports, together with the linuxkpi, or lkpi, has > > made it significantly easier to port and update our graphics drivers. > > Further, these new drivers cover the same drivers as the old drm2 driver. > > > > What does the community think? Is there anyone still using the drm2 > > driver on 12-CURRENT? If so, what is preventing you from switching to > > the port? > > > > Thank you > > Regards > > -- > > Niclas Zeising > > FreeBSD x11/graphics team > > _______________________________________________ > > 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" > > > > Sounds good ( deprecate resp remove ). It causes more confusion and > problems and it solves nothing. > Check the Makefiles % more /usr/ports/graphics/drm-next-kmod/Makefile ONLY_FOR_ARCHS= amd64 ONLY_FOR_ARCHS_REASON= the new KMS components are only supported on amd64 Not to ia32 friendly. -- Steve 20170425 https://www.youtube.com/watch?v=VWUpyCsUKR4 20161221 https://www.youtube.com/watch?v=IbCHE-hONow From owner-freebsd-current@freebsd.org Fri May 18 20:03:35 2018 Return-Path: Delivered-To: freebsd-current@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 B88BDED9DBB for ; Fri, 18 May 2018 20:03:34 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x233.google.com (mail-it0-x233.google.com [IPv6:2607:f8b0:4001:c0b::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 31AD48729F for ; Fri, 18 May 2018 20:03:34 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x233.google.com with SMTP id 144-v6so14521313iti.5 for ; Fri, 18 May 2018 13:03:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=LccFgBqC6+J6WvRUo2jgdI/Gvs+XjlxmlEAxdyoGCzY=; b=ShVnDXpW1VKznnqlj97YtZz+RAtFrxv8f3KCrcafVRuQw8MJBE313ulx7xfhTHFJtN Kg49FKSjW8Tke9UUo9QJK43TtcGAxpQtpNbvN5Xk59kmuGPKOFZw8C46kmm8TNXksmms jpBYY58i5hkBUKuACXAboiuIe+qMQzbesGJACYsRRsW+h/pO1i6am4ZVf4xuuK98NxlZ EBnszYhcKMyKtyneCEVB/zjhvj7CV1tQ73PlLSh6ffo8s7XyO3XqPS38237sPYaAPGty XMMVVL46imTAW7SrJRFhaBgA7OpGfWKLxcGbe3NfySD20wpXTJMsXrqLnUYkQi4Jwyvb yhcg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=LccFgBqC6+J6WvRUo2jgdI/Gvs+XjlxmlEAxdyoGCzY=; b=HXd8fgpXdm9KapEULNfeQwEspdolFD3CcgUjjCV5QQEYRtRoPfQdzum8DGwimE4n8U +slKruyzgq4dfmWh2tV9YhEZgLA39F90bNgxG10jQuwAfvdRJH8yTG3O+8z+5VCEopZd yJf3hoBA7WbU4n966aEIHnqXxdiYBaxEd1vdmE/MQYgbcMwbPfL6pUGu4vGp3jEmYxAU p96lBxAFEj1/0rKAMKxxbV79P8BU4tCGJYb19V7Twed4JJFNk1JQnC/3r1uFT2t8CSFr a7JbDy/pMO19klHjlqevDrofBFTXfz+FxaQy1inMxhoZwqNdbjoum2P3VVHT2SPT/Z5c NOqQ== X-Gm-Message-State: ALKqPwdDIqmYNF76G6c+4dU7X97zM4B8vkN5czH73pn8x5/TYdYvwIzR BUh/OwvXMEI8f4dDQtnTCjy/+ejQgbZ+3O2sDrKJ6w== X-Google-Smtp-Source: AB8JxZrH27B3XExaum5jY3LPXqNmjOaY7VxpWhuEwps2KPAU2kKRI0rsAJzmAJHMtWYuNacxNbvdXO4SKpF9GMeQJYQ= X-Received: by 2002:a24:e983:: with SMTP id f125-v6mr8584126ith.36.1526673813188; Fri, 18 May 2018 13:03:33 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 2002:a4f:a649:0:0:0:0:0 with HTTP; Fri, 18 May 2018 13:03:32 -0700 (PDT) X-Originating-IP: [50.253.99.174] In-Reply-To: <20180518193009.GA88432@troutmask.apl.washington.edu> References: <3a5edc5c-3caa-830b-4bd9-53ff52feb8a7@freebsd.org> <20180518193009.GA88432@troutmask.apl.washington.edu> From: Warner Losh Date: Fri, 18 May 2018 14:03:32 -0600 X-Google-Sender-Auth: 5EzZISDx7vVRxb2c4xhue_wOPBo Message-ID: Subject: Re: [RFC] Deprecation and removal of the drm2 driver To: Steve Kargl Cc: Andreas Nilsson , FreeBSD X11 mailing list , Current FreeBSD Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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 May 2018 20:03:35 -0000 On Fri, May 18, 2018 at 1:30 PM, Steve Kargl < sgk@troutmask.apl.washington.edu> wrote: > On Fri, May 18, 2018 at 09:14:24PM +0200, Andreas Nilsson wrote: > > On Fri, May 18, 2018, 20:00 Niclas Zeising wrote: > > > > > I propose that we remove the old drm2 driver (sys/dev/drm2) from > > > FreeBSD. I suggest the driver is marked as deprecated in 11.x and > > > removed from 12.0, as was done for other drivers recently. Some > > > background and rationale: > > > > > > The drm2 driver was the original port of a KMS driver to FreeBSD. It > > > was done by Konstantin Belousov to support Intel graphics cards, and > > > later extended by Jean-S=C3=A9bastien P=C3=A9dron as well as Konstant= in to match > > > what's in Linux 3.8. This included unstable support from Haswell, bu= t > > > nothing newer than that. > > > > > > For quite some time now we have had the graphics/drm-stable-kmod and > > > graphics/drm-next-kmods which provides support for modern AMD and Int= el > > > graphics cards. These ports, together with the linuxkpi, or lkpi, ha= s > > > made it significantly easier to port and update our graphics drivers. > > > Further, these new drivers cover the same drivers as the old drm2 > driver. > > > > > > What does the community think? Is there anyone still using the drm2 > > > driver on 12-CURRENT? If so, what is preventing you from switching t= o > > > the port? > > > > > > Thank you > > > Regards > > > -- > > > Niclas Zeising > > > FreeBSD x11/graphics team > > > _______________________________________________ > > > 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" > > > > > > > Sounds good ( deprecate resp remove ). It causes more confusion and > > problems and it solves nothing. > > > > Check the Makefiles > > % more /usr/ports/graphics/drm-next-kmod/Makefile > > ONLY_FOR_ARCHS=3D amd64 > ONLY_FOR_ARCHS_REASON=3D the new KMS components are only supported on am= d64 > > Not to ia32 friendly. > So do people use i386 for desktop? And need the latest KMS stuff? Warner From owner-freebsd-current@freebsd.org Fri May 18 20:13:09 2018 Return-Path: Delivered-To: freebsd-current@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 56AC0EDA186; Fri, 18 May 2018 20:13:09 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-wr0-x229.google.com (mail-wr0-x229.google.com [IPv6:2a00:1450:400c:c0c::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BF56387833; Fri, 18 May 2018 20:13:08 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-wr0-x229.google.com with SMTP id 94-v6so10346797wrf.5; Fri, 18 May 2018 13:13:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=bJsz0ic8u7sg9NN6PK0OnTs99kF596cDXdqbXyfH/Q4=; b=bli82vnQYJfihJpRw6Qt9BTG+UQp/jcomrXio4EJ5NScvjfjTk93xYJXIonWGP4eih /GL+YTdqQGNO0iI3+OHdKhzA/MC0qRfstPvOx/EYnjALzh44CygsRDnbczYD/T3CIo13 Mz+KbvlZGqlOpZqhVsDR8+Gxu4KvkC3Xx/ntmRr4LUyDgYHus4GmgiwRG2l8P96n7e1h WHK9NQjm30JTB6ArFVVTPtCJPAngm65aC824aoZ02r1aF62Gtg7f5W83AdEMW7TXwhBf u8VZeTh7rgf87uwDL/B/JjfqK4mJ3JYwgH2eYwP3eb0+gCmxstAYKOTIaL/vZ/uuEcqE 7qLA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=bJsz0ic8u7sg9NN6PK0OnTs99kF596cDXdqbXyfH/Q4=; b=PeQiZnxtJ/kvf25TPjmgzxZXM6ifmUAedHZRhjBxXlXUeFIJ1v7yyjUyxNWMrbH/Q+ e9NfOkwJSeyGmQdoPAWhVQCPirNRvn/DhBYAvrHe2GePAVEIRg9YqeUV7hYMkins+9nu hu7P5LiEH/ekKOcI/tRsfac1AJb2KW3fQ7mUk717io9U7kiMBUNc2j+Fr2+7DHgHFxce anB+GI8egKhdydPJ+Nc4DY6EvgrWaqfzxZIgks87u4MEVoHhWAjlN4Hu7DAbuvXtUyOV X9YnGrZZJYqSQNbBjUOKtQKNrwPO0zZs7XcHjycJMr8lcGj3cU78semZUev7yjXCtaiL zE1g== X-Gm-Message-State: ALKqPwdME0re8lVlEhgB3tgle8I3Sz5sVUaOHw8UlXPumgZBUGd/j/MQ 1BZ1uiNg9GruGaGyOMBmcf9Z9Vgp9yv9TzcpUbo= X-Google-Smtp-Source: AB8JxZqsQPJjiP3nP+lf7DhNyEZ9VfRrU8+P8jezuQfHlwbE1H2rwnjv1bHrhLa83Yeq5qIxWnvjM1iW8jgJdfk2p5w= X-Received: by 2002:adf:f74c:: with SMTP id z12-v6mr3625283wrp.165.1526674387054; Fri, 18 May 2018 13:13:07 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.146.194 with HTTP; Fri, 18 May 2018 13:12:26 -0700 (PDT) In-Reply-To: References: <3a5edc5c-3caa-830b-4bd9-53ff52feb8a7@freebsd.org> <20180518193009.GA88432@troutmask.apl.washington.edu> From: Johannes Lundberg Date: Fri, 18 May 2018 21:12:26 +0100 Message-ID: Subject: Re: [RFC] Deprecation and removal of the drm2 driver To: Warner Losh Cc: Steve Kargl , Andreas Nilsson , FreeBSD X11 mailing list , Current FreeBSD Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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 May 2018 20:13:09 -0000 On Fri, May 18, 2018 at 9:03 PM, Warner Losh wrote: > On Fri, May 18, 2018 at 1:30 PM, Steve Kargl < > sgk@troutmask.apl.washington.edu> wrote: > > > On Fri, May 18, 2018 at 09:14:24PM +0200, Andreas Nilsson wrote: > > > On Fri, May 18, 2018, 20:00 Niclas Zeising > wrote: > > > > > > > I propose that we remove the old drm2 driver (sys/dev/drm2) from > > > > FreeBSD. I suggest the driver is marked as deprecated in 11.x and > > > > removed from 12.0, as was done for other drivers recently. Some > > > > background and rationale: > > > > > > > > The drm2 driver was the original port of a KMS driver to FreeBSD. = It > > > > was done by Konstantin Belousov to support Intel graphics cards, an= d > > > > later extended by Jean-S=C3=A9bastien P=C3=A9dron as well as Konsta= ntin to > match > > > > what's in Linux 3.8. This included unstable support from Haswell, > but > > > > nothing newer than that. > > > > > > > > For quite some time now we have had the graphics/drm-stable-kmod an= d > > > > graphics/drm-next-kmods which provides support for modern AMD and > Intel > > > > graphics cards. These ports, together with the linuxkpi, or lkpi, > has > > > > made it significantly easier to port and update our graphics driver= s. > > > > Further, these new drivers cover the same drivers as the old drm2 > > driver. > > > > > > > > What does the community think? Is there anyone still using the drm= 2 > > > > driver on 12-CURRENT? If so, what is preventing you from switching > to > > > > the port? > > > > > > > > Thank you > > > > Regards > > > > -- > > > > Niclas Zeising > > > > FreeBSD x11/graphics team > > > > _______________________________________________ > > > > 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" > > > > > > > > > > Sounds good ( deprecate resp remove ). It causes more confusion and > > > problems and it solves nothing. > > > > > > > Check the Makefiles > > > > % more /usr/ports/graphics/drm-next-kmod/Makefile > > > > ONLY_FOR_ARCHS=3D amd64 > > ONLY_FOR_ARCHS_REASON=3D the new KMS components are only supported on > amd64 > > > > Not to ia32 friendly. > > > > So do people use i386 for desktop? And need the latest KMS stuff? > Yeah I was wondering the same.. If you're running i386, do you need drm drivers? Will scfb work an i386? (probably has legacy bios and if I remember correctly, scfb is UEFI only) I do feel sorry for anyone who would have to revert back to VESA... Would it be too much trouble to move it to a port? > > Warner > _______________________________________________ > 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= " > From owner-freebsd-current@freebsd.org Fri May 18 20:15:05 2018 Return-Path: Delivered-To: freebsd-current@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 5DE55EDA2DF for ; Fri, 18 May 2018 20:15:05 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x236.google.com (mail-it0-x236.google.com [IPv6:2607:f8b0:4001:c0b::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E19AE87AD5 for ; Fri, 18 May 2018 20:15:04 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x236.google.com with SMTP id c5-v6so3418956itj.1 for ; Fri, 18 May 2018 13:15:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=XmM2w7NU5apdjBMXblrsT46qmZSVuBRJAN7w6CRvANQ=; b=w0GBnHnNPEMTBeTnS0FjHpv0QBWr/ygo1LBax8qr9k4p+/WdJIHpTj0CHa0eIjZBQv QIb/+VaqfmpJDXdP2K8ZO3WdU0E/2drOJa+NgEDHKeB5F4ax5nGPVaUdtcuSytdaOjwk QO+URuAguxcCQNZ1llWE5X1RWp8K20/pLGF/RBItRWZvK38MPyfcbG1nwF1lT88CjR0g NhIRUjwDzXggYNN1cSWcOnS67iQGFFo+NNdegkv/tfaBsdu4S7mK8gryIe8H/WqIOtON ci8XOOgUkbQULBnIb+42MAoqm34uXaqZYhTTynM1ChCYaV7ZCyY4PbKycHLtoDpl0zvf squQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=XmM2w7NU5apdjBMXblrsT46qmZSVuBRJAN7w6CRvANQ=; b=X91Lv1yXLXnckKdrt5V3CpJSGSxSjqcI+pDwdkprOJGIND8abqxskbhHNY0sf72nlK VrH8GiIRHoGpyLulcj6iP8/n8xrAv4oHHjHhsiYb9Lv4Z6pPXuyOQRxcKxV4IPoyUU3h pjOFgtKA70ofgMrr/8OywYEWMamyPUZOo/cbMrrsOXstyZDp10cum6Y9BZXzSjIvyNCY QZzaqHzUuji9UJaUnM5rvYj/p9Z/th0K/8+Dl2yH9WSkIFlvPvbPMNHvNAcsxtcLHyEm dXHvLTfhOzOBQ44wGJGFDIhiMIXD0clYcXQ2+36Kw3uOF7WNsJ5Q9NaueOLyvVwzMpD8 TcKg== X-Gm-Message-State: ALKqPwdaDpcs98xNy68w8yYapYvdqfN/et1anaFzzMIL7kc05hk27+Py Z8QUxNi3SW23v4DbgqWadzqByL6bOY1P9obdoxbgpQ== X-Google-Smtp-Source: AB8JxZrr4Q2/ZvbONs/3smyzDHqE+N9mEwut0xRonLEw4hE7TeyDE+wNPbTDgBJSP8bS9TPObLFz2yhnHJM44Le7a0g= X-Received: by 2002:a24:6ec1:: with SMTP id w184-v6mr8255645itc.57.1526674504030; Fri, 18 May 2018 13:15:04 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 2002:a4f:a649:0:0:0:0:0 with HTTP; Fri, 18 May 2018 13:15:03 -0700 (PDT) X-Originating-IP: [50.253.99.174] In-Reply-To: References: <3a5edc5c-3caa-830b-4bd9-53ff52feb8a7@freebsd.org> <20180518193009.GA88432@troutmask.apl.washington.edu> From: Warner Losh Date: Fri, 18 May 2018 14:15:03 -0600 X-Google-Sender-Auth: N-jzcsq-0OflMXWhV4tIabisjak Message-ID: Subject: Re: [RFC] Deprecation and removal of the drm2 driver To: Johannes Lundberg Cc: Steve Kargl , Andreas Nilsson , FreeBSD X11 mailing list , Current FreeBSD Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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 May 2018 20:15:05 -0000 On Fri, May 18, 2018 at 2:12 PM, Johannes Lundberg wrote: > > > On Fri, May 18, 2018 at 9:03 PM, Warner Losh wrote: > >> On Fri, May 18, 2018 at 1:30 PM, Steve Kargl < >> sgk@troutmask.apl.washington.edu> wrote: >> >> > On Fri, May 18, 2018 at 09:14:24PM +0200, Andreas Nilsson wrote: >> > > On Fri, May 18, 2018, 20:00 Niclas Zeising >> wrote: >> > > >> > > > I propose that we remove the old drm2 driver (sys/dev/drm2) from >> > > > FreeBSD. I suggest the driver is marked as deprecated in 11.x and >> > > > removed from 12.0, as was done for other drivers recently. Some >> > > > background and rationale: >> > > > >> > > > The drm2 driver was the original port of a KMS driver to FreeBSD. >> It >> > > > was done by Konstantin Belousov to support Intel graphics cards, a= nd >> > > > later extended by Jean-S=C3=A9bastien P=C3=A9dron as well as Konst= antin to >> match >> > > > what's in Linux 3.8. This included unstable support from Haswell, >> but >> > > > nothing newer than that. >> > > > >> > > > For quite some time now we have had the graphics/drm-stable-kmod a= nd >> > > > graphics/drm-next-kmods which provides support for modern AMD and >> Intel >> > > > graphics cards. These ports, together with the linuxkpi, or lkpi, >> has >> > > > made it significantly easier to port and update our graphics >> drivers. >> > > > Further, these new drivers cover the same drivers as the old drm2 >> > driver. >> > > > >> > > > What does the community think? Is there anyone still using the dr= m2 >> > > > driver on 12-CURRENT? If so, what is preventing you from switchin= g >> to >> > > > the port? >> > > > >> > > > Thank you >> > > > Regards >> > > > -- >> > > > Niclas Zeising >> > > > FreeBSD x11/graphics team >> > > > _______________________________________________ >> > > > 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" >> > > > >> > > >> > > Sounds good ( deprecate resp remove ). It causes more confusion and >> > > problems and it solves nothing. >> > > >> > >> > Check the Makefiles >> > >> > % more /usr/ports/graphics/drm-next-kmod/Makefile >> > >> > ONLY_FOR_ARCHS=3D amd64 >> > ONLY_FOR_ARCHS_REASON=3D the new KMS components are only supported on >> amd64 >> > >> > Not to ia32 friendly. >> > >> >> So do people use i386 for desktop? And need the latest KMS stuff? >> > > Yeah I was wondering the same.. If you're running i386, do you need drm > drivers? Will scfb work an i386? (probably has legacy bios and if I > remember correctly, scfb is UEFI only) > I do feel sorry for anyone who would have to revert back to VESA... > > Would it be too much trouble to move it to a port? > If there's someone who needs it for i386, and wants to do the work and maintain it, we should allow it. But the drm2 maintainers have said its likely totally broken anyway. Warner From owner-freebsd-current@freebsd.org Fri May 18 20:19:29 2018 Return-Path: Delivered-To: freebsd-current@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 2899CEDA664; Fri, 18 May 2018 20:19:29 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.netplex.net (mail.netplex.net [204.213.176.9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.netplex.net", Issuer "RapidSSL RSA CA 2018" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C968887DB6; Fri, 18 May 2018 20:19:28 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.netplex.net (8.15.1/8.15.1/NETPLEX) with ESMTP id w4IKJLeH000517; Fri, 18 May 2018 16:19:21 -0400 X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.netplex.net) X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-4.4.3 (mail.netplex.net [204.213.176.9]); Fri, 18 May 2018 16:19:21 -0400 (EDT) Date: Fri, 18 May 2018 16:19:21 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net Reply-To: Daniel Eischen To: Warner Losh cc: Steve Kargl , Andreas Nilsson , FreeBSD X11 mailing list , Current FreeBSD Subject: Re: [RFC] Deprecation and removal of the drm2 driver In-Reply-To: Message-ID: References: <3a5edc5c-3caa-830b-4bd9-53ff52feb8a7@freebsd.org> <20180518193009.GA88432@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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 May 2018 20:19:29 -0000 On Fri, 18 May 2018, Warner Losh wrote: > On Fri, May 18, 2018 at 1:30 PM, Steve Kargl < > sgk@troutmask.apl.washington.edu> wrote: >> >> Check the Makefiles >> >> % more /usr/ports/graphics/drm-next-kmod/Makefile >> >> ONLY_FOR_ARCHS= amd64 >> ONLY_FOR_ARCHS_REASON= the new KMS components are only supported on amd64 >> >> Not to ia32 friendly. >> > > So do people use i386 for desktop? And need the latest KMS stuff? I can easily imagine an embedded x86 kiosk type appliance. Does basic xorg stuff work without drm? -- DE From owner-freebsd-current@freebsd.org Fri May 18 20:23:13 2018 Return-Path: Delivered-To: freebsd-current@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 A1378EDAA68; Fri, 18 May 2018 20:23:13 +0000 (UTC) (envelope-from benjamin.widawsky@intel.com) Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "fmsmga105.fm.intel.com", Issuer "COMODO RSA Organization Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 17FEA6837D; Fri, 18 May 2018 20:23:12 +0000 (UTC) (envelope-from benjamin.widawsky@intel.com) X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga105.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 18 May 2018 13:22:01 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.49,415,1520924400"; d="scan'208";a="47792449" Received: from gmoli3-mobl.amr.corp.intel.com (HELO localhost) ([10.252.128.225]) by fmsmga002.fm.intel.com with ESMTP; 18 May 2018 13:22:01 -0700 Date: Fri, 18 May 2018 13:22:01 -0700 From: Ben Widawsky To: Warner Losh Cc: Johannes Lundberg , Steve Kargl , Andreas Nilsson , FreeBSD X11 mailing list , Current FreeBSD Subject: Re: [RFC] Deprecation and removal of the drm2 driver Message-ID: <20180518202200.dks3twrlfyhmcgbb@mail.bwidawsk.net> References: <3a5edc5c-3caa-830b-4bd9-53ff52feb8a7@freebsd.org> <20180518193009.GA88432@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: NeoMutt/20180323 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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 May 2018 20:23:13 -0000 On 18-05-18 14:15:03, Warner Losh wrote: > On Fri, May 18, 2018 at 2:12 PM, Johannes Lundberg > wrote: > > > > > > > On Fri, May 18, 2018 at 9:03 PM, Warner Losh wrote: > > > >> On Fri, May 18, 2018 at 1:30 PM, Steve Kargl < > >> sgk@troutmask.apl.washington.edu> wrote: > >> > >> > On Fri, May 18, 2018 at 09:14:24PM +0200, Andreas Nilsson wrote: > >> > > On Fri, May 18, 2018, 20:00 Niclas Zeising > >> wrote: > >> > > > >> > > > I propose that we remove the old drm2 driver (sys/dev/drm2) from > >> > > > FreeBSD. I suggest the driver is marked as deprecated in 11.x and > >> > > > removed from 12.0, as was done for other drivers recently. Some > >> > > > background and rationale: > >> > > > > >> > > > The drm2 driver was the original port of a KMS driver to FreeBSD. > >> It > >> > > > was done by Konstantin Belousov to support Intel graphics cards, and > >> > > > later extended by Jean-Sébastien Pédron as well as Konstantin to > >> match > >> > > > what's in Linux 3.8. This included unstable support from Haswell, > >> but > >> > > > nothing newer than that. > >> > > > > >> > > > For quite some time now we have had the graphics/drm-stable-kmod and > >> > > > graphics/drm-next-kmods which provides support for modern AMD and > >> Intel > >> > > > graphics cards. These ports, together with the linuxkpi, or lkpi, > >> has > >> > > > made it significantly easier to port and update our graphics > >> drivers. > >> > > > Further, these new drivers cover the same drivers as the old drm2 > >> > driver. > >> > > > > >> > > > What does the community think? Is there anyone still using the drm2 > >> > > > driver on 12-CURRENT? If so, what is preventing you from switching > >> to > >> > > > the port? > >> > > > > >> > > > Thank you > >> > > > Regards > >> > > > -- > >> > > > Niclas Zeising > >> > > > FreeBSD x11/graphics team > >> > > > _______________________________________________ > >> > > > 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" > >> > > > > >> > > > >> > > Sounds good ( deprecate resp remove ). It causes more confusion and > >> > > problems and it solves nothing. > >> > > > >> > > >> > Check the Makefiles > >> > > >> > % more /usr/ports/graphics/drm-next-kmod/Makefile > >> > > >> > ONLY_FOR_ARCHS= amd64 > >> > ONLY_FOR_ARCHS_REASON= the new KMS components are only supported on > >> amd64 > >> > > >> > Not to ia32 friendly. > >> > > >> > >> So do people use i386 for desktop? And need the latest KMS stuff? > >> > > > > Yeah I was wondering the same.. If you're running i386, do you need drm > > drivers? Will scfb work an i386? (probably has legacy bios and if I > > remember correctly, scfb is UEFI only) > > I do feel sorry for anyone who would have to revert back to VESA... > > > > Would it be too much trouble to move it to a port? > > > > If there's someone who needs it for i386, and wants to do the work and > maintain it, we should allow it. But the drm2 maintainers have said its > likely totally broken anyway. > > Warner As a long time developer in drm/i915, and newly interested in FreeBSD (ie. no history on the matter), is there some upside and/or desire to have native support, or is the drm-next-kmod solution good enough? From owner-freebsd-current@freebsd.org Fri May 18 20:24:04 2018 Return-Path: Delivered-To: freebsd-current@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 5512BEDAB0A for ; Fri, 18 May 2018 20:24:04 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x236.google.com (mail-io0-x236.google.com [IPv6:2607:f8b0:4001:c06::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D47D868425 for ; Fri, 18 May 2018 20:24:03 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x236.google.com with SMTP id z4-v6so7657689iof.5 for ; Fri, 18 May 2018 13:24:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=sSaeiabjN7z3rHXnVuX9Qhdth3qSvFymrDa5ZSJLZJw=; b=Upb2ltkdp9PzVHN9MhRDdot8fy1I5o19hWJCdPyHo006lrG2vGR348yMaD/s1Hn9/4 W4yM+jqMlH96B9hnEmxuSOVxOSSoXtfZycq2TxI8755prhvPTjb9O1PqFAxgkYMGMtXn 2AMXFal0tTnlS47pGbqOfqPGNAAfvJ9l742ZjfYdSiX/tZRxRdgEUY2bxMJFTM+BdGKS Do713GEw3m1K5Xwq5b8lDbStu0N9PaIZOan685SVs2RZWJ8o2llmjTK7T3xcjDUYcTeG G8LK4FSEJ/V7W+eAOJ34nb898za3XsvUFjghvmHi9wQmO08z1wy++JC8QfptOPeCUlhc H+XQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=sSaeiabjN7z3rHXnVuX9Qhdth3qSvFymrDa5ZSJLZJw=; b=jAXK6NDtEN5U6BvJcvzGuRAU4+Xi/UA2j5WOBQrsFOsP/lLo8zShUocHrarx+oF3cI DWjbeKnFtAuWw3YWOU7irh51WNSWdY3GYR6FIDZQk11smV0Y3UBJ+vnX5puTK2z06l0O qDSzNM2lytpbdq2ddNr9z2eIVBgB3tUUvF/cFUxtOdy8Tv9V2uAwdBzoXdlRbAXnGhKV r9j3aYvHpiD8N74Zc725SqSbcymZe4e3TAZOE2jiagLrgfVblZA500zlWOrXJuQ5Diol fM1XJJgkJImIuZiTzOxwXIOR3Pk4DEvUEJ1flmhAvkqg7nOqsL6+iq/lzoIHWlcQpRSR PF7A== X-Gm-Message-State: ALKqPwf5xx4t00k+GotBt8zCSEQ7NWQ33VrnQoswXrHSX5iwHu9ufBKo SAyecnBCpZslDNbaRhgVVUS6QHc9dQRkNJdCCDilag== X-Google-Smtp-Source: AB8JxZoKWe+jDXsBOObgtmLn7IWddyZDtsA8NfUDhsYe2xUbUoggRH8SkhiRK4Y2o7yiPXHufPuoONZv7UPeBsSp7VE= X-Received: by 2002:a6b:be01:: with SMTP id o1-v6mr11522778iof.299.1526675043200; Fri, 18 May 2018 13:24:03 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 2002:a4f:a649:0:0:0:0:0 with HTTP; Fri, 18 May 2018 13:24:02 -0700 (PDT) X-Originating-IP: [50.253.99.174] In-Reply-To: References: <3a5edc5c-3caa-830b-4bd9-53ff52feb8a7@freebsd.org> <20180518193009.GA88432@troutmask.apl.washington.edu> From: Warner Losh Date: Fri, 18 May 2018 14:24:02 -0600 X-Google-Sender-Auth: WLsB_3DzB5s1UEyL9Sq3dOWp-m0 Message-ID: Subject: Re: [RFC] Deprecation and removal of the drm2 driver To: Daniel Eischen Cc: Steve Kargl , Andreas Nilsson , FreeBSD X11 mailing list , Current FreeBSD Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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 May 2018 20:24:04 -0000 On Fri, May 18, 2018 at 2:19 PM, Daniel Eischen wrote: > On Fri, 18 May 2018, Warner Losh wrote: > > On Fri, May 18, 2018 at 1:30 PM, Steve Kargl < >> sgk@troutmask.apl.washington.edu> wrote: >> >>> >>> Check the Makefiles >>> >>> % more /usr/ports/graphics/drm-next-kmod/Makefile >>> >>> ONLY_FOR_ARCHS= amd64 >>> ONLY_FOR_ARCHS_REASON= the new KMS components are only supported on >>> amd64 >>> >>> Not to ia32 friendly. >>> >>> >> So do people use i386 for desktop? And need the latest KMS stuff? >> > > I can easily imagine an embedded x86 kiosk type appliance. Does > basic xorg stuff work without drm? They'd be running current on such boxes? I'm asking if we have any known users. The crux of the problem is that it's hard to get any graphics support from Intel. What little support we get from them is amd64 only. And what little resources we have do support graphics is 64-bit only. There's nobody doing the work for i386, and we're not able to snag it from upstream either. So it boils down to the question of allowing old, obsolete hardware, which nobody's sure works anyway, to get in the way of moving forward to more modern hardware? I'm trying to find value from supporting i386, and a community willing to do that work and I'm not seeing much of either. Warner From owner-freebsd-current@freebsd.org Fri May 18 20:28:43 2018 Return-Path: Delivered-To: freebsd-current@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 636C3EDAEA8; Fri, 18 May 2018 20:28:43 +0000 (UTC) (envelope-from ben@bwidawsk.net) Received: from mga18.intel.com (mga18.intel.com [134.134.136.126]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "orsmga106.jf.intel.com", Issuer "COMODO RSA Organization Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CCEA7688A4; Fri, 18 May 2018 20:28:42 +0000 (UTC) (envelope-from ben@bwidawsk.net) X-Amp-Result: UNSCANNABLE X-Amp-File-Uploaded: False Received: from orsmga005.jf.intel.com ([10.7.209.41]) by orsmga106.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 18 May 2018 13:27:31 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.49,415,1520924400"; d="scan'208";a="225431872" Received: from gmoli3-mobl.amr.corp.intel.com (HELO mail.bwidawsk.net) ([10.252.128.225]) by orsmga005.jf.intel.com with ESMTP; 18 May 2018 13:27:31 -0700 Date: Fri, 18 May 2018 13:27:31 -0700 From: Ben Widawsky To: Warner Losh Cc: Johannes Lundberg , Steve Kargl , Andreas Nilsson , FreeBSD X11 mailing list , Current FreeBSD Subject: Re: [RFC] Deprecation and removal of the drm2 driver Message-ID: <20180518202730.ldhhe3ekdcgncyaw@mail.bwidawsk.net> References: <3a5edc5c-3caa-830b-4bd9-53ff52feb8a7@freebsd.org> <20180518193009.GA88432@troutmask.apl.washington.edu> <20180518202200.dks3twrlfyhmcgbb@mail.bwidawsk.net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20180518202200.dks3twrlfyhmcgbb@mail.bwidawsk.net> User-Agent: NeoMutt/20180323 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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 May 2018 20:28:43 -0000 On 18-05-18 13:22:01, Ben Widawsky wrote: > On 18-05-18 14:15:03, Warner Losh wrote: > > On Fri, May 18, 2018 at 2:12 PM, Johannes Lundberg > > wrote: > > > > > > > > > > > On Fri, May 18, 2018 at 9:03 PM, Warner Losh wrote: > > > > > >> On Fri, May 18, 2018 at 1:30 PM, Steve Kargl < > > >> sgk@troutmask.apl.washington.edu> wrote: > > >> > > >> > On Fri, May 18, 2018 at 09:14:24PM +0200, Andreas Nilsson wrote: > > >> > > On Fri, May 18, 2018, 20:00 Niclas Zeising > > >> wrote: > > >> > > > > >> > > > I propose that we remove the old drm2 driver (sys/dev/drm2) from > > >> > > > FreeBSD. I suggest the driver is marked as deprecated in 11.x and > > >> > > > removed from 12.0, as was done for other drivers recently. Some > > >> > > > background and rationale: > > >> > > > > > >> > > > The drm2 driver was the original port of a KMS driver to FreeBSD. > > >> It > > >> > > > was done by Konstantin Belousov to support Intel graphics cards, and > > >> > > > later extended by Jean-Sébastien Pédron as well as Konstantin to > > >> match > > >> > > > what's in Linux 3.8. This included unstable support from Haswell, > > >> but > > >> > > > nothing newer than that. > > >> > > > > > >> > > > For quite some time now we have had the graphics/drm-stable-kmod and > > >> > > > graphics/drm-next-kmods which provides support for modern AMD and > > >> Intel > > >> > > > graphics cards. These ports, together with the linuxkpi, or lkpi, > > >> has > > >> > > > made it significantly easier to port and update our graphics > > >> drivers. > > >> > > > Further, these new drivers cover the same drivers as the old drm2 > > >> > driver. > > >> > > > > > >> > > > What does the community think? Is there anyone still using the drm2 > > >> > > > driver on 12-CURRENT? If so, what is preventing you from switching > > >> to > > >> > > > the port? > > >> > > > > > >> > > > Thank you > > >> > > > Regards > > >> > > > -- > > >> > > > Niclas Zeising > > >> > > > FreeBSD x11/graphics team > > >> > > > _______________________________________________ > > >> > > > 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" > > >> > > > > > >> > > > > >> > > Sounds good ( deprecate resp remove ). It causes more confusion and > > >> > > problems and it solves nothing. > > >> > > > > >> > > > >> > Check the Makefiles > > >> > > > >> > % more /usr/ports/graphics/drm-next-kmod/Makefile > > >> > > > >> > ONLY_FOR_ARCHS= amd64 > > >> > ONLY_FOR_ARCHS_REASON= the new KMS components are only supported on > > >> amd64 > > >> > > > >> > Not to ia32 friendly. > > >> > > > >> > > >> So do people use i386 for desktop? And need the latest KMS stuff? > > >> > > > > > > Yeah I was wondering the same.. If you're running i386, do you need drm > > > drivers? Will scfb work an i386? (probably has legacy bios and if I > > > remember correctly, scfb is UEFI only) > > > I do feel sorry for anyone who would have to revert back to VESA... > > > > > > Would it be too much trouble to move it to a port? > > > > > > > If there's someone who needs it for i386, and wants to do the work and > > maintain it, we should allow it. But the drm2 maintainers have said its > > likely totally broken anyway. > > > > Warner > > As a long time developer in drm/i915, and newly interested in FreeBSD (ie. no > history on the matter), is there some upside and/or desire to have native > support, or is the drm-next-kmod solution good enough? Aside from lack of 32b support... -- Ben Widawsky, Intel Open Source Technology Center From owner-freebsd-current@freebsd.org Fri May 18 20:30:28 2018 Return-Path: Delivered-To: freebsd-current@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 A71A7EDB24F; Fri, 18 May 2018 20:30:28 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from smtp-out-so.shaw.ca (smtp-out-so.shaw.ca [64.59.136.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 27A9868B4E; Fri, 18 May 2018 20:30:27 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from spqr.komquats.com ([70.67.125.17]) by shaw.ca with ESMTPA id Jm14fsyYTSzNNJm15fjQ1W; Fri, 18 May 2018 14:30:20 -0600 X-Authority-Analysis: v=2.3 cv=KuxjJ1eN c=1 sm=1 tr=0 a=VFtTW3WuZNDh6VkGe7fA3g==:117 a=VFtTW3WuZNDh6VkGe7fA3g==:17 a=8nJEP1OIZ-IA:10 a=VUJBJC2UJ8kA:10 a=xfDLHkLGAAAA:8 a=pGLkceISAAAA:8 a=7Qk2ozbKAAAA:8 a=6I5d2MoRAAAA:8 a=YxBL1-UpAAAA:8 a=ezmmrFSbtsYoodHyYowA:9 a=wPNLvfGTeEIA:10 a=IfaqVvZgccqrtc8gcwf2:22 a=1lyxoWkJIXJV6VJUPhuM:22 a=IjZwj45LgO3ly-622nXo:22 a=Ia-lj3WSrqcvXOmTRaiG:22 Received: from slippy.cwsent.com (slippy [10.1.1.91]) by spqr.komquats.com (Postfix) with ESMTPS id E1631CBF; Fri, 18 May 2018 13:30:17 -0700 (PDT) Received: from slippy.cwsent.com (localhost [127.0.0.1]) by slippy.cwsent.com (8.15.2/8.15.2) with ESMTP id w4IKUHHc032592; Fri, 18 May 2018 13:30:17 -0700 (PDT) (envelope-from Cy.Schubert@cschubert.com) Received: from slippy (cy@localhost) by slippy.cwsent.com (8.15.2/8.15.2/Submit) with ESMTP id w4IKUHa3032589; Fri, 18 May 2018 13:30:17 -0700 (PDT) (envelope-from Cy.Schubert@cschubert.com) Message-Id: <201805182030.w4IKUHa3032589@slippy.cwsent.com> X-Authentication-Warning: slippy.cwsent.com: cy owned process doing -bs X-Mailer: exmh version 2.8.0 04/21/2012 with nmh-1.7.1 Reply-to: Cy Schubert From: Cy Schubert X-os: FreeBSD X-Sender: cy@cwsent.com X-URL: http://www.cschubert.com/ To: Warner Losh cc: Johannes Lundberg , FreeBSD X11 mailing list , Current FreeBSD , Steve Kargl Subject: Re: [RFC] Deprecation and removal of the drm2 driver In-Reply-To: Message from Warner Losh of "Fri, 18 May 2018 14:15:03 -0600." Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Date: Fri, 18 May 2018 13:30:17 -0700 X-CMAE-Envelope: MS4wfPVw4v3slBC3yFcY1PmtlEn9vwpJQXLzoyuXPCoxUhYlEYs6Shn8bYxwJWFDubQjftfgLr4J5jzLc1FHGE2cTXOFXHXYnwW359W5BgX9iPxB/9dNv4sO iAaVuHa0Sn6x1aFgeZiRQtddH/xiH84PQVOSi0abA4FGPuNsX9AaZu/KYoDso2t5sUnKYT+i957pfwFtBJ/S7cuc+vwZwPycasDX8JGuNPKMTbu4X+Pg/0Ar qPVWzBKyP55eZqbfkPaNsdWn9IrM2DtWfFZQRBR1+U8+s4pAYOYbpjGTVcXlkepzQQsx9gUmPIqjgztCXqbybOp5/0uA+Lyny+JBCbqLLcp5JYBqbgoI6ON8 KD+jGajj/S8pNexAWsMFXnPaoyfVv8AU4PoSziUwinOqKI+jxqo= X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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 May 2018 20:30:29 -0000 In message , Warner Losh writes: > On Fri, May 18, 2018 at 2:12 PM, Johannes Lundberg > wrote: > > > > > > > On Fri, May 18, 2018 at 9:03 PM, Warner Losh wrote: > > > >> On Fri, May 18, 2018 at 1:30 PM, Steve Kargl < > >> sgk@troutmask.apl.washington.edu> wrote: > >> > >> > On Fri, May 18, 2018 at 09:14:24PM +0200, Andreas Nilsson wrote: > >> > > On Fri, May 18, 2018, 20:00 Niclas Zeising > >> wrote: > >> > > > >> > > > I propose that we remove the old drm2 driver (sys/dev/drm2) from > >> > > > FreeBSD. I suggest the driver is marked as deprecated in 11.x and > >> > > > removed from 12.0, as was done for other drivers recently. Some > >> > > > background and rationale: > >> > > > > >> > > > The drm2 driver was the original port of a KMS driver to FreeBSD. > >> It > >> > > > was done by Konstantin Belousov to support Intel graphics cards, and > >> > > > later extended by Jean-Sébastien Pédron as well as Konstantin to > >> match > >> > > > what's in Linux 3.8. This included unstable support from Haswell, > >> but > >> > > > nothing newer than that. > >> > > > > >> > > > For quite some time now we have had the graphics/drm-stable-kmod and > >> > > > graphics/drm-next-kmods which provides support for modern AMD and > >> Intel > >> > > > graphics cards. These ports, together with the linuxkpi, or lkpi, > >> has > >> > > > made it significantly easier to port and update our graphics > >> drivers. > >> > > > Further, these new drivers cover the same drivers as the old drm2 > >> > driver. > >> > > > > >> > > > What does the community think? Is there anyone still using the drm2 > >> > > > driver on 12-CURRENT? If so, what is preventing you from switching > >> to > >> > > > the port? > >> > > > > >> > > > Thank you > >> > > > Regards > >> > > > -- > >> > > > Niclas Zeising > >> > > > FreeBSD x11/graphics team > >> > > > _______________________________________________ > >> > > > 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" > >> > > > > >> > > > >> > > Sounds good ( deprecate resp remove ). It causes more confusion and > >> > > problems and it solves nothing. > >> > > > >> > > >> > Check the Makefiles > >> > > >> > % more /usr/ports/graphics/drm-next-kmod/Makefile > >> > > >> > ONLY_FOR_ARCHS= amd64 > >> > ONLY_FOR_ARCHS_REASON= the new KMS components are only supported on > >> amd64 > >> > > >> > Not to ia32 friendly. > >> > > >> > >> So do people use i386 for desktop? And need the latest KMS stuff? > >> > > > > Yeah I was wondering the same.. If you're running i386, do you need drm > > drivers? Will scfb work an i386? (probably has legacy bios and if I > > remember correctly, scfb is UEFI only) > > I do feel sorry for anyone who would have to revert back to VESA... > > > > Would it be too much trouble to move it to a port? > > > > If there's someone who needs it for i386, and wants to do the work and > maintain it, we should allow it. But the drm2 maintainers have said its > likely totally broken anyway. Many Linux distros don't even support i386 any more. RHEL 5 was the last for Red Hat (though Fedora still does). In all fairness, we will need to bite the bullet one day too. Not suggesting anything but we should start thinking about 32-bit and planning for it (& 2038). I still have one i386 (the rest being amd64). VESA does suck on a 1280x768 monitor. The 915resolution port stopped working on it long ago. I'm not saying keep it just for this one machine, this is just a data point to the discussion. I'm also not saying to deprecate i386 now, however we should start planning for the eventuality. Maybe FreeBSD 14, 16 or beyond. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few. From owner-freebsd-current@freebsd.org Fri May 18 20:34:22 2018 Return-Path: Delivered-To: freebsd-current@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 5B8C5EDB7D1; Fri, 18 May 2018 20:34:22 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-wm0-x22a.google.com (mail-wm0-x22a.google.com [IPv6:2a00:1450:400c:c09::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A026D69163; Fri, 18 May 2018 20:34:21 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-wm0-x22a.google.com with SMTP id f6-v6so16050254wmc.4; Fri, 18 May 2018 13:34:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=bO2pP0bzh8DR5IeWVg64OUbVk+D1H8/IKUL3cWmF6hc=; b=tbSO0gPzHkKmkr3FfHLBk4W9QzA8Cs0La02CoQzp75oVSv20pPlNG5UdNrZxDLRyUg 1oEniZdbCJg/m3tjynsbQboEZtDB4VtqCyD1gPlE2JvocF9pSXF8TWogxIJZdm/KRWeX 8nJyXSbdzPqHV8CkDgHk5P4nf3Ms19F1mgeL888FAlCX5RvkUKyx6CkFltWOkCquTX3S fHkvJSCPMvsc+u/VtX3c1RKKh+uTxUTMMt/Bb+KrpeNfkSSsVu+BIUP1qLPsPAKFZjoY Ym4KmAiYyPmyIwDmCocXFY9MamRBMg4ogUw8KIGxl0Y8pW04qQKCVCsjUsnYogFfusB5 4xZA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=bO2pP0bzh8DR5IeWVg64OUbVk+D1H8/IKUL3cWmF6hc=; b=NbjuRBx6c4/cbL3Fkum1fS5W3peNnHj+DvxbeTI11Eo/m6UDw0bixJbf5UgHLADED5 RjGv9io+R/1vqwp46fAFVSmijezVGFHbar1JJV6BCe2EKda5OgB9q0CiYNVHtJX6Gvx4 JDL5/ncF8WcVaZC9yFEdQHI7LNYq5nFn2NSj0OlRKwkvl+1nRvJU3krtNuDGBjcne9JJ bsMmE7ci6I5Qp7zWzdgQQK1QARtm/GFEjwOKMq5g2EGT40Qg32P92FXCpqGERFRvL1c7 IXtpHuBINMKfRdpg1jTgNb5J8MxW/Ri8qfbfThg5Bfof0eCDnuhpd0dIrntNHFm8mmhp rXCQ== X-Gm-Message-State: ALKqPwecQ9Y2jpGrNMyfVOeDzQm0hl8zn93KAsPv+vnZ3pzr0bR8PvhP NvhQSuiRXTx0oacT2SSrwpWlfZc4qw28WHVQLi0= X-Google-Smtp-Source: AB8JxZrZpMu5BLlJtXOMkvs6Fg0C9HreDu6PS8pEeiIB8tOqk3mvc+n3OCCbRpnGCBNkU3TnltXRXRLkTL1B1kfPeSI= X-Received: by 2002:a1c:f714:: with SMTP id v20-v6mr5832011wmh.73.1526675660622; Fri, 18 May 2018 13:34:20 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.146.194 with HTTP; Fri, 18 May 2018 13:33:40 -0700 (PDT) In-Reply-To: <20180518202200.dks3twrlfyhmcgbb@mail.bwidawsk.net> References: <3a5edc5c-3caa-830b-4bd9-53ff52feb8a7@freebsd.org> <20180518193009.GA88432@troutmask.apl.washington.edu> <20180518202200.dks3twrlfyhmcgbb@mail.bwidawsk.net> From: Johannes Lundberg Date: Fri, 18 May 2018 21:33:40 +0100 Message-ID: Subject: Re: [RFC] Deprecation and removal of the drm2 driver To: Ben Widawsky Cc: Warner Losh , Steve Kargl , Andreas Nilsson , FreeBSD X11 mailing list , Current FreeBSD Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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 May 2018 20:34:22 -0000 On Fri, May 18, 2018 at 9:22 PM, Ben Widawsky wrote: > On 18-05-18 14:15:03, Warner Losh wrote: > > On Fri, May 18, 2018 at 2:12 PM, Johannes Lundberg > > wrote: > > > > > > > > > > > On Fri, May 18, 2018 at 9:03 PM, Warner Losh wrote: > > > > > >> On Fri, May 18, 2018 at 1:30 PM, Steve Kargl < > > >> sgk@troutmask.apl.washington.edu> wrote: > > >> > > >> > On Fri, May 18, 2018 at 09:14:24PM +0200, Andreas Nilsson wrote: > > >> > > On Fri, May 18, 2018, 20:00 Niclas Zeising > > >> wrote: > > >> > > > > >> > > > I propose that we remove the old drm2 driver (sys/dev/drm2) fr= om > > >> > > > FreeBSD. I suggest the driver is marked as deprecated in 11.x > and > > >> > > > removed from 12.0, as was done for other drivers recently. So= me > > >> > > > background and rationale: > > >> > > > > > >> > > > The drm2 driver was the original port of a KMS driver to > FreeBSD. > > >> It > > >> > > > was done by Konstantin Belousov to support Intel graphics > cards, and > > >> > > > later extended by Jean-S=C3=A9bastien P=C3=A9dron as well as K= onstantin to > > >> match > > >> > > > what's in Linux 3.8. This included unstable support from > Haswell, > > >> but > > >> > > > nothing newer than that. > > >> > > > > > >> > > > For quite some time now we have had the > graphics/drm-stable-kmod and > > >> > > > graphics/drm-next-kmods which provides support for modern AMD > and > > >> Intel > > >> > > > graphics cards. These ports, together with the linuxkpi, or > lkpi, > > >> has > > >> > > > made it significantly easier to port and update our graphics > > >> drivers. > > >> > > > Further, these new drivers cover the same drivers as the old > drm2 > > >> > driver. > > >> > > > > > >> > > > What does the community think? Is there anyone still using th= e > drm2 > > >> > > > driver on 12-CURRENT? If so, what is preventing you from > switching > > >> to > > >> > > > the port? > > >> > > > > > >> > > > Thank you > > >> > > > Regards > > >> > > > -- > > >> > > > Niclas Zeising > > >> > > > FreeBSD x11/graphics team > > >> > > > _______________________________________________ > > >> > > > 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" > > >> > > > > > >> > > > > >> > > Sounds good ( deprecate resp remove ). It causes more confusion > and > > >> > > problems and it solves nothing. > > >> > > > > >> > > > >> > Check the Makefiles > > >> > > > >> > % more /usr/ports/graphics/drm-next-kmod/Makefile > > >> > > > >> > ONLY_FOR_ARCHS=3D amd64 > > >> > ONLY_FOR_ARCHS_REASON=3D the new KMS components are only supporte= d on > > >> amd64 > > >> > > > >> > Not to ia32 friendly. > > >> > > > >> > > >> So do people use i386 for desktop? And need the latest KMS stuff? > > >> > > > > > > Yeah I was wondering the same.. If you're running i386, do you need d= rm > > > drivers? Will scfb work an i386? (probably has legacy bios and if I > > > remember correctly, scfb is UEFI only) > > > I do feel sorry for anyone who would have to revert back to VESA... > > > > > > Would it be too much trouble to move it to a port? > > > > > > > If there's someone who needs it for i386, and wants to do the work and > > maintain it, we should allow it. But the drm2 maintainers have said its > > likely totally broken anyway. > > > > Warner > > As a long time developer in drm/i915, and newly interested in FreeBSD (ie= . > no > history on the matter), is there some upside and/or desire to have native > support, or is the drm-next-kmod solution good enough? > Given the fast evolution of graphics hardware and the amount of code in only the AMD and Intel drivers, keep several native implementations seems impossible, if not wasteful. If you are referring to drm2 in the kernel, that's not much more native than the drm kmods, it still uses a linux compatibility layer (but not as sophisticated). If we were to focus our effort somewhere, it should be to create a Common Kernel Programming Interface for Linux and *BSDs, especially for DRM drivers. Something a bit more stable that what we see in Linux today. From owner-freebsd-current@freebsd.org Fri May 18 21:53:23 2018 Return-Path: Delivered-To: freebsd-current@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 53EC4EDD8A6 for ; Fri, 18 May 2018 21:53:23 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (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 87DC06B8B7 for ; Fri, 18 May 2018 21:53:22 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id w4ILr1lr008896 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 19 May 2018 00:53:04 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua w4ILr1lr008896 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id w4ILr0lN008895; Sat, 19 May 2018 00:53:00 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Sat, 19 May 2018 00:53:00 +0300 From: Konstantin Belousov To: Johannes Lundberg Cc: Ben Widawsky , Warner Losh , Steve Kargl , Andreas Nilsson , FreeBSD X11 mailing list , Current FreeBSD Subject: Re: [RFC] Deprecation and removal of the drm2 driver Message-ID: <20180518215300.GE6887@kib.kiev.ua> References: <3a5edc5c-3caa-830b-4bd9-53ff52feb8a7@freebsd.org> <20180518193009.GA88432@troutmask.apl.washington.edu> <20180518202200.dks3twrlfyhmcgbb@mail.bwidawsk.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.5 (2018-04-13) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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 May 2018 21:53:23 -0000 On Fri, May 18, 2018 at 09:33:40PM +0100, Johannes Lundberg wrote: > On Fri, May 18, 2018 at 9:22 PM, Ben Widawsky wrote: > > > On 18-05-18 14:15:03, Warner Losh wrote: > > > On Fri, May 18, 2018 at 2:12 PM, Johannes Lundberg > > > wrote: > > > > > > > > > > > > > > > On Fri, May 18, 2018 at 9:03 PM, Warner Losh wrote: > > > > > > > >> On Fri, May 18, 2018 at 1:30 PM, Steve Kargl < > > > >> sgk@troutmask.apl.washington.edu> wrote: > > > >> > > > >> > On Fri, May 18, 2018 at 09:14:24PM +0200, Andreas Nilsson wrote: > > > >> > > On Fri, May 18, 2018, 20:00 Niclas Zeising > > > >> wrote: > > > >> > > > > > >> > > > I propose that we remove the old drm2 driver (sys/dev/drm2) from > > > >> > > > FreeBSD. I suggest the driver is marked as deprecated in 11.x > > and > > > >> > > > removed from 12.0, as was done for other drivers recently. Some > > > >> > > > background and rationale: > > > >> > > > > > > >> > > > The drm2 driver was the original port of a KMS driver to > > FreeBSD. > > > >> It > > > >> > > > was done by Konstantin Belousov to support Intel graphics > > cards, and > > > >> > > > later extended by Jean-S??bastien P??dron as well as Konstantin to > > > >> match > > > >> > > > what's in Linux 3.8. This included unstable support from > > Haswell, > > > >> but > > > >> > > > nothing newer than that. > > > >> > > > > > > >> > > > For quite some time now we have had the > > graphics/drm-stable-kmod and > > > >> > > > graphics/drm-next-kmods which provides support for modern AMD > > and > > > >> Intel > > > >> > > > graphics cards. These ports, together with the linuxkpi, or > > lkpi, > > > >> has > > > >> > > > made it significantly easier to port and update our graphics > > > >> drivers. > > > >> > > > Further, these new drivers cover the same drivers as the old > > drm2 > > > >> > driver. > > > >> > > > > > > >> > > > What does the community think? Is there anyone still using the > > drm2 > > > >> > > > driver on 12-CURRENT? If so, what is preventing you from > > switching > > > >> to > > > >> > > > the port? > > > >> > > > > > > >> > > > Thank you > > > >> > > > Regards > > > >> > > > -- > > > >> > > > Niclas Zeising > > > >> > > > FreeBSD x11/graphics team > > > >> > > > _______________________________________________ > > > >> > > > 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" > > > >> > > > > > > >> > > > > > >> > > Sounds good ( deprecate resp remove ). It causes more confusion > > and > > > >> > > problems and it solves nothing. > > > >> > > > > > >> > > > > >> > Check the Makefiles > > > >> > > > > >> > % more /usr/ports/graphics/drm-next-kmod/Makefile > > > >> > > > > >> > ONLY_FOR_ARCHS= amd64 > > > >> > ONLY_FOR_ARCHS_REASON= the new KMS components are only supported on > > > >> amd64 > > > >> > > > > >> > Not to ia32 friendly. > > > >> > > > > >> > > > >> So do people use i386 for desktop? And need the latest KMS stuff? > > > >> > > > > > > > > Yeah I was wondering the same.. If you're running i386, do you need drm > > > > drivers? Will scfb work an i386? (probably has legacy bios and if I > > > > remember correctly, scfb is UEFI only) > > > > I do feel sorry for anyone who would have to revert back to VESA... > > > > > > > > Would it be too much trouble to move it to a port? > > > > > > > > > > If there's someone who needs it for i386, and wants to do the work and > > > maintain it, we should allow it. But the drm2 maintainers have said its > > > likely totally broken anyway. > > > > > > Warner > > > > As a long time developer in drm/i915, and newly interested in FreeBSD (ie. > > no > > history on the matter), is there some upside and/or desire to have native > > support, or is the drm-next-kmod solution good enough? > > > > Given the fast evolution of graphics hardware and the amount of code in > only the AMD and Intel drivers, keep several native implementations seems > impossible, if not wasteful. > If you are referring to drm2 in the kernel, that's not much more native > than the drm kmods, it still uses a linux compatibility layer (but not as > sophisticated). Drm2 does not use linux compat layer. drm2 is probably better on older chipsets which use AGP emulation, i.e. everything up to SandyBridge-1. Does drm-next run on gen3 and gen4 at all ? In particular, I did obtained real bug reports from people running gen 3 hardware. E.g. you cannot run amd64 kernel on T60, but you can run i386 and get hw support with drm2. I still have GM45 (gen4) laptop and use it daily with the drm from the tree. I effectively dropped supporting it when half of the HSW support code were imported. > > If we were to focus our effort somewhere, it should be to create a Common > Kernel Programming Interface for Linux and *BSDs, especially for DRM > drivers. Something a bit more stable that what we see in Linux today. From owner-freebsd-current@freebsd.org Fri May 18 21:59:47 2018 Return-Path: Delivered-To: freebsd-current@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 B182DEDDB6D for ; Fri, 18 May 2018 21:59:47 +0000 (UTC) (envelope-from oliver.pinter@hardenedbsd.org) Received: from mail-yb0-x230.google.com (mail-yb0-x230.google.com [IPv6:2607:f8b0:4002:c09::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4A1F86BB6A for ; Fri, 18 May 2018 21:59:47 +0000 (UTC) (envelope-from oliver.pinter@hardenedbsd.org) Received: by mail-yb0-x230.google.com with SMTP id g140-v6so3214692ybf.6 for ; Fri, 18 May 2018 14:59:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hardenedbsd-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=8Zr7wKS8jtfRTD4LALM+VZ98wIHQD1rHy9lWdvEeS10=; b=mSys5l/e4SZwJ6q5qgpbtSKCYx8NdvlmpbBPHx0PjycWPO+RAS9Z/5PW/ZI5O2s2/h bh7v4mhDNfRYeYB8s4/OnPVn7HvmL1fu4LrNLKzz2ERWG6RqFY5H1SxPJXE8N7C6Khgu eprs+w0iBulBsicvaqoXulceusMTicU2Pz1reIAhQrQW9NZn5J9dDJ3EQC6XUd5W2ONG L1hTT+ibC0Kltkms5MezC4W1aHxO+DYb/jn+qnGi1BmZaqc8/iT8bWKn1B9lMgxMrEgf pU6gOrzoR/JjuiAS/BaH4XqQM3mHumjLl3n1gzlCNDRf8x1b+GcNIYd6zU62+JjXhqT4 w0cA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=8Zr7wKS8jtfRTD4LALM+VZ98wIHQD1rHy9lWdvEeS10=; b=gpG2OeIzFRtCP1c/2YDrAD1tyHHHGV/H2de3clL5fSg1AHVAEFjduQ4j9KjZUIrpwC t2xZlQgylhViTQU/YVaxoIpm0vmNSpdt3btOmUWud6zXYidLuAOnhXozOnIs6Dav3CFo Ep0v5pMQAjKpvJU+wks0t/37b3MfZXl4U7dji0cGqAOo6FWjBKvxYX/BVYJJy3NvXO+d 38gA3kzGs6boW/ZzGMnVPKgK8al6LufCCNFF7jZHdIgT4HEjoqSHaSexn2FC5DuBoV1m 7zpD3VnntR8CZW1ee2OAej5T6w7Q8VtTi/LtsWbk3DKKAHBXHLAJ842NtopzGU3lf4bQ tjdw== X-Gm-Message-State: ALKqPwcTRO358nR0Lvw8uEvEs0l4y83GiQsQZLc5hhwEAk9IuDASGVkz s5+3TygJmd9xtrai58TfkwInWcOttIk+2asa7uVMfA== X-Google-Smtp-Source: AB8JxZo+Y4q35LbkT8ZAZcJqVjpIH/JHP+rKKds6TyrFHsenJijfE2I8fF3s4ViRFfHbkR5nR6FLCpBR7SsqtkVdWy8= X-Received: by 2002:a25:8e0c:: with SMTP id p12-v6mr6271780ybl.199.1526680786583; Fri, 18 May 2018 14:59:46 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a25:3894:0:0:0:0:0 with HTTP; Fri, 18 May 2018 14:59:46 -0700 (PDT) In-Reply-To: <20180518215300.GE6887@kib.kiev.ua> References: <3a5edc5c-3caa-830b-4bd9-53ff52feb8a7@freebsd.org> <20180518193009.GA88432@troutmask.apl.washington.edu> <20180518202200.dks3twrlfyhmcgbb@mail.bwidawsk.net> <20180518215300.GE6887@kib.kiev.ua> From: Oliver Pinter Date: Fri, 18 May 2018 23:59:46 +0200 Message-ID: Subject: Re: [RFC] Deprecation and removal of the drm2 driver To: Konstantin Belousov Cc: Johannes Lundberg , Ben Widawsky , Warner Losh , Steve Kargl , Andreas Nilsson , FreeBSD X11 mailing list , Current FreeBSD Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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 May 2018 21:59:48 -0000 On Friday, May 18, 2018, Konstantin Belousov wrote: > On Fri, May 18, 2018 at 09:33:40PM +0100, Johannes Lundberg wrote: > > On Fri, May 18, 2018 at 9:22 PM, Ben Widawsky wrote: > > > > > On 18-05-18 14:15:03, Warner Losh wrote: > > > > On Fri, May 18, 2018 at 2:12 PM, Johannes Lundberg < > johalun0@gmail.com> > > > > wrote: > > > > > > > > > > > > > > > > > > > On Fri, May 18, 2018 at 9:03 PM, Warner Losh > wrote: > > > > > > > > > >> On Fri, May 18, 2018 at 1:30 PM, Steve Kargl < > > > > >> sgk@troutmask.apl.washington.edu> wrote: > > > > >> > > > > >> > On Fri, May 18, 2018 at 09:14:24PM +0200, Andreas Nilsson wrote: > > > > >> > > On Fri, May 18, 2018, 20:00 Niclas Zeising < > zeising@freebsd.org> > > > > >> wrote: > > > > >> > > > > > > >> > > > I propose that we remove the old drm2 driver (sys/dev/drm2) > from > > > > >> > > > FreeBSD. I suggest the driver is marked as deprecated in > 11.x > > > and > > > > >> > > > removed from 12.0, as was done for other drivers recently. > Some > > > > >> > > > background and rationale: > > > > >> > > > > > > > >> > > > The drm2 driver was the original port of a KMS driver to > > > FreeBSD. > > > > >> It > > > > >> > > > was done by Konstantin Belousov to support Intel graphics > > > cards, and > > > > >> > > > later extended by Jean-S??bastien P??dron as well as > Konstantin to > > > > >> match > > > > >> > > > what's in Linux 3.8. This included unstable support from > > > Haswell, > > > > >> but > > > > >> > > > nothing newer than that. > > > > >> > > > > > > > >> > > > For quite some time now we have had the > > > graphics/drm-stable-kmod and > > > > >> > > > graphics/drm-next-kmods which provides support for modern > AMD > > > and > > > > >> Intel > > > > >> > > > graphics cards. These ports, together with the linuxkpi, or > > > lkpi, > > > > >> has > > > > >> > > > made it significantly easier to port and update our graphics > > > > >> drivers. > > > > >> > > > Further, these new drivers cover the same drivers as the old > > > drm2 > > > > >> > driver. > > > > >> > > > > > > > >> > > > What does the community think? Is there anyone still using > the > > > drm2 > > > > >> > > > driver on 12-CURRENT? If so, what is preventing you from > > > switching > > > > >> to > > > > >> > > > the port? > > > > >> > > > > > > > >> > > > Thank you > > > > >> > > > Regards > > > > >> > > > -- > > > > >> > > > Niclas Zeising > > > > >> > > > FreeBSD x11/graphics team > > > > >> > > > _______________________________________________ > > > > >> > > > 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" > > > > >> > > > > > > > >> > > > > > > >> > > Sounds good ( deprecate resp remove ). It causes more > confusion > > > and > > > > >> > > problems and it solves nothing. > > > > >> > > > > > > >> > > > > > >> > Check the Makefiles > > > > >> > > > > > >> > % more /usr/ports/graphics/drm-next-kmod/Makefile > > > > >> > > > > > >> > ONLY_FOR_ARCHS= amd64 > > > > >> > ONLY_FOR_ARCHS_REASON= the new KMS components are only > supported on > > > > >> amd64 > > > > >> > > > > > >> > Not to ia32 friendly. > > > > >> > > > > > >> > > > > >> So do people use i386 for desktop? And need the latest KMS stuff? > > > > >> > > > > > > > > > > Yeah I was wondering the same.. If you're running i386, do you > need drm > > > > > drivers? Will scfb work an i386? (probably has legacy bios and if I > > > > > remember correctly, scfb is UEFI only) > > > > > I do feel sorry for anyone who would have to revert back to VESA... > > > > > > > > > > Would it be too much trouble to move it to a port? > > > > > > > > > > > > > If there's someone who needs it for i386, and wants to do the work > and > > > > maintain it, we should allow it. But the drm2 maintainers have said > its > > > > likely totally broken anyway. > > > > > > > > Warner > > > > > > As a long time developer in drm/i915, and newly interested in FreeBSD > (ie. > > > no > > > history on the matter), is there some upside and/or desire to have > native > > > support, or is the drm-next-kmod solution good enough? > > > > > > > Given the fast evolution of graphics hardware and the amount of code in > > only the AMD and Intel drivers, keep several native implementations seems > > impossible, if not wasteful. > > If you are referring to drm2 in the kernel, that's not much more native > > than the drm kmods, it still uses a linux compatibility layer (but not as > > sophisticated). > Drm2 does not use linux compat layer. > > drm2 is probably better on older chipsets which use AGP emulation, i.e. > everything up to SandyBridge-1. Does drm-next run on gen3 and gen4 at > all ? In particular, I did obtained real bug reports from people running > gen 3 hardware. E.g. you cannot run amd64 kernel on T60, but you can run > i386 and get hw support with drm2. > > I still have GM45 (gen4) laptop and use it daily with the drm from the > tree. I effectively dropped supporting it when half of the HSW support > code were imported. I use the in tree DRM2 code on multiple Haswell based laptops. It working fine. So I prefer to keep it in the tree. I like to use bigger console, even if I not install anything from ports. > > > > > If we were to focus our effort somewhere, it should be to create a Common > > Kernel Programming Interface for Linux and *BSDs, especially for DRM > > drivers. Something a bit more stable that what we see in Linux today. > _______________________________________________ > 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" > From owner-freebsd-current@freebsd.org Fri May 18 22:25:52 2018 Return-Path: Delivered-To: freebsd-current@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 DFFCFEDE639; Fri, 18 May 2018 22:25:51 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 543396CAE9; Fri, 18 May 2018 22:25:51 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.15.2/8.15.2) with ESMTPS id w4IMPnNk089664 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 18 May 2018 15:25:50 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.15.2/8.15.2/Submit) id w4IMPnmk089663; Fri, 18 May 2018 15:25:49 -0700 (PDT) (envelope-from sgk) Date: Fri, 18 May 2018 15:25:49 -0700 From: Steve Kargl To: Warner Losh Cc: Andreas Nilsson , FreeBSD X11 mailing list , Current FreeBSD Subject: Re: [RFC] Deprecation and removal of the drm2 driver Message-ID: <20180518222549.GB89631@troutmask.apl.washington.edu> Reply-To: sgk@troutmask.apl.washington.edu References: <3a5edc5c-3caa-830b-4bd9-53ff52feb8a7@freebsd.org> <20180518193009.GA88432@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.2 (2017-12-15) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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 May 2018 22:25:52 -0000 On Fri, May 18, 2018 at 02:03:32PM -0600, Warner Losh wrote: > On Fri, May 18, 2018 at 1:30 PM, Steve Kargl < > sgk@troutmask.apl.washington.edu> wrote: > > > Check the Makefiles > > > > % more /usr/ports/graphics/drm-next-kmod/Makefile > > > > ONLY_FOR_ARCHS= amd64 > > ONLY_FOR_ARCHS_REASON= the new KMS components are only supported on amd64 > > > > Not to ia32 friendly. > > > > So do people use i386 for desktop? And need the latest KMS stuff? > I use drm2 on my old Dell Latitude D530 with Intel graphics. Unfortunately, she ate her old SATA-1 disk on Monday and I've only just gotten a SSD to replace. So, I need to recreate my laptop's environment. -- Steve From owner-freebsd-current@freebsd.org Fri May 18 22:27:49 2018 Return-Path: Delivered-To: freebsd-current@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 09F0DEDE738; Fri, 18 May 2018 22:27:49 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from smtp-out-so.shaw.ca (smtp-out-so.shaw.ca [64.59.136.138]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 6E65C6CC2C; Fri, 18 May 2018 22:27:47 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from spqr.komquats.com ([70.67.125.17]) by shaw.ca with ESMTPA id JnqiftcAvSzNNJnqjfjldm; Fri, 18 May 2018 16:27:47 -0600 X-Authority-Analysis: v=2.3 cv=KuxjJ1eN c=1 sm=1 tr=0 a=VFtTW3WuZNDh6VkGe7fA3g==:117 a=VFtTW3WuZNDh6VkGe7fA3g==:17 a=kj9zAlcOel0A:10 a=VUJBJC2UJ8kA:10 a=PTzpF0JeAAAA:8 a=YxBL1-UpAAAA:8 a=6I5d2MoRAAAA:8 a=VIgGObXe95TmuWEt1eEA:9 a=CjuIK1q_8ugA:10 a=22olxMbfhJEqLtC5csby:22 a=Ia-lj3WSrqcvXOmTRaiG:22 a=IjZwj45LgO3ly-622nXo:22 Received: from slippy.cwsent.com (slippy [10.1.1.91]) by spqr.komquats.com (Postfix) with ESMTPS id 1A1ADE20; Fri, 18 May 2018 15:27:44 -0700 (PDT) Received: from slippy.cwsent.com (localhost [127.0.0.1]) by slippy.cwsent.com (8.15.2/8.15.2) with ESMTP id w4IMRhjd033318; Fri, 18 May 2018 15:27:43 -0700 (PDT) (envelope-from Cy.Schubert@cschubert.com) Received: from slippy (cy@localhost) by slippy.cwsent.com (8.15.2/8.15.2/Submit) with ESMTP id w4IMRhCU033315; Fri, 18 May 2018 15:27:43 -0700 (PDT) (envelope-from Cy.Schubert@cschubert.com) Message-Id: <201805182227.w4IMRhCU033315@slippy.cwsent.com> X-Authentication-Warning: slippy.cwsent.com: cy owned process doing -bs X-Mailer: exmh version 2.8.0 04/21/2012 with nmh-1.7.1 Reply-to: Cy Schubert From: Cy Schubert X-os: FreeBSD X-Sender: cy@cwsent.com X-URL: http://www.cschubert.com/ To: Daniel Eischen cc: Warner Losh , FreeBSD X11 mailing list , Current FreeBSD , Steve Kargl Subject: Re: [RFC] Deprecation and removal of the drm2 driver In-Reply-To: Message from Daniel Eischen of "Fri, 18 May 2018 16:19:21 -0400." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 18 May 2018 15:27:43 -0700 X-CMAE-Envelope: MS4wfCOWH7B9e76E8NfCF1wjPs7df+Ptrm0NfGUruendrs7jWHJRWJDhGoGZMTCytAVQlTfZUIsE5YYldSatLpvX2DGsB3OxIPLKBi+BixX0XXIQ/QuW66Cq c55/fZ0WPwsdjT+w8DoM98UltdiuveUG8vwA1i2zXGz5mUzDpWLmOHVJ+Sz2qsxHAR8WpZPvKKpGE0T0acYGIXwtNOnb8czDwg1UQut4tP/l20+lx6bCGkb/ iglKFhJNcijg+Zj2Les+LABGLiqHatKHIwvy5Znu9OUupVISzuzyJl8PJI1M65YxW6PF6clSWjYDeWod4Oia52Ibp23381e3QHq7otQs6x1PoeFVBejS92P6 Le5XOgi9XmlGSTH+gj6NQpqD3Jk2o+ufet5t244h4qwob1bCEAI= X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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 May 2018 22:27:49 -0000 In message , Daniel Eischen wr ites: > On Fri, 18 May 2018, Warner Losh wrote: > > > On Fri, May 18, 2018 at 1:30 PM, Steve Kargl < > > sgk@troutmask.apl.washington.edu> wrote: > >> > >> Check the Makefiles > >> > >> % more /usr/ports/graphics/drm-next-kmod/Makefile > >> > >> ONLY_FOR_ARCHS= amd64 > >> ONLY_FOR_ARCHS_REASON= the new KMS components are only supported on amd64 > >> > >> Not to ia32 friendly. > >> > > > > So do people use i386 for desktop? And need the latest KMS stuff? > > I can easily imagine an embedded x86 kiosk type appliance. Does > basic xorg stuff work without drm? Yes, with VESA, albeit aspect ratios are off. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few. From owner-freebsd-current@freebsd.org Fri May 18 22:39:26 2018 Return-Path: Delivered-To: freebsd-current@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 4C413EDECC9; Fri, 18 May 2018 22:39:26 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from smtp-out-no.shaw.ca (smtp-out-no.shaw.ca [64.59.134.12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 9DAAE6D459; Fri, 18 May 2018 22:39:24 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from spqr.komquats.com ([70.67.125.17]) by shaw.ca with ESMTPA id Jo1qfovdlvB5RJo1rfiCCB; Fri, 18 May 2018 16:39:18 -0600 X-Authority-Analysis: v=2.3 cv=PvS9kTE3 c=1 sm=1 tr=0 a=VFtTW3WuZNDh6VkGe7fA3g==:117 a=VFtTW3WuZNDh6VkGe7fA3g==:17 a=kj9zAlcOel0A:10 a=VUJBJC2UJ8kA:10 a=xfDLHkLGAAAA:8 a=pGLkceISAAAA:8 a=PSgcYXQzAAAA:8 a=7Qk2ozbKAAAA:8 a=6I5d2MoRAAAA:8 a=YxBL1-UpAAAA:8 a=PRGGhdUTl-ceUwIz4A4A:9 a=CjuIK1q_8ugA:10 a=9Y0e4YsJdwUA:10 a=IfaqVvZgccqrtc8gcwf2:22 a=wWUH5_S2rmbbYoQN9rHo:22 a=1lyxoWkJIXJV6VJUPhuM:22 a=IjZwj45LgO3ly-622nXo:22 a=Ia-lj3WSrqcvXOmTRaiG:22 a=q26kHJAvr7aNoQcLmzvC:22 Received: from slippy.cwsent.com (slippy [10.1.1.91]) by spqr.komquats.com (Postfix) with ESMTPS id 102DDE51; Fri, 18 May 2018 15:39:14 -0700 (PDT) Received: from slippy.cwsent.com (localhost [127.0.0.1]) by slippy.cwsent.com (8.15.2/8.15.2) with ESMTP id w4IMdDsM033413; Fri, 18 May 2018 15:39:13 -0700 (PDT) (envelope-from Cy.Schubert@cschubert.com) Received: from slippy (cy@localhost) by slippy.cwsent.com (8.15.2/8.15.2/Submit) with ESMTP id w4IMdDsJ033410; Fri, 18 May 2018 15:39:13 -0700 (PDT) (envelope-from Cy.Schubert@cschubert.com) Message-Id: <201805182239.w4IMdDsJ033410@slippy.cwsent.com> X-Authentication-Warning: slippy.cwsent.com: cy owned process doing -bs X-Mailer: exmh version 2.8.0 04/21/2012 with nmh-1.7.1 Reply-to: Cy Schubert From: Cy Schubert X-os: FreeBSD X-Sender: cy@cwsent.com X-URL: http://www.cschubert.com/ To: Oliver Pinter cc: Konstantin Belousov , Ben Widawsky , Current FreeBSD , Steve Kargl , FreeBSD X11 mailing list , Warner Losh Subject: Re: [RFC] Deprecation and removal of the drm2 driver In-Reply-To: Message from Oliver Pinter of "Fri, 18 May 2018 23:59:46 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 18 May 2018 15:39:13 -0700 X-CMAE-Envelope: MS4wfNcbpRHrpPhE+5/hL5SNeEuRUQXIqnClG7ByzHzn5pGYebFzsFsmGiKwAjfx2yIZ22IJSKQgf+Co4FV4bFyAP782sqqsoh2pjU9jA+muCLn4iPPKYH4i lFxIDk874/Tt7C0nvvbRl/GjvthKyYhiYosZvA5xo6vVNUnjc13K+bQ8FntCdK6rNID3apj+d+OeFjTISuoXKmUM78RFpCzjatS+gUS4HVeZ+bSgTx9Iez+w sI6tszOkmPBjW+1hYLvFBu3BHlN/9/GMnbRLKdPNw7YhbE+zf1AsPc6F+cyV+FJAP800abMxrAfClVumzB2NpZ/XKewDlGJOMISbhg9lxOC4Bi/FIpniQ32E P6uWjI9uBaLyOB6hvgqtefKTJYaoOLiy8u/CBzrgiHlnGfo8xRmobTya4GJm5QWo9Omf5sx5zuDmdCYPGvUllyy1InxDCeNcUqKjJumbo15KgzYbgZPcrX8Z viJhHEog8zryFWbJ X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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 May 2018 22:39:26 -0000 In message , Oliver Pinter writes: > On Friday, May 18, 2018, Konstantin Belousov wrote: > > > On Fri, May 18, 2018 at 09:33:40PM +0100, Johannes Lundberg wrote: > > > On Fri, May 18, 2018 at 9:22 PM, Ben Widawsky wrote: > > > > > > > On 18-05-18 14:15:03, Warner Losh wrote: > > > > > On Fri, May 18, 2018 at 2:12 PM, Johannes Lundberg < > > johalun0@gmail.com> > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > On Fri, May 18, 2018 at 9:03 PM, Warner Losh > > wrote: > > > > > > > > > > > >> On Fri, May 18, 2018 at 1:30 PM, Steve Kargl < > > > > > >> sgk@troutmask.apl.washington.edu> wrote: > > > > > >> > > > > > >> > On Fri, May 18, 2018 at 09:14:24PM +0200, Andreas Nilsson wrote: > > > > > >> > > On Fri, May 18, 2018, 20:00 Niclas Zeising < > > zeising@freebsd.org> > > > > > >> wrote: > > > > > >> > > > > > > > >> > > > I propose that we remove the old drm2 driver (sys/dev/drm2) > > from > > > > > >> > > > FreeBSD. I suggest the driver is marked as deprecated in > > 11.x > > > > and > > > > > >> > > > removed from 12.0, as was done for other drivers recently. > > Some > > > > > >> > > > background and rationale: > > > > > >> > > > > > > > > >> > > > The drm2 driver was the original port of a KMS driver to > > > > FreeBSD. > > > > > >> It > > > > > >> > > > was done by Konstantin Belousov to support Intel graphics > > > > cards, and > > > > > >> > > > later extended by Jean-S??bastien P??dron as well as > > Konstantin to > > > > > >> match > > > > > >> > > > what's in Linux 3.8. This included unstable support from > > > > Haswell, > > > > > >> but > > > > > >> > > > nothing newer than that. > > > > > >> > > > > > > > > >> > > > For quite some time now we have had the > > > > graphics/drm-stable-kmod and > > > > > >> > > > graphics/drm-next-kmods which provides support for modern > > AMD > > > > and > > > > > >> Intel > > > > > >> > > > graphics cards. These ports, together with the linuxkpi, or > > > > lkpi, > > > > > >> has > > > > > >> > > > made it significantly easier to port and update our graphics > > > > > >> drivers. > > > > > >> > > > Further, these new drivers cover the same drivers as the old > > > > drm2 > > > > > >> > driver. > > > > > >> > > > > > > > > >> > > > What does the community think? Is there anyone still using > > the > > > > drm2 > > > > > >> > > > driver on 12-CURRENT? If so, what is preventing you from > > > > switching > > > > > >> to > > > > > >> > > > the port? > > > > > >> > > > > > > > > >> > > > Thank you > > > > > >> > > > Regards > > > > > >> > > > -- > > > > > >> > > > Niclas Zeising > > > > > >> > > > FreeBSD x11/graphics team > > > > > >> > > > _______________________________________________ > > > > > >> > > > 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" > > > > > >> > > > > > > > > >> > > > > > > > >> > > Sounds good ( deprecate resp remove ). It causes more > > confusion > > > > and > > > > > >> > > problems and it solves nothing. > > > > > >> > > > > > > > >> > > > > > > >> > Check the Makefiles > > > > > >> > > > > > > >> > % more /usr/ports/graphics/drm-next-kmod/Makefile > > > > > >> > > > > > > >> > ONLY_FOR_ARCHS= amd64 > > > > > >> > ONLY_FOR_ARCHS_REASON= the new KMS components are only > > supported on > > > > > >> amd64 > > > > > >> > > > > > > >> > Not to ia32 friendly. > > > > > >> > > > > > > >> > > > > > >> So do people use i386 for desktop? And need the latest KMS stuff? > > > > > >> > > > > > > > > > > > > Yeah I was wondering the same.. If you're running i386, do you > > need drm > > > > > > drivers? Will scfb work an i386? (probably has legacy bios and if I > > > > > > remember correctly, scfb is UEFI only) > > > > > > I do feel sorry for anyone who would have to revert back to VESA... > > > > > > > > > > > > Would it be too much trouble to move it to a port? > > > > > > > > > > > > > > > > If there's someone who needs it for i386, and wants to do the work > > and > > > > > maintain it, we should allow it. But the drm2 maintainers have said > > its > > > > > likely totally broken anyway. > > > > > > > > > > Warner > > > > > > > > As a long time developer in drm/i915, and newly interested in FreeBSD > > (ie. > > > > no > > > > history on the matter), is there some upside and/or desire to have > > native > > > > support, or is the drm-next-kmod solution good enough? > > > > > > > > > > Given the fast evolution of graphics hardware and the amount of code in > > > only the AMD and Intel drivers, keep several native implementations seems > > > impossible, if not wasteful. > > > If you are referring to drm2 in the kernel, that's not much more native > > > than the drm kmods, it still uses a linux compatibility layer (but not as > > > sophisticated). > > Drm2 does not use linux compat layer. > > > > drm2 is probably better on older chipsets which use AGP emulation, i.e. > > everything up to SandyBridge-1. Does drm-next run on gen3 and gen4 at > > all ? In particular, I did obtained real bug reports from people running > > gen 3 hardware. E.g. you cannot run amd64 kernel on T60, but you can run > > i386 and get hw support with drm2. > > > > I still have GM45 (gen4) laptop and use it daily with the drm from the > > tree. I effectively dropped supporting it when half of the HSW support > > code were imported. > > > I use the in tree DRM2 code on multiple Haswell based laptops. It working > fine. So I prefer to keep it in the tree. I also use it on an Acer 4752 (64-bit, Sandy Bridge, HD 3000, 1366x600) and rarely on my i386 test machine, an Acer 3624 (32-bit, Penium M, i915, 1280x768). Also with an HP 2009m (1600x900) monitor. > > I like to use bigger console, even if I not install anything from ports. Indeed. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few. From owner-freebsd-current@freebsd.org Fri May 18 23:07:20 2018 Return-Path: Delivered-To: freebsd-current@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 AB05FEDF650 for ; Fri, 18 May 2018 23:07:20 +0000 (UTC) (envelope-from toasty@dragondata.com) Received: from mail-io0-x243.google.com (mail-io0-x243.google.com [IPv6:2607:f8b0:4001:c06::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2FA046E1CD for ; Fri, 18 May 2018 23:07:20 +0000 (UTC) (envelope-from toasty@dragondata.com) Received: by mail-io0-x243.google.com with SMTP id d11-v6so8073530iof.11 for ; Fri, 18 May 2018 16:07:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dragondata.com; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=fqauz3DAVJ/ulc8xirpk7NkzgRGTxGRjdVT1/6UI0Rg=; b=iLjY5q3XFgmx/mw0eeRQOwLAmUrLbsR6pmlrGggo0SsRbefqKj2cz+KxnV+ZIO2CWc 91zvLLc3cprHXXR2LFuEGWcWeC0r3kkeNZVa9QrW+unnDU116zQ5swC3XG9p5+F53tVb anqbVPFlfvyLz6/MTsOYftcSPEyCPpBfPPKiI= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=fqauz3DAVJ/ulc8xirpk7NkzgRGTxGRjdVT1/6UI0Rg=; b=auc081046V4fov/x9BEtec12sg7g9YEnMAXS0vSfnKCIoNUNkC7fe3TDJhFOkapGBV w0zS0zhKtTUIPRQfu1Sk8hbctCFVca5XvjVL0CYZaz6YtGG1/A/uXJnZ3X/KW+mWXLud lEIcpNvUl2fRjdihm6FGJWjRH9UcP1an2Zr3EKEd6UFFa7MHmBCEHYObMPmBI2ln8XkS ECWFfub/tN8wnpDtH+OQfyv7Xlrtq72td2BgjhSPxaRanlvhF/AwdFfeu3E3ghMTg5+o PBeQGKCgZruPCSNdOBUdbgwY1u4KfsFcjk7qMpwSUSrnX6IWT76MY2KJY8jsC9AP9eWj gqIQ== X-Gm-Message-State: ALKqPwcMDcRt9KswNUrcuAPjvD4kTS6LmqHgsd53lCrizuynCltKHHNz Gq5W2TITW4B4suKrC1mR00LZ9A== X-Google-Smtp-Source: AB8JxZqRo8SD1qSqsevTe6RtADovo/vamKBQuKv5hFN4HNllEJRGglOjY3+PqwFs2nxpPoLPZZRZgg== X-Received: by 2002:a6b:998d:: with SMTP id b135-v6mr13559251ioe.122.1526684839445; Fri, 18 May 2018 16:07:19 -0700 (PDT) Received: from unassigned.v6.your.org ([2001:4978:1:45:f036:4a7b:4b23:e977]) by smtp.gmail.com with ESMTPSA id t4-v6sm5284278ita.29.2018.05.18.16.07.18 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 18 May 2018 16:07:18 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\)) Subject: Re: Current panic on boot on H11DSI motherboard with epyc cpu (nexus_add_irq: failed) From: Kevin Day In-Reply-To: <1616582.sIejGazfcv@ralph.baldwin.cx> Date: Fri, 18 May 2018 18:07:16 -0500 Cc: Vitalij Satanivskij , freebsd-current@freebsd.org, Stephen Hurd , cem@freebsd.org, Matthew Macy , "freebsd-hackers@freebsd.org" , Stephen Hurd Content-Transfer-Encoding: quoted-printable Message-Id: <40C20F1C-A3D7-4847-A365-DC94679E8ABF@dragondata.com> References: <20180416102710.GA90028@hell.ukr.net> <3628282.XVdngBdGlp@ralph.baldwin.cx> <20180418105649.GA9989@hell.ukr.net> <1616582.sIejGazfcv@ralph.baldwin.cx> To: John Baldwin X-Mailer: Apple Mail (2.3445.6.18) X-Mailman-Approved-At: Fri, 18 May 2018 23:25:13 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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 May 2018 23:07:20 -0000 > On Apr 18, 2018, at 1:42 PM, John Baldwin wrote: >>=20 >> Chenged made for it was >>=20 >> Index: sys/x86/x86/nexus.c >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> --- sys/x86/x86/nexus.c (revision 332663) >> +++ sys/x86/x86/nexus.c (working copy) >> @@ -698,7 +698,7 @@ >> { >>=20 >> if (rman_manage_region(&irq_rman, irq, irq) !=3D 0) >> - panic("%s: failed", __func__); >> + panic("%s: failed irq is: %lu", __func__, irq); >> } >=20 > Ohhhh, this is a different issue. Sorry. As a hack, try changing > 'FIRST_MSI_INT' to 512 in sys/amd64/include/intr_machdep.h. The issue > is that some systems now include more than 256 interrupt pins on I/O > APICs, so IRQ 256 is already reserved for use by one of those > interrupt pins. The real fix is that I need to make FIRST_MSI_INT > dynamic instead of a constant and just define it as the first free IRQ > after the I/O APICs have probed. I'm testing a very large AMD Epyc system, and I had to change = FIRST_MSI_INT to 768, but that fixed this issue for me. From owner-freebsd-current@freebsd.org Fri May 18 23:41:55 2018 Return-Path: Delivered-To: freebsd-current@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 4C081EE06AF; Fri, 18 May 2018 23:41:55 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from mx2.catspoiler.org (mx2.catspoiler.org [IPv6:2607:f740:16::d18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "amnesiac", Issuer "amnesiac" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id D2C806FD84; Fri, 18 May 2018 23:41:54 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from gw.catspoiler.org ([76.212.85.177]) by mx2.catspoiler.org (8.15.2/8.15.2) with ESMTPS id w4INhT5C040408 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Fri, 18 May 2018 23:43:31 GMT (envelope-from truckman@FreeBSD.org) Received: from mousie.catspoiler.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.15.2/8.15.2) with ESMTPS id w4INfiAM013131 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 18 May 2018 16:41:45 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Date: Fri, 18 May 2018 16:41:38 -0700 (PDT) From: Don Lewis Subject: Re: [RFC] Deprecation and removal of the drm2 driver To: Warner Losh cc: Steve Kargl , Andreas Nilsson , FreeBSD X11 mailing list , Current FreeBSD In-Reply-To: Message-ID: References: <3a5edc5c-3caa-830b-4bd9-53ff52feb8a7@freebsd.org> <20180518193009.GA88432@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Content-Disposition: INLINE X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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 May 2018 23:41:55 -0000 On 18 May, Warner Losh wrote: > On Fri, May 18, 2018 at 1:30 PM, Steve Kargl < > sgk@troutmask.apl.washington.edu> wrote: >=20 >> On Fri, May 18, 2018 at 09:14:24PM +0200, Andreas Nilsson wrote: >> > On Fri, May 18, 2018, 20:00 Niclas Zeising wrote= : >> > >> > > I propose that we remove the old drm2 driver (sys/dev/drm2) from >> > > FreeBSD. I suggest the driver is marked as deprecated in 11.x and >> > > removed from 12.0, as was done for other drivers recently. Some >> > > background and rationale: >> > > >> > > The drm2 driver was the original port of a KMS driver to FreeBSD. I= t >> > > was done by Konstantin Belousov to support Intel graphics cards, and >> > > later extended by Jean-S=E9bastien P=E9dron as well as Konstantin to= match >> > > what's in Linux 3.8. This included unstable support from Haswell, b= ut >> > > nothing newer than that. >> > > >> > > For quite some time now we have had the graphics/drm-stable-kmod and >> > > graphics/drm-next-kmods which provides support for modern AMD and In= tel >> > > graphics cards. These ports, together with the linuxkpi, or lkpi, h= as >> > > made it significantly easier to port and update our graphics drivers= . >> > > Further, these new drivers cover the same drivers as the old drm2 >> driver. >> > > >> > > What does the community think? Is there anyone still using the drm2 >> > > driver on 12-CURRENT? If so, what is preventing you from switching = to >> > > the port? >> > > >> > > Thank you >> > > Regards >> > > -- >> > > Niclas Zeising >> > > FreeBSD x11/graphics team >> > > _______________________________________________ >> > > 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" >> > > >> > >> > Sounds good ( deprecate resp remove ). It causes more confusion and >> > problems and it solves nothing. >> > >> >> Check the Makefiles >> >> % more /usr/ports/graphics/drm-next-kmod/Makefile >> >> ONLY_FOR_ARCHS=3D amd64 >> ONLY_FOR_ARCHS_REASON=3D the new KMS components are only supported on a= md64 >> >> Not to ia32 friendly. >> >=20 > So do people use i386 for desktop? And need the latest KMS stuff? I use it on my Pentium-M laptop. I don't need the latest KMS stuff, but I do need X11 so that I can use a browser, vncviewer, and a few terminal windows. Falling back to VESA resolution would suck. It's currently running 11.0-STABLE. I'm planning on migrating everything over to 12.0 sometime after 12.0-RELEASE. I have one other i386-class machine, but it only needs a text console. Everything else here is amd64. From owner-freebsd-current@freebsd.org Sat May 19 03:56:59 2018 Return-Path: Delivered-To: freebsd-current@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 369E2EEB14A; Sat, 19 May 2018 03:56:59 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.netplex.net (mail.netplex.net [204.213.176.9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.netplex.net", Issuer "RapidSSL RSA CA 2018" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D50FE79DAC; Sat, 19 May 2018 03:56:58 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from [10.0.0.52] (ip-414b102e.ct.fixed.ntplx.com [65.75.16.46]) (authenticated bits=0) by mail.netplex.net (8.15.1/8.15.1/NETPLEX) with ESMTPSA id w4J3usks061832 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 18 May 2018 23:56:54 -0400 X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.netplex.net) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (mail.netplex.net [204.213.176.9]); Fri, 18 May 2018 23:56:55 -0400 (EDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (1.0) Subject: Re: [RFC] Deprecation and removal of the drm2 driver From: Daniel Eischen X-Mailer: iPhone Mail (15E302) In-Reply-To: <201805182227.w4IMRhCU033315@slippy.cwsent.com> Date: Fri, 18 May 2018 23:56:54 -0400 Cc: Warner Losh , FreeBSD X11 mailing list , Current FreeBSD , Steve Kargl Content-Transfer-Encoding: quoted-printable Message-Id: <4A51EFFA-CAB7-44C6-9FC4-A5B95B5389F7@freebsd.org> References: <201805182227.w4IMRhCU033315@slippy.cwsent.com> To: Cy Schubert X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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: Sat, 19 May 2018 03:56:59 -0000 > On May 18, 2018, at 6:27 PM, Cy Schubert wrote= : >=20 > In message , Daniel=20 > Eischen wr > ites: >>> On Fri, 18 May 2018, Warner Losh wrote: >>>=20 >>> On Fri, May 18, 2018 at 1:30 PM, Steve Kargl < >>> sgk@troutmask.apl.washington.edu> wrote: >>>>=20 >>>> Check the Makefiles >>>>=20 >>>> % more /usr/ports/graphics/drm-next-kmod/Makefile >>>>=20 >>>> ONLY_FOR_ARCHS=3D amd64 >>>> ONLY_FOR_ARCHS_REASON=3D the new KMS components are only supported on a= md64 >>>>=20 >>>> Not to ia32 friendly. >>>>=20 >>>=20 >>> So do people use i386 for desktop? And need the latest KMS stuff? >>=20 >> I can easily imagine an embedded x86 kiosk type appliance. Does >> basic xorg stuff work without drm? >=20 > Yes, with VESA, albeit aspect ratios are off. I'm using drm2 with an AMD (n=C3=A9e ATI) Radeon 4850 (RV770), AGP. This is= on an amd64 somewhat old -current system. Is this supported by the drm-nex= t-kmod port? -- DE= From owner-freebsd-current@freebsd.org Sat May 19 10:27:44 2018 Return-Path: Delivered-To: freebsd-current@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 8546AEF5885; Sat, 19 May 2018 10:27:44 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [IPv6:2a01:4f8:c17:6c4b::2]) (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 1D95268ACD; Sat, 19 May 2018 10:27:44 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.128.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 6CAE82605CA; Sat, 19 May 2018 12:27:41 +0200 (CEST) Subject: Re: [RFC] Deprecation and removal of the drm2 driver To: Daniel Eischen , Cy Schubert Cc: Warner Losh , FreeBSD X11 mailing list , Current FreeBSD , Steve Kargl References: <201805182227.w4IMRhCU033315@slippy.cwsent.com> <4A51EFFA-CAB7-44C6-9FC4-A5B95B5389F7@freebsd.org> From: Hans Petter Selasky Message-ID: <00cab89b-b6cc-7ab3-18f3-4eac74871478@selasky.org> Date: Sat, 19 May 2018 12:27:33 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <4A51EFFA-CAB7-44C6-9FC4-A5B95B5389F7@freebsd.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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: Sat, 19 May 2018 10:27:44 -0000 On 05/19/18 05:56, Daniel Eischen wrote: >> Yes, with VESA, albeit aspect ratios are off. > I'm using drm2 with an AMD (née ATI) Radeon 4850 (RV770), AGP. This is on an amd64 somewhat old -current system. Is this supported by the drm-next-kmod port? I've used drm2 in the past, but noticed the anti-flicker support features are not as good as in the drm-next-kmod. Also video support is much better, external displays and so on, not only getting video on the built-in display but also various kinds of VGA, HDMI and displayports. --HPS From owner-freebsd-current@freebsd.org Sat May 19 12:30:39 2018 Return-Path: Delivered-To: freebsd-current@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 D5683EAC75C; Sat, 19 May 2018 12:30:39 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (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 6A55B6DE0F; Sat, 19 May 2018 12:30:39 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1fK10M-0007iF-9E; Sat, 19 May 2018 15:30:34 +0300 Date: Sat, 19 May 2018 15:30:34 +0300 From: Slawa Olhovchenkov To: Warner Losh Cc: Steve Kargl , Andreas Nilsson , FreeBSD X11 mailing list , Current FreeBSD Subject: Re: [RFC] Deprecation and removal of the drm2 driver Message-ID: <20180519123034.GB1954@zxy.spb.ru> References: <3a5edc5c-3caa-830b-4bd9-53ff52feb8a7@freebsd.org> <20180518193009.GA88432@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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: Sat, 19 May 2018 12:30:40 -0000 On Fri, May 18, 2018 at 02:03:32PM -0600, Warner Losh wrote: > > Check the Makefiles > > > > % more /usr/ports/graphics/drm-next-kmod/Makefile > > > > ONLY_FOR_ARCHS= amd64 > > ONLY_FOR_ARCHS_REASON= the new KMS components are only supported on amd64 > > > > Not to ia32 friendly. > > > > So do people use i386 for desktop? And need the latest KMS stuff? Removing drm2 remove all _graphics_ stuff. I am have i386 notebook, I am don't need lates KMS, I am need just X11/mplayer/firefox/skype. From owner-freebsd-current@freebsd.org Sat May 19 12:30:56 2018 Return-Path: Delivered-To: freebsd-current@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 4F218EAC830; Sat, 19 May 2018 12:30:56 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (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 D98AB6DE9D; Sat, 19 May 2018 12:30:55 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1fK0y9-0007hE-Bh; Sat, 19 May 2018 15:28:17 +0300 Date: Sat, 19 May 2018 15:28:17 +0300 From: Slawa Olhovchenkov To: freebsd-x11@freebsd.org Cc: freebsd-current@freebsd.org Subject: Re: [RFC] Deprecation and removal of the drm2 driver Message-ID: <20180519122817.GA1954@zxy.spb.ru> References: <3a5edc5c-3caa-830b-4bd9-53ff52feb8a7@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <3a5edc5c-3caa-830b-4bd9-53ff52feb8a7@freebsd.org> User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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: Sat, 19 May 2018 12:30:56 -0000 On Fri, May 18, 2018 at 07:58:10PM +0200, Niclas Zeising wrote: > [ Cross posted to freebsd-current@ and freebsd-x11@. Please respect > reply-to and send all replies to freebsd-x11@. Thanks! ] > > > Hi! > I propose that we remove the old drm2 driver (sys/dev/drm2) from > FreeBSD. I suggest the driver is marked as deprecated in 11.x and > removed from 12.0, as was done for other drivers recently. Some > background and rationale: > > The drm2 driver was the original port of a KMS driver to FreeBSD. It > was done by Konstantin Belousov to support Intel graphics cards, and > later extended by Jean-Sébastien Pédron as well as Konstantin to match > what's in Linux 3.8. This included unstable support from Haswell, but > nothing newer than that. > > For quite some time now we have had the graphics/drm-stable-kmod and > graphics/drm-next-kmods which provides support for modern AMD and Intel > graphics cards. These ports, together with the linuxkpi, or lkpi, has What about old graphics card? I am have notebook w/ i945 chipset, is this supported by graphics/drm-*? And what about nvidia? (sorry, I am not developer this drivers, I am just user, I am don't know what need for nvidia work etc) > made it significantly easier to port and update our graphics drivers. > Further, these new drivers cover the same drivers as the old drm2 driver. > > What does the community think? Is there anyone still using the drm2 > driver on 12-CURRENT? If so, what is preventing you from switching to > the port? From owner-freebsd-current@freebsd.org Sat May 19 18:38:24 2018 Return-Path: Delivered-To: freebsd-current@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 A39B2EDDB5E; Sat, 19 May 2018 18:38:24 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5E2B579E6B; Sat, 19 May 2018 18:38:24 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1354) id 3CC999D75; Sat, 19 May 2018 18:38:24 +0000 (UTC) From: Jan Beich To: Slawa Olhovchenkov Cc: freebsd-x11@freebsd.org, freebsd-current@freebsd.org Subject: Re: [RFC] Deprecation and removal of the drm2 driver References: <3a5edc5c-3caa-830b-4bd9-53ff52feb8a7@freebsd.org> <20180519122817.GA1954@zxy.spb.ru> Date: Sat, 19 May 2018 20:38:20 +0200 In-Reply-To: <20180519122817.GA1954@zxy.spb.ru> (Slawa Olhovchenkov's message of "Sat, 19 May 2018 15:28:17 +0300") Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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: Sat, 19 May 2018 18:38:24 -0000 Slawa Olhovchenkov writes: > On Fri, May 18, 2018 at 07:58:10PM +0200, Niclas Zeising wrote: > >> [ Cross posted to freebsd-current@ and freebsd-x11@. Please respect=20 >> reply-to and send all replies to freebsd-x11@. Thanks! ] >>=20 >>=20 >> Hi! >> I propose that we remove the old drm2 driver (sys/dev/drm2) from=20 >> FreeBSD. I suggest the driver is marked as deprecated in 11.x and=20 >> removed from 12.0, as was done for other drivers recently. Some=20 >> background and rationale: >>=20 >> The drm2 driver was the original port of a KMS driver to FreeBSD. It=20 >> was done by Konstantin Belousov to support Intel graphics cards, and=20 >> later extended by Jean-S=C3=A9bastien P=C3=A9dron as well as Konstantin = to match=20 >> what's in Linux 3.8. This included unstable support from Haswell, but=20 >> nothing newer than that. >>=20 >> For quite some time now we have had the graphics/drm-stable-kmod and=20 >> graphics/drm-next-kmods which provides support for modern AMD and Intel= =20 >> graphics cards. These ports, together with the linuxkpi, or lkpi, has=20 > > What about old graphics card? I am have notebook w/ i945 chipset, is > this supported by graphics/drm-*? > > And what about nvidia? > (sorry, I am not developer this drivers, I am just user, I am don't > know what need for nvidia work etc) NVIDIA dropped 32bit driver since 396.* series. None of x11/nvidia-driver* currently depend on either drm.ko or drm2.ko. However, Linux driver appears to depend on DRM/KMS since 364.12. From owner-freebsd-current@freebsd.org Sat May 19 18:43:59 2018 Return-Path: Delivered-To: freebsd-current@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 51B98EDE21F; Sat, 19 May 2018 18:43:59 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (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 DDA677A60B; Sat, 19 May 2018 18:43:58 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1fK6pf-0009Vr-NO; Sat, 19 May 2018 21:43:55 +0300 Date: Sat, 19 May 2018 21:43:55 +0300 From: Slawa Olhovchenkov To: Jan Beich Cc: freebsd-x11@freebsd.org, freebsd-current@freebsd.org Subject: Re: [RFC] Deprecation and removal of the drm2 driver Message-ID: <20180519184355.GD1926@zxy.spb.ru> References: <3a5edc5c-3caa-830b-4bd9-53ff52feb8a7@freebsd.org> <20180519122817.GA1954@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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: Sat, 19 May 2018 18:43:59 -0000 On Sat, May 19, 2018 at 08:38:20PM +0200, Jan Beich wrote: > Slawa Olhovchenkov writes: > > > On Fri, May 18, 2018 at 07:58:10PM +0200, Niclas Zeising wrote: > > > >> [ Cross posted to freebsd-current@ and freebsd-x11@. Please respect > >> reply-to and send all replies to freebsd-x11@. Thanks! ] > >> > >> > >> Hi! > >> I propose that we remove the old drm2 driver (sys/dev/drm2) from > >> FreeBSD. I suggest the driver is marked as deprecated in 11.x and > >> removed from 12.0, as was done for other drivers recently. Some > >> background and rationale: > >> > >> The drm2 driver was the original port of a KMS driver to FreeBSD. It > >> was done by Konstantin Belousov to support Intel graphics cards, and > >> later extended by Jean-Sébastien Pédron as well as Konstantin to match > >> what's in Linux 3.8. This included unstable support from Haswell, but > >> nothing newer than that. > >> > >> For quite some time now we have had the graphics/drm-stable-kmod and > >> graphics/drm-next-kmods which provides support for modern AMD and Intel > >> graphics cards. These ports, together with the linuxkpi, or lkpi, has > > > > What about old graphics card? I am have notebook w/ i945 chipset, is > > this supported by graphics/drm-*? > > > > And what about nvidia? > > (sorry, I am not developer this drivers, I am just user, I am don't > > know what need for nvidia work etc) > > NVIDIA dropped 32bit driver since 396.* series. None of x11/nvidia-driver* > currently depend on either drm.ko or drm2.ko. However, Linux driver > appears to depend on DRM/KMS since 364.12. Some of my hardware supported only by nvidia 340.106. From owner-freebsd-current@freebsd.org Sat May 19 19:57:49 2018 Return-Path: Delivered-To: freebsd-current@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 DC1B1EE1F8D; Sat, 19 May 2018 19:57:49 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [192.108.105.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.soaustin.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DE1797D933; Sat, 19 May 2018 19:57:48 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from lonesome.com (bones.soaustin.net [192.108.105.22]) by mail.soaustin.net (Postfix) with ESMTPSA id 9063ABF4; Sat, 19 May 2018 14:57:47 -0500 (CDT) Date: Sat, 19 May 2018 14:57:46 -0500 From: Mark Linimon To: Daniel Eischen Cc: Warner Losh , Steve Kargl , Andreas Nilsson , FreeBSD X11 mailing list , Current FreeBSD Subject: Re: [RFC] Deprecation and removal of the drm2 driver Message-ID: <20180519195746.GB8418@lonesome.com> References: <3a5edc5c-3caa-830b-4bd9-53ff52feb8a7@freebsd.org> <20180518193009.GA88432@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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: Sat, 19 May 2018 19:57:50 -0000 On Fri, May 18, 2018 at 04:19:21PM -0400, Daniel Eischen wrote: > I can easily imagine an embedded x86 kiosk type appliance. We need to evaluate the tradeoff of "what we can imagine someone will do with FreeBSD" vs. "what are people using with FreeBSD right now." mcl From owner-freebsd-current@freebsd.org Sat May 19 21:23:07 2018 Return-Path: Delivered-To: freebsd-current@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 04833EE4977; Sat, 19 May 2018 21:23:07 +0000 (UTC) (envelope-from agapon@gmail.com) Received: from mail-lf0-f66.google.com (mail-lf0-f66.google.com [209.85.215.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5B7C880C58; Sat, 19 May 2018 21:23:06 +0000 (UTC) (envelope-from agapon@gmail.com) Received: by mail-lf0-f66.google.com with SMTP id h197-v6so18748425lfg.11; Sat, 19 May 2018 14:23:06 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:openpgp:autocrypt :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=Yy8eQw23LRo7m0YltMaTogBgBSOK18MY4xt35BXOAkw=; b=Z4bQVcNl60mUeb+FISeTkZfGm6mJ5h/aqjNnJuqEpZQJ/ihC5pJq2rUzhLMQQ1in3w 9HovbD9kFfo9TfI8+fcRoytr5gI6B7z8sMwtJ5ng6qzitbyzfGYTJZ9P+Nl54/YY3E4h CTJsQu/2jMDFKAQKF9H65dTAPrSJkuXnd7xsqfnLcO9YsvHL1kePQPW0LckpofU4n0HJ t/a+RvYdOmFtS/jewC1LzmRRUbqIKiGQQNqz2SAZqBm2sxcZV2EHoO8mzPgFFeGK6Ip+ JDn2VIfL2StAMx4vJsn5AhAYQuDQvdhK2oLoIXn0yVrJhsg8jlOMQU+hI2WPM44+c2Yl fSZA== X-Gm-Message-State: ALKqPwdIOjeTAyQY7HA57eZpl4HdOVAOnFL234p7l7uOLi85qLDDajgO iwtfPHate91cfoLfLfgpK4whpH6Y X-Google-Smtp-Source: AB8JxZrGLze/2akb1tNZnQdvNATuvTNd/VfzOeeiGRyo3clM64BoKif1e8tltdYtKHhgi21H6rebLw== X-Received: by 2002:a19:9bd2:: with SMTP id d201-v6mr23264663lfe.52.1526764978931; Sat, 19 May 2018 14:22:58 -0700 (PDT) Received: from [192.168.0.88] (east.meadow.volia.net. [93.72.151.96]) by smtp.googlemail.com with ESMTPSA id y23-v6sm1820378ljh.88.2018.05.19.14.22.57 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 19 May 2018 14:22:58 -0700 (PDT) Subject: Re: [RFC] Deprecation and removal of the drm2 driver To: freebsd-x11@freebsd.org, freebsd-current@freebsd.org References: <3a5edc5c-3caa-830b-4bd9-53ff52feb8a7@freebsd.org> From: Andriy Gapon Openpgp: preference=signencrypt Autocrypt: addr=avg@FreeBSD.org; prefer-encrypt=mutual; keydata= xsFNBFm4LIgBEADNB/3lT7f15UKeQ52xCFQx/GqHkSxEdVyLFZTmY3KyNPQGBtyvVyBfprJ7 mAeXZWfhat6cKNRAGZcL5EmewdQuUfQfBdYmKjbw3a9GFDsDNuhDA2QwFt8BmkiVMRYyvI7l N0eVzszWCUgdc3qqM6qqcgBaqsVmJluwpvwp4ZBXmch5BgDDDb1MPO8AZ2QZfIQmplkj8Y6Z AiNMknkmgaekIINSJX8IzRzKD5WwMsin70psE8dpL/iBsA2cpJGzWMObVTtCxeDKlBCNqM1i gTXta1ukdUT7JgLEFZk9ceYQQMJJtUwzWu1UHfZn0Fs29HTqawfWPSZVbulbrnu5q55R4PlQ /xURkWQUTyDpqUvb4JK371zhepXiXDwrrpnyyZABm3SFLkk2bHlheeKU6Yql4pcmSVym1AS4 dV8y0oHAfdlSCF6tpOPf2+K9nW1CFA8b/tw4oJBTtfZ1kxXOMdyZU5fiG7xb1qDgpQKgHUX8 7Rd2T1UVLVeuhYlXNw2F+a2ucY+cMoqz3LtpksUiBppJhw099gEXehcN2JbUZ2TueJdt1FdS ztnZmsHUXLxrRBtGwqnFL7GSd6snpGIKuuL305iaOGODbb9c7ne1JqBbkw1wh8ci6vvwGlzx rexzimRaBzJxlkjNfMx8WpCvYebGMydNoeEtkWldtjTNVsUAtQARAQABzR5BbmRyaXkgR2Fw b24gPGF2Z0BGcmVlQlNELm9yZz7CwZQEEwEIAD4WIQS+LEO7ngQnXA4Bjr538m7TUc1yjwUC WbgsiAIbIwUJBaOagAULCQgHAgYVCAkKCwIEFgIDAQIeAQIXgAAKCRB38m7TUc1yj+JAEACV l9AK/nOWAt/9cufV2fRj0hdOqB1aCshtSrwHk/exXsDa4/FkmegxXQGY+3GWX3deIyesbVRL rYdtdK0dqJyT1SBqXK1h3/at9rxr9GQA6KWOxTjUFURsU7ok/6SIlm8uLRPNKO+yq0GDjgaO LzN+xykuBA0FlhQAXJnpZLcVfPJdWv7sSHGedL5ln8P8rxR+XnmsA5TUaaPcbhTB+mG+iKFj GghASDSfGqLWFPBlX/fpXikBDZ1gvOr8nyMY9nXhgfXpq3B6QCRYKPy58ChrZ5weeJZ29b7/ QdEO8NFNWHjSD9meiLdWQaqo9Y7uUxN3wySc/YUZxtS0bhAd8zJdNPsJYG8sXgKjeBQMVGuT eCAJFEYJqbwWvIXMfVWop4+O4xB+z2YE3jAbG/9tB/GSnQdVSj3G8MS80iLS58frnt+RSEw/ psahrfh0dh6SFHttE049xYiC+cM8J27Aaf0i9RflyITq57NuJm+AHJoU9SQUkIF0nc6lfA+o JRiyRlHZHKoRQkIg4aiKaZSWjQYRl5Txl0IZUP1dSWMX4s3XTMurC/pnja45dge/4ESOtJ9R 8XuIWg45Oq6MeIWdjKddGhRj3OohsltKgkEU3eLKYtB6qRTQypHHUawCXz88uYt5e3w4V16H lCpSTZV/EVHnNe45FVBlvK7k7HFfDDkryM7BTQRZuCyIARAAlq0slcsVboY/+IUJdcbEiJRW be9HKVz4SUchq0z9MZPX/0dcnvz/gkyYA+OuM78dNS7Mbby5dTvOqfpLJfCuhaNYOhlE0wY+ 1T6Tf1f4c/uA3U/YiadukQ3+6TJuYGAdRZD5EqYFIkreARTVWg87N9g0fT9BEqLw9lJtEGDY EWUE7L++B8o4uu3LQFEYxcrb4K/WKmgtmFcm77s0IKDrfcX4doV92QTIpLiRxcOmCC/OCYuO jB1oaaqXQzZrCutXRK0L5XN1Y1PYjIrEzHMIXmCDlLYnpFkK+itlXwlE2ZQxkfMruCWdQXye syl2fynAe8hvp7Mms9qU2r2K9EcJiR5N1t1C2/kTKNUhcRv7Yd/vwusK7BqJbhlng5ZgRx0m WxdntU/JLEntz3QBsBsWM9Y9wf2V4tLv6/DuDBta781RsCB/UrU2zNuOEkSixlUiHxw1dccI 6CVlaWkkJBxmHX22GdDFrcjvwMNIbbyfQLuBq6IOh8nvu9vuItup7qemDG3Ms6TVwA7BD3j+ 3fGprtyW8Fd/RR2bW2+LWkMrqHffAr6Y6V3h5kd2G9Q8ZWpEJk+LG6Mk3fhZhmCnHhDu6CwN MeUvxXDVO+fqc3JjFm5OxhmfVeJKrbCEUJyM8ESWLoNHLqjywdZga4Q7P12g8DUQ1mRxYg/L HgZY3zfKOqcAEQEAAcLBfAQYAQgAJhYhBL4sQ7ueBCdcDgGOvnfybtNRzXKPBQJZuCyIAhsM BQkFo5qAAAoJEHfybtNRzXKPBVwQAKfFy9P7N3OsLDMB56A4Kf+ZT+d5cIx0Yiaf4n6w7m3i ImHHHk9FIetI4Xe54a2IXh4Bq5UkAGY0667eIs+Z1Ea6I2i27Sdo7DxGwq09Qnm/Y65ADvXs 3aBvokCcm7FsM1wky395m8xUos1681oV5oxgqeRI8/76qy0hD9WR65UW+HQgZRIcIjSel9vR XDaD2HLGPTTGr7u4v00UeTMs6qvPsa2PJagogrKY8RXdFtXvweQFz78NbXhluwix2Tb9ETPk LIpDrtzV73CaE2aqBG/KrboXT2C67BgFtnk7T7Y7iKq4/XvEdDWscz2wws91BOXuMMd4c/c4 OmGW9m3RBLufFrOag1q5yUS9QbFfyqL6dftJP3Zq/xe+mr7sbWbhPVCQFrH3r26mpmy841ym dwQnNcsbIGiBASBSKksOvIDYKa2Wy8htPmWFTEOPRpFXdGQ27awcjjnB42nngyCK5ukZDHi6 w0qK5DNQQCkiweevCIC6wc3p67jl1EMFY5+z+zdTPb3h7LeVnGqW0qBQl99vVFgzLxchKcl0 R/paSFgwqXCZhAKMuUHncJuynDOP7z5LirUeFI8qsBAJi1rXpQoLJTVcW72swZ42IdPiboqx NbTMiNOiE36GqMcTPfKylCbF45JNX4nF9ElM0E+Y8gi4cizJYBRr2FBJgay0b9Cp Message-ID: <27f181ef-e083-db30-7c4c-58e6d624276b@FreeBSD.org> Date: Sun, 20 May 2018 00:22:56 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <3a5edc5c-3caa-830b-4bd9-53ff52feb8a7@freebsd.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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: Sat, 19 May 2018 21:23:07 -0000 On 18/05/2018 20:58, Niclas Zeising wrote: > [ Cross posted to freebsd-current@ and freebsd-x11@.  Please respect reply-to > and send all replies to freebsd-x11@.  Thanks! ] > > > Hi! > I propose that we remove the old drm2 driver (sys/dev/drm2) from FreeBSD.  I > suggest the driver is marked as deprecated in 11.x and removed from 12.0, as was > done for other drivers recently.  Some background and rationale: > > The drm2 driver was the original port of a KMS driver to FreeBSD.  It was done > by Konstantin Belousov to support Intel graphics cards, and later extended by > Jean-Sébastien Pédron as well as Konstantin to match what's in Linux 3.8.  This > included unstable support from Haswell, but nothing newer than that. > > For quite some time now we have had the graphics/drm-stable-kmod and > graphics/drm-next-kmods which provides support for modern AMD and Intel graphics > cards.  These ports, together with the linuxkpi, or lkpi, has made it > significantly easier to port and update our graphics drivers. Further, these new > drivers cover the same drivers as the old drm2 driver. > > What does the community think?  Is there anyone still using the drm2 driver on > 12-CURRENT? Please count me as one. > If so, what is preventing you from switching to the port? Suspend / resume does not work with my hardware: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ panic: implment me!! cpuid = 0 time = 1526764859 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe004d1c2280 vpanic() at vpanic+0x1a3/frame 0xfffffe004d1c22e0 panic() at panic+0x43/frame 0xfffffe004d1c2340 linux_pci_save_state() at linux_pci_save_state+0x12/frame 0xfffffe004d1c2350 radeon_suspend_kms() at radeon_suspend_kms+0x524/frame 0xfffffe004d1c23a0 linux_pci_suspend() at linux_pci_suspend+0x6e/frame 0xfffffe004d1c23d0 ... ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The hardware is old, supported by radeonkms as opposed to amdgpu, but still.. Also, last time I checked audio over HDMI did not work, but I haven't tested the latest version yet. Finally, a counter-question, does keeping the code in its current state (unsupported, but without explicitly stating so) obstruct the work on the new code? -- Andriy Gapon