[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180831223823.33404864@korsan.localdomain>
Date: Fri, 31 Aug 2018 22:38:23 +0300
From: Numan Demirdöğen <if.gnu.linux@...il.com>
To: Peter Zijlstra <peterz@...radead.org>
Cc: mingo@...hat.com, linux-kernel@...r.kernel.org,
"Rafael J. Wysocki" <rjw@...ysocki.net>
Subject: Re: PROBLEM: Keyboard not responding after resuming from
suspend/hibernate
Fri, 31 Aug 2018 21:16:11 +0200 tarihinde
Peter Zijlstra <peterz@...radead.org> yazdı:
>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
Hi,
Thank you for looking into this problem!
>
>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).
So, should I re-run a git bisect in order to confirm whether that
commit is the culprit or not?
>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.
--
Numan Demirdöğen
Powered by blists - more mailing lists