On Tue, Oct 4, 2016 at 6:25 AM Joseph Salisbury <
joseph.salisb...@canonical.com> wrote:
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
No - it's a new machine on which I've installed Yakkety.
Would
Public bug reported:
The wireless card in my Acer V3-372-587T suffers from firmware crashes
regularly (every 5-10mins approx).
$ lsb_release -rd
Description:Ubuntu Yakkety Yak (development branch)
Release:16.10
Checking dmesg I see:
$ dmesg | grep ath10k
Surprise :/, here are the steps that I took (perhaps it'll give you some
information showing my mistake):
1) I downloaded and installed all the debs - note missing linux-tools:
https://pastebin.canonical.com/99199/
2) Tested:
$ uname -a
Linux michael-X201EP 3.11.0-12-generic #19~lp1213917v1 SMP
$ uname -a
Linux michael-X201EP 3.10.0-031000-generic #201310151549 SMP Tue Oct 15
19:50:32 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
Good.
--
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/12
$ uname -a
Linux michael-X201EP 3.10.0-031000rc6-generic #201310091534 SMP Wed Oct 9
19:36:30 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
Good.
$ uname -a
Linux michael-X201EP 3.10.0-031000rc6-generic #201310101545 SMP Thu Oct 10
19:47:16 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
Also good (I'd half
$ uname -a
Linux michael-X201EP 3.10.0-031000-generic #201310011456 SMP Tue Oct 1 18:58:54
UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
Also bad.
--
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
$ uname -a
Linux michael-X201EP 3.10.0-031000-generic #201309181425 SMP Wed Sep 18
18:27:23 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
Also bad.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bug
$ uname -a
Linux michael-X201EP 3.10.0-031000-generic #201309171602 SMP Tue Sep 17
20:03:44 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
Also bad.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bug
$ uname -a
Linux michael-X201EP 3.10.0-031000-generic #201309171218 SMP Tue Sep 17
16:20:31 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
Bad.
Thanks Joseph
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchp
Also, just in case it's relevant in confirming the eventual commit, I've
already mentioned above that after the first suspend and kworker going
to 100%, I can't suspend a second time (I get a complete freeze
requiring a hard power-off), but if I instead try a soft power off
rather than the second s
$ uname -a
Linux michael-X201EP 3.10.0-031000rc5-generic #201309121250 SMP Thu Sep 12
16:51:50 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
Also good.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
$ uname -a
Linux michael-X201EP 3.10.0-031000rc6-generic #20130954 SMP Wed Sep 11
15:55:58 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
Good - multiple suspend/resume without kworker thread going crazy.
--
You received this bug notification because you are a member of Kernel
Packages, which is s
$ uname -a
Linux michael-X201EP 3.10.0-031000rc6-generic #201309101033 SMP Tue Sep 10
14:35:30 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
Good - multiple suspend/resume without kworker thread going above 5%
--
You received this bug notification because you are a member of Kernel
Packages, which is
Good - unable to reproduce the issue with:
$ uname -a
Linux michael-X201EP 3.10.0-031000rc6-generic #201309091524 SMP Mon Sep 9
19:25:40 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
(Note: I was confused at first by the change in package name and re-
tested the previous (non-rc6) version).
--
You r
Thanks Joseph. I hit the issue straight after a suspend with the
3.10.0-031000.201309061430 build.
--
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/1213917
Title:
kworker thread 99.8 - 100
On Thu, Aug 29, 2013 at 3:07 PM, Joseph Salisbury
wrote:
> I built the next test kernel, up to the following commit:
> 1b375dc30710180c4b88cc59caba6e3481ec5c8b
>
> The test kernel can be downloaded from:
> http://kernel.ubuntu.com/~jsalisbury/lp1213917
>
Running
$ uname -a
Linux michael-X201EP 3
On Tue, Aug 27, 2013 at 9:29 PM, Joseph Salisbury
wrote:
> The test kernel can be downloaded from:
> http://kernel.ubuntu.com/~jsalisbury/lp1213917
>
> Can you test that kernel and report back if it has the bug or not. I
> will build the next test kernel based on your test results.
>
> Thanks in a
@jsalisbury I looked at reporting upstream, and have the email ready,
but I think they expect the bisect to be done also.
I checked the mainline builds and it seems to be when my machine was
updated from 3.10 to 3.11. That is, I can confirm that running
v3.10.9-saucy installed [1] I cannot reprodu
*** This bug is a duplicate of bug 1213917 ***
https://bugs.launchpad.net/bugs/1213917
** This bug has been marked a duplicate of bug 1213917
kworker thread 99.8 - 100% CPU after 1st suspend - no second suspend
--
You received this bug notification because you are a member of Kernel
Packa
** Summary changed:
- kworker thread consuming 99.8 - 100% CPU after update
+ kworker thread 99.8 - 100% CPU after 1st suspend - no second suspend
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
On Thu, Aug 22, 2013 at 3:21 AM, Christopher M. Penalver <
christopher.m.penal...@gmail.com> wrote:
> Michael Nelson, the next step would be to bisect from Precise to
> Quantal, in order to identify the commit that caused this regression.
> Could you please do this fo
On Wed, Aug 21, 2013 at 10:03 AM, Christopher M. Penalver <
christopher.m.penal...@gmail.com> wrote:
> Michael Nelson, did this problem not occur in a release prior to Raring?
>
I bought the machine with Ubuntu installed (12.04 I think) and
suspend/resume worked fine. I updated to Qu
On Tue, Aug 20, 2013 at 1:41 PM, Christopher M. Penalver <
christopher.m.penal...@gmail.com> wrote:
> Michael Nelson, did this problem not occur in a release prior to Saucy?
>
Yes - I was not able to suspend/resume with Raring at all (it would wake
immediately). But after updating t
** 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
Updated to 3.11 (note, see circular dependency for linux-headers - is
that normal or am I miss-reading? [1]). It did not fix the problem.
[1] http://paste.ubuntu.com/6004055/
** Tags added: kernel-bug-exists-upstream
** Description changed:
Suspend was working after upgrading to saucy, but fa
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
I have no way currently of knowing, but just ftr, suspend is failing
whenever I try to suspend while kworker thread is near 100% cpu usage
(another bug I reported earlier - bug 1213917).
Actually, I just tested and suspend/resume works fine the first time,
but after the resume bug 1213917 starts h
...and fails again the third time.
** Changed in: linux (Ubuntu)
Status: Invalid => New
--
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/1214071
Title:
[ASUSTeK COMPUTER INC. X201E
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
Public bug reported:
Suspend was working after upgrading to saucy, but failed after updating
today (I hadn't updated for a week or two).
Screen goes blank, but fan and disk keep spinning.
ProblemType: KernelOops
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-2-generic 3.11.0-2.5
ProcVer
But works fine after a second reboot.
** Changed in: linux (Ubuntu)
Status: New => Invalid
--
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/1214071
Title:
[ASUSTeK COMPUTER INC. X2
Public bug reported:
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 00
@jsalisbury
Sorry - update: After updating the bios to the latest version from Asus,
retrying with the v3.10 kernel resumed fine :) Thanks for your help!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launch
Thanks Christopher. I updated to the latest bios, and tried again -
resumed perfectly.
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launch
@jsalisbury
I updated to saucy (for other reasons), and tried suspend with the v3.10
kernal. It suspended, but didn't resume. Details on bug 1206625. Thanks
to the team for looking at these!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Public bug reported:
This might be considered a dupe of bug 1157435. I upgrade to saucy for
other reasons, but saw a chance to check if suspend was working with
v3.10 kernal.
The machine suspended, but when I tried to resume, the fan span but the
screen never changed from a blank one :)
[1]
http
Public bug reported:
After an upgrade to 13.10, I rebooted to find a bunch of error reports
(see screenshot).
Hoping they might go away with another update, I tried that - which
resulted in the same errors [1]
[1] http://paste.ubuntu.com/5927929/
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Pac
37 matches
Mail list logo
