[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.0.99999.0801161524250.3764@localhost.localdomain>
Date: Wed, 16 Jan 2008 15:28:54 +0100 (CET)
From: Thomas Gleixner <tglx@...utronix.de>
To: Dhaval Giani <dhaval@...ux.vnet.ibm.com>
cc: Andrew Paprocki <andrew@...iboo.com>, linux-kernel@...r.kernel.org,
Balaji Rao <balajirrao@...il.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Ingo Molnar <mingo@...e.hu>, clemens@...isch.de,
venkatesh.pallipadi@...el.com, bob.picco@...com
Subject: Re: HPET timer broken using 2.6.23.13 / nanosleep() hangs
On Wed, 16 Jan 2008, Thomas Gleixner wrote:
> On Sun, 13 Jan 2008, Dhaval Giani wrote:
> > On Sun, Jan 13, 2008 at 08:10:46AM -0500, Andrew Paprocki wrote:
> > > I applied the patch to my 2.6.23.13 tree and upon reboot it stopped right after:
> > >
> > > Clocksource tsc unstable (delta = ... ns)
> > > Time: hpet clocksource has been installed.
> > >
> > > It locked up hard.. cursor stopped blinking and SysRq isn't working either.
>
> The hint is in the original report:
>
> Clocksource tsc unstable (delta = 500013666 ns)
>
> That means, that the TSC was counting, but HPET not. So it looks like
> the HPET readout is stale. Which explains, why after switching to HPET
> clocksource the time system gets hosed.
>
> I wonder why the HPET counter works check did not catch this.
>
> Can you please apply the path below and provide the output ?
Oh. Stupid me. This is 2.6.23. So the patch won't apply.
Andrew, can you please check, whether 2.6.24-rc8 works on your machine ?
I look into a backport fix for 2.6.23 later.
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