From: Lee Revell <rlrevell@joe-job.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Tony Lindgren <tony@atomide.com>,
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>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Dynamic tick, version 050127-1
Date: Sun, 06 Feb 2005 03:53:09 -0500 [thread overview]
Message-ID: <1107679990.3532.37.camel@krustophenia.net> (raw)
In-Reply-To: <20050206081137.GA994@elf.ucw.cz>
On Sun, 2005-02-06 at 09:11 +0100, Pavel Machek wrote:
> I do have CONFIG_X86_PM_TIMER enabled, but it seems by board does not
> have such piece of hardware:
>
> pavel@amd:/usr/src/linux-mm$ dmesg | grep -i "time\|tick\|apic"
> PCI: Setting latency timer of device 0000:00:11.5 to 64
> pavel@amd:/usr/src/linux-mm$
If you are sure that machine supports ACPI, maybe this is your problem
(from the POSIX high res timer patch):
If you enable the ACPI pm timer and it cannot be found, it is
possible that your BIOS is not producing the ACPI table or
that your machine does not support ACPI. In the former case,
see "Default ACPI pm timer address". If the timer is not
found the boot will fail when trying to calibrate the 'delay'
loop.
[...]
config HIGH_RES_TIMER_ACPI_PM_ADD
int "Default ACPI pm timer address"
depends on HIGH_RES_TIMER_ACPI_PM
default 0
help
This option is available for use on systems where the BIOS
does not generate the ACPI tables if ACPI is not enabled. For
example some BIOSes will not generate the ACPI tables if APM
is enabled. The ACPI pm timer is still available but cannot
be found by the software. This option allows you to supply
the needed address. When the high resolution timers code
finds a valid ACPI pm timer address it reports it in the boot
messages log (look for lines that begin with
"High-res-timers:"). You can turn on the ACPI support in the
BIOS, boot the system and find this value. You can then enter
it at configure time. Both the report and the entry are in
decimal.
HTH,
Lee
next prev parent reply other threads:[~2005-02-06 8:53 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-27 21:29 [PATCH] Dynamic tick, version 050127-1 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
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 [this message]
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=1107679990.3532.37.camel@krustophenia.net \
--to=rlrevell@joe-job.com \
--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=pavel@ucw.cz \
--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