On Tue, 15 Jan 2008, Andrew Morton wrote:
> On Thu, 10 Jan 2008 14:36:12 +0200 "Denys Fedoryshchenko" <[EMAIL PROTECTED]>
> wrote:
>
> > Hi
> >
> > I have same issue, but it's never passed synchronization.
> >
> > Jan 10 12:59:44 visp-1 Time: tsc clocksource has been installed.
> > Jan 10 13:41
Latest, 2.6.24-rc7, and 2.6.23 is the same.
If more information required, tell me. It is btw not latest (not based on
Core2) Xeon.
On Tue, 15 Jan 2008 02:17:20 -0800, Andrew Morton wrote
> On Thu, 10 Jan 2008 14:36:12 +0200 "Denys Fedoryshchenko"
> <[EMAIL PROTECTED]> wrote:
>
> > Hi
> >
> >
On Thu, 10 Jan 2008 14:36:12 +0200 "Denys Fedoryshchenko" <[EMAIL PROTECTED]>
wrote:
> Hi
>
> I have same issue, but it's never passed synchronization.
>
> Jan 10 12:59:44 visp-1 Time: tsc clocksource has been installed.
> Jan 10 13:41:51 visp-1 ACPI: HPET 000F29CD, 0038 (r1 DELL PE_SC3
Hi
I have same issue, but it's never passed synchronization.
Jan 10 12:59:44 visp-1 Time: tsc clocksource has been installed.
Jan 10 13:41:51 visp-1 ACPI: HPET 000F29CD, 0038 (r1 DELL PE_SC3 1
DELL1)
Jan 10 13:41:51 visp-1 ACPI: HPET id: 0x8086a201 base: 0xfed0
Jan 10 13:4
I'm seeing the same error as reported by Sami Farin earlier today [1], but
from my logs I can see that the issue is intermittent (2/3 failures). The
logs indicate that the issue was introduced with 2.6.22 as TSC sync was
correct for all boots with 2.6.21-6.
My system is also Pentium D: Intel(R) Pe
/var/log # grep -Ei "hpet|tsc" dmesg-2.6.19.7 dmesg.2.6.22.6-x86_64
dmesg-2.6.19.7:ACPI: HPET (v001 INTEL DQ965GF 0x15db MSFT 0x0113) @
0x3e6f2000
dmesg-2.6.19.7:ACPI: HPET id: 0x8086a201 base: 0xfed0
dmesg-2.6.19.7:[ 34.337155] hpet0: at MMIO 0xfed0, IRQs 2, 8, 0
dmesg-2.6.19
6 matches
Mail list logo