Received: by 2002:a05:6358:9144:b0:117:f937:c515 with SMTP id r4csp6726117rwr; Tue, 2 May 2023 04:53:30 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ5z6Ss5kxxFgihXsCo6PDg/wKqdp6tnggna6p4RKqyfMDKf6WwXYsLi60vOC8UOZzNzXqC8 X-Received: by 2002:a17:902:e74e:b0:1a6:7ea8:9f4f with SMTP id p14-20020a170902e74e00b001a67ea89f4fmr22031581plf.26.1683028410595; Tue, 02 May 2023 04:53:30 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1683028410; cv=none; d=google.com; s=arc-20160816; b=s5LegZqNkO+JVqtmJbfLlB9CrIo4pQ5GzGrmLsyFg1gvFf20A8DFFcYpkqEhFWazOV dJYyc0RVN4Ms60wyRVJHKEScWrwGwgqelI9anaiMJQa9dkg+VBZpTDECaU8twNk96x6K 0k+NZnVrSyzjbyWnotv3+x9Ww9KRDmzI3o3Hf88MMyB8zaje3CpxwBCGjAQNbLjYb5mR sTyfey3lOsU6sktroZYoiWga2+IgaG31gZjcQY94YWd8nMUooHL+ch4uTWwNEDFRZFef 8wCKuSseg5ieMlrHqHX8mGwwu7bXFncXvsphoi4FYH9HpqHhxpufiNw62E919r1pFFAj +/GQ== 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 :reply-to:from:references:to:content-language:subject:user-agent :mime-version:date:message-id; bh=MoPmVbc8dSZ6kroS9YlzVp3O6Kuf//94u8RZv6kxmro=; b=wz7FNXdAdwF+cw1RjxVGJ1Jkn4w0Wk8NXv0bHpcqc1AMzjsRz1QxxqlozJBQaBkK+2 fifdrF5GiA1qwJRlWzHio0ZIXPj+/SMCaYS8ZhjB+09UzLRLL82SI+n+Ic5QpJzlYNrw TM0x21UiWPm6Qf7ufuYbYCl4yBk9zwp5nyFSSM+GArNrZX+PAu4iJ1nwD6Ql6Zxykbx8 hZ1DIPemHs/Tf+f1m4jrVAUr9AxmnDZ3+AeQ/OUfbD/j3D182WenbuqjbY0FYaL1yVXi kjA1SyAxYcrRmsnLL+rWaUi6wnRGtEj7hD+4prqG1GcsYt6ixl4G3baDjhT5MS9oHZD2 IFeQ== 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 m7-20020a170902bb8700b001aae82caf71si6382042pls.211.2023.05.02.04.53.18; Tue, 02 May 2023 04:53:30 -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 S234035AbjEBLl4 (ORCPT + 99 others); Tue, 2 May 2023 07:41:56 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50244 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233807AbjEBLly (ORCPT ); Tue, 2 May 2023 07:41:54 -0400 Received: from wp530.webpack.hosteurope.de (wp530.webpack.hosteurope.de [80.237.130.52]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4C5AD55AE for ; Tue, 2 May 2023 04:41:34 -0700 (PDT) Received: from [2a02:8108:8980:2478:8cde:aa2c:f324:937e]; authenticated by wp530.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) id 1ptoNt-0003FQ-17; Tue, 02 May 2023 13:41:29 +0200 Message-ID: <2f07294a-b9a2-62c2-29a3-cd52d0ecb386@leemhuis.info> Date: Tue, 2 May 2023 13:41:26 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.10.0 Subject: Re: Fwd: 6.1.23: 0fc6fea41c71 breaks GPD Pocket 3 modeset Content-Language: en-US, de-DE To: =?UTF-8?B?VmlsbGUgU3lyasOkbMOk?= References: <4115dc28-45b6-cad1-1e38-39e5a0484a8a@garloff.de> From: "Linux regression tracking (Thorsten Leemhuis)" Reply-To: Linux regressions mailing list Cc: Linux kernel regressions list , Jani Nikula , Joonas Lahtinen , Rodrigo Vivi , Tvrtko Ursulin , Kurt Garloff , LKML In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-bounce-key: webpack.hosteurope.de;regressions@leemhuis.info;1683027694;e38e0c78; X-HE-SMSGID: 1ptoNt-0003FQ-17 X-Spam-Status: No, score=-3.3 required=5.0 tests=BAYES_00,NICE_REPLY_A, RCVD_IN_DNSWL_NONE,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 [CCing the intel drm maintainers and the lists; also CCing the regression list, as it should be in the loop for regressions: https://docs.kernel.org/admin-guide/reporting-regressions.html] [TLDR: I'm adding this report to the list of tracked Linux kernel regressions; the text you find below is based on a few templates paragraphs you might have encountered already in similar form. See link in footer if these mails annoy you.] On 29.04.23 23:38, Kurt Garloff wrote: > Hi Ville, > > (sorry for the resend, had forgotten that LKML still believes > that multipart with an HTML version is evil) > > While > 0fc6fea41c71 drm/i915: Disable DC states for all commits > (cherry picked from commit 41b4c7fe72b6105a4b49395eea9aa40cef94288d) /me wonders if 6.3 is affected as well, but will treat it as stable specific regression for now > does look correct to me, it does break modesetting on the > GPD Pocket 3, a i7-1195G7 laptop. I run the kernel with > fbcon=rotate:1 video=DSI-1:panel_orientation=right_side_up \ >   mem_sleep_default=s2idle > No special i915 parameters. > > Hardware is described here: > https://wiki.archlinux.org/title/GPD_Pocket_3 > > I disected this patch which was merged (backported) for 6.1.23. > I currently run 6.1.26 with it reverted and life is good. > > Without reverting it, when fbcon is switched to show the splash > screen (GPD logo with Ubuntu added in on working kernels), the > screen remains black (backlight on, but nothing displayed) and > nothing happens any more. It looks like something more serious > than just blackness, as SysRq or Ctrl-Alt-Del don't do anything. > Deadlocking? Thanks for the report. To be sure the issue doesn't fall through the cracks unnoticed, I'm adding it to regzbot, the Linux kernel regression tracking bot: #regzbot ^introduced 0fc6fea41c71 #regzbot title drm: i915: GPD Pocket 3 modeset broken #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 and tell me -- ideally while also telling regzbot about it, as explained by the page listed in the footer of this mail. Developers: When fixing the issue, remember to add 'Link:' tags pointing to the report (the parent of this mail). See page linked in footer for details. Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat) -- Everything you wanna know about Linux kernel regression tracking: https://linux-regtracking.leemhuis.info/about/#tldr That page also explains what to do if mails like this annoy you.