cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
Cc: Dave Jones <davej@redhat.com>,
	pjones@redhat.com, cpufreq@lists.linux.org.uk
Subject: Re: ondemand vs suspend.
Date: Mon, 26 Jun 2006 12:23:21 -0700	[thread overview]
Message-ID: <44A03429.40304@goop.org> (raw)
In-Reply-To: <EB12A50964762B4D8111D55B764A84541D4DBA@scsmsx413.amr.corp.intel.com>

Pallipadi, Venkatesh wrote:
> I am not able to reprocude this on my Core Duo system.  At this point I
> will need some more information on what exactly happens at this point of
> failure to start looking at the code.. Like questions above. Does
> scaling_available_frequencies still show all freqs. What is *max *min
> values in /sys/.../cpufreq/ ..
>   
Yes, all the expected frequencies are there.  I sent you mail with all 
the contents of /sys/.../cpu?/cpufreq/... the other day; should I resend it?

Thanks,
    J

  reply	other threads:[~2006-06-26 19:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-26 18:43 ondemand vs suspend Pallipadi, Venkatesh
2006-06-26 19:23 ` Jeremy Fitzhardinge [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-06-26 22:12 Pallipadi, Venkatesh
2006-06-28 22:20 ` Jeremy Fitzhardinge
2006-06-26 20:24 Pallipadi, Venkatesh
2006-06-26 20:58 ` Jeremy Fitzhardinge
2006-06-14  2:50 Pallipadi, Venkatesh
2006-06-14  3:08 ` Peter Jones
2006-06-19 22:52 ` Jeremy Fitzhardinge
2006-06-21 18:54   ` Venkatesh Pallipadi
2006-06-21 21:01     ` Jeremy Fitzhardinge
2006-06-23 22:45     ` Jeremy Fitzhardinge
2006-06-21 18:35 ` Venkatesh Pallipadi
2006-06-13 23:03 Pallipadi, Venkatesh
2006-06-13 23:06 ` Dave Jones
2006-06-13 20:53 Dave Jones

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=44A03429.40304@goop.org \
    --to=jeremy@goop.org \
    --cc=cpufreq@lists.linux.org.uk \
    --cc=davej@redhat.com \
    --cc=pjones@redhat.com \
    --cc=venkatesh.pallipadi@intel.com \
    /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