Received: by 2002:a5d:925a:0:0:0:0:0 with SMTP id e26csp430523iol; Sat, 11 Jun 2022 07:43:12 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzJjehwfsMLkQaO9h6hBwuJ/n+nL057LdT1GtJ1lZYaZ1bTxZF4ofG2n7JvnxEiKGQfig4E X-Received: by 2002:a63:5e47:0:b0:401:a9bc:4add with SMTP id s68-20020a635e47000000b00401a9bc4addmr10356528pgb.306.1654958592549; Sat, 11 Jun 2022 07:43:12 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1654958592; cv=none; d=google.com; s=arc-20160816; b=nXLDZPAXHDuu5bzD+7APwNCpYR+tCzRunHLM21JR/G8UMIvWDjte4cXzuLVlL3G9TI 2o8lk6Eccxl5dURXGlcPg7i6I/rnGm4DFuYUkIgAVvvJ9eIpB3dKqyuXV7OiOqyBsW7k KaN1wZTzgzHZ63lJ4ZgAiH8EBJK2pO8d26t2XonZASafG1P92rckwyIF3fzc2xc1CBV8 WT9R1zIRmfP6jwF8ObEuEpOu49PFTNee2JZ0PmOp1uXcsjZ4k+yDaIYzNC6N1WCvm71B muT2ctvAxTDyKF0v5dc2R8WuNMAFDr5CxU6nn6fk1auYInbJPkhG9ZKoInFoEXefgyae /nfg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:cc:from :references:to:content-language:subject:user-agent:mime-version:date :message-id; bh=AZlJnUxbCzrrbH+KxXQZRrU4SbeqVr277jxW3+SvdIE=; b=SmOPqyMR7g3oH2pB1QbPVYWFAYY2EUSsBSekke1kKd3bL1RoNIwYGE6psE7g4wGe6n Vcq1rf6V0/JhJBHnWWny8lomyo4lCxVHL8+7Yeb8g29nL02gWlSYmrrJCnb1D0F5z+nW +t37Cx93QaPwu+OH+teb/fILqZ+ym76eacpXxZWlgvdTdcIyPenfPfb22IK0twKhT3bc JSDfVHrLf3YX5lZfN2kAs5SnPENMe6GJNsV9rSS5gMXtMKcBfZbATHHR1tPZ9hFWxyVB H631WuUzO21/vXZBiGt2jIcrrMWSC70LXHzpcaNdiM4uCt3DlKXuujTdzg/tmQf6bU6r OiwQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id p7-20020a631e47000000b003db0f2baa25si2699579pgm.90.2022.06.11.07.43.00; Sat, 11 Jun 2022 07:43:12 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233786AbiFKNxu (ORCPT + 99 others); Sat, 11 Jun 2022 09:53:50 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57708 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233574AbiFKNxs (ORCPT ); Sat, 11 Jun 2022 09:53:48 -0400 Received: from wp530.webpack.hosteurope.de (wp530.webpack.hosteurope.de [IPv6:2a01:488:42:1000:50ed:8234::]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 6AAC33F88F; Sat, 11 Jun 2022 06:53:46 -0700 (PDT) Received: from [2a02:8108:963f:de38:eca4:7d19:f9a2:22c5]; authenticated by wp530.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) id 1o01Ye-0006jb-NG; Sat, 11 Jun 2022 15:53:44 +0200 Message-ID: <84d01637-febb-f602-2d03-fe1600e85ae3@leemhuis.info> Date: Sat, 11 Jun 2022 15:53:44 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.10.0 Subject: Re: regression, 5.19.0-rc1 not powering off when hibernated Content-Language: en-US To: Ken Moffat , linux-kernel@vger.kernel.org, "regressions@lists.linux.dev" References: From: Thorsten Leemhuis Cc: Linux PM , Pavel Machek , "Rafael J. Wysocki" In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-bounce-key: webpack.hosteurope.de;regressions@leemhuis.info;1654955626;91ad4d5f; X-HE-SMSGID: 1o01Ye-0006jb-NG X-Spam-Status: No, score=-3.1 required=5.0 tests=BAYES_00,NICE_REPLY_A, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, this is your Linux kernel regression tracker. CCing the regression mailing list, as it should be in the loop for all regressions, as explained here: https://www.kernel.org/doc/html/latest/admin-guide/reporting-issues.html Also CCing the hibernation maintainers and Linux-pm. On 09.06.22 01:55, Ken Moffat wrote: > Up to 5.18.0 hibernation has worked ok on my ryzen 5 3400G : screen > blanks, disk activity for the write to swap, screen briefly has a > trashed display, machine powers off. When powering up from > hibernation, after the saved files are loaded X starts with a > briefly trashed display before my desktop reappears. > > But with 5.19.0-rc1 the screen is blank throughtout the hibernation, > and briefly when restoring (no complaint about that), but when > hibernating it no longer powers off and I have to hold the on/off > switch to power off. > > Is this a known problem ? Thanks for the report. Maybe the hibernation maintainers might know, but often issues like this are caused by other things like drivers. If they don#t have a idea, you likely need to do a bisection to get down to the change that introduced this regressions. Anyway: To be sure below issue doesn't fall through the cracks unnoticed, I'm adding it to regzbot, my Linux kernel regression tracking bot: #regzbot ^introduced v5.18..v5.19-rc1 #regzbot title hibernate: Not powering off when hibernated #regzbot ignore-activity This isn't a regression? This issue or a fix for it are already discussed somewhere else? It was fixed already? You want to clarify when the regression started to happen? Or point out I got the title or something else totally wrong? Then just reply -- ideally with also telling regzbot about it, as explained here: https://linux-regtracking.leemhuis.info/tracked-regression/ Reminder for developers: When fixing the issue, add 'Link:' tags pointing to the report (the mail this one replied to), as the kernel's documentation call for; above page explains why this is important for tracked regressions. Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat) P.S.: As the Linux kernel's regression tracker I deal with a lot of reports and sometimes miss something important when writing mails like this. If that's the case here, don't hesitate to tell me in a public reply, it's in everyone's interest to set the public record straight.