public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Vito Caputo <vcaputo@pengaru.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [REGRESSION] 4.18-rc2: X61s thinkpad display unusable after xlock & lid close
Date: Wed, 27 Jun 2018 17:18:39 +0300	[thread overview]
Message-ID: <20180627141839.GE20518@intel.com> (raw)
In-Reply-To: <20180627000548.jdhzpgnrdebzmlsd@shells.gnugeneration.com>

On Tue, Jun 26, 2018 at 05:05:48PM -0700, Vito Caputo wrote:
> Hello,
> 
> Beginning with 4.18, when I lock my X server using the `xlock` command,
> and close the lid, upon reopening the lid I am not presented with the
> xlock UI.
> 
> The system is not hung.  If I blindly enter the password, I get an
> intact and functional pointer but none of the desktop is displayed.  I
> can move the pointer, and cycling window focus generates some random
> noise occasionally, but it's all nonsensical.  No windows are
> discernable, it's just blackness with ephemeral noise on window cycles,
> and a movable pointer.
> 
> The system does not suspend on lid close, with "HandleLidSwitch=ignore"
> in logind.conf.  So this is a bit odd, since I don't observe this when I
> just run `xlock` but don't close/open the lid before unlocking.
> 
> This is on Debian 9.4 amd64, the hardware is a 1.8Ghz X61s ThinkPad,
> kernel config attached.  I'm using the modesetting Xorg driver on i915
> KMS.

Ah, a Thinkpad with lid notifier. Now were getting somewhere :)

Can you pls test the stuff I listed here
https://bugs.freedesktop.org/show_bug.cgi?id=105902#c5 ?

-- 
Ville Syrjälä
Intel

  parent reply	other threads:[~2018-06-27 14:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-27  0:05 [REGRESSION] 4.18-rc2: X61s thinkpad display unusable after xlock & lid close Vito Caputo
2018-06-27 12:28 ` Jani Nikula
2018-06-27 14:18 ` Ville Syrjälä [this message]
2018-06-27 18:30   ` Vito Caputo

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=20180627141839.GE20518@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vcaputo@pengaru.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