[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0b30c88a-6f0c-447f-a08e-29a2a0256c1b@molgen.mpg.de>
Date: Sun, 21 Jan 2024 15:26:49 +0100
From: Paul Menzel <pmenzel@...gen.mpg.de>
To: Hans de Goede <hdegoede@...hat.com>
Cc: linux-input@...r.kernel.org, linux-pm@...r.kernel.org,
Dell.Client.Kernel@...l.com, regressions@...ts.linux.dev,
linux-kernel@...r.kernel.org
Subject: Re: PS/2 keyboard of laptop Dell XPS 13 9360 goes missing after S3
Dear Hans,
As always thank you very much for taking the time to reply.
Am 20.01.24 um 21:26 schrieb Hans de Goede:
> On 1/18/24 13:57, Paul Menzel wrote:
>> #regzbot introduced v6.6.11..v6.7
>> There seems to be a regression in Linux 6.7 on the Dell XPS 13 9360 (Intel i7-7500U).
>>
>> [ 0.000000] DMI: Dell Inc. XPS 13 9360/0596KF, BIOS 2.21.0 06/02/2022
>>
>> The PS/2 keyboard goes missing after S3 resume¹. The problem does not happen with Linux 6.6.11.
>
> Thank you for reporting this.
>
> Can you try adding "i8042.dumbkbd=1" to your kernel commandline?
>
> This should at least lead to the device not disappearing from
>
> "sudo libinput list-devices"
>
> The next question is if the keyboard will still actually
> work after suspend/resume with "i8042.dumbkbd=1". If it
> stays in the list, but no longer works then there is
> a problem with the i8042 controller; or interrupt
> delivery to the i8042 controller.
>
> If "i8042.dumbkbd=1" somehow fully fixes things, then I guess
> my atkbd driver fix for other laptop keyboards is somehow
> causing issues for yours.
Just a quick feedback, that booting with `i8042.dumbkbd=1` seems to fix
the issue.
> If "i8042.dumbkbd=1" fully fixes things, can you try building
> your own 6.7.0 kernel with commit 936e4d49ecbc:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=936e4d49ecbc8c404790504386e1422b599dec39
>
> reverted?
I am going to try that as soon as possible.
Kind regards,
Paul
>> [ 1.435071] i8042: PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
>> [ 1.435409] i8042: Warning: Keylock active
>> [ 1.437624] serio: i8042 KBD port at 0x60,0x64 irq 1
>> [ 1.437631] serio: i8042 AUX port at 0x60,0x64 irq 12
>> […]
>> [ 1.439743] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0
>>
>> $ sudo libinput list-devices
>> […]
>> Device: AT Translated Set 2 keyboard
>> Kernel: /dev/input/event0
>> Group: 15
>> Seat: seat0, default
>> Capabilities: keyboard
>> Tap-to-click: n/a
>> Tap-and-drag: n/a
>> Tap drag lock: n/a
>> Left-handed: n/a
>> Nat.scrolling: n/a
>> Middle emulation: n/a
>> Calibration: n/a
>> Scroll methods: none
>> Click methods: none
>> Disable-w-typing: n/a
>> Disable-w-trackpointing: n/a
>> Accel profiles: n/a
>> Rotation: 0.0
>>
>> `libinput list-devices` does not list the device after resuming
>> from S3. Some of the function keys, like brightness and airplane
>> mode keys, still work, as the events are probably transmitted over
>> the embedded controller or some other mechanism. An external USB
>> keyboard also still works.
>>
>> I haven’t had time to further analyze this, but wanted to report
>> it. No idea
>>
>>
>> Kind regards,
>>
>> Paul
>>
>>
>> ¹ s2idle is not working correctly on the device, in the sense, that
>> energy usage is very high in that state, and the full battery is at
>> 20 % after leaving it for eight hours.
Powered by blists - more mailing lists