** Branch linked: lp:ubuntu/sreadahead
--
sreadahead uses 100 % of the CPU in Karmic
https://bugs.launchpad.net/bugs/421116
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
This fix appears to have corrected the problem, at least for me. I no
longer see the CPU at 100% when I log in after a major software upgrade.
--
sreadahead uses 100 % of the CPU in Karmic
https://bugs.launchpad.net/bugs/421116
You received this bug notification because you are a member of
I have uploaded the fix for this bug, however due to the freeze it may
take a little while to show up, so I've also uploaded it to the ubuntu-
boot PPA. Please test.
** Changed in: sreadahead (Ubuntu Karmic)
Status: In Progress = Fix Committed
--
sreadahead uses 100 % of the CPU in
This bug was fixed in the package sreadahead - 1.0-4
---
sreadahead (1.0-4) karmic; urgency=low
* Replace custom bubble sort with qsort(), to avoid using 100% CPU
for a long time after boot. LP: #421116, #434116.
-- Anders Kaseorg ande...@mit.edu Sun, 20 Sep 2009 13:31:45
** Also affects: sreadahead (Ubuntu Karmic)
Importance: Undecided
Assignee: Anders Kaseorg (anders-kaseorg)
Status: In Progress
** Changed in: sreadahead (Ubuntu Karmic)
Importance: Undecided = Medium
** Tags added: ubuntu-boot
--
sreadahead uses 100 % of the CPU in Karmic
** Changed in: sreadahead (Ubuntu Karmic)
Assignee: Anders Kaseorg (anders-kaseorg) = Scott James Remnant (scott)
--
sreadahead uses 100 % of the CPU in Karmic
https://bugs.launchpad.net/bugs/421116
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: sreadahead (Ubuntu Karmic)
Milestone: None = ubuntu-9.10
--
sreadahead uses 100 % of the CPU in Karmic
https://bugs.launchpad.net/bugs/421116
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
On Sun, 2009-09-20 at 17:52 +, Anders Kaseorg wrote:
As it turns out, the 100% CPU time is spent bubble-sorting a list of
readahead records. That’s idiotic. The C library comes with a standard
qsort() function for a reason. This is easy to fix and we should do so.
Right, I'd looked
As it turns out, the 100% CPU time is spent bubble-sorting a list of
readahead records. That’s idiotic. The C library comes with a standard
qsort() function for a reason. This is easy to fix and we should do so.
** Changed in: sreadahead (Ubuntu)
Status: Won't Fix = Confirmed
**
Patch: http://bazaar.launchpad.net/~anders-kaseorg/sreadahead/qsort/revision/44
Fixed packages: https://launchpad.net/~anders-kaseorg/+archive/ppa
** Changed in: sreadahead (Ubuntu)
Status: Confirmed = In Progress
--
sreadahead uses 100 % of the CPU in Karmic
Scott, is the intented behaviour of sreadahead to run only once, or
after each reboot ? If it is meant to run only once as you said, then
there definately is a problem, because it keeps running after the first
one.
--
sreadahead uses 100 % of the CPU in Karmic
On Thu, 2009-09-17 at 15:25 +, Steve Dodier wrote:
Scott, is the intented behaviour of sreadahead to run only once, or
after each reboot ? If it is meant to run only once as you said, then
there definately is a problem, because it keeps running after the first
one.
It will usually
I am seeing this on every reboot, not just the first. I just rebooted
twice in a row without doing any updates. The system had been running
smoothly overnight before the first reboot, then I let sreadahead finish
before rebooting again and it started up again. If this is considered
normal behavior
i can confirm this annoying behaviour in karmic64bit.
for some reason sreadahead keeps popping up after every reboot with 100%cpu for
10+ seconds. quite a nuisance.
(and yes, this wasn't the case before readahead was replaced by
sreadahead)
--
sreadahead uses 100 % of the CPU in Karmic
This is quite normal, it takes a few minutes after the first boot to
generate the lists - it's operating as a very low priority so
shouldn't affect system performance.
If you don't let it finish, it will be slow every time you boot ;-)
** Changed in: sreadahead (Ubuntu)
Status: New =
I have never interrupt it but after 27 reboots. it wasn't
improved...
--
sreadahead uses 100 % of the CPU in Karmic
https://bugs.launchpad.net/bugs/421116
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I can confirm this bug as I've seen the same behavior. After a fresh
boot, when I log in my CPU is running at 100% and the culprit is
sreadahead. sreadahead then exits after a minute or so. If you want,
you can disable sreadahead by editing the file at
/etc/init/sreadahead.conf and commenting
17 matches
Mail list logo
