xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Chen, Tiejun" <tiejun.chen@intel.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Ross Lagerwall <ross.lagerwall@citrix.com>,
	Xen-devel <xen-devel@lists.xen.org>, Keir Fraser <keir@xen.org>,
	len.brown@intel.com
Subject: Re: [PATCH 2/2] mwait_idle: Broadwell support
Date: Fri, 24 Oct 2014 11:02:57 +0800	[thread overview]
Message-ID: <5449C161.4090009@intel.com> (raw)
In-Reply-To: <5440F21A020000780003F7C3@mail.emea.novell.com>

On 2014/10/17 16:40, Jan Beulich wrote:
>>>> On 17.10.14 at 03:22, <tiejun.chen@intel.com> wrote:
>> On 2014/10/16 22:06, Jan Beulich wrote:
>>> Also, reporting issues just verbally (i.e. without any logs or other
>>> actual technical information) rarely makes a lot of sense.
>>
>> As I said above the machine reboot directly. I can't see any output.
>
> Triple faults are extremely rare. Are you sure you have
> "sync_console noreboot" in place on your hypervisor command line
> (and of course a serial console properly set up)?

Looks current BIOS can't output anything so I will try this once I get 
the latest.

Thanks
Tiejun

  reply	other threads:[~2014-10-24  3:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-08 12:42 [PATCH 1/2] mwait_idle: Disable Baytrail Core and Module C6 auto-demotion Ross Lagerwall
2014-09-08 12:42 ` [PATCH 2/2] mwait_idle: Broadwell support Ross Lagerwall
2014-09-08 13:24   ` Jan Beulich
2014-10-16 12:54   ` Chen, Tiejun
2014-10-16 14:06     ` Jan Beulich
2014-10-17  1:22       ` Chen, Tiejun
2014-10-17  8:40         ` Jan Beulich
2014-10-24  3:02           ` Chen, Tiejun [this message]
2014-10-17  1:00     ` Chen, Tiejun
2014-09-08 13:22 ` [PATCH 1/2] mwait_idle: Disable Baytrail Core and Module C6 auto-demotion Jan Beulich
2014-09-08 14:02   ` Ross Lagerwall
2014-09-08 14:20     ` Jan Beulich

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=5449C161.4090009@intel.com \
    --to=tiejun.chen@intel.com \
    --cc=JBeulich@suse.com \
    --cc=keir@xen.org \
    --cc=len.brown@intel.com \
    --cc=ross.lagerwall@citrix.com \
    --cc=xen-devel@lists.xen.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).