All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christopher S. Aker" <caker@theshore.net>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: xen devel <xen-devel@lists.xensource.com>
Subject: Re: LVM userspace causing dom0 crash
Date: Mon, 07 May 2012 15:59:14 -0400	[thread overview]
Message-ID: <4FA82992.1030508@theshore.net> (raw)
In-Reply-To: <4FA81669.5040202@theshore.net>

On 5/7/12 2:37 PM, Christopher S. Aker wrote:
> This looks suspiciously like the problem described by Nai Xia in "mm:
> page_check_address bug fix and make it validate subpages in huge pages"
> <http://lkml.org/lkml/2011/3/28/196> - which never made it into mainline
> that I can detect.
>
> We've rebuilt without CONFIG_HIGHPTE and are running our test again. We
> shall see.

No joy just disabling CONFIG_HIGHPTE.  Triggered it on four boxes in no 
time.  Bugs out exactly the same as before except the second BUG 
"scheduling while atomic" doesn't happen.

On 5/7/12 1:17 PM, Konrad Rzeszutek Wilk wrote:
> Hm, can you give more details on what parameters you are passing to
> dom0 and the hypervisor so I can reproduce it?

Xen and dom0 binaries and modules, and arguments here:

http://theshore.net/~caker/xen/BUGS/lvm/

This is atop hardware RAID -- we haven't tested on anything other than 
Supermicro motherboards.

Thanks,
-Chris

  reply	other threads:[~2012-05-07 19:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-07 15:36 LVM userspace causing dom0 crash Christopher S. Aker
2012-05-07 17:17 ` Konrad Rzeszutek Wilk
2012-05-07 18:37   ` Christopher S. Aker
2012-05-07 19:59     ` Christopher S. Aker [this message]
2012-05-10 15:49       ` Christopher S. Aker
2012-05-11 15:39 ` Konrad Rzeszutek Wilk
2012-05-11 18:30 ` Konrad Rzeszutek Wilk
2012-05-11 22:40   ` Christopher S. Aker
2012-05-24 17:56     ` 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=4FA82992.1030508@theshore.net \
    --to=caker@theshore.net \
    --cc=konrad.wilk@oracle.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.