Mailinglist Archive: opensuse-bugs (13468 mails)
| < Previous | Next > |
[Bug 334170] Too many Wakeups-from-idle per second after suspend2ram
- From: bugzilla_noreply@xxxxxxxxxx
- Date: Tue, 16 Oct 2007 05:18:12 -0600 (MDT)
- Message-id: <20071016111812.71D56CC7AC@xxxxxxxxxxxxxxxxxxxxxx>
https://bugzilla.novell.com/show_bug.cgi?id=334170#c4
Thomas Renninger <trenn@xxxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC|
|rjwysocki@xxxxxxx, pavel@xxxxxxxxxx
--- Comment #4 from Thomas Renninger <trenn@xxxxxxxxxx> 2007-10-16 05:18:10
MST ---
I don't think that has to do with processes.
I expect the timer set up got screwed somehow. In nohz mode the timer
interrupts are switched off or lowered. For some reason the system seems to
fall back to normal HZ mode an timer interrupts are fired (not sure whether we
are at 250 or 1000 timers per second -> it normally doesn't matter anymore..).
If you do a:
watch -n1 cat /proc/interrupts
you should see the timer interrupts increase regularly by 250 or 1000 per
second after s2ram, but not before?
Maybe setting different clocksources help?
/sys/devices/system/clocksource/clocksource0/
However, this is rather complex code written by Ingo Molnar and Thomas
Gleixner.
IMO this bug should get verified in latest kernel and reported upstream, e.g.
via http://bugzilla.kernel.org
To verify whether the latest mainline kernel is also affected, you can take
this one:
ftp.suse.com/pub/projects/kernel/kotd/HEAD/x86_64/kernel-vanilla-2.6.23.1-20071013190126.x86_64.rpm
(the timestamp might vary of course).
Adding Pavel and Rafael, they may already know about this or might want to know
about it.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Thomas Renninger <trenn@xxxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC|
|rjwysocki@xxxxxxx, pavel@xxxxxxxxxx
--- Comment #4 from Thomas Renninger <trenn@xxxxxxxxxx> 2007-10-16 05:18:10
MST ---
I don't think that has to do with processes.
I expect the timer set up got screwed somehow. In nohz mode the timer
interrupts are switched off or lowered. For some reason the system seems to
fall back to normal HZ mode an timer interrupts are fired (not sure whether we
are at 250 or 1000 timers per second -> it normally doesn't matter anymore..).
If you do a:
watch -n1 cat /proc/interrupts
you should see the timer interrupts increase regularly by 250 or 1000 per
second after s2ram, but not before?
Maybe setting different clocksources help?
/sys/devices/system/clocksource/clocksource0/
However, this is rather complex code written by Ingo Molnar and Thomas
Gleixner.
IMO this bug should get verified in latest kernel and reported upstream, e.g.
via http://bugzilla.kernel.org
To verify whether the latest mainline kernel is also affected, you can take
this one:
ftp.suse.com/pub/projects/kernel/kotd/HEAD/x86_64/kernel-vanilla-2.6.23.1-20071013190126.x86_64.rpm
(the timestamp might vary of course).
Adding Pavel and Rafael, they may already know about this or might want to know
about it.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
| < Previous | Next > |