From: Dave Jones <davej@redhat.com>
To: Ashley Pittman <ashley@quadrics.com>
Cc: cpufreq <cpufreq@www.linux.org.uk>
Subject: Re: Patch to stop i386 longhaul from deadlocking the kernel
Date: Thu, 20 Nov 2003 12:46:13 +0000 [thread overview]
Message-ID: <20031120124613.GA12049@redhat.com> (raw)
In-Reply-To: <1068045570.23318.34.camel@ashley>
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
next prev parent reply other threads:[~2003-11-20 12:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-05 15:19 Patch to stop i386 longhaul from deadlocking the kernel Ashley Pittman
2003-11-20 12:46 ` Dave Jones [this message]
2003-11-20 13:24 ` Ashley Pittman
2003-11-20 13:40 ` Dave Jones
2003-11-20 14:12 ` Ashley Pittman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20031120124613.GA12049@redhat.com \
--to=davej@redhat.com \
--cc=ashley@quadrics.com \
--cc=cpufreq@www.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.