From: Shaun Reitan <mailinglists@unix-scripts.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: 2.6.35.7 pvops crash
Date: Fri, 19 Nov 2010 09:49:46 -0800 [thread overview]
Message-ID: <4CE6B8BA.9080708@unix-scripts.com> (raw)
In-Reply-To: <4CE6B419.5050607@goop.org>
Sorry probably should have gave you more info...
> xen-devel is probably the right place for this, but its a bit unclear
> what's going on here. Unfortunately your report is missing the most
> interesting information.
Ya, unfortunately i don't have more of the crash for you. I'll try to
get more if i can reproduce it!
> Can you go into more detail about what's going on here? This is a 32bit
> kernel, but what are the other details? What kernel version is it (is
> it a distro kernel?) dom0? domU? Which version of Xen? What was the
> system doing at the time?
Dom0 OS is CentOS 4
Dom0 Kernel version is 2.6.18.8
Xen Version is 3.4.0
This crash is from a DomU
As for what the system was doing I'm unsure, this is a customer's domU.
~Shaun
next prev parent reply other threads:[~2010-11-19 17:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-19 17:15 2.6.35.7 pvops crash Shaun Reitan
2010-11-19 17:30 ` Jeremy Fitzhardinge
2010-11-19 17:49 ` Shaun Reitan [this message]
2010-11-19 18:04 ` Jeremy Fitzhardinge
2010-11-19 18:32 ` Shaun Reitan
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=4CE6B8BA.9080708@unix-scripts.com \
--to=mailinglists@unix-scripts.com \
--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.