Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#21625 - Latency every two seconds

Attached to Project: Arch Linux
Opened by Dominik (cpcgm) - Sunday, 07 November 2010, 14:15 GMT
Last edited by Andrea Scarpino (BaSh) - Wednesday, 10 November 2010, 13:25 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

After rebooting this morning (first reboot in two or three days) I get a latency of about one second every two seconds. It's impossible to work because neither mouse nor keybord work for that second. If I keep typing, some letters don't show up once the latency is over.

Additional info:
* powertop shows that one of the two processor cores is peaking to 100 percent during the latency times but no program seems to be resonsible. I shut everything (even hal, ...) down but it's still peaking.
* I thought it might be a kernel issue and tried kernel26-lts instead of kernel26 but the problem persists.
* A friend suggested using latencytop but it's not supported by the Arch kernel.
This task depends upon

Closed by  Andrea Scarpino (BaSh)
Wednesday, 10 November 2010, 13:25 GMT
Reason for closing:  Not a bug
Comment by Dominik (cpcgm) - Sunday, 07 November 2010, 15:30 GMT
A few days ago I added another 2 GB of RAM and the computer worked fine afterwards. But I thought it might be the reason so I put the hardware out and in again, booted and the latency problem is gone. Could that have been the issue?
Comment by Dave North (north) - Wednesday, 10 November 2010, 04:31 GMT
Yes it could have been the issue. If your RAM was not seated properly or a bit of lint interfered with one of the contacts, it could lead to this kind of problem. If things are still working normally you might consider getting this bug closed.
Comment by Dominik (cpcgm) - Wednesday, 10 November 2010, 08:16 GMT
Thanks for the answer. Everything's still working so let's close the bug.

Loading...