OK, I've got access to the machine and can easily reproduce this. This
is not a stress-ng bug per-se, it's a locking issue so I'll remove
stress-ng from the bug.
** No longer affects: stress-ng
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
--
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 package in Ubuntu:
In Progress
Bug description:
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1652132/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
