From owner-freebsd-current@freebsd.org Sat Oct 6 10:54: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 5E2B210B615C for ; Sat, 6 Oct 2018 10:54:13 +0000 (UTC) (envelope-from grahamperrin@gmail.com) Received: from mail-wr1-x435.google.com (mail-wr1-x435.google.com [IPv6:2a00:1450:4864:20::435]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C68B270628 for ; Sat, 6 Oct 2018 10:54:12 +0000 (UTC) (envelope-from grahamperrin@gmail.com) Received: by mail-wr1-x435.google.com with SMTP id 63-v6so15921406wra.11 for ; Sat, 06 Oct 2018 03:54:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=EMrNSqcyFfCPwbhrDAxV1LZO0w4QOInk9irn1Jnd5V0=; b=Qso8Gwr74jclIq33TAIajc9w5hJ9kj9yfp/uGV0K8FUQG8J4qxgZD0atw77nl80nzD Rx/zY1yfenv0P1oIF5+IVX5ab8QGeiY4ycf2W0IrKCk1Ob1AUQ5TP3tLG/mOO9FCIJhS NDU+osmEG34edtlrp4J20SrrJZRV3X3qxmo0lHNdJWEsYS7jcbPPj1OF5oD4uY3w/iWi dl3CxoZYCaF9W+kbvbPk5N64//ttga+d+J15+JBdxzaCJrVCeppDxQPwbMI8LIetJhMG 927+jF56J0x6pT0Dw00t27WMO19bNxQ8316asAEIzGJ3P4nPWAgw5KQu60ssVIA78XGZ gyRA== 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:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=EMrNSqcyFfCPwbhrDAxV1LZO0w4QOInk9irn1Jnd5V0=; b=bQKdSwSO9B83EOpjh261c7z1y0AlR+0w+fKxJHE2kiyaDn0xi0QLZEhel4SzpVFmkx 2xKcGLhE1/XZu2qwueHCuox3qLRPIg7ST1QMlcns4uIlV8bYO1X/8livqaf/b2ybbsIl ZWD0fDK2ry5pJcp/P0ms4xY0Jq7yRl/oNvnAeIcfUtRcBUxPo3pnGFdWCoIvvggcTg4I nHgeNO4f2MHcLRyJhdzrtEYcUBL68vNyeVB15kEVH42G81ooTBzeaZBZozZlrubX3jbR bjU96A1apRr/yJ0DqUH0grAw3Nh70SghA3T1lSEWYCnCqyJUp1+yK6tcD+9j4XEKnLdB zp6A== X-Gm-Message-State: ABuFfogd2HNaYF/Hqn8Ufbquujrk93BuKFINA/BMrstgQHZQaKXDFAH3 hTfRKoFFzN+HbhQSq3/BmjlyIC9/ X-Google-Smtp-Source: ACcGV60nFqlshjaNHdnthinflmeDW7SCFOQjVj2qPW03+YPuGL3lbzdYzio9wS6k3o2QTvWqmC9S2g== X-Received: by 2002:adf:9592:: with SMTP id p18-v6mr11504219wrp.202.1538823251156; Sat, 06 Oct 2018 03:54:11 -0700 (PDT) Received: from [192.168.1.231] (79-66-139-63.dynamic.dsl.as9105.com. [79.66.139.63]) by smtp.gmail.com with ESMTPSA id p62-v6sm21790453wrc.97.2018.10.06.03.54.09 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 06 Oct 2018 03:54:09 -0700 (PDT) Subject: Re: Radeon HD 7570M: drm: deep frustration with r339186 To: Johannes Lundberg Cc: freebsd-current References: <93fcf295-1dae-12d4-5530-ef0c55bd8cc2@gmail.com> <0aa72278-c17b-0bd7-1f5b-960366890426@nomadlogic.org> <549ab380-60a8-c919-980a-b5b6a541e3c9@gmail.com> <38395f26-faa5-e56e-6a4c-3e72fbfc2a73@gmail.com> <88d6b0fc-7843-4cb0-dd05-99daf463794e@gmail.com> <3a204983-d06b-1a6c-dd48-911a8d6525dc@nomadlogic.org> From: Graham Perrin Message-ID: Date: Sat, 6 Oct 2018 11:54:08 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 06 Oct 2018 10:54:13 -0000 On 06/10/2018 10:05, Johannes Lundberg wrote: > … Regarding instability with CURRENT. When something changes in CURRENT that might affect the drm drivers there's always a delay until the drm-kmod packages have been rebuilt against the new source. That's fine, thanks 👍 My frustration was less about instability (not at all about any delay); more about the sense that I might not _predictably_ get myself back to a working desktop environment. That sense was extraordinary but :-) I'm not complaining, I know to expect the unexpected with -CURRENT. > If you're frequently updating your -CURRENT system, it's safest to build drm-kmod from source at the same time. Either with ports or from the github repo. I built with poudriere but forgot, the jail was not particularly recent. Updating now, poudriere jail -u -j current > We're working on trying to reduce this lag but to avoid it completely is impossible when living in -CURRENT. Understood. Not a problem for me. ---- Incidentally re: suspend and resume, I think I stumbled across a good workaround for the current situation. I'll await a reply from Pete Wright (to my previous e-mail) before sharing. Best, Graham