xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <ijc@hellion.org.uk>
To: Mauro <mrsanna1@gmail.com>
Cc: "599161@bugs.debian.org" <599161@bugs.debian.org>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: #599161: Xen debug patch for the "clock shifts by 50 minutes" bug.
Date: Fri, 26 Oct 2012 19:40:03 +0100	[thread overview]
Message-ID: <1351276803.12176.4.camel@dagon.hellion.org.uk> (raw)
In-Reply-To: <CAE17a0WfpKHxN=3iF6F+P0nT4UbyF9Lbpm8R5+JJEquQOmudXw@mail.gmail.com>

On Fri, 2012-10-26 at 19:25 +0100, Mauro wrote:
> On 26 October 2012 14:59, Ian Campbell <ijc@hellion.org.uk> wrote:
> > Hi all,
> >
> > I've BCC'd a number of people who have reported seeing this bug at
> > various times in the past.
> >
> > If you can still repro I'd appreciate it if you could give the patch in
> > http://marc.info/?l=xen-devel&m=135049062216685&w=2 (also attached) a go
> > and report back success/failure and the output of the debugging messages
> > produced.
> 
> Is that patch for amd64 architectures?

It is for 32 and 64 bit x86, so yes.

BTW, you were the original recipient of this patch in the thread linked
above.

Ian.
-- 
Ian Campbell


"I'd love to go out with you, but I'm having all my plants neutered."

  parent reply	other threads:[~2012-10-26 18:40 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-26 12:59 #599161: Xen debug patch for the "clock shifts by 50 minutes" bug Ian Campbell
2012-10-26 18:25 ` Mauro
     [not found] ` <CAE17a0WfpKHxN=3iF6F+P0nT4UbyF9Lbpm8R5+JJEquQOmudXw@mail.gmail.com>
2012-10-26 18:40   ` Ian Campbell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-11-07 10:10 Philippe.Simonet
2012-11-07 13:22 ` Ian Campbell
2012-11-07 17:40   ` Keir Fraser
2012-11-08  9:39     ` Jan Beulich
2012-11-08 10:38       ` Keir Fraser
2012-11-08 13:53         ` Jan Beulich
2012-11-08 14:04           ` Keir Fraser
2012-11-08 13:47       ` Philippe.Simonet
2012-11-08 14:29         ` Ian Campbell
2012-11-08 15:21         ` Mauro
     [not found]         ` <1352384968.12977.104.camel@hastur.hellion.org.uk>
2012-11-09  9:05           ` Philippe.Simonet
     [not found]           ` <FF93AF260AC2BB499A119CC65B092CF73151901D@sg000713.corproot.net>
2012-11-09  9:47             ` Jan Beulich
2012-11-09  9:54               ` Mauro
2012-11-13 10:14             ` Jan Beulich
2012-11-08 16:45       ` Tim Deegan
2012-11-08 16:53         ` Keir Fraser
2012-11-08 11:43     ` Ian Campbell
2012-11-08 14:20     ` Keir Fraser
2012-11-07 17:07 ` Jan Beulich
     [not found] <1352375011.12977.95.camel@hastur.hellion.org.uk>
2012-11-08 12:54 ` Keir Fraser
2012-11-08 14:28   ` Ian Campbell
2012-11-08 14:34     ` Keir Fraser
     [not found] <CAE17a0XdxhaoCZaDDT6RXm1DPnabf2hWXAnzU5NukHeXX45grA@mail.gmail.com>
     [not found] ` <CCCD845A.44DB0%keir.xen@gmail.com>
     [not found]   ` <CAE17a0Xit58cLiJ+pE7uKuCDq3Xn+7-5+iDpV2+5S+TX3yuT+Q@mail.gmail.com>
2012-11-26 10:20     ` Jan Beulich
2012-11-26 10:28       ` Mauro
2012-11-26 10:40         ` Ian Campbell
2012-11-26 12:18           ` Jan Beulich
2012-11-26 13:08             ` Philippe.Simonet
2012-11-26 14:15               ` Sylvain Munaut
2012-11-26 14:29               ` 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=1351276803.12176.4.camel@dagon.hellion.org.uk \
    --to=ijc@hellion.org.uk \
    --cc=599161@bugs.debian.org \
    --cc=mrsanna1@gmail.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).