FWIW, I have run this on a Xeon Phi system and not reproduced the
failure using stress-ng 0.07.16 (built in our PPA for Xenial).
This appears to have an AMI fake keyboard and mouse as the Power system that
fails does.
Bus 003 Device 003: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and
Mouse
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x046b American Megatrends, Inc.
idProduct 0xff10 Virtual Keyboard and Mouse
bcdDevice 1.00
iManufacturer 1
iProduct 2
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 59
bNumInterfaces 2
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 1 Boot Interface Subclass
bInterfaceProtocol 1 Keyboard
iInterface 3
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.10
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 65
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 1 Boot Interface Subclass
bInterfaceProtocol 2 Mouse
iInterface 4
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.10
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 63
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
and
ubuntu@cx1640-1:~$ lsusb
Bus 002 Device 002: ID 8087:8002 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:800a Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and
Mouse
Bus 003 Device 002: ID 05af:1012 Jing-Mold Enterprise Co., Ltd
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
This appears to be the same virtual HID device that the failing power
system has. Though as this is a Xeon Phi system, not an OpenPower box,
do not treat this as conclusive that the bug is fixed for the failing
system.
The summary says to run fstat 10 times, so I ran it in a loop like so and did
not experience any lockups:
for x in `seq 1 10`; do sudo stress-ng --fstat 128 -t 60 -v; done
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1652132
Title:
Call trace when testing fstat stressor on ppc64el with virtual
keyboard and mouse present
Status in Linux:
Unknown
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
Fix Committed
Bug description:
== SRU REQUEST [Xenial, Yakkety, Zesty] ==
Ubuntu 16.04.1
Kernel = 4.4.0-53-generic-74-Ubuntu ppc64le
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://www.spinics.net/lists/linux-usb/msg152977.html
== 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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1652132/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
