From: Kurt Garloff <kurt@garloff.de>
To: LKML <linux-kernel@vger.kernel.org>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>
Subject: Fwd: 6.1.23: 0fc6fea41c71 breaks GPD Pocket 3 modeset
Date: Sat, 29 Apr 2023 23:38:57 +0200 [thread overview]
Message-ID: <fce7ea8d-d89c-daf0-f900-d26455d1bb74@garloff.de> (raw)
In-Reply-To: <4115dc28-45b6-cad1-1e38-39e5a0484a8a@garloff.de>
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)
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?
Best,
--
Kurt Garloff<kurt@garloff.de>
Cologne, Germany
next parent reply other threads:[~2023-04-29 21:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4115dc28-45b6-cad1-1e38-39e5a0484a8a@garloff.de>
2023-04-29 21:38 ` Kurt Garloff [this message]
2023-05-02 11:41 ` Linux regression tracking (Thorsten Leemhuis)
2023-05-02 13:13 ` Ville Syrjälä
2023-05-07 17:27 ` Kurt Garloff
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fce7ea8d-d89c-daf0-f900-d26455d1bb74@garloff.de \
--to=kurt@garloff.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ville.syrjala@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®