From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dominik Brodowski Subject: Re: oops on resume Date: Thu, 5 Aug 2004 23:03:49 +0200 Sender: cpufreq-bounces@www.linux.org.uk Message-ID: <20040805210349.GA23087@dominikbrodowski.de> References: <20040805192613.GA9008@dominikbrodowski.de> <1091734482.10552.20.camel@pc> <20040805195248.GA32045@redhat.com> <1091736171.10552.26.camel@pc> <20040805200857.GA28775@redhat.com> <1091737170.10552.32.camel@pc> <20040805202941.GB28775@redhat.com> Mime-Version: 1.0 Return-path: Content-Disposition: inline In-Reply-To: <20040805202941.GB28775@redhat.com> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: cpufreq-bounces+glkc-cpufreq=gmane.org@www.linux.org.uk Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Dave Jones Cc: "Brian J. Murrell" , cpufreq@www.linux.org.uk On Thu, Aug 05, 2004 at 09:29:41PM +0100, Dave Jones wrote: > On Thu, Aug 05, 2004 at 04:19:30PM -0400, Brian J. Murrell wrote: > > > Yeah, me too. Any (one have any) idea how to calculate fsb for that > > sucker? > > Hunting for docs on developer.intel.com right now. So far I've turned > up nothing useful. Can you edit pentium4_get_frequency() in arch/i386/kernel/cpu/cpufreq/speedstep-lib.c > so that before the switch (fsb_code) { add a > printk ("FSB code = %d\n", fsb_code); _and_ enable SPEEDSTEP_DEBUG in both speedstep-ich.c and speedstep-lib.c > Hopefully, Intel are predictable and this is going to be '4'. > > > I may as well throw that code in there too to see if it > > alleviates the problem. > > reminds me, moving speedstep's dprintk over to the same style > as longhaul/powernow-k7 should happen sometime, then it's just a > module parameter away instead of a recompile. ... though I'd prefer if it'd be done at the cpufreq-core level, i.e. cpufreq_dprintk(); with a sysfs-exported ( /sys/parameters/cpufreq/debug ) boot-time parameter cpufreq.debug=1 Dominik