All of lore.kernel.org
 help / color / mirror / Atom feed
From: woody <marvel@us.ibm.com>
To: Mark Williamson <mark.williamson@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: [bug?] xm sysrq == Internal Server Error
Date: Mon, 28 Mar 2005 17:03:43 -0800	[thread overview]
Message-ID: <4248A96F.60006@us.ibm.com> (raw)
In-Reply-To: <004001c533f6$101d3c50$0201a8c0@hawk>


[-- Attachment #1.1: Type: text/plain, Size: 1328 bytes --]

Mark,

Thanks, if these patches are in 2.0 and 2.0-testing, will they be in 
xen-unstable?

wm
============

Christopher S. Aker wrote:

>>I think the Python build system must have done something weird on your system 
>>- I just tested the patches and they fix the problem for me, whereas without 
>>them I see the same error you are getting.
>>
>>Can you double check your tools install?  You may find it helps to blow away 
>>the current Xen Python libraries!  I have occasionally had issues with the 
>>Python's build / install system before.
>>    
>>
>
>Yeah -- I did blow away /usr/lib/python/xen, but forgot to restart xend :/  
>
>   # xm sysrq domain3 s
>
>   xennode root # dmesg 
>   SysRq : Emergency Sync
>   Emergency Sync complete
>
>Thanks!  It works now -- nice job :)
>
>-Chris
>
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@lists.xensource.com
>http://lists.xensource.com/xen-devel
>
>  
>

-- 
Sincerely, Woody Marvel   LTC Open Source Projects   Beaverton, OR
tel: 503-578-3833/775-3833	email: marvel@us.ibm.com
=======================================================================
"The branch is not only ever near the stem, but ever receiving life and fruitfulness from it." -- C.H.Spurgeon
=======================================================================


[-- Attachment #1.2: Type: text/html, Size: 2015 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

  parent reply	other threads:[~2005-03-29  1:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-25 17:13 [bug?] xm sysrq == Internal Server Error Christopher S. Aker
2005-03-28 16:02 ` Mark Williamson
2005-03-28 18:05   ` Christopher S. Aker
2005-03-28 18:59     ` Mark Williamson
2005-03-28 20:12       ` Christopher S. Aker
2005-03-28 23:56         ` Mark Williamson
2005-03-29  0:27           ` Christopher S. Aker
2005-03-29  0:41             ` Mark A. Williamson
2005-03-29  1:03             ` woody [this message]
2005-03-29  1:07               ` Mark A. Williamson
  -- strict thread matches above, loose matches on Subject: below --
2005-03-25 19:34 Ian Pratt
2005-03-25 19:59 ` Christopher S. Aker
2005-03-25 23:21   ` woody

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=4248A96F.60006@us.ibm.com \
    --to=marvel@us.ibm.com \
    --cc=mark.williamson@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 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.