xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: David F Barrera <dfbp@us.ibm.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: "Xen development list" <xen-devel@lists.xensource.com>,
	"Stephan Böni" <boeni@bpm.ch>
Subject: Re: bug report
Date: Fri, 21 Oct 2005 06:28:04 -0500	[thread overview]
Message-ID: <4358D0C4.4090902@us.ibm.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D32E4F7@liverpoolst.ad.cl.cam.ac.uk>

Ian,

I replied to that original message indicating that I did not see the 
problem anymore, since aroung changeset 7396. Stephan replied that he 
had been wrong, working on an older build (reply copied below).


David

Hi David


>>> > 1. Time stopped (Build 7398)
>>    
>>
>> That's odd. I have not seen this problem since Monday, using 
>> changesets
>> 7396 and up. 
>  
>

You have right. As i've tested it, it was on an older build.
7398 i've installed just later. sorry, my fault.

Stephan



Ian Pratt wrote:

>>1. Time stopped (Build 7398)
>>
>>When starting a domU the system time (in dom0) stopps for a 
>>few seconds and sometimes forever. With disabled Hyperthreading or
>>maxcpus=1 all works fine.
>>    
>>
>
>Can anyone repro this?
>Are you using the -xen kernel config?
>
>Ian
>
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@lists.xensource.com
>http://lists.xensource.com/xen-devel
>
>  
>

  reply	other threads:[~2005-10-21 11:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-21  8:42 bug report Ian Pratt
2005-10-21 11:28 ` David F Barrera [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-12-22 20:07 Bug report Ing. Ricardo Brisighelli
2016-12-23 13:15 ` Wei Liu
2005-10-20 16:47 bug report Stephan Böni
2005-10-20 12:47 Stephan Böni
2005-10-20 15:28 ` David F Barrera

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=4358D0C4.4090902@us.ibm.com \
    --to=dfbp@us.ibm.com \
    --cc=boeni@bpm.ch \
    --cc=m+Ian.Pratt@cl.cam.ac.uk \
    --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).