From owner-freebsd-current@FreeBSD.ORG Fri Jun 24 20:01:14 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9B76316A41C; Fri, 24 Jun 2005 20:01:14 +0000 (GMT) (envelope-from vanco@satro.sk) Received: from mail.satronet.sk (mail.satronet.sk [217.144.16.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id 53B0943D48; Fri, 24 Jun 2005 20:01:13 +0000 (GMT) (envelope-from vanco@satro.sk) Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.satronet.sk (Postfix) with ESMTP id A4A4C16050715; Fri, 24 Jun 2005 22:01:12 +0200 (CEST) Received: from mail.satronet.sk ([127.0.0.1]) by localhost (mail [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 22039-01; Fri, 24 Jun 2005 22:01:11 +0200 (CEST) Received: from [10.1.14.183] (strojar.garda.sk [147.175.8.5]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.satronet.sk (Postfix) with ESMTP id 5D4CE16051D58; Fri, 24 Jun 2005 22:01:11 +0200 (CEST) Message-ID: <42BC6684.2000804@satro.sk> Date: Fri, 24 Jun 2005 22:01:08 +0200 From: Michal Vanco User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050620) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Hajimu UMEMOTO References: <42BC519E.8010309@satro.sk> In-Reply-To: X-Enigmail-Version: 0.91.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by ANTIvirus at satronet.sk Cc: freebsd-current@freebsd.org Subject: Re: cpufreq & enhanced speedstep X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 24 Jun 2005 20:01:14 -0000 Hajimu UMEMOTO wrote: > > I saw similar error on my laptop (Panasonic Let'snote CF-R4). It > occured when doing kldload cpufreq after boot. In my case, I wrote > cpufreq_load="YES" into my /boot/loader.conf, then est(4) became > usable. > wow ... after doing this everything seems working: est0: on cpu0 p4tcc0: on cpu0 thanks ... should't this behavior be treated as a bug? michal