From owner-freebsd-current@FreeBSD.ORG Fri Aug 1 18:21:32 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 786FE25F; Fri, 1 Aug 2014 18:21:32 +0000 (UTC) Received: from mail-qg0-x231.google.com (mail-qg0-x231.google.com [IPv6:2607:f8b0:400d:c04::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 277182412; Fri, 1 Aug 2014 18:21:32 +0000 (UTC) Received: by mail-qg0-f49.google.com with SMTP id j107so6241781qga.36 for ; Fri, 01 Aug 2014 11:21:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=rlLT1/V9zpSYVnkUnF3kul7kCJdvh0H1fn3Tker2zsY=; b=FXGTsM7aciCSyZ1jXe/veIynRzQ8XAwp1OhZi9rUpARS27SnJZd0AOnQlXNPYPvphv T0ZOzeRRBNfuvdB8eaVsxcdD6rBd2DgR40RYbWsOckL6OLdAWDC30hilsXt9x3VJddOj KMBsAgzw6OLHfKoR9GR1rxs8AbXlEvKvjZBvY9GsqyGUedjSBKBP5Pe1owYxvYIALE6U 2K3EUwi70eLEb21OE0J7ZVK9gjMT6vS2KBqXC7j+stHnBc2xu/m13tlo5SuhBs55qBh4 SFa5757j17QWiI285O7J2p3sN2TqECa9FwWyEVH2dFCQR6XtFvOPfD4xjMMDZgeM7h0f Mz8A== MIME-Version: 1.0 X-Received: by 10.229.38.3 with SMTP id z3mr5962669qcd.17.1406917291276; Fri, 01 Aug 2014 11:21:31 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.1.6 with HTTP; Fri, 1 Aug 2014 11:21:31 -0700 (PDT) In-Reply-To: <20140801181800.GA18604@mouf.net> References: <20140731142100.GP92036@heechee.tobez.org> <53DA6727.7080702@gmail.com> <20140731162227.GQ92036@heechee.tobez.org> <20140801181800.GA18604@mouf.net> Date: Fri, 1 Aug 2014 11:21:31 -0700 X-Google-Sender-Auth: i4bUaIU-wbsR2X0jztp5C8cfxa4 Message-ID: Subject: Re: Fresh current (r269328) amd64: high load average while idle, slow keyboard reaction From: Adrian Chadd To: Steve Wills Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: =?UTF-8?Q?Jan_Kokem=C3=BCller?= , freebsd-current , Anton Berezin X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Aug 2014 18:21:32 -0000 Hi! On 1 August 2014 11:18, Steve Wills wrote: > Hi, > > On Thu, Jul 31, 2014 at 06:22:27PM +0200, Anton Berezin wrote: >> Jan, >> >> On Thu, Jul 31, 2014 at 05:56:23PM +0200, Jan Kokem=C3=BCller wrote: >> > On 31.07.2014 16:21, Anton Berezin wrote: >> > >At the console, depressing and holding a key does not lead to auto-re= peat. >> > > >> > >At the console, sometimes a key only appears on the terminal after an= other >> > >key is pressed. >> > >> > Maybe this is a problem caused by a misdetected clock source? I've had= this >> > problem as well. >> > >> > Try to set kern.timecounter.hardware and/or kern.eventtimer.timer to o= ther >> > settings that are listed in kern.timecounter.choice and >> > kern.eventtimer.choice, such as HPET which works great for me. >> >> Setting both to HPET certainly helped the LA. I cannot check the keyboa= rd >> input until tomorrow, but chances are that it is indeed the fix. > > Just wanted to throw in another datapoint, I had this issue too and setti= ng > kern.eventtimer.timer=3DHPET alone solved it for me. Please throw this into a bug report ticket and poke mav@ about it. -a