[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1023214
alecm3, the patch mentioned by Stephen Croll is available in Precise+ as
per http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-
precise.git;a=commit;h=a041ea7c6c7b5ab0b4cfc2d0d50fbab9a9f9602c . Would
it be possible to test this out in Precise server via
http://releases.ubuntu.com/precise/ and advise to
@Stephen Croll :Do you know if this patch has been incorporated into
12.04LTS? What about 10.04LTS?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1023214
Title:
bogus utime and stime in
FYI: There are a pair of kernel commits that *might* solve this
issue, at least for newer kernels. The first can be found in
Linus's tree (as well as linux-next) and the second is currently
only in linux-next:
[scroll@scroll-kernel-vm linux-next]$ git remote -v
origin
I have a 2.6.32-40-server production machine that just entered this
state after a month of normal operations. If anyone is interested, I can
collect more data from it. So far,
# ps -o pid,pcpu,time -p3061
PID %CPU TIME
3061 14157 1184014533-20:50:00
# cat /proc/3061/stat
3061 (mysqld) S
@alecm3, do you have the option to test some kernels on a machine that
exhibits this bug?
** Changed in: linux (Ubuntu)
Importance: Medium = High
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@alecm3,
If you can:
1. The kernel you are running is not the most recent in -updates. Please
update one of your systems and see if the problem is still happening.
2. If the problem still exists, please try one of our LTS backport packages.
I'd suggest trying the Oneiric one and see if that
I upgraded several machines to 2.6.32-41-server about a week ago, which
seems to be the latest 10.04 LTS kernel. If the bug occurs on
2.6.32-41-server, I will add information immediately. I am not very
optimistic about this upgrade, since the diff of fs/proc/array.c between
2.6.32-41-server and
@brad-figg
re: option 2
I could potentially try a backported kernel, do I need to use Oneiric or I can
go with Pangolin, because Pangolin is LTS?
This upgrade would require some preparation and scheduling, I cannot do it
immediately.
--
You received this bug notification because you are a
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1023214
Title:
bogus utime and stime in /proc/PID/stat
To manage notifications about
I am not sure why it's marked medium importance: it keeps happening on
all our production servers. Unfortunately, this bug will cause us to
switch distributions.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
I administer a large number of servers, and I have this problem only
with Ubuntu 10.04 LTS: I run a server under normal load (say load
average 3.0 on an 8-core server). The top command shows processes
taking certain % of CPU that cause this load average: say
-
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1023214
Title:
bogus utime and stime in /proc/PID/stat
To manage notifications about this bug go to:
** Changed in: linux (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1023214
Title:
bogus utime and stime in /proc/PID/stat
To manage notifications about this
14 matches
Mail list logo
