From: Jonathan Woithe <jwoithe@physics.adelaide.edu.au>
To: tglx@linutronix.de
Cc: jwoithe@physics.adelaide.edu.au (Jonathan Woithe),
linux-kernel@vger.kernel.org
Subject: Re: 2.6.16-rt11: Hires timer makes sleep wait far too long
Date: Mon, 10 Apr 2006 16:57:33 +0930 (CST) [thread overview]
Message-ID: <200604100727.k3A7RX6c017659@auster.physics.adelaide.edu.au> (raw)
In-Reply-To: <1144319324.5344.688.camel@localhost.localdomain> from "Thomas Gleixner" at Apr 06, 2006 12:28:43 PM
Thomas
> On Wed, 2006-04-05 at 09:51 +0930, Jonathan Woithe wrote:
> > ENABLING IO-APIC IRQs
> > ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
> > Event source pit new caps set: 05
> > Event source lapic installed with caps set: 02
> > :
> > Time: tsc clocksource has been installed.
> > hrtimers: Switched to high resolution mode CPU 0
> > :
> > Time: acpi_pm clocksource has been installed.
> > hrtimers: Switched to high resolution mode CPU 0
>
> Nothing wrong so far. I have to find a test box with pm timer to get
> some more info.
FYI, the same problem occurs in 2.6.16-rt12. I note that rt14 is out now
so I'll give that a go overnight and let you know the results.
One final observation I did make under 2.6.16-rt12: in the first 30 seconds
or there abouts after the boot, "sleep 1" did result in short sleeps - they
weren't always 1 second, but they were in the ballpark. After the machine
had been up for 30-60 seconds however, "sleep 1" would produce waits along
the lines of what I reported in the initial report - anywhere between 20
seconds to 45 seconds and more. There didn't seem to be any gradual
increase either - the "sleep 1" wait times seemed to jump from 1-2 seconds
up to 20-30 seconds very suddenly.
Regards
jonathan
prev parent reply other threads:[~2006-04-10 7:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-04 3:40 Jonathan Woithe
2006-04-04 4:26 ` Thomas Gleixner
2006-04-05 0:21 ` Jonathan Woithe
2006-04-06 10:28 ` Thomas Gleixner
2006-04-06 23:58 ` Jonathan Woithe
2006-04-10 7:27 ` Jonathan Woithe [this message]
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=200604100727.k3A7RX6c017659@auster.physics.adelaide.edu.au \
--to=jwoithe@physics.adelaide.edu.au \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®