From: Jan Kiszka <jan.kiszka@siemens.com>
To: Christophe Thil <christophe@thil.de>, Len Brown <len.brown@intel.com>
Cc: Ben Hutchings <ben@decadent.org.uk>,
763320@bugs.debian.org, linux-pm@vger.kernel.org
Subject: Re: Bug#763320: linux-image-3.16-2-amd64: intel_idle enabled for Intel Atom S1260, causes high CPU temperature when idle
Date: Wed, 01 Oct 2014 15:01:37 +0200 [thread overview]
Message-ID: <542BFB31.8000402@siemens.com> (raw)
In-Reply-To: <269B8283-9171-4EBD-9852-0796A4AA2008@thil.de>
On 2014-10-01 14:42, Christophe Thil wrote:
> I have attached the output of /proc/cpuinfo (kernel 3.16-2-amd64) and cpuid (20140123).
This is from my N2800:
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 54
model name : Intel(R) Atom(TM) CPU N2800 @ 1.86GHz
stepping : 1
microcode : 0x10d
cpu MHz : 798.000
cache size : 512 KB
physical id : 0
siblings : 4
core id : 0
cpu cores : 2
apicid : 0
initial apicid : 0
fdiv_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc arch_perfmon pebs bts nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl est tm2 ssse3 cx16 xtpr pdcm movbe lahf_lm arat dtherm
bogomips : 3733.68
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
Comparing it to your cpuinfo, the stepping may make the difference -
hope it's not just the name... Suggestions?
Jan
--
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2014-10-01 13:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140929095709.3255.93208.reportbug@izoard.lan>
2014-09-30 0:13 ` Bug#763320: linux-image-3.16-2-amd64: intel_idle enabled for Intel Atom S1260, causes high CPU temperature when idle Ben Hutchings
2014-09-30 5:56 ` Jan Kiszka
2014-10-01 12:42 ` Christophe Thil
2014-10-01 13:01 ` Jan Kiszka [this message]
2014-10-09 4:37 ` Brown, Len
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=542BFB31.8000402@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=763320@bugs.debian.org \
--cc=ben@decadent.org.uk \
--cc=christophe@thil.de \
--cc=len.brown@intel.com \
--cc=linux-pm@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;
as well as URLs for NNTP newsgroup(s).