From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dominik Brodowski Subject: Re: Problem with ondemand on Athlon Date: Tue, 11 Nov 2003 19:29:38 +0100 Sender: cpufreq-bounces+glkc-cpufreq=gmane.org@www.linux.org.uk Message-ID: <20031111182938.GA4825@brodo.de> References: <20031105182110.GA922@inferi.kami.home> <20031110205912.GB7149@brodo.de> <20031111095143.GC930@inferi.kami.home> Mime-Version: 1.0 Return-path: Content-Disposition: inline In-Reply-To: <20031111095143.GC930@inferi.kami.home> 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: cpufreq@www.linux.org.uk On Tue, Nov 11, 2003 at 10:51:43AM +0100, Mattia Dongili wrote: > On Mon, Nov 10, 2003 at 09:59:12PM +0100, Dominik Brodowski wrote: > > This is really strange... will provide a DEBUG()-printk patch soon, would be > > great if you could test it then... > > of course I can. In the meantime if you can tell a couple of interesting > functions and variables, I could add some printk-s by myself (if I get > some spare time before you do) Basically the ->governor function in the ondemand() governor, the __cpufreq_governor, cpufreq_governor, cpufreq_set_policy after the call to __cpufreq_set_policy, and the sysfs fuctions (show / store / store_scaling_governor). > > > > pass "clock=pit" as a command line argument > > > > > > this semms not to be a valid argument here > > > > ? clock=pit specifies that the PIT should be used instead of the TSC as > > timing source... so it should be a valid boot argument. > > sorry... my bad. I used it as a p4_clockmod argument Sorry for my unclear comment "command line argument"... > I'll re-test it as soon as possible. Many thanks. Dominik