[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <46B371AA.1040906@redhat.com>
Date: Fri, 03 Aug 2007 14:19:22 -0400
From: Chuck Ebbert <cebbert@...hat.com>
To: Ben Collins <ben.collins@...ntu.com>
CC: Linus Torvalds <torvalds@...ux-foundation.org>,
Cal Peake <cp@...olutedigital.net>,
Gabriel C <nix.or.die@...glemail.com>,
Frank Hale <frankhale@...il.com>,
Kernel Mailing List <linux-kernel@...r.kernel.org>,
Kernel ACPI Mailing List <linux-acpi@...r.kernel.org>,
len.brown@...el.com, Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...e.hu>,
Andrew Morton <akpm@...ux-foundation.org>,
Andi Kleen <andi@...stfloor.org>
Subject: Re: ACPI on Averatec 2370
On 08/03/2007 11:52 AM, Ben Collins wrote:
>
> This is the same problem I'm seeing (See Subject: Regression in 2.6.22,
> clock problems on Turion with 32-bit kernel).
>
> This commit is what we bisected to:
>
> commit e9e2cdb412412326c4827fc78ba27f410d837e6e
> Author: Thomas Gleixner <tglx@...utronix.de>
> Date: Fri Feb 16 01:28:04 2007 -0800
>
> [PATCH] clockevents: i386 drivers
>
Yes, and the lapic timer apparently worked okay until then, right?
FWIW when you disable it this appears in the boot messages:
Clockevents: could not switch to one-shot mode:<6>Clockevents: could not switch to one-shot mode: lapic is not functional.
Could not switch to high resolution mode on CPU 0
lapic is not functional.
Could not switch to high resolution mode on CPU 1
Yet "highres=off" does not fix the problem. Very strange...
-
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