Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linux |
Unknown
|
Unknown
|
|||
linux (Ubuntu) |
Fix Released
|
High
|
Colin Ian King | ||
Xenial |
Fix Released
|
Undecided
|
Colin Ian King |
Bug Description
== SRU REQUEST [Xenial, Yakkety, Zesty] ==
Ubuntu 16.04.1
Kernel = 4.4.0-53-
When running the stress-ng "fstat" stressor, it is trying to access the USB bus and giving a call trace and locking up any further USB activity (lsusb hangs). This only seems to occur so far on openpower(Firestone and Garrison) where there is a virtual USB keyboard and mouse built into the BMC.
From lsusb(before crashing): Bus 001 Device 004: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse
Another openpower server(Briggs) has no virtual usb devices and does not experience the failure.
Please see attached kern.log and dmesg output for further details.
== Fix ==
Quirking the Virtual AMI keyboard and mouse with ALWAYS_POLL addresses the issue. The patch has been accepted into the upstream queue for 4.11, see http://
== Test Case ==
run 10 times:
sudo stress-ng --fstat 128 -t 60 -v
Without the fix, it will hang, with the fix there is no hang or USB error messages.
== Regression Potential ==
This only quirks a specific AMI virtual keyboard and mouse into a poll mode, so it touches one device. Futhermore, the poll mode shouldn't affect operation; it just makes the URB handling less efficient.
summary: |
Call trace when testing fstat stressor on ppc64el with virtual keyboard - and mouse + and mouse present |
tags: | added: blocks-hwcert-server |
Changed in linux (Ubuntu): | |
status: | Incomplete → Confirmed |
Changed in stress-ng: | |
assignee: | nobody → Colin Ian King (colin-king) |
description: | updated |
description: | updated |
Changed in linux (Ubuntu Xenial): | |
assignee: | nobody → Colin Ian King (colin-king) |
status: | New → Fix Committed |
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
apport-collect 1652132
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.