From: Pavel Machek <pavel@suse.cz>
To: Tony Lindgren <tony@atomide.com>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Arjan van de Ven <arjan@infradead.org>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Andrea Arcangeli <andrea@suse.de>,
George Anzinger <george@mvista.com>,
Thomas Gleixner <tglx@linutronix.de>,
john stultz <johnstul@us.ibm.com>,
Zwane Mwaikambo <zwane@arm.linux.org.uk>,
Lee Revell <rlrevell@joe-job.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Dynamic tick, version 050127-1
Date: Tue, 1 Feb 2005 22:25:43 +0100 [thread overview]
Message-ID: <20050201212542.GA3691@openzaurus.ucw.cz> (raw)
In-Reply-To: <20050201204008.GD14274@atomide.com>
Hi!
> > I used your config advices from second mail, still it does not work as
> > expected: system gets "too sleepy". Like it takes a nap during boot
> > after "dyn-tick: Maximum ticks to skip limited to 1339", and key is
> > needed to make it continue boot. Then cursor stops blinking and
> > machine is hung at random intervals during use, key is enough to awake
> > it.
>
> Hmmm, that sounds like the local APIC does not wake up the PIT
> interrupt properly after sleep. Hitting the keys causes the timer
> interrupt to get called, and that explains why it keeps running. But
> the timer ticks are not happening as they should for some reason.
> This should not happen (tm)...
:-). Any ideas how to debug it? Previous version of patch seemed to work better...
> I've noticed that the only machine I have with ACPI C2/C3 support
> does not do anything in the C2/C3 loops, it just spins around and
> consumes more power than in C1 with hlt!
>
> That's because we currently don't have any code to enable the C2/C3
> states in the southbridges on many Athlon boards. It's the same
> problem on my Crusoe laptop ALi 1533 chipset.
I do not think we should need any chipset-specific code. ACPI
is expected to solve it... Can you ask on acpi-devel?
--
64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms
next prev parent reply other threads:[~2005-02-01 21:50 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-27 21:29 Tony Lindgren
2005-01-27 21:50 ` Tony Lindgren
2005-02-01 11:00 ` Pavel Machek
2005-02-01 20:40 ` Tony Lindgren
2005-02-01 21:25 ` Pavel Machek [this message]
2005-02-01 23:03 ` Tony Lindgren
2005-02-02 13:50 ` Pavel Machek
2005-02-02 13:50 ` Pavel Machek
2005-02-02 13:56 ` Pavel Machek
2005-02-02 14:11 ` Pavel Machek
2005-02-03 3:04 ` Tony Lindgren
2005-02-03 10:56 ` Pavel Machek
2005-02-03 16:43 ` Tony Lindgren
2005-02-04 5:19 ` Tony Lindgren
2005-02-04 6:33 ` Zwane Mwaikambo
2005-02-04 17:18 ` Tony Lindgren
2005-02-04 17:31 ` Zwane Mwaikambo
2005-02-04 17:42 ` Tony Lindgren
2005-02-04 17:54 ` Zwane Mwaikambo
2005-02-04 18:58 ` Tony Lindgren
2005-02-04 19:24 ` Tony Lindgren
2005-02-05 23:00 ` Pavel Machek
2005-02-06 2:33 ` Tony Lindgren
2005-02-06 3:54 ` Tony Lindgren
2005-02-06 8:41 ` Pavel Machek
2005-02-06 8:50 ` Pavel Machek
2005-02-06 17:07 ` Tony Lindgren
2005-02-06 12:15 ` Pavel Machek
2005-02-06 17:08 ` Tony Lindgren
2005-02-06 8:11 ` Pavel Machek
2005-02-06 8:53 ` Lee Revell
2005-02-06 10:25 ` Pavel Machek
2005-02-07 22:08 ` George Anzinger
2005-02-06 17:10 ` Tony Lindgren
2005-02-06 18:34 ` Pavel Machek
2005-02-01 20:20 ` Lee Revell
2005-02-01 23:42 ` Tony Lindgren
2005-02-02 1:06 ` Eric St-Laurent
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050201212542.GA3691@openzaurus.ucw.cz \
--to=pavel@suse.cz \
--cc=andrea@suse.de \
--cc=arjan@infradead.org \
--cc=benh@kernel.crashing.org \
--cc=george@mvista.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.com \
--cc=schwidefsky@de.ibm.com \
--cc=tglx@linutronix.de \
--cc=tony@atomide.com \
--cc=zwane@arm.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome