From owner-freebsd-current@freebsd.org Sat Oct 6 09:06: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 38D1C10B34C6 for ; Sat, 6 Oct 2018 09:06:22 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-wm1-x331.google.com (mail-wm1-x331.google.com [IPv6:2a00:1450:4864:20::331]) (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 9603F8C0AD for ; Sat, 6 Oct 2018 09:06:21 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-wm1-x331.google.com with SMTP id z25-v6so5232712wmf.1 for ; Sat, 06 Oct 2018 02:06:21 -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=//CiTj2DTGoypknVMAhFYEQOGmRXS+6CPVoeo9uLP9U=; b=KFy9LvlLRYmMrXzZ/u+MLjc+hfdQZQpczEfawlElNQGYoWu7kxpsKCneh2WYSOIuvJ HjdU48BnKxeMEm/WIfMO/cG7eymP1DztaFDq7XCoWNyePL3DikscqHfvlYmOFWAPXxUQ DnCFCTvr6ftrwEAGCSSxHd5Q3/TI3BwoDDyUlDs1IqMyw1aOiRKoBCftK9lTWJt/sWiJ D6GRKpPWiG+2Ww4q4KFa4gEGu95AISNNT7Zm5yCj165M+tay7nmyX+wpQ4IHrRrRqGzy 1BXCIqnbJolQVAHgVAnelwIVhwN9QaQGMoxN5cM39GA2h7uXI3CFHjl4Gv/v8I24RO3x 7b6g== 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=//CiTj2DTGoypknVMAhFYEQOGmRXS+6CPVoeo9uLP9U=; b=a2NPZAESCmuFRtR0FJXINe83OlcUd8zSo4IQBUc2asBjH39/41pxNeTTeOR9QRGZKj IyycaLETdSlTgUhWgphsPEpzsdx5yjRn6YL1XVhiEkQv3bcE5a5WSIjagupleqhZKPIk XYGbSzJ6EkFTOlreSGHjXxAhxn7WTC/DsRlcEht4uQP7ao0vO0Wi7hfuNFwNUFkC+BfS Z2ZE2HEKzIgI9Q1qP4boDF9eZZ2/0lIMwLWEyre3sgA3pq37lmbVj83EU4mEQFTY9yJw 3C2k7zgiph1rtLAk2NjPBykKJD+AkaWQACxKYecO7h58MdVA6hv3vaQ9nBOiGkcf/vUa zHxQ== X-Gm-Message-State: ABuFfohb7M1EYoev8mY9Xyu3n8BUOzaj51nzqE2TAKvzGYdKp/fEWNdy ZfpYvXkze7QLpl51ThEQ3hrCRr0TOHmROey5wEs= X-Google-Smtp-Source: ACcGV613IX09WGZzM9juchI2jQYySPUISDFnF3EASPhU/dOTUaOcdph9zXQtfwIkzX9h60rkU7jBCiNjJxKCwPTEcVw= X-Received: by 2002:a1c:8cd2:: with SMTP id o201-v6mr9406230wmd.65.1538816780362; Sat, 06 Oct 2018 02:06:20 -0700 (PDT) MIME-Version: 1.0 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> In-Reply-To: <3a204983-d06b-1a6c-dd48-911a8d6525dc@nomadlogic.org> From: Johannes Lundberg Date: Sat, 6 Oct 2018 10:05:43 +0100 Message-ID: Subject: Re: Radeon HD 7570M: drm: deep frustration with r339186 To: Pete Wright Cc: Graham Perrin , freebsd-current Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.27 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 09:06:22 -0000 On Sat, Oct 6, 2018 at 7:19 AM Pete Wright wrote: > > On 10/5/18 6:34 PM, Graham Perrin wrote: > > On 23/09/2018 08:09, Graham Perrin wrote: > > > >> Re: Suspend, resume, UEFI, CSM, drm-stable-kmod and drm-next-kmod with > Radeon HD 7570M > >> =E2=80=A6 better without drm-next-kmod; and (as expected, given the pa= ckage > message) drm-stable-kmod has known problems with UEFI. > > Now (with r339186) it seems that drm-next-kmod is the only usable optio= n. > > > > However, I'm sorry to say: > > > > - it does feel regressive, compared to working without drm-next-kmod > with earlier versions of -CURRENT. > > > > I can no longer find a way to reliably suspend (sleep) the notebook. > > hey Graham - I'm struggling with suspend/resume issues as well on my end > with recent 12-ALPHA releases. can you verify that you can > suspend/resume without loading the radeonkms.ko (i believe that is what > you are using for gfx)? on my systems it's broken regardless if i load > the drm modules. > > also, what was the last version of CURRENT you were able to > suspend/resume with? > > > > At the time of writing my part-working configuration is as outlined > below. > > > > However =E2=80=93 frustratingly =E2=80=93 for a while, an hour or so ag= o, it seemed as > if the same configuration was useless; after a point, the screen would go > blank (grey) and things would progress no further e.g. no login manager > (sddm); no response to Control-Alt-F2; no response to Control-Alt-Delete. > The apparent unpredictability leading to a dead-end situation has created= a > sense of unease; now I'm genuinely afraid to test suspend :-( > > i believe johannes lundberg is working on a fix for this issue. i'm in > the same uneasy situation as you. the system i use for dogfooding is > also my main work laptop, and not having suspend/resume and other > instability like this is certainly not ideal. one potential fix > workaround we've found is to not load the module via "kld_list" but > rather load it by hand via "kldload" manually. i believe the bug is in > relation to how the BIOS allocates memory - i'll let him fill in details = :) > Hi This kld_list issue is only for newer Intel and drm-devel. 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. 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. We're working on trying to reduce this lag but to avoid it completely is impossible when living in -CURRENT. for me at least it looks like system instability when loading drm-next > kernels is separate from suspend/resume. but its certainly possible my > laptop is a snowflake :p > > hope this helps. > > -pete > > > -- > Pete Wright > pete@nomadlogic.org > @nomadlogicLA > > _______________________________________________ > 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= " >