Keyboard unresponsive after suspend Ubuntu 16.04 with touchscreen

Bug #1668006 reported by nacenteno
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Ubuntu 16.04 64 bit
Toshiba Satellite P55W-C with touchscreen
CPU: Intel® Core™ i7-5500U CPU @ 2.40GHz × 4
Video Card: Intel® HD Graphics 5500 (Broadwell GT2)
Display: 15.6” diagonal widescreen TruBrite ® TFT LCD display at 1920 x 1080
native resolution (FHD)

After suspend, several times the keyboard is unresponsive.

Touchscreen remain responsive all the time so I had to suspend again using the touchscreen and try again until keyboard is finally responsive.

Already tried with an edit to /etc/default/grub
Changed the line
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
to
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash atkbd.reset"

Then run update-grub, and reboot.

That did not fix the issue.

I have attached the output of ubuntu-bug linux, what other information is needed to fix the issue?

What do you suggest to solve the issue?

Thanks.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-64-generic 4.4.0-64.85
ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
Uname: Linux 4.4.0-64-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: arturo 2047 F.... pulseaudio
 /dev/snd/pcmC1D0p: arturo 2047 F...m pulseaudio
 /dev/snd/controlC1: arturo 2047 F.... pulseaudio
CurrentDesktop: Unity
Date: Sat Feb 25 23:23:09 2017
HibernationDevice: RESUME=UUID=16283a3e-099e-4e71-9bb9-60cae60bfc06
InstallationDate: Installed on 2016-05-31 (271 days ago)
InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1)
MachineType: TOSHIBA Satellite P55W-C
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic root=UUID=13ab440b-6f1e-465c-969e-b434431dce7d ro quiet splash atkbd.reset vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-64-generic N/A
 linux-backports-modules-4.4.0-64-generic N/A
 linux-firmware 1.157.8
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/01/2015
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 5.00
dmi.board.asset.tag: No Asset Tag
dmi.board.name: 0692
dmi.board.vendor: FF40
dmi.board.version: 2.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis ManuFacturer
dmi.chassis.version: OEM Chassis Version
dmi.modalias: dmi:bvnINSYDECorp.:bvr5.00:bd07/01/2015:svnTOSHIBA:pnSatelliteP55W-C:pvrPSPVJU-00V016:rvnFF40:rn0692:rvr2.0:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
dmi.product.name: Satellite P55W-C
dmi.product.version: PSPVJU-00V016
dmi.sys.vendor: TOSHIBA

Revision history for this message
nacenteno (nacenteno) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
nacenteno (nacenteno) wrote :

I took a look at the syslog and I see this error with suspend:
Feb 25 16:06:03 TSat-P55W-C systemd-sleep[4251]: /lib/systemd/system-sleep/wpasupplicant failed with error code 255.

Is it related to the issue?

Thanks.

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.10 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10.1

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
nacenteno (nacenteno) wrote :

Hi Joseph,

I appreciate your help with this issue.

I got the laptop late on 2015 new and installed 16.04 removing the original OS (Win10).

The issue has been there since the very first start on Ubuntu 16.04 but Windows 10 never had issues.

As for the upstream kernel, I see several Kernels 4.10 and 4.10.1, sorry but your instruction is vague. I am not going to guess and install without a very specific target.

Is there other specific log of settings you need to see before trying any install?

Let me know.

Thanks.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.