HID: Fix RayD touchscreen failure to resume from suspend
Bug #1741168 reported by
AaronMa
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| HWE Next |
Won't Fix
|
Critical
|
AaronMa | ||
| linux (Ubuntu) |
Won't Fix
|
Critical
|
AaronMa | ||
Bug Description
Link: https:/
Link: https:/
[Impact]
Resume of S3 cause system hang on Lenovo laptops with RayD touchscreen.
[Fix]
RayD touchscreen issued corrupted data after it resume from suspend,
then HID driver didn't handle the data well because of the data overflow
and made a call trace and hang.
Keep memset safe from corrupted data and add command to make RayD
touchscreen back to normal.
Then touchscreen works fine.
[Test Case]
Tested on ThinkPad L380, works fine with fixes.
[Regression Potential]
Low, keep the data in hid-core and i2c-hid more strictly.
Add specific device quirk in i2c-hid.
| Changed in linux (Ubuntu): | |
| importance: | Undecided → Critical |
| assignee: | nobody → AaronMa (mapengyu) |
| tags: | added: originate-from-1731135 sutton |
| Changed in hwe-next: | |
| importance: | Undecided → Critical |
| assignee: | nobody → AaronMa (mapengyu) |
Revision history for this message
| Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote Missing required logs. | #1 |
| Changed in linux (Ubuntu): | |
| status: | New → Incomplete |
| Changed in linux (Ubuntu): | |
| status: | Incomplete → In Progress |
| Changed in linux (Ubuntu): | |
| status: | In Progress → Won't Fix |
| Changed in hwe-next: | |
| status: | New → Won't Fix |
To post a comment you must log in.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 1741168
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.