From: Bruno Ducrot <ducrot@poupinou.org>
To: holbling@cpt.univ-mrs.fr
Cc: Dominik Brodowski <linux@dominikbrodowski.de>, cpufreq@www.linux.org.uk
Subject: Re: [PATCH] 2.6.5 speedstep on P4Ms
Date: Thu, 10 Jun 2004 11:10:22 +0200 [thread overview]
Message-ID: <20040610091022.GY13782@poupinou.org> (raw)
In-Reply-To: <40C7AF6C.1080408@cern.ch>
On Thu, Jun 10, 2004 at 12:46:36AM +0000, Christian Hoelbling wrote:
> hi dominik,
>
> thanks alot for your detailed reply and patience with a newbie. i have
> attached 2 patches w.r.t. 2.6.7-rc3 that should adress your suggestions.
>
> i also wonder about one thing, maybe you can help me on that. with the
> old speedstep driver, i would have occational hard freezups of my
> machine. this seems to be gone (just experimental evidence, since i
> didn't have one in a few days now where before they occured about
> hourly). so my guess is that something in this patch must have corrected
> it. since my machine just has one physical cpu, i really don't
> understand what went wrong before. do you have any idea on that?
>
IMHO the lockup is due to the fact we use local_irq_disable() but it
should be done more globally. I believe you may still have some lockup
still.
Cheers,
--
Bruno Ducrot
-- Which is worse: ignorance or apathy?
-- Don't know. Don't care.
next prev parent reply other threads:[~2004-06-10 9:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-08 17:15 [PATCH] 2.6.5 speedstep on P4Ms Christian Hoelbling
2004-06-08 15:30 ` Bruno Ducrot
2004-06-08 23:53 ` Christian Hoelbling
2004-06-09 15:47 ` Dominik Brodowski
2004-06-09 16:09 ` Bruno Ducrot
2004-06-09 16:29 ` Dave Jones
2004-06-09 16:53 ` Dominik Brodowski
2004-06-09 18:32 ` Mattia Dongili
2004-06-10 0:46 ` Christian Hoelbling
2004-06-10 8:30 ` Dominik Brodowski
2004-06-10 11:20 ` Dave Jones
2004-06-10 9:10 ` Bruno Ducrot [this message]
2004-06-10 15:37 ` Bruno Ducrot
2004-06-10 16:44 ` Dominik Brodowski
2004-06-10 19:26 ` [PATCH] Remove notify in speedstep_set_state [1/2] Bruno Ducrot
2004-06-10 19:28 ` [PATCH] Remove notify in speedstep_set_state [2/2] Bruno Ducrot
2004-06-10 19:35 ` [PATCH] security fix for speedstep-smi Bruno Ducrot
2004-06-10 19:44 ` [PATCH] 2.6.5 speedstep on P4Ms Bruno Ducrot
2004-06-10 20:04 ` [PATCH] replace for_each_cpu with for_each_cpu_mask (was Re: [PATCH] 2.6.5 speedstep on P4Ms) Bruno Ducrot
2004-06-10 21:38 ` Dave Jones
2004-06-11 9:55 ` Bruno Ducrot
-- strict thread matches above, loose matches on Subject: below --
2004-06-11 0:21 [PATCH] 2.6.5 speedstep on P4Ms Christian Hoelbling
2004-06-11 0:30 Christian Hoelbling
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=20040610091022.GY13782@poupinou.org \
--to=ducrot@poupinou.org \
--cc=cpufreq@www.linux.org.uk \
--cc=holbling@cpt.univ-mrs.fr \
--cc=linux@dominikbrodowski.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox