cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Nigel Cunningham <ncunningham@cyclades.com>
To: Pat Double <pat@patdouble.com>,
	Cpu-freq mailing list <cpufreq@www.linux.org.uk>
Cc: Suspend2 Devel List <suspend2-devel@lists.suspend2.net>
Subject: Re: p4-clockmod help
Date: Mon, 12 Dec 2005 10:29:37 +1000	[thread overview]
Message-ID: <1134347376.3810.8.camel@localhost> (raw)
In-Reply-To: <200512100652.41406.pat@patdouble.com>

Hi again Pat et al.

On Sat, 2005-12-10 at 22:52, Pat Double wrote:
> On Friday 09 December 2005 19:14, Bojan Smojver wrote:
> > On Fri, 2005-12-09 at 11:07 -0600, Pat Double wrote:
> > > Has anyone been successful resuming with the p4-clockmod module loaded,
> > > or compiled in?
> >
> > It works on my notebook with FC Rawhide kernels and suspend2.
> 
> It does not work well here. I believe it is because I have a P4 HT, the SMP 
> part is causing problems. I get a BUG sometime after it starts writing the 
> image. Normally it happens while writing the image but can also happen during 
> the atomic copy. I tried to disable calls to change the freq during suspend 
> but I do not even get the suspend function called until the atomic copy, so 
> the bug happens before then. I do not know how to fix this.
> 
> Nigel, any help?
> 
> I get a BUG at p4-clockmod.c, line 142:
> BUG_ON(smp_processor_id() != i);
> 
> The error is an invalid operand 0000
> 
> Also, writing the image becomes VERY slow with p4-clockmod loaded. I do not 
> have any governer loaded except performance.

Since any fix should come from the cpufreq guys, and they'll understand
the issue better than me, I want to refer the problem to them...

Cqufreq guys, I've only had a superficial look at this, but this BUG_ON
appears to be triggering because hot unplugging of cpu1 is not being
taken into account. Can you please help?

Regards,

Nigel

           reply	other threads:[~2005-12-12  0:29 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <200512100652.41406.pat@patdouble.com>]

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=1134347376.3810.8.camel@localhost \
    --to=ncunningham@cyclades.com \
    --cc=cpufreq@www.linux.org.uk \
    --cc=pat@patdouble.com \
    --cc=suspend2-devel@lists.suspend2.net \
    /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