xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Cris Daniluk <cris.daniluk@gmail.com>
To: Jan Beulich <JBeulich@novell.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Xen 4.0 crashes with pvops kernel
Date: Tue, 15 Jun 2010 09:49:29 -0400	[thread overview]
Message-ID: <AANLkTinzH8yDGFREonrJwAn3A9SYYhC_1u_543tbsXWz@mail.gmail.com> (raw)
In-Reply-To: <4C179FBC020000780000685D@vpn.id2.novell.com>

[-- Attachment #1: Type: text/plain, Size: 689 bytes --]

On Tue, Jun 15, 2010 at 9:43 AM, Jan Beulich <JBeulich@novell.com> wrote:
>>>> On 15.06.10 at 15:24, Cris Daniluk <cris.daniluk@gmail.com> wrote:
>> For what its worth, it happened in 2.6.32.11 in addition to 2.6.32.13.
>> I also had earlier tried a 2.6.31 pvops distro kernel with the same
>> results last week. Interestingly, I also tried a 2.6.31 kernel with
>> Xen 3.4 on the same hardware with no issues. It seems like XenLinux
>> kernel with Xen 4.0 is fine, and pvops with Xen 3.x is fine.
>
> That's odd, but perhaps the kernel behaves differently on older Xen.
> Attempts to map IO-APIC space should be disallowed by 3.4 just as
> with 4.0.
>

SSDT and DSDT dumps attached.

Cris

[-- Attachment #2: acpidump.tgz --]
[-- Type: application/x-gzip, Size: 7515 bytes --]

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

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

  reply	other threads:[~2010-06-15 13:49 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-14 22:10 Xen 4.0 crashes with pvops kernel Cris Daniluk
2010-06-15  6:54 ` Jan Beulich
     [not found]   ` <AANLkTimslcbXQnihpIB0c-ceWbD7H-eyUY_BV2igyfzv@mail.gmail.com>
2010-06-15 12:50     ` Jan Beulich
2010-06-15 12:56       ` Keir Fraser
2010-06-15 13:20         ` Jan Beulich
2010-06-15 13:24           ` Cris Daniluk
2010-06-15 13:43             ` Jan Beulich
2010-06-15 13:49               ` Cris Daniluk [this message]
2010-06-15 14:13                 ` Jan Beulich
2010-06-15 14:35                   ` Cris Daniluk
2010-06-15 14:58                     ` Jan Beulich
2010-06-15 15:01                       ` Cris Daniluk
2010-06-15 15:21                         ` Jan Beulich
2010-06-15 16:18                           ` Boris Derzhavets
2010-06-15 14:17               ` Pasi Kärkkäinen
2010-06-15 15:11                 ` Konrad Rzeszutek Wilk
2010-06-16 14:42                   ` Jan Beulich
2010-06-15 13:57           ` Jan Beulich
2010-06-15 15:15             ` Konrad Rzeszutek Wilk
2010-06-16 14:36               ` Jan Beulich
2010-06-24  9:29             ` Jeremy Fitzhardinge
2010-06-24 11:30               ` Jan Beulich
2010-06-24 21:25                 ` 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=AANLkTinzH8yDGFREonrJwAn3A9SYYhC_1u_543tbsXWz@mail.gmail.com \
    --to=cris.daniluk@gmail.com \
    --cc=JBeulich@novell.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 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).