From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S266155AbUFUIXq (ORCPT ); Mon, 21 Jun 2004 04:23:46 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S266164AbUFUIXp (ORCPT ); Mon, 21 Jun 2004 04:23:45 -0400 Received: from gprs187-64.eurotel.cz ([160.218.187.64]:12416 "EHLO midnight.ucw.cz") by vger.kernel.org with ESMTP id S266155AbUFUIWE (ORCPT ); Mon, 21 Jun 2004 04:22:04 -0400 Date: Mon, 21 Jun 2004 10:22:35 +0200 From: Vojtech Pavlik To: Jeff Garzik Cc: Linux Kernel Subject: Re: 2.6.7-bk way too fast Message-ID: <20040621082235.GA1200@ucw.cz> References: <40D64DF7.5040601@pobox.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <40D64DF7.5040601@pobox.com> User-Agent: Mutt/1.4.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Jun 20, 2004 at 10:54:47PM -0400, Jeff Garzik wrote: > Something is definitely screwy with the latest -bk. I updated from a > kernel ~1 week ago, and all timer-related stuff is moving at a vastly > increased rate. My guess is twice as fast. Most annoying is the system > clock advances at twice normal rate, and keyboard repeat is so sensitive > I am spending quite a bit of time typing this message, what with having > to delettte (<== example) extra characters. Double-clicking is also > broken :( Q: Are you using the atkbd.softrepeat=1 parameter? Or an USB keyboard? If not, you shouldn't be getting faster repeats even if the timer were off, because the repat shoul be generated by the keyboard itself. > dmesg and config attached. > > My guess would be someone broke HPET, but maybe not judging from other > lkml reports. > > This is the _first_ 2.6 kernel that has been obviously and wildly broken > for me :( -- Vojtech Pavlik SuSE Labs, SuSE CR