[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1281385169.5065.0.camel@zwerg>
Date: Mon, 09 Aug 2010 22:19:29 +0200
From: Alexey Fisher <bug-track@...her-privat.net>
To: john stultz <johnstul@...ibm.com>
Cc: Priit Laes <plaes@...es.org>,
linux-kernel <linux-kernel@...r.kernel.org>, tglx@...utronix.de,
Chris Wilson <chris@...is-wilson.co.uk>
Subject: Re: [BISECTED/2.6.35+] Regression: Machine runs really slowly
after commit f12a15be
On Mo, 2010-08-09 at 12:51 -0700, john stultz wrote:
> On Mon, 2010-08-09 at 21:38 +0200, Alexey Fisher wrote:
> > cat /sys/devices/system/clocksource/clocksource0/current_clocksource
> > hpet
> >
> > cat /sys/devices/system/clocksource/clocksource0/available_clocksource
> > hpet acpi_pm
>
>
> On Mon, 2010-08-09 at 22:43 +0300, Priit Laes wrote:
> > cat /sys/devices/system/clocksource/clocksource0/current_clocksource
> > hpet
> > cat /sys/devices/system/clocksource/clocksource0/available_clocksource
> > hpet acpi_pm
>
>
> Ok. Good. Chris Wilson has created the following patch which should
> hopefully resolve this issue. It would be great if you could try booting
> with it to verify that there are no other problems lurking here.
>
> Thanks again for the great bug reporting!
>
> thanks
> -john
>
>
> From: Chris Wilson <chris@...is-wilson.co.uk>
> Subject: [PATCH] x86/hpet: Use the FSEC_PER_SEC constant for femto-second
> periods
>
> The current computation, introduced with f12a15be63, of FSEC_PER_SEC using
> the multiplication of (FSEC_PER_NSEC * NSEC_PER_SEC) is performed only
> with 32bit integers on small machines, resulting in an overflow and a
> *very* short intervals being programmed. An interrupt storm follows.
>
> Note that we also have to specify FSEC_PER_SEC as being long long to
> overcome the same limitations.
>
> Signed-off-by: Chris Wilson <chris@...is-wilson.co.uk>
> Signed-off-by: John Stultz <johnstul@...ibm.com>
> Cc: Thomas Gleixner <tglx@...utronix.de>
> ---
This patch work for me. At least it boot.
Tank you.
--
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