[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.1.10.0809082254550.3271@apollo.tec.linutronix.de>
Date: Mon, 8 Sep 2008 22:56:15 +0200 (CEST)
From: Thomas Gleixner <tglx@...utronix.de>
To: Stefan Hellermann <stefan@...2masters.de>
cc: Frans Pop <elendil@...net.nl>, linux-kernel@...r.kernel.org
Subject: Re: [regression] __tick_program_event of hpet is stuck
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists