[Bug 273829] Re: updating near freezes system in extremely nonlinear way
We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again! ** Changed in: apt (Ubuntu) Status: Incomplete = Invalid -- updating near freezes system in extremely nonlinear way https://bugs.launchpad.net/bugs/273829 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 273829] Re: updating near freezes system in extremely nonlinear way
Also, I no longer am using ubuntu on my acer aspire one, but based on the ubuntu wiki for it, I am guessing maybe this is the result of not having had scrollkeeper disabled. -- updating near freezes system in extremely nonlinear way https://bugs.launchpad.net/bugs/273829 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 273829] Re: updating near freezes system in extremely nonlinear way
I've been monitoring top during the update process and have noticed a few things. frequent CPU users are: synaptic xorg dpkg apt-check gconftool-2 There are usually two processes for synaptic, they both seem to spend most of their time waiting or idle, but sometimes spike. Gconftool-2, when running, uses near 100% cpu, and was the only single process I could point to as having used massive amounts of the CPU. However, during the most severe spikes, Top actually froze itself for anywhere from 4 to 20 seconds, leaving me uncertain what was going on during those periods. The interesting thing is that either all live updating items were paused/frozen, too, or the CPU did not scale up from 800mhz during this time stretch (in other words it seems like CPU frequency scaling was possibly not responding to the package manager's load, a state which could turn 50% load into 100% load). -- updating near freezes system in extremely nonlinear way https://bugs.launchpad.net/bugs/273829 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 273829] Re: updating near freezes system in extremely nonlinear way
(The temp freeze of top at the relevant time is why I haven't bothered with a screen shot.) -- updating near freezes system in extremely nonlinear way https://bugs.launchpad.net/bugs/273829 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 273829] Re: updating near freezes system in extremely nonlinear way
Could you please open a terminal during an update and run top, then copy and paste the top 10 lines into this after the system freezes up. You may find something leaps to the top of the list then goes back down. Let us know if that happens and which program it is. ** Changed in: ubuntu Status: New = Incomplete -- updating near freezes system in extremely nonlinear way https://bugs.launchpad.net/bugs/273829 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 273829] Re: updating near freezes system in extremely nonlinear way
** Changed in: apt (Ubuntu) Sourcepackagename: None = apt -- updating near freezes system in extremely nonlinear way https://bugs.launchpad.net/bugs/273829 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
