This bug was fixed in the package linux - 4.10.0-35.39
---
linux (4.10.0-35.39) zesty; urgency=low
* linux: 4.10.0-35.39 -proposed tracker (LP: #1716606)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- SAUCE: s390/mm: fix local TLB flushing vs. de
This bug was fixed in the package linux - 4.12.0-13.14
---
linux (4.12.0-13.14) artful; urgency=low
* linux: 4.12.0-13.14 -proposed tracker (LP: #1714687)
* vhost guest network randomly drops under stress (kvm) (LP: #1711251)
- Revert "vhost: cache used event for better perfo
Alvin confirmed to me (in an email) that the fix in proposed solves the
problem.
** Tags removed: verification-needed-zesty
** Tags added: verification-done-zesty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
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-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verificati
** Changed in: linux (Ubuntu Zesty)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711096
Title:
dma-buf: performance issue when looking up the fence stat
** Description changed:
SRU Request:
[Impact]
When a timeout of zero is specified, the caller is only interested in
the fence status.
In the current implementation, dma_fence_default_wait will always call
schedule_timeout() at least once for an unsignaled fence. This adds a
sig
** Description changed:
+ SRU Request:
+
+ [Impact]
When a timeout of zero is specified, the caller is only interested in
the fence status.
In the current implementation, dma_fence_default_wait will always call
schedule_timeout() at least once for an unsignaled fence. This adds a
sig
** Description changed:
When a timeout of zero is specified, the caller is only interested in
the fence status.
In the current implementation, dma_fence_default_wait will always call
schedule_timeout() at least once for an unsignaled fence. This adds a
significant overhead to a fence