mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Stefan Hellermann <stefan@the2masters.de>
Cc: Frans Pop <elendil@planet.nl>, linux-kernel@vger.kernel.org
Subject: Re: [regression] __tick_program_event of hpet is stuck
Date: Mon, 8 Sep 2008 22:56:15 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.1.10.0809082254550.3271@apollo.tec.linutronix.de> (raw)
In-Reply-To: <48C57046.5090509@the2masters.de>

On Mon, 8 Sep 2008, Stefan Hellermann wrote:
> Frans Pop schrieb:
> > On Monday 08 September 2008, Frans Pop wrote:
> >   
> > > With current git head (v2.6.27-rc5-319-g7686ad5) I'm seeing repeated
> > > occurrences of the following on my HP Compaq 2510p laptop. Not seen
> > > with earlier kernels, including 2.6.27-rc5.
> > >     
> > 
> > I meant repeated as in "after different boots", but I now also see repeats
> > when I leave the system on for some time. It keeps increasing the
> > min_delta_ns to ever higher values.
> > 
> > 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
> > 
> > The call trace is basically the same each time.
> >   
> Exactly the same problem here. This is a Lenovo Thinkpad R61 with current git
> head (7686ad56).

Can you both please provide the full dmesg output and the out put from
lspci -vvv please ?

Thanks,

	tglx

  reply	other threads:[~2008-09-08 20:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-07 23:14 Frans Pop
2008-09-08  1:13 ` Frans Pop
2008-09-08 18:34   ` Stefan Hellermann
2008-09-08 20:56     ` Thomas Gleixner [this message]
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
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=alpine.LFD.1.10.0809082254550.3271@apollo.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=elendil@planet.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stefan@the2masters.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®