From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dave Jones Subject: Re: Patch to stop i386 longhaul from deadlocking the kernel Date: Thu, 20 Nov 2003 12:46:13 +0000 Sender: cpufreq-bounces+glkc-cpufreq=gmane.org@www.linux.org.uk Message-ID: <20031120124613.GA12049@redhat.com> References: <1068045570.23318.34.camel@ashley> Mime-Version: 1.0 Return-path: Content-Disposition: inline In-Reply-To: <1068045570.23318.34.camel@ashley> 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: Ashley Pittman Cc: cpufreq On Wed, Nov 05, 2003 at 03:19:30PM +0000, Ashley Pittman wrote: > This patch stops the deadlock in the case where the speed of the fsb is > undetected. I've also made the guess function more vague so it can > detect the correct speed for my cpu, it might need to be even more vague > for other cpu's. 0xbf seems bizarre. Something went wrong somewhere. Can you put some printk's in there, so I can see what values _guess() and guess_fsb() are being called with ? > I am still unable to change the CPU speed even with this patch however. You're not the first report I've had of this. I'm not sure what I broke. It was a case of 'fix for some, break others'. > longhaul: VIA C3 'Ezra' [C5C] CPU detected. Longhaul v1 supported. > longhaul: MinMult=3.0x MaxMult=6.0x > longhaul: FSB: 0MHz Lowestspeed=0MHz Highestspeed=0MHz > > At this point the whole system would lock solid. Why it locks up is also odd. Dave