All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugme-daemon@bugzilla.kernel.org
To: cpufreq@www.linux.org.uk
Subject: [Bug 10654] New: cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed gets BUG on Transmeta Crusoe CPU
Date: Thu,  8 May 2008 19:22:45 -0700 (PDT)	[thread overview]
Message-ID: <bug-10654-3570@http.bugzilla.kernel.org/> (raw)

http://bugzilla.kernel.org/show_bug.cgi?id=10654

           Summary: cat
                    /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed
                    gets BUG on Transmeta Crusoe CPU
           Product: Power Management
           Version: 2.5
     KernelVersion: 2.6.25
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: cpufreq
        AssignedTo: cpufreq@www.linux.org.uk
        ReportedBy: masaki-c@nict.go.jp


Latest working kernel version: 2.6.24
Distribution: Fedora 9(rawhide)

Problem Description:

Reading from /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed
gets BUG() on Transmeta CPU.
See https://bugzilla.redhat.com/show_bug.cgi?id=443354 for more info.


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

             reply	other threads:[~2008-05-09  2:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-09  2:22 bugme-daemon [this message]
2008-05-09  7:08 ` [Bug 10654] cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed gets BUG on Transmeta Crusoe CPU bugme-daemon
2008-05-09  7:09 ` bugme-daemon
2008-05-09 12:13 ` bugme-daemon
2008-05-28 13:15 ` bugme-daemon
2008-05-28 19:07 ` bugme-daemon

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=bug-10654-3570@http.bugzilla.kernel.org/ \
    --to=bugme-daemon@bugzilla.kernel.org \
    --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.