From: "Alexander Perschbacher" <alexander.perschbacher@rub.de>
To: cpufreq@vger.kernel.org
Subject: Re: Bug entdeckt
Date: 3 Feb 2012 11:31:20 +0100 [thread overview]
Message-ID: <11576422.T8BdOecNyQ@elabi> (raw)
In-Reply-To: <20120203101612.GB27116@rincewind.brq.redhat.com>
i cant english
google!?:
"Hello! I have discovered the following errors:
There seems to be a display bug: Although
"cat / sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq"
800 000 display (that is, within the limits that I did in the
cpufreqd.conf set), cpufreq-info shows stable at 2.40 GHz.
Also, "cat / proc / cpuinfo" confirmed to me that the processor
800MHz running.
Cpufreq-info seems to output wrong data.
My system: Acer Timeline 3830TG, Core i5, driver's
acpi_cpufreq and my Gentoo Linux.
Best regards,"
Am Freitag, 3. Februar 2012, 11:16:12 schrieb Petr Šabata:
> On Fri, Feb 03, 2012 at 10:59:11AM +0100, Alexander
Perschbacher wrote:
> > Hallo! Ich habe folgenden Fehler entdeckt:
> >
> > Es scheint einen Anzeige-Bug zu geben: Obwohl
> > "cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq"
> > 800000 anzeigt (also innerhalb der Grenzen, die ich in der
> > cpufreqd.conf setzte), zeigt cpufreq-info beständig 2,40GHz
an.
> > Auch "cat /proc/cpuinfo" bestätigt mir, dass der Prozessor
mit
> > 800MHz läuft.
> >
> > Cpufreq-info scheint hier falsche Daten auszugeben.
> >
> > Mein System: Acer TimelineX 3830TG, Core i5, Treiber ist
> > acpi_cpufreq und mein Linux Gentoo.
> >
> >
> > Liebe Grüße,
>
> I suggest you resend your email in English if you expect any
help.
>
> -P
>
> > --
> > To unsubscribe from this list: send the line "unsubscribe
cpufreq" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-
info.html
prev parent reply other threads:[~2012-02-03 10:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-03 9:59 Bug entdeckt Alexander Perschbacher
2012-02-03 10:16 ` Petr Šabata
2012-02-03 10:31 ` Alexander Perschbacher [this message]
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=11576422.T8BdOecNyQ@elabi \
--to=alexander.perschbacher@rub.de \
--cc=cpufreq@vger.kernel.org \
/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