From: Sergio Monteiro Basto <sergio@sergiomb.no-ip.org>
To: Pavel Troller <patrol@sinus.cz>
Cc: linux-acpi@vger.kernel.org
Subject: Re: Strange things on 2.6.19/20 for a dual-core CPU
Date: Tue, 06 Feb 2007 00:04:02 +0000 [thread overview]
Message-ID: <1170720242.4926.17.camel@monteirov> (raw)
In-Reply-To: <20070205060404.GA23121@tangens.sinus.cz>
[-- Attachment #1: Type: text/plain, Size: 2924 bytes --]
On Mon, 2007-02-05 at 07:04 +0100, Pavel Troller wrote:
> Hi!
> I posted the following question, when 2.6.19 was freshly out. However, nobody
> has answered. OK, I told myself, let's get things to stabilize, and I waited
> patiently for 2.6.20. Now, the things are absolutely the same, and IMHO wrong.
> Could anybody look at this and decide, whether it is a real bug, which has to
> be fixed, or not ?
Hi , I also have a Pentium D with a very strange things
http://bugzilla.kernel.org/show_bug.cgi?id=6419
have you test yours in older kernels?
> With regards, Pavel Troller
>
> ----- Forwarded message from Pavel Troller <patrol@sinus.cz> -----
>
> From: Pavel Troller <patrol@sinus.cz>
> To: linux-acpi@vger.kernel.org
> Subject: Strange things on 2.6.19 for a dual-core CPU
> Mail-Followup-To: Pavel Troller <patrol@sinus.cz>,
> linux-acpi@vger.kernel.org
> Content-Disposition: inline
> User-Agent: Mutt/1.5.9i
>
> Hi!
> I've updated to vanilla 2.6.19 on my Pentium-D (dual-core x86_64) box.
> Now I can't see even C1 in the /proc/acpi/processor/*/power output:
> patrol@arcus:~$ cat /proc/acpi/processor/CPU1/power
> active state: C0
> max_cstate: C8
> bus master activity: 00000000
> maximum allowed latency: 2000 usec
> states:
> patrol@arcus:~$ cat /proc/acpi/processor/CPU2/power
> active state: C0
> max_cstate: C8
> bus master activity: 00000000
> maximum allowed latency: 2000 usec
> states:
>
> Another interesting thing is shown here:
> patrol@arcus:~$ cat /proc/acpi/processor/CPU1/info
> processor id: 0
> acpi id: 1
> bus mastering control: no
> power management: no
> throttling control: yes
> limit interface: yes
> patrol@arcus:~$ cat /proc/acpi/processor/CPU2/info
> processor id: 1
> acpi id: 2
> bus mastering control: no
> power management: no
> throttling control: no
> limit interface: no
>
> As I remember, both cores were showing the same things formerly.
> The only line referring to CPUs during boot is
> ACPI: Processor [CPU1] (supports 8 throttling states)
> and CPU2 is not mentioned at all.
>
> The last (but maybe not acpi-related) strange thing is that in /proc/cpuinfo,
> CPU1 reports 6403.56 bogomips (as always, approximately twice the clock) and CPU2
> 8314.32 ones (too much). It's also very suspicious. Formerly the difference was
> very small.
>
> Should I provide more info to debug these things, or is it OK ?
> With regards, Pavel Troller
>
> ----- End forwarded message -----
> -
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Sérgio M.B.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 2192 bytes --]
prev parent reply other threads:[~2007-02-06 0:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-05 6:04 Strange things on 2.6.19/20 for a dual-core CPU Pavel Troller
2007-02-05 6:34 ` Luming Yu
2007-02-06 1:05 ` Sergio Monteiro Basto
2007-02-06 0:04 ` Sergio Monteiro Basto [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=1170720242.4926.17.camel@monteirov \
--to=sergio@sergiomb.no-ip.org \
--cc=linux-acpi@vger.kernel.org \
--cc=patrol@sinus.cz \
/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