This bug was fixed in the package linux - 3.13.0-36.63
---
linux (3.13.0-36.63) trusty; urgency=low
[ Joseph Salisbury ]
* Release Tracking Bug
- LP: #1365052
[ Feng Kan ]
* SAUCE: (no-up) irqchip:gic: change access of gicc_ctrl register to read
modify write.
-
We have switched to the kernel in -proposed and everything looks good.
So verified.
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
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-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from
** Branch linked: lp:ubuntu/precise-proposed/linux-lts-trusty
--
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/1357295
Title:
bcache_writebac blocks and goes silent on trusty kernel
** Branch linked: lp:ubuntu/trusty-proposed/linux-keystone
--
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/1357295
Title:
bcache_writebac blocks and goes silent on trusty kernel
Thanks. It does indeed look like this got rid of the lockups in dmesg.
Thanks!
--
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/1357295
Title:
bcache_writebac blocks and goes silent on
What's the best way for us to test this fix in Trusty right now?
--
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/1357295
Title:
bcache_writebac blocks and goes silent on trusty kernel
Either pick the test-kernel from comment #7 or wait for a trusty kernel
with that patch get into proposed (which should trigger a automated
request for verification).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Trusty)
Importance: Undecided = Medium
** Changed in: linux (Ubuntu Trusty)
Status: New = Triaged
--
You received this bug notification because you are a member of Kernel
SRU Justification:
Impact: Right now whenever the bcache module gets loaded, we can see
softlockup warnings caused by the writeback thread.
Fix: A patch picked from 3.17-rc1 will avoid those warnings. I bundled
this with one patch from upstream that avoids a crash on shutdown, which
is also
** Also affects: linux (Ubuntu Utopic)
Importance: Medium
Status: Triaged
** Changed in: linux (Ubuntu Utopic)
Status: Triaged = Fix Committed
** Changed in: linux (Ubuntu Trusty)
Status: Triaged = Fix Committed
** Changed in: linux (Ubuntu Trusty)
Assignee:
This bug was fixed in the package linux - 3.16.0-10.15
---
linux (3.16.0-10.15) utopic; urgency=low
[ dann frazier ]
* [debian] Fix regression with ABI subversions and backport
[ Feng Kan ]
* SAUCE: (no-up) irqchip:gic: change access of gicc_ctrl register to read
So I am not sure there already is any solution to the load of 1, that I
see. 3.16/3.17 kernels that I tried have even more serious issues
(crashing). I pulled together three patches I got so far and build
Trusty kernels which can be found at [1]. It would be good if someone
could try them in a
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
** Changed in: linux (Ubuntu)
Status: Confirmed = Triaged
--
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/1357295
I think that the patch now (3.17-rc1) is upstream but in a slightly
modified version:
commit 7f179da0d15ded8f9d56616099f940d50ec582b5
Author: Slava Pestov s...@daterainc.com
Date: Thu May 1 13:48:57 2014 -0700
bcache: fix uninterruptible sleep in writeback thread
I cherry-picked that
Confirmed it's still happening with an updated kernel:
| [ 241.558831] INFO: task bcache_writebac:501 blocked for more than 120
seconds.
| [ 241.648361] Not tainted 3.13.0-34-generic #60-Ubuntu
| [ 241.717161] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables
this message.
| [
Looks like there's a pending patch[1].
I used the fix suggested by Sam Fulcomer[2] to set
/sys/.../bcache/writeback_running to 0 because the cache mod we're using
is writethrough.
| $ cat /sys/block/bcache0/bcache/writeback_running
| 1
| $cat /sys/block/bcache0/bcache/state
| clean
| $ cat
** Tags added: regression-release
--
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/1357295
Title:
bcache_writebac blocks and goes silent on trusty kernel
3.13.0-24-generic #47-Ubuntu
Is that still the case with an updated kernel? The trace shows -23.47
which was the initially released kernel.
--
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/1357295
Title:
19 matches
Mail list logo
