This bug was fixed in the package linux - 4.8.0-38.41
---
linux (4.8.0-38.41) yakkety; urgency=low
[ Thadeu Lima de Souza Cascardo ]
* Release Tracking Bug
- LP: #1661232
* Backport Dirty COW patch to prevent wineserver freeze (LP: #1658270)
- SAUCE: mm: Respect FOLL_F
This bug was fixed in the package linux - 4.4.0-63.84
---
linux (4.4.0-63.84) xenial; urgency=low
[ Thadeu Lima de Souza Cascardo ]
* Release Tracking Bug
- LP: #1660704
* Backport Dirty COW patch to prevent wineserver freeze (LP: #1658270)
- SAUCE: mm: Respect FOLL_FO
Tested with Yakkety 4.8.0-38-generic #41-Ubuntu, no failures
** Tags removed: verification-needed-yakkety
** Tags added: verification-done-yakkety
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652132
Tested with Xenial 4.4.0-63-generic #84-Ubuntu, no failures.
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652132
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'. If the problem still exists,
change the tag 'verifi
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
Note, the above comment was validated on a Fujitsu CX1640 Xeon Phi system with
Xenial and the stock ubuntu kernel:
Linux cx1640-1 4.4.0-59-generic #80-Ubuntu SMP Fri Jan 6 17:47:47 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Ubuntu
B
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Colin Ian King (colin-king)
** Changed in: linux (Ubuntu Xenial)
Status: New => Fix Committed
--
You received this bug notification becau
** Description changed:
+ == 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 han
Going to quirk this with polling to avoid the issue with the urb kill.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652132
Title:
Call trace when testing fstat stressor on ppc64el with virtual
k
Checked this right through 4.0 to 4.10-rc5, it can be triggered with any
of these kernels with enough run time.
** Bug watch added: Linux Kernel Bug Tracker #193301
http://bugzilla.kernel.org/show_bug.cgi?id=193301
** Also affects: linux via
http://bugzilla.kernel.org/show_bug.cgi?id=193301
OK, so this is annoying race condition, so bisecting it has been causing
me some pain today. It turns out that 4.10-rc4 seems OK, whereas
4.10-rc3 and before will hang after two or 3 iterations of my stress
test.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
4.9 fails, 4.10-rc1 OK, bisecting on that
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652132
Title:
Call trace when testing fstat stressor on ppc64el with virtual
keyboard and mouse present
To
Can't break the kernel with 4.10-rc4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652132
Title:
Call trace when testing fstat stressor on ppc64el with virtual
keyboard and mouse present
To mana
Fails on mainline 4.9 too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652132
Title:
Call trace when testing fstat stressor on ppc64el with virtual
keyboard and mouse present
To manage notific
Hang seems to occur when on a race when fstat'ing /dev/psaux
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652132
Title:
Call trace when testing fstat stressor on ppc64el with virtual
keyboard an
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)
Assi
This test has been run dozens of times across multiple machines and
deployments and reboots. It is completely reproducible.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652132
Title:
Call trace wh
It looks to me that a reset on a USB device from an atomic context
occurred, causing __usb_queue_reset_device to be executed from a worker
thread but this got hung for some reason. The fstat stressor was being
run at the time, and that also locks up. So my current hunch is that
this may have been
FYI, Added stress-ng task as a specific test case in that tool is
exposing this issue. Just want to be sure this is not a test tool issue
instead of a legit kernel issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: stress-ng
Assignee: (unassigned) => Colin Ian King (colin-king)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
apport-collect is not functioning on this server:
The collected information can be sent to the developers to improve the
application. This might take a few minutes.
tar: Removing leading `/' from member names
tar: Removing leading `/' from member names
tar: Removing leading `/' from member nam
** Also affects: stress-ng
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652132
Title:
Call trace when testing fstat stressor on ppc64el with virtual
k
** Summary changed:
- Call trace when testing fstat stressor on ppc64el with virtual keyboard and
mouse
+ Call trace when testing fstat stressor on ppc64el with virtual keyboard and
mouse present
** Tags added: blocks-hwcert-server
--
You received this bug notification because you are a mem
25 matches
Mail list logo