public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frans Pop <elendil@planet.nl>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [regression] __tick_program_event of hpet is stuck
Date: Tue, 9 Sep 2008 14:38:56 +0200	[thread overview]
Message-ID: <200809091438.57158.elendil@planet.nl> (raw)
In-Reply-To: <alpine.LFD.1.10.0809091248590.3271@apollo.tec.linutronix.de>

On Tuesday 09 September 2008, Thomas Gleixner wrote:
> > CE: __tick_program_event of hpet is stuck 1468f1b3c9 1468f1c751
> > CE: increasing min_delta_ns 5000 to 10000 nsec
> > [...]
> > CE: __tick_program_event of hpet is stuck 33576032f74 33576035684
> > CE: increasing min_delta_ns 10000 to 20000 nsec
> > [...]
> > CE: __tick_program_event of hpet is stuck 63242b30d28 63242b35b48
> > CE: increasing min_delta_ns 20000 to 40000 nsec
>
> what's the highest value which you have seen ?

These are the highest I've seen, but that's possibly because I haven't 
left the system running for longer. There's just under an hour between 
the messages (kern.log has 00:59:17, 01:56:38, 02:51:23 for the three 
increases listed above) with the first fairly shortly after boot.

I've just awakened the laptop from suspend and will let it sit for the 
rest of the day. If I get any higher values I'll let you know.

  reply	other threads:[~2008-09-09 12:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-07 23:14 [regression] __tick_program_event of hpet is stuck Frans Pop
2008-09-08  1:13 ` Frans Pop
2008-09-08 18:34   ` Stefan Hellermann
2008-09-08 20:56     ` Thomas Gleixner
2008-09-08 22:11       ` Frans Pop
2008-09-08 22:12       ` Guillaume Chazarain
2008-09-09 10:49   ` Thomas Gleixner
2008-09-09 12:38     ` Frans Pop [this message]
2008-09-09 13:27       ` Thomas Gleixner
2008-09-09 19:20         ` Frans Pop
2008-09-09 19:36           ` Thomas Gleixner

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=200809091438.57158.elendil@planet.nl \
    --to=elendil@planet.nl \
    --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