From: Andrew Cooper <andrew.cooper3@citrix.com>
To: "Luis R. Rodriguez" <mcgrof@suse.com>
Cc: "Luis R. Rodriguez" <mcgrof@kernel.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Xen default install - no cpufreq on dom0 ?
Date: Tue, 23 Feb 2016 23:55:48 +0000 [thread overview]
Message-ID: <56CCF184.5080504@citrix.com> (raw)
In-Reply-To: <20160223234417.GJ25240@wotan.suse.de>
On 23/02/2016 23:44, Luis R. Rodriguez wrote:
> On Tue, Feb 23, 2016 at 10:44:56PM +0000, Andrew Cooper wrote:
>> On 23/02/2016 22:18, Luis R. Rodriguez wrote:
>>> On Tue, Feb 23, 2016 at 05:00:12PM -0500, Konrad Rzeszutek Wilk wrote:
>>>> On Tue, Feb 23, 2016 at 12:48:18PM -0800, Luis R. Rodriguez wrote:
>>>>> For a while now I've been installing Xen from source on my Debian box,
>>>>> with a default configuration always. This is party why I've run into
>>>>> compile issues before it seems, but I've also just picked up on
>>>>> another possible issue. My system on dom0 overheats and shuts itself
>>>>> off. For a while I didn't think this was Xen related and perhaps
>>>>> related to the fact that I built this system myself. However, after
>>>>> running Debian without Xen (rm -rf /boot/xen*; update-grub; reboot;
>>>>> systemd-detect-virt yield none) it would seem this does not happen.
>>>>> What's a bit concerning though is even if I run offlineimap in
>>>>> singlethreaded mode (offlineimap -1) the machine overheats and shuts
>>>>> itself off, so I don't necessarily need to be doing a lot of work. I
>>>>> tried compiling the kernel without Xen while running offlineimap as
>>>>> well with make -j 8 and it doesn't overheat, meanwhile on Xen dom0
>>>>> just using offlineimap -1 seems to trigger a shutoff rather quickly.
>>>> What exactly triggers the shutoff.
>>> Clearly, overheating. I'm not yet sure if its just BIOS/kernel/hypervisor
>>> induced forced shutdown. Will try again, but this is rather intrusive as
>>> its on my personal home system.
>> You have dislodged the heat sync and the processor is shutting down due
>> to thermal cutout.
> How do I prevent this ?
Open up your computer and shuffle things around. Alternatively unclog
the fan. Possibly both.
> The difference in operation between dom0 and
> bare metal is rather extreme. Is this expected ? Is there a clutch
> I can use ?
The only thing software can control is now badly things go wrong. It is
not the source of the problem.
Baremetal probably has deep C and P states set up properly, but it will
still be under clocking as much as it can in an attempt to avoid
generating as much heat.
~Andrew
next prev parent reply other threads:[~2016-02-23 23:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-23 20:48 Xen default install - no cpufreq on dom0 ? Luis R. Rodriguez
2016-02-23 22:00 ` Konrad Rzeszutek Wilk
2016-02-23 22:18 ` Luis R. Rodriguez
2016-02-23 22:36 ` Konrad Rzeszutek Wilk
2016-02-23 22:44 ` Andrew Cooper
2016-02-23 23:44 ` Luis R. Rodriguez
2016-02-23 23:55 ` Andrew Cooper [this message]
2016-04-06 3:18 ` Luis R. Rodriguez
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=56CCF184.5080504@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=mcgrof@kernel.org \
--cc=mcgrof@suse.com \
--cc=xen-devel@lists.xensource.com \
/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).