cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: "Brian J. Murrell" <brian@interlinx.bc.ca>
Cc: Dominik Brodowski <linux@dominikbrodowski.de>, cpufreq@www.linux.org.uk
Subject: Re: oops on resume
Date: Thu, 5 Aug 2004 20:52:48 +0100	[thread overview]
Message-ID: <20040805195248.GA32045@redhat.com> (raw)
In-Reply-To: <1091734482.10552.20.camel@pc>

On Thu, Aug 05, 2004 at 03:34:42PM -0400, Brian J. Murrell wrote:
 > On Thu, 2004-08-05 at 21:26 +0200, Dominik Brodowski wrote:
 > > cat /sys/devices/system/cpu/cpu0/cpufreq/*
 > 
 > Just to be sure you knew which values where for which nodes I did a
 > 
 > grep ".*" /sys/devices/system/cpu/cpu0/cpufreq/*
 > 
 > and got:
 > 
 > /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq:1200000
 > /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq:2200000
 > /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq:1200000
 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies:2200000 1200000
 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors:userspace performance
 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq:1200000
 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_driver:speedstep-ich
 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor:userspace
 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq:2200000
 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq:1200000
 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed:1200000


My guess is that speedstep_get_processor_frequency() is returning null

What does /proc/cpuinfo say ?

		Dave

  reply	other threads:[~2004-08-05 19:52 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-05 19:02 oops on resume Brian J. Murrell
2004-08-05 19:26 ` Dominik Brodowski
2004-08-05 19:34   ` Brian J. Murrell
2004-08-05 19:52     ` Dave Jones [this message]
2004-08-05 20:02       ` Brian J. Murrell
2004-08-05 20:08         ` Dave Jones
2004-08-05 20:19           ` Brian J. Murrell
2004-08-05 20:29             ` Dave Jones
2004-08-05 21:03               ` Dominik Brodowski
2004-08-05 21:26               ` Brian J. Murrell
2004-08-05 21:27                 ` Dave Jones
2004-08-05 21:29                 ` Dave Jones
2004-08-05 21:09             ` Dominik Brodowski
2004-08-05 21:45               ` Brian J. Murrell
2004-08-06 17:14                 ` Dominik Brodowski
2004-08-06 17:43               ` Brian J. Murrell
2004-08-06 17:55                 ` Dominik Brodowski
2004-08-06 21:13                   ` Dave Jones
2004-08-06 21:18                     ` Brian J. Murrell
2004-08-06 21:44                       ` Dave Jones
2004-08-06 22:10                         ` Brian J. Murrell
2004-08-06 22:51                           ` Dave Jones
2004-08-06 23:00                             ` Brian J. Murrell
2004-08-06 23:23                               ` Dave Jones
2004-08-07 13:24                   ` Dominik Brodowski
2004-08-07 19:03                     ` Brian J. Murrell
2004-08-08 16:24                       ` Dominik Brodowski
2004-08-09 13:37                         ` Brian J. Murrell
2004-08-09 14:53                           ` Dominik Brodowski
2004-08-09 17:27                         ` Brian J. Murrell
2004-08-09 19:38                           ` Dominik Brodowski

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=20040805195248.GA32045@redhat.com \
    --to=davej@redhat.com \
    --cc=brian@interlinx.bc.ca \
    --cc=cpufreq@www.linux.org.uk \
    --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