We can perform a kernel bisect to identify the commit that introduced
this regression. Do you happen to know the last kernel version that did
not exhibit this bug? If not, can you test the following kernels:
v3.11-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc1-saucy/
v3.11-rc2: htt
Also, this issue appears to be an upstream bug, since you tested the
latest upstream kernel. Would it be possible for you to open an upstream
bug report[0]? That will allow the upstream Developers to examine the
issue, and may provide a quicker resolution to the bug.
Please follow the instructions
** Description changed:
After updating today (hadn't updated for a while), my fan won't stop and
top is showing:
- PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND
- 4 root 20 0
OK, I've just tested 3 times, and this issue seems to be triggered by
suspend/resume, which works fine the first time, but after the first
resume, the kworker CPU consumption starts and the next suspend fails
(bug 1214071).
I'll update to 3.11 and check if I can reproduce it there.
--
You receiv
On Mon, Aug 19, 2013 at 7:27 PM, Joseph Salisbury <
joseph.salisb...@canonical.com> wrote:
> Would it be possible for you to test the latest upstream kernel? Refer
> to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
> v3.11 kernel[0].
>
Yes - although since rebooting it's n
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.11 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix t
6 matches
Mail list logo
