After a month, and off course, I checked that the issue was still
present with an up to date system when I added notes to this bug report
a couple of hours ago, right?
Well, due to incompetence on my part, I was not running the current
14.04 kernel, when I thought I was.
This issue is fixed when
The issue is that all of those kernels work, the issue does not appear
until the kernel configuration changes between saucy and trusty, as
mentioned in my original posting.
Without even knowing a good starting point, I tried a kernel bi-section,
but with the "new configuration" and went back as fa
Can you test the following kernels and report back? We are looking for
the first kernel version that exhibits this bug:
v3.8 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8-raring
v3.9 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.9-saucy
v3.10 final: http://kernel.ubuntu.com/~
@ Joseph Salisbury: Thank you for the suggestions.
I would like to try to bisect the kernel. I am setup with GIT for my
kernel.org version of the kernel. I have tried to bisect the kernel 3
times before, and succeeded once. I will have to study GIT again to
remember how to do anything beyond "git
We could also perform a kernel bisect to identify the issue that
introduced this issue. Do you happen to know the last kernel version
that did not exhibit the bug? If not, I can list out some prior kernel
versions with their links for testing.
--
You received this bug notification because you a
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 on th
I tried the Ubuntu kernel 3.13RC2, and the CPU user, sys, idle, and wait
information making no sense at all issue remains.
As I see it now, if there is a fb0 device, then the issue will exist:
doug@test-smy:~$ ls -l /dev/fb0
crw-rw 1 root video 29, 0 Dec 1 08:25 /dev/fb0
If there is not a f
I have isolated the kernel configuration differences down to:
doug@v32-serv03:~/kernel/linux-3.12.0$ diff config_def config_05
781c781
< CONFIG_X86_SYSFB=y
---
> # CONFIG_X86_SYSFB is not set
4869c4869
< CONFIG_FB_BOOT_VESA_SUPPORT=y
---
> # CONFIG_FB_BOOT_VESA_SUPPORT is not set
4900c4900
< CONFI
** Attachment added: "various delays on vstat - good config"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1254920/+attachment/3918412/+files/vmstat_loop_good.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I noticed some differences with the output of vmstat depending on the
delay parameter. The attachment is a loop of vmstat command for delay =
1 to 50 in steps of 1.
In a moment I will add the same thing but with the "good" kernel
configuration.
I have been trying to create a 14.04 i386 VM on my g
Yes, I already tried kernel 3.13RC1 a couple of days ago, and it was the
same. I tried the one from the Ubuntu kernel PPA, not the one directly
from kernel.org (as I mentioned in an earlier post, I can not compile
the kernel on this computer).
I tried many many kernels in an attempt to isolate the
Can you see if this is also an issue with the upstream 3.13-rc1 kernel:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13-rc1-trusty/
** Tags removed: kernel-key
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
apport-collect has never worked for me on server computers. I end up in
some mess with my putty SSH connection and have never been able to
figure it out.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchp
To clarify, I am suggesting that the reported numbers are incorrect, not
that there is some strange new loads going on.
I did many tests with disk I/O and CPU loading and such to determine if
there were any real increased overheads. Maybe a couple of percent of
CPU OS increased overhead and a litt
That does seem like a high sys utilization. Can you provide a sample
top output to see what the top processes are? You can have top write to
a file with:
top -n 180 -b -d 30 > top.out 2>&1 &
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Tags added: kernel-key trusty
--
** Attachment added: "kernel config differences between saucy and trusty"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1254920/+attachment/3917140/+files/diff_config_saucy_trusty
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Attachment added: "sudo lspci -vnvn > lspci-vnvn.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1254920/+attachment/3917141/+files/lspci-vnvn.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bu
17 matches
Mail list logo
