All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: sven <ml@infinitumb.de>
Cc: "Alan J. Wylie" <NDA5OWUy@wylie.me.uk>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Gianni Tedesco <gianni.tedesco@citrix.com>,
	Andreas Kinzler <ml-xen-devel@hfp.de>
Subject: Re: Xen dom0 crash in get_phys_to_machine
Date: Fri, 12 Nov 2010 16:53:31 -0800	[thread overview]
Message-ID: <4CDDE18B.204@goop.org> (raw)
In-Reply-To: <4CDDC288.3000401@infinitumb.de>

On 11/12/2010 02:41 PM, sven wrote:
> is there any news regarding this problem?
>
> This evening I tried next-2.6.32 again, but still no luck.
>
> (..had the slight hope the recent changes about lowest-megabyte memory
> area might have fixed this, too .. but ..)

Sorry, I'd set it to one side while dealing with all the 2.6.37
upstreaming work.  Unfortunately I don't have a machine which reproduces
this problem, so I've been relying on other people's reports, and they
haven't shown any smoking guns yet.

But I have been seeing other odd things occasionally which could be the
same problem in different guises, so I'll see if I can track those down.

Thanks,
    J

  reply	other threads:[~2010-11-13  0:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-12  7:55 Xen dom0 crash in get_phys_to_machine Alan J. Wylie
2010-10-13  0:19 ` Jeremy Fitzhardinge
2010-10-22 12:47 ` Alan J. Wylie
2010-11-12 22:41   ` sven
2010-11-13  0:53     ` Jeremy Fitzhardinge [this message]
2010-10-22 13:05 ` Gianni Tedesco
2010-10-22 13:33   ` Alan J. Wylie
2010-10-22 13:45     ` Gianni Tedesco
2010-10-22 14:20       ` Alan J. Wylie
2010-10-22 22:26   ` Jeremy Fitzhardinge

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=4CDDE18B.204@goop.org \
    --to=jeremy@goop.org \
    --cc=NDA5OWUy@wylie.me.uk \
    --cc=gianni.tedesco@citrix.com \
    --cc=ml-xen-devel@hfp.de \
    --cc=ml@infinitumb.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.