From: "Christopher S. Aker" <caker@theshore.net>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: xen devel <xen-devel@lists.xensource.com>
Subject: Re: Xen 3.2.1-rc5: FATAL PAGE FAULT
Date: Tue, 22 Apr 2008 15:39:56 -0400 [thread overview]
Message-ID: <480E3F0C.6080803@theshore.net> (raw)
In-Reply-To: <C433F11A.17BD4%keir.fraser@eu.citrix.com>
Keir Fraser wrote:
> The second crash is just some overzealous asserting. Easily fixed but also
> not very interesting, unfortunately.
>
> The two main backtraces are exactly the same bug as you saw last time.
> Except in this case you have bogus nonsense in a pair of L2 pagetable
> entries, whereas last time the garbage was in an L3 entry.
>
> My best guess just now, seeing as noone else has reported ever seeing this,
> is that maybe you have a bad driver or hardware corrupting memory? Obviously
> that's a bit of a stab in the dark though.
>
> Have you seen this particular type of crash on multiple different machines?
> If so, are they different types of machine?
Two machines thus far, both are of identical software and hardware
configurations.
Now that it looks like the 3ware issues have been corrected in post-Xen
3.1 dom0, I'll update our boxes from 2.6.16.x to 2.6.18.8 and hope for
the best.
Thanks for your help so far.
-Chris
next prev parent reply other threads:[~2008-04-22 19:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-03 4:34 Xen 3.2.1-rc1: FATAL PAGE FAULT Christopher S. Aker
2008-04-03 14:04 ` Christopher S. Aker
2008-04-03 15:55 ` Keir Fraser
2008-04-22 18:19 ` Xen 3.2.1-rc5: " Christopher S. Aker
2008-04-22 18:46 ` Keir Fraser
2008-04-22 19:39 ` Christopher S. Aker [this message]
2008-04-22 20:21 ` Keir Fraser
2008-04-28 14:02 ` Christopher S. Aker
2008-04-28 14:44 ` Keir Fraser
2008-04-28 15:00 ` Christopher S. Aker
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=480E3F0C.6080803@theshore.net \
--to=caker@theshore.net \
--cc=keir.fraser@eu.citrix.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.