All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: "Numan Demirdöğen" <if.gnu.linux@gmail.com>
Cc: mingo@redhat.com, linux-kernel@vger.kernel.org,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>
Subject: Re: PROBLEM: Keyboard not responding after resuming from suspend/hibernate
Date: Fri, 31 Aug 2018 21:16:11 +0200	[thread overview]
Message-ID: <20180831191611.GR24124@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20180831215121.1b1f66bf@korsan.localdomain>

On Fri, Aug 31, 2018 at 09:53:11PM +0300, Numan Demirdöğen wrote:
> If I put laptop to suspend or hibernate by closing lid, power
> manager or any other method and then I resume/wake up laptop, keyboard
> is not responding. My laptop is a Sony Vaio VPCEH2F1E. 
> 
> Steps to produce bug:
> 1. Boot
> 2. Put laptop to sleep
> 3. Resume
> What I expect to happen: Keyboard responds to key press.
> What happens: Keyboard does not respond but mouse and trackball are
> working.
> 
> git bisect point 9d659ae14b545c4296e812c70493bfdc999b5c1c as the first
> bad commit.
> 
> Bad commit link:
> https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?id=9d659ae14b545c4296e812c70493bfdc999b5c1c

That doesn't make any kind of sense... if that commit had trouble (oddly
there is one another report fingering this) all the mutex locking should
be busted (and there is a _lot_ of that in the kernel).

I really wouldn't know where to begin debugging this. Suspend/resume
isn't really something I know much of, all I can say it that it works on
my laptop.

Rafael, any idea where to start looking for this?

>  Link to actual bug report:
> https://bugzilla.kernel.org/show_bug.cgi?id=195471

No, _this_ is the actual report, that is a random website you put stuff
on.

  reply	other threads:[~2018-08-31 19:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-31 18:53 PROBLEM: Keyboard not responding after resuming from suspend/hibernate Numan Demirdöğen
2018-08-31 19:16 ` Peter Zijlstra [this message]
2018-08-31 19:38   ` Numan Demirdöğen
2018-09-03  8:53 ` Numan Demirdöğen
2018-09-18 18:54   ` Pavel Machek
2018-10-19  7:20 ` Fw: " Numan Demirdöğen
2018-10-25  7:49   ` [regression, bisected] " Pavel Machek
2018-10-28 19:06     ` Numan Demirdöğen
2018-11-30 12:44       ` Numan Demirdöğen
2018-11-30 12:44         ` Numan Demirdöğen
2018-12-02 22:28         ` Pavel Machek
2018-12-18  7:23           ` Numan Demirdöğen
2019-03-14 19:54             ` Peter Zijlstra

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=20180831191611.GR24124@hirez.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=if.gnu.linux@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rjw@rjwysocki.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.